fastboot - Droid Eris Android Development

Someone please explain to me what/how ivanmmj needs us to check. I do not know how to open into fastboot, also is it just a normal CMD box? or is this phone side.

Interesting.. I see what hes getting at thinking along the nexus line ivan?

To get to fastboot you power down your phone and than power it back up holding down the volume down key and power, you will than be in the bootloader screen than select fastboot from there you can use fastboot commands..... but since we have a "perfect SPL" all the fastboot commands are locked down.
Alternitavally you can plug your phone in and do "adb shell reboot oem-78" and this will bring your phone to a screen that has HTC on it and you can use fastboot commands but they dont seem to do much.
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
Hope this helps

Code:
INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOenableqxdm
INFOrtask
INFOtask
OKAY
thats all i get when i type in the command fastboot oem h

enableqxdm ... whats that

all i did was see those i didnt mess with it

Just tried the nexus way oem unlock ERR!

do what????

Fastboot oem unlock is not a command that is why you get err

yeah, seems its new to nexus one. Oh well laxattack did you pm ivan with what showed up?

I dont know if anyone did this before but this is all htc throws up for open source about our phone:
http://developer.htc.com/
http://developer.android.com

yea never got a response though

Related

Can't unlock bootloader....what am I missing

I'm going nuts here. I use a mac, have had the 6p since preorder (well...since they shipped it) and I haven't had a need for unlocking or rooting (first phone ever to leave it stock) but I've got a few glitches and what not and wanted to flash the newest update released today rather than wait for OTA. Figured a complete wipe can't hurt. unfortunately the fastboot flashing unlock command isn't working. Developer options enabled, OEM unlock tab enabled...usb debugging enabled.....but when I enter ./fastboot flashing unlock this is what I get in terminal (yes mac requires the ./ before any command)
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] 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
-s <serial number> specify device serial number
-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
-n <page size> specify the nand page size. default: 2048
Perhaps you have an outdated version? Just a wild guess here but usually if an option is invalid, that's the case.
Sent from my Nexus 6P using Tapatalk
Yep - as @funnel71 said - outdated version.
I unlocked the bootloader on my shiny new 6p yesterday, and initially I got exactly the same result initially. I were doing it on my ubuntu desktop (14.04) at work which has adb installed from packages, which was working perfectly fine with other devices. I manually installed the latest android sdk - and in no time at all I had unlocked and rooted goodness
As others have said, your fastboot package is outdated. You need to install the Android SDK and make sure the platform-tools package is updated.
Thanks. I was thinking that. But it's been so long since I've done that... I got read up again lol
Sent from my Nexus 6P using XDA-Developers mobile app
Updated the SDK. Thanks everyone. It's unlocked now. I knew I was missing something.
Ok, now I'm really getting frustrated. Got the bootloader unlocked, but now I can't flash anything. I've never been able to get the flash-all.sh to work ........ever in the past with my N7, and it's not working here either. Get this message. ./flash-all.sh: line 17: tbfastboot: command not found
./flash-all.sh: line 19: fastboot: command not found
./flash-all.sh: line 20: fastboot: command not found
./flash-all.sh: line 22: fastboot: command not found
When I try to flash the bootloader, radio, or image separately I get this messagem8994f-2.6.31.1.09.img
target reported max download size of 494927872 bytes
sending 'radio' (56758 KB)...
OKAY [ 1.727s]
writing 'radio'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.74yt
318sugarhill said:
Ok, now I'm really getting frustrated. Got the bootloader unlocked, but now I can't flash anything. I've never been able to get the flash-all.sh to work ........ever in the past with my N7, and it's not working here either. Get this message. ./flash-all.sh: line 17: tbfastboot: command not found
./flash-all.sh: line 19: fastboot: command not found
./flash-all.sh: line 20: fastboot: command not found
./flash-all.sh: line 22: fastboot: command not found
When I try to flash the bootloader, radio, or image separately I get this messagem8994f-2.6.31.1.09.img
target reported max download size of 494927872 bytes
sending 'radio' (56758 KB)...
OKAY [ 1.727s]
writing 'radio'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.74yt
Click to expand...
Click to collapse
What is the exact command you're issuing?
318sugarhill said:
Ok, now I'm really getting frustrated. Got the bootloader unlocked, but now I can't flash anything. I've never been able to get the flash-all.sh to work ........ever in the past with my N7, and it's not working here either. Get this message. ./flash-all.sh: line 17: tbfastboot: command not found
./flash-all.sh: line 19: fastboot: command not found
./flash-all.sh: line 20: fastboot: command not found
./flash-all.sh: line 22: fastboot: command not found
When I try to flash the bootloader, radio, or image separately I get this messagem8994f-2.6.31.1.09.img
target reported max download size of 494927872 bytes
sending 'radio' (56758 KB)...
OKAY [ 1.727s]
writing 'radio'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.74yt
Click to expand...
Click to collapse
Have you edited the flash-all.sh script to include a ./ in front of all of the fastboot commands?
./flash-all.sh is what type in and it gives me the error above.
When I tried to flash just the bootloader first I used
./fastboot flash bootloader (bootloader name).img
It gives me this error
target reported max download size of 494927872 bytes
sending 'bootloader' (4387 KB)...
OKAY [ 0.160s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.182s
Same with the radio. I've never had an issue with terminal and flashing on any other phone prior.
Sent from my Nexus 6P using XDA-Developers mobile app
nathanchance said:
Have you edited the flash-all.sh script to include a ./ in front of all of the fastboot commands?
Click to expand...
Click to collapse
yes. nothing works on a mac in terminal for android without the ./ learned that lesson years ago.
318sugarhill said:
yes. nothing works on a mac in terminal for android without the ./ learned that lesson years ago.
Click to expand...
Click to collapse
Have you tried flashing the images manually like in Heisenberg's guide? I hate the flash-all script, it rarely works properly.
nathanchance said:
Have you tried flashing the images manually like in Heisenberg's guide? I hate the flash-all script, it rarely works properly.
Click to expand...
Click to collapse
agree, very hit or miss, personally I flash each file manually. just the best results this way. I also agree that a outdated version of fastboot/you're gonna have a bad time.
nathanchance said:
Have you tried flashing the images manually like in Heisenberg's guide? I hate the flash-all script, it rarely works properly.
Click to expand...
Click to collapse
Yes.....this is what I get
./fastboot flash bootloader (bootloader name).img
It gives me this error
target reported max download size of 494927872 bytes
sending 'bootloader' (4387 KB)...
OKAY [ 0.160s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.182s
Same with the radio. I've never had an issue with terminal and flashing on any other phone prior.
318sugarhill said:
Yes.....this is what I get
./fastboot flash bootloader (bootloader name).img
It gives me this error
target reported max download size of 494927872 bytes
sending 'bootloader' (4387 KB)...
OKAY [ 0.160s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.182s
Same with the radio. I've never had an issue with terminal and flashing on any other phone prior.
Click to expand...
Click to collapse
Did you ever use the following command?
Code:
fastboot erase bootloader
DJBhardwaj said:
Did you ever use the following command?
Code:
fastboot erase bootloader
Click to expand...
Click to collapse
No. I have to erase first? I've never had to with other phones. is that a Nexus thing? I'm hesitant to erase anything without know I can flash something.
318sugarhill said:
No. I have to erase first? I've never had to with other phones. is that a Nexus thing? I'm hesitant to erase anything without know I can flash something.
Click to expand...
Click to collapse
No! Not at all. Was just curious to ask, since your output showed that the partition table doesn't exist.
Never erase the bootloader.
DJBhardwaj said:
No! Not at all. Was just curious to ask, since your output showed that the partition table doesn't exist.
Never erase the bootloader.
Click to expand...
Click to collapse
When I try to flash anything that what I get. Radio, image, bootloader.....i get the remote partition table doesn't exist error. It's beyond frustrating.
318sugarhill said:
When I try to flash anything that what I get. Radio, image, bootloader.....i get the remote partition table doesn't exist error. It's beyond frustrating.
Click to expand...
Click to collapse
Just to confirm, while flashing the bootloader, you are using the exact same command as follows?
Code:
fastboot flash bootloader bootloader-angler-angler-03.51.img
DJBhardwaj said:
Just to confirm, while flashing the bootloader, you are using the exact same command as follows?
Code:
fastboot flash bootloader bootloader-angler-angler-03.51.img
Click to expand...
Click to collapse
yes.....just with a ./ in front. I've shorted the name of the booloader to bootloader.img just to keep the typing down.....but I've tried with the original name too. It's not angler.....it's ......
Holy F..........!!!!!!!!! I downloaded the factory image for the 5X.....it's friggin bullhead! AHHHHHHHHH
Facepalm.

Flashing problem with bootloader

Guys,
I have the nexus 7 grouper tab and I have been trying to flash bootloader-grouper-4.23 from azoller1's post and my tab does not seem to be flashed, steps I followed.
Vol- and power to enter fastboot mode,it is showing
C:\adb>fastboot devices
015d188422200619 fastboot
then with the command fastboot boot bootloader-grouper-4.23.img seem to be flashed but showing the message as
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: N/A
Serial Number........: 015d188422200619
--------------------------------------------
this clearly shows that my tab was not flashed with the bootloader properly. Even to continue with 4.18 bootloader only, it is giving error
erasing 'userdata'...
OKAY [ 7.413s]
sending 'userdata' (102525 KB)...
OKAY [ 12.599s]
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 136.188s
Evenif I manually erase userdata after rebooting into bootloader , (with the command fastboot erase userdata , it says success but got stuck on boot logo (image attached) .I waited for more than 30 minutes.
This is the fate of my tab. can anybody help me a best solution on this ?
to flash the bootloader you need to
fastboot flash bootloader-grouper-4.23.img
I had a small problem now bro.
Instead of thw command "fastboot erase boot",
I gave the command "fastboit erase bootloader"
Niw the tab is not turning on anymore.
Can you suggest me any solution ?
If you already rebooted ... no, I don't have a solution otherwise you could flash directly the bootloader again and you are recovered from this situation.
That command is incorrect.
Should be - fastboot flash bootloader bootloader-grouper-4.23.img
@renildrah I wanted to state only that he needs to flash and not to boot the bootloader image
Sent from my Nexus 7 using XDA Labs
Command is olay bro.. issue is my tab is not even switching on but recognized by PC when connected.
Any possibility to get back my tab??
renildrah said:
That command is incorrect.
Should be - fastboot flash bootloader bootloader-grouper-4.23.img
Click to expand...
Click to collapse

FAILED (remote: unknown command) enable camera2api with fastboot

i was read and do the guide to enable camera2api,
i use Linux Mint OS, adb and fastboot was installed.
i was enter to bootloader mode and run command
Code:
sudo fastboot devices
, the devices is detected.
but when i run command
Code:
sudo fastboot oem enable_camera_hal3 true
i got error
Code:
sudo fastboot oem enable_camera_hal3 true
...
FAILED (remote: unknown command)
finished. total time: 0.001s
what wrong with this?
how to fix this, how update driver adb on LinuxMint?

need help relocking bootloader

sorry to post the same old ask for help. im on PPOS29.114-16-7-2
I unlocked because I thought there would be more to do if I did. then noticed not much going on. id like to get security updates without all the trouble . ive noticed people having problems with relocking. I just would like the right way laid out for me and I will give it a shot. also when you say enter the commands in for fastboot do I copy from text editor and do it or do then one at a time. lot of commands
I appreciate all help
thanks
millede74 said:
sorry to post the same old ask for help. im on PPOS29.114-16-7-2
I unlocked because I thought there would be more to do if I did. then noticed not much going on. id like to get security updates without all the trouble . ive noticed people having problems with relocking. I just would like the right way laid out for me and I will give it a shot. also when you say enter the commands in for fastboot do I copy from text editor and do it or do then one at a time. lot of commands
I appreciate all help
thanks
Click to expand...
Click to collapse
You can script them if you know how to make one. Otherwise enter them one at a time. You only need to flash this once so if you do them once each it doesn't take a long time.
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash dtbo dtbo.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
then
Code:
fastboot oem lock
you may have to repeat this last lock command until it works. I had to do it 4-5 times.
I really appreciate the help. Thanks. Do I need to put boot image or 29.114-16-7-2 extract file in tools folder and do this?
millede74 said:
I really appreciate the help. Thanks. Do I need to put boot image or 29.114-16-7-2 extract file in tools folder and do this?
Click to expand...
Click to collapse
fastboot needs to be in the folder with the 29.114-16-7-2 files.
Thanks
Note that you need to run the fastboot oem lock command a few times in the beginning (before you flash) and after you flash a few more times for this to completely work!
Did like said and pretty much everything after fb_mode_set said command failed
Didn't do nothing to phone I can tell. I stopped after trying bootloader
What's wrong
millede74 said:
Did like said and pretty much everything after fb_mode_set said command failed
Didn't do nothing to phone I can tell. I stopped after trying bootloader
What's wrong
Click to expand...
Click to collapse
Do them one at a time and post the results of each command here so we can see.
Sorry won't be able to try again till tomorrow. One question. If I run lmsa what will it do if I use rescue after downloading system image?
millede74 said:
Sorry won't be able to try again till tomorrow. One question. If I run lmsa what will it do if I use rescue after downloading system image?
Click to expand...
Click to collapse
It does the same thing as the commands above. The process is just automated.
This is what i get when running
ptn107 said:
It does the same thing as the commands above. The process is just automated.
Click to expand...
Click to collapse
C:\ProgramData\LMSA\Download\RomFiles>fastboot dev
ZY225FR3QL fastboot
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem
mmand erases all user data.
(bootloader) Please re-run this command to continu
OKAY [ 0.014s]
Finished. Total time: 0.020s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem
oid images now
(bootloader) Then re-run this command to lock
OKAY [ 0.018s]
Finished. Total time: 0.024s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.009s]
Finished. Total time: 0.014s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.009s]
Finished. Total time: 0.015s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.008s]
Finished. Total time: 0.015s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.010s]
Finished. Total time: 0.016s
C:\ProgramData\LMSA\Download\RomFiles>fastboot getvar max-sparse-size
max-sparse-size: 268435456
Finished. Total time: 0.006s
C:\ProgramData\LMSA\Download\RomFiles>fastboot oem fb_mode_set
OKAY [ 0.005s]
Finished. Total time: 0.011s
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash partition gpt.bin
fastboot: error: cannot load 'gpt.bin': No such file or directory
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash bootloader bootloader.img
fastboot: error: cannot load 'bootloader.img': No such file or directory
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash modem NON-HLOS.bin
fastboot: error: Failed to identify current slot
C:\ProgramData\LMSA\Download\RomFiles>fastboot flash fsg fsg.mbn
fastboot: error: Failed to identify current slot
C:\ProgramData\LMSA\Download\RomFiles>
Correct me if I'm wrong but doesn't lmsa download the firmware as a zip file in C:\ProgramData\LMSA\Download\RomFiles ? If that's the case you need to make sure the files are extracted before running commands.

AOSP 9.0 - Deviations from official guide

When following the official guide if an error occurs when running 'fastboot flash' commands then try using a USB hub.
Also in the case of failures such as:
FAILED (remote: 'No such partition.')
Run the following commands:
fastboot getvar current-slot
current-slot: _a
Use the resulting current slot value as follows:
fastboot flash boot_a out/target/product/pioneer/boot.img
fastboot flash system_a out/target/product/pioneer/system.img
When flashing I had to flash the following:
boot.img
system.img
vendor.img
userdata.img

Categories

Resources