Root Flash new radio in S-OFF device. "Not allowed"

[cicciocant]

This is my situation:

[HIGH]C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.15.50.05.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.161.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4124mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.075s[/HIGH]

I tried to flash a new radio take form PkgOTA.

[HIGH]C:\adb>fastboot flash radio radio.img
sending 'radio' (31713 KB)...
OKAY [ 2.348s]
writing 'radio'...
FAILED (remote: not allowed)
finished. total time: 2.396s[/HIGH]

Why?
The change of CID is allowed.

 

[cicciocant]

THe same with lower Hboot

[HIGH]C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0002
(bootloader) version-baseband: 1.08es.50.02.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.38.161.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:*****
(bootloader) imei: ********
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4043mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 1a7fdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.108s

C:\adb>fastboot flash radio radio.img
sending 'radio' (31713 KB)...
OKAY [ 2.238s]
writing 'radio'...
FAILED (remote: not allowed)
finished. total time: 2.288s[/HIGH]

 

[scotty85]

Regular ship hboots do not permit full write permissions. If the booltoader is unlocked,you can fastboot flash boot and recovery,that's it. If you're locked,you cannot fastboot flash anything.

With normal,ship hboots,you will need to package up the image you want to flash,along with an android info.txt document. The resulting file is flashed from fastboot:

fastboot erase cache

fastboot oem rebootRUU

fastboot flash zip zipname.zip

If you need to get out of ruu mode,
fastboot reboot-bootloader
Should get you back to fastboot

 

[cicciocant]

Than you. And S-off is not useful for this purpose?

 

[scotty85]

Than you. And S-off is not useful for this purpose?

yes! s-off is absolutely neccessary- it is what allows un-official,unsigned files to be flashed in the above manner.

if the phone would be s on,you could flash boot and recovery and system,but all other partitions would be off limits. no radio,hboot,splash,etc. images could be changed. if the phone were locked and s on,you couldnt change anything.

if an engineering hboot existed,you could install it,and then be able to fastboot flash all partitions,but if theres one i dont know about it,and it likely is older. installing the images as ruus from fastboot,is IMO the best way to chagne partitions on an s-off device,as it lets you run the most current ship hboot.

 

[Bodhi Brock]

Regular ship hboots do not permit full write permissions. If the booltoader is unlocked,you can fastboot flash boot and recovery,that's it. If you're locked,you cannot fastboot flash anything.

With normal,ship hboots,you will need to package up the image you want to flash,along with an android info.txt document. The resulting file is flashed from fastboot:

fastboot erase cache

fastboot oem rebootRUU

fastboot flash zip zipname.zip

If you need to get out of ruu mode,
fastboot reboot-bootloader
Should get you back to fastboot

/what if the green install bar only reaches 95% and then hangs there?

 

[scotty85]

/what if the green install bar only reaches 95% and then hangs there?

The green bar is irrelevant. It is normal for it to not reach the other side when flashing unsigned files.the important thing is that the cmd window says "finished"