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!
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
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?
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
It's looking like, at least for some users, unlocking the bootloader on OTA 4.5.141 is causing more issues than the expected soft brick that happens with 4.5.91. When new users are asking about unlocking the latest version, I see the standard advice offered:
- flash pudding sbf (just the unlocker)
- probably get soft-bricked
- issue "fastboot oem unlock" command anyway, reboot & life is great
OR use the one-click BL unlock script.
-----------------
But Nottach said he nearly hard-bricked after flashing pudding while unlocking a stock phone on 4.5.141. He had to do a vol up + power combo WHILE inserting the battery in order to bring it back...
and this user apparently had to do at least a battery pull to complete the process (not sure since posts were edited)...
and still other users are reporting success with the one-click tool.
-----------------
So: is it a fair statement that BL unlocking on the latest version runs an increased risk of bricking the phone, compared with 4.5.91? Is there something else I'm missing here? If I had a stock phone on the latest update I'd be thinking twice about unlocking it.
sheeparecurious said:
It's looking like, at least for some users, unlocking the bootloader on OTA 4.5.141 is causing more issues than the expected soft brick that happens with 4.5.91. When new users are asking about unlocking the latest version, I see the standard advice offered:
- flash pudding sbf (just the unlocker)
- probably get soft-bricked
- issue "fastboot oem unlock" command anyway, reboot & life is great
OR use the one-click BL unlock script.
-----------------
But Nottach said he nearly hard-bricked after flashing pudding while unlocking a stock phone on 4.5.141. He had to do a vol up + power combo WHILE inserting the battery in order to bring it back...
and this user apparently had to do at least a battery pull to complete the process (not sure since posts were edited)...
and still other users are reporting success with the one-click tool.
-----------------
So: is it a fair statement that BL unlocking on the latest version runs an increased risk of bricking the phone, compared with 4.5.91? Is there something else I'm missing here? If I had a stock phone on the latest update I'd be thinking twice about unlocking it.
Click to expand...
Click to collapse
Anybody?
Had to replace my Atrix today, new one already has 4.5.141 on it. Is it safe to unlock the BL using pudding? Or should I wait till the Dev's get it fully worked out?
I'll post my experience/method that I did several times over on my 2 Atrix phones (Both AT&T)
Both phones had unlocked bootloader
I upgraded both phones via the Automatic Update (Motorola Website tool...it downloads the SBF and flashes it to your phone)
At that point you're at 141, stock, unrooted (I did this over unlocked bootloader)
Then I used the Automatic Bootloader Unlock 4.2 to do fastboot oem unlock
I root using preinstall method and restore from Titanium Backup
I have not run into any problems going to and from 141 with unlocked bootloader (I did not try going to FroYo but GB works fine)
I release two ATRIX with GB 2.3.6 Version 4.5.141 very easy
Use RSD Lite 5.7
but the pudding in this link:
http://forum.xda-developers.com/showthread.php?t=1136261
First go to applications and places the phone in debug mode, then turn it off, and plug it in RSD mode and flash with RSD Lite SBF
If for some reason fails you failed to boot OS 0x1000 not detected, goin to RSD mode in 5 seconds
Then use this software
http://forum.xda-developers.com/showthread.php?t=1182871
And utliza the Options for Failed To Apply FIX 0x1000 Boot ", the cel should be in fastboot mode
Write down the key will throw you via commands and then put it again when prompted, after this and you will the unlocked bootloader.
regards
psychephylax said:
I'll post my experience/method that I did several times over on my 2 Atrix phones (Both AT&T)
Both phones had unlocked bootloader
I upgraded both phones via the Automatic Update (Motorola Website tool...it downloads the SBF and flashes it to your phone)
At that point you're at 141, stock, unrooted (I did this over unlocked bootloader)
Click to expand...
Click to collapse
When you did this, did you not get soft-bricked? I know I did.
psychephylax said:
Then I used the Automatic Bootloader Unlock 4.2 to do fastboot oem unlock
I root using preinstall method and restore from Titanium Backup
Click to expand...
Click to collapse
I've done the preinstall, but I can't get CWM to flash the recovery partition.
Can anybody help with reinstalling CWM? Should I flash a pudding / SBF again though I know (based on the contents of ReservedOdm that my BL is still unlocked)?
just wanted to post my experience as i did this a couple of days ago...
i flashed the pudding file (not the one that the automatic unlocker script uses when choosing the 2.3.4/4.5.91 option), got the failed to boot error, put the phone into fastboot mode and did the oem unlock commands (on a PC running winXP), and my bootloader was successfully unlocked. at this point i was able to boot into the stock ROM, with the data partition freshly wiped. i then flashed romracer's cwm using fastboot mode, and then installed the nottachtrix rom. btw i noticed that on the stock rom, cwm would not stay loaded. seems like it gets wiped out after reboot? not sure.
i had previously created a tarball of my data partition and restored it after installing the new rom, but this was a bad idea. better to just use the batch functions of TiBu for the apps, and some sort of sms backup app (from the play store) for keeping your messages.
Just the topic I was looking for. I was trying to unlock my bootloader for this version, but haven't been able to find a guide showing me how and this is my first time.
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.