I am a new guy using flashing rom. Please inform me diff. between signed and unsigned HardSPL as I need to flash to unlock CID.
Signed means only approved ROMs can be flashed, unsigned means anything can be flashed.
Related
can i use the cid unlock put a mod rom and then somehow use the original spl from the last world wide eng rom and how can i extract and use a spl only update from the original file. thanks again....
nikkpap said:
can i use the cid unlock put a mod rom and then somehow use the original spl from the last world wide eng rom and how can i extract and use a spl only update from the original file. thanks again....
Click to expand...
Click to collapse
why would you do it?just unlock and everything will be ok,no need for returning spl
Hi Guys,
I have a problem with my mda compact 4 and for that reason i would like to send it back.
I flashed the device with the rom panosha 1.6 and got the spl 1.40.
Now when i want to flash back to the original stock t-mobile rom, it gives an error on 1% which says "this update utility cannot be used for your PDA phone. please check your update utility"
I tried several other roms and they all work when i flash them.
i've downloaded the dutch t-mobile stock rom from this link: http://rapidshare.com/files/1324381...iamond_52.26a.25.09_Radio_1.00.25.03.rar.html
when i extract this rom to a new folder it doesn't come with an update utility only the nbh file maybe this is the problem?
Hope someone can help me out..much thanks in advance
you have to put RUU on the same folder then you can flashi it.
sumitescp said:
you have to put RUU on the same folder then you can flashi it.
Click to expand...
Click to collapse
I tried that already..it works with all other roms.
But the stock t-mobile rom is the only one that gives the error at 1%
I think the SPL causes your problem. The file you mentined is with OS, radio and SPL, so you have have two possibilities:
1. flash back the original SPL
2. flash the stock ROM without radio and SPL
For both possibilities you need to download the necessary filed. I don't know where to find the dutch stock one, but try SPL here:
http://forum.xda-developers.com/showthread.php?t=408621
But take care: Read before you flash
buildex101 said:
I think the SPL causes your problem. The file you mentined is with OS, radio and SPL, so you have have two possibilities:
1. flash back the original SPL
2. flash the stock ROM without radio and SPL
For both possibilities you need to download the necessary filed. I don't know where to find the dutch stock one, but try SPL here:
http://forum.xda-developers.com/showthread.php?t=408621
But take care: Read before you flash
Click to expand...
Click to collapse
Thanks for the reply.
The rom file i downloaded is the only one i can find for stock t-mobile NL. Is there a way to remove the radio and SPL out of the stock rom with radio and SPL?
So that i can try the second possibility''flash the stock rom without radio and SPL
And is there a way to found out what the original SPL on the mda compact 4 was, or is that just trying?
did the flash to the SPL 1.34 and after that i could flash the stock rom.
many thanks !!
thnx for the info i needed this too in case something goes wrong i want to flash t mobile nl rom back
I don't fully understand this. If I have branded soft it's obvious that I can't upgrade to any other roms with different CID via RUU, can I? What about flashing it via CWM, e.g. this rom http://forum.xda-developers.com/showthread.php?t=1546970 even if I have different CID?
Custom ROMs can be flashed to ANY handset, it's only RUUs that are bound by the CID
not helpful
how about a quick English tutorial ? did you tested the package ?
on what CID you managed to flash the altered rom zip file ?
I have used Googe to translate the Read Me
View attachment 1453868
1immortal said:
how about a quick English tutorial ? did you tested the package ?
on what CID you managed to flash the altered rom zip file ?
Click to expand...
Click to collapse
I have unlocked bootloader
RUU extract 1.19.exe, I have rom.zip
extract rom.zip
in the rom folder, I change mainver of the android-info.txt from 1.29 to 2.17
perform file compression 3 (android-info.txt, boot_signed.img, recovery_signed.img, system.img) with a new name "rom.zip" (it is different from the original rom.zip) and copy the file "rom.zip "the tool Endeavoru_CustomRUU
HTC trip one x on fastboot
run ARUWizard.exe
Just a heads up ... Updating bootloaders are irreversible I would recommend to wait until a recognized developer conforms it otherwise you may end up bricking the device permanently.
did anyone test it?
if we can re sign the zip file it may give s-off too
ShyamSasi said:
Just a heads up ... Updating bootloaders are irreversible I would recommend to wait until a recognized developer conforms it otherwise you may end up bricking the device permanently.
Click to expand...
Click to collapse
I've done successfully on my htc one x
heobanhki said:
I've done successfully on my htc one x
Click to expand...
Click to collapse
This does not help in any way because if you try flashing ROM.zip with hboot.img inside it won't flash because of signature verification failed..
You can do system.img and boot.img and recovery sure will pass because that is what unlocked bootloader is already allowing you too flash other then that it just won't flash...hboot still can't pass the verification...
MemAllocatoR said:
This does not help in any way because if you try flashing ROM.zip with hboot.img inside it won't flash because of signature verification failed..
You can do system.img and boot.img and recovery sure will pass because that is what unlocked bootloader is already allowing you too flash other then that it just won't flash...hboot still can't pass the verification...
Click to expand...
Click to collapse
rom.zip signatures are disabled
Not possible.
This method tampered signature of ROM.zip. It did fool the edited RUU pass version check for ROM installation, but remember the ROM.zip signature is no more signed from HTC thus can only install on unlock phone.
While the firmware.zip required lock bootloader to work with. A S-On's hboot will also check the sign of firmware.zip before flashing. Under this method, firmware.zip inside remain untampered but it will not be accept by existing hboot as bootloader is not lock and if firmware.zip contain a older version of hboot.
REVISED: firmware.zip (hboot lay inside) is not required lock bootloader because OTA can be apply on unlock bootloader. However, it will check signature from HTC before replacing itself.
Recently, some taiwan guys use this method to create custom RUU to getting back to *stock* because they only have an ROM.zip extracted from 2.17 RUU but not RUU itself. Nice to tell that their method also caplable to convert three taiwan carriers CID into taiwan unbranded CID and received .709. OTA. This was possible because the firmware.zip itself allow it.
HebeGuess said:
Not possible.
This method tampered signature of ROM.zip. It did fool the edited RUU pass version check for ROM installation, but remember the ROM.zip signature is no more signed from HTC thus can only install on unlock phone.
While the firmware.zip required lock bootloader to work with. A S-On's hboot will also check the sign of firmware.zip before flashing. Under this method, firmware.zip inside remain untampered but it will not be accept by existing hboot as bootloader is not lock and if firmware.zip contain a older version of hboot.
Recently, some taiwan guys use this method to create custom RUU to getting back to *stock* because they only have an ROM.zip extracted from 2.17 RUU but not RUU itself. Nice to tell that their method also caplable to convert three taiwan carriers CID into taiwan unbranded CID and received .709. OTA. This was possible because the firmware.zip itself allow it.
Click to expand...
Click to collapse
thanks for all
Happy days
So does it work or no?
I'm wanting to go custom but do I really need s_off and supercid or can I just unlock boot loader and be happy lol. I'm using a UK m8
No need S-Off
What you need :
The device now on Marshmallow firmware 6.xx.xxx.x
Unlocked Bootloader
Latest TWRP
Custom ROM
ckpv5 said:
No need S-Off
What you need :
The device now on Marshmallow firmware 6.xx.xxx.x
Unlocked Bootloader
Latest TWRP
Custom ROM
Click to expand...
Click to collapse
Hopefully I'll be ba Co here later all custom
ttocs99 said:
I'm wanting to go custom but do I really need s_off and supercid or can I just unlock boot loader and be happy lol. I'm using a UK m8
Click to expand...
Click to collapse
I think you are confusing custom ROMs with stock (HTC) ROMs (RUU).
Custom ROMs (as mentioned): s-on if fine, just need unlocked bootloader, and custom recovery TWRP
Stock/official ROM (RUU): If you are changing carrier/region versions, you need s-off and change the CID (or SuperCID). But this is not recommended nor necessary for most folks (only suggested for experienced users, with the proper circumstances).