Hi, i flashed the ICS HongKong/Taiwan because i want to install CM10.1 Kexec.
I'm using this method: http://forum.xda-developers.com/showthread.php?p=35000737
I have installed the latest moto drivers, and i have activated usb debugging.
I open the .bat and says
<waiting for device>
sending boot 8192KB
Or something like that, but, never moves from there.
I'm using windows 8, but i tried the same in another pc with windows 7, and it happens almost the same.
PS: Can i install CM10.1 Kexec with Retail UAE?
PS: I think it fails at this line:
adb shell mv /data/local/12m/batch /data/local/12m/batch.bak
adb shell ln -s /data /data/local/12m/batch
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
no you didn't turned on usb debugging before starting too flash.
or manually flash the Chinese kernel then reboot then root using 4.0.4 root method then flash hktw kernel.
well it worked for me. is used this method to go on official miui becausei have mb one
Sent from my ME865 using xda premium
Related
I have a Nexus 4, rooted, Franco kernel, and factory stock rom. Downloaded CyanogenMod mako build, extracted CM File Manager, installed the apk successfully, but am unable to access the advanced options in the settings menu - specifically access mode. Also tried reinstalling it by copying to /system/app, changing permissions rw -r -r, but the app's advanced options still remained inaccessible. When I first open up the app, SuperSU never prompts me to grant root access. I'm assuming it does that if I was able to change the access mode from safe to root.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 4 using Tapatalk 2
Your devices must have all the command listed at https://github.com/CyanogenMod/android_packages_apps_CMFileManager/tree/cm-10.1(property shell_required_commands). Otherwise, you shouldn't be able to access root functionality.
The link doesn't work, can you explain me what are the command required to enable the root mode? Thanks.
- sorry for my bad english -
Does anyone know how to get tethering working on 6.0 on Sprint again? The settings.db file is no longer where it used to be (using SQLite editor) so I am not sure if something else needs to be changed now or anything.
I can turn tethering on just fine. I get no message or anything about needing to pay for it or whatever. My laptop can connect to it just fine as well but nothing will load. Google simply says there is no connection.
Edit - Found the solution. I just used terminal emulator on the play store to enter the adb shell code(requires root).
http://forum.xda-developers.com/showpost.php?p=62968861&postcount=8570
WhiteWidows said:
Here's the fix
--modified /system/build.prop to add: "net.tethering.noprovisioning=true" (without quotes)
Next do this from ADB shell:
$ su
# settings put global tether_dun_required 0
Maybe @daniel84cs can incorporate it into the rom
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you! This is exactly what I was looking for. Worked like a charm, my results below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you very much, this worked like a charm!
Is this still working on MOB30P
Sent from my Nexus 5 using Tapatalk
hai guys, so i'm using windows 10 and trying to copy file using adb push to OPO via fastboot but the CMD not listing my OPO as i type "adb devices" during fastboot mode
I'm sure that i do a proper installation because my PC detect it during normal mode (MTP and USB debugging)
my device manager detect the adb interface (i'm using samsung driver as i follow driver manager guide on OPO toolkit 2.0 but i use v1.5.51 since it's newer than suggested by the guide)
here is what i got as i type "adb device"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know this is not problem from the OPO but from the windows 10 but any of you facing same problem like me??
Last I checked adb shouldn't work in fastboot. It works while booted up and can also work while in recovery but fastboot mode is for fastboot commands so that should tell you where to attempt adb push. Use fastboot devices and you'll notice the device is listed while in that mode
Hello everyone! I have a Moto g XT1040 and was wearing cm13, but after a while I had a problem in \system and could not clean the system. I tried to install Stock 4.4.4 and 5.1 and have not had success. I can enter TWRP recovery and it shows that my inner mamoria is 0 and my date, cache and system can not be mounted, so I can not install custom rom. Can anyone give me any tips of what to do?
NOTE: If I install stock again, is nothing more than "warning bootloader unlocked."
With TWRP booted, run these commands on your connected PC:
adb pull /tmp/recovery.log
adb shell dmesg > dmesg.txt
Post recovery.log and dmesg.txt.
_that said:
With TWRP booted, run these commands on your connected PC:
adb pull /tmp/recovery.log
adb shell dmesg > dmesg.txt
Post recovery.log and dmesg.txt.
Click to expand...
Click to collapse
Appears "error: device not found".
using the "copy to log sd" the TWRP, picked up this .txt do not know if you can help.
Recovery log.
This is the error I get when trying to install custom ROMs, any custom:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello Guys
I have this Moto G xt1032 (version whitout sdcard slot)
I used this cm-14.1-20161225-NIGHTLY-falcon.zip and open_gapps-arm-7.1-pico-20170928.zip
I got this message when I tried to use the camera:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My guess is the mount point do not worked fine
So I made a ssh connection:
$: df
$: Vim /fstab.qcom
I tried other snapshots from lineageOS and CyanogenMod but the error is the same
I know some versions of this phone has sdcard slot, but mine don’t.
You guys have any clue to solve this? Thank you
I discover that /storage/emulated/0 or /sdcard has no DCIM folder, so I tried to create with no sucess this fodler, i got no permissions, even root on Terminal.
so I boot on TWRP and create folder there, sucess, but when android boots again I cant write any files there
falcon:/storage/emulated/0/DCIM # chmod 7777 /storage/emulated/0/DCIM -R
falcon:/storage/emulated/0/DCIM # touch 34
touch: '34': Permission denied
Solved!
Hi man, I had the same, the problem was I did format internal storage with that every folder was deleted, but I fixed, how come?
Install de rom stock and this fixed the folders problem and then you could flash your favorite rom