BlackRose
This is HTC Incredible S custom bootloader
Lecahel
This is HTC Incredible S custom bootloader
Lecahel
Last edited:
[HBOOT][S-OFF] BlackRose [2013.02.03]
- Thread starter dla5244
- Start date
-
- Tags
- development
HBOOT 2.03.0000 Partition Layout
Capable size is 557MB+152MB=709MB
To use lib parititon, we need to modify init.vivo.rc(ramdisk) and update-script
init.vivo.rc
Jump to new loader
You can jump new bootloader by typing this command, "fastboot flash loader <LOADER_IMAGE_FILE>"
This command is to copy new loader image recived by fastboot to RAM(at physical address 0x9e008000) and make CPU jump to 0x9e008000
It is difficult porting new bootloader. but if succeed, we can get other platform(windows phone 7, linux, etc..) on our INCS.
if it hanged after typing command, you failed to boot new loader and it is required pulling battery to return hboot.
Base Address is 0x0(physical address) or 0x8d000000(virtual address, hboot mmu table) our phone(INCS)
As MMU is enabled, we can't access physical address directly but our mmu table included hboot is mapped property, also entry point of lk bootloader(form code aroura) include disabling mmu and relocate routine.
So we(developer of new loader) can set MEMBASE at 0x0.
Also We must know the method to communicate OEMSBL(RADIO) in order to port new bootloader
You must enter the RADIO(AMSS) before execute LK Bootloader
As I analyse HBOOT, I know how to communicate with OEMSBL and enter the radio.
You must add some function(enter the radio) to before target_init routine
Since I succeed to port LK Bootloader our INCS, I'm sure that this command(flash loader) is working property.
Please don't doubt that.
Capable size is 557MB+152MB=709MB
To use lib parititon, we need to modify init.vivo.rc(ramdisk) and update-script
init.vivo.rc
Code:
on emmc
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /devlog 0700 root root
devwait emmc@system
# exec /system/bin/e2fsck_recvy -p emmc@system
mount ext3 emmc@system /system rw data=ordered
[B]mkdir /system/lib 0771 system system
devwait emmc@lib
mount ext3 emmc@lib /system/lib ro data=ordered[/B]
mount ext3 emmc@system /system remount ro
devwait emmc@userdata
exec /system/bin/e2fsck_recvy -p emmc@userdata
mount ext3 emmc@userdata /data nosuid nodev data=ordered
devwait emmc@cache
exec /system/bin/e2fsck_recvy -p emmc@cache
mount ext3 emmc@cache /cache nosuid nodev data=ordered
devwait emmc@devlog
exec /system/bin/e2fsck_recvy -p emmc@devlog
mount ext3 emmc@devlog /devlog nosuid nodev data=orderedJump to new loader
You can jump new bootloader by typing this command, "fastboot flash loader <LOADER_IMAGE_FILE>"
This command is to copy new loader image recived by fastboot to RAM(at physical address 0x9e008000) and make CPU jump to 0x9e008000
It is difficult porting new bootloader. but if succeed, we can get other platform(windows phone 7, linux, etc..) on our INCS.
if it hanged after typing command, you failed to boot new loader and it is required pulling battery to return hboot.
Base Address is 0x0(physical address) or 0x8d000000(virtual address, hboot mmu table) our phone(INCS)
As MMU is enabled, we can't access physical address directly but our mmu table included hboot is mapped property, also entry point of lk bootloader(form code aroura) include disabling mmu and relocate routine.
So we(developer of new loader) can set MEMBASE at 0x0.
Also We must know the method to communicate OEMSBL(RADIO) in order to port new bootloader
You must enter the RADIO(AMSS) before execute LK Bootloader
As I analyse HBOOT, I know how to communicate with OEMSBL and enter the radio.
You must add some function(enter the radio) to before target_init routine
Since I succeed to port LK Bootloader our INCS, I'm sure that this command(flash loader) is working property.
Please don't doubt that.
Last edited:
Hi!
Can I use this and update?
I have now:
Vivo pvt ship s-off rl
hboot-1.13.0000
radio-3822.11.08.29_m
emmc-boot
Thanks!!
Can I use this and update?
I have now:
Vivo pvt ship s-off rl
hboot-1.13.0000
radio-3822.11.08.29_m
emmc-boot
Thanks!!
Yes you can.
Maybe you are radio s-off user.
Even if you are radio s-off, You can't use some command on stock ship hboot
While there is no restrict on BlackRose
Sent from my HTC Incredible S using XDA App
Nice work. I haven't tried it yet as I can't justify the risk but really appreciate the contribution
What's advantage of this hboot? How can a normal user like me who doesn't have much knowledge about this can be benefited?
Sent from my HTC Incredible S using Tapatalk
Sent from my HTC Incredible S using Tapatalk
Congratz for making it onto the front page http://www.xda-developers.com/android/hboot-2-00-blackrose-for-incredible-s-now-available/
http://www.xda-developers.com/android/hboot-2-00-blackrose-for-incredible-s-now-available/
Congratz for making it onto the front page
Yeah nice work m8
Sent from my HTC Incredible S using XDA App
Installed this a couple days ago and ran into some trouble. Nothing I couldn't fix myself but just wanted to let you know.
In the script "install.bat" you have a commandline "adb shell reboot-bootloader", might wanne change that to "adb reboot bootloader"
Sent from my HTC Incredible S using XDA App
In the script "install.bat" you have a commandline "adb shell reboot-bootloader", might wanne change that to "adb reboot bootloader"
Sent from my HTC Incredible S using XDA App
Is there anyway to get rid of the blackrose hboot? I'm trying to flash another hboot in fastboot, but I keep getting "INFOimage update is bypassed". I know why I'm getting it, I'm just curious if I can get rid of it?
Last edited:
To uninstall blackrose, you must execute uninstall.bat.
HBOOT will be changed 1.13.0000
Thanks, I have no reason to remove it, just was curious.
edit: tried it to see if it worked, all it did was restart the phone. Booted to fastboot manually and the same thing happen. Odd.
edit2: renamed hboot_2.00.0000_br.img to hboot_1.13.0000_CRC_8a731c6e_0401.img and used the install.bat instead and that did the trick. Weird.
edit: tried it to see if it worked, all it did was restart the phone. Booted to fastboot manually and the same thing happen. Odd.
edit2: renamed hboot_2.00.0000_br.img to hboot_1.13.0000_CRC_8a731c6e_0401.img and used the install.bat instead and that did the trick. Weird.
Last edited:
What are the conditions (IF ANY) in which we should not install Blackrose HBOOT (eg. certain current hboot versions, s-on/s-off, root, etc.)?
Also what are the reasons and possibilities of BRICKING the device?
Sorry if these questions seem very "beginner", but I think a solid answer to these questions would be all for anyone to just read and decide/understand whether or not to go ahead with this!
Also what are the reasons and possibilities of BRICKING the device?
Sorry if these questions seem very "beginner", but I think a solid answer to these questions would be all for anyone to just read and decide/understand whether or not to go ahead with this!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
26HBOOT 2.03.0000 Partition Layout
Capable size is 557MB+152MB=709MB
To use lib parititon, we need to modify init.vivo.rc(ramdisk) and update-script
init.vivo.rc
Code:on emmc mkdir /system mkdir /data 0771 system system mkdir /cache 0770 system cache mkdir /devlog 0700 root root devwait emmc@system # exec /system/bin/e2fsck_recvy -p emmc@system mount ext3 emmc@system /system rw data=ordered [B]mkdir /system/lib 0771 system system devwait emmc@lib mount ext3 emmc@lib /system/lib ro data=ordered[/B] mount ext3 emmc@system /system remount ro devwait emmc@userdata exec /system/bin/e2fsck_recvy -p emmc@userdata mount ext3 emmc@userdata /data nosuid nodev data=ordered devwait emmc@cache exec /system/bin/e2fsck_recvy -p emmc@cache mount ext3 emmc@cache /cache nosuid nodev data=ordered devwait emmc@devlog exec /system/bin/e2fsck_recvy -p emmc@devlog mount ext3 emmc@devlog /devlog nosuid nodev data=ordered
Jump to new loader
You can jump new bootloader by typing this command, "fastboot flash loader <LOADER_IMAGE_FILE>"
This command is to copy new loader image recived by fastboot to RAM(at physical address 0x9e008000) and make CPU jump to 0x9e008000
It is difficult porting new bootloader. but if succeed, we can get other platform(windows phone 7, linux, etc..) on our INCS.
if it hanged after typing command, you failed to boot new loader and it is required pulling battery to return hboot.
Base Address is 0x0(physical address) or 0x8d000000(virtual address, hboot mmu table) our phone(INCS)
As MMU is enabled, we can't access physical address directly but our mmu table included hboot is mapped property, also entry point of lk bootloader(form code aroura) include disabling mmu and relocate routine.
So we(developer of new loader) can set MEMBASE at 0x0.
Also We must know the method to communicate OEMSBL(RADIO) in order to port new bootloader
You must enter the RADIO(AMSS) before execute LK Bootloader
As I analyse HBOOT, I know how to communicate with OEMSBL and enter the radio.
You must add some function(enter the radio) to before target_init routine
Since I succeed to port LK Bootloader our INCS, I'm sure that this command(flash loader) is working property.
Please don't doubt that.7
If you haven't been able to successfully install blackrose yet, give this method a try.
- Download this
- Place it on the root of your SD-card
- Reboot into bootloader and the file should be picked up automatically
- Go through the update process
That's how I installed blackrose on my phone.
I believe the partitions have changed to accommodate ICS with Sense 3.6. Also a new /lib partition is available in HBOOT 2.02, although I haven't found a use for it myself.
