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
Related
Hi, I am new to rooting my tablet. I manage to unlock my tablet "asus tf700" but i cannot for the life of me understand how to root this. I have read all the threads/posts regarding this issue but since its my first time i dont understand what "flashing" means or "bootloader". Please any step by step advice is greatly appreciated.
I have the ASUS TF700T Infinity Jellybean Android 4.1.1 I believe it is unlocked because I am able to go into that screen and theres four Icons.
Pms or a step by step guide for this noob because i dont understand any of these terms =(
Sorry for the trouble and thanks in advance
Cheers,
deocare
deocare said:
Hi, I am new to rooting my tablet. I manage to unlock my tablet "asus tf700" but i cannot for the life of me understand how to root this. I have read all the threads/posts regarding this issue but since its my first time i dont understand what "flashing" means or "bootloader". Please any step by step advice is greatly appreciated.
I have the ASUS TF700T Infinity Jellybean Android 4.1.1 I believe it is unlocked because I am able to go into that screen and theres four Icons.
Pms or a step by step guide for this noob because i dont understand any of these terms =(
Sorry for the trouble and thanks in advance
Cheers,
deocare
Click to expand...
Click to collapse
also tried reverting back to ICS to do that auto root but had no idea what "fastlooader" was..
sorry im a total noob at this
deocare said:
also tried reverting back to ICS to do that auto root but had no idea what "fastlooader" was..
sorry im a total noob at this
Click to expand...
Click to collapse
Not too worry, it's very simple, just download the zip, then unzip and double click on the bat file, then follow on screen instruction.
Here is a nice instruction for rooting:
http://tutznet.com/root-tf700t-asus-...-infinity.html
this will work with the specs for my tablet? jellybean etc..?
does not work... i tried this debug already it says failed i think because it doesn't support jellybean.
deocare said:
does not work... i tried this debug already it says failed i think because it doesn't support jellybean.
Click to expand...
Click to collapse
no, it's for ics only, I thought you are on ICS? well you downgrade back to .30 then use my method above, If you don't want to downgrade, then you must unlocked first then follow this method:
http://forum.xda-developers.com/showthread.php?t=1916762
You put your device in fastboot mode, by turn off your device, hold volume down and power button, when you will see white text appeared on the screen release both, hit volume down to navigate to the USB icon, then hit volume up to select and now you are fastboot. plug in your usb cable then open fastboot command on your pc and do your thing.
buhohitr said:
no, it's for ics only, I thought you are on ICS? well you downgrade back to .30 then use my method above, If you don't want to downgrade, then you must unlocked first then follow this method:
http://forum.xda-developers.com/showthread.php?t=1916762
You put your device in fastboot mode, by turn off your device, hold volume down and power button, when you will see white text appeared on the screen release both, hit volume down to navigate to the USB icon, then hit volume up to select and now you are fastboot. plug in your usb cable then open fastboot command on your pc and do your thing.
Click to expand...
Click to collapse
sorry i dont understand that concept of flashing can you go through it with me on how to do it
deocare said:
sorry i dont understand that concept of flashing can you go through it with me on how to do it
Click to expand...
Click to collapse
Not a problem, but I need to verify what your setup first.
1. Are you on Jelly Bean?
2. Are you unlocked? (when you turn on your device, it should displays "device is unlocked"
3. Do you have SDK and fastboot/ADB tool installed on your device?
Once you answered all 3 questions, I will recommend the easiest way to root.
buhohitr said:
Not a problem, but I need to verify what your setup first.
1. Are you on Jelly Bean?
2. Are you unlocked? (when you turn on your device, it should displays "device is unlocked"
3. Do you have SDK and fastboot/ADB tool installed on your device?
Once you answered all 3 questions, I will recommend the easiest way to root.
Click to expand...
Click to collapse
1.yes
2.yes
3. maybe? not sure i have been trying alot of random things trying to root it so im not sure if its installed on my device
deocare said:
1.yes
2.yes
3. maybe? not sure i have been trying alot of random things trying to root it so im not sure if its installed on my device
Click to expand...
Click to collapse
OK, we need to verify if your fastboot is working or not. Put your device in fastboot mode (see my thread above..how to select the usb icon). On your pc, go to the folder that you have fastboot command (should be fastboot.exe). Open window command prompt, navigate to the folder where "fastboot.exe" located (usually located in "platform-tools" folder), then execute this :
type in:
fastboot devices
hti enter, you should be device ID show up
again type:
fastboot reboot
then hit enter
Your device should reboot. If it does, your fastboot is working.
buhohitr said:
OK, we need to verify if your fastboot is working or not. Put your device in fastboot mode (see my thread above..how to select the usb icon). On your pc, go to the folder that you have fastboot command (should be fastboot.exe). Open window command prompt, navigate to the folder where "fastboot.exe" located (usually located in "platform-tools" folder), then execute this :
type in:
fastboot devices
hti enter, you should be device ID show up
again type:
fastboot reboot
then hit enter
Your device should reboot. If it does, your fastboot is working.
Click to expand...
Click to collapse
i dont know where this fastboot.exe is
is there a link i can get it from
deocare said:
i dont know where this fastboot.exe is
is there a link i can get it from
Click to expand...
Click to collapse
Here you go, instruction and fastboot download.
http://forum.xda-developers.com/showpost.php?p=27218675&postcount=20
okay i have no idea it does not work i opend cmd prompt got the bootloader but the commands dont work heres a Screen
{
"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"
}
@deocare
first you have to "cd" into the path wehre you store the fastboot.exe.Ideally you've installed a full android sdk with adb, etc. After setup your android sdk and fastboot, make sure that you're tablet is booted in fastboot mode and you've installed the fastboot drivers, e.g. from universal naked driver package. After this you can send fastboot commands to your tablet but please note that it doesn't answer to fastboot devices.
Here are some threads explaining how to setup fastboot and how to after flashing jellybean, e.g. chainfires SU.
thunderger said:
@deocare
first you have to "cd" into the path wehre you store the fastboot.exe.Ideally you've installed a full android sdk with adb, etc. After setup your android sdk and fastboot, make sure that you're tablet is booted in fastboot mode and you've installed the fastboot drivers, e.g. from universal naked driver package. After this you can send fastboot commands to your tablet but please note that it doesn't answer to fastboot devices.
Here are some threads explaining how to setup fastboot and how to after flashing jellybean, e.g. chainfires SU.
Click to expand...
Click to collapse
I installed the drivers already i believe i checked under portable devices and it says "TF700t transfomer pad.." and I am in booted in fastboot mode with the power+volume down key and went over to the USB icon then opened cmd prompt
deocare said:
I installed the drivers already i believe i checked under portable devices and it says "TF700t transfomer pad.." and I am in booted in fastboot mode with the power+volume down key and went over to the USB icon then opened cmd prompt
Click to expand...
Click to collapse
Based on your screen shot, you put the "fastboot folder" on your desktop. Do this.
open cmd
type:
cd\ then hit enter
you should see:
c:\
now type:
cd users\david\desktop\fastboot then hit enter
you should see
c:\users\david\desktop\fastboot>
now type:
fastboot devices then hit enter
you should see device ID
now type:
fastboot reboot then hit enter
your device should reboot.
buhohitr said:
Based on your screen shot, you put the "fastboot folder" on your desktop. Do this.
open cmd
type:
cd\ then hit enter
you should see:
c:\
now type:
cd users\david\desktop\fastboot then hit enter
you should see
c:\users\david\desktop\fastboot>
now type:
fastboot devices then hit enter
you should see device ID
now type:
fastboot reboot then hit enter
your device should reboot.
Click to expand...
Click to collapse
i am gonna assume it is not installed properly doesn't show devices and it says rebooting but doesn't.
deocare said:
i am gonna assume it is not installed properly doesn't show devices and it says rebooting but doesn't.
Click to expand...
Click to collapse
Do you have your table booted in fastboot mode and usb cable plug into your PC?
i doo
deocare said:
i doo
Click to expand...
Click to collapse
OK, you problably don't have android sdk instalaled. Here is the link to install SDK. When you run the sdk installation, only select anything with android packages and install, don't install everything.
http://forum.xda-developers.com/showthread.php?t=1616059
Another question is are you planing to install custom ROM??? or you just want root?
{
"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"
}
Setup, Preparation and Prerequisites
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
USB Debugging - On your nexus player go to Settings > About > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enter bootloader mode - Hold the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
Once you are in fastboot mode, the light below nexus player will be blinking constantly. You can verify by using "fastboot devices"
ADB Installation
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 here
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**
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
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.
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 done.
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal storage (pictures, music, etc.). Copy all important files off the nexus player onto a PC or upload them to a cloud.
Driver Installation
Go to Device Manager, find the Android device, and select Update Driver Software.
Select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer
Selecting show all devices
Clicking have disk
Finally selecting Desktop\android-sdk-windows\extras\google\usb_driver\android_winusb.inf as the driver
Alternative you can also download and install the Universal ADB Driver.
Downloads
Root:
Android 7.X:
- Coming Soon-
Android 6.X:
http://cord-cutters.wonderhowto.com/how-to/root-nexus-player-0160218/
http://androidflagship.com/16765-root-nexus-player-android-6-0-marshmallow
Android 5.X:
Download the SuperSU zip below. Extract the zip file and you will have (root.img) to platform-tools folder located on your desktop within the android-sdk-windows folder.
SuperSU (Forum Thread) or SuperSU (Direct link)
Information
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 2 main steps: Unlocking the Bootloader and Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the device in future.
Rooting: You can gain root booting up root.img
1. Unlocking Bootloader
Turn the nexus player off. Then go into bootloader mode by holding the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
Plug nexus player into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your nexus player serial number shows up you are good to go and may continue. If the nexus player is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the nexus player has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
OEM unlock twice
Code:
fastboot oem unlock
Code:
fastboot oem unlock
After you have done, please proceed onto the next section of the guide.
2. Installing a Custom Recovery
http://forum.xda-developers.com/nex...recovery-twrp-2-8-6-0-touch-recovery-t3114717
https://twrp.me/devices/asusnexusplayer.html
3. Rooting
Now that your nexus player has an unlocked bootloader, now this step is to gain root
Android 7.X
- coming soon -
Android 6.X
Require: TWRP, Custom boot.img and flashable supersu
(Refer to above link)
Android 5.0
Warning: This rooting guide is for Android 5.X only!
Boot (not flash) the root image which will give you root with the stock ROM
Confirm that you have downloaded the SuperSU zip from the downloads section above and you have extracted it and it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Make sure the nexus player is in bootloader mode
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot boot root.img
This will install SuperSU on your device, once the command has completed continue.
Open SuperSU and update the binaries.
Keep in mind that the first boot may take longer than usual.
Congrats! Your nexus player now has an unlocked bootloader, and is rooted.
==================================================
How to flash factory image for Nexus Player?
1) Download image file for your nexus player - https://developers.google.com/android/nexus/images
2) Boot your Nexus device into fastboot mode.
3) On your computer, use 7zip to extract the .tgz file you downloaded from the Android Developer website. Use 7zip a second time to extract the .tar file you extracted from the .tgz. When you’re done, you should have a folder with several files in it.
4) Copy all of these files and paste them in the platform-tools folder in the Android SDK on your computer. If you followed the above tutorial, this should be under the C drive, then under Program Files (x86) on Windows. Linux users, you know where you put it.
5) If you have not already done so, connect your Nexus device to your computer. ADB and Fastboot commands should already work at this point if you’ve been following along.
There are two flash-all files. If you’re in Windows, you’ll want to double click the one that has the gear logo and says “Windows Batch File” on the right. If you’re on Linux, you’ll want to double click the flash-all.sh.
At this point a box should pop up and you should see the installation taking place. While this is going on, do not unplug your device for any reason. Let it do its thing.
6) Once the installation process as finished, your device will automatically reboot and you can now safely disconnect your device from your computer.
==================================================
Credits:
- Chainfire (SuperSU and Rooting guide)
- Chromium (Easy to understand and detailed guide format)
- DevinWatson (USB driver guide)
- androidauthority (Flash firmware image guide)
Nice guide.
What about installing BusyBox?
I have a USB OTG cable but the adapter is female on the available USB side...I am not sure how to go about connecting my laptop/PC to the NP in order to perform ADB commands. Do I need a special cable or is there another way?
arecad said:
I have a USB OTG cable but the adapter is female on the available USB side...I am not sure how to go about connecting my laptop/PC to the NP in order to perform ADB commands. Do I need a special cable or is there another way?
Click to expand...
Click to collapse
Don't use the USB OTG cable, use a micro USB cable (same kind of cable that comes with android phones)
I cannot believe I missed that, how embarrassing. Thanks for the response, now I can follow this guide. I was thinking too hard about the OTG cable being a necessary piece of the puzzle.
I am able to get to the bootloader with no problems, I've got ADB and Fastboot installed on my PC, as well as the drivers. However ADB doesn't pick up my NexusPlayer even though fastboot does. Thoughts?
See Attachments
EDIT: Nevermind, I was expecting different responses from adb/fastboot. When in the bootloader adb will not confirm a connection, only fastboot. Sorry for being a noob...
xDragonZ said:
1. Unlocking Bootloader
[*] Turn the nexus player off. Then go into bootloader mode by holding the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
[*] Plug nexus player into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
[COLOR="red"]adb devices[/COLOR]
This command will list the connected devices. If your nexus player serial number shows up you are good to go and may continue. If the nexus player is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under adb devices.
Click to expand...
Click to collapse
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
midnightzak said:
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
Click to expand...
Click to collapse
AFAIK ADB is for Android, and Fastboot is for bootloader.
But i have the oposite problem. Mine NP is getting recognized useing ADB when normaly booted, but when i am in fastboot mode, fastboot isent working. I get no output when run 'fastboot devivces'. I have both tried to set the NP in fastboot mode by using the hiod button and plug in power, and with adb rebbot bootloader.
Any one have a clue why adb works, but not fastboot?
Double check to see if you have the latest version of fastboot. I have read that if you don't have the most up to date version the NP is not recognized.
Sleeepy2 said:
Double check to see if you have the latest version of fastboot. I have read that if you don't have the most up to date version the NP is not recognized.
Click to expand...
Click to collapse
+1 this.
goxboxlive said:
AFAIK ADB is for Android, and Fastboot is for bootloader.
But i have the oposite problem. Mine NP is getting recognized useing ADB when normaly booted, but when i am in fastboot mode, fastboot isent working. I get no output when run 'fastboot devivces'. I have both tried to set the NP in fastboot mode by using the hiod button and plug in power, and with adb rebbot bootloader.
Any one have a clue why adb works, but not fastboot?
Click to expand...
Click to collapse
Have you re-installed the Google driver when you are booted in the bootloader? The driver needs to install twice: once when booted into Android, and once when booted into the bootloader
ADB fastboot for Mac Quick Question??
Hey guys does anyone have any idea on how this can be done on a Mac....I know I know. When I initially plug in my Nexus player with the micro usb, nothing happens on my mac or the Nexus so i am guessing that the drivers are not installed. How would i go about getting these for the Mac? I have already downloaded the slim version of the ADB and Fastboot files with the platform tools into a folder on my desktop named Andriod, so i have these already. And i know that if you hold the button down on the nexus and plug the power in it brings up the bootloader screen. I just need help with the commands in terminal and where to access the drivers from. Also, on the Nexus the Developer options have already been enabled and USB debugging has been turned on. If anyone can help, It would be much appricated! Just started to use terminal commands so yes i am a noob in this department . Thanks agin in advance.
-Jason
MrBoostinduced said:
Hey guys does anyone have any idea on how this can be done on a Mac....I know I know. When I initially plug in my Nexus player with the micro usb, nothing happens on my mac or the Nexus so i am guessing that the drivers are not installed. How would i go about getting these for the Mac? I have already downloaded the slim version of the ADB and Fastboot files with the platform tools into a folder on my desktop named Andriod, so i have these already. And i know that if you hold the button down on the nexus and plug the power in it brings up the bootloader screen. I just need help with the commands in terminal and where to access the drivers from. Also, on the Nexus the Developer options have already been enabled and USB debugging has been turned on. If anyone can help, It would be much appricated! Just started to use terminal commands so yes i am a noob in this department . Thanks agin in advance.
-Jason
Click to expand...
Click to collapse
http://developer.android.com/sdk/win-usb.html
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. To start developing with your device, read Using Hardware Devices."
http://developer.android.com/tools/device.html
Sleeepy2 said:
http://developer.android.com/sdk/win-usb.html
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. To start developing with your device, read Using Hardware Devices."
http://developer.android.com/tools/device.html
Click to expand...
Click to collapse
Hey Sleepy2, I just did a brief read through and it states this:
Set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If that is the case, what would you suggest doing next? Thanks again for helping!
MrBoostinduced said:
Hey Sleepy2, I just did a brief read through and it states this:
Set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If that is the case, what would you suggest doing next? Thanks again for helping!
Click to expand...
Click to collapse
Open a terminal, navigate to the directory where you downloaded fastboot and go ahead with the commands shown in the first post. You will probably have to add a "./" in front of the commands given that you are on a mac, e.g.,
Code:
fastboot devices
becomes
Code:
./fastboot devices
I seem to be having the same problem as goxboxlive. I have tried installing the drivers about 100x tried on several computers and rebooted many a time. The only thing I can think of from the posts in here was to update fastboot but I dled the android studio and I would assume that has the latest version in there? Otherwise I couldn't find somewhere to download just fastboot from. Any help or recommendations or where I can dl the latest fastboot?
---------- Post added at 02:28 PM ---------- Previous post was at 01:57 PM ----------
Follow up. Got it to work. In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
knobbs said:
I seem to be having the same problem as goxboxlive. I have tried installing the drivers about 100x tried on several computers and rebooted many a time. The only thing I can think of from the posts in here was to update fastboot but I dled the android studio and I would assume that has the latest version in there? Otherwise I couldn't find somewhere to download just fastboot from. Any help or recommendations or where I can dl the latest fastboot?
---------- Post added at 02:28 PM ---------- Previous post was at 01:57 PM ----------
Follow up. Got it to work. In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
Click to expand...
Click to collapse
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
midnightzak said:
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
Click to expand...
Click to collapse
knobbs said:
In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
Click to expand...
Click to collapse
midnightzak said:
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
Click to expand...
Click to collapse
To avoid further confusion, I've updated the post since the OP hadn't yet.
midnightzak said:
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
Click to expand...
Click to collapse
efrant said:
To avoid further confusion, I've updated the post since the OP hadn't yet.
Click to expand...
Click to collapse
Thank you, saw your post that time and wanted to change it but keep forgetting.
Currently working on some basic developer app for Nexus Player.
xDragonZ said:
Thank you, saw your post that time and wanted to change it but keep forgetting.
Currently working on some basic developer app for Nexus Player.
Click to expand...
Click to collapse
It's all good, wasn't terrible let to figure out, and if you're developing even more for the Nexus Player, the more power to ya! Keep it up!
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 ?
{
"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"
}
Micromax Bharat 1 is a feature phone with 4G VoLTE capability at extremely low cost.
Below are its basic specs:
Runs on Snapdragon 200.
Has a custom-made Android KitKat 4.4.4 based rom with a minimalist UI.
Has a 240x320 resolution display.
2000mAH battery.
Basic Notes:
To get into recovery mode: '*' + Power on
To get into fastboot mode: '#' + Power on
What will you find in this thread?
To enable adb and installation of apps from unknown sources.
To obtain root privileges.
Discussion and more ideas worth exploring
To enable installing from unknown sources and to enable adb, follow the instructions below.
Make sure you have installed all the necessary drivers.
Download and extract everything from the attachment to a folder.
Turn off your device.
Put it in fastboot mode and connect to your PC.
Once you can confirm that the device is correctly recognized, open up a powershell (Shift + Right click) in the extracted folder. (Or a terminal if you are using linux based distro).
Type in the following:
Code:
fastboot devices
fastboot boot recovery_V407.img
Your device will now reboot to recovery. The recovery I have provided is not complete. So you will not be able to do much with it on the device. However adb works. So let's continue.
Type in the following code to enable adb
Code:
adb shell
mount system
echo '' >> /system/build.prop
echo '# Enable ADB (By Ravikirancg)' >> /system/build.prop
echo 'persist.service.adb.enable=1' >> /system/build.prop
echo 'persist.service.debuggable=1' >> /system/build.prop
echo 'persist.sys.usb.config=mtp,adb' >> /system/build.prop
reboot
This should reboot your device.
Once you are back in the interface of your phone, you should be able to see an icon on the status bar indicating adb. Just press the left soft key and then notifications.
Now click on the notification about adb. This should take you to the hidden Developer Settings which you could not access earlier.
Scroll down and click on "Revoke USB debugging authorisations".
Turn off Debugging and back on. This should prompt a dialogue box that asks you for providing debugging authorisations. Tick always allow and then on OK. (Enter something like 'adb devices' on the powershell if required.)
Type in 'adb devices' in powershell and it should show your devices id and then 'device' instead of 'unauthorised'
Congrats! You have now enabled android debugging on Micromax Bharat 1.
Now using this, let us enable installing apks from unknown sources. To do that follow the steps below:
Type in
Code:
adb shell settings put global install_non_market_apps 1
That's it! Go ahead and install an apk file that you downloaded from the internet or sent from another phone. You will now be able to do it.
Do note that even though you can install any app you want, it is really difficult to navigate in the app as most are not designed for non-touch screen phones. Apps like share it does work well though.
Going further, if you wish to root your phone, you will need to download the latest installation zip file, extract everything and push the su binary to its place manually. And the install the apk using adb.
Well that's it for now! Go ahead and let me know what you wish to do further! Happy Hacking!
Reserved Post
It shows adb devices attached then blank.
Ravikirancg said:
Reserved Post
Click to expand...
Click to collapse
where can I get the drivers.
Sumati59697 said:
where can I get the drivers.
Click to expand...
Click to collapse
Downlaoded the drivers via Google.
Still stuck at the same place.
Network problem
No internet working on phone after fastboot boot recovery img.v407
Sumati59697 said:
No internet working on phone after flashing recovery.
Click to expand...
Click to collapse
Who asked you to flash recovery? Just boot from it.
Data not working
fastboot boot recovery_V407.img after doing this no internet.I have usb debbugging on but after that no adb devices found on adb shell it
Shows adb device attached
Like this.I have stuck at this place.
Sumati59697 said:
fastboot boot recovery_V407.img after doing this no internet.I have usb debbugging on but after that no adb devices found on adb shell it
Shows adb device attached
Like this.I have stuck at this place.
Click to expand...
Click to collapse
Post a video. Forget about internet, Its not supposed to boot into system when you use the recovery.
ashwinprakas said:
Downlaoded the drivers via Google.
Still stuck at the same place.
Click to expand...
Click to collapse
https://androidfilebox.com/tool/minimal-fastboot-adb-driver-installer/
This version worked for me on Windows 10, all good. Thank you O.P.
android go
can android go version could come in this mobile .because android go programm is for lite hardware phone.i think there would be a custom rom for this phone as the current software is very buggy.{v407}
Gapps
What about gapps
Works like a charm, hell lot of thanks ser
Can we get system updates after doing this.
Awesome! Waiting for Android GO
Unable to enable unknown apps installation
Plz tell me full procedures to enable unknown apps installation however I have enable USB debugging
Plz help any body also who have enable it.
Thanks
bharat 1 recovery mode video tutorial
i have successfully entered into recovery mode.
video tutorial- youtu.be/7WJrvzSiWZo
how plz tell full procedure line by line i hv enable usb debugging but unable to inst
Rishabh728 said:
I don't get root but i can install Apps
Click to expand...
Click to collapse
how
plz tell full procedure line by line i hv enable usb debugging but unable to install any app
Ravikirancg said:
Congrats! You have now enabled android debugging on Micromax Bharat 1.
Now using this, let us enable installing apks from unknown sources. To do that follow the steps below:
Type in
Code:
adb shell settings put global install_non_market_apps 1
Click to expand...
Click to collapse
i have Successfully able to bring on Developer Mode ON but after that adb devices when we enter it shows list of devices attached......not the device id......
for not showing Device id this last code [adb shell settings put global install_non_market_apps 1] go going on
so please help me
---------- Post added at 11:23 PM ---------- Previous post was at 11:19 PM ----------
Rajat chandra said:
Works like a charm, hell lot of thanks ser
Click to expand...
Click to collapse
but how did u able to install app from unknown sources.........i mean developer option is on but unknown source installer still not opened.......
---------- Post added at 11:25 PM ---------- Previous post was at 11:23 PM ----------
Sumati59697 said:
Can we get system updates after doing this.
Click to expand...
Click to collapse
nope u can get ota updates & updates will download but after that clicking on install the updates phone will reboot but new update file will not show the system update thus it will automatically reboot the phone but again ota update will pop up that means update will not happen........
unable to install Unknown app
After connecting phone in fastboot
Entering following code in command opne by shift+right click in adb folder.
'fastboot devices (inter)
fastboot boot recovery_V407.img (inter)
adb shell settings put global install_non_market_apps 1 (inter)
error come following:-
/sbin/sh/: settings: not found
How can it enable?????????????????
shahidalam31012018 said:
After connecting phone in fastboot
Entering following code in command opne by shift+right click in adb folder.
'fastboot devices (inter)
fastboot boot recovery_V407.img (inter)
adb shell settings put global install_non_market_apps 1 (inter)
error come following:-
/sbin/sh/: settings: not found
How can it enable?????????????????
Click to expand...
Click to collapse
Read the OP correctly. You are not supposed to do that. You are in fastboot only to modify the build prop and thus enable adb. To enable unknown sources, you need to be booted up into the rom and then have adb enabled.
Code:
#/usr/bin/env python3
from hct_principle import permission, content
print('''
Your warranty is void.
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.
''')
if content.repost('other_content_farm_website_or_tech_forum'):
if not permission:
print('Please DM me for permission')
raise Exception('RepostNotAllowedException')
Recently I got a prototype OS backup from a Nokia 5.3 engineering sample unit that contains ABL image with bootloader unlock capability.
Later I found it can be used on retail unit, but flashing it can be tough depends on Android OS version installed on your phone.
{
"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"
}
Case 1: If you already have Android 11 or 12 installed
I'm sure that's the mostly seen situation for Nokia 5.3 users. Unfortunately to do this, you'll have to open up the phone and have Qualcomm EDL driver installed, or consider to use bkerler's live DVD on your PC (prepare a spare USB drive).
1. Clone and download this repository, or just boot into LiveDVD mentioned in README. Install it according to README.
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
Also download prototype ABL and attached firehose programmer from here:
Click here to download Prototype ABL
SHA256 checksum of ABL image: C8021967F91908BBE30C4534AA2174B72FB18A204F73BB96561A3F8A17140F0E
If you see error code 00000101, please use industrial standard web browser like Google Chrome.
2. Power off your phone.
3. Follow this video to disassemble the phone, until 4:40. Make sure you have motherboard exposed and battery DISCONNECTED. Please ask an experienced technician for help if you're not familiar with phone disassembly procedure.
4. (Skip this step if you're using Linux) Change EDL port driver according to README.md of edl toolkit said, and reconnect the phone after driver changed.
5. Execute these commands to backup original ABL and write prototype ABL.
For Windows, you should be able to see Qualcomm EDL Port in Device Manager.
For Linux, you'll have to use lsusb command to check if your phone is listed.
:
Code:
./edl r abl_a,abl_b abl_a.bin,abl_b.bin --loader=/home/your_user_name/Download/prog_emmc_firehose_Sm6125_ddr.elf
./edl w abl_a /home/your_user_name/Download/CAP-abl.elf --loader=/home/your_user_name/Download/prog_emmc_firehose_Sm6125_ddr.elf
./edl w abl_b /home/your_user_name/Download/CAP-abl.elf --loader=/home/your_user_name/Download/prog_emmc_firehose_Sm6125_ddr.elf
After executed and waiting for connection, attach a side of your USB cable on your phone, then use a tweezer to short the test point indicated below. While shorting test point with tweezers, connect it to PC. You may need to repeat this when you execute next 2 commands.
6. Disconnect the phone, reattach the battery and reassemble the phone. Your phone should boot right into Fastboot mode.
7. Execute these commands to perform bootloader unlock:
Code:
fastboot flashing unlock_critical
(confirm unlock on your phone)
fastboot oem unlock-go
(confirm unlock on your phone again)
8. Once bootloader unlock confirmed, execute this command to check if unlock successful:
Code:
fastboot oem device-info
If both unlock state are indicated as True, you can restore the ABL back to retail (if you don't then phone will not boot to normal OS), wipe userdata and reboot:
Code:
fastboot flash abl_a abl_a.bin
fastboot flash abl_b abl_b.bin
fastboot -w reboot
9. If your phone had initial release of Android 12 that bricked the phone after factory reset, unbrick the phone by following this procedure.
10. Enjoy your bootloader unlocked Nokia 5.3 and have fun for hacking.
Watch this video in case you still don't understand:
Case 2: If you know someone who can provide remote phone flash service for you
I can help when the phone has Android 10 installed, but it's pretty rare nowadays, at least it's difficult to find outside China mainland.
However in this case you don't need to disassemble the phone, you'll just need to reinstall stock firmware after bootloader unlock.
1. Grant service permission. I know how the service permission granting works under initial release of Android 10, which I can't disclose here (also how I confirmed bootloader unlock method working).
If you know someone who can flash a recent Nokia phone for you, Then it will work under Android 11 or 12. When you request such service, ask him not to reboot your phone after the procedure completes.
2. Execute these commands to perform bootloader unlock:
Code:
fastboot flash abl CAP-abl.elf
fastboot reboot-bootloader
fastboot flashing unlock_critical
(confirm unlock on your phone)
fastboot oem unlock-go
(confirm unlock on your phone again)
3. Flash stock ABL image and wipe userdata. Stock image from Android 12 release is attached below - extract it before flashing, or it will brick your phone and you'll have to use EDL method to revive it.
It may break OTA functionality, so use with care.
Code:
fastboot flash abl CAP-340A-abl.elf
fastboot -w reboot
I waited a long time, but do not leave this status
thiago92nr said:
I waited a long time, but do not leave this status
Click to expand...
Click to collapse
1. In case that happens, check if your laptop only has USB 3.x port. If yes, try to execute the command before connecting the phone to PC.
2. Execute the command under /home/your_user_name instead of /opt/edl to prevent permission issue.
Worked perfectly. I was able to unbrick my Nokia 5.3 by flashing the stock rom with Fastboot after unlocking the bootloader.
Regarding to stock firmware installation after bootloader unlock.
I'm sure you can obtain a stock ROM somewhere, for example the one I obtained has filename "HMDSW_TA-1229-340A-0-00WW-B01_user_devicekit.zip". (However it can be used on non TA-1229 models like TA-1234)
HMDSW_TA-1229-340A-0-00WW-B01_user_devicekit.zip | by Hikari Calyx for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
DO NOT USE MINIMAL ADB AND FASTBOOT! DELETE IT BEFORE YOU PROCEED!
These are possible locations of Minimal ADB and Fastboot:
Code:
C:\adb
C:\Program Files (x86)\Minimal ADB and Fastboot
C:\Program Files\Minimal ADB and Fastboot
C:\Windows\system32
Delete these 4 files: adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe
Extract the firmware package twice and you'll see a batch file named "sm6125_fastboot_all_images.bat". Right click on it and remove the second line (adb reboot bootloader) - since you're already in fastboot mode.
Then, extract Platform Tools from following websites and place files along with firmware files: https://developer.android.com/studio/releases/platform-tools
Make sure fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll are placed altogether with firmware files, then double click "sm6125_fastboot_all_images.bat" to reinstall stock firmware.
As for macOS and Linux, you've probably noticed the existence of Captain_download_mac.sh and Captain_download_ubuntu.sh. Edit them and execute it under terminal.
Hello, do you mind to make a video how to do those steps? It's quite confusing especially for the 1st step and the 6th step.
xmichaxb7 said:
Hello, do you mind to make a video how to do those steps? It's quite confusing especially for the 1st step and the 6th step.
Click to expand...
Click to collapse
I'll have to wait few days to weeks for another Nokia 5.3 test unit's arrival.
hikari_calyx said:
I'll have to wait few days to weeks for another Nokia 5.3 test unit's arrival.
Click to expand...
Click to collapse
Oh, alright. I guess I must wait patiently. My Nokia 5.3 has a problem with the NFC on A12. It just keeps detecting my E-Money card like every 1 second or 0.5 second. So, I hopefully will be able to downgrade to A11 after I unlock the bootloader.
hikari_calyx said:
1. In case that happens, check if your laptop only has USB 3.x port. If yes, try to execute the command before connecting the phone to PC.
2. Execute the command under /home/your_user_name instead of /opt/edl to prevent permission issue.
Click to expand...
Click to collapse
I tried this after facing the same issue as @thiago92nr with no success still stuck on mode detected Sahara.
I used the live CD to try unlocking the bootloader and still no luck
pingusp said:
I tried this after facing the same issue as @thiago92nr with no success still stuck on mode detected Sahara.
I used the live CD to try unlocking the bootloader and still no luck
Click to expand...
Click to collapse
Type the command and press enter before connecting the device, then connect. it worked for me like this
I'll give it a go thanks
thiago92nr said:
Type the command and press enter before connecting the device, then connect. it worked for me like this
Click to expand...
Click to collapse
@thiago92nr I have another eorr.edl.py: No such file or directory
pingusp said:
@thiago92nr I have another eorr.edl.py: No such file or directory
Click to expand...
Click to collapse
remove the .py extension
Tried that and it's giving me this error @thiago92nr
Hey everyone I'm stuck on this part with no idea on what to do
pingusp said:
Hey everyone I'm stuck on this part with no idea on what to do
Click to expand...
Click to collapse
try this command
edl printgpt --loader=/home/user/Download/prog_emmc_firehose_Sm6125_ddr.elf
Then this one for Abl flash a and b
edl r abl_a abl_a.bin --memory=emmc --loader=/home/user/Download/prog_emmc_firehose_Sm6125_ddr.elf
Before I do this should I download all 3 files or the one with the prototype abl
thiago92nr said:
try this command
edl printgpt --loader=/home/user/Download/prog_emmc_firehose_Sm6125_ddr.elf
Then this one for Abl flash a and b
edl r abl_a abl_a.bin --memory=emmc --loader=/home/user/Download/prog_emmc_firehose_Sm6125_ddr.elf
Click to expand...
Click to collapse
Tried it same message
Apparently it could be due to pkhash does match the device pkhash or hardware doesn't match loader
some indan dude can unluck it without disassembling the Device! thats interesting he gives 20$ for that but i wanna know how its possible????
I think he might use hickari calyx bootloader unlock method or the hmd device toolkit