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.
Related
I am looking for info for the Dev section library. Though there are a few comments made regarding flashing back to stock, none seem to offer a (up to date) return to store, stock phone method.
That having been said could sombody offer up a tutorial so I can post it.
Thank you.
Entropy's Thread entitled "[Heimdall][Odin][Stock][Root]UCKH7 Return/Unbrick to Stock (or Root)" is the closest you are going to find to a complete restore to stock.
http://forum.xda-developers.com/showthread.php?t=1286432
I believe this will work for a good majority of folks needing to get back to stock (provided they haven't completely hosed or done something crazy).
Basic steps:
1. Flash the package in the second link of the OP - *NEW* - Kernel + non-rooted system package using either Odin or Heimdall (user's choice - and extract or prepare files accordingly)
2. If the user has accidentally flashed a i9100 International ROM, then they may need to also reflash the stock ATT modem (also in the thread)
3. For good measure, after those items are flashed, probably best to do a factory reset (either via # code or in the UI)
As I mentioned, that should work for 95% of folks that need to go back to stock.
The other 5% are people that flashed a ROM that had new or alternate bootloaders. In this case, I am not aware of any Odin one-click package or bootloader pack available (yet) for the stock ROM, so this may been an issue. But someone may have some more updated information on that.
First settings> privacy> factory data reset.
Then boot into download mode and flash stock plus non root package from here
http://forum.xda-developers.com/showthread.php?t=1286432
With heimdall or Odin
And for anyone who has flashed a different modem you can get the stock modem from the above thread also.
and encase you need to repartition you will need a stock .pit file as well - though as of now as far as I know this is not needed for any reason - non of the roms or kernels in the dev section here in the att xda forums would cause any need for a repartition. Take care with .pit and repartitioning you could end up with a soft brick, a situation that can be recovered from but still not desirable
And if you have flashed anything containing the boot loaders you will need stock boot loaders too, but be very careful with boot loaders as a mistake with boot loaders can result in a hard brick
Sent from my SAMSUNG-SGH-I777 using XDA App
tomween1 said:
I am looking for info for the Dev section library. Though there are a few comments made regarding flashing back to stock, none seem to offer a (up to date) return to store, stock phone method.
That having been said could sombody offer up a tutorial so I can post it.
Thank you.
Click to expand...
Click to collapse
How to Prepare Your Phone to Return to the Store or for Warranty Replacement
There you go. A nice easy to read guide by creepy. Good work.
Sent from my SAMSUNG-SGH-I777 using XDA App
Great guide creepy.
To the OP - why do you believe my packages are not up to date? There is only one firmare revision available for our phone, and that's UCKH7. UCKJ2 is a leak - trying to return a phone with J2 will be a surefire sign to AT&T that you've been diddling around.
It is correct I don't include bootloaders in the package - this is intentional, flashing bootloaders is extremely dangerous. I have a bootloader dump buried within the thread, but I strongly encourage you NOT to try flashing those - again, very dangerous with a good chance of hardbricking.
Entropy512 said:
Great guide creepy.
To the OP - why do you believe my packages are not up to date? There is only one firmare revision available for our phone, and that's UCKH7. UCKJ2 is a leak - trying to return a phone with J2 will be a surefire sign to AT&T that you've been diddling around.
It is correct I don't include bootloaders in the package - this is intentional, flashing bootloaders is extremely dangerous. I have a bootloader dump buried within the thread, but I strongly encourage you NOT to try flashing those - again, very dangerous with a good chance of hardbricking.
Click to expand...
Click to collapse
Well I read through my post again. I thought my question was pretty straight forward, by the responses I received, but I can see where you could have misconstrued my request.
Your packages are all great and (with out a doubt) are the go-to steps. However for noobs, I wanted a more "spelled out" dictation of the steps.... Like the ones supplied by creepyncrawly!
Bro my apologies if I've offended you.... THIS WAS NOT MY INTENT!!!
I still have questions of superuser being in the apps, after all these steps. As I stated to you (PM). I really don't remember if this is installed by AT&T/Samsung out of the box. If not, how is it removed? I would assume, if one were to return a phone, this would be something AT&T wouldn't want to see (again assuming it wasn't stock).
Was the su app still there after flashing entropy's non root package? Are you sure you flashed the non root package and not the stock + root?
Sent from my SAMSUNG-SGH-I777 using XDA App
tomween1 said:
Well I read through my post again. I thought my question was pretty straight forward, by the responses I received, but I can see where you could have misconstrued my request.
Your packages are all great and (with out a doubt) are the go-to steps. However for noobs, I wanted a more "spelled out" dictation of the steps.... Like the ones supplied by creepyncrawly!
Bro my apologies if I've offended you.... THIS WAS NOT MY INTENT!!!
I still have questions of superuser being in the apps, after all these steps. As I stated to you (PM). I really don't remember if this is installed by AT&T/Samsung out of the box. If not, how is it removed? I would assume, if one were to return a phone, this would be something AT&T wouldn't want to see (again assuming it wasn't stock).
Click to expand...
Click to collapse
did you use the UNROOTED version of the package that he provided?
no, superuser is NOT provided by ATT, for obvious reasons.
dayv said:
Was the su app still there after flashing entropy's non root package? Are you sure you flashed the non root package and not the stock + root?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Well there's something interesting. I will retry. I had both on my computer and may have used the wrong one.
Hi,
I've had a look around and can't find a thread that answers my question completely. I just want to gain root access to phone, I have no intention of flashing a custom firmware. My phone is a Galaxy S2 I9100 running Vodafone Australia's stock 4.0.3 ICS.
As I am new to rooting, I have browsed through this page but still have questions:
http://forum.xda-developers.com/showthread.php?t=1103399
I want to be able to easily restore my phone to its stock, unrooted state for warranty purposes. I'm not quite sure how to do this, Is there a way to backup my phones kernel as it is now, and be able to flash back to the stock kernel if something were to go wrong?
Also, My kernel version is 3.0.15-I9100TDULP9-CL422302 ..... The key letters being LP9? So then which one of these 2 would I flash?
CF-Root-SGS2_XW_KPN_LP9-v5.4-CWM5.zip OR
CF-Root-SGS2_DX_SIN_LP9-v5.4-CWM5.zip
Or would either work?
(Yes still going, sorry!) I also saw something called a Binary Flash Counter which counts the amount of times a phone has been modified? Would I be affected by this by just gaining root access? And if so how do I prevent that? (My ultimate aim is to root, but still keep warranty)
Thanks in advance for any help, its really appreciated.
mkirpy22 said:
Hi,
I've had a look around and can't find a thread that answers my question completely. I just want to gain root access to phone, I have no intention of flashing a custom firmware. My phone is a Galaxy S2 I9100 running Vodafone Australia's stock 4.0.3 ICS.
As I am new to rooting, I have browsed through this page but still have questions:
http://forum.xda-developers.com/showthread.php?t=1103399
I want to be able to easily restore my phone to its stock, unrooted state for warranty purposes. I'm not quite sure how to do this, Is there a way to backup my phones kernel as it is now, and be able to flash back to the stock kernel if something were to go wrong?
Click to expand...
Click to collapse
To get back to stock look for your firmware in Intratech's thread. It also provides links for kernel only downloads.
Also, My kernel version is 3.0.15-I9100TDULP9-CL422302 ..... The key letters being LP9? So then which one of these 2 would I flash?
CF-Root-SGS2_XW_KPN_LP9-v5.4-CWM5.zip OR
CF-Root-SGS2_DX_SIN_LP9-v5.4-CWM5.zip
Or would either work?
Click to expand...
Click to collapse
From the thread you were referencing:
The XX and OXA identifiers are not that important. Usually a "KG1" kernel is a "KG1" kernel, and that is that. Sometimes (pretty rare) it happens there will be multiple different kernels with the same name in different firmwares, that are actually different. If this happens, they are usually only very minor changes and you should expect them to still be fully compatible. I include the "XX" and "OXA" identifiers so the very advanced users can deduce from which full firmware I have taken the kernel file.
Click to expand...
Click to collapse
(Yes still going, sorry!) I also saw something called a Binary Flash Counter which counts the amount of times a phone has been modified? Would I be affected by this by just gaining root access? And if so how do I prevent that? (My ultimate aim is to root, but still keep warranty)
Click to expand...
Click to collapse
Yes you will be affected (if rooting with CF-root method) and no, you can't prevent it. However you can reset things. The easiest way to do this is to use TriangleAway from the Play store.
Best thing to do if you want a backup that's as close to stock as possible is to root your phone & then do a Nandroid backup in CWM before doing anything else to the phone (flashing custom roms, other kernels, etc). That will give you a backup that is essentially stock other than the rooted kernel.
If you want to guarantee warranty service, don't mess with your phone (yes, I'm serious). Once you start messing with it, you should lose any expectation of warranty service should the worst happen (rooting your phone/running non stock firmware voids your warranty). Having said that, many people who have rooted their phones and/or run non-stock firmware have been able to get warranty service by going back to stock & resetting the flash counter either with a jig or Triangle Away before sending it in for service. However, this is never a guaranteed, rolled gold 100% certainty.
FXRB is right, before you root your phone, either download your current firmware from Intratech's thread, or use the PC version of Checkfus to download it. This will save you problems if you need to go back to stock in say, 12 mths, and you forget which firmware was originally on the phone.
Unrooting Sprint Samsung s2 ics 4.0.4 fh13
I rooted my phone but would like to unroot it back to previous or stock. Please help with any information to unroot. Thanks.
hispeed10 said:
I rooted my phone but would like to unroot it back to previous or stock. Please help with any information to unroot. Thanks.
Click to expand...
Click to collapse
1. Reset binary counter using Triangle away app.
2. Download Stock firmware for your country/region here: http://www.sammobile.com/firmware/
3. Flash the firmware via Odin.
Done
hispeed10 said:
I rooted my phone but would like to unroot it back to previous or stock. Please help with any information to unroot. Thanks.
Click to expand...
Click to collapse
In addition to what Jokesy said, you say you have a Sprint Samsung s2 ics 4.0.4 fh13. The Sprint variant is the Epic 4G Touch, and has a different forum located at http://forum.xda-developers.com/forumdisplay.php?f=1281.
This forum is for the I9100, which is a GSM phone, and doesn't even work on Sprint's CDMA network.
For your own sake and future sanity, please go to and stay in that forum, and avoid flashing anything from this forum for the I9100.
I rooted my phone pushing CWM.zip and SU-busybox in recovery mode.
First CWM.zip And then su-busybox in the Clockwork orange mod. Its rooted and no yellow triangle.
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
KetoSoi said:
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
Click to expand...
Click to collapse
Never flash an SBF unless you have no other choice. Major hard brick risk.
In this section I have a stickied thread with the answers you need.
If your bootloader is still unlocked and you still have a custom recovery installed, flashing a fruit cake should work fine.
upndwn4par said:
Never flash an SBF unless you have no other choice. Major hard brick risk.
In this section I have a stickied thread with the answers you need.
If your bootloader is still unlocked and you still have a custom recovery installed, flashing a fruit cake should work fine.
Click to expand...
Click to collapse
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
KetoSoi said:
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
Click to expand...
Click to collapse
I just sold mine but will look in PC history. My matrix was stock 4.5.145 and I rooted it. I remember failing a few methods till I found one that worked. If I figure out what I did I will post it for you. If not fruitcake is best way
KetoSoi said:
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
Click to expand...
Click to collapse
The difference between what you posted (an SBF) and what I suggest (a fruit cake) is that an SBF is full stock firmware (bootloader, boot, system, radio, etc). It is the bootloader that causes the problems. Flashing an SBF is a crap shoot. You might do it 10 times without a problem, and the 11th time you hard brick your device. By hard brick I mean hard brick = your device is now a paperweight.
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
However, you are in a different situation - uncharted waters so to speak. No one knows what to expect from 145. And since you don't have a custom recovery installed (CWM, TWRP, etc.) you can't just flash a fruit cake like you would flash a ROM. You should be able to use the fastboot method to flash the fruit cake, but again...uncharted waters.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
upndwn4par said:
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
Click to expand...
Click to collapse
Understood, thanks for the explanation.
UnlockRoot couldnt gain root access
I will attempt your suggestions Thanks very much for the guidance, its invaluable
http://forum.xda-developers.com/showthread.php?t=1769497.
I am pretty sure this is the method I used to root 4.5.145 before I sold it
KetoSoi said:
Unless some one figures out what motorola/att did with 145 to completely screw root ...
Click to expand...
Click to collapse
From what I hear, the only thing that Moto "screwed up" (I wouldn't really call it that) is that on .145 they filled up /system. That is actually trivial to resolve - delete a few apps from /system/app that you don't need/want (you can install them later if you want to, some can live happily on /data) and - this is crucial - wipe /preinstall, since that is what fills up /system. If you don't wipe /preinstall, just deleting apps from /system will only last until next boot. Or, well, you don't need to wipe /preinstall, you can just flash the rooting preinstall image.
upndwn4par said:
Let me know how things go with the above before you even consider this.
Click to expand...
Click to collapse
I was able to flash CWM Recovery no problem. I was able to flash your superuser zip as well, however it did not root the system. All indicators showed it as being successful, but ultimately it was a no-go.
At that point I flashed your fruitcake 141 images, good to go there. I then applied the preinstall method, and viola, rooted again.
I am good to go, thanks to your knowledge and skills Thank you!
Now, all I have to do is email a scan of my middle finger to motorola/att.... lol
ravilov said:
From what I hear, the only thing that Moto "screwed up" (I wouldn't really call it that) is that on .145 they filled up /system. That is actually trivial to resolve - delete a few apps from /system/app that you don't need/want (you can install them later if you want to, some can live happily on /data) and - this is crucial - wipe /preinstall, since that is what fills up /system. If you don't wipe /preinstall, just deleting apps from /system will only last until next boot. Or, well, you don't need to wipe /preinstall, you can just flash the rooting preinstall image.
Click to expand...
Click to collapse
I tried several variations of what youre refering to, however it was to no avail.
I went as far as to delete several useless items (apps) out of the dir, the free space indicated never changed. The amount I removed was more that enough copy su in... yet, it always reports not enough space.
I tried an experiment. I renamed the 'fake' su (always zero bytes) in the bin dir to 'su.old'. Within 30 seconds, *something* renamed it back to 'su', happened right in front of my eyes in Root Explorer.
When you say 'wipe preinstall', specifically you mean?
KetoSoi said:
I tried several variations of what youre refering to, however it was to no avail.
I went as far as to delete several useless items (apps) out of the dir, the free space indicated never changed. The amount I removed was more that enough copy su in... yet, it always reports not enough space.
I tried an experiment. I renamed the 'fake' su (always zero bytes) in the bin dir to 'su.old'. Within 30 seconds, *something* renamed it back to 'su', happened right in front of my eyes in Root Explorer.
When you say 'wipe preinstall', specifically you mean?
Click to expand...
Click to collapse
Wow, that's just bizarre. Not sure what to think here.
I meant something like
Code:
moto-fastboot erase preinstall
KetoSoi said:
I was able to flash CWM Recovery no problem. I was able to flash your superuser zip as well, however it did not root the system. All indicators showed it as being successful, but ultimately it was a no-go.
At that point I flashed your fruitcake 141 images, good to go there. I then applied the preinstall method, and viola, rooted again.
I am good to go, thanks to your knowledge and skills Thank you!
Now, all I have to do is email a scan of my middle finger to motorola/att.... lol
Click to expand...
Click to collapse
Awesome!
I really don't understand why the superuser zip did not give you root access.
Moreover, I don't understand why some users seem to be able to root 145.
I guess I shouldn't be surprised since this device has always been a PITA.
upndwn4par said:
Awesome!
I really don't understand why the superuser zip did not give you root access.
Moreover, I don't understand why some users seem to be able to root 145.
I guess I shouldn't be surprised since this device has always been a PITA.
Click to expand...
Click to collapse
Very odd some cannot root. I was on permalocked bootloader and still rooted after soak
Its sad, because the 145 update seemed like it made the phone a little snappier, and the screen was a pinch smoother.
What do you guys think about applying the CWM Zip for update 4.5.145 in my situation? Would that be safer?
Uh oh.... you guys ran away! LOL
I was able to flash the 145 update via CWM from NYG-SBXLII's handy zip file
No real problems, 145 running fine WITH root intact. Awesome
Had to blow away the recovery-from-boot.p file afterwards, and re-flash CWM Recovery, but it was all good.
Updated SU and bin's, good to go.
affiatic said:
http://forum.xda-developers.com/showthread.php?t=1769497.
I am pretty sure this is the method I used to root 4.5.145 before I sold it
Click to expand...
Click to collapse
This worked for me too with 4.5.145, followed it exactly and had no problems. Thanks!
KetoSoi said:
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
Click to expand...
Click to collapse
How did you unlock the bootloader for firmware 4.5.145? I've been looking everywhere on how to do it safely!
upndwn4par said:
The difference between what you posted (an SBF) and what I suggest (a fruit cake) is that an SBF is full stock firmware (bootloader, boot, system, radio, etc). It is the bootloader that causes the problems. Flashing an SBF is a crap shoot. You might do it 10 times without a problem, and the 11th time you hard brick your device. By hard brick I mean hard brick = your device is now a paperweight.
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
However, you are in a different situation - uncharted waters so to speak. No one knows what to expect from 145. And since you don't have a custom recovery installed (CWM, TWRP, etc.) you can't just flash a fruit cake like you would flash a ROM. You should be able to use the fastboot method to flash the fruit cake, but again...uncharted waters.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
Click to expand...
Click to collapse
hello, ive been using 4.5.145 and was unable to root it, the problem with mine is that when I try to use the preinstall method it chokes when i type the "cp /preinstall/su /system/bin/... there was a message cp write error: no space left on device.. I have tried everything (almost) to root it but was unlucky.. then i saw this thread http://forum.xda-developers.com/showthread.php?t=2153422 ... i wanna try your suggestion but cant find the zip file in suggestion 1 and the 141 fruitcake you made on suggestion 2 and cant find file on option 3.. please do help me.. I have unlocked bootloader and have rom racers cwm.. thank you and more power..
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 see a few threads on root and unlocking the boot loader. which one is the most accepted and still current?
I didnt find any that have been updated recently but my searching probably wasnt the best.
And i see that cm installer works on this phone. Will that install recovery and a new rom and root? if so is there any limitations to changing the rom off of a cm?
Anything?
I don't know of any recent updated methods likely because most devs have obviously moved on to the newer devices (I used what you found on XDA - it's solid). However, there's been a couple of updated universal rooting apps such as VRoot (I haven't used it but I sent it to my novice BIL and he rooted an LG without a problem.) I think those are pretty much your choices.
This device is very ez to root, I think I know that the bootloader is not locked. There's even instructions on how to carrier unlock it if you need that.
Once I got CM 6.0.4 on there I haven't messed with it again. The more I have read about recoveries the more I want to minimize my messings with it. So I have been lazy or too comfy with my current setup so I haven't tried cm installer. I have jumped about 10+ roms and versions this year, I just find it ez to use my current setup. I guess it allows me the freedom to test roms other than cm.
Both of the rooting methods that are stickied dont work anymore. the .tar file is gone from the one that increases the flash counter and the other is a gingerbread kernel.
do you have a link to a root method that is intact?
oscar the grouch said:
Both of the rooting methods that are stickied dont work anymore. the .tar file is gone from the one that increases the flash counter and the other is a gingerbread kernel.
do you have a link to a root method that is intact?
Click to expand...
Click to collapse
Read here and here and watch this video
https://www.youtube.com/watch?v=vjbiF0Ohpe4
http://forum.xda-developers.com/showthread.php?t=1581185&highlight=ics+root
Final step - If you need to reset the flash counter flash this zip (even though this doesn't really matter if the phone is not warrantied[/URL]