Ok, thanks a lot. I will get the dump files in a while. I do not know noone with Locked bootloader, so I will relock my own and grab the dump files again.
Anyway, do you know any other way to back to LOCKED status?
[how to] lock/unlock your bootloader without htcdev(s-off required)
- Thread starter scotty1223
- Start date
Ok, thanks a lot. I will get the dump files in a while. I do not know noone with Locked bootloader, so I will relock my own and grab the dump files again.
Anyway, do you know any other way to back to LOCKED status?
We are working on that.
http://xdaforums.com/showthread.php?p=50546613
Let's keep discussions on that thread. If youd like to help, I'd like a getvar all, and I need to see mmcblk0p3 and 0p7
Sent from my HTC6435LVW using Tapatalk
If you can get s off via some method that does not require htcdev unlock, then it is not required
Sent from my HTC6435LVW using Tapatalk
Hi scotty buddy.
My Model id PN07110, cid HTC__38, hboot 1.56, android 4.4.2. Indian HTC one. I am soff and locked boot loader and not rooted. Need recovery zip to flash in ruu mode. Bro, can you make a proper recovery zip of twrp to flash in ruu mode. Thanks.
Sent from my HTC One using Tapatalk
My Model id PN07110, cid HTC__38, hboot 1.56, android 4.4.2. Indian HTC one. I am soff and locked boot loader and not rooted. Need recovery zip to flash in ruu mode. Bro, can you make a proper recovery zip of twrp to flash in ruu mode. Thanks.
Sent from my HTC One using Tapatalk
No one said you needed to be on a stock room and recovery. You just need to be in a root shell to enter the lock command.
If you're not rooted, you can run the command in a custom recovery, or use a temp root.
Sent from my HTC6435LVW using Tapatalk
You'll have to find one that works with wherever software build you're on. You're on you're own there, I've no idea.
Sent from my HTC6435LVW using Tapatalk
I've used this method to lock the bootloader for shipping it to HTC service (camera issues).
Additionally I set the device back to S-ON.
Problem is that I am no longer able to unlock the bootloader with htcdev. The unlock-splash doesn't appear anymore. My guess is it could has something to do with this: http://xdaforums.com/showpost.php?p=50335978&postcount=197
So be careful with this.
Additionally I set the device back to S-ON.
Problem is that I am no longer able to unlock the bootloader with htcdev. The unlock-splash doesn't appear anymore. My guess is it could has something to do with this: http://xdaforums.com/showpost.php?p=50335978&postcount=197
So be careful with this.
Is your phone a converted GPE? Your error sounds consistent with converted phones. I've not heard this complaint on phones converted back to their original state.
I don't think the post you referenced is an issue. When you run the command,it only writes 4 bytes,im by no means an expert,but there is no evidence to me that the command is filling the rest of the partition with 00(it actually is all 00 allready) .
If you trace the origins of this all the way back to s_trace's original thread, you'll see that unlocking makes a couple other changes in other partitions. It may be possible we need to change more than the lock flag,but again,I've not heard of folks having trouble reunlocking again,other than the converted gpe phones.
IMO,people need to start understanding that s-off is not an indicator you have messed with the device,and stop turning the radio secure flag back on for warranty work. If you were still s off,you could easily install a recovery and re-root.
I apologize this mod has.gotten you into a pickle. Please keep us updated on your solution
have you tried a.factory reset from hboot? Thanks for bringing it to our attention,folks indeed should be careful.
Sent from my HTC PG09410 using Tapatalk 2
edit:
a bit of research before i have to leave for the day shows its an issue with some real GPE phones as well,possibly some sort of mismatch with the 4.4 update.
if you have a "normal" phone,it sounds like one of your partitions may be something other than what the phone is expecting(tho not extreme enuff to invoke a "do not boot" mode).
i had similar issue with an att one x. i did not get the splash failure error,but did get the failure of an unlock splash/option to appear
in my case,i had hex edited the misc partition to a lower main version,and after i restored the original,the unlock worked successfully.i did find references to GPE s-off folks who got your same error being able to downgrade to 4.2.2,and then fastboot oem unlock worked again. doesnt help you much,but may add to the liklehood that the prollem lies within the 4.4 update
my only suggestion is at this time is to try and find a working temp root and then run firewater. a bit more info about your phone may help... specs of before and after if its a converted phone,and maybe a getvar all
Last edited:
Factory Reset was one of the first things I tried. Didn't help.
Converted GPE means it originally was a Google Edition converted to a Stock Edition? In this case - no. It was a european unbranded "401" phone. I only converted it once in the other direction to a GPE by this thread. Maybe this cause my problem.
Converted GPE means it originally was a Google Edition converted to a Stock Edition? In this case - no. It was a european unbranded "401" phone. I only converted it once in the other direction to a GPE by this thread. Maybe this cause my problem.
No... The other way. As you did.
Very likely the issue is missing bits of other firmware done the conversion ruu is not complete and signed by HTC.
You should have gone back to stock .401 if you wanted to turn s on.
Did you change cid/mid as well?
Sent from my HTC6435LVW using Tapatalk
Oh ok, I wasn't aware of that.
Before I locked the phone I flashed the original 2.24.401.1 firmware and Stock Odexed ROM inclusive Stock Recovery and CID HTC__102 but I assume there was something the GPE RUU changed I didn't roll back before locking. You could say I locked out myself and flushed the key down the toilet.
Before I locked the phone I flashed the original 2.24.401.1 firmware and Stock Odexed ROM inclusive Stock Recovery and CID HTC__102 but I assume there was something the GPE RUU changed I didn't roll back before locking. You could say I locked out myself and flushed the key down the toilet
.Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
87*this thread is for m7. it will not work on m8,m9, or any other newer devices! search m8 general for the thread there(same name)
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock.
originally,we used a zip file flashable in recovery. i have found it to work on gsm devices with 1.44 hboot and CW recovery. it did not work with twrp. if the following is too scary,feel free to test the zip files. that thread,info,and downloads can be found here. since not all recoverys are working,these values can be changed with simple adb commands.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
you do NOT need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.
*you must be s off.
*you must have superuser installed(seethis post] if you need help installing a recovery so you can install superuser)
read this:
this will not work if your s on. its not a way to magically unlock
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for giving me the echo comand,so yall didnt need to dump,edit with a hex editor,and copy back
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
-kdj67f for fearlessly testing on vzw m7_wlv and putting up some screenshots in post 2. thanks!
-matthew0776 for fearlessly testing for sprint m7_wls
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb
2)reset your "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
*i have tested this on my gsm htc one. if someone wants to test on vzw,ill add you to the credits
1299% is good enough for me haha! Phone just hut 50% charged, give me a minute. Will post back with pictures.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 08:56 PM ---------- Previous post was at 08:41 PM ----------
Confirmed, code working. Flags set/reset. Phone even reboots and works will upload pics/screenshots.
Thanks!
Starting out unlocked:
Locking:
Locked:
Unlocking:
Re-unlocked:
Very good work!4you dont really need to unlock. pack your recovery image with an android info text document for your variant. you can get the document from an OTA firmware package or decrypted ruu.
you can install this type of zip file in the following manner:
once you have a custom recovery you can add superuser,or flash a rom. you do not need to unlock,but you can if you want after adding superuser,or by just running the command in recovery,as most custom recoverys have an adb root shell access.
Hi scotty, love your work :good:
Just dropped by to leave this here: TWRP/CWM for RUU mode for M7_U/UL only
these are packaged with an android-info.txt that has PN0710000 through PN0714000 and all CIDs should work (except 1 or 2 very rare ones).
4
you can still flash a recovery. you just need to pack it up in a zip file with an android info document and flash via ruu mode.
you do not need to be unlocked for anything. it is strictly a personal preference(of youd rather use fastboot flash than a zip file)
New posts
-
-
General [HELP THREAD] Ask ANY Question. Noob Friendly.
- Latest: TheGiantHogweed
