[Solved] Compile Lollipop-Kernel - Xperia Z1 Compact Q&A, Help & Troubleshooting

Hi,
I just tired to compile and repack the LL-Kernel for Z1c into a boot.img.
But I can't get it to start. I only see red LED blinken when I try to boot.
I used following sources:
http://developer.sonymobile.com/dow...rchives/open-source-archive-for-14-5-a-0-242/
And did it like it is mentioned in README_Xperia, which was all working fine and without errors.
Code:
### get defconfig
ARCH=arm CROSS_COMPILE=./arm-eabi-4.6/bin/arm-eabi- make rhine_amami_row_defconfig
### compile kernel
ARCH=arm CROSS_COMPILE=./arm-eabi-4.6/bin/arm-eabi- make
echo "checking for compiled kernel..."
if [ -f arch/arm/boot/zImage ]
then
echo "generating device tree..."
./dtbTool -o dt.img -s 2048 -p ./scripts/dtc/ ./arch/arm/boot/
echo "DONE"
fi
### D5503
./mkbootimg --cmdline "androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3b7 ehci-hcd.park=3 androidboot.bootdevice=msm_sdcc.1 vmalloc=300M dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y" --base 0x00000000 --kernel arch/arm/boot/zImage --ramdisk ramdisk.cpio.gz --ramdisk_offset 0x02000000 -o boot.img --dt dt.img --tags_offset 0x01E00000
The ramdisk.img I got from http://forum.xda-developers.com/son...5-0-242-generic-1279-6978-pre-rooted-t3083764
And I extracted the boot.elf with "Andrid Kitchen", which was working almost:
Code:
7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
p7zip Version 9.20 (locale=de_DE.UTF-8,Utf16=on,HugeFiles=on,4 CPUs)
Processing archive: kernel.elf
Extracting 0
Extracting 1
Extracting 2
Everything is Ok
Files: 3
Size: 11304622
Compressed: 11308906
mv: call of stat for »3“ not possible: File or Directory not found
mv: call of stat for »cmdline.txt“ not possible: File or Directory not found
After that there was a ramdisk.img in output folder which I used for mkbootimg.
After getting boot.img I tried to flash/load it via fastboot, which was not working. Can't figuere aout why.
Bootloader is unlocked.
Code:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.349s]
booting...
FAILED (status read failed (No such device))
finished. total time: 5.437s
Code:
fastboot flash boot boot.img
sending 'boot' (11044 KB)...
OKAY [ 0.349s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.352s
And because of that I tried to flash it via TWRP/CWM/... with following updater-script:
Code:
show_progress(0,0);
ui_print(" flashing boot.img...");
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
ui_print(" finished");
show_progress(10.000000, 1);
So maybe anyone can point me to mistake I make?
EDIT:
Problem solved and Kernel is working. I must have relocked my bootloader in the past and couldn't remember it^^
So now I was able to flash the boot.img via fastboot.

Related

How can I make my own boot.img ?

Hi !
I search to unpack and repack my HTC DESIRE Z Boot image :
Code:
[email protected]:/tmp/ROM# unpack-bootimg.pl boot.img
kernel written to boot.img-kernel.gz
ramdisk written to boot.img-ramdisk.cpio.gz
536 blocs
extracted ramdisk contents to directory boot.img-ramdisk/
[email protected]:/tmp/ROM# cd boot.img-ramdisk
[email protected]:/tmp/ROM/boot.img-ramdisk# vim default.prop
[email protected]:/tmp/ROM/boot.img-ramdisk# cd ..
[email protected]:/tmp/ROM# repack-bootimg.pl boot.img-kernel.gz boot.img-ramdisk/ test.img
536 blocs
repacked boot image written at boot.img-ramdisk/-repack.img
[email protected]:/tmp/ROM# fastboot boot test.img
downloading 'boot.img'... OKAY
booting... OKAY
[email protected]:/tmp/ROM#
it's still on HTC Logo.
If I boot the orginal boot.img, the phone boot normaly.
Why ?
Thanks.

Editing Huawei Ascend P1 (U9200) boot.img

I'm trying to make insecure boot.img for U9200 for my firmware version (V100R001C185B104). Unpacking original boot.img and ramdisk goes OK. After making changes to defult.prop I do the following:
mkbootfs ./ramdisk | gzip > ramdisk-new.gz
mkbootimg --kernel boot.img-kernel --ramdisk ramdisk-new.gz --base 0x80000000 --cmdline "console=ttyGS2,115200n8 mem=1G vmalloc=768M omap_wdt.timer_margin=30 mmcparts=mmcblk015(splash)" --board omap4 -o tools/flash/boot.img
New boot.img is successfuly created but doesn't boot (fastboot boot boot.img). What am I doing wrong?
I've got parameters using bootimg.exe and I think they are OK. There's nothing about them on the net
EDIT:
I made it using other mkbootimg.exe. This one accept more input parameters. This time I use bootimg.exe for upacking bootimg and unpacking and packing ramdisk. I did:
>bootimg.exe --unpack-bootimg
>bootimg.exe --unpack-ramdisk
Do changes at default.prop.
>bootimg.exe --repack-ramdisk
>mkdir flash\
>mkbootimg --kernel kernel --ramdisk ramdisk.cpio.gz --cmdline "console=ttyGS2,115200n8 mem=1G vmalloc=768M omap_wdt.timer_margin=30 mmcparts=mmcblk015(splash)" --board omap4 --base 0x80000000 --pagesize 2048 -o flash\boot.img
Reboot to bootloader:
>adb reboot bootloader
Test if you have good drivers installed:
>fastboot devices
If OK, test your new boot.img without flashing it:
>fastboot boot boot.img
If device boots and you want to have this image permanant flash it with:
>fastboot flash boot.img.
I've attached the tools that worked for me. I'm coplete noob in Android cooking, this is my first steps. There are lot about editing boot.img on the internet but nothing about my device so I decided to start a new topic if someone is also interested in.
also cracking my U9500. Have you done with your problems?
i use bootimg.exe to unpack & repack the img file, using same parameters and nothing modified to the extracted files,
but,
the new & old boot.img(should be same) are not same using binary compare.
according to a file that describes how boot.img is structured, i found that some key parameters are different in these two img file.
I don't know why ....
so if you have succeeded, PLZ tell me ..
contact me qq 6777711 if you're Chinese. or mail me: 6777711 AT qq.com
Nice one. I'll take a look at this aswell.

[Q] Roadblock on trying to s-off incredible 2. cmd line history provided.

So I'm trying to use the "Comprehensive S-OFF/Root Methods" guide posted in the developer section and am trying to s-off a previously dev. unlocked droid incredible 2. here's the command line and i'll highlight the part I believe is at issue.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:/Android
C:\Android>md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01
.0622_NV_VZW1.92_release_199487_si.zip
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\Android\]
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2... 100% cea499f51b40055ffd118960e1e73255
C:\Android>md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\Android\]
1.09.01.0312_vivow_Radio_PG32IMG.zip ea6b98be48210d7797e62362f49ff751
C:\Android>md5sums misc_version
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\Android\]
misc_version 050f55d34ddbcc860efa5982491437de
C:\Android>adb devices
List of devices attached
HT1AGMA01271 device
C:\Android>adb push CWM-SuperSU-v0.94.zip /sdcard
failed to copy 'CWM-SuperSU-v0.94.zip' to '/sdcard': Is a directory
C:\Android>adb push CWM-SuperSU-v0.94.zip /mnt/sdcard
1667 KB/s (674673 bytes in 0.395s)
C:\Android>adb reboot bootloader
C:\Android>
C:\Android>fastboot devices
HT1AGMA01271 fastboot
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5330 KB)... OKAY [ 1.749s]
writing 'recovery'... OKAY [ 1.218s]
finished. total time: 2.968s
C:\Android>adb push misc_version /data/local/tmp/misc_version
889 KB/s (367096 bytes in 0.403s)
C:\Android>adb shell chmod 777 /data/local/tmp/misc_version
C:\Android>adb shell /data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
Error opening input file.
C:\Android>adb reboot bootloader
C:\Android>fastboot devices
HT1AGMA01271 fastboot
C:\Android>fastboot getvar mainver
mainver: 6.01.605.05
finished. total time: 0.003s
C:\Android>
it says in the walkthrough instructions that "Result should be 2.18.605.3. If it isn't, make sure you didn't get any errors in the above code and everything was copied correctly." I'm pretty sure I copied everything correctly as I simply highlighted and pasted the codes, and was sure to take out the space in the radio code at the beginning as pointed out by developer. Where am I going wrong? Thanks for any input, I'm learning as I go.
Did you relock your device?
Sent from my SCH-I535 using xda app-developers app
GoonAssJuan said:
Did you relock your device?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
No, I'm using the instructions for those who have a dev. unlocked device but not s-off. http://forum.xda-developers.com/showthread.php?t=1751796
Also, half the time when I reboot out of recovery my computer wont recognize my incredible 2 until I reinstall the usb drivers and restart the computer. I am using the correct drivers provided.3.0.0.007. Running windows 7 64 bit.
try a different computer
Jasonp0 said:
try a different computer
Click to expand...
Click to collapse
Or at least a USB 2.0 port instead of 3.0.
gtdtm said:
Or at least a USB 2.0 port instead of 3.0.
Click to expand...
Click to collapse
Ok, pulled out my 10 year old laptop running xp pro and the usb issue was able to be avoided but I'm still having trouble at this point in the command line
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5330 KB)... OKAY [ 1.719s]
writing 'recovery'... OKAY [ 1.125s]
finished. total time: 2.844s
C:\Android>adb push misc_version /data/local/tmp/misc_version
1764 KB/s (0 bytes in 367096.000s)
C:\Android>adb shell chmod 777 /data/local/tmp/misc_version
C:\Android>adb shell /data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
Error opening input file.
C:\Android>
Why is it having trouble opening the input file to downgrade? This is the same thing it does on my desktop.
Double checked phone software, its running android 2.3.4, htc sense 2.1, build 6.01.605.05 (cl353602 release keys) so I should be doing the right method according to the guide.
nate7784 said:
Ok, pulled out my 10 year old laptop running xp pro and the usb issue was able to be avoided but I'm still having trouble at this point in the command line
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5330 KB)... OKAY [ 1.719s]
writing 'recovery'... OKAY [ 1.125s]
finished. total time: 2.844s
C:\Android>adb push misc_version /data/local/tmp/misc_version
1764 KB/s (0 bytes in 367096.000s)
C:\Android>adb shell chmod 777 /data/local/tmp/misc_version
C:\Android>adb shell /data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
Error opening input file.
C:\Android>
Why is it having trouble opening the input file to downgrade? This is the same thing it does on my desktop.
Double checked phone software, its running android 2.3.4, htc sense 2.1, build 6.01.605.05 (cl353602 release keys) so I should be doing the right method according to the guide.
Click to expand...
Click to collapse
It's been sooo long since I went s-off, and I don't think this is even the method I used (although this is probably a better one). I may be totally misunderstanding the snippet you pasted above, but why are you flashing recovery before following all the tacoroot instructions?
Nevermind...I just remembered you are already HTC-Dev unlocked. I'll look at it again.
gtdtm said:
It's been sooo long since I went s-off, and I don't think this is even the method I used (although this is probably a better one). I may be totally misunderstanding the snippet you pasted above, but why are you flashing recovery before following all the tacoroot instructions?
Nevermind...I just remembered you are already HTC-Dev unlocked. I'll look at it again.
Click to expand...
Click to collapse
thanks I appreciate it. Here's the entire command line if that helps, I had just included the end b/c the part i highlighted in blue is where things seem to go awry as best as I can tell.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\WINDOWS>cd C:/Android
The system cannot find the path specified.
C:\WINDOWS>cd C:\Android
C:\Android>md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01
.0622_NV_VZW1.92_release_199487_si.zip
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\Android\]
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2... 100% cea499f51b40055ffd118960e1e73255
C:\Android>md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\Android\]
1.09.01.0312_vivow_Radio_PG32IMG.zip ea6b98be48210d7797e62362f49ff751
C:\Android>md5sums misc_version
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\Android\]
misc_version 050f55d34ddbcc860efa5982491437de
C:\Android>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT1AGMA01271 device
C:\Android>adb push CWM-SuperSU-v0.94.zip /sdcard
failed to copy 'CWM-SuperSU-v0.94.zip' to '/sdcard': Is a directory
C:\Android>adb push CWM-SuperSU-v0.94.zip /mnt/sdcard
739 KB/s (0 bytes in 674673.000s)
C:\Android>adb reboot bootloader
C:\Android>fastboot devices
HT1AGMA01271 fastboot
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5330 KB)... OKAY [ 1.719s]
writing 'recovery'... OKAY [ 1.125s]
finished. total time: 2.844s
C:\Android>adb push misc_version /data/local/tmp/misc_version
1764 KB/s (0 bytes in 367096.000s)
C:\Android>adb shell chmod 777 /data/local/tmp/misc_version
C:\Android>adb shell /data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
Error opening input file.
C:\Android>
nate7784 said:
thanks I appreciate it. Here's the entire command line if that helps, I had just included the end b/c the part i highlighted in blue is where things seem to go awry as best as I can tell.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\WINDOWS>cd C:/Android
The system cannot find the path specified.
C:\WINDOWS>cd C:\Android
C:\Android>md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01
.0622_NV_VZW1.92_release_199487_si.zip
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\Android\]
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2... 100% cea499f51b40055ffd118960e1e73255
C:\Android>md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\Android\]
1.09.01.0312_vivow_Radio_PG32IMG.zip ea6b98be48210d7797e62362f49ff751
C:\Android>md5sums misc_version
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\Android\]
misc_version 050f55d34ddbcc860efa5982491437de
C:\Android>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT1AGMA01271 device
C:\Android>adb push CWM-SuperSU-v0.94.zip /sdcard
failed to copy 'CWM-SuperSU-v0.94.zip' to '/sdcard': Is a directory
C:\Android>adb push CWM-SuperSU-v0.94.zip /mnt/sdcard
739 KB/s (0 bytes in 674673.000s)
C:\Android>adb reboot bootloader
C:\Android>fastboot devices
HT1AGMA01271 fastboot
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5330 KB)... OKAY [ 1.719s]
writing 'recovery'... OKAY [ 1.125s]
finished. total time: 2.844s
C:\Android>adb push misc_version /data/local/tmp/misc_version
1764 KB/s (0 bytes in 367096.000s)
C:\Android>adb shell chmod 777 /data/local/tmp/misc_version
C:\Android>adb shell /data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
Error opening input file.
C:\Android>
Click to expand...
Click to collapse
I'm really no pro at this, but did you make sure and go into recovery and flash the SuperSU file? Other than that, when you hit the magical 10 posts you may want to ask in the s-off thread. The dev is usually willing to help out.
gtdtm said:
I'm really no pro at this, but did you make sure and go into recovery and flash the SuperSU file? Other than that, when you hit the magical 10 posts you may want to ask in the s-off thread. The dev is usually willing to help out.
Click to expand...
Click to collapse
yeah, I'm pretty sure I am. here is what I do, just like the instructions say. "fastboot flash recovery recovery.img This might take a while, be patient and do not interrupt it. Once it is done, use the volume buttons on your phone to navigate through the menu until RECOVERY is highlighted, then press Power to select it. Your phone will reboot into another menu, once it shows up, select "install from sdcard" then "choose zip from sdcard," then scroll down and select CWM-SuperSU-v0.94.zip, and accept it. Once it is finished, press power then select reboot. Once you are fully booted, continue with the instructions"
that is what you are talking about right?
nate7784 said:
yeah, I'm pretty sure I am. here is what I do, just like the instructions say. "fastboot flash recovery recovery.img This might take a while, be patient and do not interrupt it. Once it is done, use the volume buttons on your phone to navigate through the menu until RECOVERY is highlighted, then press Power to select it. Your phone will reboot into another menu, once it shows up, select "install from sdcard" then "choose zip from sdcard," then scroll down and select CWM-SuperSU-v0.94.zip, and accept it. Once it is finished, press power then select reboot. Once you are fully booted, continue with the instructions"
that is what you are talking about right?
Click to expand...
Click to collapse
Yeah, I'm not sure what else to tell you. You'll have to defer to people smarter than me.
gtdtm said:
Yeah, I'm not sure what else to tell you. You'll have to defer to people smarter than me.
Click to expand...
Click to collapse
Alright well thanks for taking at look at least. I posted something in the dev. thread but have yet to hear back from anyone. Really annoying being stuck with sense 2.1, can't even get OTA updates b/c i'm using page plus not verizon per-say.

nexus 5x bootloader not unlocked

C:\adb>fastboot flashing unlock
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\adb>
That means your version of fastboot doesn't understand the command. You'll need to update it.

enter fastbootd

when i type fastboot reboot fastboot my phone does nothing and that's what i get:
PS F:\ONEPLUS 7T\platform-tools_r30.0.4-windows\platform-tools> fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
It seems like i do not enter fastbootd. any solution?
altojd said:
when i type fastboot reboot fastboot my phone does nothing and that's what i get:
PS F:\ONEPLUS 7T\platform-tools_r30.0.4-windows\platform-tools> fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
It seems like i do not enter fastbootd. any solution?
Click to expand...
Click to collapse
Download latest fastboot version
Kollachi said:
Download latest fastboot version
Click to expand...
Click to collapse
Thanks but where do i find the latest fastboot version? if u mean fastboot.exe in platform tools i am on the latest one (r30.0.4)
altojd said:
Thanks but where do i find the latest fastboot version? if u mean fastboot.exe in platform tools i am on the latest one (r30.0.4)
Click to expand...
Click to collapse
Download the All in one tool from the forums here, it contains all of the drivers and files you need.
When you open up a command window, drag the fastboot.exe into command and then leave a space
Type fastboot reboot fastboot
Same thing happened with me it's weird but I use this is as a workaround
i solved my problem by flashing msm extended recovery. it has the function in advance to reach fastbootd.

Categories

Resources