I'm trying to read device id with a "fastboot oem get_unlock_data" command to unlock bootloader, but nothing. I followed all the instructions with installing adb drivers, android sdk and motorola drivers,and I just can't get it working. Did everything it said on motorola site.
!!!!
Darezi said:
I'm trying to read device id with a "fastboot oem get_unlock_data" command to unlock bootloader, but nothing. I followed all the instructions with installing adb drivers, android sdk and motorola drivers,and I just can't get it working. Did everything it said on motorola site.
Click to expand...
Click to collapse
are you drunk?:cyclops:
Except development version, others all can't unlock bootloader...
Sent from my RAZR using xda app-developers app
mirot said:
are you drunk?:cyclops:
Click to expand...
Click to collapse
lol
Sent from my XT910 using Tapatalk 2
LMAO
Darezi said:
I'm trying to read device id with a "fastboot oem get_unlock_data" command to unlock bootloader, but nothing. I followed all the instructions with installing adb drivers, android sdk and motorola drivers,and I just can't get it working. Did everything it said on motorola site.
Click to expand...
Click to collapse
Well the man does have dreams...
Moved To Q&A
Not in the dev section
Related
With a little modding, I was able to get ROMRacer's Atrix recovery console working on the Photon, I PM'd him letting him know the change that needs to be made for it to work, so if he post a thread over here, I will close this one.
So for the time being, here's a true CWM recovery console for the Photon.
I chose the blue version for this but I imagine that if ROMRacer makes a thread, he will post the other colors also.
And as the title states, THIS IS ONLY FOR UNLOCKED PHONES
Install instructions
Extract the zip, put the recovery.img in the same directory as adb and get the phone into fastboot mode the same way you did to unlock it
And type this
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Calkulin said:
With a little modding, I was able to get ROMRacer's Atrix recovery console working on the Photon, I PM'd him letting him know the change that needs to be made for it to work, so if he posted a thread over here, I will close this one.
So for the time being, here's a true CWM recovery console for the Photon.
I chose the blue version for this but I imagine that if ROMRacer makes a thread, he will post the other colors also.
And as the title states, THIS IS ONLY FOR UNLOCKED PHONES
Install instructions
Extract the zip, put the recovery.img in the same directory as adb and get the phone into the fastboot mode the same way you did to unlock it
And type this
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
you effin rock dood!!!
Today is the best day for the Motorola Photon!
Thank you Mr. Calkulin! Its awesome seeing you over here @ the Photon deck! Welcome aboard my friend! The best of the best and he's right here folks! Am I excited? Uum ... yes I am!
Hold on while I do my happy dance...
Hey Calkulin I have been waiting for you to do an all-in-one(radio,wimax,pri,prl) for my EVO 3D. Glad to see you here too. Thanks you for your work.
Hey calk good to see you moved on to the photon. Thanx for the post.
Flashing now. Thanks Calkulin!!
Sent from my MB855 using XDA App
When I type "fastboot erase recovery" adb sits on <waiting for device> what am I forgetting? It's been a long night!
Try moto-fastboot
anti-up said:
When I type "fastboot erase recovery" adb sits on <waiting for device> what am I forgetting? It's been a long night!
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
anti-up said:
When I type "fastboot erase recovery" adb sits on <waiting for device> what am I forgetting? It's been a long night!
Click to expand...
Click to collapse
make sure debugging is enabled then run the command fastboot devices to make sure fastboot is seeing yours
Yay 4 Juggs said:
make sure debugging is enabled then run the command fastboot devices to make sure fastboot is seeing yours
Click to expand...
Click to collapse
got into fastboot, typed fastboot devices and it shows my device. When I type 'fastboot erase recovery' it says erasing recovery then FAILED <remote: <00180001>>
anti-up said:
got into fastboot, typed fastboot devices and it shows my device. When I type 'fastboot erase recovery' it says erasing recovery then FAILED <remote: <00180001>>
Click to expand...
Click to collapse
then you're not unlocked...
Do I put this file in the tools folder or just the adb folder?
aaron130 said:
Do I put this file in the tools folder or just the adb folder?
Click to expand...
Click to collapse
depending on your setup it would go in the same directory as fastboot
How do you know if you're unlocked or not?
Sent from my MB855 using Tapatalk
Yay 4 Juggs said:
then you're not unlocked...
Click to expand...
Click to collapse
when I type su I get the $ sign and a msg. to allow permissions then a msg. saying terminal emulator has been granted superuser permissions. I have the bootstrap recovery installed and created a backup already...I'm pretty sure I'm unlocked. I just cant get this recovery to install for some reason...UGH!!!!
Being rooted and being unlockes are 2 different things
anti-up said:
when I type su I get the $ sign and a msg. to allow permissions then a msg. saying terminal emulator has been granted superuser permissions. I have the bootstrap recovery installed and created a backup already...I'm pretty sure I'm unlocked. I just cant get this recovery to install for some reason...UGH!!!!
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
mikeyinid said:
Being rooted and being unlockes are 2 different things
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Ahhh gotcha....thanks. Back to work
If you follow Yays instructions in his thread you will be both rooted and unlocked.
anti-up said:
Ahhh gotcha....thanks. Back to work
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Just want to say thanks! Now I have a rooted and unlocked phone that's not gimmicky. Now for the overclocking...
Sent from my MB855 using XDA App
Worked perfectly. Thanks!
Sent from my UNLOCKED Photon 4G using the XDA App for Android
( i admit i am a noob at this stuff) I bought this rezound from a guy, and i came home and downloaded the Rezound All-In-One kit, i installed the htc drivers registered at htcdev. I tried to get token ID.. didnt work, and i tried to do the ICS leak and followed the instructions exactly... didnt work.. well i looked at my phone while in bootloader and it said unlocked, i tried running the All-in-one kit "Relock Bootloader" command and it still doesnt work. in command prompt it says ( Rezound_All-In-One_Kit_v2.0\data>fastboot oem lock
< waiting for device >
and thats it.. doesnt do anything else.. can someone please help me re-lock this phone.
First, try doing the above again, only uninstall/disable HTC sync this time. Report back if it doesn't work. Also, why do you wish to relock?
rabidwookie said:
( i admit i am a noob at this stuff) I bought this rezound from a guy, and i came home and downloaded the Rezound All-In-One kit, i installed the htc drivers registered at htcdev. I tried to get token ID.. didnt work, and i tried to do the ICS leak and followed the instructions exactly... didnt work.. well i looked at my phone while in bootloader and it said unlocked, i tried running the All-in-one kit "Relock Bootloader" command and it still doesnt work. in command prompt it says ( Rezound_All-In-One_Kit_v2.0\data>fastboot oem lock
< waiting for device >
and thats it.. doesnt do anything else.. can someone please help me re-lock this phone.
Click to expand...
Click to collapse
Is your phone in HBOOT when you issue the command? If not, it should be. Fastboot commands only work in HBOOT.
Snuzzo said:
First, try doing the above again, only uninstall/disable HTC sync this time. Report back if it doesn't work. Also, why do you wish to relock?
Click to expand...
Click to collapse
MrSmith317 said:
Is your phone in HBOOT when you issue the command? If not, it should be. Fastboot commands only work in HBOOT.
Click to expand...
Click to collapse
Yeah you're right MrSmith. I looked at the .bat related to re-locking in the A-I-O toolkit and it doesn't invoke "adb reboot bootloader" command before attempting "fasboot oem lock".
I ran into this problem as well. Make sure usb debugging is on. Should work like a charm.
Sent from my ADR6425LVW using xda premium
Fergusonfox7 said:
I ran into this problem as well. Make sure usb debugging is on. Should work like a charm.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Again, its not a matter of having debugging enabled. See my post above.
Sent from my ADR6425LVW using XDA
Try rebooting into HBOOT then unplugging the phone and plugging it back in. Sometimes the device manager(on your PC) doesn't pickup the change in modes. The AIO could just be firing off commands instead of waiting for the phone to be ready as well. Try doing it manually.
Alright, so Yesterday I got my DNA, I've been trying all day yesterday to get the bootloader unlocked. I did the one click method and checked the CID and it is all ones. When I went to HTC dev I'm getting the error of 160. I've done research to see that this is because of the unsupported device and that the exploit failed, yet I'm getting all ones? SOme help and or guiding would be great
Oh and I have tried on my windows 7 desktop and windows 8 laptop.
CinemaGFX said:
Alright, so Yesterday I got my DNA, I've been trying all day yesterday to get the bootloader unlocked. I did the one click method and checked the CID and it is all ones. When I went to HTC dev I'm getting the error of 160. I've done research to see that this is because of the unsupported device and that the exploit failed, yet I'm getting all ones? SOme help and or guiding would be great
Oh and I have tried on my windows 7 desktop and windows 8 laptop.
Click to expand...
Click to collapse
I am getting the exact same error.
From bootloader, run fastboot cmd
fastboot oem writecid 22222222
Then go back to htcdev and start over. Make sure you use a new copy/paste from
fastboot oem get_identifier_token
Sent from my SPH-L710 using Tapatalk 2
18th.abn said:
From bootloader, run fastboot cmd
fastboot oem writecid 22222222
Then go back to htcdev and start over. Make sure you use a new copy/paste from
fastboot oem get_identifier_token
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Or just use the SuperCID app (need to download the new one that got updated)
Sent from my HTC6435LVW using XDA Premium HD app
18th.abn said:
From bootloader, run fastboot cmd
fastboot oem writecid 22222222
Then go back to htcdev and start over. Make sure you use a new copy/paste from
fastboot oem get_identifier_token
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
How do you run fastboot cmd from the bootloader? When i go to bootloader and to fastboot what does run fastboot cmd refer to?
superbl11 said:
How do you run fastboot cmd from the bootloader? When i go to bootloader and to fastboot what does run fastboot cmd refer to?
Click to expand...
Click to collapse
From a terminal on your pc
Sent from my HTC6435LVW using xda app-developers app
18th.abn said:
From bootloader, run fastboot cmd
fastboot oem writecid 22222222
Then go back to htcdev and start over. Make sure you use a new copy/paste from
fastboot oem get_identifier_token
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
You can't just run that command. You need to do the exploit(only works on 1.15)
Sent from my HTC6435LVW using xda app-developers app
Team,
I've searched and tried to relock the bootloader with fastboot oem lock on my MAC and windows through the command prompt and the command is not recognized. I need to reset this damn DNA tonight before I send it back in to Verizon. Please give me a little assistance here. I have the RUU on my desktop also, I just dont know wtf is wrong with the command fastboot oem lock...
Yes I am restarting and chosing fastboot with the phone plugged in..
OverrideJones said:
Team,
I've searched and tried to relock the bootloader with fastboot oem lock on my MAC and windows through the command prompt and the command is not recognized. I need to reset this damn DNA tonight before I send it back in to Verizon. Please give me a little assistance here. I have the RUU on my desktop also, I just dont know wtf is wrong with the command fastboot oem lock...
Yes I am restarting and chosing fastboot with the phone plugged in..
Click to expand...
Click to collapse
Any love?
OverrideJones said:
Any love?
Click to expand...
Click to collapse
there is a thread in the dna android deveolpement forum that has all the info u need.
mopartonyg said:
there is a thread in the dna android deveolpement forum that has all the info u need.
Click to expand...
Click to collapse
There are many threads that I have read through...
when I fastbooted and so forth... I typed in the command box fastboot oem lock and that did nothing.
From what I read, you need to flash the lock boot loader zip to lock it.. Fastboot oem lock command won't work apparently if you have S-offed.
Sent from my DNA
Uzephi said:
From what I read, you need to flash the lock boot loader zip to lock it.. Fastboot oem lock command won't work apparently if you have S-offed.
Sent from my DNA
Click to expand...
Click to collapse
Thanks a lot and where is the lockbootloader zip located at along with the other files?
OverrideJones said:
There are many threads that I have read through...
when I fastbooted and so forth... I typed in the command box fastboot oem lock and that did nothing.
Click to expand...
Click to collapse
Read through this entire guide before you start any of them to make sure you follow the proper one.
http://forum.xda-developers.com/showthread.php?t=2293919
Sent from my dlx using XDA Premium HD app
.torrented said:
Read through this entire guide before you start any of them to make sure you follow the proper one.
http://forum.xda-developers.com/showthread.php?t=2293919
Sent from my dlx using XDA Premium HD app
Click to expand...
Click to collapse
Read this...
what does this mean?
Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice
Whos internal storage? SD card on the phone?
OverrideJones said:
Read this...
what does this mean?
Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice
Whos internal storage? SD card on the phone?
Click to expand...
Click to collapse
Yes. Flash it in a custom recovery
Sent from my Rezound
Uzephi said:
Yes. Flash it in a custom recovery
Sent from my Rezound
Click to expand...
Click to collapse
Are there any places around maryland or northern va who can assist...? I would love to learn the terminology but it took me 4 days to learn how to code on a MAC to perform the dang root lol and not I cant image how long it would take to reverse it.
Uzephi said:
Yes. Flash it in a custom recovery
Sent from my Rezound
Click to expand...
Click to collapse
Which process did u use to achieve s-off and unlock?
Sent from my dlx using xda app-developers app
jaymazz13 said:
Which process did u use to achieve s-off and unlock?
Sent from my dlx using xda app-developers app
Click to expand...
Click to collapse
Mine got given to me s-off.
Sent from my Rezound
What does your hboot say when you boot into bootloader?
Phaded said:
What does your hboot say when you boot into bootloader?
Click to expand...
Click to collapse
It says S-OFF unlocked ...
I do not know the process... I need to be walked through it to be fair. Not to sound incompetent lol
Uzephi said:
Yes. Flash it in a custom recovery
Sent from my Rezound
Click to expand...
Click to collapse
Also, I am using clockwork mod...
What does the ENTIRE thing say?
Phaded said:
What does the ENTIRE thing say?
Click to expand...
Click to collapse
No worries now guys, I suppose now I have to give Verizon a damn good reason as to why my phone was rooted as hell. I have a decent alibi created.
Flash the lock boot loader zip as you would if flashing a ROM.
After that, do the RUU instructions, then s-on (fastboot OEM write secure flag 3). It is pretty simple.
Sent from my Rezound
Uzephi said:
Flash the lock boot loader zip as you would if flashing a ROM.
After that, do the RUU instructions, then s-on (fastboot OEM write secure flag 3). It is pretty simple.
Sent from my Rezound
Click to expand...
Click to collapse
Phone is gone now, however, what I did was...
restart phone, hold down volume blah...
boot loader fast boot and so forth, when fastboot USB popped up on phone on the windows computer open command up and type fastboot oem lock
some sort of error popped up.. so that is where I was. Pardon the english and grammar, had a few Jamesons'
OverrideJones said:
Phone is gone now, however, what I did was...
restart phone, hold down volume blah...
boot loader fast boot and so forth, when fastboot USB popped up on phone on the windows computer open command up and type fastboot oem lock
some sort of error popped up.. so that is where I was. Pardon the english and grammar, had a few Jamesons'
Click to expand...
Click to collapse
You can't lock the boot loader by fastboot commands, you needed to lock it by flashing the lock zip in recovery.
Sent from my Rezound
I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2109862
and on the 3. a. step, it wants you to open Windows CMD and type "fastboot oem readcid". I type this in and the CMD simply says "unknown command" or something similar to that, therefor I am not sure if I unlocked the bootloader or whatever.
mdelzell said:
I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2109862
and on the 3. a. step, it wants you to open Windows CMD and type "fastboot oem readcid". I type this in and the CMD simply says "unknown command" or something similar to that, therefor I am not sure if I unlocked the bootloader or whatever.
Click to expand...
Click to collapse
What firmware are you on? That method won't work on any updated DNAs. Check out rumrunner or firewater. There's also a thread in general called "too late to root" or something like that.
Sent from my HTC6435LVW using xda app-developers app