Related
Failed to boot 2
Starting RSD mode.
I tried to flash the new Ninja Rom from the Gingerblur rom. I am now stuck on the dual core screen with the message above stuck there. Someone please help, I looked through the forms but it seems like I should be able to get into recovery still, which I cannot... If you need any other info please let me know....
rp2gardner said:
Failed to boot 2
Starting RSD mode.
I tried to flash the new Ninja Rom from the Gingerblur rom. I am now stuck on the dual core screen with the message above stuck there. Someone please help, I looked through the forms but it seems like I should be able to get into recovery still, which I cannot... If you need any other info please let me know....
Click to expand...
Click to collapse
Were you unlocked before trying to flash Ninja rom?
unlocked... no at least I dont think? Obviously I was rooted but unlocked i dunno...
That is why, your bootloader has to be unlocked.
Sent from my MB860 using XDA Premium App
rp2gardner said:
unlocked... no at least I dont think? Obviously I was rooted but unlocked i dunno...
Click to expand...
Click to collapse
Ah ok... gingerblur was a pseudo-rom... made before we were able to install custom roms because we couldn't unlock our bootloader. That changed last month when devs figured it out and thus the newer custom roms. To install them you need to unlocked your bootloader.
Please read this thread for information on how to unlock
http://forum.xda-developers.com/showthread.php?t=1136261
Now, since you're already softbricks, running that may not work right now. BUT it's start.
My suggestion- read the thread, follow the instructions and see if that gets you to boot up properly after running the oem unlock.
If not, then download a fresh stock 1.8.3 SBF form the development thread and RSD flash that.
Ok thank you for your help, will post a question if I come to one. How would I download the stock 1.8.3 SBF if I am stuck on the boot screen? Im feeling like Im in over my head, Paypal donation to anyone who can walk me through this....
rp2gardner said:
Ok thank you for your help, will post a question if I come to one. How would I download the stock 1.8.3 SBF if I am stuck on the boot screen? Im feeling like Im in over my head, Paypal donation to anyone who can walk me through this....
Click to expand...
Click to collapse
Stock SBFs are in the development forum as well.
I guess first things first, do you have the tools needed
Do you have or know how to use RSD?
How about Fastboot?
Just downloaded RSD lite and flashed the SBF..
"Open and extract the Fastboot package from above" is the step I am on.. Not sure where to go from here.
The phone rebooted to the same screen that it was at before with the error message but says PASS in RSDLite for the sbf flash
rp2gardner said:
Just downloaded RSD lite and flashed the SBF..
"Open and extract the Fastboot package from above" is the step I am on.. Not sure where to go from here.
The phone rebooted to the same screen that it was at before with the error message but says PASS in RSDLite for the sbf flash
Click to expand...
Click to collapse
Which SBF? The pudding/unlock?
If you flashed the pudding SBF, then you need to do the fastboot steps next.
Did you download and unzip the fastboot package to your computer?
I did, I just dont know what to do with fastboot. Do I run it or what?.. THANKS A TON BY THE WAY...
Ok, I still have the failed to boot 2, but I am now getting the Starting Fastboot protocol support. I dont understand this step..
Type the following command:
fastboot oem unlock
rp2gardner said:
I did, I just dont know what to do with fastboot. Do I run it or what?.. THANKS A TON BY THE WAY...
Click to expand...
Click to collapse
let's say you saved and extracted the fastboot files to c:\fastboot
then you have to open up CMD (start - run - cmd )
then cd to the directory it's saved (in this example c:\fastboot )
Now you have to get your phone into fastboot mode (directions are in the link), but in short, as you turn on your phone, hold the down button. THen it should say fastboot, then hit volume up, should say entering fastboot
Then back on computer in the command window
while your in the fastboot directory
type the oem unlock command (specific command in the instruction).
after it's all done, type fastboot reboot.
I have to go now for a while, but if all that doesn't work. I suggest flashing via RSD the 1.83 SBF with Pudding built in.
The download is in the pudding thread near the top "1. All phones If you have unlocked then try to use 2.3.4 update zip from Motorola servers, then revert back to a "pre-unlock" version(1.8.3 or earlier on ATT) you will get bricked! Do not use the OTA via experimental servers and revert to older versions WITHOUT pudding preinstalled in your sbf.
ATT ONLY Get your 1.8.3 with pudding from gitbrew or multiupload."
I cant figure out where to type the command in (fastboot oem unlock) i have the screen that came up when i located the fastboot. It has a list of commands, but nothing about oem unlock...
rp2gardner said:
I cant figure out where to type the command in (fastboot oem unlock) i have the screen that came up when i located the fastboot. It has a list of commands, but nothing about oem unlock...
Click to expand...
Click to collapse
Is your phone in fastboot mode and connected?
All you gotta do is just type the command in the command window
C:\fastboo\ fastboot oem unlock
can i flash back to stock 4.5.91 to to unroot the phone. do i just put the .zip on my sd card and flash using clockworkmod
also curious
Same question.
I was previously on GB that was pushed to me OTA. I got bored and rooted, unlocked, and flashed Ken's Alien not thinking about the consequences of not being able to revert to stock thanks to previous root methods like Gingerblur and SBF that made it so easy. I want to get my work email back on my phone, but cannot if I am rooted.
Will flashing a 1.8.3 Fruitcake and then OTA to GB brick me? I've looked everywhere and am still noobiously confused.
Anyone know how to unroot w/unlocked bootloader? Is it possible?
bbunsen said:
Same question.
I was previously on GB that was pushed to me OTA. I got bored and rooted, unlocked, and flashed Ken's Alien not thinking about the consequences of not being able to revert to stock thanks to previous root methods like Gingerblur and SBF that made it so easy. I want to get my work email back on my phone, but cannot if I am rooted.
Will flashing a 1.8.3 Fruitcake and then OTA to GB brick me? I've looked everywhere and am still noobiously confused.
Anyone know how to unroot w/unlocked bootloader? Is it possible?
Click to expand...
Click to collapse
"GB that was pushed to me OTA" so you are indeed has the new bootloader so you only way to downgrade will be moto-flash or CWM to 1.83
But why you dont try to download MOTO official SBF 2.3.4/4.5.91 and RSD this the only OFFICIAL MOTO SBF you can RSD with GB new bootloader
the following procedure will bring you device to out-of-the-box state with GB 2.3.4/4.5.91
First have a backup because you phone will be complete clean after this so remove external sd card
1. First format internal sdcard by settings->storage->internal sdcard->format
2. Turn off the phone and press VOL DOWN while your turn ON your phone
3. Wait until "fastboot" tag show up release VOL DOWN and now PRESS VOL UP once to enter to fastboot
4. Now you in fastboot mode "Starting fastboot......."
5. Now go to command windows box (CMD)
(You need moto-fastboot to perform this and you need to be in the same folder where is located moto-fastboot)
moto-fastboot erase boot
moto-fastboot erase system
moto-fastboot erase webtop
moto-fastboot erase recovery
moto-fastboot erase userdata
moto-fastboot erase cache
moto-fastboot erase preinstall
just to make sure everythings is wipe
moto-fastboot -w
after this
moto-fastboot reboot (at the same time press VOL UP and hold until show up "Starting RSD......"
Now start RSD and select the official moto GB 2.3.4/4.5.91 SBF (you can find a copy in dev forum, stickie under the thread of all the SBF's, make sure you chose 2.3.4/4.5.91)
Press start and what until reboot and RSD show up PASS in the status...
This the manual way to do it... and you are 100% you wipe everything...
The other one is doing MSU (motorola software update) and run all the process (in the background what it do is RSD the service SBF of GB 2.3.4/4.5.91) after it finish you can go back an do a factory default restore, inside settings in Android OS
Thanks. I thought about using moto software update, but wasn't sure if it would work. Same with RSD. I just don't wanna brick, but since I won't be RSD downgrading I probably shouldn't be all that worried.
bbunsen said:
Thanks. I thought about using moto software update, but wasn't sure if it would work. Same with RSD. I just don't wanna brick, but since I won't be RSD downgrading I probably shouldn't be all that worried.
Click to expand...
Click to collapse
This is the only SBF without pudding and MOTOROLA OFFICIAL that can be flashed by RSD for now if you already have GB OTA
http://www.filesonic.com/file/15073...signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
CONFIRMED, IS SAFE TO RSD THIS SPECIFIC SBF FROM MOTOROLA:
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
MD5: 56721d893e43b814e95683a00b165555
SHA1: e00786e975b4f1d9fba2ff90c1ee6bbf95bb47b2
I tested both MSU (Motorola Software Update) and RSD and work perfect from GB OTA unlocked
mramirezusa said:
This is the only SBF without pudding and MOTOROLA OFFICIAL that can be flashed by RSD for now if you already have GB OTA
http://www.filesonic.com/file/15073...signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
CONFIRMED, IS SAFE TO RSD THIS SPECIFIC SBF FROM MOTOROLA:
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
MD5: 56721d893e43b814e95683a00b165555
SHA1: e00786e975b4f1d9fba2ff90c1ee6bbf95bb47b2
I tested both MSU (Motorola Software Update) and RSD and work perfect from GB OTA unlocked
Click to expand...
Click to collapse
Does this go for stock locked bootloaders as well. You mentioned you were unlocked. All that I have done on my atrix is root currently. Not to crazy to unlock yet. I'm on the OTA 4.5.91. Have alot of random reboot issues lately and considering this process!
Thanks in advance.
Thanks for the info. I used your fastboot wipe and RSD'd suggeations to SBF. Now my phone appears to be stock. It no longer says unlocked at boot and is not rooted. Exactly what I was looking for.
My first try of using the 183 fruitcake and then OTA update didn't work due to CWM still being there. It may have worked if I had first flashed the stock recovery. I didn't try that.
Thanks again for your assistance!
Sent from my MB860 using XDA Premium App
SGTShark said:
Does this go for stock locked bootloaders as well. You mentioned you were unlocked. All that I have done on my atrix is root currently. Not to crazy to unlock yet. I'm on the OTA 4.5.91. Have alot of random reboot issues lately and considering this process!
Thanks in advance.
Click to expand...
Click to collapse
If you previously installed the OTA update, it should be fine to flash this if locked as well. Its just installing the same software but without root.
The problems after the OTA update happen if you flash a SBF older than gingerbread.
It was the unlocked part of my situation that had me concerned. I haven't messed with bootloaders until this week and was confused and nervous about how that would come into play. If I hadn't unlocked, I wouldn't have hesitated as much to flash the official GB SBF to unroot.
Sent from my MB860 using XDA Premium App
So Guess who got an Atrix today? me! Guess who also probably bricked their atrix today? me!
So here is what happened:
1: I have an unlocked, rooted Atrix 4G from AT&T running 2.2 1.5.7 I believe.
2: I wanted to flash some roms, so I so I attempted to flash tenfar's CWM, but that didn't work, it said install succeeded but I could not get into CWM ( I tried everything, believe me, I'm no noob)
3: I then attempted to flash CWM from Rom Manager and so I did and I flashed the Atrix version, I then hit boot into recovery from within Rom Manager.
4: What I got next is a screen that says "failed to boot 2, starting RSD mode", now I cannot get passed that screen when it powers up.
5: Worst of all, using MSU (moto sw update), it says device is connected but not what kind, meaning I can't restore it, probably because I had adb mode turned on previosly.
update: after attempting to flash a new SBF, the phone told me it failed because the phone did not re-enumerate. Now I have the same problem, but with a new error message on the boot screen: Battery to low to flash!
I have searched everywhere, now I need to resort to you, xda community, Thanks So Much!!!
If you can get into RSD , check to see if fastboot is an option. If you can get into that I would advise to start over by erasing recovery. Command is fastboot erase recovery, then flash romracers recovery thru fastboot. Once you have recovery reboot into it and flash any ROM like Alien, Aura whatever you like.
Alien Atrix
See the thing is, fastboot is not an option , it immediately goes to RSD mode. I may have found a fix, and I am now flashing a new SFB with rsdlite
That's another option, noticed you were on 1.5.7 so I would advise 1.8.3 fruitcake sbf. Make sure you battery is fully charged, if your battery gives out during sbf flash you will hard brick your phone.
Alien Atrix
while I was flashing the sfb, the device failed to reenumerate and now it gives me a low battery warning, with no way to charge it, regardless, I have a friend who will let me borrow his battery tommorrow then Ill try to flash again, really I should use the 1.8.3? I just tried to flash the 1.2.6, so Your saying its ok to go forward with a SFB flash? I come from a world of Samsung's so these are all new to me besides the time I had a backflip for a week (ugh).
Are you sure your unlocked the bootloader? If you successfully unlocked you would have unlocked on top right corner of boot screen and have fastboot also.
Alien Atrix
I'm not sure if I have there is nothing that says "unlocked" at the top of the screen, and I could previously access the recovery and fastboot before this. I did not get this phone new, it came from the AT&T dev center or something like that. My dad works there.
You need to charge the battery. I stripped an old USB cable down and used the red with the positive side of the battery and black with the negative using tape to hold them in place then inserted the battery in the phone and plugged the USB in the computer. This allowed me to flash a ROM and unlock bootloader. Etc.
Warning this could harm you're phone. If you cross the wrong wires or touch more then just negative or positive areas of the phone and or battery. Although I didn't have any trouble with it you might.
If in doubt do it the right way buy a battery charger for your battery, use someone's battery or phone to charge yours.
Sent from my MB860 using Tapatalk
Ok Im at my computer, If you are unsure of unlocked bootloader I now recommend you RSD either 1.8.3 with unlocker & preinstall or the newest is 2.3.4 with unlocker & preinstall read this thread about 3 times first http://forum.xda-developers.com/showthread.php?t=1136261
Unlock using fastboot, after you get phone to boot for first time, ADB commands for preinstall root, after root use Root Explorer app then delete "install-recovery.sh" @ /system/etc.
Now you are ready to install the newest recovery by Romracer 3.2, Tenfars is outdated and no support from the developer. Read this thread 2 times http://forum.xda-developers.com/showthread.php?t=1204500 I recomend flashing this recovery thru fastboot per Romracer.
Now you are ready to flash your choice of ROM, follow proper procedure to flash new ROMs thru Recovery.
Also check out the unlocked sim codes thread in general, unlock sim.
If I helped click the thanks button
what Im confused on is what exactly i should flash if I am stuck in a kind of RSD mode bootloop/soft brick?
On your first post you said you were on 1.5.7 correct?
Atrix first released with 1.2.6 then updated to 1.5.7 then updated again to 1.8.3
Bootloader was unlocked with the 1.8.3 update
I updated to 1.2.6>1.5.7>1.8.3 then followed this tutorial http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader[/UR
ok thanks very much! Ill get back to you later once I get a fresh battery.
Ok so I'm about to flash the Pudding .sbf, am I doing this right?
iCracked said:
Ok so I'm about to flash the Pudding .sbf, am I doing this right?
Click to expand...
Click to collapse
yes, that's what you should have done in the first place. you can't do anything with "ROM" in its name without unlocking your bootloader which is why you're in this predicament. unlocked phone (maybe you mean SIM unlocked, free to use on any carrier) is not the same as an unlocked bootloader.
The title of this thread is epic. I lol'd.
Sent from my MB860 using XDA App
defnow said:
The title of this thread is epic. I lol'd.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Definitely laughed myself. I knew it was a 'i bricked my pants'.
I voided my warranty.
pukemon said:
Definitely laughed myself. I knew it was a 'i bricked my pants'.
I voided my warranty.
Click to expand...
Click to collapse
haha thanks guys, yes I am SIM unlocked and everything just said unlocked so maybe I thought the reason they where specific to carrier locking was the radios? haha but I was wrong
Hi Everybody,
I know there's a lot of "failed to boot 2" around, but it seems like most people can still start their phones, but just can't get into cwm. I can't boot at all, always get failed to boot 2, starting rsd.
My phone was 4.1.52.mb860.att.en.us, running 2.2 Froyo, and I'm not sure about its hacking history (bought in HK, pre-rooted). I did successfully use rsd lite to flash a new radio when i first got the phone, but nothing else until today. I tried to install cwm through rom manager, but my phone must be locked, and now I can't boot at all.
I tried flashing the unlocker only pudding (ATT ONLY - Unlocker for 1.8.3 and 4.5.91 ATT firmwares). It completed fairly quickly (the guide said it would take a while), and rebooted me right back to "failed to boot 2". I'm worried about flashing a full sbf or doing anything else for fear of hard bricking. Any advice on what to do next? Flash the sbf, try the automated unlocker, etc?
Thanks a ton
Try the moto-Fastboot unlock command then flash an sbf with pudding preinstalled.
sent from my Atrix via XDA premium
just follow this guide. start from 13 if you've already flashed unlocker.
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
once thats done you can get cwm installed, and back up your phone before installing any custom roms/firmware.
Sent from my MB860 using XDA App
Alright, I tried again following the briefmobile guide and it's all fixed. I guess I just needed that extra boost of confidence. Thanks again!
Getting the Failed to boot 3 error.
I've been working at this for days now trying to reflash an sbf image to the phone to no avail. Every single time RSDLite (5.6) gives me the error saying it failed to re-enumerate the device no matter which sbf file I use. I am running as admin, and have all the drivers installed. Any help on this would be VERY much appreciated. Any info you need, just ask.
Hows the charge on the battery.
Sent from my MB855 using xda app-developers app
Well, I keep trying to get it to flash so it runs out a lot but I have a battery charger and I periodically charge it for a few hours. There's no way for me to tell how much of a charge it has but I assume it's somewhere around 75%.
"SVF: 108: 1: 2
Failed to boot 3
Starting RSD mode"
is what is says on the phone.
Always gets stuck on "Waiting for re-enumeration" in RSD Lite.
I get this error:
Phone did re-enumerate after RAM downloader was sent. (0x703e). Phone connected.
This is not much info, we need to know, if you were unlocked, locked, what sbf did you flashed last before this, if you flashed some OTA update, or radio, which sbf are you flashing now, if you can boot into fastboot after this error, and anything, that you think might be important to know.
But if you didn't do anything special, first try redownloaing the sbf.
I never successfully unlocked my bootloader, and I think this is where the brick occured so as far as I know it is locked still. I never flashed any sbf prior to this, I was trying to install a different ROM (I don't like blur very much). As far as I know I am able to boot into fastboot (power + volume up button) and it says fastboot on my phone and when it is plugged into my computer RSD lite displays it as fastboot mode but I can't flash anything to it, it'll give me an error in fastboot. When I hold power + volume down, it says something about NVFlash which I believe is an NVidia tool except the phone just shuts off almost immediately after this. The SBF I am flashing is the Sprint 2.3.5 version, and I've tried downloading and redownloading it from about 4 different locations to no avail. I purchased an external battery charger so I can keep trying different things, so the battery is almost always at a 100% charge. As of now I believe the phone to be unrecoverably bricked, and it's pretty sad because I had the photon for all of maybe 10 hours. Safe to say I've learned my lesson about flashing non HTC devices. My EVO 4G was so easy to do, I guess Motorola really doesn't like people messing with their devices.
Edit: If there is anymore information you think would be helpful let me know.
So you can get into rsd lite or not? There is no flashable 2.3.5 sbf, except the electrify one. All these sprint test sbfs, who knows, what it is for, but there is no signature and no full partition smgs. I think it won't even start flashing. Or? If it started to flash in your case, then your phone is bricked. But if you never flashed anything like 2.3.5 ota or 2.3.5 electrify or 2.3.5 pudding, and you can get into rsd lite or fastboot, I don't think it's unrecoverablly bricked.
peetr_ said:
So you can get into rsd lite or not? There is no flashable 2.3.5 sbf, except the electrify one. All these sprint test sbfs, who knows, what it is for, but there is no signature and no full partition smgs. I think it won't even start flashing. Or? If it started to flash in your case, then your phone is bricked. But if you never flashed anything like 2.3.5 ota or 2.3.5 electrify or 2.3.5 pudding, and you can get into rsd lite or fastboot, I don't think it's unrecoverablly bricked.
Click to expand...
Click to collapse
Yes I am able to get into RSD lite, and it recognizes my phone just fine everytime with no trouble. I believe it starts flashing, or it at least creates the image but everytime it gets stuck on "waiting for re-enumeration" and it fails there with an error like "phone did not re-enumerate" or something along those lines. I've tried flashing a 2.3.4 sbf as well but it gives me the same error as if I were to flash one of the 2.3.5 files.
Ok. If it was 2.3.4 - 198_7 or 198_6 sbf and did not even re-enumerated, you need to get unlocked. Try flashing pudding unlock and recovery from fastboot or try flashing this - http://d-h.st/WKD or use this method - http://forum.xda-developers.com/showthread.php?p=25826491
peetr_ said:
Ok. If it was 2.3.4 - 198_7 or 198_6 sbf and did not even re-enumerated, you need to get unlocked. Try flashing pudding unlock and recovery from fastboot or try flashing this - http://d-h.st/WKD or use this method - http://forum.xda-developers.com/showthread.php?p=25826491
Click to expand...
Click to collapse
Pudding unlock in fastboot gives me the error "Failed flashing process. Unable to retrieve interface handle(0x7027) phone connected."
Deblur gives me the same error as before, "failed to re-enumerate".
The link to the third method is really hard for me to understand. I understand the basics in which he speed hacks it, but I don't understand which files I will need to put in and where to get those files and which ones are correct etc.
I've found the directory with all the .smg files that I'm assuming is the image. Which files would I need to speed hack to have a chance at saving this thing?
Also, my phone fails to flash anything. I'm pretty sure it doesn't actually get anything done except to create the image.
In the command line when I type in "moto-fastboot oem unlock" it says INFOOEM unlock not implemented so I take it that means I'm still locked for sure.
When I try to manually write stuff via command line with the command "moto-fastboot flash recovery derpunlock" and any of the .smg files, it sends it fine but it fails on writing it.
bdotr said:
When I try to manually write stuff via command line with the command "moto-fastboot flash recovery derpunlock" and any of the .smg files, it sends it fine but it fails on writing it.
Click to expand...
Click to collapse
thats because deprunlock is a bootloader not a recovery.
step by step what have to done to get this error. sounds like your have a error in recovery.
mof9336 said:
thats because deprunlock is a bootloader not a recovery.
step by step what have to done to get this error. sounds like your have a error in recovery.
Click to expand...
Click to collapse
Well it would never get far enough to let me flash a recovery. I'm not able to flash any .sbf's through RSD lite either. The error it gives me every time is "device failed to re-enumerate".
I'm trying it through the ramloader now. I'm pretty sure I'm stuck on an bum electrify install. When I use the electrify ramloader it reboots to a blank screen with the motorola logo on it and when I try to flash derpunlock over through command line it doesn't say anything past "writing 'boot'".
Pudding must be flashed in rsd lite too.
Fastboot oem unlock is useless right now. You need to get there unlockable bootloader there first.
You need to speedhack CG42 it's bootloader, and it's preventing from re-enumeration, because it is not booting to rsd after re-enumeration. Try that one CG42 from pudding first. You need to split that with moto android depacker. But I have suspicion, that your bootloader or ramdownloader was switched to another signature version.
Last chance, but really the last, is flashing Electrify sbf.
****, now I noticed that, you should never ever flash electrify ramdownloader there. You changed rdl signature version. Now you have only the last chance. Download and flash full electrify sbf. But you will have no 4g, no more ota, and I am not sure if it flashes electrify radio or not, so maybe you will have no service.
If you really want, you can try some combination with creating custom sbf for recovering, but you need to read the whole thread in dev section and get much more familiar with that situation.
peetr_ said:
Pudding must be flashed in rsd lite too.
Fastboot oem unlock is useless right now. You need to get there unlockable bootloader there first.
You need to speedhack CG42 it's bootloader, and it's preventing from re-enumeration, because it is not booting to rsd after re-enumeration. Try that one CG42 from pudding first. You need to split that with moto android depacker. But I have suspicion, that your bootloader or ramdownloader was switched to another signature version.
Last chance, but really the last, is flashing Electrify sbf.
Click to expand...
Click to collapse
It now says fail to boot 2. I'm going to try the speedhack when I get home from work today and I'll let you know how it goes. No 4G I can do without, no ota as well I'm fine with. The radio thing might bug me though. So do I drop pudding's CG42 file into the 2.3.5 image while it's being created? Or do I flash just the CG42?
You cannot get unlocked anymore with cg42 from pudding, even with speed hack. You must read whole how to make custom sbf thread if you want to try custom combinations. If nothing will help, your only solution is flashing Electrify 2.3.5 sbf or wait, if some similar photon sbf comes out (I doubt).