This requires an ENG HBOOT, get it here
1. Run the command line and type the command: cd (your platform tools folder) (Press Enter after each command)
2. Enter the command adb devices . It should come back with a list of connected devices and your serial number.
3. Enter the command adb reboot bootloader . (Your device will reboot and boot into a FastBoot USB)
(If your phone will not boot in normal mode. Manually reboot to boot and select fastboot).
4. Enter the command fastboot getvar mid .The window will show your current mid.
5. Enter the command fastboot oem writemid PG58*****
6. Enter the command fastboot reboot-bootloader
7. Enter the command fastboot reboot
Related
Its simple just u should have the desired files but in case you used Hassoon2000 kit for rooting the desired files will already be present in C:/ directory of your pc.
Just boot your phone in bootloader mode and open command prompt on your pc by typing 'cmd' in 'RUN' command now just type the following strings...
cd C:/Android (press enter)
fastboot erase cache (press enter)
fastboot flash boot boot.img (press enter) and reboot...
Here boot.img is the kernel file so keep in mind the name of kernel file you are using..
faheem_khan said:
Its simple just u should have the desired files but in case you used Hassoon2000 kit for rooting the desired files will already be present in C:/ directory of your pc.
Just boot your phone in bootloader mode and open command prompt on your pc by typing 'cmd' in 'RUN' command now just type the following strings...
cd C:/Android (press enter)
fastboot erase cache (press enter)
fastboot flash boot boot.img (press enter) and reboot...
Here boot.img is the kernel file so keep in mind the name of kernel file you are using..
Click to expand...
Click to collapse
saying cd C:/Android is not recognized in internal and external
Open cmd and ad "fastboot flash boot boot.img" without " ". location of boot.img is not necessarily c:\. Initially what you open cmd could be location of boot.img and recovery.img. This is an example of procedure c:\ Users\Name of your computer>fastboot flash boot boot.img
First Step : Installing ADB Drivers
For windows : download PdaNet from here http://pdanet.co/a/
Second Step : Downloading ADB
For Mac : View attachment 2566782
For Windows : View attachment 2566785
Third Step : Installing ADB :-
For windows : Just extract it in directly in "C" partition
For Mac : Just extract it in any partition you want
Fourth Step :-
Openingthe ADB on Windows : Open start > Type "cmd" > Open the appeared program > Type in it "cd.." > Type "cd.." again
Opening the ADB on Mac :-
1) Open Start
2) Type "Terminal"
3) Open the appeared program
4) Type in it "nano ~/.bash_profile"
5) Type in it "export PATH=${PATH}:@@@@" (Replace the "@@@@" with the folder where you extract the ADB)
6) Save the files
7) press CTRL+X (To exit)
8) press Y (to confirm the save then press enter)
Final Step :-
Using the ADB on Windows/Mac :-
1) Type : "adb shell reboot recovery" (To reboot your phone into recovery)
2) Type "adb shell" (after rebooting Your phone into ClockworkMod Recovery)
3) Type "parted /dev/block/mmcblk0" (To open parted and mounts your SD-Card)
4) Type "print" (displays SD-Card partitions info)
5) Type "rm" (To delete a partition) then write the number of it
6) Type "mkpartfs primary fat32 0 27992" (This is for the Primary SD-Card-Ext) 28GB
7) Type "mkpartfs primary ext2 27992 28492" (This is for the System) 3GB
8) Type "mkpartfs primary ext2 28492 31492" (This is for the SD-Card-Int) 500MG
9) Type "mkpartfs primary ext2 31492 31692" (This is for the SD-Cache)199 MG
10) Type "mkpartfs primary linux-swap 00000 00000" (This is for the Lynux-swap) (If you do not know what it do, Do not try to make it)
You can change the Blue number according to your SD-Card size the provided numbers in this thread is for 32GB SD-Card
Note : You can Creat 4 SD-Partitions including the Primary SD-Card
Useful ADB commands :-
Note: to run all these commands, make sure USB debugging is enabled on your device
adb devices = list all connected devices
adb push = copy file/dir to device
adb pull [] = copy file/dir from device
adb sync [] = copy host->device only if changed
adb reboot = reboot your phone normally
adb reboot recovery = to reboot into recovery
adb reboot fastboot = to reboot fastboot
adb reboot bootloader = to reboot into bootloader
adb install [-l] [-r] [-s] = push this package file to the device and install it
adb uninstall [-k] = remove this app package from the device (‘-k’ means keep the data and cache directories)
adb help = show this help message
adb version = show version num
adb root = restarts the adbd daemon with root permissions
adb shell = run remote shell interactively
adb shell = run remote shell command
Useful Fastboot commands :-
Note: to run all these commands, your android devices must be in fastboot mode.
fastboot devices = to detect devices in fastboot mode
fastboot flash recovery twrp.img = to flash a recovery called twrp.img (put it in your fastboot folder)
fastboot oem unlock = to unlock bootloader of Nexus devices.
I got the latest ADB and Fastboot fresh from Google, used to have them in C:\Windows and they worked fine without even setting an environment variable, but today for unknown reason fastboot stopped working all together.
So I tried to download again, put the tools in C:\platform-tools, this time I set the environment variable properly in Windows but still no luck.
ADB returns a list of example commands, as expected.
fastboot returns
fastboot: usage: no command
Any ideas?
Windows 10
PS
shift click to open command prompt window here in the platform-tools folder gives the same result, fastboot: usage: no command
Hello,
I'm trying to flash a custom a ROM for the first time but I'm facing some issues.
I'm using an Ubuntu 20.04 and my phone is an Asus Max Pro M1.
I can see my device with "adb devices" and I can boot in the bootloader with "adb reboot bootloader".
Then I can see my device with "fastboot devices". But when I'm trying another fastboot command (for example "flash recovery"/"flashing unlock"/"oem unlock") my terminal prompt is just hanging, I don't get any output. And it won't do anything until I restart my phone by pushing the power button, at that time it will just print three lines of logs telling me that the command failed.
Here is an example of what I get :
Bash:
[email protected]:~/Documents/Code/tel$ adb devices
List of devices attached
K3AXB762C86977F device
[email protected]:~/Documents/Code/tel$ adb reboot bootloader
[email protected]:~/Documents/Code/tel$ sudo fastboot oem unlock
...
FAILED (command write failed (Success))
finished. total time: 0.000s
Does anyone have an idea of what is happening ?
IMHO the typical command sequence is
Code:
adb devices
adb reboot fastboot
fastboot devices
fastboot <subcommand>
but I may err, as always ...
When name is the lpm file for asus zenfone, i want to change the script to automatically poweron device when charger connected
IMO it's far easier to achieve this by means of ADB and Fastboot IF Fastboot supports command oem off-mode-charge what you can verify with fastboot oem device-info command
Code:
adb reboot fastboot
fastboot reboot fastboot
fastboot flashing unlock <= ONLY IF BOOTLOADER NOT AREADY GOT UNLOCKED
fastboot oem off-mode-charge 0
fastboot reboot