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.
Related
Hi Everyone,
Many apologies upfront - I'm new to this forum - Hello everyone! - and I'm a complete newbie to phones and am starting to learn this whole thing about rooting/SBF/unlocking guides - please bare with me...
I have a Xoom 3G, and have successfully created my own unsecured boot.img and have been able to patch it to an unlocked bootloader (fastboot oem unlock) and have been able to flash the boot.img successfully, giving me an easy root access on HC 3.1. Where I'm failing to understand with the Atrix is:
1. What is this SBF (Binary File) - I've trialed and errored as much with sbf_flash -x on the original SBF with all thje *.img files and in theory it all appears to be the same as what I have on the Xoom (CG56.img being the boot.img)? Can I just flash the boot.img with the modified ro.secure=0 to emulate what was done on the Xoom - so flash the unsecured boot.img and push the su and Superuser.apk?
2. Following question 1, do I need to have the bootloader unlocked prior to flashing the unsecure boot.img to the boot partition? Is this a neccessary step? Will I brick my phone if I do not unlock the bootloader prior to flashing a unsecure boot.img?
3. I think I have a HKTW version of the phone (this is the firmware I have):
Branding: Retail Hong Kong/Taiwan
Version: 0.56.0 Service
Android Version: 2.2.2
Bootloader Version: N/A
Webtop version: 6.61.22
Is there a way I can upgrade to 2.3.4? I'm guessing there is a leaked version of the SBF (even if it's a testing/development version) that I can easily RSD the sbf to this phone, and everything should be still AOK? What I really mean is, is there a necessary requirement for puddings like the ATT/OLYFR versions?
4. Again - following question 3, if I did let's say apply the SBF of the HKTW 2.3.4, can I then apply the original SBF so that I can get OTA of 2.3.4 when it becomes available?
Many apologies upfront - I seem to be getting confused because I learnt how to root/unlock on the Xoom, and this "signed/unsigned" / "locked/unlocked bootloader" thing is really confusing...
Any advice is much appreciated.
Thanks heaps in advance!!!
PART ONE ON ANSWERING YOUR QUESTION (UNLOCKING BOOTLOADER)
I have no idea about flashing an unsecured boot.img. I am guessing that is the way you root the xoom and you are wondering how to unlock the atrix.
An SBF file cannot be flashed by fastboot. To flash an sbf file, you need to download a utility called RSD Lite.
I am going to give you step by step instructions on how to unlock your bootloader.
(You agree this will void your warranty and the bootloader on the atrix CANNOT be relocked)
1. Download RSD Lite 5.3.1 and the drivers for your phone.
2.Download this bootloader unlock file for International Atrix
3.Unzip (or unrar lols) the file. You should get a .sbf file
4. Power down your phone.
5. Turn on your phone by holding the power/lock button and the volume up key.
6. You should see a line of text that reads "Starting RSD protocol support"
7. Start RSD Lite and plug your phone into your computer.
8. RSD Lite should detect your phone as model SE Flash olympus
9. Press the "..." button and select the file you unzip.
10. Press start and wait.
11. After awhile, your phone should reboot.
12. Turn it off and put it in RSD mode (step 5)
13. Check RSD Lite. Make sure the Result states "PASS"
14. Disconnect the USB and remove the battery.
15. Put the battery back in and now start your phone while holding power/lock and volume down.
16. You should see "Fastboot". Press volume up.
17. You should see "Starting Fastboot protocol support"
18. Now plug your USB back in and issue the "fastboot oem unlock" command
19. You should get a unique ID for your device.
20. Run fastboot oem unlock "unique ID" (without quotes)
21. You now have an unlocked bootloader.
frankus0512 said:
2. Following question 1, do I need to have the bootloader unlocked prior to flashing the unsecure boot.img to the boot partition? Is this a neccessary step? Will I brick my phone if I do not unlock the bootloader prior to flashing a unsecure boot.img?
Click to expand...
Click to collapse
Yes it is necessary. With a locked bootloader flashing it will fail but should not brick your device.
If all you want is root, there are easier ways ie gingerbreak
frankus0512 said:
Is there a way I can upgrade to 2.3.4? I'm guessing there is a leaked version of the SBF (even if it's a testing/development version) that I can easily RSD the sbf to this phone, and everything should be still AOK? What I really mean is, is there a necessary requirement for puddings like the ATT/OLYFR versions?
Click to expand...
Click to collapse
2.3.4 RSD is for AT&T atrix for now, it will not work on our phones.
"is there a necessary requirement for puddings"
puddings are used to unlock your bootloader
If you want 2.3.4, custom roms are your best bet now
Thank you for your kind response!!!!
If I flash the IHOP.sbf, can I then revert back to the original SBF if I need to get Warranty claims, etc? Do I need to "fastboot oem unlock" prior to flashing the original SBF?
Also - what's the main difference between a ROM and a AOSP kernel? Is a ROM equivalent to a SBF?
Thanks so much once again!!!
frankus0512 said:
If I flash the IHOP.sbf, can I then revert back to the original SBF if I need to get Warranty claims, etc?
Click to expand...
Click to collapse
Nope =( It is irreversible.
frankus0512 said:
Do I need to "fastboot oem unlock" prior to flashing the original SBF?
Click to expand...
Click to collapse
Run "fastboot oem unlock" after flashing the IHOP file. Doing it before will result in nothing.
frankus0512 said:
Also - what's the main difference between a ROM and a AOSP kernel?
Click to expand...
Click to collapse
ROM is like an operating system for your phone (example windows 7, ubuntu 10.10) while kernel is like drivers, they allow the OS to interect with the hardware. AOSP kernel? I don't think it exists.
frankus0512 said:
Is a ROM equivalent to a SBF?
Click to expand...
Click to collapse
ROM is like an OS, SBF is a file motorola uses to flash a phone back to stock.
frankus0512 said:
Thank you for your kind response!!!!
Thanks so much once again!!!
Click to expand...
Click to collapse
Your welcome! Hope it helped!
Thank you so much again Matthew5025!
Final question - ROM, you mentioned it's like an OS.
After the bootloader has been unlocked - I found out that the SBF with pudding contains certain *.img only - can I flash any ROM that is posted here? I know there are different ways to apply a ROM out there, but I'm guessing all a ROM flash does is change the root.img and the system.img for their respective partitions? It doesn't touch anything on the radio side or anything else, right?
Reason I ask is so that I can keep using multiple SIM since the phone is not carrier locked - I travel quite a bit - whenever I'm in different countries (just need to set the APN in there).
Thank you so much once again!!!
Cheers.
frankus0512 said:
After the bootloader has been unlocked - I found out that the SBF with pudding contains certain *.img only - can I flash any ROM that is posted here?
Click to expand...
Click to collapse
I don't actually quite understanding what you are trying to say =(
SBF is not a ROM
Yes you can flash any ROM made for the international atrix. It's always good practice to red the specific ROM threads for more info on the specific ROMS.
frankus0512 said:
I know there are different ways to apply a ROM out there, but I'm guessing all a ROM flash does is change the root.img and the system.img for their respective partitions? It doesn't touch anything on the radio side or anything else, right?
Click to expand...
Click to collapse
Actually, a ROM changes your system partition and alot more. As before, different ROMs change different things and you should always refer back to specific ROM pages on what a specific ROM might change.
Although it is possible for a ROM to modify your radio and kernel, moet developer require you to do it yourself.
frankus0512 said:
Reason I ask is so that I can keep using multiple SIM since the phone is not carrier locked - I travel quite a bit - whenever I'm in different countries (just need to set the APN in there).
Click to expand...
Click to collapse
Get an international kernel/radio and it should work!
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
Hello to all
I receive an atrix 4g locked to at&t usa. I unlocked with a code, after i unlock the BL.
I install cwm and romracer and flash CM7(2.3.6) rom from sd.
After i flash Darkside(2.3.5) rom. Now i want to return back to stock.
I have some small problems, the soft keys light is very dimm and the wifi signal is very low compared with my previous iphone 4.
The question is: is it safe to flash 4.5.91(2.3.4) stock sbf with rsd?
I know that the other option are fruitcakes but i just want to know if i can flash this vers with rsd.
System version: 4.5.133.mb860.att.en.us
Android version 2.3.5
Baseband: N_01.77.30P
I read many threads about but i'm still in the "fog". I know that the answer is somewere on the forum and sorry for opening another thread.
Thanks a lot for understanding.
While it's not recommended to use RSDlite after unlocking the bootloader, it will work as long as you only use the 4.5.91 GB2.3.4 SBF (signed). I have done it twice but at my own risk of course.
If you need to return to stock you can flash the fruitcakes, which are stock files. This method is definitely recommended over sbf.
M_Alin said:
Hello to all
I receive an atrix 4g locked to at&t usa. I unlocked with a code, after i unlock the BL.
I install cwm and romracer and flash CM7(2.3.6) rom from sd.
After i flash Darkside(2.3.5) rom. Now i want to return back to stock.
I have some small problems, the soft keys light is very dimm and the wifi signal is very low compared with my previous iphone 4.
The question is: is it safe to flash 4.5.91(2.3.4) stock sbf with rsd?
I know that the other option are fruitcakes but i just want to know if i can flash this vers with rsd.
System version: 4.5.133.mb860.att.en.us
Android version 2.3.5
Baseband: N_01.77.30P
I read many threads about but i'm still in the "fog". I know that the answer is somewere on the forum and sorry for opening another thread.
Thanks a lot for understanding.
Click to expand...
Click to collapse
live4nyy said:
While it's not recommended to use RSDlite after unlocking the bootloader, it will work as long as you only use the 4.5.91 GB2.3.4 SBF (signed). I have done it twice but at my own risk of course.
If you need to return to stock you can flash the fruitcakes, which are stock files. This method is definitely recommended over sbf.
Click to expand...
Click to collapse
Will flashing the SBF via RSD re-lock the bootloader? I need to take my phone in for a warranty swap (hardware issue) and don't want them to know I unlocked the phone.
It will hide the "unlocked" text during boot but it does not actually re-lock the bootloader. But when you think about it, even though they never intended for the end user to unlock the phone (hence the encrypted/locked bootloader), they still put the warning in if/when anyone unlocked the bootloader. It's there for a reason but I doubt they will find out.
ItsLunchBOX said:
Will flashing the SBF via RSD re-lock the bootloader? I need to take my phone in for a warranty swap (hardware issue) and don't want them to know I unlocked the phone.
Click to expand...
Click to collapse
live4nyy said:
It will hide the "unlocked" text during boot but it does not actually re-lock the bootloader. But when you think about it, even though they never intended for the end user to unlock the phone (hence the encrypted/locked bootloader), they still put the warning in if/when anyone unlocked the bootloader. It's there for a reason but I doubt they will find out.
Click to expand...
Click to collapse
So yeah I was impatient and tried to flash it without waiting for a reply. It kept failing and then all I would get on my phone was "Failed to boot 4 Starting RSD Protocol".
I ended up having to re-flash pudding, which was an adventure in itself (upgrading RSD, rebooting computer, trying different USB ports & cables before it would finally take). I think I will just take it in tomorrow even with it saying "Unlocked" and see if they will swap it out. I'm having touch screen issues with intermittent dead spots and ghost touches.
Did you try the stock SBF with the same combination of port and cable as you did when you successfully flashed pudding? I've heard those two factors can cause a bad flash in the past. I've read that a back port on the computer is recommended for sufficient power and using the actual OEM cable the phone came with is highly recommended as well.
Oh well, hope you get it swapped out, the people at the AT&T stores (if that's where you got it) usually don't pay no mind to that anyways.
ItsLunchBOX said:
So yeah I was impatient and tried to flash it without waiting for a reply. It kept failing and then all I would get on my phone was "Failed to boot 4 Starting RSD Protocol".
I ended up having to re-flash pudding, which was an adventure in itself (upgrading RSD, rebooting computer, trying different USB ports & cables before it would finally take). I think I will just take it in tomorrow even with it saying "Unlocked" and see if they will swap it out. I'm having touch screen issues with intermittent dead spots and ghost touches.
Click to expand...
Click to collapse
Hi,
I do have the same kind of query. I have AT&T Motorola Atrix 4G. I unlocked SIM, unlocked BL, rooted and installed CWM recovery, De-dexed and Webtop over HDMI hacked. I am still on AT&T Stock ROM 2.3.4 / Build # 4.5.91
I am facing random reboot problem while using 3G data service. I want to re-flash Stock 2.3.4 ROM. As per your reply in this thread I can only do this by flashing Fruitcakes as I have unlocked BL ... right? But in this link I am bit confused which file to download and flash amongst 2.3.4 / 2.3.5 att 4.5.133 / ATT 4.5.140 - 2.3.6? Also, after flashing a fruitcake can I still flash a custom ROM later on and at any point of time revert back to stock?
Thanks so much.
live4nyy said:
While it's not recommended to use RSDlite after unlocking the bootloader, it will work as long as you only use the 4.5.91 GB2.3.4 SBF (signed). I have done it twice but at my own risk of course.
If you need to return to stock you can flash the fruitcakes, which are stock files. This method is definitely recommended over sbf.
Click to expand...
Click to collapse
If you want to go back to stock, as in the last "Official" build released by Motorola, then you want the 2.3.4 build. And as long as you use the fruitcakes you can go back to a custom rom at any time.
sony108 said:
Hi,
I do have the same kind of query. I have AT&T Motorola Atrix 4G. I unlocked SIM, unlocked BL, rooted and installed CWM recovery, De-dexed and Webtop over HDMI hacked. I am still on AT&T Stock ROM 2.3.4 / Build # 4.5.91
I am facing random reboot problem while using 3G data service. I want to re-flash Stock 2.3.4 ROM. As per your reply in this thread I can only do this by flashing Fruitcakes as I have unlocked BL ... right? But in this link I am bit confused which file to download and flash amongst 2.3.4 / 2.3.5 att 4.5.133 / ATT 4.5.140 - 2.3.6? Also, after flashing a fruitcake can I still flash a custom ROM later on and at any point of time revert back to stock?
Thanks so much.
Click to expand...
Click to collapse
Thanks for your early reply ... Just one thing more I wanna ask that if I flash ATT 4.5.140 - 2.3.6 fruitcake, then can I flash ATT 2.3.4 - 4.5.91 over it? Is the brick warning for going back to stock ATT ROM only after having BL unlocked?
Thanks for your help
live4nyy said:
If you want to go back to stock, as in the last "Official" build released by Motorola, then you want the 2.3.4 build. And as long as you use the fruitcakes you can go back to a custom rom at any time.
Click to expand...
Click to collapse
Yes, you can flash 2.3.4 fruitcake over a 2.3.6 fruitcake. Just make sure to do the "wipes" (clear data/cache/factory reset/fastboot wipe/etc).
As far as I understand, the fruitcakes will not brick your device, as long as you follow the directions. The risk for bricking applies to using an SBF file and RSDlite.
sony108 said:
Thanks for your early reply ... Just one thing more I wanna ask that if I flash ATT 4.5.140 - 2.3.6 fruitcake, then can I flash ATT 2.3.4 - 4.5.91 over it? Is the brick warning for going back to stock ATT ROM only after having BL unlocked?
Thanks for your help
Click to expand...
Click to collapse
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).
WARNING!
DO NOT EVEN TOUCH ANY OF THESE LINKS, IF YOUR PHOTON IS UNLOCKED OR LOCKED, BUT NEVER FLASHED ANYTHING HIGHER THAN 2.3.4_198_7 OR SOME CUSTOM ROM? IF YOU DON´T KNOW, ASK!
THIS WILL PERMANENTLY LOCK YOUR BOOTLOADER!
ONLY FOR PEOPLE WHO REALLY NEED THIS!
AND NOONE TOUCH THIS, AFTER 2.3.6 OR ICS UPDATE!
If you want to know why, read here.
Anyone after succesfull 2.3.5 ota update or after flashing 2.3.5 USC_19 sbf - these links are for you.
But I am not responsible for any damage, you are not forced to flash these.
Don´t flash anything from here, if you do not know well, what are you doing.
Radios:
198_7 radio sbf ----- 198_7 libmoto_ril.so (or older) needed, flashable with bootstrap recovery
254_12 radio sbf ----- 254_12 libmoto_ril.so (or newer) needed, flashable with bootstrap recovery
Be sure, to have the right libmoto_ril.so first, then sbf.
Flashing radio through RSD Lite resets the radio and can solve "Modem did not power up" issue and switched baseband in phone info.
Others:
2.3.5_254_13 sv2 boot, recovery and cdrom image sbf with sv2 bootloader and microboot from USC_19 sbf -
- mostly for unbrick of your device, after failed to boot bricks - 254_13 modules needed, flashable with bootstrap recovery
Full:
There is only one - 2.3.5_USC_19 sbf - but it is for Electrify. After flashing this, you need to flash locked custom rom, "2.3.5_254_13 sv2 boot, recovery and cdrom image" and some sv2 sbf radio, for working Sprint services, including 4G.
Do not try to flash any of those Sprint 2.3.5 full sbf files, they are not signed and your device will not accept them.
Step by step 2.3.5 unbrick for Photon:
yairku said:
1)Flash this SBF. Now you'll have stock 2.3.5 for Electrify. But you need Sprint services (I assume), so you don't stop here.
2) Download bootstrap from DroidX2 forum, and get it working. Of course you need to root your photon first.
3) Flash this ROM from bootstrap. Please follow the instructions for this ROM carefully, you don't wanna flash the SBF again.
4) Flash 254_13 modules with bootstrap. you need them.
5) Flash 2.3.5_254_13 sv2 boot, recovery and cdrom image sbf with RSD Lite.
6) Flash 254_12 libmoto_ril.so with bootstrap. You don't need to flash the radio SBF.
4) and 6) is not needed, if you install rom 3)
Click to expand...
Click to collapse
I am copying and modifying post from yairku, thank him.
One important thing about modules.
In every rom, there are modules for wifi (dhd.ko), wimax (bcmsdio.ko) and VPN (some vpn*.ko) and some other .ko (maybe not important, but they are there).
These modules work only with the kernel they were built with (don't know why).
Example: You are locked and you flashed USC_19 sbf = you flashed USC_19 boot.img ("kernel"), then you flash some rom (locked) without kernel = you reflashed the modules, but still have USC_19 kernel = wifi and wimax is not working, so you need to get these two puzzle pieces together again.
You have two choices -
1- flash 2.3.5 sv2 moto-signed boot.img corresponding with the rom modules
2- flash modules corresponding with the kernel you have (USC_19 in this case)
Very similar important thing applies to radio and libmoto_ril.so.
198_7 radio = 198_7 libmoto_ril.so
254_12 radio = 254_12 libmoto_ril.so
But here it's not so strict -
-198_7 radio = USC_19 libmoto_ril.so without problems
Thank "swuln" for 254_13 dump from his Photon.
Excellent work......
Hi, My photon had been accidentally updated with 2.3.5 USC. Is it flash to flash your file : 2.3.5_254_13 sv2 boot, recovery and cdrom image will this bring me back to Sprint version of 2.3.5 ?
Please help
Not only this, you need to install some sprint based custom rom for locked (mof 2.3.5ish), with bootstrap recovery first. Then install modules and in the end, flash that sbf.
OK, I'm a little unclear on this...
I unfortunately allowed the OTA and on a locked bootloader with the 254_13 ROM.
Are these files I can install to downgrade and then unlock my bootloader and flash a custom recovery?
Short answer. No.
Peetr_,
I wanna get my girls Photon back to legit stock Sprint. She is currently on 2.3.5 from the Moto soak test (the first one) and using RockoDev's Sprint-2.3.5 rom. I just wanna make sure I do this process correctly so that everything turns out OK and she won't have any worries...
So, to start the process I should:
• First flash the mof-2.3.5 rom via BSR
• Then flash module...
• Then flash the 2.3.5 sbf...
When in this process do I flash the radio/lib files? I would assume before or after the module file maybe? Or is it not actually needed.
Thanks for your time man, much appreciated!
Sent from my MB855 using Tapatalk 2
I don't understand correctly, what do you mean by legit. You mean latest not modified stock 254_13 version? Because mof 2.3.5ish is modified custom rom, the only one available with active support.
Someone would have to make 254_13 as flashable zip for bootstrap recovery, to get it in the phone.
But if you really want mof 2.3.5ish rom, you can just install it with bootstrap recovery, install 254_13 modules with bootstrap recovery and flash that sbf with boot.img, recovery.img and cdrom.
peetr_ said:
I don't understand correctly, what do you mean by legit. You mean latest not modified stock 254_13 version? Because mof 2.3.5ish is modified custom rom, the only one available with active support.
Someone would have to make 254_13 as flashable zip for bootstrap recovery, to get it in the phone.
But if you really want mof 2.3.5ish rom, you can just install it with bootstrap recovery, install 254_13 modules with bootstrap recovery and flash that sbf with boot.img, recovery.img and cdrom.
Click to expand...
Click to collapse
Sorry, yes legit as in not modified stock Sprint 2.3.5
My girls device is locked down and a while back I had flashed SprintRocko2.3.5 rom (when it was active).
Currently, I'd like to get her device back to "normal" Sprint device so she could bring it back to Sprint if she wanted without them harassing her about custom firmware on there (as they say).
Sent from my MB855 using Tapatalk 2
That won't be so easy. We don't have no flashable zip with the stock latest rom. And I am not sure, if webtop will flash properly from bootstrap recovery. These two are needed to get it back to stock. Then removing bootstrap and unroot.
Hi Thank you very much for your explanation. Currently i want to flash rom for locked (mof 2.3.5ish), with bootstrap recovery but in his thread show that "You must be coming from 2.3.4. or using a 2.3.4. kernel or none of the service will work" Should i just go ahead ?
Because my photon currently using from 2.3.5 USC Electrify ?
Please help thank you very much in advanced
peetr_ said:
That won't be so easy. We don't have no flashable zip with the stock latest rom. And I am not sure, if webtop will flash properly from bootstrap recovery. These two are needed to get it back to stock. Then removing bootstrap and unroot.
Click to expand...
Click to collapse
OK, thanks for the reply man!
I was hoping that flashing the .sbf file in the OP was gonna be enough lol. Guess not
Sent from my MB855 using Tapatalk 2
Hey friend I am not clear ....wht to do??
I have updated..my photon with latest OTA. its build number is 4.5.1A-1_SUN-254_13 .
And I want to unlock bootloader...
What should i do???
Which files i hav to use????
Sent from my MB855 using xda app-developers app
I am sorry, it's not possible to unlock after ota update.
Thanx... for ur quick reply .....
Its my bad luck....
But any hope to unlock .... means any dev. is working on this or not????
Sent from my MB855 using xda app-developers app
I havnt heard much work on fixing this though this is pretty recent so in time we could possibly come out with a way to downgrade/unlock
Sent from my Kitchen Sync'ed MoPho!
peetr_ said:
WARNING!
DO NOT EVEN TOUCH ANY OF THESE LINKS, IF YOUR PHOTON IS UNLOCKED OR LOCKED, BUT NEVER FLASHED ANYTHING HIGHER THAN 2.3.4_198_7 OR SOME CUSTOM ROM? IF YOU DON´T KNOW, ASK!
THIS WILL PERMANENTLY LOCK YOUR BOOTLOADER!
ONLY FOR PEOPLE WHO REALLY NEED THIS!
AND NOONE TOUCH THIS, AFTER 2.3.6 OR ICS UPDATE!
If you want to know why, read here.
Anyone after succesfull 2.3.5 ota update or after flashing 2.3.5 USC_19 sbf - these links are for you.
But I am not responsible for any damage, you are not forced to flash these.
Don´t flash anything from here, if you do not know well, what are you doing.
Radios:
198_7 radio sbf ----- 198_7 libmoto_ril.so (or older) needed, flashable with bootstrap recovery:thumbdown:
Others:
2.3.5_254_13 sv2 boot, recovery and cdrom image sbf with sv2 bootloader and microboot from USC_19 sbf -
- mostly for unbrick of your device, after failed to boot bricks - 254_13 modules needed, flashable with bootstrap recovery
Full:
There is only one - 2.3.5_USC_19 sbf - but it is for Electrify. After flashing this, you need to flash locked custom rom, "2.3.5_254_13 sv2 boot, recovery and cdrom image" and some sv2 sbf radio, for working Sprint services, including 4G.
Do not try to flash any of those Sprint 2.3.5 full sbf files, they are not signed and your device will not accept them.
Thank "swuln" for 254_13 dump from his Photon.
Click to expand...
Click to collapse
I was at 2.3.5 Ota. Stuck on locked. I flashed the electrify and and was on uscc 2.3.5 .
still locked. I then proceeded to flash sv2 after it booted. Then I rooted, installed bootstrap and install peetr's 2.3.5 . I did not install a sprint radio, nor the lib. I am now working on att. 3G, as I write from my phone not on Wi-Fi. My bootloader is still locked. I can't install sbfs. Nor recovery. However att 3g works. Sim is working. I am in the us. Sj, ca.
Sent from my MB855 using xda app-developers app
If you are satisfied now, good finding.
The radio from USC sbf flashed or not?
Well when USC sbf was flashed the sim did not recognize. It was after flashing your rom.
Sent from my MB855 using xda app-developers app
Hmm, this is interesting.
But good to know.
So you think that kddi radio is not needed?
And you can still use cdma too?