rooting using casual unlocker - Verizon Samsung Galaxy Note II

I was wondering if i can root the vzw note 2 with casual and not unlock the device? is there a way to just use it to root the device? Im guessing that it actually unlocks the device and then the rom that i put on the device will be rooted? Ive spoke about rooting without unlocking before, I would prefer keeping the device locked for warranty reasons. Please help if its available. Thanks in advance.

that would depend on which stock rom youre using. I dont think there has been much demand for rooting without unlocking the bootloader, so Mr.Outler probably didnt consider it when creating casual. which is awesome..
It should be a relatively straight-forward process to return the phone back to stock using odin though. Even if your screen breaks or something you can still do it. provided you follow the directions on the forum post.
So:
If you have vraljb----Yes you can root without unlocking the bootloader
if you have vramc3---No you cant as of yet. Although, if i understood correctly, you can just use Odin to flash your phone to vraljb. But good luck cuz its a pain in the ass. make sure you have a list of instructions that has been confirmed to work because youll probably sitting with your phone and odin for an hour or more just retrying flashing the proper PIT files and such.

Related

[Q] Identifying safe-to-install ROMs

ROM newbie here, but I wanted to know how the pros figure out which ROMs they can safely install.
Over on the development board, I see all sorts of references to hard bricking phones as a result of installing the wrong ROM.
I'd really like to update my rooted/gingerblur'd (I believe, how can I check?) phone to Gingerbread.
Thanks for any tips y'all can give me!
Start here : http://forum.xda-developers.com/showthread.php?t=1154600
For the rom safety installs ... just read the all information about the rom and understand what you need to have and if it fits to your phone.
Its rare a rom bricks a phone. Hard brick that is. Its the pre rom stuff required that's gets people into trouble. Soft bricks usually have an easy escape route. Its the panic and the omg I bricked my phone because I didn't read the instructions threads that confuses people.
Sent from the coolest voided warranty phone ever.
the only way you'll hard brick a phone is if you use RSDlite to flash an SBF file.
Specifically, if you did the OTA gingerbread upgrade, then flash a pre-gingerbread SBF.
If you do everything through clockwork recovery, then you'll be able to recover in one way or another.
Have you unlocked your bootloader? If not I recommend doing so, check the pudding thread, unfortunately this does involve using an SBF file (no other way I believe?). But thats just once, after you unlock, flash recovery via moto-fastboot, then do everything through moto-fastboot or recovery, 0% chance of bricking. After you unlock your bootloader its pretty straightforwards.
Roms don't usually brick phones. Most ppl tend to brick by messing up on rooting/unlocking.
I used the Automatic Root/Unlocker/CWM installer (http://forum.xda-developers.com/showthread.php?t=1182871) to do the setup and it all went fine.

Unlocking Galaxy S2

Hi All,
I am a newbie...I would appreciate if someone could help me.
I am planning to root my phone using following,
http://forum.xda-developers.com/showthread.php?t=1309293&page=3
If I use that root can I use following to unlock?
http://forum.xda-developers.com/showthread.php?t=1289395
much appreciate your help
Rooting and unlocking the phone will not conflict. You can do both.
If you try the rooting method you posted, assuming you are still straight stock, it will not work for you. I suggest you either use the rooting method in the sticky post in the general forum, or if you are concerned about incrementing the flash counter, use the stock + root method posted by Entropy512. See the Guide "How to flash custom binaries..." linked in my signature for that.
creepyncrawly...
what are the disadvantages of incrementing the flash counter? I would like to follow an easy method since I am new to this whole thing....used to be iphone customer for long.
appreciate your help.
There is quite a bit of information in the discussion portion of the first two guides. Some people are very cautious about possibly having their warranty voided, since in the agreement with the carrier, flashing custom binaries voids the warranty. On the other hand, many people are very cavalier about it, even returning their phones with custom software still installed. I have not seen anyone post that they actually had their warranty denied. I have been reading both the captivate forums and these forums for about a year and a half.
creepyncrawly said:
There is quite a bit of information in the discussion portion of the first two guides. Some people are very cautious about possibly having their warranty voided, since in the agreement with the carrier, flashing custom binaries voids the warranty. On the other hand, many people are very cavalier about it, even returning their phones with custom software still installed. I have not seen anyone post that they actually had their warranty denied. I have been reading both the captivate forums and these forums for about a year and a half.
Click to expand...
Click to collapse
Thanks. So could I use the second method of not increasing the counter and use the kernel from this below?
http://forum.xda-developers.com/showthread.php?t=1309293
Thanks in advance
Thanks I successfully rooted without increasing flash counter and also flashed the CWM....Yeeee....first timer here so happy. Now I have to unlock but I am really scared it will mess things up. Creepy could you please let me know if I could use the unlock method I mentioned will work?
Thanks.
woow14610 said:
Thanks I successfully rooted without increasing flash counter and also flashed the CWM....Yeeee....first timer here so happy. Now I have to unlock but I am really scared it will mess things up. Creepy could you please let me know if I could use the unlock method I mentioned will work?
Thanks.
Click to expand...
Click to collapse
Congrats on rooting, that method in your post works for unlocking. On step 2, just remember to wait. Your phone will be unlocked after it reboots. So if it says the application is not responding, click "wait"
HTC Chris said:
Congrats on rooting, that method in your post works for unlocking. On step 2, just remember to wait. Your phone will be unlocked after it reboots. So if it says the application is not responding, click "wait"
Click to expand...
Click to collapse
Thanks all....
I did unlock it and also....flashed the unnammed. Very cool. I read everything like 5 times and followed everything to a letter.
Only difference was in the Android SDK...adb.exe is not in the tools anymore it is moved to platform-tools. That is where now you have to copy the zImage as the commands in the instruction assumes that adb is in the same dir.
Thanks.
woow14610 said:
Thanks all....
I did unlock it and also....flashed the unnammed. Very cool. I read everything like 5 times and followed everything to a letter.
Only difference was in the Android SDK...adb.exe is not in the tools anymore it is moved to platform-tools. That is where now you have to copy the zImage as the commands in the instruction assumes that adb is in the same dir.
Thanks.
Click to expand...
Click to collapse
Changed the wording in the Guide to make it clear. Thanks.
For unlock codes visit:
Why would anybody pay for an S2 unlock code when you can install a program from the Market for free?
'cuz they don't know free tool is avail., i guess.
Well if you google unlock s2 to find one of the various unlock code websites, you should see the app as well. its actually the first result. hope nobody pays for a code
If I'm not mistaken, you're not allowed to advertise for paid services in these forums. There's a marketplace on here I think for this.

[Q] ICS Leak question, need a direct answer.

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.

unsure 2.3.4 user - root or upgrade questions

I have a 2.3.4 (45.3.6.MB855.Sprint.en.US) Photon 4g. After reading a bunch of threads, I still want to ask some questions to make sure I'm understanding this all correctly, so I can best decide what I want to do.
I had been putting off rooting, but now I've got this annoying nag screen about upgrading to 2.3.5, and it seems the only way to get rid of the nag screen is to be rooted, right? [EDIT: it's a good month later now. i've actually forgotten what I did to get rid of the nag screen, but it involved finding a file on the part of the system files that gets revealed when you root the phone, and then changing some value in a file from 1 to 0 or vice-versa.]
If I only want to root to have access to the full internal file structure of my phone, I don't need to rom flash, right?[EDIT: right]
Once rooted, I can unroot and upgrade at a later time if some future version comes out that I do want to update to, right? Do I even need to unroot to upgrade if I'm comfortable with never rooting* again and I haven't rom flashed but only rooted? For example, would a 2.3.5 upgrade hurt a rooted 2.3.4 phone or just unroot it?
Rooting will delete everything** and cause me to have to reinstall every app, right? [EDIT: no, it doesn't; bootloader unlocking could though.] If that's true, can I make a backup first that would make reloading apps easy?
What about eFuse? No one's mentioning it as a problem though this older article says it should be.
Type "bad-news-root-crew-the-droid-3-has-a-locked-bootloader" into Google, b/c I can't post hyperlinks as a new user.[EDIT: I dont' know about efuse, but having rooted now, I never ran into a problem caused by it.]
*Actually, the below copy-pasted reply from another thread makes it sound like even after upgrading to 2.3.5, the device can still be rooted, presumably using the photon torpedo method.
"My opinion is do not do the update right now .. It will lock your bootloader.. yes you can root your phone again but thats basically it.. You wont be able the flash any unlocked custom roms"
**This youtube video seems to suggest so: "deleting all yo ****" Go to youtube for qbking77's "How to root the Motorola Photon 4G and get Free Wifi Wireless Hotspot"
If you update to 2.35 you should be able to root. Rooting should not wipe your device. You won't be able to unlock your bootloader. So don't do it. If you must update to 2.35, root first and see if you can find a version of it on these forums with a bootloader that won't permanently lock yours. I think I read a post somewhere about that. Google is your friend.
Sent from my MB855 using xda premium
Really depends on how you intend to use the phone. If you ever want to flash custom kernels as of right now you need to unlock the bootloader. With the update to 2.3.5. right now you cannot unlock your bootloader. The update to 2.3.5. brings really negligible upgrades to the phone and in my opinion the update is really only meant to lock the phone down further.
Rooting does not delete any system files(apps and such) the AIO root seen in the video by QBKing77 prints out deleting all yo ****, shabbypenguin intended this as a joke I think. You can unroot by flashing one of the sbf images floating around.
Hope this helps some.
Thanks for the input JohnH4 and mof9336. My paranoia about the phone getting wiped comes from...
"Warning: Unlocking your phone’s bootloader voids its warranty. It also completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc."
from googling "what-is-bootloader-and-how-to-unlock-bootloader-on-android-phones-complete-guide"
...though I guess "unlocking your phone's bootloader" is not the same thing as rooting.
Exactly. They're two seperate critters.
Sent from my Magical MoPho using xda premium

[Q] Proper way to root?

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

Categories

Resources