Sorry for the long title, but the following occurs
Code:
SIM card detected but emergency calls only
SDCard unsupported but can mount elsewhere(including recovery)
MagiskSU disappeared
Terminal Emulator opens up and quickly closes(plays closing animation)
Also if I reflash stock, and magisk these issues go
EDIT:Wiped to get rid of encryption, all issues are gone now
Related
Today i read from droidforum.net and i see this one, and try to bring it here
source from droidforum and credit by SGMD1
All tutorials below are working as of February 2011. You will only need one file to root, which is included at the bottom of this post.
ROOT/UNROOT TUTORIAL (Courtesy of RyanZA on xdadevelopers)
1. Download and extract the z4root.zip file and copy the .apk directly to /sdcard.
2. Go to Settings -> Applications and make sure "Unknown sources - Allow installation of non-Market applications" is checked. Then click "Development" on the same page and make sure "USB debugging" is checked.
3. Open the "Files" app, navigate to the z4root location and install.
4. Launch z4root and select the Permanent Root option. Give it a minute to do its thing and reboot. If it spends more than two minutes on the message "'Running exploit in order to obtain root access" then you'll want to restart the app; this happens sometimes. Just exit the app by pressing the Home key, kill the app via a task killer (or Settings -> Applications -> Manage Applications -> z4root -> Force stop) and run z4root again. Voila, you're rooted! (You can also use z4root to unroot.)
5. Wireless Tether is a good first app to download if you're rooted. Download the most recent version of Wireless Tether (v2.0.6 as of 1/09/11) to test if you're rooted properly here
MANUAL UNROOT TUTORIAL (Use only if you previously rooted using the terminal emulator method, NOT z4root)
1. Download and install "Android Terminal Emulator" by Jack Palevich from the Market.
2. At the "$" symbol, type the following lines of code (press Enter after each line):
su (you should now see the "#" symbol)
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/bin/busybox
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
3. Exit the terminal emulator and reboot your phone. You will no longer have root.
CUSTOM RECOVERY TUTORIAL (Courtesy of Koushik Dutta aka Koush)
1. Download the Droid2Bootstrap.zip file at the bottom of this post, extract the .apk file and place it on /sdcard.
2. Go to the "Files" app, locate the Droid2Bootstrap.apk on /sdcard, install it, and open it. (Select "allow" when asked whether to grant the app superuser permissions)
3. Click "Bootstrap Recovery" and wait for the "success" notification. Then click "Reboot Recovery" and you're done! This will boot you into recovery where you can make nandroid backups, install from .zips, etc (do a search on the forums for more about custom recovery if you aren't familiar with it)
4. DO NOT delete the Droid 2 Bootstrap app once you have completed step 2, as this is the only surefire way to access the custom recovery. Holding "X" + "Power" will take you into the normal recovery.
SIM UNLOCK TUTORIAL
1. Make sure your phone line has been active and had no late payment history for at least six months. If it hasn't, VZW will not unlock your SIM.
2. Call VZW Global Support at 1-800-711-8300 and ask the representative for your phone's SIM unlock code.
3. To test it, you will need a non-VZW SIM. Once you insert it and power your D2 Global back on, it will ask for the unlock code.
NOTE: It appears that Verizon has put a carrier lock on the device for US GSM carriers. Therefore until someone figures out a workaround, you will not be able to use this device on AT&T or T-Mobile in its current state, even if SIM unlocked. The good news is that devs on various boards seem to be close to a workaround so as soon as one becomes available I will add it here.
Not the same phone.
That was very confusing for a second... lol
Sent from my ADR6350 using XDA App
Diferent exploit on droid2 than for incredible 2. Wish it could be that easy though.
Sent from my SCH-I500 using XDA Premium App
Thread closed since you are in the wrong forum.
Yes, I'm a noob, and I was simply installing applications from the store based on reviews. Thank you all for spending the time to read this post; should you respond, thank you even more!
T-Mobile Galaxy S III 16GB.
NO SD card installed! - /sdcard apparently mirrors the phone storage.
Otterbox Defender case installed by the salesman.
On PC, installed Odin 3.0.4
Rooted via http://www.redmondpie.com/how-to-root-galaxy-s-iii-att-t-mobile-or-sprint-model-tutorial/
included the CWM_SuperUser_v3.0.7.zip file from there
Failed to get CM10 installed
Installed ClockworkRecoveryMod 5.8.4.6
Installed CM10 (20121110 Nightly)
Installed Google Apps
Set a long password
** Encrypted storage **
Installed GetJar, Google Play, DroidWall
Set Droidwall to whitelist mode; allowed only GetJar and Google Play store/Download app/Play services access.
Installed LBE Privacy Guard (I had no idea there was any issue with JB)
Granted LBE Privacy Guard Superuser and let it remember SU rights (that was a mistake too)
On PC (Windows 7), installed Android SDK 20.0.3
On PC, used SDK to download platform tools and Google USB driver.
Attempted to follow tmpfs instructions in http://forum.xda-developers.com/showthread.php?t=1401813&page=2
ADB shell responds with "device not found" when in the CWR screen.
ADB shell has a limited amount of time to respond when in the main OS after the decryption password is entered.
After booting the phone into the main OS and decrypting the phone, I can get the normal unlock kscreen. However, the screen goes blank and re-locks right around the time I can get my unlock password entered - if I go really fast, I have a second or two after. Eventually it reboots itself and the cycle starts over.
I can definitely use the power button at the decyrption screen to reboot into recovery or download modes.
In the CWR screen, of course, I can't mount /sdcard, since it's encrypted.
How can I recover to a useful function, either by disabling LBE Privacy Guard, deleting LBE Privacy Guard, or resetting the phone to bare CM10 and/or stock?
On PC:
Followed wiki Howto:_Install_the_Android_SDK
Note that device showed up as Samsung.... before, now it's Android ADB Interface.
Tried again
boot in Recovery
ok
format cache partition
"wipe cache partiton" ok
adb shell mount -t tmpfs none /sdcard
no error
adb push cm-10-20121110-NIGHTLY-d2tmo.zip /sdcard
168375589 bytes in 31.947s
use the recovery to flesh the ROM as usual
??? I tried:
install zip from sdcard
choose zip from sdcard
And the SIII responded:
E:Can't mount /sdcard/
I then tried
adb shell
df
And saw no sdcard
ls -al
showed that the CM-10 was now "sdcard", so I tried:
mv sdcard cm10.zip
mkdir sdcard
mount -t tmpfs none /sdcard
df
this shows /sdcard is a "none" filesystem
mv cm10.zip sdcard
cd sdcard
ls -al
shows cm10.zip
In CWR, I again try "choose zip from sdcard
And again get:
E:Can't mount /sdcard/
In adb shell, I see
df
none 849028 164600 684428 19% /sdcard
ls -al | grep sdcard
drwxrwxrwt 2 root root 60 Jan 3 20:02 sdcard
Again, if anyone can provide me with some assistance, I'd appreciate it.
The actual set of fixes:
1) To remove LBE Privacy Guard, boot into "Safe Mode" by holding down just the lower left "menu" touch sensitive button (NOT the actual home button) during a reboot. Then remove LBE Privacy Guard.
You can then use the phone. Regrettably, neither CWM nor TWRP can see the encrypted data, nor back it up, nor install files from it. Goomanager doesn't, therefore, appear to be able to apply updates to it. Overall, the system tools on Android are just not capable of handling an encrypted device at this point in time.
2) To remove encyrption and allow most of the system level apps to work again:
2a) Back everything up as best you can. I used Titanium Backup Free and Mybackup Root Free to do inital backups, and then "adb root" and "adb pull / drive:\path" to get as much as I could of that local. I also used "adb pull /data/data drive:\path" (or maybe it was "adb pull /data/data/ drive:\path") to make sure I got "drive\path\com.android.providers.contacts\databases" which contains the SQLite Contacts database, just in case.
2b) Boot into TWRP (installed via Goomanager)
!!? Probably not required ?!! 2c) Wipe everything - EVERYTHING. Format EVERYTHING, even when it warns it could be bad.
2d) Use Odin to load up the Stock Root66 rooted ROM from the thread: T-Mobile, Wind, Mobilicity, Videotron Samsung Galaxy S III > T-Mobile Galaxy S III Android Development > [Firmware/OTAs] T999(V) Official, Leaked & Root66 FW & OTA Updates! (sorry, no hotlink - I don't have enough posts)
2di) Remember to follow the instructions in page 2 of that thread VERY CAREFULLY
2e) Boot into Recovery mode again after the device tries to ask you for the encryption password (which no longer works). Then wipe the /data partition entirely. Reboot again
2f) Now you can go through initial setup on your rooted phone and install your preferred ROM normally.
TryingToBeBetter said:
The actual set of fixes:
1) To remove LBE Privacy Guard, boot into "Safe Mode" by holding down just the lower left "menu" touch sensitive button (NOT the actual home button) during a reboot. Then remove LBE Privacy Guard.
You can then use the phone. Regrettably, neither CWM nor TWRP can see the encrypted data, nor back it up, nor install files from it. Goomanager doesn't, therefore, appear to be able to apply updates to it. Overall, the system tools on Android are just not capable of handling an encrypted device at this point in time.
2) To remove encyrption and allow most of the system level apps to work again:
2a) Back everything up as best you can. I used Titanium Backup Free and Mybackup Root Free to do inital backups, and then "adb root" and "adb pull / drive:\path" to get as much as I could of that local. I also used "adb pull /data/data drive:\path" (or maybe it was "adb pull /data/data/ drive:\path") to make sure I got "drive\path\com.android.providers.contacts\databases" which contains the SQLite Contacts database, just in case.
2b) Boot into TWRP (installed via Goomanager)
!!? Probably not required ?!! 2c) Wipe everything - EVERYTHING. Format EVERYTHING, even when it warns it could be bad.
2d) Use Odin to load up the Stock Root66 rooted ROM from the thread: T-Mobile, Wind, Mobilicity, Videotron Samsung Galaxy S III > T-Mobile Galaxy S III Android Development > [Firmware/OTAs] T999(V) Official, Leaked & Root66 FW & OTA Updates! (sorry, no hotlink - I don't have enough posts)
2di) Remember to follow the instructions in page 2 of that thread VERY CAREFULLY
2e) Boot into Recovery mode again after the device tries to ask you for the encryption password (which no longer works). Then wipe the /data partition entirely. Reboot again
2f) Now you can go through initial setup on your rooted phone and install your preferred ROM normally.
Click to expand...
Click to collapse
did this work for anyone?
EDIT: I just fixed permissions and was able to get back into the phone and uninstall LBE from the play store.
Hello,
I am trying to get UbuntuDesktop using Install or Mount from this forum runnning on my Samsung S4mini
http://forum.xda-developers.com/showthread.php?t=2627255
Anyhow always when I try to mount the linux.img it says: mount: permission denied (are you root?)
(please see the attached screenshot)
You probably first recommend me to check if I have my phone properly rooted and if I have the root privileges. Yes I have both.
For rooting I used this: http://forum.xda-developers.com/showthread.php?t=2364980
It worked successfully. The App RootChecker says, Phone successfully rooted, the App SuperSU also.
I installed Terminal Emulator for the Install or Mount and also BusyBox X+ for some missing commands. Both are in the list of SuperSU and when I am starting Terminal Emulator and typing "su" a message tells me that I have SuperUser rights.
Also the installation of Install or Mount was without any error - except at the end when it was trying to mount the linux.img.
I searched the forum and google for this problem - but all solutions are concerning problems when the users didn't type su or haven't properly rooted or something similar. Unfortunately I'm a new member and so not allowed to post my question in the Q&A of the Install or Mount. I hope it's ok to do it here now.
If your apps can't write files to your internal memory, or having problems saving images from IMGR/Chrome, this fix is for you.
I'm not sure how many had this issue after rooting their phones but it had been driving me crazy since I rooted my phone. I tried editing my build.prop securestorage=false, with no positive results.
I then came across a fix someone had for their Note 3, using terminal to fix this error, without having to reflash your rom.
Notes-
1. Read all the steps before attempting this
2. I have used this method to successfully fix my sdcard and make it usable
Prerequisites-
1. You will need root
2. You will need terminal emulator on your phone
3. You will need some reading skills and glasses if your eyes are weak..
Steps-
1. Open terminal emulator
2. Type "su"
Your screen should look like this
Code:
su
Now press enter
3. Now type this command, "restorecon -v -R /data/media"
Your screen should look like this now
Code:
su
restorecon -v -R /data/media
Now press enter
It will run several lines of code as it restores your system entries
4. Reboot
5.Now you can use your internal sdcard without any issues
Credit
Dude. I've been searching for this for like 2 hours. I was about to wipe my phone. You're awesome!
Didnt work for me. im using ES File Manager to edit the file but it wont let me. reboot like 3 times already.
Never mind, i think is a ES File Manager issue, i got Build.pro editor and that fixed.
didn't work for me
Lookie here
http://forum.xda-developers.com/showthread.php?t=2906384
And this is pretty much what the app does
Go to page 4 & post #35 in this thread.
http://forum.xda-developers.com/showthread.php?t=1810294&page=4
sent from nowhere
Thanks so much!! Works for me too, and I was about to ODIN flash,.
[Qualcomm]
Hello.
I went through the process of rooting my XT1768. I did it only to be able to use my phone as a hotspot even though my carrier blocked it. The guides I found were very helpful, but there were a few things specific to this model, and to my specific goal of having a hotspot, that I had to figure out on my own. I'm writing this to help anyone else who's trying to do the same as I did.
References:
Main guide: https://forum.xda-developers.com/moto-e4/how-to/moto-e-guide-to-rooting-t3652982
Unlock hotspot guide (do this after the main guide): https://forum.xda-developers.com/moto-e4/how-to/how-to-enable-hotspot-t3654214
So here is what I learned:
Be careful clicking on hyperlinked words in posts. This forum system injects ads into our posts, so it looks like links to additional information. For example, the word "stock" may be hyperlinked and it sends you to buy chicken stock at Walmart (real example that happened to me). If you want to click something, hover over it and look at the bottom of your browser. The ad links are insanely long and start with the same domain name (I forget what it was, something like vlink dot com etc etc). Adblock doesn't block these.
After getting to the bootloader, I was not able to flash TWRP recovery. I got a failed error. I needed to boot from it, not flash it, everytime I wanted to use it: fastboot boot twrp-x-x-x.img
Small thing: the main guide tells to click wipe data, then slide. The TWRP I used (3.2.3-r1) had wipe data, but I had to type "yes", not slide.
The guide tells you to install Magisk ZIP but doesn't tell you where to get it. A simple google will help, but here's the link anyway. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
After wiping data, you can use the ADB tool to send the zips for no-verity and magisk to the device storage so you can install them. You don't have to get an external SD card for that. Just type adb push [localfile] /sdcard . For example: adb push Magisk-v18.zip /sdcard . You will then have the file in the /sdcard folder and you can navigate there in TWRP and install the zip.
If you get red errors in TWRP when trying to do something (wipe, install, etc.), I found that you just need to go back to bootloader and re-boot TWRP and try doing it again.
When the main guide says "set system as R/W", they mean going into Mount in TWRP, removing the tick from "read only system" and picking "system" to mount. Took me a while to realize that.
After installing the no-verity and magisk ZIP, while still in TWRP, you can access a shell prompt using your ADB. You'll need to do that in order to edit your /system/build.prop file. Type adb shell in your PC and hit enter. Make sure you mounted /system as writable (not read only) or else you won't be able to change build.prop.
After you add the line to build.prop, you can make sure it's there by typing cat /system/build.prop . The last line should be the line you added.
After I added that line I booted into my device and installed Terminal Emulator. I installed it through googling Terminal Emulator APK and installing it directly, but you can probably find it in the google Play store. When you open it, it will ask you to allow it SuperUser rights with a countdown timer. If not, it means you didn't install magisk properly, and it's a good idea to start over. When you get SuperUser in Terminal Emulator, type the line and press Enter: settings put global tether_dun_required 0
I don't remember if I rebooted after typing that and before trying to use my hotspot.
If you get a bootloop (just the Motorola and Lenovo logos), go to this other thread which I made: https://forum.xda-developers.com/moto-e4/how-to/advice-xt1768-flashing-stock-motorola-t3879797
Please let me know how it went. Even if it went perfectly, just say that this worked for you, it'll help others dealing with problems.
Good luck!