Hi I have a HTC one SV K2_UL and I hard bricked it while unlocking the boot loader, can anyone supply a working debrick.IMG from the /dev/block/mmcblk0p6 partition?
I don't care what its locked to I just need this partition!
Related
Just got my Sensation back from repair, so now it's already on 4.03 ICS. I remember from before there was some discussion of the new HBOOT version not being about to S-off. However, HTC offers the unlock tool. Just wondering if it's a bad thing to do using their unlock tool or does it matter?
Look at the S-OFF guides for 1.2x.xxxx HBOOTs.
The wire trick is a pain but does work.
EDIT: meant to say that I believe you don't need the HTC unlock thing now. I used it but......
newr said:
Just got my Sensation back from repair, so now it's already on 4.03 ICS. I remember from before there was some discussion of the new HBOOT version not being about to S-off. However, HTC offers the unlock tool. Just wondering if it's a bad thing to do using their unlock tool or does it matter?
Click to expand...
Click to collapse
S-OFF and htcdev tool are two different things
htcdev tool only disables write protection on recovery partition - allowing you to flash custom recovery.
S-OFF unlocks all partitions including boot partition which means you can flash ROMs without flashing boot.img manually or needing to have 4EXT SmartSync on.
In short the htcdev tool is misnamed because it does not unlock the bootloader - only unlocks recovery
Jonny said:
In short the htcdev tool is misnamed because it does not unlock the bootloader - only unlocks recovery
Click to expand...
Click to collapse
only recovery ? isn't it recovery,system,boot and data partitions ?
ganeshp said:
only recovery ? isn't it recovery,system,boot and data partitions ?
Click to expand...
Click to collapse
Boot partition? no because you have to manually flash a boot.img with htcdev
system partition write protection is controlled by the OS and disabled by rooting - rooting allows the end user to give certain programs write permission. As to whether the recovery can access system and data partitions without unlocking the bootloader, I believe it can because stock recovery can overwrite system and data using OTA files controlled by a similar updater-script that we use in custom ROMs
Jonny said:
Boot partition? no because you have to manually flash a boot.img with htcdev
system partition write protection is controlled by the OS and disabled by rooting - rooting allows the end user to give certain programs write permission. As to whether the recovery can access system and data partitions without unlocking the bootloader, I believe it can because stock recovery can overwrite system and data using OTA files controlled by a similar updater-script that we use in custom ROMs
Click to expand...
Click to collapse
If boot partition is locked then you can't even flash boot.img via bootloader using fastboot flash command.. I think it has some issue getting flashed from recovery.. That's all
First to get root itself you require write permission on system partition.. That means at the end you require system partition unlocked.
The stock recovery can only flash signed stuff.. Thus a signature check is made.. (at the end unlocking of partitions is nothing but removing sign checking of whatever we flash)
Iirc the FAQ of htc-dev mentioned about what partitions are unlocked.... And those are what I mentioned
Sent from my HTC Sensation 4G using xda premium
Hello,
I'm a newbie with Android but I've managed to unlock the bootloader and root my device successfully. Now I wish to change my CID from TELUS001 to HTC__001. Ive been following this guide:
http://forum.xda-developers.com/show....php?t=1674202
However in step 3 it seems to want to send the mmcblk0p4 file to the phone's sdcard which I don't have cause Im using an HTC ONE S.
Is there a way to send that mmcblk0p4 file to the phone's storage instead? Or is there some other way to change my CID to HTC__001?
Thanks in advance
well, hope someone have gone throught this
here is how i did it
i have a z710e, with root through htcdev (the stuff with the token), then i flashed a recovery (TWRP 2.3.3.0)
my CID is BSTAR301 a my mid is PG5811000
the bootloader version 1.21.0001
and the main version is 1.52.515.4
also i have S-ON
with all that i tried to flash a c-rom (dant say anything i know i screwed up by having s-on):crying: :crying::crying:
and i got stuck at boot
i cant go back to stock because i cant find a ruu that meets the requirements, i cant boot anything only recovery and fastboot
i know that for tunring s-on to s-off i need to do the wire trick with JuopunutBear
but it needs a booting fw
and for puting a booting fw i need s-off
so im stuck in this situation
do anyone know a solution for this?
hope you understand my english
many thanks!
Search the KGS utility and after that make the super cid,with that utility for she has been worked....i have the latest bootloader,by the way you can download a friendly firmware and that's it
get a formatted sdcard plug it into your pc with a sdcard adapter and create a goldcard then put the sdcard into your phone and run any RUU and then try to S-OFF. please use This Thread for howto create goldcard this method is your best bet mate run the RUU when in fastboot
alfovic said:
well, hope someone have gone throught this
here is how i did it
i have a z710e, with root through htcdev (the stuff with the token), then i flashed a recovery (TWRP 2.3.3.0)
my CID is BSTAR301 a my mid is PG5811000
the bootloader version 1.21.0001
and the main version is 1.52.515.4
also i have S-ON
with all that i tried to flash a c-rom (dant say anything i know i screwed up by having s-on):crying: :crying::crying:
and i got stuck at boot
i cant go back to stock because i cant find a ruu that meets the requirements, i cant boot anything only recovery and fastboot
i know that for tunring s-on to s-off i need to do the wire trick with JuopunutBear
but it needs a booting fw
and for puting a booting fw i need s-off
so im stuck in this situation
do anyone know a solution for this?
hope you understand my english
many thanks!
Click to expand...
Click to collapse
i managed to make it boot, i flashed ICS digitalized v0.9_final and it did boot
then i tried to do the juopunutBear and it send me the following message
======== ControlBear version 0.1 for JuopunutBear S-OFF ==========
Old beer detected...... Please wait......
Starting up......
Using eMMC dev /dev/block/mmcblk0
Using MMC dev /dev/block/mmcblk1
Boot partition is /dev/block/mmcblk0p20
Recovery partition is /dev/block/mmcblk0p21
Is information correct? You have 5 seconds time to press CTRL+C
Finding some beer.....
Rebooting.......
Waiting device....
Found device... Please wait...
/system/bin/sh: /data/local/JuopunutBear: cannot execute - Permission denied
Quit....
Press ENTER to exit.....
after wich i have to reflash the kernel to be able to boot again
is there something im missing? btw im going to try the goldcard metod later
thanks!!!
solved evrything
thanks to evryone!
I don't know how this happened because I didn't never flash or root my htc. I have access to hboot and fastboot + RUU. I want to flash my htc with new firmware but if I can't get to android then I can't 'confirm' bootloader unlocking. I have Unlock_code.bin, I flashed it but in android I can't confirm unlocking. Now i don't know what can I do please help me
Duplicate.
http://forum.xda-developers.com/gen...op-problem-t3163264/post61997737#post61997737
Can anyone explain to me the eMMC boot and tampered locked!?!?
You could help yourself by adding device / model to thread's title.
My guess is it's a screen generated by device's bootloader. Indicates device got tampered in whatever way, and bootloader is locked ( S-ON -> Security On ). eMMC-boot seems to be size of /boot partition.