Related
So I've had my Atrix for a few months now, and it's mostly awesome. I'm coming from having owned an iPhone before, and it's just fantastic. I've stayed away from modding it too much however, since I knew the bootloader was locked and not a lot could really be done. But, according to several posts I see here, the bootloader seems to have been unlocked recently. Yay?
So, I ask that you forgive my ignorance. What does this mean? Does a given ROM need to be modified to work with every model of phone? If so, which ones presently work with the Atrix? Any? (It looks like the unlock was found very recently.) How does that process work exactly? Is there any way to ensure a recovery path if something were to go wrong, so that I don't brick my phone?
I'm just curious here. Presently, my phone is on the stock firmware without any upgrades at all, and I've simply rooted it and installed the webtop mod so I could play games on my TV. Other than that, it's been lots of Android Market for me. I'd like to branch out, and I don't even know where to begin.
There aren't any custom rom's for this yet, there's work being done, so it's just a matter of time. However, there is a developer build from Asia that can be flashed. There are a few issues with it, so if you are averse to troubleshooting or dealing with issues then just wait a few days.
One of the good things you can do right now though is to Unlock it, and then install the Clockwork Mod recovery port in the developer's section. You can use that to make full system backup that you can flash.
Can I flash the UK Firmware on a unlocked ATT Atrix now?
Pretty sure you can at least fastboot flash the CG from the SBF (need system and boot) not sure about flashing the whole SBF. You can try though.
schlupp88 said:
Can I flash the UK Firmware on a unlocked ATT Atrix now?
Click to expand...
Click to collapse
_Dennis_ said:
Pretty sure you can at least fastboot flash the CG from the SBF (need system and boot) not sure about flashing the whole SBF. You can try though.
Click to expand...
Click to collapse
_Dennis_ is right. You should sbf_flash -x to extract the UK firmware and use fastboot to flash just boot.img (CG56 in Froyo) and system.img (CG57 in Froyo). If you want to flash the radio, use a custom .sbf (for AT&T) with only the radio. We don't yet know whether you can replace your bootloader with a UK bootloader. We still flashed a signed bootloader to our phone. In the worst case, if you flash a UK signed bootloader and your boot ROM is looking to find an AT&T signature in your bootloader: BAD! It is fairly unclear that the unlock ALSO tells boot ROM not to care about signatures, it may very well still care. And the order of RSD: erase,write,verify is a little dangerous...
I as well, don't know much about this... but as far as I know, this will mean that developers will be able to create real operating systems for the phone and not have to wait for att/moto to do that...
in the past it was an OS from att/moto, and all the "roms" in xda were actually the same OS but with some skins and mods added to them...
Yes, if you look at the development forums for just about any other android phone, you will see full customized ROMs that can be installed. That's where we are headed.
_Dennis_ said:
Pretty sure you can at least fastboot flash the CG from the SBF (need system and boot) not sure about flashing the whole SBF. You can try though.
Click to expand...
Click to collapse
I did a test with this.
I flashed 1.8.3 SBF over my unlocked bootloader to see if I could use moto-fastboot to flash over a 'stock' bootloader. It works to flash system (since it is still technically unlocked) but fails to flash boot.
So DO NOT TRY TO SBF FLASH A INTERNATIONAL VERSION unless you want to be stuck on the version with no way to get your phone back off.
I also would not flash the boot.img of a international version for the same reason.
beatphreek said:
One of the good things you can do right now though is to Unlock it, and then install the Clockwork Mod recovery port in the developer's section. You can use that to make full system backup that you can flash.
Click to expand...
Click to collapse
I just finished unlocking and installed the new CWM recovery, just waiting for some roms! About the full system backup with CWM, does is deposit a folder to the SD card I can remove for safe keeping like TIBu? I never used CWM to backup or restore.
climo said:
I just finished unlocking and installed the new CWM recovery, just waiting for some roms! About the full system backup with CWM, does is deposit a folder to the SD card I can remove for safe keeping like TIBu? I never used CWM to backup or restore.
Click to expand...
Click to collapse
I think that the backup will be found in a Clockwork folder on your sd card. I also think that when you do the backup you will get to choose the destination. Either sd or external sd.
I haven't used the bl unlock or the new ClockworkMod (Just waiting on a nice rom). But that is how it went for me on the previous CWM that didn't require the unlocked bootloader.
Maybe someone who has this newer stuff can shed a little more light on it.
beatphreek said:
One of the good things you can do right now though is to Unlock it, and then install the Clockwork Mod recovery port in the developer's section. You can use that to make full system backup that you can flash.
Click to expand...
Click to collapse
Does this essentially create an image of your device? Or does it just back up the firmware?
When CWM backs up ur files it creates a image file of
Boot.img
Cache.img
Data.img
recovery.img
system.img
so yes it does use a image.
Y'all talking about custom ROM's and such, no one seems to care about overcloking.. no one seems to realize what a beast a 1.4ghz Atrix would be.
Viamonte said:
Y'all talking about custom ROM's and such, no one seems to care about overcloking.. no one seems to realize what a beast a 1.4ghz Atrix would be.
Click to expand...
Click to collapse
+1.
ROMs will sometimes require you to have the custom kernel associated with them. CM7 for the Captivate comes to mind. With custom kernels, the Captivate was a beast. We had the VooDoo lagfix, which actually made the device usable on bootup. We were able to convert all partitions to ext4, and kind-of make the GPS work.
Overclocking is a possibility too. There's so much that is able to be done. It's a bit difficult coming from an iPhone where customization was limited, even with jailbreaking. But you'll soon get the hang of it.
GPS. Nice point too, but Moto itself promisses improvements on the 2.3.4 OTA. This is the most sorely needed fix for me, since my gps SUCKS. It can take anywhere up to 30 minutos to find my locations. Yes, you read that right.
Viamonte said:
GPS. Nice point too, but Moto itself promisses improvements on the 2.3.4 OTA. This is the most sorely needed fix for me, since my gps SUCKS. It can take anywhere up to 30 minutos to find my locations. Yes, you read that right.
Click to expand...
Click to collapse
Mine works great. You may have a hardware issue?
Sent from my MB860 using XDA App
JayRolla said:
Mine works great. You may have a hardware issue?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
+2
It shouldn't take that long to lock on. Mine locks on instantly.
i have version 1.8.3 with root and with unlocked bootloader if i want to upgrade 2.3.4, i need to flash a clean 1.8.3 and after that to unlocked again ?
or if i do that i will be in risk getting a hard brick??
liranm2 said:
i have version 1.8.3 with root and with unlocked bootloader if i want to upgrade 2.3.4, i need to flash a clean 1.8.3 and after that to unlocked again ?
or if i do that i will be in risk getting a hard brick??
Click to expand...
Click to collapse
When in doubt, use the fruit cakes! =D Mmmmmmm
But yeah, honestly, you don't need to re-lock or un-root. You can just use the Automated Upgrade found here. That will save all your data and stuff, and it'll upgrade you to Gingerbread! =D
BEFORE YOU DO ANYTHING THOUGH (I don't know how many times i emphasize this, but I guess it's worth emphasizing), BACK UP ALL YOUR DATA. In the event you lost all of it, we MIGHT be able to recover some, but expect to loose it all if you just screw my warning over. Oh, and if you want to root again, use the pre-install method. That works well for lots of people (use search bar above to find it =])
Happy upgrading!
BTW if you want unlocked bootloader again, it doesn't come with this Gingerbread build (god only knows why). Just use pudding and you'll be good to go =]
~jojojohnson7410~
jojojohnson7410 said:
When in doubt, use the fruit cakes! =D Mmmmmmm
But yeah, honestly, you don't need to re-lock or un-root. You can just use the Automated Upgrade found here. That will save all your data and stuff, and it'll upgrade you to Gingerbread! =D
BEFORE YOU DO ANYTHING THOUGH (I don't know how many times i emphasize this, but I guess it's worth emphasizing), BACK UP ALL YOUR DATA. In the event you lost all of it, we MIGHT be able to recover some, but expect to loose it all if you just screw my warning over. Oh, and if you want to root again, use the pre-install method. That works well for lots of people (use search bar above to find it =])
Happy upgrading!
BTW if you want unlocked bootloader again, it doesn't come with this Gingerbread build (god only knows why). Just use pudding and you'll be good to go =]
~jojojohnson7410~
Click to expand...
Click to collapse
The link in your post points to the official OTA.
It contains the new bootloader as a part of the payload.
This bootloader will make it impossible to go back to 1.8.3 SBF (or any other SBF) without the risk of hard brick.
For your safety, use Fruit Cakes or any of the ROMs floating around.
Stay away from official OTA or anything that does not have the new bootloader disarmed (or removed).
liranm2 said:
i have version 1.8.3 with root and with unlocked bootloader if i want to upgrade 2.3.4, i need to flash a clean 1.8.3 and after that to unlocked again ?
or if i do that i will be in risk getting a hard brick??
Click to expand...
Click to collapse
In general, you do not need to go back to anything to flash a new ROM.
Just back up your phone (through CWM) and flash a zip file with the ROM of your choice.
Most of the time, you will need to recreate your setup (download the apps and regenerate your preferred settings). To make your life much easier, I would highly recommend investing in Titanium Backup.
lol sorry forgot to mention the fruitcake part X_X made so many posts in the past hour or so, I tend to leave out information I've repeated over a lot of times. I honestly don't have a problem with the OTA (minus the fingerprint, but i think that's with everyone), so that is another viable method. So long as he stays away from SBF (which we technically should anyways) and sticks with eating his Fruitcake, I don't see what's the big deal =]
That's just my two cents on that matter. However, feisty_noodles is probably right about flashing ROMs, as they are usually well tested and don't blow the Odmfuse like the new bootloader does when you unlock with it. It's really your choice, but I preferred having an OTA (until my ROM-itis kicks back in >.>), so I just gave you the method I used.
Good luck!
~jojojohnson7410~
feisty_noodle said:
In general, you do not need to go back to anything to flash a new ROM.
Just back up your phone (through CWM) and flash a zip file with the ROM of your choice.
Most of the time, you will need to recreate your setup (download the apps and regenerate your preferred settings). To make your life much easier, I would highly recommend investing in Titanium Backup.
Click to expand...
Click to collapse
Oh, and yeah. These are important too =] Kenneth made a ROM from the Gingerbread, so you can probably use that (make sure it's not fastboot images though! A lot of people (soft?)bricked their phones that way. And Titatium ftw =D
~jojojohnson7410~
jojojohnson7410 said:
Oh, and yeah. These are important too =] Kenneth made a ROM from the Gingerbread, so you can probably use that (make sure it's not fastboot images though! A lot of people (soft?)bricked their phones that way. And Titatium ftw =D
~jojojohnson7410~
Click to expand...
Click to collapse
There is nothing wrong with fastboot images. I am running a stock from system.img (from Ken's archive) at the moment.
1.8.3 with unlocked bootloader you have 3 way to have official GB 2.3.4/4.5.91
1. Flash 1.83 "WITH" Pudding and then apply OTA by settings->about phone->system update
2. Flash 2.3.4/4.5.91 Official Motorola SBF, you can get this one by Motorola Software Updater or Development forum -> stickie -> SBF thread
3. Download 2.3.4/4.5.91 extract img's and moto-fastboot
Option 1 and 2 update the bootloader
Option 3 preserve old bootloader
liranm2 said:
i have version 1.8.3 with root and with unlocked bootloader if i want to upgrade 2.3.4, i need to flash a clean 1.8.3 and after that to unlocked again ?
or if i do that i will be in risk getting a hard brick??
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
thanks you all....
i will decide today what to do.
mramirezusa said:
1.8.3 with unlocked bootloader you have 3 way to have official GB 2.3.4/4.5.91
1. Flash 1.83 "WITH" Pudding and then apply OTA by settings->about phone->system update
2. Flash 2.3.4/4.5.91 Official Motorola SBF, you can get this one by Motorola Software Updater or Development forum -> stickie -> SBF thread
3. Download 2.3.4/4.5.91 extract img's and moto-fastboot
Option 1 and 2 update the bootloader
Option 3 preserve old bootloader
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Continuing on with the list--options that do not mess with the bootloader:
4) Flash the .img files from Ken found here plus the CWM-flashable radio
5) Fruit cakes!!!
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Are you asking for info for your Atrix or SGS2 device?
Sorry, I am asking about the SGS2.
ds1904.ds said:
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Click to expand...
Click to collapse
If you used the 1-Click method, yes. Your bootloaders are changed. Wouldve been much better to use the Heimdall method or just root your phone then flash the Leak ROM that task650 and Fenny made. As far as reverting bootloaders to stock, thats out of my range of knowledge. Im sure there is a way to do it though.
EDIT: For rooting, best way is to be on stock 2.3.4 and use the Zergrush exploit.
I've seen you're using the past tense a lot, I thought you already DID.
Anyway, for rooting and installing custom ROM, follow this thread:
http://forum.xda-developers.com/showthread.php?t=1311081
I can't pinpoint exactly what to do since having no info.
Thanks for the answers so far, now that I know my bootloaders have been changed I need to figure out how to either change back / and how to safely root. I may just have to wait it out I think though, no problem with that really, working just fine now. And never use the alarm
For clarification, my rooting experience is limited to the Atrix, the SGS2 is new as of Monday, and I am having trouble sifting through information. What I've learned so far is that maybe it was a little hasty to install the ICS leak the way I did. Prior to the ICS leak there was nothing changed on the phone.
You're going to have to get some experience with ODIN. Here is the bootloader you'll want to flash back to, however, then you'll probably need to flash a kernel with CWM (clock work mod) and then boot into cwm to flash a rom such as Tasks stock ICS leak. http://forum.xda-developers.com/showthread.php?t=1316726
So if I follow correctly the ICS leak I installed added newer bootloaders that prevent jigging in the future if it was needed. My two options are apparently to use the method that bypasses the counter, which was posted, or to use ODIN and flash the older bootloader, but this can be dangerous if done incorrectly.
The danger of bricking scares me a little, but I successfully used RSD Lite to unlock the bootloader on my Atrix, don't know if it's similar. Perhaps I should take the Atrix and attempt to install an older bootloader on it to get a feel for things? I figure that it wouldn't make much of a difference however...
I figured out that even though I have a newer bootloader now I still have a 0 for the binary counter, as the leak is considered a samsung official release, of course I don't know how that would effect any given warranty.
So, I still feel that these following questions are unanswered, I apologize if I am not understanding correctly:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lote).
Sorry if these are stupid questions, I hope I am asking good enough questions to help others out in the future
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
ds1904.ds said:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
Click to expand...
Click to collapse
Dont believe you can root since you already flashed it with ODIN 1-Click
ds1904.ds said:
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
Click to expand...
Click to collapse
You cannot install custom ROM's because you dont have CWM.
ds1904.ds said:
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lot).
Click to expand...
Click to collapse
Really not sure on these questions. Any takers?
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Click to expand...
Click to collapse
No; Only download mode (Odin/Heimdall) flashes trigger changes to the warning screen.
ds1904.ds said:
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
Kernel is a set of drivers that tells the hardware what to do. Firmware is like a new base. (XXLPQ, DXLP7 etc.) A ROM is the whole package.
Please if I missed anything or am incorrect about some/all of this, somebody correct me.
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
D3M3NT3D_L0RD said:
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
Click to expand...
Click to collapse
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
ds1904.ds said:
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
Click to expand...
Click to collapse
Where in the hell are you getting an apk from? If you dl Siyah or Entropy kernel, the zImage is in the zip. Pull that and put it on your SD card
I am interested because I was in your position. Did the ICS leak 1 day too early and lost root. So what method did you use to go back to GB? Did you have to flash a new bootloader or was that all done in one package? Was it Entropy's "return" method?
I was seeing if I can keep the ICS leak and root. A dev here advised that all I need to do is re-flash the zip filed ICS leak. However since I have no root, I can't CWM recovery...I don't know another method to flash the rooted ICS leak.
So I'm thinking I have to wait for an exploit, or flash back to an old GB, root, ensure I have CWM, nandroid (I nandroided my rooted GB before upgrading to ICS leak), then flash the zip ICS leak.
Does anyone else have alternatives?
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
SMH...root is not needed for CWM... a custom kernel is
Pirateghost said:
SMH...root is not needed for CWM... a custom kernel is
Click to expand...
Click to collapse
True but to do it with Mobile ODIN you need root
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Entropy512 said:
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Click to expand...
Click to collapse
Glad you chimed in. I now feel stupid at my lack of knowledge
I almost think that the issue is that your "unzipping" the zip image files that you are downloading.
Why is it so important that you keep the phone in a reversable mode? Are you planning on returning it or perhaps selling it and do not want it to be known that you have flashed it?
Personally I am not knowledgeable enough to offer much advice, I just read the forums as most and try to put together the peices of information that fit my situation.
The Dev forum is by far the best place to look and get your questions answered and there are a bunch of guides on step by step processes. The only real advice I can give you is to google each term and understand what it is you need and then post your question.
Hey all. I am actually from the Samsung Galaxy W community and since I'm gonna get the Atrix from my mom soon, I thought I should get a little heads up on how to root it and all. However, the guides here (no offense) freaked me out cuz they had lots of warnings and since the phone I use now is really simple to root (flash update.zip and you're rooted), I realised that rooting the Atrix isn't as easy as rooting the W. Thus I consulted my best friend, Google. He gave me this link: http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Is this the proper way to root? If so, then what do I do next? Because my motive for this phone is to install a custom recovery (ClockworkMod if possible) and (50% chance) stop it right there... I will really appreciate all the help I can get. Thank you, Atrix community.
---EDIT---
I got the method of installing the recovery. Now I just need you guys to verify if that is the proper way.
This looks like the well-known preinstall method. Yes, this is the most common (and IMO the most reliable) way to root the Atrix.
However, a common misconception when it comes to the Atrix is that you need root to get custom recovery. Those two probably couldn't be farther apart - one has nothing to do with the other. You not only don't need root to get custom recovery, it is in fact completely irrelevant because it operates on a much lower level. Instead, you need to unlock the bootloader (because fastboot is implemented in the bootloader, and because you need fastboot that isn't locked down), and then you simply flash your custom recovery via fastboot.
Now here's the problem. First, unlocking the bootloader is by far the most risky step of all. To do that you need to flash a piece of code (the unlocked bootloader, also known as pudding) in the most sensitive part of the phone. You screw this up and you got yourself a brick. Second, when you finally do unlock the bootloader, sometimes you'll be left in an unbootable state (the infamous Failed to boot XXX error). No worries, there's a fix for that too (it is called a softbrick btw). Point is, in that case you cannot just install the custom recovery and then "stop there", you'll need to install an OS too. If you prefer to stick to stock firmware, you should go with so-called fruitcakes, which is just stock firmware prepared to be flashed through custom recovery.
Nothing much to worry about though, everything is explained in detail here. You don't need to google or search in other places, everything you need is right here on XDA (in fact it is probably preferred that you stay within XDA instead of trying to follow random procedures from random places). I suggest you start with some basic noob stuff like this and this. (Some of the stuff in there is somewhat outdated, take any version info mentioned with a grain of salt.)
One big point. You will inevitably come across "SBFs" and advices to flash them. SBFs are inherently dangerous because they contain full complete systems (bootloader, radio, pds, and all the other very sensitive parts of the system), and they are flashed without any error checking, so it's very easy to brick (also known as hardbrick) your phone if you don't know exactly what you're doing. (That is also why all SBFs have been removed from XDA.) Unlocking the bootloader is the only time you should ever be dealing with a SBF, it should be avoided any other time if at all possible.
What I want to do is to get root and at the same time, get a custom recovery. Which means, I want to stick to stock ROM (again 50% chance of sticking to it). And that exactly what I meant by scary warnings... I have no idea what SBFs are (are they like .zip files that Galaxy W users use to flash files?). Anyway, the PUDDING thread was really, and I mean really, scary. Considering the fact that if I screw this phone, my mom will make me own the Galaxy W again...
Sent from my Samsung Galaxy W (GT-I8150) with CM9 RC 6
Yes, it can be scary, and for a reason. It is not for the faint hearted, although it goes without a hitch at least 95% of the time. The idea is that you get familiar with the process until the point where you feel comfortable with doing it.
SBFs are nothing like flashable ZIPs (well, except that both are used to flash stuff onto a device). Fruitcakes and custom ROMs come in flashable ZIPs. SBF stands for "single binary file" and is a proprietary Motorola file. It is created and signed by Motorola. Other than the pudding SBF which is the hacked unlocked bootloader, not much is known about them really, except that in some cases they can easily brick a device if misused.
There's another thing. If your atrix is too new, you might have a newer, non-unlockable bootloader. In that case all you can do is root the phone, no way to get custom recovery on it. Good news is, trying to unlock a non-unlockable BL won't do any harm, it just won't work.
If your goal is to have a custom recovery and root, I suggest you first deal with the recovery and then do the rooting. If you end up having to flash a fruitcake, by doing so you might get root anyway, depending on the fruitcake you choose (some are completely untouched, meaning no root, while some are completely stock but also rooted).
There is also an automated unlock method which you can try if you want. It should be slightly less scary to deal with. Personally, I dislike automated anything, I prefer to do the whole process myself (that way I also learn a bunch of stuff in the process), but to each their own.
ravilov said:
Yes, it can be scary, and for a reason. It is not for the faint hearted, although it goes without a hitch at least 95% of the time. The idea is that you get familiar with the process until the point where you feel comfortable with doing it.
SBFs are nothing like flashable ZIPs (well, except that both are used to flash stuff onto a device). Fruitcakes and custom ROMs come in flashable ZIPs. SBF stands for "single binary file" and is a proprietary Motorola file. It is created and signed by Motorola. Other than the pudding SBF which is the hacked unlocked bootloader, not much is known about them really, except that in some cases they can easily brick a device if misused.
There's another thing. If your atrix is too new, you might have a newer, non-unlockable bootloader. In that case all you can do is root the phone, no way to get custom recovery on it. Good news is, trying to unlock a non-unlockable BL won't do any harm, it just won't work.
If your goal is to have a custom recovery and root, I suggest you first deal with the recovery and then do the rooting. If you end up having to flash a fruitcake, by doing so you might get root anyway, depending on the fruitcake you choose (some are completely untouched, meaning no root, while some are completely stock but also rooted).
There is also an automated unlock method which you can try if you want. It should be slightly less scary to deal with. Personally, I dislike automated anything, I prefer to do the whole process myself (that way I also learn a bunch of stuff in the process), but to each their own.
Click to expand...
Click to collapse
So I was looking through the threads of the QnA section. And I came across this. Should I use the method mentioned in post #2 and #3? It looks pretty straightforward to me...
No, you cannot. The procedure you found assumes you have an unlocked bootloader.
I told you clearly what you need to do. Do not try to short-circuit the procedure. You need to go through ALL of those steps, there is no skipping ahead. It might seem scary, but either deal with it or give up on it. Do or do not, there is no try.
Oh, so is it like, you need to unlock bootlkader then root? If so, then I've finally got it!
Sent from my Samsung Galaxy W (GT-I8150) with CM9 RC 6
i rooted then was forced to unlock the boot loader when i screwed up my phone un-installing apps
used rescue root to one click root my atrix 4g (http://rescueroot.com/)
download clockwork mod recovery (http://www.clockworkmod.com/rommanager)
i installed clockwork mod recovery from fastboot (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus)
unlock the boot loader following this guide (http://forum.xda-developers.com/showthread.php?t=1302423)
as an added bonus here how to bypass that stupid motoblur crap (http://www.youtube.com/watch?v=wXDj-h1DEAM)... not nessicery for anything other then turning off the blur social media thing that comes installed with the phone
now i'm rooted, got the boot loader unlocked and running neutrino rom 2.91 GT+ for the last week, and so far i couldn't be happier
also it helped me to have a second computer, one to have all the how to running on and another to do all the work with
I am wanting to update my phone, but from what I can see there isn't a huge difference between these 2.
Currently I have twrp installed and unlocked bootloader but I am trying to see what I would lose to get the update.
First, you don't have an unlocked bootloader. You have an exploit of the bootloader that is loki patched to allow a custom recovery. The updates (ME7 and MJ7) have patched that exploit.
You can't put TWRP (custom recovery on your phone if you take any update. The new bootloader will not allow you to flash a custom recovery.
So, what safestrap does is allows the bootloader to boot and check all signatures and the stock recovery to make sure its the only one and it hijacks the bootloader after it sees what it is supposed to see. Then it enters into a recovery (safestrap) basically on top of the existing recovery. The problem with Safestrap is your current ROM is still there taking up space on the phone and you have to use the remaining phone memory to load up other ROMS. The other issue is without Kexec you can't flash and run any kernel but the stock kernel which means only stock ROMs and no ROMs like CM or any AOSP ROMs.
So I would say it all depends on what you want or expect from rooting your device. Just clearing some bloat and you like TW ROMs or do you want to have full control to use any ROMs and any kernels.
Point is... if you ask me, there is no way if you're on MDK should you ever take an OTA. They will port over the new update soon enough as it is. The problem is you can't have any other bootloader on your phone but MDK if you want a true custom recovery.
I don't install anything but stock roms anyway, but I'm hesitant since there is no going back.
Eric214 said:
First, you don't have an unlocked bootloader. You have an exploit of the bootloader that is loki patched to allow a custom recovery. The updates (ME7 and MJ7) have patched that exploit.
You can't put TWRP (custom recovery on your phone if you take any update. The new bootloader will not allow you to flash a custom recovery.
So, what safestrap does is allows the bootloader to boot and check all signatures and the stock recovery to make sure its the only one and it hijacks the bootloader after it sees what it is supposed to see. Then it enters into a recovery (safestrap) basically on top of the existing recovery. The problem with Safestrap is your current ROM is still there taking up space on the phone and you have to use the remaining phone memory to load up other ROMS. The other issue is without Kexec you can't flash and run any kernel but the stock kernel which means only stock ROMs and no ROMs like CM or any AOSP ROMs.
So I would say it all depends on what you want or expect from rooting your device. Just clearing some bloat and you like TW ROMs or do you want to have full control to use any ROMs and any kernels.
Point is... if you ask me, there is no way if you're on MDK should you ever take an OTA. They will port over the new update soon enough as it is. The problem is you can't have any other bootloader on your phone but MDK if you want a true custom recovery.
Click to expand...
Click to collapse
Thanks for this explanation.
I am also on MDK and don't intend to give that up. I am wondering if there is anything preventing me from using safestrap recovery on top of my custom recovery as a way to quickly switch between roms without backup and restore each time? In my nexus days, there was an app called boot manager - I believe - that allowed me to choose the rom slot just by a reboot. I would like to do this with a couple - 3 roms because I have a flash addiction but don't want my phone out of commission for 30 min or so while I backup and restore any time I want to switch.
Safestrap
Safestrap is cooler.
dowens9603 said:
Safestrap is cooler.
Click to expand...
Click to collapse
Why?
While I agree that dual/triple/quadruple booting is kind of cool in certain scenarios, it's silly for a lot of people, especially because of the space limitations. I swapped my ME7 for an MDK at the retailer after I realized that I was stuck with TW ROMs only. Now I've got TWRP and CM installed and am much happier.
32BitWhore said:
Why?
While I agree that dual/triple/quadruple booting is kind of cool in certain scenarios, it's silly for a lot of people, especially because of the space limitations. I swapped my ME7 for an MDK at the retailer after I realized that I was stuck with TW ROMs only. Now I've got TWRP and CM installed and am much happier.
Click to expand...
Click to collapse
ROFL safestrap is not cooler. You can't change and use Custom Kernels and you are booting a ROM on top of the stock rom you have so you lose even more internal phone memory. Safestrap is great for those that took any OTA to be able to use SOME Custom ROMs.