I need to sell my atrix, so I wiped using the CWM, now it doesn't show the SU anymore. does this mean i'm not rooted anymore? When I go to settings it says OLYFR_U4_1.5.7. If I'm not rooted anymore, do I just start with the Gladroot process? Or do i have to start all over again? the phone's going to be picked up tomorrow and I said it's rooted =s
Run an app that "requires root" like Titanium Backup. That will tell you if your phone is rooted or not...
Sent from my MB860 using XDA App
nope, it doesn't sideload anymore. i used to do this with my captivate. wipe with CWM and then i'd still be rooted. do i have to flash back to 1.2.6 and start the process all over again?
tepickytoo said:
nope, it doesn't sideload anymore. i used to do this with my captivate. wipe with CWM and then i'd still be rooted. do i have to flash back to 1.2.6 and start the process all over again?
Click to expand...
Click to collapse
Just to let you know, I don't have the AT&T version. (I have the Bell)
With that said, I've been following the Gladroot thread for both phones. Currently I'm rooted with Bell using Gladroot.
My suggestion is to "carefully" follow the checklist in the Gladroot thread to get root again:
http://forum.xda-developers.com/showthread.php?t=1016060
Especially when it says --> "If you are already on 1.57 and do not have root, you MUST flash back to 1.26 for this to work. NO EXCEPTIONS."
^ So with that said it looks like you need to get back to 1.26 before gaining root again.
Most importantly, be slow and take your time. I've soft bricked a phone in the past when I was in a rush and skipped a step.
Best of luck!...
wiping is known to remove root for 4.1.57, so you will need to so the whole process again going back to 4.1.26.
Ahhhh. I see. I've started the process, i'm on the gladroot atm. Thanks for all the help guys!
Related
So I picked up an ATT Atrix 4g the other day and I love it! Last cell's were a BlackBerry and before that an iPhone. Android OS blows those away. So I am the tinkering type and want to root and use custom ROM (greyblur). Currently I am upto date (version 4.1.83). From what I read here, I need to flash back to 1.26 via this guide (http://forum.xda-developers.com/showthread.php?t=991072). Installed RSDlite, passworded file, removed sim card, memory card, booted with RSD support, opened RSDlite, selected file (extracted to c:\GladRoot...also tried directly into c, Start. Created the image, it rebooted my atrix, and then the Status threw this message:
"Failed flashing process. failed flashing process. Phone did not re-enumerate after RAM-downloader was sent. (0x703E); phone disconnected.
Progress: Exectuded 100%
Result: FAIL
So was am I missing here? I am on version 4.1.83, but there is reference to 1.2.6 and 1.5.2...I assume these numbers are the firmware revision/version? So as I take it I need to "downgrade" from 4.1.83 to 1.26....? I am kinda lost here. Any help in the right direction would be great.
Look here to root your Atrix http://forum.xda-developers.com/showthread.php?t=1016060
1) Where can I verify that I am on 1.2.6 on my Atrix?
2) I ran the gladroot.bat as admin (win7 user) and got:
waiting for root access to kick in...
psneuter failed to execute properly
I extracted gladroot to c:\gladroot
Any thoughts?
Did you try to use Gingerbreak?
This is really easy, i got no problem with that...
Also, I think you need to install motorola usb windows driver to use rsdlite...
No I didnt try gingerbreak.
I do have the Moto USB drivers installed.
Settings>about phone>build number
Will show if you are on 4.1.26
When it comes to the psneuter fail, I had an issue with that too I believe. Try battery pull/restart. Make sure phone is fully charged. Make sure to right click and run it as admin. Other then that, I don't know what else to suggest.
Edit: if you have any system apps frozen with titanium backup, try unfreezing them and also make sure you have the home motoblur launcher unfrozen if you are flashing an sbf.
Sent from my MB860 using XDA App
lhurtado said:
Did you try to use Gingerbreak?
This is really easy, i got no problem with that...
Also, I think you need to install motorola usb windows driver to use rsdlite...
Click to expand...
Click to collapse
Please tell me a way to unroot after rooting with ginger break?
Sent from my MB860 using XDA App
Jazor28 said:
Please tell me a way to unroot after rooting with ginger break?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Flash sbf.
Sent from WinBorg 4G via XDA premium app
why do not root with gingerbreak?
briefmobile[dot]com/motorola-atrix-4g-root - this is even a link i found on xda-dev
i want my device rooted too, but noneed to flash back, flash up, flash back blabla?
gingerbreak sounds much more easier for me - why you guys recommend gladroot? whats the diffrence? is gingerbreak that bad?
Backing out gingerbreak - "flash sbf"?
CaelanT said:
Flash sbf.
Sent from WinBorg 4G via XDA premium app
Click to expand...
Click to collapse
So what does this really mean? I used gingerbreak after superoneclick hung on psneuter. Phone rebooted after gingerbreak, but superuser app was nowhwere to be seen. I got cold feet and did a factory reset thinking this was all I needed to undo what gingerbreak (and superioneclick?) did. EasyTether now hangs when disabling to I think something is broken.
using gingerbreak to root is real simple I can't post a URL, but briefmobile has instructions on how to do so using gingerbreak. briefmobile.com/motorola-atrix-4g-root
Gingerbreak and Gladroot are equally good. Some don't like Gingerbreak as it can wipe internal sdcard.
Beamed in from WinBorg 4G via XDA Premium app
Hi, just installed the new BELL OTA update that is now available. If you have not received it, go to Settings -> About Phone -> System Update.
To Root, download GingerBreak from this thread:
http://forum.xda-developers.com/showthread.php?t=1044765
You will need v1.20 - install, enable USB Debugging, and wait. It took around 1 minute on my phone. Afterwards, if you were not rooted previously, download SuperUser from the market.
Can confirm this method works. First try did not work; rebooted unmounted formatted SD card, remouted. Then retried gingerbreak. 1 min approx to root, root confirmed with superuser.
Downloading now...
What about gladroot? It doesn't work?
Glad root will work, frozenfish is left intact in /osh/sbin.
(That's just the su binary with a different name, but the right permissions, you can adb shell, and type /osh/sbin/frozenfish and have a root shell.)
Cheers!
Worked for me. Takes a few good minutes so be patient.
Yeah, works fine to root and unroot, just have to be patient and wait.
NFHimself said:
Glad root will work, frozenfish is left intact in /osh/sbin.
(That's just the su binary with a different name, but the right permissions, you can adb shell, and type /osh/sbin/frozenfish and have a root shell.)
Cheers!
Click to expand...
Click to collapse
I just updated (37.23) yesterday, there is no /osh/sbin/frozenfish on my Atrix
Now running Blur_Version.0.37.23.MB860.BellMobility.en.CA (build OLYLA_U4_0.37.23)
I had used GladRoot 4.3 to previously root the device. Now I'm wondering if it's going to be safe to run Gingerbreak 1.2 - anyone in the same scenario ?
daymz said:
I just updated (37.23) yesterday, there is no /osh/sbin/frozenfish on my Atrix
Now running Blur_Version.0.37.23.MB860.BellMobility.en.CA (build OLYLA_U4_0.37.23)
I had used GladRoot 4.3 to previously root the device. Now I'm wondering if it's going to be safe to run Gingerbreak 1.2 - anyone in the same scenario ?
Click to expand...
Click to collapse
Just thought I'd report that I successfully ran Gingerbreak 1.20 on 37.23 (after having used GladRoot on 37.4) and everything seems OK, I'm back in root mode.
nikechristo said:
What about gladroot? It doesn't work?
Click to expand...
Click to collapse
I used Gladroot for the initial FW version, but I didn't want to chance that it may not work or cause any issues like SuperOneClick. I went with Gingerbreak just to be safe.
Put me on the list of the list confirming that Gingerbreak works with this FW...
Hi I tried to use Gingerbreak but the application was running for about 20 minutes and then it crashed. I was wondering if this root app worked for everybody and if maybe I'm doing something wrong.
I'm have a Bell Atrix with the latest firmware.
Any information or suggestion/solution would be appreciated!!!
heptic buttons
Anyone having issues with their backlighting? Mine seems dim and sometimes don't come on.
Thanks
Just ran on 37.23. Works! Only took a minute.
Can confirm this works on bell 2.2.2. This indeed deleted my internal sd data though, so make sure to back up before proceeding.
Sent from my MZ604 using XDA Premium App
I just have a quick question about using Gingerbreak on my Atrix running this newest firmware.
Do I absolutely need an SD card in the phone?
I don't have one so I was wondering if I can stil do it or I need to go out and get one tomorrow?
Thanks!
You need one definately.
Successful 37.23 update - unsuccessful root.
I've just ran the the bell 37.23 update.
I managed to gain root access again after running super one click.
However after I factory reset the phone all my root applications stopped working.
Super user was still in the app drawer, but titanium backup was saying it didn't have root access. (along with every other root app)
I tried rooting/unrooting the phone again with super one click and every time it hangs on "Running psneuter..."
I also tried rooting with GingerBreak and it just stays on the "Running exploit..." screen.
Any suggestions?
I had a new phone on 2.3.4. The first thing I tried to do was to unlock it by RSD flashing the unlock sbf from the main pudding thread (http://forum.xda-developers.com/showthread.php?t=1136261).
The initial process seemed to go okay, but I think when the phone was supposed to reboot, it ended up giving me a boot failure message (0x1000, if I remember correctly).
So, I tried the "fastboot oem unlock" command anyway, and it worked.
I tried to RSD flash the full 2.3.4 sbf from brandon15811's thread, but RSD gave an error, something about not being able to find the handle or something.
So, the next thing I did was to see if I could flash RomRacer's CWM via fastboot, and that seemed to work, too.
After that, if I tried to reboot, I would get the motorola startup screen and the word "unlocked", but it just seems to stay there.
I'm about to see if I can use the recovery to flash the full 2.3.4 sbf from here (http://forum.xda-developers.com/showthread.php?t=1138204).
Is that the right way to try to fix this, or is there something else I should try?
Haphim said:
I had a new phone on 2.3.4. The first thing I tried to do was to unlock it by RSD flashing the unlock sbf from the main pudding thread (http://forum.xda-developers.com/showthread.php?t=1136261).
The initial process seemed to go okay, but I think when the phone was supposed to reboot, it ended up giving me a boot failure message (0x1000, if I remember correctly).
So, I tried the "fastboot oem unlock" command anyway, and it worked.
I tried to RSD flash the full 2.3.4 sbf from brandon15811's thread, but RSD gave an error, something about not being able to find the handle or something.
So, the next thing I did was to see if I could flash RomRacer's CWM via fastboot, and that seemed to work, too.
After that, if I tried to reboot, I would get the motorola startup screen and the word "unlocked", but it just seems to stay there.
I'm about to see if I can use the recovery to flash the full 2.3.4 sbf from here (http://forum.xda-developers.com/showthread.php?t=1138204).
Is that the right way to try to fix this, or is there something else I should try?
Click to expand...
Click to collapse
If you have cwm just use samcripp's fruitcakes and see if that works.
Sent from my MB860 using XDA Premium App
msd24200 said:
If you have cwm just use samcripp's fruitcakes and see if that works.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I haven't confirmed it works yet, but if it does, why those builds instead of brandon15811's?
Haphim said:
I haven't confirmed it works yet, but if it does, why those builds instead of brandon15811's?
Click to expand...
Click to collapse
Sbf flashing is dangerous and not recommended
Sent from my MB860 using XDA Premium App
Unlocking an atrix already on 2.3.4 will give you a soft brick, its been confirmed many times. No way around it. Find the fruit cakes thread as msd24200 stated. Any recovery will work. If you do the full 2.3.4 sbf you can't rds back to an older build our even if you try the 2.3.4, that would give you a hard brick. If your unlocked just go for one of the great roms available.
Sent from my MB860 using XDA App
Dirtburgler said:
Unlocking an atrix already on 2.3.4 will give you a soft brick, its been confirmed many times. No way around it. Find the fruit cakes thread as msd24200 stated. Any recovery will work. If you do the full 2.3.4 sbf you can't rds back to an older build our even if you try the 2.3.4, that would give you a hard brick. If your unlocked just go for one of the great roms available.
Click to expand...
Click to collapse
I did a lot of reading before doing this, and somehow, I never came across that particular fact. Ai! Well, thank you for pointing that out!
So, here's a question then... I have another phone that has 1.83 on it. What's the best way to upgrade that to 2.3.4, unlocked and rooted? Should I follow the same path I did here, do the OTA update, unlock and brick via the unlock sbf, flash a recovery, then apply a fruitcake?
Or is there a better way? I've heard that the 2.3.4 update resizes the partitions, and that seems like a good thing, so I'm not sure I want a path that avoids that.
What do you think?
Haphim said:
I did a lot of reading before doing this, and somehow, I never came across that particular fact. Ai! Well, thank you for pointing that out!
So, here's a question then... I have another phone that has 1.83 on it. What's the best way to upgrade that to 2.3.4, unlocked and rooted? Should I follow the same path I did here, do the OTA update, unlock and brick via the unlock sbf, flash a recovery, then apply a fruitcake?
Or is there a better way? I've heard that the 2.3.4 update resizes the partitions, and that seems like a good thing, so I'm not sure I want a path that avoids that.
What do you think?
Click to expand...
Click to collapse
why bother to update if you're going to downgrade it again?
the unlocker SBF if 1.8.3, and the phone is on 1.8.3, so flash that. then install 2.3.4 via CWM with a fruitcake. done.
dLo GSR said:
why bother to update if you're going to downgrade it again?
the unlocker SBF if 1.8.3, and the phone is on 1.8.3, so flash that. then install 2.3.4 via CWM with a fruitcake. done.
Click to expand...
Click to collapse
Unce I've unlocked the phone on 1.8.3, would it be better to do the OTA update for 2.3.4, and then root? Is this even possible?
One important question, if I apply the CWM fruitcake over 1.83. will it resize the partitions the way the OTA update would?
Haphim said:
Unce I've unlocked the phone on 1.8.3, would it be better to do the OTA update for 2.3.4, and then root? Is this even possible?
One important question, if I apply the CWM fruitcake over 1.83. will it resize the partitions the way the OTA update would?
Click to expand...
Click to collapse
I don't believe so, someone correct me if I'm wrong, but in all honesty there is no reason to use fruitcakes if you don't plan on going back to an older build. Even if you mess something up flashing roms you can go into recovery and restore a backup and your good to go. The only way I've seen a hardbrick is from going back with rsd.
I would unlock then ota to 2.3.4 then install romracers cwm and then your free to flash pre rooted stock roms or cherry (3.14) or alien rom.
Sent from my MB860 using XDA App
Nevermind 10char
I could see flashing back to an older build beneficial to a developer but not your everyday user and rom flasher. Both methods will get you to the same place, fruitcake or ota. I know there are benefita doing the ota like partition size and some other tweaks but I'm not 100% what those benefits are.
I jumped in early and got the leaked ota before we knew of the hard brick issue and like I said I'm still rocking the same atrix I bought back in march.
Sent from my MB860 using XDA App
Dirtburgler said:
I don't believe so, someone correct me if I'm wrong, but in all honesty there is no reason to use fruitcakes if you don't plan on going back to an older build. Even if you mess something up flashing roms you can go into recovery and restore a backup and your good to go. The only way I've seen a hardbrick is from going back with rsd.
I would unlock then ota to 2.3.4 then install romracers cwm and then your free to flash pre rooted stock roms or cherry (3.14) or alien rom.
Click to expand...
Click to collapse
Thanks! If that's an okay route to take, then that's what I'll do.
Please help!!!! I think I may have screwed up. I am running HoneyVillian 1.2 Rom on my a500. I inadvertently used the unroot option on the Gingerbreak app. Now I can't re-root my tablet. Am I screwed? What can I do to get back root. Please help....
Just boot into cwm and restore a backup that you made that had root on it
Sent from my A500 using xda premium
I can't get to recovery. When I hold down power and vol I get the bee icon and it freezes. Any they way that I can access clockwork?
is my problem the fact that I unrooted an android 3.2 Rom? What can I do? CAN 3.2 even be rooted? I'm stuck with an unrooted version of Honeyvillian?
Epic..... what goes through people's minds....
I would think that uninstalling the current gingerbreak apk, then reinstalling it fresh probably won't work. So I guess the only option, is to do the rollback procedure to 3.1, and this time, you can use IconiaRoot apk.
http://forum.xda-developers.com/showthread.php?t=1276227
Don't fix what ain't broke.
yep......that's what I ended up doing. Worked fine. Hopefully I can limit future brain farts!!!!!!!
Thanks to all.
jbmmurph said:
yep......that's what I ended up doing. Worked fine. Hopefully I can limit future brain farts!!!!!!!
Thanks to all.
Click to expand...
Click to collapse
No Problem! (we all have brain farts on occassion)
Which method did you use? Re-installing the apk? Or the rollback to 3.1?
Did the roll back the iconia root. Worked like a champ.
I know there have been varying posts on the subject, but I thought I would share my experience with the update. I originally started out on a bootloader unlocked, rooted, At&t branded Atrix. I had installed the 2.3.4/4.5.91 fruitcake previously and had been using it for some time. When the update came down I rolled back to stock recovery using fastboot and after the installation of the update, the phone gave me an failed to boot 4. I used rsd to flash the official 2.3.4/4.5.91. I received a failed to boot 1. (After going to launder my, now soiled, trousers) I noticed that when I plugged the phone in, RSD still recognized the phone, even though it did not show the "entering RSD mode" tag. It occured to me to attempt to flash pudding using the 4.2 auto unlock. Immediately after flashing pudding the phone booted up and everything was working fine.
At this point I rooted and installed clockwork on the phone using the same 4.2 tool. I then used Voodoo OTA Rootkeeper to back up my root. Unfortunately the tool installs clockwork in order to root the phone, so I had to flash back to stock recovery using fastboot. . I then booted, downloaded, and then installed the update.
After the update the phone rebooted, and gave me "failed to boot 2, starting RSD mode". At which point I installed pudding again using the tool. Rebooted after having installed pudding, the phone booted beautifully. I used OTA Rootkeeper to restore my root after the boot. Everything is working fine and it is on current version 4.5.141. I hope this helps someone else, or maybe someone to find a more simple, straight-forward way of doing this.
Doogiedoo said:
I know there have been varying posts on the subject, but I thought I would share my experience with the update. I originally started out on a bootloader unlocked, rooted, At&t branded Atrix. I had installed the 2.3.4/4.5.91 fruitcake previously and had been using it for some time. When the update came down I rolled back to stock recovery using fastboot and after the installation of the update, the phone gave me an failed to boot 4. I used rsd to flash the official 2.3.4/4.5.91. I received a failed to boot 1. (After going to launder my, now soiled, trousers) I noticed that when I plugged the phone in, RSD still recognized the phone, even though it did not show the "entering RSD mode" tag. It occured to me to attempt to flash pudding using the 4.2 auto unlock. Immediately after flashing pudding the phone booted up and everything was working fine.
At this point I rooted and installed clockwork on the phone using the same 4.2 tool. I then used Voodoo OTA Rootkeeper to back up my root. Unfortunately the tool installs clockwork in order to root the phone, so I had to flash back to stock recovery using fastboot. . I then booted, downloaded, and then installed the update.
After the update the phone rebooted, and gave me "failed to boot 2, starting RSD mode". At which point I installed pudding again using the tool. Rebooted after having installed pudding, the phone booted beautifully. I used OTA Rootkeeper to restore my root after the boot. Everything is working fine and it is on current version 4.5.141. I hope this helps someone else, or maybe someone to find a more simple, straight-forward way of doing this.
Click to expand...
Click to collapse
Thanks for the info. Do you mind if I re-post in this thread over in the dev forum? I noticed your post count is too low to post over there.
I just got my phone back from Motorola after they fixed a shattered screen. I had sent it in with an unlocked BL, running a CM7 kang. They sent it back running stock .141.
Since I didn't do the update, I had no idea how to proceed re-unlocking it. But it sounds like between you and Nottach, I should be ok with the pudding unlocker(knock on wood).
how did you get rid of superuser on fruitcake?
ghost_og said:
Thanks for the info. Do you mind if I re-post in this thread over in the dev forum? I noticed your post count is too low to post over there.
I just got my phone back from Motorola after they fixed a shattered screen. I had sent it in with an unlocked BL, running a CM7 kang. They sent it back running stock .141.
Since I didn't do the update, I had no idea how to proceed re-unlocking it. But it sounds like between you and Nottach, I should be ok with the pudding unlocker(knock on wood).
Click to expand...
Click to collapse
Not at all, if it's any use to anyone, feel free to repost it. Also, I had a hardware problem (screen banding) on my atrix and sent it back for repairs. When it was returned, it no longer showed unlocked. The bootloader was still unlocked, but I had to reapply the unlock sbf to get it to show again (before using another rom).
ummkiper said:
how did you get rid of superuser on fruitcake?
Click to expand...
Click to collapse
I still had it installed on fruitcake, but lost it (well, rather lost root access, as the app "superuser" is still there but not functional) when I installed the sbf file initially. I'm not sure if flashing pudding or using the automatic unlock on the fruitcake initially would have worked. I didn't think to try it initially.
Cool,thanks for the info.
Sent from my Nexus One using xda premium