Hi guys.
I have been trying to root my HTC One S for hours now without any luck.
I have been using this guide,(http://forum.xda-developers.com/showthread.php?t=1583427) and have managed to get all the way to the last step in the "recovery"-section.
But when I try to flash the recovery, this is what I get:
c:\fastboot>fastboot recovery clockwork-touch.img
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
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
How can this be?
Thanks in advance for your help
Type the following command
c:\fastboot>fastboot recovery recovery clockwork-touch.img
Thanks for your reply, frazzeld.
It didn't work. Sorry. Still the same text coming up.
Maybe there is something wrong with have a managed my fastboot-folder.
Because I am a new member I cant post a picture of my folder :/
But it is set up like this:
(folder)add-ons
(Folder)platforms
Folder)tools
adb
adbWinapi.dll
AVD Manager
clockwork-touch.img
fastboot.exe
SDK Manager
SDK Readme
Unlock-code
Never mind.
It worked after all. Don't know what I did wrong the first 50 times.
Thank you
which clockwork are you trying to install?
Edit: I see you've sorted it now
Are you in fastboot mode? Also the recovery image has to be in the same folder as fastboot.exe is.
To point to the correct folder its "cd"
e.g.
cd c:\fastboot
And the correct command is;
fastboot flash recovery name_of_the_recovery.img
Thats all i can see from what you've posted
edit: too slowwww, glad you got it sorted
Big_Den said:
...
fastboot flash recovery name_of_the_recovery.img
...
Click to expand...
Click to collapse
This.
Just in case someone else stumbles across this thread.
Unconn said:
This.
Just in case someone else stumbles across this thread.
Click to expand...
Click to collapse
From the proper directory. It's not C:\ for everyone... Some have their fastboot.exe in C:\Android and some even C:\Android\platform-tools for example.
Point being, make sure u know where your fastboot.exe is located
Sent from my HTC VLE_U using xda premium
I am trying to put a ROM on the TF300. I have Unlocked the tablet and installed the ADB driver. When I boot into recovery and the USB icon it asks for a driver for fastboot. I can't seem to get that anywhere. I have the Android SDK installed and java etc. Where is the driver located? I look in the USB driver folder but its not in their...
If you need just fastboot, use this guide, that you will find in the index for tf300 (General & Dev forums)
HELP FOR FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "fastboot.zip"
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
The line command is :
Code:
c:\fastboot>
Enter
Code:
c:\fastboot>fastboot flash recovery recovery.img
Enter
If you want to flash the "recovery.img" file
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
usage: fastboot [ ]
commands:
update reflash device from update.zip
flashall flash boot + recovery + system
flash [ ] write a file to a flash partition
erase erase a flash partition
getvar display a bootloader variable
boot [ ] download and boot kernel
flash:raw boot [ ] 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 specify device serial number
-p specify product name
-c override kernel commandline
-i specify a custom USB vendor id
-b specify a custom kernel base address
-n specify the nand page size. default: 2048
And if you have some problems with your drivers, you can use this : How to install Universal Naked Drivers
Sent from my N7 3G with DroiDevs premium between sky and earth.
I got it to work thanks!
Hello, if i start the phone pushing power an vol down going to fastboot theres a recovery menu, how does it work? Can i make a full backup via this stock recovery menu? Does anybody know the others fastboot menu feature?
To learn more fastboot features in cmd or terminal type fastboot. The stock recovery image is bugged,and you can't do nand backups with it. Some command you may want to become familiar with are fastboot flash (insert what you are flashing)
Sent from Sauwny the TL
can anybody explain all the feature fastboot are.. im new to bootloader..
PerKakah said:
can anybody explain all the feature fastboot are.. im new to bootloader..
Click to expand...
Click to collapse
Here is a list of fastboot functions
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 (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
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
thanks but wasnt this what i meant
i mean the fastboot menu that shows up pressing power and vol down when power up the phone
the menu is
aè fastboot flash mode s
normal powerup
recovery
factory
switch console
barcodes
bp tools
what is this menus?
raniero1 said:
thanks but wasnt this what i meant
i mean the fastboot menu that shows up pressing power and vol down when power up the phone
the menu is
aè fastboot flash mode s
normal powerup
recovery
factory
switch console
barcodes
bp tools
what is this menus?
Click to expand...
Click to collapse
Here is the info.
Normal power up : It simply reboots your device.
Recovery : takes you to recovery menu of your device. From here you can flash any ROM, backup or restore your device, factory reset or do any other kind of tweak.
Factory : Deletes all the user data. (I.e. all your apps)
Switch console : I don't know what it does.
Barcodes and BP tools just provide you with some info of your device.
This is a general users guide to unbrick your Transformer tablet.
This guide will help you if your Asus tablet will only boot into recovery
and the command
Code:
adb reboot-bootloader
does not work to get you booted back to bootloader screen ..
If the above command works then skip to the first fastboot command ..
WHAT YOU NEED
An Asus tablet that will only boot into recovery …
Woking adb and fastboot on your PC
Windows drivers (if using Windows)
A fully charged tablet
Asus data cable
Stock firmware blob (from Asus's web site, make sure you get the right one)
_that's bootit.ko (unzipped and placed with fastboot.exe)
Downloads
Asus Stock firmware---MAKE SURE YOU GET THE CORRECT SKU FOR YOUR TRANSFORMER TABLET
click me
_that's bootit.ko----click me
INSTRUCTIONS
Extract your stock firmware in your downloads folder twice...You will see a blob file rename it boot.blob and move it to the same folder as your fastboot.exe or if in linux to your home folder
Unzip the bootit.ko and place it wth the above blob file.
Let start with this command to make sure that your PC can see your table as an ADB device in recovery
Code:
adb devices
OUTPUT
Code:
[email protected] ~ $ adb devices
List of devices attached
015c7d7a445c260c recovery
Then lets push the bootit.ko to the root of the device like this
Code:
adb push bootit.ko /
OUTPUT
Code:
[email protected] ~ $ adb push bootit.ko /
673 KB/s (27690 bytes in 0.040s)
Then lets insmod this .ko file
Code:
adb shell insmod /bootit.ko
This should reboot the tablet into the bootloader menu, lets verifiy.
Once in the bootloader screen lets make sure your PC can see the device in fastboot.
Code:
fastboot devices
OUTPUT
Code:
[email protected] ~ $ fastboot devices
015c7d7a445c260c fastboot
So now its time to erase the misc & cache partitions, as that is most likely the partitions that is making it boot to recovery...
Code:
fastboot erase misc
OUTPUT
Code:
[email protected] ~ $ fastboot erase misc
erasing 'misc'...
OKAY [ 1.021s]
finished. total time: 1.021s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected] ~ $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.096s]
finished. total time: 2.096s
Once these two command run with OKAY as the OUTPUT .
It is time to make sure we can reboot into the bootloader with the hardware buttons
So from where you are at in the bootloader screen use the VOL DOWN & POWER buttons to boot the tab back into the bootloader screen ..
Run these command in fastboot in this order
The next command is to just verify your computer can see your device
Code:
fastboot devices
OUTPUT
Code:
[email protected]:~ > fastboot devices
015d2bbce2501405 fastboot
Code:
fastboot erase system
OUTPUT
Code:
[email protected]:~ > fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.954s]
finished. total time: 2.954s
Code:
fastboot erase recovery
OUTPUT
Code:
[email protected]:~ > fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.945s]
finished. total time: 1.945s
Code:
fastboot -w
OUTPUT
Code:
[email protected]:~ > fastboot -w
erasing 'userdata'...
OKAY [ 23.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
sending 'userdata' (139133 KB)...
writing 'userdata'...
OKAY [ 26.358s]
erasing 'cache'...
At this point it will either hangs on erasing 'cache'
Or it will give you an error, either way you will need to
reboot the tablet back into fastboot with the hardware buttons
Once that is done continue on the path
Code:
fastboot erase boot
OUTPUT
Code:
[email protected]:~ > fastboot erase boot
erasing 'boot'...
OKAY [ 1.209s]
finished. total time: 1.209s
Code:
fastboot erase misc
OUTPUT
Code:
[email protected]:~ > fastboot erase misc
erasing 'misc'...
OKAY [ 0.978s]
finished. total time: 0.978s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected]:~ > fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.843s]
finished. total time: 2.843s
Code:
fastboot -i 0x0B05 flash system boot.blob
During the sending/writing process of this step you will get the blue bar on your screen.....
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 flash system boot.blob
erasing 'system'...
OKAY [ 2.339s]
sending 'system' (800927 KB)...
OKAY [133.094s]
writing 'system'...
[OKAY [178.036s]
finished. total time: 313.469s
Code:
fastboot -i 0x0B05 reboot
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
Let it boot into stock ROM ...
Credits
@_that for his bootit.ko
TEAM CROMBi and TEAM ZOMBi-X @sbdags @hardslog
Troubleshooting
Here is some troubleshooting
Check out this thread for fasboot.exe, adb.exe and driver help ...CLICK ME
@lj50036
A typo on your very first command: adb device?
Edit: What would you recommend if the userdata is corrupted and have only fastboot/adb? fastboot format data-partition? Thanks...
LetMeKnow said:
@lj50036
A typo on your very first command: adb device?
Edit: What would you recommend if the userdata is corrupted and have only fastboot/adb? fastboot format data-partition? Thanks...
Click to expand...
Click to collapse
Fixed let me know if you see anymore ..
Thx @LetMeKnow
LetMeKnow said:
@lj50036
A typo on your very first command: adb device?
Edit: What would you recommend if the userdata is corrupted and have only fastboot/adb? fastboot format data-partition? Thanks...
Click to expand...
Click to collapse
I am going to get to this once you have fastboot back and you can boot with hardware buttons then its just like @Buster99's
guide but there is one very important command that he leaves out ..
I will post the rest of the guide after bit ...
Thx Josh
Here is the original thread where the bootit module was tested for the first time -> http://forum.xda-developers.com/showthread.php?t=2291974
The problem was that the installed recovery was too old and incompatible with the bootloader and so could not access the eMMC at all. The bootloader command to boot to recovery is stored in the MSC partition (mmcblk0p3), and the recovery could not clear it. Since the bootloader checks the MSC partition before checking for volume-down, it is impossible to get to fastboot without some additional kick in the butt (aka "bootit.ko").
The correct bootit.ko file to use is the one in "bootit-bootloader.zip": http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132 - the older version turned out to be too weak. Note that this is a zipped kernel module, not a recovery-installable ZIP. You need to unzip it on your PC before adb push.
After making it to the bootloader menu and working fastboot, you can fastboot flash a current version of TWRP and install the custom ROM of your choice. No real need for the stock blob, unless you want to make sure you have the current bootloader and a known working ROM.
Here is another thread where bootit.ko didn't help, maybe it was really a hardware problem. But lots of good background info from me. -> http://forum.xda-developers.com/showthread.php?t=2437376
And here is another success story -> http://forum.xda-developers.com/showthread.php?p=47525770
_that said:
Here is the original thread where the bootit module was tested for the first time -> http://forum.xda-developers.com/showthread.php?t=2291974
The problem was that the installed recovery was too old and incompatible with the bootloader and so could not access the eMMC at all. The bootloader command to boot to recovery is stored in the MSC partition (mmcblk0p3), and the recovery could not clear it. Since the bootloader checks the MSC partition before checking for volume-down, it is impossible to get to fastboot without some additional kick in the butt (aka "bootit.ko").
The correct bootit.ko file to use is the one in "bootit-bootloader.zip": http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132 - the older version turned out to be too weak. Note that this is a zipped kernel module, not a recovery-installable ZIP. You need to unzip it on your PC before adb push.
After making it to the bootloader menu and working fastboot, you can fastboot flash a current version of TWRP and install the custom ROM of your choice. No real need for the stock blob, unless you want to make sure you have the current bootloader and a known working ROM.
Here is another thread where bootit.ko didn't help, maybe it was really a hardware problem. But lots of good background info from me. -> http://forum.xda-developers.com/showthread.php?t=2437376
And here is another success story -> http://forum.xda-developers.com/showthread.php?p=47525770
Click to expand...
Click to collapse
Thx _that I did update the OP with the correct bootit.ko ...
lj50036 said:
Thx _that I did update the OP with the correct bootit.ko ...
Click to expand...
Click to collapse
Great stuff! Thanks for this thread Josh!
Now , if I understand this correctly, the insmod command injects a command into the kernel to boot straight to the bootloader before checking misc to break that 'forced reboot to recovery' cycle.
Kinda correct?
In another thread @_that stated once that
Code:
fastboot getvar all
does not return misc as a supported partiton and that
Code:
fastboot erase misc
only "theoretically" erases misc partition. Is that confirmed now?
You guys are great! So much fun to learn this...
I tried to follow this but i get this output:
After pushing bootit.ko to the root and insmod, the transformer reboots directly in the bootloader.
When try fastboot devices, nothing happens just the next line to fill in a command.
Also, when trying then to fastboot erase misc, it hangs with 'waiting for devices'..
lvrijn said:
I tried to follow this but i get this output:
After pushing bootit.ko to the root and insmod, the transformer reboots directly in the bootloader.
When try fastboot devices, nothing happens just the next line to fill in a command.
Also, when trying then to fastboot erase misc, it hangs with 'waiting for devices'..
Click to expand...
Click to collapse
Did you have a working fastboot driver on your PC before you got into this pickle?
Give us a detailed description on why you tried this procedure.
berndblb said:
Did you have a working fastboot driver on your PC before you got into this pickle?
Give us a detailed description on why you tried this procedure.
Click to expand...
Click to collapse
Thanks for the advice.
It was not the driver, if was my fastboot and adb .exe, i think an old version?
I now downloaded from here http://forum.xda-developers.com/showthread.php?t=2588979
And these are working!
So if someone ever have problems command doesn't recognize fastboot commands, its not always the driver! It can also be the fastboot.exe
This transformer is working again !
lvrijn said:
Thanks for the advice.
It was not the driver, if was my fastboot and adb .exe, i think an old version?
I now downloaded from here http://forum.xda-developers.com/showthread.php?t=2588979
And these are working!
So if someone ever have problems command doesn't recognize fastboot commands, its not always the driver! It can also be the fastboot.exe
This transformer is working again !
Click to expand...
Click to collapse
Great to see you up and running...:good:
I did add a Troubleshooting post number 3
The Josh
berndblb said:
Great stuff! Thanks for this thread Josh!
Now , if I understand this correctly, the insmod command injects a command into the kernel to boot straight to the bootloader before checking misc to break that 'forced reboot to recovery' cycle.
Kinda correct?
In another thread @_that stated once that
Code:
fastboot getvar all
does not return misc as a supported partiton and that
Code:
fastboot erase misc
only "theoretically" erases misc partition. Is that confirmed now?
You guys are great! So much fun to learn this...
Click to expand...
Click to collapse
No, I dont think it injects anything into the kernel as there may not even be one in the LNX partition ..
The bootit.ko module comes from the source of the kernel code..
Also the /misc partition is a full partition as shown here ..
Code:
mmcblk0p3
Offset: 1292369920 (0x4d080000)
Size: 2097152 (0x200000)
File system size: 512 * 4096 = 2097152 (fully occupies partition)
Linux rev 1.0 ext3 filesystem
Not mounted
Permissions: GID system can manipulate
Contains: Empty file system
Purpose: Recovery /misc
Referenced by: /system/lib/libandroid_runtime.so recovery ramdisk: /etc/recovery.fstab
Note: File system is referenced in recovery as emmc, not ext3!
Thx Josh
lj50036 said:
No, I dont think it injects anything into the kernel as there may not even be one in the LNX partition ..
Click to expand...
Click to collapse
I think berndblb meant that insmod injects something into the *currently running* kernel, which it does. It's used for loading additional kernel modules, usually drivers. When a module is loaded, its "init" function is called by the kernel so that it can hook its functionality into the proper kernel subsystems. My bootit.ko's init function simply reboots the tablet - without properly terminating processes, unmounting filesystems, etc. - so it should only be loaded when no partitions are mounted.
_that said:
I think berndblb meant that insmod injects something into the *currently running* kernel, which it does. It's used for loading additional kernel modules, usually drivers. When a module is loaded, its "init" function is called by the kernel so that it can hook its functionality into the proper kernel subsystems. My bootit.ko's init function simply reboots the tablet - without properly terminating processes, unmounting filesystems, etc. - so it should only be loaded when no partitions are mounted.
Click to expand...
Click to collapse
Nothing like _that to put you in your place....
lj50036 said:
Nothing like _that to put you in your place....
Click to expand...
Click to collapse
I'm trying to get back to a working recovery. Now I get a cycle of TWRP splash screens. This method looks promising because it appears to rebuild all of the partitions. I can use the Vol Down + Power keys to get to the bootloader (us_epad-10.6.1.14.10-20130801 A03. Can I skip to the fastboot steps? I had Crombi-kk running with rom2sd before I broke something trying to upgrade to zombie-x.
Thanks!
awilson77584 said:
I'm trying to get back to a working recovery. Now I get a cycle of TWRP splash screens. This method looks promising because it appears to rebuild all of the partitions. I can use the Vol Down + Power keys to get to the bootloader (us_epad-10.6.1.14.10-20130801 A03. Can I skip to the fastboot steps? I had Crombi-kk running with rom2sd before I broke something trying to upgrade to zombie-x.
Thanks!
Click to expand...
Click to collapse
You can skip all the way down to the command "fastboot erase misc". It should kick you out of twrp cycling...good luck..:fingers-crossed:
LetMeKnow said:
You can skip all the way down to the command "fastboot erase misc". It should kick you out of twrp cycling...good luck..:fingers-crossed:
Click to expand...
Click to collapse
Thx!
Back up and running! Thanks!!!
tl;dr: I followed the procedure to flash Android's Generic System Image (gsi_gms_arm64-exp-TP1A.220624.014-8819323-8a77fef1) on my Blackview BV 4900 Pro, but I am stuck in a bootloop that ends with "Cannot load Android system. Your data may be corrupt."
In details:
PrepI made sure that my phone could support GSI
$adb shell getprop ro.treble.enabled
true
$adb shell cat /system/etc/ld.config.29.txt | grep -A 20 "\[vendor\]"
…
namespace.default.isolated = true
…
$adb shell getprop ro.product.cpu.abi
arm64-v8a
Additional Checks
Bootloader is unlocked.
Device was launched with Android 9 or higher (it was launched with Android 10)
Android 13 GSIs was downloaded (build Build: TP1A.220624.014) was downloaded from https://developer.android.com/topic/generic-system-image/releases and checksum for ARM64+GMS was confirmed to be 8a77fef1842da4a4cff68e36802f779d65e52ae0cfce024a33901d5dc48d47d0.
The phone has Android Verified Boot (AVB):
$adb shell getprop ro.boot.veritymode
enforcing
Flashing
I followed the official tutorial for flashing GSIs but changed a couple of things (I may have the order wrong, but I essentially did, once I was in fastboot mode
fastboot flashing unlock # To unlock bootloader
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img # Disable secure boot
fastboot reboot fastboot # Restart in fastbootd
fastboot delete-logical-partition product # I didn't have enough space for Resizing 'system' (I had FAILED (remote: 'Not enough space to resize partition'))
fastboot erase system
fastboot format:ext4 system # because when I tried to flash system.img the first time, I had "Invalid sparse file format at header magic"
fastboot flash system system.img
fastboot format:ext4 userdata
fastboot erase userdata
fastboot format:ext4 metadata
fastboot erase metadata
fastboot erase cache
But when I restart, I am always prompted with
Android Recovery
Blackview /BV4900Pro_US/BV4900Pro10/…
user/release-keys
Use volume up/down and power
Can't load Android system. Your data
may be corrupt. If you continue to get
this message, you may need to perform a
factory data reset and erase all user
data stored on this device
-------------------------
Try again
Factory data reset
-------------------------
Supported API:3
I have tried to reset factory data and to reboot, but I always have the same message…
$ adb --version
Android Debug Bridge version 1.0.41
Version 33.0.3-8952118
I just realized / remembered that this phone uses super.img instead of system.img, maybe I need to repack the system.img into a super.img, following this procedure?
tl;dr: Yes, repacking the system.img into a super.img and then flashing it was key to success.
I have essentially followed what I have described here: https://forum.xda-developers.com/t/...n-blackview-bv-4900-pro.4453955/post-87029001
Except that the three images I used were the original vendor.img, the original product.img, and
aosp_arm64-exp-TP1A.220624.014-8819323-996da050/system.img (available at
Generic System Images (GSIs) | Platform | Android Developers
developer.android.com
)
I used the command
python3 lpmakesimple.py lpbinary/binary/lpmake ./super_20220510.img 4294967296 system=system.img,vendor=./vendor.img,product=./product.img
(4294967296 being picked semi-randomly: it's a multiple of the block size (65536), less than the size of the super partition but more than the size of the three images combined + some more).
That's it: I flashed that super_20220510.img using fastboot flash super super_20220510.img and it was all good!