I thought it was necessary to unlock the bootloader on android phones before i could root them and flash different roms. A buddy of mine had rooted his old s3 but forgot to unlock the bootloader, so when he tried restarting it, it soft bricked. For the longest time I thought you had to unlock the bootloader then root the phone in order to flash custom roms, have I been wrong all this time?
Think of the Loki workaround as a way to trick the bootloader into flashing improperly signed files. Its like using a credit card on the bolt of a locked door. The door is still locked but you get through anyway.
brizey said:
Think of the Loki workaround as a way to trick the bootloader into flashing improperly signed files. Its like using a credit card on the bolt of a locked door. The door is still locked but you get through anyway.
Click to expand...
Click to collapse
And what are the risks of using the loki tool if you use it correctly? if there is an OTA update to the phone, will it mess it all up?
You don't you the tool...the developers do. And technically, it is only used for flashing a recovery and flashing ROMS with the recovery. You can root without unlocking the bootloader because there is an pre-release official rootable kernel than can be flashed with Odin. It flashes because it is legit.
So I should be able to just go to the how to root page on here http://forum.xda-developers.com/showthread.php?t=2290798 and follow the instructions and flash one of the roms as usual?
yes,go ahead
Related
Hello. The subject matter says it all.
I currently have a rooted and unlocked AT&T Atrix on 1.26 version (yeah...still in ice age ) with a locked bootloader. Im with a non-US telco carrier. It came unlocked and rooted so that was great. No hassle but now I have started doing research on custom roms and webtop mods. I am trying to get around the info overload, so pls bear with my questions.
The overall goal is to have a stock/custom rom devoid of all the bloatwares and can run webtop2sd, and if that is not possible then, webtop. Very simple needs.
Option 1
======
To remain on stock rom and update to 1.83 version, and then to install the webtop2sd mod. Ideally I would like to boot off Debian from the microsd card. There was a post in which a forumer mentioned that he was able to "frankenstein" the webtop2sd and webtop mods. Thats great if I understood correctly.
Option 2
======
To update to 4.5.91 (probably a custom rom like Aura) and then install the webtop2sd/webtop mod.
What should be done?
I am going to update 1.26 -> 1.57 -> 1.83 -> 4.5.91 via system update. (which means I now have to signed with moto account...yes I have not as I read that there were some privacy issues.)
Through the update process, I would lose root. To keep everything clean, I am going to go through factory reset and then perform the update.
Once I am in 1.83 or 4.5.91, I will apply the root and unlock the bootloader. Which is the best way to go about this? Should I just follow the instruction here or this way. Or is there any other better way?
This is all I have for now until I install the webtop mod or the custom rom...
update your phone to wherever you want it at, then use this script to unlock the bootloader:
http://forum.xda-developers.com/showthread.php?t=1182871
after that, you can easily root your phone using the preinstall method found here:
http://forum.xda-developers.com/showthread.php?t=1138204 (second post)
if you update to 4.5.91 though, as you attempt to unlock the bootloader you will get a semi-hard brick, just have it boot up into fastboot mode and continue using the script. easy as pie!
I never got a semi-hard or *soft* brick from unlocking but that's just cause I must love to eat pudding =D . Do all the OTA updates, unlock / root, and then install the 2.3.4 fruitcake and install webtop. Best option by far, IMO, as far as the ease of transition goes. Should be cake. That's what I did and as long as you don't RSD lite with an .SBF back once on 2.3.4 OTA yer good to go.
eat yer fruitcake once updated to 2.3.4 OTA *stock gingerbread*-http://forum.xda-developers.com/showthread.php?t=1163009
Install a custom kernel if ya wanna overclock or undervolt, I would personally suggest Faux123's. -http://forum.xda-developers.com/showthread.php?t=1156040
aaand freeeze all that bloatware!-http://forum.xda-developers.com/showthread.php?t=972459
I read that its easier to update via SBF than OTA? What have your experiences been so far?
Alcapone263 said:
if you update to 4.5.91 though, as you attempt to unlock the bootloader you will get a semi-hard brick, just have it boot up into fastboot mode and continue using the script. easy as pie!
Click to expand...
Click to collapse
Maybe I should try to unlock it now... And then update.
tech_girl said:
I read that its easier to update via SBF than OTA? What have your experiences been so far?
Click to expand...
Click to collapse
well, i can't find it anymore but there is an SBF in the development forum that will allow you to update to 2.3.4 android without getting the brickable bootloader, but i personally don't see a point in using SBF. it's not meant for the end user, and using it can be risky.
SBF flashing is faster i believe, but as i said can also potentially harm your device if you're unsure of what you're doing.
SamCripp, one of the most esteemed devs here, suggests for the average person to completely stay away from sbf flashing after you've unlocked your bootloader unless you absolutely have to use it for something.
remember though, if you use the OTA update you CANNOT downgrade your device through SBF flashing, you HAVE to use the fruitcakes method. it WILL brick your device to downgrade, but only with the OTA update.
EDIT: and it's a semi-hard brick, it doesn't hurt your device in the least. you might panic at first, but it's as simple as booting into fastboot mode and finishing the script. or if you're more tech inclined, you can just do the fastboot oem unlock command through fastboot.
Phalanx7621 said:
....
eat yer fruitcake once updated to 2.3.4 OTA *stock gingerbread*-....
Click to expand...
Click to collapse
Alcapone263 said:
......
remember though, if you use the OTA update you CANNOT downgrade your device through SBF flashing, you HAVE to use the fruitcakes method.....
Click to expand...
Click to collapse
Fruitcakes??? All this jargon.... Hmmm...gotta check this out.
http://forum.xda-developers.com/showthread.php?t=1163009
yep, Fruitcakes. it's a CWM alternative to sbf flashing, much safer since it doesn't edit the bootloader at all, so there's no risk in hard bricking your device.
after you unlock your bootloader, you should install Romracer's CWM recovery here: http://forum.xda-developers.com/showthread.php?t=1204500
do all of your flashing through CWM after you unlock your bootloader, just remember to clear cache/dalvik/data between each ROM or you might get stuck in a bootloop.
Ok...CWM sounds more familiar....
If I understand correctly, I actually dont have to go via OTA. As long as I have the img file for flashing to each version, I could just use the CWM and not via OTA, right?
tech_girl said:
Ok...CWM sounds more familiar....
If I understand correctly, I actually dont have to go via OTA. As long as I have the img file for flashing to each version, I could just use the CWM and not via OTA, right?
Click to expand...
Click to collapse
well, you have to have an unlocked bootloader to get CWM. and to unlock your bootloader, you have to update to 1.8.3 or later.
after you unlock your bootloader, you can install CWM and proceed to just use CWM for your flashing needs.
i repeat again though, after you unlock your bootloader you should stay away from SBF flashing altogether. it's the quickest way to brick your device.
Alcapone263 said:
well, you have to have an unlocked bootloader to get CWM. and to unlock your bootloader, you have to update to 1.8.3 or later.
after you unlock your bootloader, you can install CWM and proceed to just use CWM for your flashing needs.
i repeat again though, after you unlock your bootloader you should stay away from SBF flashing altogether. it's the quickest way to brick your device.
Click to expand...
Click to collapse
+1
Once you unlock and get CWM installed its just a case of wiping the device and flashing zip files.
Yep after unlocking and getting rom racers cwm in, you get to have lots of fun and almost zero chance of hard bricking. Make sure you understand the pudding part. After you unlock throw rsd lite away.
After updating to 1.83 and unlocked, can I immediately installing a GB custom rom like Aura or Alien? Or do I need to update to 4.5.91 stock before I can install a custom rom? Which I assume is pre-rooted, which mean I dont have to root it..
tech_girl said:
After updating to 1.83 and unlocked, can I immediately installing a GB custom rom like Aura or Alien? Or do I need to update to 4.5.91 stock before I can install a custom rom? Which I assume is pre-rooted, which mean I dont have to root it..
Click to expand...
Click to collapse
You should be able to start flashing if you used pudding. No need to upgrade to .91 stock. I didn't. I think most roms are pre rooted now. Not that the rooting method was hard for the atrix.
I voided my warranty.
pukemon said:
You should be able to start flashing if you used pudding. No need to upgrade to .91 stock. I didn't. I think most roms are pre rooted now. Not that the rooting method was hard for the atrix.
I voided my warranty.
Click to expand...
Click to collapse
Yep thats how it works. once BL unlocked and CWM installed you can flash anything, including yes .91 stock.
Note that .91 stock OTA is not only the operating system but also modifies the bootloader hence all the hard brick warnings about flashing sbfs. When you flash zip files you don't touch the bootloader, so there is no chance of hard bricking. i.e. if you flash .91 stock from zip file from CWM as opposed to OTA, you get only the OS, not the bootloader update (which doesn't matter ).
Hi guys! I have a couple of questions. I just updated my Atrix to 2.3.4 by OTA update, so i created a brickable device, haven't i? I would like to know what i have to do know, i want to root the phone and unlock the bootloader to install custom roms, but im afraid to brick my new phone. I have read a lot the past two hours, but im still not sure about what to do now in order to unlock the phone and achieve root.
Also, the device will brick if i try to flash any 2.2 rom, no matter how i flash it (via CWM for example)? Or only if i flash a 1.8.3 SBF via RSDLite? Are there any other files that i have to avoid if i don't want to brick my phone?
Thanks for helping me out guys!
djluis48 said:
Hi guys! I have a couple of questions. I just updated my Atrix to 2.3.4 by OTA update, so i created a brickable device, haven't i? I would like to know what i have to do know, i want to root the phone and unlock the bootloader to install custom roms, but im afraid to brick my new phone. I have read a lot the past two hours, but im still not sure about what to do now in order to unlock the phone and achieve root.
Also, the device will brick if i try to flash any 2.2 rom, no matter how i flash it (via CWM for example)? Or only if i flash a 1.8.3 SBF via RSDLite? Are there any other files that i have to avoid if i don't want to brick my phone?
Thanks for helping me out guys!
Click to expand...
Click to collapse
After you unlock the boot loader, do not flash any sbf prior to 4.5.91. In fact after you unlock the boot loader, there's no need to flash a sbf at all, b/c you can just flash a fruitcake to return to stock.
As far as picking a ROM, it doesn't really matter... any ROM that requires a unlocked boot loader (which they all do), it is at least based off of gingerbread Android 2.3.4+
Use the pudding unlock sbf to unlock your boot loader. Most rooms include root. See my sig for further info.
Sent from my CM7 Atrix 4G
Swiftks said:
After you unlock the boot loader, do not flash any sbf prior to 4.5.91. In fact after you unlock the boot loader, there's no need to flash a sbf at all, b/c you can just flash a fruitcake to return to stock.
As far as picking a ROM, it doesn't really matter... any ROM that requires a unlocked boot loader (which they all do), it is at least based off of gingerbread Android 2.3.4+
Use the pudding unlock sbf to unlock your boot loader. Most rooms include root. See my sig for further info.
Sent from my CM7 Atrix 4G
Click to expand...
Click to collapse
Thanks for your fast response! So, if i use the auto-unlocker on that thread, it wont brick my device right? Thanks for pointing me that, it seems very usefull. Now, this leads me to the next question, i also have to SIM Unlock my Atrix, because its locked to ATT and im trying to use it outside the US, so i need to SIM unlock it, i have seen several threads of users reporting problems SIM unlocking the phone, should i wait for the SIM Unlock code before proceding to unlock the bootloader? I have already ordered one, the guys should email it any time now, it will take less than 24hrs, and no less than 2hrs (which have already passed).
Thanks for your answers guys!
EDIT: Couldn't resist, unlocked the bootloader and achieved root. It was super easy with the automated batch. I hope i don't run into problems when i try to SIM unlock the phone lol
what does that mean. apparently there is a technique to root the phone and put CWR on it to flash things. but why is unlocking the bootloader so important.
kidhudi said:
what does that mean. apparently there is a technique to root the phone and put CWR on it to flash things. but why is unlocking the bootloader so important.
Click to expand...
Click to collapse
Unlocked Bootloader allows one to flash custom Kernel/ROMs.
If you don't know what flashing means or don't care about anything custom, then you're all good to go...
Methods have been discovered so far to boot custom recoveries, root, and boot custom kernels. Still cant flash a new bootloader. What that basically means as far as I understand it, is that while we can run custom kernels, etc, the exploit can be quickly patched by an OTA, and anyone using said method will not be able to take OTA updates.
Its a workaround, not a polished solution (yet), but the devs are doing amazing work, and if you care about the cause then be sure to donate to them!
Hey all,
I'm fairly new to unlocking/rooting (I'm from the simple iPhone jailbreak world).
I have my Atrix 4G rooted with no issues and ClockworkMod installed... that was the easy part it seems.
Where I am struggling is to figure out IF I can unlock my Atrix 4G and if it is safe to do.
I am running Android 2.3.6 on the Bell network. I see a bunch on unlocks for bootloader 2.3.4 and am confisued if that bootloader version has any relation to the android version? How can I figure out what bootloader I have? Would it also be 2.3.6?
If it is indeed 2.3.6, is it possible to unlock, I see no specific unlocks for that version.
Thanks,
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Random Canadian said:
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Click to expand...
Click to collapse
Sorry should have been a little more clear, I have installed ROM Manager and choose the CWM install, but I cannot boot into it, I get a boot error 2 (I think). Sorry phone is at home now so I can't recall exact error will post later.
I got phone 6 month ago, was used phone. I am fairly certain its not unlocked because I cannot boot with CWM, hence cannot install custom ROM.
Thanks for the reply.
Random Canadian said:
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Click to expand...
Click to collapse
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
cerps said:
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
Click to expand...
Click to collapse
Right, my phone is rooted so I have CWM, just can't boot it. My understanding is because I need to unlock, but I don't know how to unlock because I don't know how to figure out what bootloader I have.
cerps said:
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
Click to expand...
Click to collapse
Locked or it just didnt say unlocked at the top? two very different things.
avalanche333 said:
Right, my phone is rooted so I have CWM, just can't boot it. My understanding is because I need to unlock, but I don't know how to unlock because I don't know how to figure out what bootloader I have.
Click to expand...
Click to collapse
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one. Aside from the fact you no longer have any sort of a functional recovery mode.
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Random Canadian said:
Locked or it just didnt say unlocked at the top? two very different things.
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Click to expand...
Click to collapse
Yes I see what your saying, but I am saying that I cannot run CWM. I can only install onto my SD card. But the boot in recovery does not work (ie it will not run CWM). I'll post the error little later tonight when I try at it again.
I realize there is lots of info on unlocking bootloader and I am not concerned about doing the unlock, once I find a way to verify my bootloader version. Ive seen a few posts warning that bootloader must be v 2.3.4 or you can brick the phone.
So I guess ultimately my question is, how can I figure out my bootloader version? Have not seem this answers after some googling.
http://forum.xda-developers.com/showthread.php?t=1136261
Read that and your version will be in settings and then about phone. although I do believe that 234 and 236 unlock via the same method.
If you are going to install Custom roms CM7/9/10 or a blur based then you dont need to even worry about root. otherwise there are instructions in that thread to root that SBF
Random Canadian said:
Locked or it just didnt say unlocked at the top? two very different things.
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one. Aside from the fact you no longer have any sort of a functional recovery mode.
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Click to expand...
Click to collapse
I'm positive it was locked, running 1.83, and had CWM on it. I bought the phone at an AT&T store myself. I rooted it and put CWM on it. The early version of CWM for the Atrix only was accessible by turning the phone on while plugged into the wall charger that came with the phone.
Hi,
As we all know unless we downgrade and stuff, or install custom recoveries (which require some hackeries) we can't root the latest firmware.
I came across this method: http://whiteboard.ping.se/Android/Rooting
It uses the original boot.img and edits it then using fastboot it flashes it with the su binaries and security turned off.
Would this work on our Xperia?
Thanks
Probably, but you'd need to unlock your bootloader...
That kind of defeats the purpose. I'm trying to not do that
I want to be able to install OTA updates and support.
You can alway relock back once rooted. By that, you can OTA update safely and keep rooting
Sent from my little big badass boy!
worf_1977 said:
You can alway relock back once rooted. By that, you can OTA update safely and keep rooting
Sent from my little big badass boy!
Click to expand...
Click to collapse
Ok so if I follow that guide to get root, unlock bootloader, flash the new boot, and relock bootloader, I will be able to install OTA?
Won't that brick my device since I have a modified boot.img?
In order to relock the bootloader you must firdt change back to a stock kernel, otherwise you will brick the phone, wich luckily is recoverable...
Even if yo relock on custom kernel, you will also can enter in fastboot mode to flash stock one
Sent from my little big badass boy!