Related
Okay, I'm currently flashing the original 1.2.6 SBF to my atrix, to clear it out. Then to my knowledge, to root the 1.8.3 update or whatever it is called I need to plainly update it to the latest update then use Gingerbreak? I tried Gingerbreak, on a flashed SBF of 1.8.3 and that didn't work. It stayed on the window where it said it was currently executing the thing. Am I right? Is there any other way to root the latest update?
btw I used the exe shortcut to get gingerbreak.
Use GladRoot. It works with the new update promise.
updated and rooted with GingerBreak
I updated to 4.1.83 and rooted without problem with GingerBreak. As it was warned, the process deleted the files from the SD internal card. So it's good to make a backup before.
Hi
I did factory reset and wanted to re-root my phone but seems that it doesn't not work.
I used gladroot before (couple of times) and all was easy and worked fine. Now i dont get any errors, i am getting all successful messages, even superuser is now on my phone but phone is not rooted.
i have Bell with olyla_u4_0.37.4 and used http://forum.xda-developers.com/showthread.php?t=1016060
Any help would be appreciated.
Tnx
You can disregard this previous msg. I was able to update to 2.2.2 than to 2.3.4 via SD method.
Any suggestion about rooting 2.3.4 on Bell phone (Bell original update)?
Hey, there seems to be a few of us(or maybe it's just me) confused about how we can root after the new update.
I just wanted to know if there was a confirmed safe way to restore root.
Thanks
Update:
Thanks to superkev. Manual way works. I can also confirm it also.
Also remember to keep your phone awake (ie. not in the locked screen)
superkev said:
I tried the manual instructions from here: http://briefmobile.com/motorola-atrix-4g-root
Step 6 failed for me, possibly because I had used this method to root 2.3.4. The rest of it went perfectly. I think the 2.3.6 update changed the permissions of the su binary, so these instructions just reset that to what they're supposed to be. I am rooted again!
Click to expand...
Click to collapse
I can't seem to find any root information on bell atrix 2.3.6 either.
saw some unconfirmed reports that superoneclick worked, but it doesn't work for me just sits at "Failed to set prot mask"
and then "WaitforDevice" forever...
if anyone has legit root info for the bell atrix 2.3.6 posting it would be greatly appreciated.
All I want is to install it! But im in usa so I need someone to make a fruitcake of it for me. Oh and I have also read super one click is supposedly working for some.
Sent from my MB860 using Tapatalk
I've got super one click working but superuser keeps denying all my root permissions without giving me a prompt.
DANGER!
So I tried SuperOneClick 2.3.1 and got my Bell Atrix 2.3.6 rooted.... all seemed good and Root Checker told me I was rooted. Light Flow got Super User permission and I thought I was gold!
Then my phone started freezing up and rebooting. Now I can't use the phone because it is crashing every 30 seconds. I would say avoid SuperOneClick (at least this version) for now!!
Oh, and SuperOneClick won't unroot my device so I'm kind of stuck. I would rather not reset my device and have to reinstall all my apps (which are backed up with Titanium Back-up, but which of course needs root to work...).
I'm just trying GingerBreak to unroot so we'll see how that goes.....
---------- Post added at 02:51 AM ---------- Previous post was at 02:44 AM ----------
... OK... so GingerBreak unrooted my phone but it is still completely hooped and the crashing woes continue... anyone with a solution on which system files I might be able to replace to fix this?!?!?
Aaaarrrg!
I tried wit Pete's first and it failed but super one click worked right from the first attempt. Before doing that though, I did a factory reset and started from scratch. Then I restored my apps only with TB. All is OK except that in market my apps list is empty with a message saying that my purchased apps will appear here. I have read that it is a known problem, but not necessarily with this update or because of rooting. In my experience super one click has otherwise been OK. Hope that helps. Don't have a solution for you except maybe trying to do a factory reset first if you are able to and then try again.
Sent from my MB860 using xda premium
Hey thanks. Yes, I ended up having to do a reset from the boot menu (power+vol down) and do an 'Android Recovery' which apparently wipes the system files and reinstalls the OS. My TB backups are still sitting on the internal SD but I am hesitant to re-root so I can reinstall TB and restore... what build of SuperOneClick did you use?
I tried with SuperOneClick 2.3.1.0 (latest). It says that it worked, but even after rebooting, my apps are being denied root access.
UPDATE:
I tried the manual instructions from here: http://briefmobile.com/motorola-atrix-4g-root
Step 6 failed for me, possibly because I had used this method to root 2.3.4. The rest of it went perfectly. I think the 2.3.6 update changed the permissions of the su binary, so these instructions just reset that to what they're supposed to be. I am rooted again!
I just updated to 2.3.6 and used the Briefmobile method to root and can also confirm that it is working. I had previously used this method to do 2.3.4 and had no issues on 2.3.6. Cheers
I might caution those who are not on AT&T about using the "manual" root method from BriefMobile. It was built with AT&T 2.3.4 files. Flashing the root.img in fastboot flashes those files to your /preinstall folder possibly hosing your Bell specific files. This has in the past, and possibly could in the future cause issues when trying to install future updates.
For those of you who have done it, can you look in /preinstall/md5 and see if you have att files?
Sent via 2.3.4 Rooted/Unlocked Moto Atrix using Tapatalk
superoneclick 2.3.1.0
this works flawlessly and on first attempt. so easy!
gingerbreak 1.2 didn't work this time, but it was useful to me for unrooting.
just make sure you do that before installing the update, and follow the superoneclick instructions.
too early to comment on battery life, and other than the keyboard I don't notice any aesthetic changes.
bell atrix
Remember to flash back the original preinstall image to avoid update issues.
Cheers!
das8nt said:
For those of you who have done it, can you look in /preinstall/md5 and see if you have att files?
Click to expand...
Click to collapse
That directory does contain some ATT and Cingular files. However, I used this method to root 2.3.4 and it didn't prevent me from installing the 2.3.6 update. I'm hoping I won't have any trouble going to ICS (fingers crossed that such a thing will even happen!)
superkev said:
That directory does contain some ATT and Cingular files. However, I used this method to root 2.3.4 and it didn't prevent me from installing the 2.3.6 update. I'm hoping I won't have any trouble going to ICS (fingers crossed that such a thing will even happen!)
Click to expand...
Click to collapse
Good deal. I had to help a few revert that folder when updating from 2.2.2 to 2.3.4 due to missing the gameloft stuff, but if it didn't effect your update that's good news.
Just in case, here's the 2.3.6 Bell stock preinstall.img to flash via moto-fastboot (thanks to NFHimself's new Gobstopper): http://www.megaupload.com/?d=C098P9IV
Sent via 2.3.4 Rooted/Unlocked Moto Atrix using Tapatalk
I used the manual way to root with the 2.3.6 update but TB is saying it can't can't gain root access and su keeps fc'ing on me. Anyone have any ideas what could be causing this? I also tried the superone click method but during the exe install on my pc it keeps stopping saying i don't have an internet connection????
j7logan said:
I also tried the superone click method but during the exe install on my pc it keeps stopping saying i don't have an internet connection????
Click to expand...
Click to collapse
that's weird. you definitely don't need internet access to perform the root (i was offline), provided you have superoneclick and phone drivers installed i'd say. does the driver check feature complain about it too?
Yeah, i thought it was strange too. It doesn't give me that error with the driver check, only when it is going through the install process of the exe.
Sometimes you need to treat your phone like a computer when it starts acting weird, save yourself some hassle and just do a format/factory reset and start fresh.
i used Doomlord's Rooting Toolkit: http://forum.xda-developers.com/show....php?t=1319653 it worked in 30 sec
Link to the exact Superoneclick you used? I tried the Doomloader link but it's broken.
is there an one click root 2.3.6 for the atrix? I tried the 2 programes but none of them seemed to work?
Same question here, thanks
http://briefmobile.com/motorola-atrix-4g-root
works for me with a locked bootloader.
There's also a voodoo root method that saves root before the update and restores root after the update.
gnahc79 said:
http://briefmobile.com/motorola-atrix-4g-root
works for me with a locked bootloader.
There's also a voodoo root method that saves root before the update and restores root after the update.
Click to expand...
Click to collapse
ok so now I screwed up and I am getting
svf 108 1:2
failted to boot 3
You got a failed to boot 3 using the fastboot preinstall method?? At which step did you get the error
Sent from my MB860 using XDA App
Ok, I'm on 2.3.4 and rooted using the instructions from brief mobile. I don't believe I have an unlocked bootloader. The only things I have done to the phone were original script from here for rooting (not one click), and then a modified version of it after the first Atrix update which had a before update and after update script to run.
Then, when upgrading to 2.3.4, I used the brief mobile/fastboot method to root it.
So, am I correct in thinking that to update the phone now I need to:
1. Download the update installer from Motorolla and update the phone to 2.3.6? (am I right that I the OTA update won't work or could cause a problem????)
2. Follow the instructions at Brief Mobile to root the phone.
Is this right, or should I wait a while before upgrading for things to be sorted out? The message popping up is irritating, but I can live with it if it avoids bricking my phone or having other problems.
Thanks
[Q] rooting help on 2.3.6
what is the proper way to root without unlocking the bootloader on 2.3.6 att?
http://briefmobile.com/motorola-atrix-4g-root
It still works
hdblab said:
http://briefmobile.com/motorola-atrix-4g-root
It still works
Click to expand...
Click to collapse
+1
Sent from my MB860 using XDA App
Root 2.3.6 one click
can someone upload a script or program that is one click root (not unlock) att atrix using 2.3.6?
http://forum.xda-developers.com/showthread.php?t=1505900
http://forum.xda-developers.com/showthread.php?t=1502735
http://forum.xda-developers.com/showthread.php?t=1500819
The preinstall method is real easy. If that is too challenging then maybe you should wait for someone to volunteer to provide a 1-click/batch script on their own rather than requesting(demanding) it.
sillyshyme said:
can someone upload a script or program that is one click root (not unlock) att atrix using 2.3.6?
Click to expand...
Click to collapse
I tried that before and I got soft booted.
Try again by using the instructions from the "Android-advice" website.
http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Note: In those instructions specifically, it is important clarify that the phone should be in "fastboot" before entering in commands. Basically, do "step 6" before "step 4".
sillyshyme said:
I tried that before and I got soft booted.
Click to expand...
Click to collapse
do you need to undo the root on 2.3.4 before you upgrade to 2.3.6?
przemeknzb said:
do you need to undo the root on 2.3.4 before you upgrade to 2.3.6?
Click to expand...
Click to collapse
yes
btw, before you unroot 2.3.4. can you check if you have su, dosu and superuser.apk in /system/preinstall/ ? I'm not sure if I had those files when I was on 2.3.4, but I see them now on 2.3.6. I only removed the su related files as listed in the link when I was on 2.3.4, never removed su, dosu, etc from system/preinstall...guess it's not necessary for the 2.3.6 OTA to be successful on a locked bootloader.
I just rooted my Atrix after the OTA to 2.3.6 using this method. Worked perfect.
http://androidadvices.com/root-motorola-atrix-4g-45141-gingerbread-236-firmware/2/
no not had any of those files
tnedator said:
Ok, I'm on 2.3.4 and rooted using the instructions from brief mobile. I don't believe I have an unlocked bootloader. The only things I have done to the phone were original script from here for rooting (not one click), and then a modified version of it after the first Atrix update which had a before update and after update script to run.
Then, when upgrading to 2.3.4, I used the brief mobile/fastboot method to root it.
So, am I correct in thinking that to update the phone now I need to:
1. Download the update installer from Motorolla and update the phone to 2.3.6? (am I right that I the OTA update won't work or could cause a problem????)
2. Follow the instructions at Brief Mobile to root the phone.
Is this right, or should I wait a while before upgrading for things to be sorted out? The message popping up is irritating, but I can live with it if it avoids bricking my phone or having other problems.
Thanks
Click to expand...
Click to collapse
1) unroot 2.3.4 first:
http://androidforums.com/atrix-4g-all-things-root/423259-best-way-unroot.html
2) apply the 2.3.6 OTA update
3) redo the fastboot preinstall root method
btw before you unroot 2.3.4 can you check to see if you have su, dosu and superuser.apk in /system/preinstall? I see it now in 2.3.6 and am not sure if I had it there back when I was on 2.3.4
I didn't unroot before updating to 2.3.6 and now I can't get it to work. I keep getting the error "cp: write error: No space left on device", what should I do now?
Thanks.
sillyshyme said:
is there an one click root 2.3.6 for the atrix? I tried the 2 programes but none of them seemed to work?
Click to expand...
Click to collapse
what i did ...
UPDATE FROM STOCK 4.2.91 UNLOCKED BOOTLOADER AND ROOTED ATRIX 4G
try using OTA keeper from the market , before trying the OTA update , this is what i did
1 ) i unlocked my atrix 4g (2.3.4 all stock) with AUTOMATIC_UNLOCK_V4.2 and rooted with PetesMotorolaRootTools_v1.07 after that i installed CWM recovery
2 ) Make a Full backup of you rom using CWM and Titaniumbackup (never is enough)
3 ) MANY people say that using RSD LITE is not good , i just take the risk , because anyways the touch of my atrix is not doing good so i will be sending it to warranty soon anyways , i take the risk , i flash my atrix with RSD Lite 5.5 and this sbf
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
i don´t know any other people but i did not loose any data or apps from my atrix it was everything there , unlocked sign erased , CWM recovery partition erased , ROOT was there it is like everything go back to stock ... almost everything my data part was untoched.
4 ) download from the market OTA Root Keeper make a backup of your root and then press unroot temp
5 ) with that done I started to download and install the OTA update
6 ) after this point the phonewill reboot to stock recovery mode and start to upgrade it took almost 10 min to do the update after finishing copying files, it restarted 2 times on the moto logo then started booting , it take a longtime to pass the att boot image be patience mine took almost 5 min after that the phonestarted with everything loaded my apps , photos videos etc.
I think this could be a workaround (it work for me) for updating to .141 , also the baseband was updated to N_01.77.37P_usa_att
The only thing that was untoched was the webtop part , it stays on WT 1.2, ireally don´t use it , but i think if im already on 2.3.6 i can RDS the full SBF to get Webtop upgraded also the kernel say 2.6.32.9 is that the correct kernel for 2.3.6 i read that kernel is for a Froyo sbf not pretty sure
The thing now is , i wanna try installing CWM recovery and see if im already "unlocked" and try fruitcakes to downgrade 2.3.4 but i am not pretty sure about this i think i will get a brick
Also , you can try investigate to downgrade of wait for a generous dev to take out of the oven the fruitcake for 2.3.6 and try the method above
I TAKE no responsibility with this mini-tuto for anything that could happen to your atrix it on you own do this , i take the risk and it works !!!
thanks everyone
I have a Galaxy Ace...which came with Android 2.2
My partner rooted it and everything was fine. At the same time he upgraded to Gingerbread 2.3.3
But a couple of weeks ago he upgraded it to Gingerbread 2.3.6....and now it says it is root...but it doesn't have access to the root only apps....and it doesn't show the Superuser app that is needed.
Somehow it seems to be in some sort of limbo between unrooted and rooted.
I am well confused. Can anyone out there help please.
It looks like that the latest GB ROM used for the upgrade does not have the root.
You can add root to it. Before you do that, check by using terminal app with su command if the phone is rooted or not.
Sent from my Amazon Kindle Fire using Tapatalk
Thank you....it sounds a bit technical.
I will get my partner to read it in a while.
Although it sounded like I KNOW what I am on about...I am, in fact, a complete beginner when it comes to Android.
Updating from kies or from odin will make your phone unroot again. U need to reroot.
Sent from your phone
julado said:
I have a Galaxy Ace...which came with Android 2.2
My partner rooted it and everything was fine. At the same time he upgraded to Gingerbread 2.3.3
But a couple of weeks ago he upgraded it to Gingerbread 2.3.6....and now it says it is root...but it doesn't have access to the root only apps....and it doesn't show the Superuser app that is needed.
Somehow it seems to be in some sort of limbo between unrooted and rooted.
I am well confused. Can anyone out there help please.
Click to expand...
Click to collapse
a stock rom update resets your phone to most basic version..all things gone root,,clockworkmod etcc.....
u need to re-root follow this thread---
http://forum.xda-developers.com/showthread.php?t=1034145
happy rooting..
Root issue on Ace...
Hello all! I am Julado's partner. I had better explain what this is about in more detail here...
I took the original OS (Froyo) and updated it to Gingerbread (2.3.3) via Kies, I then used SOC to root it using ChainFire method - then installed and performed a TB back up. ALL Good - a few weeks later - I flashed an update using Odin to get 2.3.6 and an updated version of CF's kernel. At THAT point, CWM recovery had root access - but fully booted GingerBread had no SU app or returned root status via test command (both using a script and terminal). Sys info in settings shows 2.3.6 and ROOTED kernel image, but NO ROOT ACCESS is there in GB ~ Just in CWM Recovery.
I have re-flashed the CF kernel a few times and STILL have the same situation. I cannot understand why CWM has ROOT access but FULL 2.3.6 system doesn't.
Can anyone offer my any help please? Or possibly point out the blindingly obvious if I have missed what's clearly staring me in the face! Thanks.
So u already flashed ketut's cfroot kernel and still doesn't have root access in the rom? Thats weird.
Btw kernel name in system settings even if it said root doesnt mean your rooted. thats the build host of the kernel compiler.
Sent from your phone
When you are in GB, you can't root your ace via SOC. It will look success, but actually it's not. You have to root it using update.zip and flash via recovery. Just find it by googling.
Sent from my GT-S5830 using Tapatalk
an0nym0us_ said:
So u already flashed ketut's cfroot kernel and still doesn't have root access in the rom? Thats weird.
Btw kernel name in system settings even if it said root doesnt mean your rooted. thats the build host of the kernel compiler.
Sent from your phone
Click to expand...
Click to collapse
Thanks for the speedy reply!
I understand that the settings name is from build compiler. I have tested for root access with terminal and various apps (even tried downloading & installing SU app myself!!) - but don't understand why CWM DOES have root - but full OS doesn't!
I am truly baffled ATM!
mikeybaby72 said:
Hello all! I am Julado's partner. I had better explain what this is about in more detail here...
I took the original OS (Froyo) and updated it to Gingerbread (2.3.3) via Kies, I then used SOC to root it using ChainFire method - then installed and performed a TB back up. ALL Good - a few weeks later - I flashed an update using Odin to get 2.3.6 and an updated version of CF's kernel. At THAT point, CWM recovery had root access - but fully booted GingerBread had no SU app or returned root status via test command (both using a script and terminal). Sys info in settings shows 2.3.6 and ROOTED kernel image, but NO ROOT ACCESS is there in GB ~ Just in CWM Recovery.
I have re-flashed the CF kernel a few times and STILL have the same situation. I cannot understand why CWM has ROOT access but FULL 2.3.6 system doesn't.
Can anyone offer my any help please? Or possibly point out the blindingly obvious if I have missed what's clearly staring me in the face! Thanks.
Click to expand...
Click to collapse
Sits and grins at screen.....having absolutely NO idea what any of this post means
Would anyone like me to KNIT them an Android
hallidafykzir said:
When you are in GB, you can't root your ace via SOC. It will look success, but actually it's not. You have to root it using update.zip and flash via recovery. Just find it by googling.
Sent from my GT-S5830 using Tapatalk
Click to expand...
Click to collapse
I did get FULL root access after using SOC to root (chainfire method) GB - I rooted 2.3.3 with SOC, NO PROBLEMS! - THEN made TB (needs root) successfully. It was only after using Odin to flash 2.3.6 that SOC root resulted in the current quasi-rooted state.
I have tried re-flashing CF kernel both using Odin AND via CWM (update.zip) method - Neither worked = STILL BAFFLED???!