Just curious what exactly is going on during that 30 minutes required to unlock the bootloader on P769. What is it that has to take place within the phone/radio to allow it to be unlocked?
Also, say you wait an hour, then pass the oem-unlock command only to have the phone simply reboot, do you then have to wait an additional 30+ to even have a chance of it unlocking?
I have been able to unlock it once, but the bastard refuses to do anything but reboot when I try now. Just seeking more info as to what exactly is going on in that 30 minutes so I can make sure I am doing everything possible.
socalledsin said:
Just curious what exactly is going on during that 30 minutes required to unlock the bootloader on P769. What is it that has to take place within the phone/radio to allow it to be unlocked?
Also, say you wait an hour, then pass the oem-unlock command only to have the phone simply reboot, do you then have to wait an additional 30+ to even have a chance of it unlocking?
I have been able to unlock it once, but the bastard refuses to do anything but reboot when I try now. Just seeking more info as to what exactly is going on in that 30 minutes so I can make sure I am doing everything possible.
Click to expand...
Click to collapse
Are you talking about one device ? What did you do after you unlocked the bootloader ?
Lelus said:
Are you talking about one device ? What did you do after you unlocked the bootloader ?
Click to expand...
Click to collapse
Yeah same device. I flashed CM10 before the bugs were fixxed, then went back to V20D which appears to have relocked the bootloader.
socalledsin said:
Yeah same device. I flashed CM10 before the bugs were fixxed, then went back to V20D which appears to have relocked the bootloader.
Click to expand...
Click to collapse
Since you've unlocked it already ,you just need xloader and uboot from jb p760, use ones from this post
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/p2.bin of=/dev/block/mmcblk0p2
adb shell su -c busybox dd if=/sdcard/external_sd/p1.bin of=/dev/block/mmcblk0p1
or use fastboot option 6
Lelus said:
Since you've unlocked it already ,you just need xloader and uboot from jb p760, use ones from this post
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/p2.bin of=/dev/block/mmcblk0p2
adb shell su -c busybox dd if=/sdcard/external_sd/p1.bin of=/dev/block/mmcblk0p1
or use fastboot option 6
Click to expand...
Click to collapse
Awesome, I will give that a shot. Thanks a ton man.
So after doing that, I can then just push CWM and reflash CM10?
socalledsin said:
Awesome, I will give that a shot. Thanks a ton man.
So after doing that, I can then just push CWM and reflash CM10?
Click to expand...
Click to collapse
sure , you can even flash recovery x and u at the same time
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery_file of=/dev/block/mmcblk0p4
Lelus said:
sure , you can even flash recovery x and u at the same time
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery_file of=/dev/block/mmcblk0p4
Click to expand...
Click to collapse
OMG It worked! Thank you so much. I feel like such an idiot now lol. Let the flashing commence!
Related
I've corrupted my recovery image. I'd be very grateful to anyone who could take a minute to grab the image from their amaze.
Here's the step-by-step on how to do it:
1. Unzip zergRush from the attached zipfile. Place it on your PC
2. Push it to your phone using adb (adb push zergRush /data/local)
3. Adb shell to your phone (adb shell)
4. cd to /data/local (cd /data/local)
4. Run zergRush (./zergRush)
5. It will churn for a bit and then you should have temp root.
6. Adb shell back onto the phone. (adb shell)
7. From the # prompt run (dd if=/dev/block/mmcblk0p23 /sdcard/recovery.img)
8. post the recovery image somewhere I can access.
9. receive my gratitude
tia
-xdadevelopers-user
Here you go....
http://dl.dropbox.com/u/19769336/recovery.img
Thank you!
I feel much better now that I have a working recovery - though I'm not exactly sure why.
-xdadevelopers-user
other than fastboot how would you push it back to the device
Hboot
Sent from my HTC Sensation Z710e using xda premium
crackeyes said:
other than fastboot how would you push it back to the device
Click to expand...
Click to collapse
I guess in theory, if you have root, you could dd it back to the correct partition from the running android os.
Code:
#dd if=recovery.img of=/dev/block/mmcblk0p23
Though I haven't tried that. I just used fastboot.
-xdadevelopers-user
xdadevelopers-user said:
I guess in theory, if you have root, you could dd it back to the correct partition from the running android os.
Code:
#dd if=recovery.img of=/dev/block/mmcblk0p23
Though I haven't tried that. I just used fastboot.
-xdadevelopers-user
Click to expand...
Click to collapse
that worked but it is still f'ed up this phone is a brick LOL oh well lets see how i can fry it and get a new one
crackeyes said:
that worked but it is still f'ed up this phone is a brick LOL oh well lets see how i can fry it and get a new one
Click to expand...
Click to collapse
hey crack eyes could you test something for me?
Code:
dd if=(direcotry path to hboot.img Example: C:\Hboot.img) of=/dev/block/mmcblk0p12
could you trry that with this hboot.img
http://www.multiupload.com/D7HEFK9DH6
exract hboot.img first then place in c:\
xboarder56 said:
hey crack eyes could you test something for me?
Code:
dd if=(direcotry path to hboot.img Example: C:\Hboot.img) of=/dev/block/mmcblk0p12
could you trry that with this hboot.img
http://www.multiupload.com/D7HEFK9DH6
exract hboot.img first then place in c:\
Click to expand...
Click to collapse
That cannot work. The example you provide has the input file on the PC and the output file is a block device on the phone. The dd command, when run from a PC won't be able to see the output file since it doesn't exist on the PC. Or, if you run dd from the phone it won't be able to see the hboot.img because it's on the PC - not the phone.
For it to work you'd need to first get the hboot.img on the phone somewhere. If you have an sd card you could copy it to /sdcard or you could put it on /data/local.
Then the command would be something like:
dd if=/sdcard/hboot.img /dev/block/mmcblk0p12
And, of course for this to work you'd need an unlocked bootloader and a working device that has root. And, even then, I'd guess this would either not work or brick the device. But, if someone's willing to test it then, hey, who am I to say otherwise - go for it!
-xdadevelopers-user
cmenard said:
Here you go....
http://dl.dropbox.com/u/19769336/recovery.img
Click to expand...
Click to collapse
Can anyone verify if the recovery in the above link is the Stock Recovery for T-Mo Amaze? I'm on GB and want to get the ICS OTA update but Hasoon has removed the Stock Recovery from his AIO toolkit. Thanks!
ernieg92 said:
Can anyone verify if the recovery in the above link is the Stock Recovery for T-Mo Amaze? I'm on GB and want to get the ICS OTA update but Hasoon has removed the Stock Recovery from his AIO toolkit. Thanks!
Click to expand...
Click to collapse
You don't need a stock recovery, just repock boot loader and apply update
Sent from my HTC_Amaze_4G using Tapatalk 2
Just do what? Thanks
EclipzeRemix said:
You don't need a stock recovery, just repock boot loader and apply update
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Wrong place to ask questions
Sent from my HTC_Amaze_4G using xda premium
One month after i bought it, my ShooterU has got a MB replacement (RMA)
And now it's impossible for me to unlock bootloader with the htcdev method.
Is there another way to make it possible (Evo3d with stock ICS) ?
Thank you for helping me, i'm furious with it.
Post in q&a not development !
crossmanbx said:
One month after i bought it, my ShooterU has got a MB replacement (RMA)
And now it's impossible for me to unlock bootloader with the htcdev method.
Is there another way to make it possible (Evo3d with stock ICS) ?
Thank you for helping me, i'm furious with it.
Click to expand...
Click to collapse
HTCDev unlock method doesn't work on phones with replaced motherboards. You're out of luck, sorry.
it's called bad blocks. nothing you can do about it ...
Can't you use juopunutbear and do the wire trick?
00mpollard said:
Can't you use juopunutbear and do the wire trick?
Click to expand...
Click to collapse
I think it's a good idea to try the juopunutbear, but i need to have temp root at least.
And all temp root i find are made for Gingerbread.
Does anyone know a temp root method for ICS ?
Thank you
Questions and non-development related should be posted in the appropriate sections. This thread is not dev related, so I'm moving it.
So there isn't another method to unlock my bootloader ? Htcdev is the only way to do this ? What does it mean ?
My evo 3d is unrootable ? The bootloader still be blocked forever ?
Please help me not to sell it ! Thank you
crossmanbx said:
So there isn't another method to unlock my bootloader ? Htcdev is the only way to do this ? What does it mean ?
My evo 3d is unrootable ? The bootloader still be blocked forever ?
Please help me not to sell it ! Thank you
Click to expand...
Click to collapse
Unless Unlimited.io releases a version of controlbear that works on just temp root, nothing can be done.
Such a method already exists for the HTC Sensation.
kgs1992 said:
Unless Unlimited.io releases a version of controlbear that works on just temp root, nothing can be done.
Such a method already exists for the HTC Sensation.
Click to expand...
Click to collapse
I don't believe there's a temp root technique that works on the Evo 3D anyway, but if you know of one some users here have been looking for it for other reasons, especially one that works with ICS.
The Evo 3D is definitely not the same phone as the Sensation and has different capabilities and limitations.
ramjet73
ramjet73 said:
I don't believe there's a temp root technique that works on the Evo 3D anyway, but if you know of one some users here have been looking for it for other reasons, especially one that works with ICS.
The Evo 3D is definitely not the same phone as the Sensation and has different capabilities and limitations.
ramjet73
Click to expand...
Click to collapse
I agree. Only speculating.
Doesn't TPSparkyRoot work?
Try this:
To root:
Code:
adb shell "rm /data/local/tmp.orig"
adb shell "mv /data/local/tmp /data/local/tmp.orig"
adb shell "rmdir /data/local/tmp"
adb shell "ln -s /data /data/local/tmp"
adb shell "rm /data/local.prop"
adb shell "chmod 777 /data/local/"
adb shell "echo ro.kernel.qemu=1 > /data/local/local.prop"
adb reboot
adb shell "chmod 777 /data/local/local.prop"
adb shell "mv /data/local/local.prop /data/local.prop"
adb reboot
It's okay if the "adb shell rm" or "adb shell rmdir" commands fail.
To unroot:
Code:
adb shell "rm /data/local.prop"
adb shell "rm /data/local/tmp"
adb shell "mv /data/local/tmp.bak /data/local/tmp"
kgs1992 said:
I agree. Only speculating.
Doesn't TPSparkyRoot work?
Click to expand...
Click to collapse
Never heard of that for the Evo 3D. If you can post a link I'll give it a try if it's compatible with the CDMA Evo 3D. Mostly people are looking for it so they can backup a stock unrooted ROM with Titanium Backup before they root and S-OFF.
ramjet73
ramjet73 said:
Never heard of that for the Evo 3D. If you can post a link I'll give it a try if it's compatible with the CDMA Evo 3D. Mostly people are looking for it so they can backup a stock unrooted ROM with Titanium Backup before they root and S-OFF.
ramjet73
Click to expand...
Click to collapse
Instructions are above. But it needs to be tried on LOCKED S-ON E3D.
Temp root is unstable, the only thing you can see on the phone is the statusbar.
You can't use the phone till temproot is removed, only use adb commands.
You can probably adb pull /data & restore it later.
kgs1992 said:
Instructions are above. But it needs to be tried on LOCKED S-ON E3D.
Temp root is unstable, the only thing you can see on the phone is the statusbar.
You can't use the phone till temproot is removed, only use adb commands.
You can probably adb pull /data & restore it later.
Click to expand...
Click to collapse
I'm out of thanks right now, but appreciate your posting that.
Being S-OFF already via JuopunutBear I'm not as anxious to try it since it requires going back to S-ON, but maybe someone who is currently S-ON on an Evo 3D would be willing to test. I'm assuming that it shouldn't matter if the phone is a GSM or CDMA model based on the commands above.
ramjet73
ramjet73 said:
I'm out of thanks right now, but appreciate your posting that.
Being S-OFF already via JuopunutBear I'm not as anxious to try it since it requires going back to S-ON, but maybe someone who is currently S-ON on an Evo 3D would be willing to test. I'm assuming that it shouldn't matter if the phone is a GSM or CDMA model based on the commands above.
ramjet73
Click to expand...
Click to collapse
Yes, that's right, it doesn't matter.
That is basically the TPSparkyRoot exploit, but I've modified it slightly.
Hope it does work.
If it doesn't, whoever tries it, please post the error message.
kgs1992 said:
I agree. Only speculating.
Doesn't TPSparkyRoot work?
Try this:
To root:
Code:
adb shell "rm /data/local/tmp.orig"
adb shell "mv /data/local/tmp /data/local/tmp.orig"
adb shell "rmdir /data/local/tmp"
adb shell "ln -s /data /data/local/tmp"
adb shell "rm /data/local.prop"
adb shell "chmod 777 /data/local/"
adb shell "echo ro.kernel.qemu=1 > /data/local/local.prop"
adb reboot
adb shell "chmod 777 /data/local/local.prop"
adb shell "mv /data/local/local.prop /data/local.prop"
adb reboot
It's okay if the "adb shell rm" or "adb shell rmdir" commands fail.
To unroot:
Code:
adb shell "rm /data/local.prop"
adb shell "rm /data/local/tmp"
adb shell "mv /data/local/tmp.bak /data/local/tmp"
Click to expand...
Click to collapse
i am willing to test this.i have gsm evo 3d with hboot 1.5(OTA ICS),LOCKED S-ON.but i have some questions:
1)when i execute those commands should i be in fastboot usb or just connect the phone in charging mode and with usb debugging checked?
2)if i sucesfully temp root what can i do in order to perm root my phone?
THANKS!!!
johnmarshton said:
i am willing to test this.i have gsm evo 3d with hboot 1.5(OTA ICS),LOCKED S-ON.but i have some questions:
1)when i execute those commands should i be in fastboot usb or just connect the phone in charging mode and with usb debugging checked?
2)if i sucesfully temp root what can i do in order to perm root my phone?
THANKS!!!
Click to expand...
Click to collapse
1) adb access required. Hence, charging mode with USB Debugging enabled.
2) You cannot permanently root without an unlocked bootloader or S-OFF.
kgs1992 said:
1) adb access required. Hence, charging mode with USB Debugging enabled.
2) You cannot permanently root without an unlocked bootloader or S-OFF.
Click to expand...
Click to collapse
then,if i succesfully obtain temp root,what can i do?can i unlock my bootloader,downgrade hboot?what can i do?thanks!
johnmarshton said:
then,if i succesfully obtain temp root,what can i do?can i unlock my bootloader,downgrade hboot?what can i do?thanks!
Click to expand...
Click to collapse
Very little. You can probably make backup of your data.
You can get root access via adb shell. But what you can do is limited.
The most this will establish is whether or not the E3D can be temprooted or not.
kgs1992 said:
Very little. You can probably make backup of your data.
You can get root access via adb shell. But what you can do is limited.
The most this will establish is whether or not the E3D can be temprooted or not.
Click to expand...
Click to collapse
Could he push an "su" binary to the system partition while he has temp root?
ramjet73
i have unlocked international htc one max by htcdev
i have vipermax 1.0.1 rom
my hboot is 2.49.0000
i wanna to s-off it but i can not understand the steps of using firewater from here
http://forum.xda-developers.com/showthread.php?t=2632385
i dont understand what this mean
Push, Prepare, and Execute firewater:
adb reboot <–important!!!!
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
what is this? where to but the firwater file? what should i do after?
the commands are shell comands
make sure you have fastboot, adb and firewater files all in the same folder.
hold shift and right click the folder you have the files and choose command promt here
this is where you'll type the commands
ps dont know it soff works with hboot 2.49. and i did it with a stock rom.
try and see
Quote "ps dont know it soff works with hboot 2.49. and i did it with a stock rom"
It works, I've already S-Off on my Verizon One Max
what command exactly should i write in fastboot cmd to make firewater work?
rowihel2012 said:
what command exactly should i write in fastboot cmd to make firewater work?
Click to expand...
Click to collapse
It wont work in fastboot mode, You need to follow the instructions while you are in Android. Plus make sure you have USB Debbuging on.
adb reboot <–important!!!!
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
Follow these commands, except typing wait-for-device. I mean wait for device, but do not type it. You would enter adb push /data/local/tmp
i did this
adb reboot
the phone reboot but i didn't know what to write after that
rowihel2012 said:
i did this
adb reboot
the phone reboot but i didn't know what to write after that
Click to expand...
Click to collapse
After you reboot you write these cammands:
adb push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
wow i did it
is their any step after your devise now is s off? gave us your money?
=========================================================
Yes you should send them all your money ?
Is there any easy tool to do this for those noobs?
ferdie553 said:
Is there any easy tool to do this for those noobs?
Click to expand...
Click to collapse
Ummm.. How much easier can it get? Don't mean to be an ass but if you don't think this is easy get an windows phone or an iPhone.
Sent from my HTC0P3P7 using xda app-developers app
ferdie553 said:
Is there any easy tool to do this for those noobs?
Click to expand...
Click to collapse
That's as easy as these tools get lol
Sent from my HTC6525LVW using XDA Premium 4 mobile app
hi all
i restore my htc one max (international) & returned the original recovery but how i can remove the warning?
Please help!!!
bumet3eb said:
hi all
i restore my htc one max (international) & returned the original recovery but how i can remove the warning?
Please help!!!
Click to expand...
Click to collapse
I believe you need to be S-OFF then go here: http://forum.xda-developers.com/showthread.php?t=2540004
JBS976 said:
I believe you need to be S-OFF then go here: http://forum.xda-developers.com/showthread.php?t=2540004
Click to expand...
Click to collapse
Please Advice
bumet3eb said:
hi all
i restore my htc one max (international) & returned the original recovery but how i can remove the warning?
Please help!!!
Click to expand...
Click to collapse
you need soff. use firewater.. this will remove the tampered banner.
then you can unlock and lock(not relock) using scotty123's method.
all info is on this site, already been talked about.
scotty123's method:
soff and at least an unsecured kernel are needed
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
Hi.I have two problems !!! First I have HTC one max and i have rooted the phone. but after the root the fingerprint is not working anymore. And my second problem is that when i try to install OTA (lollipop update) the phone download the software but when the phone install it at about 20% it shows error ( red exclamation mark ) and i got the update failed to install.
I have original recovery and i don't know what to do !!
Have to relock boot loader for finger print scanner to work. There's a thread in dev on how to do that. I think you have to be stock to take the ota tho, might have to do an ruu. Should just s-off if possible, install twrp and relock boot loader and get the stock Rom in dev.
Tenounce said:
Have to relock boot loader for finger print scanner to work. There's a thread in dev on how to do that. I think you have to be stock to take the ota tho, might have to do an ruu. Should just s-off if possible, install twrp and relock boot loader and get the stock Rom in dev.
Click to expand...
Click to collapse
I got stock rom with rooted and relocked bootloader
Does your boot loader show "Locked" or "relocked"?
These are the instructions flyhalf posted that I originally used back when I first got the phone and had the same problem with the fingerprint scanner
1.) Fingerprint scanner not working....
Check to make sure your bootloader says "LOCKED" not relocked
if not do this
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
adb reboot bootloader
verify you are now locked
Tenounce said:
Does your boot loader show "Locked" or "relocked"?
These are the instructions flyhalf posted that I originally used back when I first got the phone and had the same problem with the fingerprint scanner
1.) Fingerprint scanner not working....
Check to make sure your bootloader says "LOCKED" not relocked
if not do this
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
adb reboot bootloader
verify you are now locked
Click to expand...
Click to collapse
Any way of doing this through fastboot? My phone is in a boot loop and it wont boot up no matter what I do. It has RELOCKED on it with s-off but maybe unlocking it or locking it could help me finally boot it up.
I don't think it can be done in fastboot but I could be wrong. I read your op. Since you say everything seems to flash fine have you tried flashing different firmware?
Tenounce said:
Does your boot loader show "Locked" or "relocked"?
These are the instructions flyhalf posted that I originally used back when I first got the phone and had the same problem with the fingerprint scanner
1.) Fingerprint scanner not working....
Check to make sure your bootloader says "LOCKED" not relocked
if not do this
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
adb reboot bootloader
verify you are now locked
Click to expand...
Click to collapse
Will this work with S-ON ????? Because i have S-ON and it didn't work with me
kareim1 said:
Will this work with S-ON ????? Because i have S-ON and it didn't work with me
Click to expand...
Click to collapse
It should but you need to unlock again first
Tenounce said:
It should but you need to unlock again first
Click to expand...
Click to collapse
Well it didn't work.... Is there any other solution ??