XT1040 - Problem in memory internal - Moto G Q&A, Help & Troubleshooting

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"
}

Related

Backup Rom and Bootloader from ADB or FASTBOOT

Hi,
I have an HTC Paradise, it's a phone that never saw the light of day. It's working properly but the rom is "watermarked".
I would like to know if there is any way to backup my current ROM and bootloader from ADB shell.
That way I can backup it, modify it and flash it again.
Would this work? I know that backup is very easy with "custom recovery", but dunno without it.
This is a picture of the bootloader:
{
"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"
}
The phone is already rooted.
I have found that busybox might help, but I don't want to brick the phone.
No help?
Any comments?
Got BusyBox running thru "adb shell".
I backuped the "/system" folder but it seems that it's not enough to generate and "update.zip"
I found in another forum how to dump "recovery" and "bootloader".
Using: "adb shell" and then "busybox cat /proc/mtd" I've got this:
mtd0 "misc"
mtd1 "recovery"
mtd2 "boot"
mtd3 "system"
mtd4 "cache"
mtd5 "userdata"
mtd6 "crashdata"
So I proceed to "busybox dd if=/dev/mtd/mtd1 of=/sdcard/recovery-dump.img bs=4096"
Now I have an IMG file of about 5mb...
That's enough to flash it thru FASTBOOT? What about the ROM? Can I modify it (remove sense) and flash it again?

Problem rooting ICS HKTW

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

empty ADB device on CMD windows 10

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

insert an sd card before using the camera

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

Question Realme C2 is not booting into TWRP recovery mode.

I have unlocked my Realme C2's bootloader and my device shows this
{
"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"
}
But when I input the "adb reboot bootloader" command the phone booting into this (USB Debugging is "ON")
I have flashed TWRP and it showed "OKAY", but when I input the "fastboot reboot recovery" my phone rebooting into ColorOS!, what is going on? Please help.
patraputt said:
I have unlocked my Realme C2's bootloader and my device shows this
View attachment 5673129
But when I input the "adb reboot bootloader" command the phone booting into this (USB Debugging is "ON")
View attachment 5673131
I have flashed TWRP and it showed "OKAY", but when I input the "fastboot reboot recovery" my phone rebooting into ColorOS!, what is going on? Please help.
Click to expand...
Click to collapse
If you are on ColorOS, 1stly, use COS TWRP ( not RUI TWRP ), 2ndly, u should try : fastboot oem reboot-recovery instead of fastboot reboot recovery.

Categories

Resources