I am wanting to relock my bootloader. I have unlocked bootloader with CWM alien rom. I am returning my phone thus the need for relocking. Or is there a rom I can flash that will not have unlocked on motorola screen while it is booting.
In the same place you found the unlock .sbf, you can find a file called "nopuddingforu.rar." This is the bootloader locker, follow the instructions EXACTLY on that page as to locking the phone again. Also, you can flash the MR5 .sbf if you want 100% stock. Be sure to do a factory reset before flashing back to stock.
-Jason
ERROR MESSAGE FAILED TO BOOT 4....RELocking Bootloader
I flashed CM5 recovery, installed nopudding.rar via rsdlite...my phone reboots and I get FAIL on rsdlite. When I cut my phone on it is stuck on Motorola screen with Failed to boot 4 at top of screen and starting RSD mode below it...
when I boot into fastboot I get same thing failed to boot 4 and I have starting fastboot protocol support....
I didnt see the do factory reset before I flashed back to stock......
rslawson said:
I flashed CM5 recovery, installed nopudding.rar via rsdlite...my phone reboots and I get FAIL on rsdlite. When I cut my phone on it is stuck on Motorola screen with Failed to boot 4 at top of screen and starting RSD mode below it...
when I boot into fastboot I get same thing failed to boot 4 and I have starting fastboot protocol support....
I didnt see the do factory reset before I flashed back to stock......
Click to expand...
Click to collapse
just flash the full MR5 .sbf with rsdlite
Thexfactor2011 said:
just flash the full MR5 .sbf with rsdlite
Click to expand...
Click to collapse
That should fix your problem. Forgive me if I'm wrong, but when you flash things with RSDLite you are flashing an actual partition image. The phone internal memory is broken up into multiple partitions, such as /system, /data, etc. When you flash the full MR5.sbf file, I believe it actually flashes all the partitions in the phone with the stock images.
Where is the full MD5 .sbf file located? I didnt see it in the pudding thread....
sorry MR5.sbf
Now that I realize it, I was actually seeing the full MR5.sbf WITH unlock... I can't seem to find one that is locked. Here is the one to the unlock though: http://mophoforum.com/the2dcour/pudding_stock.rar I imagine you could flash that and then flash the nopudding4u to relock it.
EDIT
Here is the nopudding4u file: http://diamantephoto.com/photon_nopudding4u.rar
It consists of only the locked bootloader. So flashing the full MR5.sbf (unlocked) will return your phone back to stock but with an unlocked bootloader. After you have flashed the full MR5, flash the nopudding4u file I linked so that it relocks the bootloader.
It's here in the developer forum. Look for the post from 8/11 about the "Final" sbf. Can't miss it. Good luck!
mrinehart93 said:
Now that I realize it, I was actually seeing the full MR5.sbf WITH unlock... I can't seem to find one that is locked. Here is the one to the unlock though: http://mophoforum.com/the2dcour/pudding_stock.rar I imagine you could flash that and then flash the nopudding4u to relock it.
EDIT
Here is the nopudding4u file: http://diamantephoto.com/photon_nopudding4u.rar
It consists of only the locked bootloader. So flashing the full MR5.sbf (unlocked) will return your phone back to stock but with an unlocked bootloader. After you have flashed the full MR5, flash the nopudding4u file I linked so that it relocks the bootloader.
Click to expand...
Click to collapse
I was thinking I could flash the unlock again and then flash the lock....
rslawson said:
I was thinking I could flash the unlock again and then flash the lock....
Click to expand...
Click to collapse
That's what I told you in the post you quoted
Jason_Thames said:
In the same place you found the unlock .sbf, you can find a file called "nopuddingforu.rar." This is the bootloader locker, follow the instructions EXACTLY on that page as to locking the phone again. Also, you can flash the MR5 .sbf if you want 100% stock. Be sure to do a factory reset before flashing back to stock.
-Jason
Click to expand...
Click to collapse
Yea, this should not be told to people, because as far as I know you HAVE to have the original recovery and as far as I know we have no zip or img file of it currently. So telling people to flash this will only cause problems.
Here is the nopudding4u file: http://diamantephoto.com/photon_nopudding4u.rar
It consists of only the locked bootloader. So flashing the full MR5.sbf (unlocked) will return your phone back to stock but with an unlocked bootloader. After you have flashed the full MR5, flash the nopudding4u file I linked so that it relocks the bootloader.
Click to expand...
Click to collapse
Also, if you flash the full MR5 you do not need to flash the nopudding4u file because you just flashed the complete MR5 file. Meaning you just flashed the whole img file of the phone, meaning that the original recovery is there and it already relocked your phone. The nopudding4u was suppose to just make it so you don't have to flash the MR5, just the small file, so it doesn't take much time. But it wasn't really made clear that you need to have the original recovery, or how to get said recovery.
-DJ
So I just flash the pudding stock rar file?
rslawson said:
So I just flash the pudding stock rar file?
Click to expand...
Click to collapse
No, flash this. http://forum.xda-developers.com/showthread.php?p=16328237
Sent from my MB855 using Tapatalk
To all that replied to my post
I would like to thank everyone for your assisstance. I have my phone back up and working. I am returning my photon and going to pick up the Epic 4G Touch....any of you heard anything I should know about Epic before I get it? I have an EVO that I love...I have it rooted and flash Roms and such so Im not a newb. The support on XDA from people like yourselves is in a worx F#%$ING AWESOME!!!!
I had to use MR3. Once I flashed it I was able to download the MR5 update from the phone. Nothing else worked for me.
MR3 SBF - will relock bootloader
Here is the link to MR3 if anyone needs it
http://forum.xda-developers.com/show...1225220&page=2
M
Related
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
I got root using the /preinstall method with those 2 .bat files posted yesterday.
From page 30-35 is the guidance I followed from mramirezusa.
Other than that we are in the same boat.. I read puddings will flash relatively safely.http://forum.xda-developers.com/showthread.php?t=1159950&page=30
cthomas5714 said:
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
Click to expand...
Click to collapse
Question #2- Is there a possible way to unlock the new bootloader? yes use pudding
cthomas5714 said:
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
Click to expand...
Click to collapse
hey man first things first. dont panic, you are not stuck. this is temporary at best, in the mean while theres plenty of stuff you can do, sbf is not safe to begin with. so actually be gladd you only got to use RSD one time
first things first, get yourselfed unlocked, pudding will do the trick. once after pudding, you never have to touch RSD
Once you are done with pudding go ahead and get tenfars unlocked cwm
once you are done with that you are free to flash pretty much all the roms, as usually custom roms, or fruit cakes dont have bl, only the rest
enjoy
Okay guys, thanks for your help. but let me get this clear, i do not have a unlocked bootloader, im a pudding virgin. I can simply rsd the 1.83 with pudding and thats it? No worries no nothing?
cthomas5714 said:
Okay guys, thanks for your help. but let me get this clear, i do not have a unlocked bootloader, im a pudding virgin. I can simply rsd the 1.83 with pudding and thats it? No worries no nothing?
Click to expand...
Click to collapse
Yes but you still can't use any other sbf. I'd use the raw pudding sbf, unlock, then use CWM from here on out. No more rsd
Sorry about that. There is just the unlock and then the unlock packaged with 1.8.3. The one that has has been causing bricks from my understanding is the packaged one. Be sure you flash just the unlock.
Anyone know what exactly will be erased from /data after flashing the unlock? Also I don't want to restore backed up files that will conflict with new ones. Any guidance on this is appreciated.
snudmusk said:
Sorry about that. There is just the unlock and then the unlock packaged with 1.8.3. The one that has has been causing bricks from my understanding is the packaged one. Be sure you flash just the unlock.
Anyone know what exactly will be erased from /data after flashing the unlock? Also I don't want to restore backed up files that will conflict with new ones. Any guidance on this is appreciated.
Click to expand...
Click to collapse
All user data is wiped when unlocking. The 1.8.3 sbf with pudding is safe to flash but i recommend just using pudding and then CWM and ditch rsd.
jruweaver said:
All user data is wiped when unlocking. The 1.8.3 sbf with pudding is safe to flash but i recommend just using pudding and then CWM and ditch rsd.
Click to expand...
Click to collapse
Agree, just use the pudding only sbf. to unlock , then preinstall to get root.
Make sure to have 50 or so battery so you don't run into the trouble I had with battery being to low to fastboot. Also once you flash pudding you wont be able to boot the phone, don't panic just follow steps to fastboot oem unlock and phone will boot fine afterwards.
Sent from my MB860 using Tapatalk
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
cthomas5714 said:
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
Click to expand...
Click to collapse
Which did you flash? Pudding or 1.8.3 with pudding?
Try connecting your phone to pc select fastboot and finish the pudding instructions (fastboot oem unlock)
It might boot then.
Sent from my MB860 using XDA Premium App
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/show....php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/show....php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Is there a way to root without unlocking the bootloader?
five3zero said:
Is there a way to root without unlocking the bootloader?
Click to expand...
Click to collapse
Yes.
Follow the instructions listed on here:
http://forum.xda-developers.com/showthread.php?p=15023030
The 3rd post has the instructions I followed.
If you have problems be sure to read through the thread as someone else has most likely already had the same issue.
This worked for me.
cthomas5714 said:
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
Click to expand...
Click to collapse
Just do: fastboot oem unlock (or whatever tthe code is)
Them: fastboot reboot
Sent from my MB860 using XDA App
Alright, I unlocked my ATT Atrix while it was on the stock 1.8.3 sbf. I installed tenfars CWM next. Then I installed kenns Ginger Blur ROM. After that I flashed back to stock 1.8.3 with the SBF file located here http://forum.xda-developers.com/showthread.php?t=1125944
I used this one:
Branding: AT&T US
Version: 1.8.3 Full
Android Version: 2.2.2
Bootloader Version: N/A
Webtop version: 4.257.30
Requires RSD Lite 5.0.0
Requires Moto Android (De)packer 1.3 to edit.
My phone no longer said unlocked at boot. I then went on to do the OTA update to 4.5.91 so that I would have gingerbread.
My question is, am I still unlocked? When I try to boot into android recovery, I get a caution symbol with an android standing next to it. I am no longer rooted either. I have read that you need to use CWM in order to root the Atrix on Gingerbread, but I can't use CWM. So will I have to wait?
I managed to get it rooted via the preinstall.img trick. When I installed ROM manager and flashed CWM it said it flashed successfully. Upon trying to boot into recovery I now get the message "Failed to boot 2." Do I have to unlock it again? I didn't try that first out of fear for bricking. Any help is appreciated
jadwv2210 said:
I managed to get it rooted via the preinstall.img trick. When I installed ROM manager and flashed CWM it said it flashed successfully. Upon trying to boot into recovery I now get the message "Failed to boot 2." Do I have to unlock it again? I didn't try that first out of fear for bricking. Any help is appreciated
Click to expand...
Click to collapse
You're semi unlocked. Usually you just have to reflash pudding again (but don't need to do the oem unlock). So that would be the first thing I would do.
Next, flash tenfars unlocked CWM (make sure to delete the file that it tells you... installrecovery.sh or something). I would use that rather than the rom manager cwm at this time.
mysticdrew said:
You're semi unlocked. Usually you just have to reflash pudding again (but don't need to do the oem unlock). So that would be the first thing I would do.
Next, flash tenfars unlocked CWM (make sure to delete the file that it tells you... installrecovery.sh or something). I would use that rather than the rom manager cwm at this time.
Click to expand...
Click to collapse
Alright so I just need to flash the same unlocked sbf file that I flashed when I unlocked on 1.8.3? The one called zomgunlock-lite.sbf?
jadwv2210 said:
Alright so I just need to flash the same unlocked sbf file that I flashed when I unlocked on 1.8.3? The one called zomgunlock-lite.sbf?
Click to expand...
Click to collapse
Yea, although (i haven't kept up), but the original pudding thread has updated the "pudding" file to resolve some memory timing issues so might want to download that.
I have a few questions on unlocking the bootloader and installing a custom recovery. I switched over from the nexus s and things are a little different then what I am used to.
I have already rooted the phone but I was looking at unlocking the bootloader and installing the CWM Recovery to flash over the Alien Rom. My question is if I decide to go back to stock will flashing the 4.5.1A SBF file through RSD Lite return everything back to stock including the recovery. And to lock the bootloader would just be a process of flashing nopudding4u.sbf and runnning moto-fastboot oem lock? If not what is else needed?
This might be a stupid question but I have looked around for a stock recovery file and couldn't find one.
forumx2 said:
I have a few questions on unlocking the bootloader and installing a custom recovery. I switched over from the nexus s and things are a little different then what I am used to.
I have already rooted the phone but I was looking at unlocking the bootloader and installing the CWM Recovery to flash over the Alien Rom. My question is if I decide to go back to stock will flashing the 4.5.1A SBF file through RSD Lite return everything back to stock including the recovery. And to lock the bootloader would just be a process of flashing nopudding4u.sbf and runnning moto-fastboot oem lock? If not what is else needed?
This might be a stupid question but I have looked around for a stock recovery file and couldn't find one.
Click to expand...
Click to collapse
There was an update yesterday the 25th in the pudding thread found here with a file that will lock the bootloader for you. I don't know it has been tested yet but it is only the bootloader not the recovery it could potentially bork something according to the OP but the sbf will fix it. So long story short you are correct welcome to the photon I left from the nexus as well and this phone is just fantastic!
[email protected] said:
There was an update yesterday the 25th in the pudding thread found here with a file that will lock the bootloader for you. I don't know it has been tested yet but it is only the bootloader not the recovery it could potentially bork something according to the OP but the sbf will fix it. So long story short you are correct welcome to the photon I left from the nexus as well and this phone is just fantastic!
Click to expand...
Click to collapse
Perfect, thank you for answering my questions. I agree, I absolutely love this phone and the download speeds are way faster then my nexus s. Do you think with google purchasing motorola they will release an update with an unlocked bootloader?
Need some help please.
I have Telstra Atrix with ota gingerbread, unlocked BL, rooted.
I can't get it to boot into cwm recovery.
I installed ROM Manager from market, flashed CWM 2.0.2.0 , selected Reboot into Recovery but it only gets to the triangle. From there I can hold down Vol Up+VolDown and get to Basic Android recovery.
I have deleted the racing car app as suggested in one thread to make room, but no help.
If I power off and boot it from Power+Vol Down it comes up "Failed to boot 2"
Can't find a solution in XDA or Google. Any help appreciated.
See if you can fastboot flash a recovery image
sent from my Atrix via XDA premium
Most likely need to delete "install-recovery.sh" @ /system/etc, if it's there, then try re-installing CWM Recovery, and see if that works.
Thanks fellas.
Turns out I had lost my unlock BL by flashing the Telstra Froyo sbf from the xda Atrix Firmwares Superthread.
Reflashed the pudding and it's unlocked again. Actually romracer explained it better in his thread. I thought you couldn't relock bootloader. CWM recovery works now.
Thanks fellas.
Turns out I had lost my unlock BL by flashing the Telstra Froyo sbf from the xda Atrix Firmwares Superthread.
Reflashed the pudding and it's unlocked again. Actually romracer explained it better in his thread. I thought you couldn't relock bootloader. CWM recovery works now.
U can't actually relock the boot loader, it "Burns a fuse" inside the unit when u unlock. But flashing an .sbf makes it appear as if it's locked again.
Sent from my MB860 using Tapatalk
Phalanx7621 said:
U can't actually relock the boot loader, it "Burns a fuse" inside the unit when u unlock. But flashing an .sbf makes it appear as if it's locked again.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Yeah thanks. Romracer explained it to me. It doesn't seem to be common knowledge at all. So people flashing sbf's of stock roms are effectively losing root. I spent hours trying to figure it out and get info searching and asking questions. Anyway, all good now and I appreciate the assistance.
On another point do you know how I can get the Telstra radio so I can use it with custom roms? My phone use is way better since installing Telstra stock Gingerbread ota. If I flash another rom I'll lose it won't I? It is N_01.100.00R
Edit: thanks to @Msd24200 and @marko! for pointing out that Radio remains unchanged when flashing cm7. Also discovered where to get the zip of this radio if I lose it http://forum.xda-developers.com/showpost.php?p=15787709&postcount=1
I´ll start with writing, what happend to me, about some weeks ago.
Warning:
Never do this !!!
I wanted to flash the radio from the Photon 2.3.5 leak and I could not find the CWM recovery method (found later after this, thanks Olegfusion), so I took the bp.img and tear it apart with hexeditor to:
amss_sec.mbn
dbl_sec.mbn
osbl_sec.mbn
partition.mnb
RDL1.smg
Depacked full sbf with Motoandroiddepacker (from Skrilax_CZ), extracted headers and just changed mbns and cdt.bin (CG3.smg), later unlocked bootloader (CG42.smg) and tried to repack. Problem was, any try to include CG3.smg (even the default) failed when repacking, so I decided to not include this one.
After several tries I "succesfully" flashed my repacked sbf with radio, but everytime ended at 90% of flashing CG5.smg. I tried more variations, but nothing.
And ended up with Failed to boot 1 (when trying to start as locked) and after unlocking modem did not power up.
So my state now was, switched fuse with broken radio part. Cool
My fuse now - cat /sys/firmware/fuse/ReservedOdm - 10000000000030001000100004000
Then I found the cwm method of flashing radio, thanks to Olegfusion, but this did not helped me. Always, modem did not power up. Only way, how to start Android was through fastboot option Boot Android (No BP).
So I had to find a way, how to fully flash the radio with RSD Lite.
Everytime I tried to flash full 198_7 sbf, it ended right before flashing the radio. Because it flashed the locked bootloader first and while restarting right before CG5.smg (radio) flashing, it writes Failed to boot 1.
I tried to make my own full sbf with unlocked bootloader, but MotoAndroidDepacker, does not accept CG3.smg
So I started thinking(lol):
When RSD Lite creates the image at the beggining, where it is stored?
I found it at C:\Users\--your user dir--\AppData\Local\Motosftemp (win7).
It was a surprise for me, when I found, it was just the depacked sbf with all smgs and firmware.hmg right after the creating image part was done.
This gave me the light of hope.
So I tried to flash my sbf, took those smgs, then full sbf, changed smgs I needed and started with 2nd reflashing. But another problem, RSD Lite recognizes, when those files are changed and when not. If there are unchanged files, and you start 2nd reflashing without exiting RSD, it skips the creating image files. But when you change any, it´s starting over, and all those smgs are created again.
So I started to think about speed hacking it.
I have depacked derpunlock.sbf, my.sbf and full.sbf in RSD temp dir and I thought, I need the leaked cdt.bin and radio.img, because of fuse switched (that was not the right combination). So I started with very slow full sbf flashing speed hacks. Many times.
The super clever speed hack method (lol):
Right after creating image files part, the phone restarts.
This is the time, you need to quickly change (overwrite) those needed smgs.
The right combination that helped me to flash full sbf with radio was CG3.smg (cdt.bin - not sure if it is needed, I took the one from the leaked 2.3.5 zip) and CG42.smg (unlocked bootloader).
That lets the flashing process continue when changing to CG5.smg (radio) flashing. No failed to boot 1.
So, the fuse is switched forever, but I have my radio working again.
As I don´t need 4G, I don´t mind being unlocked.
Most of you don´t need all this, but someone could find it helpful.
Sorry for my English.
but anyway failed to boot 1 is there with locked bootloader.
Yes, that method keeps you unlocked. Because of that, no failed to boot 1.
I still don't understand how my fuse got switched. I flashed the 2.3.5 that did not include the bootloader
Sent from my MB855 using Tapatalk 2
Neither I flashed the new bootloader, there would be no way to unlocking then.
But the radio did it on my side.
for truth, I really worry flashing sbfs really hope once we'll get new unlock
peetr_ said:
The super clever speed hack method (lol):
Right after creating image files part, the phone restarts.
This is the time, you need to quickly change (overwrite) those needed smgs.
The right combination that helped me to flash full sbf with radio was CG3.smg (cdt.bin - not sure if it is needed, I took the one from the leaked 2.3.5 zip) and CG42.smg (unlocked bootloader).
That lets the flashing process continue when changing to CG5.smg (radio) flashing. No failed to boot 1.
Click to expand...
Click to collapse
im looking at the folder(motosftemp) and hit start (to begin flashing) but i dont see it creating the extracted temp files.
So is it possible to flash the new radio? If so is there a link?
Sent from my MB855 using Tapatalk 2
js11222 said:
So is it possible to flash the new radio? If so is there a link?
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
Seems like it but also might switch a fuse and leave you locked down to a certain bootloader.
Sent from my MB855 using Tapatalk 2
For those who has death of phone on reboot or power off and who needs to pull out the battery for some time after the phone dead, this method will fix this trouble for you.
Replace codegroups 3 and 42 from unlocked sbf and flash original sbf with that. you'll fix reboot/power off death.
I fixed it in my photon.
---------- Post added at 03:34 PM ---------- Previous post was at 03:31 PM ----------
regarding radio flash, I think I wouldn't recommend to do it until you understand fully next thing:
when you flash radio bp.img from ota, you have no troubles with fuse.
but if you'll flash boot.img original, you'll switch your fuse on first kernel boot if you'll have radio flashed. So, I do not recommend to flash any native original kernels if you're unlocked. The result may go that you'll not able to lock back and receive failed to boot 1. You'll have only way to flash 2.3.5 bootloader or stay unlocked.
boot.img + bp.img from 2.3.5 = cat /sys/firmware/fuse/ReservedOdm - 10000000000030001000100004000 after first boot.
Hi!
I'm stuck on locked ota (wife was using phone and clicked "install update" before I had a chance to to anything...).
Would there be a way to use the "RSD speed hack" to install stock SBF 2.3.5 and the Japanese radio that is being used to enable our phones to work on domestic USA GSM networks?
There is no Photon 2.3.5 sbf, but you could be probably able to flash the radio with bootstrap, because it looks like Lightsword1942 got motoflash working on bootstrap.
But if you will want the default radio back, you have to flash sbf, that we do not have. But there is a possibility of reflashing 198_7 by hacking rsd flash with 2.3.5 bootloader.
But again, it's risky and noone tried it yet.
peetr_ said:
There is no Photon 2.3.5 sbf, but you could be probably able to flash the radio with bootstrap, because it looks like Lightsword1942 got motoflash working on bootstrap.
But if you will want the default radio back, you have to flash sbf, that we do not have. But there is a possibility of reflashing 198_7 by hacking rsd flash with 2.3.5 bootloader.
But again, it's risky and noone tried it yet.
Click to expand...
Click to collapse
Out of the code groups..which is the bootloader?
Sent from my MB855 using Tapatalk 2
CG42.smg
I did try to flash the radio zip on bootstrap. Didn't work. (btw - I have an electrify).
http://forum.xda-developers.com/showpost.php?p=26383711&postcount=75
Because you don't have the right zip for bootstrap. Ask Lightsword1942 for this.
If you have electrify, then you can probably reflash with 2.3.5 sbf normally, you don't need to hack RSD.