I finally gave in to the update nagging screen and tried to update.
My phone was rooted with preinstall method, nothing else.
I was on 2.3.4 (4.5.91).
I installed RootKeeper and unrooted before the update (kept root backup).
The phone downloaded the update, restarted, and I saw the Android Icon and an "unpacking" progress bar. The bar stopped about half way and the icon turned into an exclamation point. I thought I was toast....
The phone rebooted fine, everything still there. I got a message box "Update failed" once I got on my home screen. The phone is still 2.3.4. The update nagging is gone.
I have pretty rare reboots, maybe 2 a month. I am quite happy with it.
Anyone had the same issue? Should I even bother going to 2.3.6?
The only thing I am really missing on the Atrix is HDMI mirroring option with 720p or 1080p up-conversion.
How can I get the cause for the "fail"? Should I use the Moto USB method?
I wouldnt mind going to CM9 but I want the Finger Sensor, Camera etc all to work. I dont want to loose any current functionality going to CM9 and its not there yet, correct?
Thanks!
I would just stay where you are at. Unless you really want the mirroring. You seem to not mind stock so I would wait for Moto to release ICS for the Atrix. They put it on the list.
if you only rooted, did nothing else that requires root (freeze apps, put files in /system, etc) and did not unlock the bootloader, just unroot and then apply the 2.3.6. update.
Code:
1. Open Android Terminal Emulator (ADB)
2. Type in the following commands, hitting ENTER after each line of code: (after typing 'su' below, look for the Superuser request and approve it, you can only continue if you get the # prompt.
Code:
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o rw,remount /dev/block/mmcblk0p17 /preinstall
rm /system/bin/su
rm /preinstall/sqlite3
rm /preinstall/dosu
rm /preinstall/Superuser.apk
rm /preinstall/su
reboot
3. Let the phone reboot fully and then go into Settings > Applications > Manage Applications > find Superuser and uninstall it just like any other app.
thx guys,
so you are saying that it failed because the unroot in rootkeeper did not do it right?
so with the manual unroot it should work? is there anyway to see why the update failed? log file or smth?
Thanks
spacev said:
thx guys,
so you are saying that it failed because the unroot in rootkeeper did not do it right?
so with the manual unroot it should work? is there anyway to see why the update failed? log file or smth?
Thanks
Click to expand...
Click to collapse
There have been posts in various 2.3.6 threads where rootkeeper did not work if you used the fastboot preinstall method.
It should work if you manually unroot as long as everything else is stock.
for seeing why the update failed, hold the Volume up and power button when the error appears and you should see some sort of error msg...never tried it myself though.
I have the same issue. I used the preinstall root as well as unroot. I have not found a way to install the update. I tried OTA (I am locked) and I also tried to install from SD.
No dice
otter9309 said:
I have the same issue. I used the preinstall root as well as unroot. I have not found a way to install the update. I tried OTA (I am locked) and I also tried to install from SD.
No dice
Click to expand...
Click to collapse
Did you undo everything that requires root access prior to applying the OTA? I usually do the following prior to an OTA (and redo once the OTA is applied):
uninstall Swype beta, restore stock Swype files (the so and apk files)
move ringtones out of /system/media
Help Needed
Hi All,
I am a newbie here and I am not sure if my question makes any sense. Couple weeks back, I bought an Atrix 4g (US version), an unlocked version (the seller told me that this phone is unlocked using AT&T code) and I am using it with Vodafone (India) sim. It works perfectly and so far I didnt face any problems with this phone. But last week, I got an alert in phone saying that software update (2.3.4.5.141) is available for AT&T users and enable wifi to download. However, I didnt download and install the update as I was not sure why is it saying the update is available only for AT&T users. Also wherever I read about this software udpate, the name 'AT&T users' come along with that.
So my doubt here is, what will happen if I, who is not an AT&T user, download and install the software update in my phone ? will it cause any issues in the phone (like getting locked again or bricking the phone)
I have not done any modification like rooting or installing custom ROM and things like that and I am using the phone as I recieved it.
Thanks in advance for your help.
-Qaddaffi
Related
After I installed the firmware update, via Odin, i can't seem to re-root my phone. I re-installed the update, renamed the zip, flashed it and no smoke. I'm kind of new with all of this so what do i do to access root at this point?
Also, I re-downloaded the superuser app from the market and it stated that there was a new version available. The app states" an error occurred and su was not updated. A zip(su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary. " I tried to flash this recieved an error message saying that the zip was "(bad)". What do I do?
did not have a problem with ryans one touch lag fix that also takes care of root
I'm having the same problem. Also new to this so I'm sure it's going to be something simple. But it's dricing me crazy. I'm sooo close. Anyone with advice it would be much appreciated.
sorry I forgot to say that I have the Epic 4g
aaconteh said:
After I installed the firmware update, via Odin, i can't seem to re-root my phone. I re-installed the update, renamed the zip, flashed it and no smoke. I'm kind of new with all of this so what do i do to access root at this point?
Also, I re-downloaded the superuser app from the market and it stated that there was a new version available. The app states" an error occurred and su was not updated. A zip(su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary. " I tried to flash this recieved an error message saying that the zip was "(bad)". What do I do?
Click to expand...
Click to collapse
The Superuser app from the market isn't going to give you superuser privileges without the phone being rooted. That's why you are rooting the phone in the first place.
As I've made a habit of experimenting with every ROM known to man I've gotten this down to a routine when it comes to flashing and re-rooting. And a big part of my routine is using TGA_Gunnman's handy One Click ROOT Windows application (also a mac version available in the same thread)...
http://forum.xda-developers.com/showthread.php?t=739300
Just use it and follow the instruction. Biggest thing is to make sure the phone has USB Debugging enabled and that the internal and external SD's are NOT MOUNTED. Just click the ROOT ME button, look in the shell window to see that the update.zip has been pushed successfully, use the vol rocker keys to select REINSTALL PACKAGES, and reboot.
It's never failed for me so far, and I've re-rooted dozens of times now.
Best of luck!
DemDonkies said:
sorry I forgot to say that I have the Epic 4g
Click to expand...
Click to collapse
The root method for the Epic4g is a tad different...and located in another forum...
http://forum.xda-developers.com/showthread.php?t=770388
Stock 2.1 -> Rooted that with Ryan's OCLF
Did Lag Fix V1 cause V2 didn't work..
Everything ran..and ran... then that OTA update came while I was at school
It kept installing then restarting and looping itself...Finally I believe it installed and stopped asking me to reinstall.
My phone shows it has the Update, yet my phone isnt rooted anymore...Yet I still have the lag fix installed. I tried running the update.zip in recovery and it says signature failure. I try booting into clockwork to apply that update ROM that is posted and nothing happens. I hit boot into Recovery with ROM Manager and nothing happens.. I'm really confused..It's like I have partially rooted things like Lagfix on yet I'm not rooted and I cant root my phone ??
Anyone got an idea?
Thank you everyone.
Um, I think you're confused about what root really is. Being rooted just means that you have permissions (and the applications necessary) to modify protected areas of the OS. Even if you lost root access, the lag fix remains because the filesystem modifications to put it in place are already done. The extra commands it adds are run by the system itself during boot up, which of course has root access. It's not like an app that needs to request root access via Superuser every time it runs.
I'm not sure what has actually happened to your phone, but I would recommend rooting the old-fashioned way, via advanced commands, so that you don't have to deal with any recovery issues. If that doesn't work, you may have to flash back to factory stock and start over again.
Sent from my SCH-I500 using XDA App
johnz1 said:
Stock 2.1 -> Rooted that with Ryan's OCLF
Did Lag Fix V1 cause V2 didn't work..
Everything ran..and ran... then that OTA update came while I was at school
It kept installing then restarting and looping itself...Finally I believe it installed and stopped asking me to reinstall.
My phone shows it has the Update, yet my phone isnt rooted anymore...Yet I still have the lag fix installed. I tried running the update.zip in recovery and it says signature failure. I try booting into clockwork to apply that update ROM that is posted and nothing happens. I hit boot into Recovery with ROM Manager and nothing happens.. I'm really confused..It's like I have partially rooted things like Lagfix on yet I'm not rooted and I cant root my phone ??
Anyone got an idea?
Thank you everyone.
Click to expand...
Click to collapse
Flash CMW recovery via Odin. Then do the following..
adb shell (you should have the # prompt, if not su)
cd /system/xbin (or /system/bin if your files are there)
chmod 4755 su
chmod 4755 busybox
all done.
Thankyou very much brandon
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.
HI,
I am unable to mount /system as r/w in root explorer or other apps. When they load it asks SpuerSU for permissions which are granted.
I am trying to install xposed installer which fails and asks (are you root?)
I originally rooted my Z2 when it was first released, then when the 4.4.4 update became available in the UK i restored stock recovery so i could update. When the Phone rebooted I found I still had root. I can get a # prompt in terminal emulator and apps like folder mount work fine.
Has something messed up somewhere? I tried reinstalling SuperSU to no avail.
Thanks
stubbadub said:
HI,
I am unable to mount /system as r/w in root explorer or other apps. When they load it asks SpuerSU for permissions which are granted.
I am trying to install xposed installer which fails and asks (are you root?)
I originally rooted my Z2 when it was first released, then when the 4.4.4 update became available in the UK i restored stock recovery so i could update. When the Phone rebooted I found I still had root. I can get a # prompt in terminal emulator and apps like folder mount work fine.
Has something messed up somewhere? I tried reinstalling SuperSU to no avail.
Thanks
Click to expand...
Click to collapse
Have you tried to downgrade to 4.4.3 and make a rooted flashable zip with 4.4.4??
Might work. Havent tried Root explorer, cuz FileCommander works fine with root...
bjorn96 said:
Have you tried to downgrade to 4.4.3 and make a rooted flashable zip with 4.4.4??
Might work. Havent tried Root explorer, cuz FileCommander works fine with root...
Click to expand...
Click to collapse
I have just run the Easyroot Tool again and this seems to have solved it. :good:
stubbadub said:
I have just run the Easyroot Tool again and this seems to have solved it. :good:
Click to expand...
Click to collapse
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
stonegroover said:
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
Click to expand...
Click to collapse
My bootloader came unlocked on the phone. I bought the phone when it was released. I rooted and when 4.4.4 firmware was released it initially failed to update OTA. I had to remove the dual recovery. The OTA then worked fine and i still had root. However i could not mount the /system folder as R/W/. I just ran easyroot again and this solved it.
stonegroover said:
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
Click to expand...
Click to collapse
NC not working happened to me too. But only in niaboc79's version (and by this I mean the Russian OTA). I also tried the OTA and all was good. But after that I lost my root and tried to restore it (I ran the restore-mount script). This script messed things up. Instead of looking into that, I tried different approaches (niaboc79's / .314+root+script) except check if it was because of the the script .
If you have root now, install the dualrecovery and dirty flash for example shockss pre-rooted .267 and run the script. Stock .267, everything working but pre-rooted. Ow and 4G icon = LTE icon.
stubbadub said:
I have just run the Easyroot Tool again and this seems to have solved it. :good:
Click to expand...
Click to collapse
Thank you, this method worked for me too !
Actually I couldn't run the whole Easyroot tool (got stuck at creating vm) so I just ran the important part which is where it pushes files/installmount.sh with
Code:
adb push files/installmount.sh /data/local/tmp
And then executes it with
Code:
adb shell "su -c /data/local/tmp/installmount.sh"
pec0ra said:
Thank you, this method worked for me too !
Actually I couldn't run the whole Easyroot tool (got stuck at creating vm) so I just ran the important part which is where it pushes files/installmount.sh with
Code:
adb push files/installmount.sh /data/local/tmp
And then executes it with
Code:
adb shell "su -c /data/local/tmp/installmount.sh"
Click to expand...
Click to collapse
Mine sticks at creating the VM too. So the code you've quoted is all you need? I opened up the .bat file to have a look and those lines of code are only 2 of many, and only around half way through the file- I'm looking at it thinking there's got to be more to it than that, it can't be that simple......
stonegroover said:
Mine sticks at creating the VM too. So the code you've quoted is all you need? I opened up the .bat file to have a look and those lines of code are only 2 of many, and only around half way through the file- I'm looking at it thinking there's got to be more to it than that, it can't be that simple......
Click to expand...
Click to collapse
If you only want to fix the system not mounting then yes, it's only this. The rest of the script is an exploit to gain root and install su but you don't need it since you already have it.
If you are looking for a full root method these two lines are not enough. In this case I suggest you try another rooting tool.
pec0ra said:
If you only want to fix the system not mounting then yes, it's only this. The rest of the script is an exploit to gain root and install su but you don't need it since you already have it.
If you are looking for a full root method these two lines are not enough. In this case I suggest you try another rooting tool.
Click to expand...
Click to collapse
I still have 'some root', my Adaway still works but it won't load new/updated hosts, BusyBoxPro won't install, etc. I tried what you did, just ran the two lines of code but it said I didn't have permission when I tried to run the second line. Did you get that error? If you did, how did you get past that?
hi, i have a digiland tablet that i have tried rooting without success. its model is DL701Q, version 4.4.0. i have tried all of the rooting methods that i could find. from my investigation, there appears to be no specific rooting method for the version and model.
has anyone with this tablet successfully rooted it yet?
I find root genius to work on it.
wkLeon said:
I find root genius to work on it.
Click to expand...
Click to collapse
Thanks! It worked. The root program took a little while to do it, but it worked.
Failed
Root Genius rebooted the device several times, then showed failure in rooting. Nothing critical - it did not work however.
This is AFTER there was a 130MB OTA update "Wireless Update" that 'fixed some security issues' and I had already applied it wondering what it would do.
Go into About Phone and you will see Wireless Update as the second option below System Update. Hold off on applying it if you want root. As you will also lose root when applying it.
Off-the-shelf:
>adb shell
produces a $ prompt instead of a # prompt like it used to.
These devices are rootable off-the-shelf. Once the OTA has been applied, not at this time.
See also:
http://forum.xda-developers.com/chef-central/android/help-rooting-digiland-tablet-dl701q-t2960712
http://forum.xda-developers.com/android/general/digiland-dl700d-tips-tricks-t2867764
http://forum.xda-developers.com/android/general/digiland-dl700d-tablet-kit-kat-t2851783
http://forum.xda-developers.com/android/help/digiland-android-tablet-root-t2816435 (four pages)
In short, -and I read all the prior threads, so this is a summary to-date-, if you accept the update OTA, you will lose adb shell root access, and Root Genius will no longer work.
It does seem to work on the device off-the-shelf (without applying the OTA).
stock recovery and fastboot access
ndrsconschrtysvcs said:
Root Genius rebooted the device several times, then showed failure in rooting. Nothing critical - it did not work however.
This is AFTER there was a 130MB OTA update "Wireless Update" that 'fixed some security issues' and I had already applied it wondering what it would do.
Go into About Phone and you will see Wireless Update as the second option below System Update. Hold off on applying it if you want root. As you will also lose root when applying it.
Off-the-shelf:
>adb shell
produces a $ prompt instead of a # prompt like it used to.
These devices are rootable off-the-shelf. Once the OTA has been applied, not at this time.
See also:
http://forum.xda-developers.com/chef-central/android/help-rooting-digiland-tablet-dl701q-t2960712
http://forum.xda-developers.com/android/general/digiland-dl700d-tips-tricks-t2867764
http://forum.xda-developers.com/android/general/digiland-dl700d-tablet-kit-kat-t2851783
http://forum.xda-developers.com/android/help/digiland-android-tablet-root-t2816435 (four pages)
In short, -and I read all the prior threads, so this is a summary to-date-, if you accept the update OTA, you will lose adb shell root access, and Root Genius will no longer work.
It does seem to work on the device off-the-shelf (without applying the OTA).
Click to expand...
Click to collapse
Opps, meant to reply in the this thread. See my other post:
forum.xda-developers.com/showpost.php?p=57557683&postcount=35