Related
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.
I have rooted HTC One, I noticed a new software update was released by AT&T, and I wondered if it I updated it, would my root be gone? I tried to update it and after downloading the update, my phone restarted and booted into TWRP recovery and I rebooted and there was no update installed. Are any rooted HTC One users experiencing the same problem? What should I do, should i just forget about the OTA updates?
blackjack95129 said:
I have rooted HTC One, I noticed a new software update was released by AT&T, and I wondered if it I updated it, would my root be gone? I tried to update it and after downloading the update, my phone restarted and booted into TWRP recovery and I rebooted and there was no update installed. Are any rooted HTC One users experiencing the same problem? What should I do, should i just forget about the OTA updates?
Click to expand...
Click to collapse
Anytime you root the phone it changes the stock recovery so when the OTA tries to run it fails because the recovery needed to do it is the stock one. Just wait for someone to post a updated ota that works with twrp.
For the most part, updates will be baked into roms so you won't need to take the OTA
Sent from my Tricked out HTC One
jznomoney said:
Anytime you root the phone it changes the stock recovery so when the OTA tries to run it fails because the recovery needed to do it is the stock one. Just wait for someone to post a updated ota that works with twrp.
Click to expand...
Click to collapse
On top of stock recovery, you need to have all stock apps present on the phone. They can be frozen, but they must be there. The first thing any official OTA does it check the signatures of all .apks it expects to find on the device--if any are missing, the update will abort. I learned today that when you unlock your bootloader, several HTC-specific applications are automatically deleted from the phone and this will prevent the phone from accepting the OTA. You'll need to either A) replace those apks, or B) flash a stock NAND backup, flash stock recovery, do the update, then re-flash custom recovery and continue on from there.
blackjack95129 said:
I have rooted HTC One, I noticed a new software update was released by AT&T, and I wondered if it I updated it, would my root be gone? I tried to update it and after downloading the update, my phone restarted and booted into TWRP recovery and I rebooted and there was no update installed. Are any rooted HTC One users experiencing the same problem? What should I do, should i just forget about the OTA updates?
Click to expand...
Click to collapse
I installed it and it worked great. I have a unlocked bootloader but I am not rooted.
AT&T update file name and location?
Same experience. If I knew the location and file downloaded through AT&T Software Update, perhaps I could install it through TWRP. Anyone know? Tried?
blackjack95129 said:
I have rooted HTC One, I noticed a new software update was released by AT&T, and I wondered if it I updated it, would my root be gone? I tried to update it and after downloading the update, my phone restarted and booted into TWRP recovery and I rebooted and there was no update installed. Are any rooted HTC One users experiencing the same problem? What should I do, should i just forget about the OTA updates?
Click to expand...
Click to collapse
StanAnderson said:
Same experience. If I knew the location and file downloaded through AT&T Software Update, perhaps I could install it through TWRP. Anyone know? Tried?
Click to expand...
Click to collapse
no it will not work
Please...a little advice
Many thanks for all your help.
One question:
I have an HTC One (ATT) - SW Ver 1.26.502.10, bootloader unlocked, rooted, bloatware erased.
If I flash CM 10.1 - does this include the latest OTA update.
Many thanks
Today I received an OTA update to 10e. I will see how it goes today and report back with any findings.
It may just be my imagination but the phone seems to run hotter on 10e
Sent from my LGMS769 using XDA Premium 4 mobile app
Battery life seems to be pretty good. I went all day without charging and that's with heavy use. I do have cpu tuner installed and running though.
all these updates still coming,I think 4.4 won't be far ,at least I'm hoping for 4.2
are these MetroPCS roms usable on T-Mobile with wifi calling? also does anyone know if this fixes roaming that's been broken since jellybean came out?
pnum said:
are these MetroPCS roms usable on T-Mobile with wifi calling? also does anyone know if this fixes roaming that's been broken since jellybean came out?
Click to expand...
Click to collapse
Yes, they work. Check out Kuma's ROM. (2nd poster on this thread)
devilanuj17 said:
all these updates still coming,I think 4.4 won't be far ,at least I'm hoping for 4.2
Click to expand...
Click to collapse
as far as i can tell besides google drive and a few extra apps and removing root, wasn't much.. speaking of root, i was P'O'd and just flashed to v10b on the hunt for the almighty bootloader unlock.. on v20b now, irrelevant.. has anyone tried rooting after a factory reset? i've seen mixed posts of having root once updated.. i used cydia impactor to root on v10d.. after update root was gone, tried running it again but it kicked up errors.. su could not be found.. i'm waiting another 30 minutes before reverting to stock for the time being.. i'm willing to test it if no one else has but it won't be for a few days.. honestly tired of messin with it for now..
I just got this phone today and it automatically updated to the 10e version. I didn't even have the opportunity to root it at all. I've heard that cydia was the best way to root it,, do you think that would still work? Also, which is the best guy to use to unlock my boot loader with 10e and it being MetroPCS..any suggesitons? I've been reading but would like some useful opinions if thats okay.
Okay, so I finally got the update today. I was on the stock v10d, and rooted. I opened Titanium and unfroze all of the junk I had disabled. Then I told it to go ahead and apply the update. It rebooted and started to update, and I got the fallen down android with exclamation point. Hold power and restart. Boots back into my v10d, except now I somehow have the inverted touch screen again. What? I mean, I know can fix the touch screen easy enough, but what gives? Don't know why the update fails, and I especially don't know why I get the inverted touch. Any insight here?
Zhono said:
Okay, so I finally got the update today. I was on the stock v10d, and rooted. I opened Titanium and unfroze all of the junk I had disabled. Then I told it to go ahead and apply the update. It rebooted and started to update, and I got the fallen down android with exclamation point. Hold power and restart. Boots back into my v10d, except now I somehow have the inverted touch screen again. What? I mean, I know can fix the touch screen easy enough, but what gives? Don't know why the update fails, and I especially don't know why I get the inverted touch. Any insight here?
Click to expand...
Click to collapse
I think you still have the euro recovery installed, that's why you got the wonky screen. The boot or recovery images will cause the funk.
The update will fail because you have the 2nd init cwm or because you have made changes to the system apk file.
I have a cwm backup of 10e plus the radio files. I know the 10e is in my thread themed lgms769 ROM.
I'm not to sure where I uploaded the 10e radio. Lol I just remembered it's in my themed ROM thread as well. It's not in the first post, look around the end of the thread for the files.
Sent from my LGMS769 using XDA Premium 4 mobile app
Updated to 10e today, did this update bring anything new or no? Doesn't seem like there's anything new inside.
Anyone have a link to dl this
About a month ago I rooted my Samsung Galaxy Grand(the single sim version) with the help of Klingo Root, worked like a charm and had no problems at all. I even uninstalled all the bloatware samsung and the carrier had installed. About 3 weeks ago then an official update poped-up, so I updated my phone through Samsung Kies. Everything went fine, but after the reboot of the phone I noticed that all the bloatware was back, so I just figured, maybe i have to uninstall it again.
But then disaster struck SuperU said there is no SU Binary installed, so I though could have the update unrooted my phone? So I tried rooting it again with Klingo, doesn't work, I tried Framaroot, doesn't work either, I even tried to install Clockworkmod with Odin and it doesn't work. I even repeated the procedure while factory resetting my phone.
Has anyone else encountered this? It seems my phone is somewhere in between being unrooted and rooted? Everything else works fine.
Help! I just want to uninstall the carrier bloatware!
Difference In Android Firmware
ne6c said:
About a month ago I rooted my Samsung Galaxy Grand(the single sim version) with the help of Klingo Root, worked like a charm and had no problems at all. I even uninstalled all the bloatware samsung and the carrier had installed. About 3 weeks ago then an official update poped-up, so I updated my phone through Samsung Kies. Everything went fine, but after the reboot of the phone I noticed that all the bloatware was back, so I just figured, maybe i have to uninstall it again.
But then disaster struck SuperU said there is no SU Binary installed, so I though could have the update unrooted my phone? So I tried rooting it again with Klingo, doesn't work, I tried Framaroot, doesn't work either, I even tried to install Clockworkmod with Odin and it doesn't work. I even repeated the procedure while factory resetting my phone.
Has anyone else encountered this? It seems my phone is somewhere in between being unrooted and rooted? Everything else works fine.
Help! I just want to uninstall the carrier bloatware!
Click to expand...
Click to collapse
When you update your software it actually update your firmware. So the previous method will not work for this firmware.
1. you need to do it with different method if developers found it for you
2. just installed previous version of android .
3. May be fixed by factory reset..
4. You can even install prerooted custom rom like CM11
As per my experience new update will not that much compactible for all phones..
Hi, I'll start from the beginning, so I have a smart phone vodafone 2 (Alcatel V860) I wanted to upload the new software but accidentally I uploaded a backup of the tablet, after uploading the backup phone can not be connected as the flash mode, or in any way, you can not enter the recovery can not in any way connect the computer, the phone is as if dead. when I connect it to the computer when it is turned off the sound indicating that a new device has been detected, however, this software can not be installed. I hope that there will be a magician who already had a similar problem and knows what to do. Please help as soon as possible, if anyone knows what's going on I can talk about it on skype because it seems to me that it will be hard to even describe.
Thanks in advance.
aditya.kamble said:
When you update your software it actually update your firmware. So the previous method will not work for this firmware.
1. you need to do it with different method if developers found it for you
2. just installed previous version of android .
3. May be fixed by factory reset..
4. You can even install prerooted custom rom like CM11
As per my experience new update will not that much compactible for all phones..
Click to expand...
Click to collapse
Can I then "downgrade" through Samsung Kies then?
Flash Firmware through Odin...
ne6c said:
Can I then "downgrade" through Samsung Kies then?
Click to expand...
Click to collapse
No... Samsung kies doesnt provide feature to downgrade android.
You need to flash firmware package through odin.
you can google it for your device or search on xda...
All the best..
Press Thanks button for each person helped you...
Hello!
A few weeks ago, HTC sends me an update to fix the Heartbleed Bug from Android 4.1. On my device I have root and Xposed. If I install the update, would it remove my root and Xposed? It's my first Android Update after rooting
Thanks,
Weely_XD
I think you have to go back to full stock (Rom,recovery,bootloader locked) to update, so yes update remove root.
Could someone that installed this confirm if root was lost or not?
Thanks!
I will not be changed
romy25 said:
I will not be changed
Click to expand...
Click to collapse
of course not, but what about your phone, LOL
Well, I went ahead and installed the stock recovery and this OTA-update.
Everything seemed fine so I re-installed a new copy of TWRP (same version number as I had before)... Confused me totally. It was asking me to root again as soon as I quit recovery, which I did a few times... But I could never finish the installation of SuperSU. It always failed...
I was messing around with this for 2 days, until I for some reason tried to install TWRP from another "old" file I found on my computer (the exact same file I used when i rooted my phone the first time).
Now everything worked fine...
I guess the other recovery image was corrupt, incorrect, or something else...
Well, the mess was sorted out at least, and I still have root, did not have to reset my phone, and everything else seems to be OK.
Thanks! :good: