Related
I found how for the X2 but the instructions dont work for the Revolution.
Anyone know the way to stop it?
Thanks
Using root explorer goto /system/lib/libdme_main and add .bak to the end of it. You will keep bluetooth and no more update. Make sure you do NOT mess with anything else!
Sent from my VS910 4G using xda premium
I deleted that file (adding.bak sounds much better) and it has gone away, just like mtmichaelson said.
Sweet thank. Ya on my droid 2 i stopped a bunch of stuff and just did the .bak so if i need it later i can just change it back.
Thanks
Just to double check, this works on revo phone.
When I acess file it has .so file type do I change .so to bak?
I just added .bak after the .so
Sent from my VS910 4G using XDA Premium App
Revolt - LTE
I'm not sure if this is related, but I noticed that after I flashed Revolt 1.3, I never see the "LTE" symbol in my notification bar. I'm in an LTE area, so I know it's available--does that mean my phone isn't running LTE anymore or is the symbol just not showing up on this ROM? I apologize in advance if this is a ridiculously misguided question--I'm new here and learning as I go.
By the way, mtmichaelson--I said this before and I'll say it again--awesome ROM! Thanks again for your hard work.
mtmichaelson said:
Using root explorer goto /system/lib/libdme_main and add .bak to the end of it. You will keep bluetooth and no more update. Make sure you do NOT mess with anything else!
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
will this also work for the updated Revolution (2.2.2)?
Thanks in advance
ally3447 said:
will this also work for the updated Revolution (2.2.2)?
Thanks in advance
Click to expand...
Click to collapse
Yes it does
Sent from my VS910 4G using xda premium
mtmichaelson said:
Yes it does
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
So, right now it is a .so file. Do I just add .bak to it, or change it from .so to .bak?
(Just want to be extra sure.)
Also,I would like to root my phone. I found a way that someone rooted theirs with their 2.2.2. Do you think I should root first, then change the file so it doesn't update? Or does it matter?
by the way, Here is the root I found(sorry it's a bit long):
"How to root your OTA Updated Revo:
This method requires you to downgrade your phone back to the V4 stock version. As of now, there seems to be no root process for the V6 update. This method has worked for me and I am also on a custom ROM that has been said to have some, if not most of the V6 updates included without the bloatware.
Step One:
- Be sure to get the following files:
---- LG VZW_United_WHQL_v1.2.0.exe
---- LGAndroidDriver_Ver_1.0_All.exe
---- LGNPST_Store_Lab-1.zip
---- VS910.dll (required to use LGNPST_Store_Lab-1.zip)
---- VS910ZV4_04.S4_04.P58008.R5.user.tot
---- RevoToolkit-1.0.apk (This is untested by me but supposed to provide an easier method to install CWM mod vs the ADB method)
---- SuperOneClickv2.1.1-ShortFuse (Includes the needed ADB program)
---- rageagainstthecage-arm5.bin (The exploit needed to root revo, not necessarily found with SuperOneCLick)
---- RevoltRom1.3.zip (This is optional, but recommended to speed up your revo and also to comply with the original topic of this thread. It 'seems' to stop the OTA from 'trying' the update since it includes updated features. NOTE that I said 'seems'... Other things I did may be the actual result I haven't seen the OTA try to install...
Ok, so to start, you will want to be sure that you have the drivers on your computer (I'm using windows 7 x64), so that is what this method has proven to work on by me.
Be sure to install:
- LG VZW_United_WHQL_v1.2.0.exe
- LGAndroidDriver_Ver_1.0_All.exe
Both may not be required, but I have both installed and things worked.
Then you will need to install:
- LGNPST_Store_Lab-1.zip
- VS910.dll (This is just copied into the folder LGNPST/Models. My install put the LGNPST program in C:\LG Electronics, not c:\Program Files (x68)... )
- You will run the LGNPST program, select the VS910.dll via Menu: File --> Select DLL.
- Then, in the bottom right of the LGNPST program, select BIN File (folder icon) to load the 'bin'.
--- This will require you to enter *.* in order to find the .tot file. Don't worry, this .tot file is what you need in the LGNPST Program.
- Once loaded and your phone is connected and recognized (Phone must be in 'Internet USB Mode'), hit the Start Button. This will begin the process of restoring your phone back to V4.
After that has completed, which takes a while, you will then need the SuperClick program to root.
- Copy, or verify, the rageagainstthecage-arm5.bin file is located in the Exploits folder where you extraced SuperOneClick.
- Run SuperOneClick, Select the exploit pull down (which defaults to 'auto') and select the rageagainstthecage option.
- Press the Root button and let it do its thing.
--- If it fails, this is what I had to do.. Reboot your phone. While it is rebooting, have the SuperOneClick program ready and waiting for you to hit Root again. As soon as the LG Logo becomes animated, hit Root and let it try again (While it is rebooting). This seemed to get the read/write options to work, where failed. This possibly is part of the update that is sticking around to stop you from rooting. So, try a few times. If/when succeeded, move on to the next steps if you wish to have some of the update 'fixes' without the update and a faster custom ROM...
To install a ROM, you need to have CWM installed.
Two methods to doing so seem to exist:
- The method I used was at this link: [RELEASE][6-14-2011] CWM Ported to the Revolution 4G! - xda-developers
Follow that and you should have a backup original image and the new image to get CWM to work to install custom ROMs
- The OTHER method, which is UNTESTED by me, is to use a simple tool called RevoToolKit, which is and APK file that runs directly on your phone. If it works, which others seem to say it does, this would be the most simple form of installing CWM to your phone. Be aware that this app is small, but uses a downloader to install CWM, so you want to make sure you have a good internet connection or data connection...
After that, you will want to follow the directions for CWM (ClockWorkMod) at this link:
- [Rom][8-17-11]Revolt Rom 1.3 - xda-developers
After all that, you should have a rooted Revo AFTER you managed to do the update.
I included links to some instructions in order to shorten up this post and not 'copy' someone else's methods and be sure that you can give the credit to them. The only credit I deserve for this is a complete step-by-step, in one place procedure to get you back or to root your Revo if you did the update.
In time, I am sure that there will be a simpler way to root the OTA Update, but until then, this is working for me and hope that this helps clear up some issues for others that find it tough to get back to root after the OTA Update."
It then has the file links, but I cannot post them since I am a newb.
Thanks again!
I don't see a way for you to change the file from .so to .so.bak without having root as far a rooting you only have to downgrade if your phone its v6 if out is running v4 all you need to do is root it
Sent from my VS910 4G using xda premium
Is there a way to do this without buying root explorer? I have bloat freezer so is there anything I can just freeze?
Thank You
*EDIT* just bought root explorer for $.99 through Amazon Appstore for those who still need it.
I'm on V4 and rooted back from V6 but it does not let me rename due to it being a read only file? sooo how do I add the bak? opened it with root explorer and it requested superuser privileges and I ok'ed it but when I go to /system/lib/libdme_main.so and try to rename it, it won't let me.
Sleepykat said:
I'm on V4 and rooted back from V6 but it does not let me rename due to it being a read only file? sooo how do I add the bak? opened it with root explorer and it requested superuser privileges and I ok'ed it but when I go to /system/lib/libdme_main.so and try to rename it, it won't let me.
Click to expand...
Click to collapse
On the top right of root explorer is a "Mount R/W" button. Click that and it should let you make changes to the system.
Hope it helps
"Home-Less and Iconic"
Thanks a bunch . That worked! I had pushed it at the system level. Didn't pay attention that I had to do it at the folder I'm in.
Sleepykat said:
Thanks a bunch . That worked! I had pushed it at the system level. Didn't pay attention that I had to do it at the folder I'm in.
Click to expand...
Click to collapse
Glad to help.
"Home-Less and Iconic"
Is it possible to unroot after using the 1 Click Root? I'm coming from a rooted Droid Eris and I remember the first few people who rooted their Erises had lots of problems and I just wanna make sure we can go back and re-root if a better root process comes along later on...
magicelf said:
Is it possible to unroot after using the 1 Click Root? I'm coming from a rooted Droid Eris and I remember the first few people who rooted their Erises had lots of problems and I just wanna make sure we can go back and re-root if a better root process comes along later on...
Click to expand...
Click to collapse
Yes, but you'd have to do it manually at this point.
You'd delete busybox and su, uninstall superuser.apk, and there may be a symlink you need to undo, but I think the latest one-click cleans that up. I'd have to go back and check.
And any bloat you froze needs to be unfrozen, or bloat removed needs to be restored.
Okay, first version of this tool, be kind and let me know if there are any problems with it.
Also: NO GUARANTEES. If it does something that breaks your phone, I am not liable. Use at your own risk. Etc., etc.
http://www.psouza4.com/Droid3/PetesMotorolaRootTools_v1.03.zip
UPDATE 9/1/2011: version 1.03
I'm trying the one touch unroot and keep getting an error about the /sdcard/d3unroot folder missing files.
I extracted all of the APKs from your link to my /sdcard/d3unroot directory, but for some reason one touch unroot will not work.
The root worked great
same error here...
Get that error as well
Same here.
Why does it even need that to un-root @ that point?
I'm getting the same error.
Is it really a one-click method?
I'm a dummy so I think I'm gonna wait for some clarity.
Thanks for doing this, man!
Fully re-written and should un-root and restore /system/app for both v5.5.959 and v5.6.890. Enjoy!
http://www.psouza4.com/Droid3/PetesMotorolaRootTools_v1.03.zip
This program is for Windows only and can:
root your device (most Motorola Gingerbread devices)
unroot your device
restore your /system/app, even if you deleted files
And a bit more, such as un-freezing apps if you un-root just like Titanium Backup can.
So how do I do this. Is it the same as the one click root meaning unzip the file and put my phone into charging mode and let it do its thing
Sent from my DROID3 using XDA App
spacecasespiff said:
So how do I do this. Is it the same as the one click root meaning unzip the file and put my phone into charging mode and let it do its thing
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Pretty much -- this is an all-in-one. It'll tell you where to download files and where to put them when you begin.
I guess I'm just retarded I can't get this to work. I give up. Looks like I'm gonna have to get VZ to mail me a new D3
Yonnor said:
I guess I'm just retarded I can't get this to work. I give up. Looks like I'm gonna have to get VZ to mail me a new D3
Click to expand...
Click to collapse
Why can't you? More than willing to help, but have to tell me what the problem is. And bear in mind that I put out a new version less than 2 hours ago that fixes a LOT (it's a full rewrite).
ok ive downloaded the file to my computer.
Keep getting the error for the Restore data not being in the right place. I've extracted the files to the right spot (I think)
is the restore folder supposed to be located in the Root Tools folder, and then all the apk's placed that Restore folder?
Yonnor said:
Keep getting the error for the Restore data not being in the right place. I've extracted the files to the right spot (I think)
is the restore folder supposed to be located in the Root Tools folder, and then all the apk's placed that Restore folder?
Click to expand...
Click to collapse
Basically, yes.
I'll use your desktop as an example, so if you have:
Desktop\New Folder\Pete's Motorola Root Tools.exe
Then you'll want to extract all the files for the /system/app fix to:
Desktop\New Folder\restore
So that you have:
Desktop\New Folder\restore\AccountAndSyncSettings.apk
Desktop\New Folder\restore\AccountAndSyncSettings.odex
Desktop\New Folder\restore\AdminFeedNotifier.apk
etc.
This assumes you are using my new version 1.03.
psouza4 said:
Basically, yes.
I'll use your desktop as an example, so if you have:
Desktop\New Folder\Pete's Motorola Root Tools.exe
Then you'll want to extract all the files for the /system/app fix to:
Desktop\New Folder\restore
So that you have:
Desktop\New Folder\restore\AccountAndSyncSettings.apk
Desktop\New Folder\restore\AccountAndSyncSettings.odex
Desktop\New Folder\restore\AdminFeedNotifier.apk
etc.
This assumes you are using my new version 1.03.
Click to expand...
Click to collapse
Ok thank you, I'll give this a shot again.
EDIT: I have it set up as:
Desktop/PetesMotorolaRootTools_v1.03/restore/(all the apk's)
And I'm still getting the:
ERROR: /restore/ backup doesn't exist or is incomplete! etc etc
ok i just unrooted and all is good now im rooting agian. so thank you for this on click unroot meathod. its good to know that if i want to unroot i can. You should put this on every forum that you can. I will aslo tell people about it. You did a good thing for the people on this one. I think a lot of new people will whant to root now that they have a way to undo it.
Lol well like 8th try and I got it to work. Sorry for pestering you so much.
Hi
First post here, I'm new to Android and rooting but I know my way around computer systems in general so hoping you guys can help me, haven't seen a thread about this exact problem so far.
I've semi-bricked (bootlooped) my Samsung Galaxy Ace running Gingerbread, having rooted it last month using the upd_1 package and enjoying a bloatware-free phone, happily installing apps onto my second partition on my SD card. I've not changed my ROM, just the stock is good enough for me for now. However I was getting continually prompted by Homescreen Selector nags at powering up for some reason and I thought I could disable it by applying Freeze using LInk2SD, but since doing that I continually get the Samsung logo, the orange "explosion" (I'm with Orange) then a vibration and the whole cycle repeats. My guess is the operating system can't find the selector.apk app since I froze it.
I thought the solution would be simple - use adb shell to rename back from selector.fro to selector.apk. However I'm unable to find any such file in my system/app folder. There are a load of other apk and odex files but not that one. When I type su I get "permission denied", though I definitely rooted my phone but I don't think I have my bootloader unlocked.
I don't have CWM installed or any backups unfortunately (yes, I know...), so even if I took one now prior to a factory reset, surely the same problem would come back if I were to restore from any backup I were to take now. I can get into Recovery and Download screens ok but don't want to restore the whole ROM unless I have to, since I know it's only one APK that is at fault.
So, please can anyone tell me how to locate the selector.fro file to turn it back to selector.apk? Or can't I do that without unlocking the bootloader first, or is there another solution?
Many thanks in advance,
Graham
Wouldnt it be possible to make a zip of the selector.apk and flash it? Rename the zip-file to "update" (since you're unable to browse to your specific file).
QNBT said:
Wouldnt it be possible to make a zip of the selector.apk and flash it? Rename the zip-file to "update" (since you're unable to browse to your specific file).
Click to expand...
Click to collapse
Hi, thanks for the response
Do you mean copy a zip of selector.apk to the SD card and run it from there, same as I did when I rooted? Where can I obtain a copy of that apk from? I can't find it on my computer or via Google...
gkey2112 said:
Hi, thanks for the response
Do you mean copy a zip of selector.apk to the SD card and run it from there, same as I did when I rooted? Where can I obtain a copy of that apk from? I can't find it on my computer or via Google...
Click to expand...
Click to collapse
You can extract it from the ROM's zip file, just locate it as you would on your phone.
But I don't have a ROM zip file. I'm not using a custom ROM, just stock. I may go down the custom ROM route one day, but for now I just want my phone to work again in the quickest way possible.
All I need is a copy of the original stock home selector APK. Can anyone help here please?
Found the file!
Never mind, got the apk from another thread. Flashing tonight...
Fellas, I come to here, humble and contribed. I, as all others, have the dreaded gps bug. I know there are a few posts concerning it, however, those are starting to get confusing to me. I ask for some simple instructions as to simply root my device, and procedure to replacing the files that are to make it functional again. No debloating, flashing of ROMs, or etc. DL links would be nice too.
Phone specs:
At&t n900a
4.3 stock
baseband n900aucubnb4
build number jss15j.n900aucubnb4
Have rooted other samsung devices, so not totally an idiot...
Any help will be much appreciated
Kingo
Sent from my SAMSUNG-SM-N900A using Tapatalk
zinupe14 said:
Kingo
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
As well as other posts to many threads here, someone posts partial answers, or simply something they read. Thanks . People wonder why they brick their devices....SMH
You asked how to root p. Kingo app is as simple as it gets. And it doesn't trip your Knox counter. If you want 4.4.2 then I would suggest downloading the urdroid rom and following the detailed instructions. I'm running the stock kitkat rom rooted with no Knox counter trip. Not trying to be a prick but the kingo root method was as simple as pi
Sent from my SAMSUNG-SM-N900A using Tapatalk
I'm not interested in kitkat, honestly, I dont care about custom ROMs. I just need to root, and the procedure for replacing the gps files that are to make the AT&T GN3 gps actually work. And possibly stop the updates.
if you're on the latest nb4 baseband than you'll need to google Kingo v.1.15 and find a download of that version. if you're still on mj5 than just google kingo app, download and install to a windows pc. open the app and follow the instructions. its easy. kingo should install the correct drivers. kingo doesn't always succeed the first time. if that's the case try again until kingo says success. once done update su superuser app via google play and restart your phone. now you have root. i don't have gps problems so hopefully someone else can help you with. good luck. sry i can't post any download links but if you use google you should have no problems
Honestly I'd just wait if I were you....
Rogers and tellus note 3 have gotten kitkat the s4 has gotten kitkat for att in looking for kitkat in the next few weeks to month.
Sent from my XT907 using xda app-developers app
Would some explain how to "flash" the gps files to fix the friggen thing. I have root with kingo, and downloaded the gpsfix from drakeymcmb, but 2 folders are extracted and only one is told what to do with, as well as how to change permissions for the files...thanks in advance
crazysgt said:
Would some explain how to "flash" the gps files to fix the friggen thing. I have root with kingo, and downloaded the gpsfix rom drakeymcmb, but 2 folders are extracted and only one is told what to do with, as well as how to change permissions for the files...thanks in advance
Click to expand...
Click to collapse
Ignore the meta folder. You're not "flashing" these files, you're copying them to your phone's system folder. Open the zip and open the system folder, then open the etc folder. Now copy the gps.conf file to your phone's system/etc directory. Now go back to the gpsfix.zip and open system then open lib. Copy the 3 libloc files to your phone's system/lib directory. Go back to the zip. Open system, open lib, open hw. Now copy the 2 GPS files to the phones system/lib/hw directory. Change each files properties to rw-r-r(Fix permissions). Now reboot. Warning if you don't know what you are doing i don't recommend doing this as messing with system files can lead to very expensive paperweight
The Basilisk said:
Ignore the meta folder. You're not "flashing" these files, you're copying them to your phone's system folder. Open the zip and open the system folder, then open the etc folder. Now copy the gps.conf file to your phone's system/etc directory. Now go back to the gpsfix.zip and open system then open lib. Copy the 3 libloc files to your phone's system/lib directory. Go back to the zip. Open system, open lib, open hw. Now copy the 2 GPS files to the phones system/lib/hw directory. Change each files properties to rw-r-r(Fix permissions). Now reboot. Warning if you don't know what you are doing i don't recommend doing this as messing with system files can lead to very expensive paperweight
Click to expand...
Click to collapse
Thanks! This is what I needed, I understand the risks, but also know the reward is a functioning gps, the meta folder and how to change the permissions is what was holding me back.
So on permissions, just rw, r,r no execute on any right? Now how to disable att updates? Thank goodness for yall smart fellas
crazysgt said:
So on permissions, just rw, r,r no execute on any right? Now how to disable att updates? Thank goodness for yall smart fellas
Click to expand...
Click to collapse
Sry for the late reply. Owner=read write, group=read, other=read. No execute
To disable AT&T updates, freeze the at&t update app. (Sorry, I can't get the name right now, I'm on a ROM that had it removed, but it's at&t <something to do with updates>, with little red and green lines on the icon.) Link2SD or TiB will freeze it.
One more quick ?, When I open Super SU, a popup appears, Samsung KNOX has been detected. This might limit root capabilities and cause annoying popups. Try to disable KNOX? I have always cancelled the popup. Is that correct? or should I ok it? Again, thanks guys for all the help. I used my gps without fail all weekend long. Not a single problem, gps or phone wise. Wonder if I was to unroot using Kingo app, and leave the gps patch alone, if it would still get OTA?
Hi All,
Since I am getting nowhere and no replies for my questions, I am going to rephrase them differently here so hopefully someone can jump in and give me a helping hand... (and please forgive if I seem to bombard the forums with questions).
My Note 3 SM-N900A, build KOT49H.N900AUCUCNC2, running 4.4.2. It is having issues with permissions that effectively block the phone from seeing any SD Card, USB, and internal memory space. It won't access any remote resources like internet or Google Play...either
Issues arose after I changed platform.xml. I since then unrooted the phone and uninstalled SuperSU. I can see that these 3 changes were reckless on my part, that I just put the phone into a very bad state that made it very very difficult to recover. I am still banging my head for the blunders but obviously that didn't help fix the phone. :crying:
I would like to know if there is a way to gain access to the phone's system area again to fix the permission issues. Can I use ADB Shell along with USB debugging? If yes, what are the commands I need? Can I somehow send towelroot and SuperSU to the phone via Odin and execute them? The reason I ask this is that I have no way to access any storage area on the phone, and there is no way to go online to download apps. Or can I put the phone into service mode by typing in the *# numbers on the keypad and hopefully fix it there?
Thank you
At this point I'm not even sure if adb would be able to access your memory card to push TowelRoot to it. You might be best off restoring using the stock Odin files, lick your wounds, start over and chalk it up as a learning experience.
http://forum.xda-developers.com/showthread.php?t=2703006
Sent from my AT&T Galaxy Note 3 using Tapatalk®
OK, Something Positive
andygev35 said:
At this point I'm not even sure if adb would be able to access your memory card to push TowelRoot to it. You might be best off restoring using the stock Odin files, lick your wounds, start over and chalk it up as a learning experience.
http://forum.xda-developers.com/showthread.php?t=2703006
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Ah, thanks for replying. I was really worrying about that too.
However, I just installed ADT on my PC and connected to the phone via USB debugging. Using the adb shell ls command, I could see the entire directory structure. I was able to get to the system folder too.
I pulled the platform.xml back and attached to this message. Could you or someone please take a look and let me know if anything is wrong in the file? I made very small changes and reverted them. So it should be same as original, but I am not so sure. Also do you know if the encoding of the file is wrong so that Android couldn't read it?
At this point, it appears all is NOT lost. I just need some of your experts to guide me thru the commands needed to regain the access to my SD card or storage from the phone.
Now, let me bring in another point: Prior to having all this snafu, I granted ES File Explorer root access so that I could overwrite the platform.xml file. I don't know if doing that messed up the system. If it did, what would be the most straight forward way, simplest way to try to get back to normal? Provided now adb seems to be able to access the files and directory.
I know I could try install towelroot again, but would like to see if I can bring the system back to normal operation first.
Thanks
I may be wrong, but adb being able to see and pull system files is one thing. To get adb to actually modify system files, you'd need to be able to give adb root access. You may however be able to download the TowelRoot apk to your computer, put it in the same directory as adb, then in the command prompt type "adb push towelroot.apk /data/app/" (without quotes). Reboot and see if TowelRoot installed.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
vbcomer said:
Ah, thanks for replying. I was really worrying about that too.
However, I just installed ADT on my PC and connected to the phone via USB debugging. Using the adb shell ls command, I could see the entire directory structure. I was able to get to the system folder too.
I pulled the platform.xml back and attached to this message. Could you or someone please take a look and let me know if anything is wrong in the file? I made very small changes and reverted them. So it should be same as original, but I am not so sure. Also do you know if the encoding of the file is wrong so that Android couldn't read it?
At this point, it appears all is NOT lost. I just need some of your experts to guide me thru the commands needed to regain the access to my SD card or storage from the phone.
Now, let me bring in another point: Prior to having all this snafu, I granted ES File Explorer root access so that I could overwrite the platform.xml file. I don't know if doing that messed up the system. If it did, what would be the most straight forward way, simplest way to try to get back to normal? Provided now adb seems to be able to access the files and directory.
I know I could try install towelroot again, but would like to see if I can bring the system back to normal operation first.
Thanks
Click to expand...
Click to collapse
Here's the original stock platform.xml if it helps you.
andygev35 said:
I may be wrong, but adb being able to see and pull system files is one thing. To get adb to actually modify system files, you'd need to be able to give adb root access. You may however be able to download the TowelRoot apk to your computer, put it in the same directory as adb, then in the command prompt type "adb push towelroot.apk /data/app/" (without quotes). Reboot and see if TowelRoot installed.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Edit: instead of using adb push, use "adb install towelroot.apk" (if that's the actual package name). Go through the rooting process, download the ES File Explorer apk to your computer install it using adb. Hopefully if all that works, you'll be able to check and fix any permissions that got messed up with your platform.xml. It should be rw-r-r.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
A Step Forward
andygev35 said:
I may be wrong, but adb being able to see and pull system files is one thing. To get adb to actually modify system files, you'd need to be able to give adb root access. You may however be able to download the TowelRoot apk to your computer, put it in the same directory as adb, then in the command prompt type "adb push towelroot.apk /data/app/" (without quotes). Reboot and see if TowelRoot installed.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
OK. You are right. adb doesn't have write access yet.
I tried this and got success:
C:\AndroidDev\sdk\platform-tools>adb install tr.apk
1767 KB/s (113099 bytes in 0.062s)
pkg: /data/local/tmp/tr.apk
Success
What should I do next? Does it mean the tr.apk has been installed?
Thanks
Update: I saw the Towelroot app in the App Drawer, but after clicking on it and choosing "make it ralr", I got message "Unfortunately, towelroot has stopped."
vbcomer said:
OK. You are right. adb doesn't have write access yet.
I tried this and got success:
C:\AndroidDev\sdk\platform-tools>adb install tr.apk
1767 KB/s (113099 bytes in 0.062s)
pkg: /data/local/tmp/tr.apk
Success
What should I do next? Does it mean the tr.apk has been installed?
Thanks
Click to expand...
Click to collapse
Sounds as though towelroot is now installed. Go to your app drawer and run it.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
andygev35 said:
Sounds as though towelroot is now installed. Go to your app drawer and run it.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Yeah, it is installed in the App drawer, but running it gave me error "Unfortunately, towelroot has stopped.".
I went ahead and install both ES File Explorer and SuperUser packages. From ES FE, I could look at the /system/ect/permissions/platform.xml and could see that it had a different date, its date is older, 3/15/2014. I think it came with the N900AUCUCNC2 that I flashed with Odin yesterday.
So, it appears the permission come from a different place or source, I would like to know where Android actually sees the permissions. You know, how did it think that it needed to lock down read/write access to storage areas while the /system folder has been replaced.
Thanks
vbcomer said:
Yeah, it is installed in the App drawer, but running it gave me error "Unfortunately, towelroot has stopped.".
I went ahead and install both ES File Explorer and SuperUser packages. From ES FE, I could look at the /system/ect/permissions/platform.xml and could see that it had a different date, its date is older, 3/15/2014. I think it came with the N900AUCUCNC2 that I flashed with Odin yesterday.
So, it appears the permission come from a different place or source, I would like to know where Android actually sees the permissions. You know, how did it think that it needed to lock down read/write access to storage areas while the /system folder has been replaced.
Thanks
Click to expand...
Click to collapse
I'm at the limit of my experience here... Did you do the all in one restore or the 4 file restore?
Sent from my AT&T Galaxy Note 3 using Tapatalk®
andygev35 said:
I'm at the limit of my experience here... Did you do the all in one restore or the 4 file restore?
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Thanks for hanging in and helping, you don't know how much I appreciate your time!
I did the all in one first. That didn't help. Then I did it again with the re-partition with PIT file. But that didn't help either. I didn't try the 4 files individually for fear of losing data.
vbcomer said:
Thanks for hanging in and helping, you don't know how much I appreciate your time!
I did the all in one first. That didn't help. Then I did it again with the re-partition with PIT file. But that didn't help either. I didn't try the 4 files individually for fear of losing data.
Click to expand...
Click to collapse
I think you've just about done everything you can do without a complete Odin reinstall and reformat. If adb pull is working for you I suggest pulling the folders you want to save and doing the complete 4 file install with the PIT file as well.
Someone more experienced than I may be able to get you back up without losing your but tbh with the amount of troubleshooting you've done already I think a full Odin reinstall is your best option and will prevent any issues that could stem from this further down the line.
The only thing I can think of with towelroot is that it needs internet access to run were you connected to wifi when you ran it? It's probably not that simple but figured it couldn't hurt to try!
brisinger08 said:
I think you've just about done everything you can do without a complete Odin reinstall and reformat. If adb pull is working for you I suggest pulling the folders you want to save and doing the complete 4 file install with the PIT file as well.
Someone more experienced than I may be able to get you back up without losing your but tbh with the amount of troubleshooting you've done already I think a full Odin reinstall is your best option and will prevent any issues that could stem from this further down the line.
The only thing I can think of with towelroot is that it needs internet access to run were you connected to wifi when you ran it? It's probably not that simple but figured it couldn't hurt to try!
Click to expand...
Click to collapse
Hi there,
Thanks for replying. I am kind of afraid I will have to go down that route, but at the same time trying not to if I could.
One of the other reasons I didn't try the 4 files was because I thought the all-in-one, as its name suggested, would be equivalent to those 4 files.
Is there a way to pull the SMS, MMS, call logs from the phone via adb? Do you know where those records are kept?
Thanks
vbcomer said:
Hi there,
Thanks for replying. I am kind of afraid I will have to go down that route, but at the same time trying not to if I could.
One of the other reasons I didn't try the 4 files was because I thought the all-in-one, as its name suggested, would be equivalent to those 4 files.
Is there a way to pull the SMS, MMS, call logs from the phone via adb? Do you know where those records are kept?
Thanks
Click to expand...
Click to collapse
The all-in-one file is the same as the 4 files, the only difference is installing it doesn't wipe the internal storage.
Have you tried running adb backup? That would be a heck of a lot easier than pulling a bunch of folders...if that doesn't work the databases are in /data/data
Calls: /data/data/com.android.providers.contacts
SMS and MMS: data/data/com.android.providers.telephony
Is there is any shell command to long tap