FORUMS

Intel & Micron Announce “Revolutionary” Storage Tech

Intel & Micron have announced 3D Xpoint technology—”the … more

Google Now Interfaces With Third-Party Messaging Apps

Google has announced that Ok Google voice commands can now be used to send … more

Make Your Lockscreen More Productive With Widgets

Are you running Android Lollipop? Do you miss the ability to add widgets to your lock … more

Moto X Style, Moto X Play and Moto G Forums Are Here!

The latest family members of the new generation of Motorola devices are … more

[Q] New HTC One - S-OFF!!

189 posts
Thanks Meter: 42
 
Post Reply Subscribe to Thread Email Thread
14th June 2014, 11:09 AM |#31  
Rah0ol's Avatar
OP Senior Member
Thanks Meter: 42
 
More
Quote:
Originally Posted by nkk71

Nothing will be lost, but during the "masked firmware" flash, you will end up with a custom recovery (depending on which file you choose), i recommend TWRP 2.6.3.3 or 2.6.3.4
you need a custom recovery to run scotty's commands since it gives you superuser access; scotty's commands just toggle the locked/unlocked status of bootloader it doesn't touch any files.

upon reboot, TWRP will probably tell you that you are not rooted, just select NO to the "install root" prompt.


Got it Thanks for all the info
 
 
14th June 2014, 12:49 PM |#32  
Rah0ol's Avatar
OP Senior Member
Thanks Meter: 42
 
More
Quote:
Originally Posted by nkk71

Nothing will be lost, but during the "masked firmware" flash, you will end up with a custom recovery (depending on which file you choose), i recommend TWRP 2.6.3.3 or 2.6.3.4
you need a custom recovery to run scotty's commands since it gives you superuser access; scotty's commands just toggle the locked/unlocked status of bootloader it doesn't touch any files.

upon reboot, TWRP will probably tell you that you are not rooted, just select NO to the "install root" prompt.

I successfully installed the TWRP Recovery on my One. But to follow the process to Unlocking the bootloader, the system shud be rooted. Can I take a Superuser Zip and install over recovery? or will the bootloader block it?

I didnt get prompt to Install Root on TWRP Recovery though..
14th June 2014, 01:55 PM |#33  
Quote:
Originally Posted by Rah0ol

I successfully installed the TWRP Recovery on my One. But to follow the process to Unlocking the bootloader, the system shud be rooted. Can I take a Superuser Zip and install over recovery? or will the bootloader block it?

I didnt get prompt to Install Root on TWRP Recovery though..

do the adb commands while booted in TWRP not in the ROM, in TWRP you already have SU privileges
14th June 2014, 03:24 PM |#34  
Rah0ol's Avatar
OP Senior Member
Thanks Meter: 42
 
More
Quote:
Originally Posted by nkk71

do the adb commands while booted in TWRP not in the ROM, in TWRP you already have SU privileges

I am sorry, I didnt get this step.. Do you mean,

1. In the terminal on TWRP recovery, excecute the commands?

or

Now that I have TWRP Installed, I can boot to the bootloader and excecute the commands?
14th June 2014, 03:30 PM |#35  
Quote:
Originally Posted by Rah0ol

I am sorry, I didnt get this step.. Do you mean,

1. In the terminal on TWRP recovery, excecute the commands?

or

Now that I have TWRP Installed, I can boot to the bootloader and excecute the commands?

Not sure why you're trying to make things hard on yourself so check the red parts:


Since you are S-Off, use a custom recovery masked in a firwmare package: you can use of these "firmware" packages (m7_u/ul only):
http://www.androidfilehost.com/?w=files&flid=13085

in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip fw_m7ul_TWRP_2.6.3.3_1.26.401.33.zip
fastboot reboot-bootloader


-> enter RECOVERY (should be TWRP or CWM now)

and use the commands below (thanks to @scotty1223's commands in custom recovery http://forum.xda-developers.com/show....php?t=2475914 to unlock bootloader)


Code:
C:\ADB3>adb devices
List of devices attached
HT34xxxxxxxx    recovery <- you need to be in custom recovery to
                            ensure root privileges
                            i.e. an adb shell with # as opposed to $


C:\ADB3>adb shell

Note
CWM shell prompt usually looks like ~#
TWRP shell prompt usually looks like ~ # ←[6n
it doesn't matter, you just type (or even better copy/paste) the commands in bold blue


Setting UNLOCKED
~ # echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 
4+0 records in
4+0 records out
4 bytes (4B) copied, 0.007691 seconds, 520B/s

~ # exit
exit

C:\ADB3>adb reboot bootloader
^^ if this doesn't work in your particular version, 
   just select reboot to bootloader in TWRP.

ps: your version-main will now say 1.26.401.33 (reflecting the recovery version 2.6.3.3); it didn't actually change, but version-main always shows the last thing flashed in ruu mode.
.
The Following User Says Thank You to nkk71 For This Useful Post: [ View ]
14th June 2014, 03:43 PM |#36  
Rah0ol's Avatar
OP Senior Member
Thanks Meter: 42
 
More
Quote:
Originally Posted by nkk71

Not sure why you're trying to make things hard on yourself so check the red parts:


Since you are S-Off, use a custom recovery masked in a firwmare package: you can use of these "firmware" packages (m7_u/ul only):
http://www.androidfilehost.com/?w=files&flid=13085

in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip fw_m7ul_TWRP_2.6.3.3_1.26.401.33.zip
fastboot reboot-bootloader


-> enter RECOVERY (should be TWRP or CWM now)

and use the commands below (thanks to @scotty1223's commands in custom recovery http://forum.xda-developers.com/show....php?t=2475914 to unlock bootloader)


Code:
C:\ADB3>adb devices
List of devices attached
HT34xxxxxxxx    recovery <- you need to be in custom recovery to
                            ensure root privileges
                            i.e. an adb shell with # as opposed to $


C:\ADB3>adb shell

Note
CWM shell prompt usually looks like ~#
TWRP shell prompt usually looks like ~ # ←[6n
it doesn't matter, you just type (or even better copy/paste) the commands in bold blue


Setting UNLOCKED
~ # echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 
4+0 records in
4+0 records out
4 bytes (4B) copied, 0.007691 seconds, 520B/s

~ # exit
exit

C:\ADB3>adb reboot bootloader
^^ if this doesn't work in your particular version, 
   just select reboot to bootloader in TWRP.

ps: your version-main will now say 1.26.401.33 (reflecting the recovery version 2.6.3.3); it didn't actually change, but version-main always shows the last thing flashed in ruu mode.
.

He he , I just flashed SuperUser Zip from recovery and voila, I have root access Now gonna run those commands to get Unlocked Bootloader
14th June 2014, 06:58 PM |#37  
Rah0ol's Avatar
OP Senior Member
Thanks Meter: 42
 
More
Quote:
Originally Posted by nkk71

Not sure why you're trying to make things hard on yourself so check the red parts:


Since you are S-Off, use a custom recovery masked in a firwmare package: you can use of these "firmware" packages (m7_u/ul only):
http://www.androidfilehost.com/?w=files&flid=13085

in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip fw_m7ul_TWRP_2.6.3.3_1.26.401.33.zip
fastboot reboot-bootloader


-> enter RECOVERY (should be TWRP or CWM now)

and use the commands below (thanks to @scotty1223's commands in custom recovery http://forum.xda-developers.com/show....php?t=2475914 to unlock bootloader)


Code:
C:\ADB3>adb devices
List of devices attached
HT34xxxxxxxx    recovery <- you need to be in custom recovery to
                            ensure root privileges
                            i.e. an adb shell with # as opposed to $


C:\ADB3>adb shell

Note
CWM shell prompt usually looks like ~#
TWRP shell prompt usually looks like ~ # ←[6n
it doesn't matter, you just type (or even better copy/paste) the commands in bold blue


Setting UNLOCKED
~ # echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 
4+0 records in
4+0 records out
4 bytes (4B) copied, 0.007691 seconds, 520B/s

~ # exit
exit

C:\ADB3>adb reboot bootloader
^^ if this doesn't work in your particular version, 
   just select reboot to bootloader in TWRP.

ps: your version-main will now say 1.26.401.33 (reflecting the recovery version 2.6.3.3); it didn't actually change, but version-main always shows the last thing flashed in ruu mode.
.

Now my device is not responding to adb commands

Tried drivers, softwares etc.. Still working on it.. Any suggestions?
15th June 2014, 08:53 AM |#38  
Rah0ol's Avatar
OP Senior Member
Thanks Meter: 42
 
More
Thanks for all the help @nkk71 , I was successfully able to unlock the bootloader, install TWRP recovery, Install Superuser on my phone with CID - 111111111 , I think I can flash any ROMs (except carrier which I wouldnt too )

On the terms of MID, I had mentioned that the device MID is written as (bootloader) modelid: PN071**** I had pulled the mmcblk0p6_bak.img and when opened form text, I am not getting much info on the device ID, U had mentioned as a form of table on the info provided by the img file.

Just want to know how to open mmcblk0p6_bak.img on a readable format
15th June 2014, 09:29 AM |#39  
Quote:
Originally Posted by Rah0ol

Thanks for all the help @nkk71 , I was successfully able to unlock the bootloader, install TWRP recovery, Install Superuser on my phone with CID - 111111111 , I think I can flash any ROMs (except carrier which I wouldnt too )

On the terms of MID, I had mentioned that the device MID is written as (bootloader) modelid: PN071**** I had pulled the mmcblk0p6_bak.img and when opened form text, I am not getting much info on the device ID, U had mentioned as a form of table on the info provided by the img file.

Just want to know how to open mmcblk0p6_bak.img on a readable format

you need to use a hex editor to be able to "read" it.


or just change it using the tool: http://forum.xda-developers.com/show....php?t=2535365 to PN0710000 (that's international UL model)
15th June 2014, 06:57 PM |#40  
Rah0ol's Avatar
OP Senior Member
Thanks Meter: 42
 
More
Quote:
Originally Posted by nkk71

you need to use a hex editor to be able to "read" it.


or just change it using the tool: http://forum.xda-developers.com/show....php?t=2535365 to PN0710000 (that's international UL model)

Done and Dusted Thanks a lot @nkk71 You were of great help in this
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes