I recently discovered this, and I thought it would be of some benefit to those who are wanting to unlock, modify partitions, etc without the need to flash derpunlock.sbf or modify your photon in any way. What you need to do this:
1) fastboot for Windows or Linux
2) unlocked RDL3 (ramloader) which I am providing
The process is very simple, reboot your Motorola Photon, and hold the volume down button and power button. You will see "fastboot" on the screen, now press volume up. Connect your phone to your computer, and issue the following command which I discovered:
[email protected]:~$ fastboot flash rdl.bin RDL3_unlocked.smg
sending 'rdl.bin' (3072 KB)...
OKAY [ 0.193s]
writing 'rdl.bin'...
OKAY [ 0.000s]
finished. total time: 0.193s
This will load the unlocked ramloader (unlocked will be displayed at the top even if your phone is locked) which is normally only loaded into ram when flashing an SBF! Amazing, I know. Now you can do all kinds of stuff and you've made no modifications, just issue a "fastboot reboot" and nothing has been modified. Now you are able to erase boot, recovery, oem unlock, etc. Here is an example after you have executed the above. This is just me restoring my default boot and recovery partitions which you can't do from your locked bootloader:
[email protected]:~$ fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.739s]
finished. total time: 0.739s
[email protected]:~/Desktop/SMG$ fastboot flash recovery CG58_0x00000120.smg sending 'recovery' (8192 KB)...
OKAY [ 8.760s]
writing 'recovery'...
OKAY [ 1.013s]
finished. total time: 9.773s
[email protected]:~/Desktop/SMG$ fastboot erase boot
erasing 'boot'...
OKAY [ 0.761s]
finished. total time: 0.761s
[email protected]:~/Desktop/SMG$ fastboot flash boot CG59_0x00000130.smg
sending 'boot' (8192 KB)...
OKAY [ 8.800s]
writing 'boot'...
OKAY [ 0.697s]
finished. total time: 9.497s
good progress on it
You can actually unlock the radio with the stock locked bootloader still in place (derpunlock.sbf flashing no longer needed):
[email protected]:~/Desktop/SMG_derpunlock$ fastboot flash rdl.bin RDL3_unlocked.smg
sending 'rdl.bin' (3072 KB)...
OKAY [ 0.193s]
writing 'rdl.bin'...
OKAY [ 0.000s]
finished. total time: 0.193s
[email protected]:~/Desktop/SMG_derpunlock$ fastboot oem unlock
...
(bootloader) Unlocking your device can permanently VOID your warranty.
(bootloader) This process cannot be reversed. If you wish to proceed,
(bootloader) reissue the unlock OEM command containing the unique ID
(bootloader) of your device: XXXXXXXXXXXXXXXX
OKAY [ 0.006s]
finished. total time: 0.006s
[email protected]:~/Desktop/SMG_derpunlock$ fastboot oem unlock XXXXXXXXXXXXXXXX
...
(bootloader) Device is already unlocked
OKAY [ 0.003s]
finished. total time: 0.003s
[email protected]:~/Desktop/SMG_derpunlock$
4G ?
Has anyone tried this method and retained 4G?
scottgl9 said:
You can actually unlock the radio with the stock locked bootloader still in place (derpunlock.sbf flashing no longer needed):
[email protected]:~/Desktop/SMG_derpunlock$ fastboot flash rdl.bin RDL3_unlocked.smg
sending 'rdl.bin' (3072 KB)...
OKAY [ 0.193s]
writing 'rdl.bin'...
OKAY [ 0.000s]
finished. total time: 0.193s
[email protected]:~/Desktop/SMG_derpunlock$ fastboot oem unlock
...
(bootloader) Unlocking your device can permanently VOID your warranty.
(bootloader) This process cannot be reversed. If you wish to proceed,
(bootloader) reissue the unlock OEM command containing the unique ID
(bootloader) of your device: XXXXXXXXXXXXXXXX
OKAY [ 0.006s]
finished. total time: 0.006s
[email protected]:~/Desktop/SMG_derpunlock$ fastboot oem unlock XXXXXXXXXXXXXXXX
...
(bootloader) Device is already unlocked
OKAY [ 0.003s]
finished. total time: 0.003s
[email protected]:~/Desktop/SMG_derpunlock$
Click to expand...
Click to collapse
what would be the process coming from locked stock _6, would i just flash clock work mod, flash rom.zip then OP's inputs?
bigslanki said:
what would be the process coming from locked stock _6, would i just flash clock work mod, flash rom.zip then OP's inputs?
Click to expand...
Click to collapse
The process of loading the unlocked ramloader is the same regardless of your firmware, even if the bootloader is 'locked'. The ramloader is just that, its written to ram, and so when the phone is reset the code is cleared out of memory. This means to unlock your radio, you don't have to flash anything to your ram, flashing rdl.bin basically just loads the ramloader to executable memory, then jumps to it. I'm still working on figuring out how to use this to chain load a custom recovery.
Love this! Keep up the good work!
So can I flash CWM after this kind of unlock the bootloader and then custom rom.
Sent from my SPH-D710 using XDA
Will this be useful for the ones that flash the electrify rom on the photon?
Sent from my MB855 using XDA
may you attach stock recovery here? thanks
rrusek said:
Has anyone tried this method and retained 4G?
Click to expand...
Click to collapse
+1
4G confirmed working or not?
I like what I m reading. Sounds like this would be the saving grace for those photon users stuck on an electrify rom (and yeah I m one of them!). Please let us know when you get to rewrite system with a custom rom with this method!
dito33 said:
So can I flash CWM after this kind of unlock the bootloader and then custom rom.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Not yet, you can flash it but it is not yet bootable since I haven't figured out yet how to jump to recovery from the ramloader (you'll probably get an error 2 if you flash CWM then boot to recovery). After you reset your phone, rdl.bin gets cleared out so the same protection mechanisms are still in the bootloader. It's something I'm working on.
firtermish said:
I like what I m reading. Sounds like this would be the saving grace for those photon users stuck on an electrify rom (and yeah I m one of them!). Please let us know when you get to rewrite system with a custom rom with this method!
Click to expand...
Click to collapse
I already can. just do the following:
fastboot flash rdl.bin RDL3_unlocked.smg
fastboot erase system
fastboot flash system your_system_file.smg
fastboot erase boot
fastboot flash boot your_boot.smg
fastboot reboot
EDIT: file extension doesn't really matter, can be smg or img
Theres also updating from fastboot using a zip file, I'm not 100% sure if this works the same as in recovery:
update <filename> reflash device from update.zip
jortiz12885 said:
Will this be useful for the ones that flash the electrify rom on the photon?
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Nope. I just tried and it doesn't work. I get error on phone like below.
1c10d60
SVF:106:1:2
sec_exception: b655, eddc, eb
Anyone knows what that is?
herach said:
Nope. I just tried and it doesn't work. I get error on phone like below.
1c10d60
SVF:106:1:2
sec_exception: b655, eddc, eb
Anyone knows what that is?
Click to expand...
Click to collapse
At what point did you receive the error?
scottgl9 said:
At what point did you receive the error?
Click to expand...
Click to collapse
After the Fastboot. It does Fastboot successfully but it gives the error on the phone screen.
herach said:
After the Fastboot. It does Fastboot successfully but it gives the error on the phone screen.
Click to expand...
Click to collapse
It looks like it is some sort of security error(possibly a failed sigcheck or something).
Lightsword1942 said:
It looks like it is some sort of security error(possibly a failed sigcheck or something).
Click to expand...
Click to collapse
I'm pretty sure the reason you're receiving this error is because this RDL is from derpunlock.sbf from photon_pudding.rar. I'll post the unlocked pudding electrify ramloader.
Attached is the unlocked pudding electrify ramloader, run:
fastboot flash rdl.bin RDL3_unlocked_electrify.smg
scottgl9 said:
I'm pretty sure the reason you're receiving this error is because this RDL is from derpunlock.sbf from photon_pudding.rar. I'll post the unlocked pudding electrify ramloader.
Attached is the unlocked pudding electrify ramloader, run:
fastboot flash rdl.bin RDL3_unlocked_electrify.smg
Click to expand...
Click to collapse
Tried that. It reboots the device and the device stays on Moto Logo Dual-core Screen with nothing written on it and nothing else works.
Related
I had niles business rom on my phone and it kept messing up on me. so i downloaded the toolkit for s-off. After many tries i was able to get s-off. Now here is where my problem is there is no recovery on my phone now and when i try and do a fastboot in the cmd for my phone it will not write the Amon Ra recovery file. I now get this.
C:\Android\sdk-tools>fastboot flash boot boot.img
sending 'boot' (3896 KB)... OKAY [ 0.814s]
writing 'boot'... FAILED (remote: not allowed)
finished. total time: 1.130s
what should i do?
eggbert81 said:
I had niles business rom on my phone and it kept messing up on me. so i downloaded the toolkit for s-off. After many tries i was able to get s-off. Now here is where my problem is there is no recovery on my phone now and when i try and do a fastboot in the cmd for my phone it will not write the Amon Ra recovery file. I now get this.
C:\Android\sdk-tools>fastboot flash boot boot.img
sending 'boot' (3896 KB)... OKAY [ 0.814s]
writing 'boot'... FAILED (remote: not allowed)
finished. total time: 1.130s
what should i do?
Click to expand...
Click to collapse
So your trying to flash it as a boot.img? Amon Ra should be flashed as fastboot flash recovery recovery.img. Also if your on stock HBoot i think you need a modified HBoot for fastboot commands or unlocked eve on S-Off
sorry should have been
C:\Users\jamie\Desktop\Fastboot>fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
sending 'recovery' (7078 KB)... OKAY [ 1.426s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.742s
eggbert81 said:
sorry should have been
C:\Users\jamie\Desktop\Fastboot>fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
sending 'recovery' (7078 KB)... OKAY [ 1.426s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.742s
Click to expand...
Click to collapse
Do you have a stock HBoot? if so i think it has to be unlocked for fastboot commands even on s-off unless you have a modified Hboot that allows for fastboot commands while locked.
jon7701 said:
So your trying to flash it as a boot.img? Amon Ra should be flashed as fastboot flash recovery recovery.img. Also if your on stock HBoot i think you need a modified HBoot for fastboot commands or unlocked eve on S-Off
Click to expand...
Click to collapse
i was reading about flashing the boot image so i also tried to take the boot.img out of CleanROM Standard 4.5 and tried to flash the boot and that didnt work either
i do have s-off and i can get my phone to say FASTBOOT USB but everything i try and write to it says sending OKAY then writing FAILED ( remote: not allowed)
eggbert81 said:
i was reading about flashing the boot image so i also tried to take the boot.img out of CleanROM Standard 4.5 and tried to flash the boot and that didnt work either
i do have s-off and i can get my phone to say FASTBOOT USB but everything i try and write to it says sending OKAY then writing FAILED ( remote: not allowed)
Click to expand...
Click to collapse
Well if your bootloader is locked i would unlock it or get a modified bootloader that allows fastboot commands while locked. If those dont work then youll have to ask a dev
somehow i didnt even notice that was locked. ok got recovery on. now going to try and get a rom on it. with all this headache i almost miss my GNex but it has tons of issues
eggbert81 said:
somehow i didnt even notice that was locked. ok got recovery on. now going to try and get a rom on it. with all this headache i almost miss my GNex but it has tons of issues
Click to expand...
Click to collapse
Glad i could help :highfive:
got it all to work. Thanks
eggbert81 said:
got it all to work. Thanks
Click to expand...
Click to collapse
i didt understand much
still a newbie
first how do u know if the bootloader is locked or not
and how did u workout the problem
im having the same issue please help
& thnx:good:
When your in bootloader there will be a big pink highlight that says locked or unlocked
Sent from my ADR6425LVW using xda app-developers app
Deleted
Hi
I want Going back to stock for official Jelly Bean update and I followed this tutorial:
http://forum.xda-developers.com/showthread.php?p=36138808 # post36138808
I try to flash the recovery with the attached file: http://forum.xda-developers.com/showpost.php?p=35031493&postcount=25
fastboot flash recovery recovery.img
sending 'recovery' (4272 KB)...
OKAY [ 1.813s]
writing 'recovery'...
OKAY [ 1.609s]
finished. total time: 3.422s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.531s]
finished. total time: 0.531s
fastboot erase cache
erasing 'cache'...
OKAY [ 0.266s]
finished. total time: 0.266s
When I returned to the fastboot and I select "recovery" the phone gets stuck on the following picture: http://s13.postimage.org/6hy5sfs2f/IMG_20120530_193934_1.jpg (photo found on google on another device)
This is my configuration :
Desire X
--> Bootloader unlocked
PROTO PVT SHIP S-ON RL
HBOOT-1.24.0000
RADIO-1.12.40.03
eMMC-boot
Oct 30 2012,20:09:09
Android : 4.0.4
HTC sense 4.1
N° 1.18.401.3
API HTC SDK : 4.24
HTCExtension_403_1_GA_24
Kernel :
3.0.21-g6c11713
[email protected]#1
Radio : 10.21.40.06U_1.12.40.03
Build : 1.18.401.3 CL128557 release-keys
Anyone know why my recovery doesn't work ?
Have you tried another another links for recovery? or the one from hansoons kit?
you could have just bad luck and flash buggy one
btw your question is wrong, from what you said, recovery was flashed in ok way, so there must be something wrong with recovery you flashed
Eliastux said:
I want Going back to stock for official Jelly Bean update
I try to flash the recovery with the attached file: http://forum.xda-developers.com/showpost.php?p=35031493&postcount=25
When I returned to the fastboot and I select "recovery" the phone gets stuck on the following picture: http://s13.postimage.org/6hy5sfs2f/IMG_20120530_193934_1.jpg (photo found on google on another device)
Anyone know why my recovery can not be flashed?
Click to expand...
Click to collapse
Your recovery is flashed fine.
But why do you need to go to fastboot and recovery again when your aim is getting the JB update ?
Thank you for this quick answer !
mindlesSheep said:
Have you tried another another links for recovery? or the one from hansoons kit?
you could have just bad luck and flash buggy one
Click to expand...
Click to collapse
Okey I have tried this one :
http://forum.xda-developers.com/attachment.php?attachmentid=1618686&d=1357387592
fastboot.exe flash recovery stock_recovery.img
sending 'recovery' (4272 KB)...
OKAY [ 1.297s]
writing 'recovery'...
OKAY [ 1.641s]
finished. total time: 2.938s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.250s]
finished. total time: 0.250s
fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.648s]
finished. total time: 0.650s
--> When I returned to the fastboot and I select "recovery" and now I see the same picture : http://s13.postimage.org/6hy5sfs2f/I...0_193934_1.jpg
And after 5 sec the phone reboot : Is it normal ?
mindlesSheep said:
btw your question is wrong, from what you said, recovery was flashed in ok way, so there must be something wrong with recovery you flashed
Click to expand...
Click to collapse
Ok I will edit my first post
mindlesSheep said:
or the one from hansoons kit?
Click to expand...
Click to collapse
Ok I try this immediately
ckpv5 said:
Your recovery is flashed fine.
But why do you need to go to fastboot and recovery again when your aim is getting the JB update ?
Click to expand...
Click to collapse
When I want to apply the Jelly Bean 2.20.401.5 update the phone reboot on the buggy recovery and the phone gets stuck on the same picture
ckpv5 said:
Your recovery is flashed fine.
But why do you need to go to fastboot and recovery again when your aim is getting the JB update ?
Click to expand...
Click to collapse
I thought I had to go back to stock recovery for the update of Jelly Bean I'm wrong?
Am I also wrong about the fact that we can apply the update without relock the bootloader?
Eliastux said:
I thought I had to go back to stock recovery for the update of Jelly Bean I'm wrong?
Am I also wrong about the fact that we can apply the update without relock the bootloader?
Click to expand...
Click to collapse
1. Must have stock recovery installed
2. Must have a complete stock ROM (nothing is deleted)
3. Not necessary to flash a stock boot.img but it is advisable to have one
4. Not necessary to relock bootloader
5. If no.4 still brings problem then relock the bootloader but you will lose all data when unlocking again.
Eliastux said:
Okey I have tried this one :
http://forum.xda-developers.com/attachment.php?attachmentid=1618686&d=1357387592
fastboot.exe flash recovery stock_recovery.img
sending 'recovery' (4272 KB)...
OKAY [ 1.297s]
writing 'recovery'...
OKAY [ 1.641s]
finished. total time: 2.938s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.250s]
finished. total time: 0.250s
fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.648s]
finished. total time: 0.650s
--> When I returned to the fastboot and I select "recovery" and now I see the same picture : http://s13.postimage.org/6hy5sfs2f/I...0_193934_1.jpg
And after 5 sec the phone reboot : Is it normal ?
Click to expand...
Click to collapse
--> When I apply the update with this recovery, the phone boot on the recovery and I see the same picture and after 5 sec the phone shut down (no picture on the screen)... and the only way to boot after this is to remove/put the battery.
ckpv5 said:
1. Must have stock recovery installed
2. Must have a complete stock ROM (nothing is deleted)
3. Not necessary to flash a stock boot.img but it is advisable to have one
4. Not necessary to relock bootloader
5. If no.4 still brings problem then relock the bootloader but you will lose all data when unlocking again.
Click to expand...
Click to collapse
1 --> NOK
2 --> OK
3 --> I have to install first a stock recovery if I want to flash a stock boot.img...
4,5 --> OK not necessary
Thanks for your reply
Eliastux said:
or the one from hansoons kit?
Ok I try this immediately
Click to expand...
Click to collapse
I've tried to install TWRP 2.4.3.0 from the HTC Desire X All-In-One Kit (Hasoons kit) :
(I made it with command line because v2.1 of this tool is a little buggy :
astboot.exe flash recovery TWRP.img
< waiting for device >
sending 'recovery' (6158 KB)...
OKAY [ 5.680s]
writing 'recovery'...
OKAY [ 6.375s]
finished. total time: 12.055s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.563s]
finished. total time: 0.563s
fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 1.834s]
finished. total time: 1.874s
--> When I returned to the fastboot and I select "recovery" and now I see the same picture !! ( the phone gets stuck ! )
Is the recovery of my phone bricked ?
Ok guys I found the solution ( after 4hours of research ! ) flashing my phone with this RUU : RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed.exe
Unfortunately (grr) I was not able to use the RUU normally (maybe because my recovery was buggy, I had a signature error) and I follow theses steps to install it :
1) fastboot erase cache
2) fastboot oem rebootRUU
3) fastboot flash zip rom.zip --> the rom.zip was extracted from the RUU.exe
4) fastboot reboot-bootloader
5) fastboot reboot
After that I could make two consecutive updates ( 1.18.401.3 and Jelly Bean update )
I hope it can help others who have the same problem :good:
I am unable to get out of bootloader loop. The phone was already not able to boot into the bone stock rom, so i thought I would try to flash a custom recovery and install a custom rom.
After applying the token, the phone won't unlock bootloader.
C:\Amaze>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.146s]
writing 'unlocktoken'...
(bootloader) unlock token check success
OKAY [ 0.011s]
finished. total time: 0.161s
But nothing happens on the phone! Still says **LOCKED** on top. Also wierd enough says S-OFF!
But as I can't unlock bootloader, can't flash anything. It keeps rebooting into the bootloader on reboot, power off, and restart via fastboot command.
The phone is from Wind Mobile Canada, and there is no ICS -based RUU for it.
Thoughts?
SaHiLzZ said:
I am unable to get out of bootloader loop. The phone was already not able to boot into the bone stock rom, so i thought I would try to flash a custom recovery and install a custom rom.
After applying the token, the phone won't unlock bootloader.
C:\Amaze>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.146s]
writing 'unlocktoken'...
(bootloader) unlock token check success
OKAY [ 0.011s]
finished. total time: 0.161s
But nothing happens on the phone! Still says **LOCKED** on top. Also wierd enough says S-OFF!
But as I can't unlock bootloader, can't flash anything. It keeps rebooting into the bootloader on reboot, power off, and restart via fastboot command.
The phone is from Wind Mobile Canada, and there is no ICS -based RUU for it.
Thoughts?
Click to expand...
Click to collapse
try a new token? or since your s off simply run a ruu
Hi, guys I have a HOX+, which bricked just now. It seems like the bootloader cannot be fully unlocked. When I flash bootloader unlock_token, it gives this message:
Code:
C:\adb-setup-1.3\adb>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 17.987s
How ever on HBOOT it says the bootloader is unlocked with S-ON, now I flash CM11 the phone just keep stuck at bootloop, already wipe everything. Any idea??? The phone is unusable right now. :crying: Got TWRP, can't boot...
soralz said:
Hi, guys I have a HOX+, which bricked just now. It seems like the bootloader cannot be fully unlocked. When I flash bootloader unlock_token, it gives this message:
Code:
C:\adb-setup-1.3\adb>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 17.987s
How ever on HBOOT it says the bootloader is unlocked with S-ON, now I flash CM11 the phone just keep stuck at bootloop, already wipe everything. Any idea??? The phone is unusable right now. :crying: Got TWRP, can't boot...
Click to expand...
Click to collapse
you have to flash the boot.img in fastboot usb mode!
Thanks, that worked.
Everytime I type the command 'fastboot oem unlock', the screen says;
OKAY [ 0.002s]
finished. total time: 0.002s
but then when I want to flash a recovery it says;
target reported max download size of 1073741824 bytes
sending 'recovery' (15482 KB)...
OKAY [ 0.498s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)<<< Why does this happen? -_-
finished. total time: 0.501s
Anybody has a solution for this?
Have you tried just flashing stock recovery? Does it say that for everything you try and flash? A lot of people are trying these shortcuts to try and upgrade bootloader. Though most can work the safest bet is to flash original stock recovery and upgrade from there. You might be looking at going through the hard brick guide.
seems like you locked the bootloader while you are rooted...iam stack on same step too...
Exodusche said:
Have you tried just flashing stock recovery? Does it say that for everything you try and flash? A lot of people are trying these shortcuts to try and upgrade bootloader. Though most can work the safest bet is to flash original stock recovery and upgrade from there. You might be looking at going through the hard brick guide.
Click to expand...
Click to collapse
But everything else works. And yeah, I did try flashing the stock recovery too
Fastboot oem unlock>fastboot reboot>doesn't ask about wiping
I've followed every tutorial they all say that after requesting oem unlock, you can verify the unlock was successful with fastboot oem devices-info> device tampered-false, device unlock-true, then fastboot reboot> system reboot, but it does NOT ask to wipe the data. Am I missing something?
Ubuntu_noobi said:
I've followed every tutorial they all say that after requesting oem unlock, you can verify the unlock was successful with fastboot oem devices-info> device tampered-false, device unlock-true, then fastboot reboot> system reboot, but it does NOT ask to wipe the data. Am I missing something?
Click to expand...
Click to collapse
Not necessarly.
If it 's device unlock-true , you're OK. If not...