Hey guys
I have a Moto x (xt1052) with unlocked bootloader. At this moment I have no OS installed. I can enter bootloader and recovery mode but none of them work properly. As I tried flashing the system using mfastboot it seemed as everything has worked properly but when I tried rebooting the phone, I found out there was still no OS installed.
In recovery mode I get an error no matter what I'm doing. Most of the time it says "unable to mount /data" or "unable to mount storage". I think I lost root but I can't install supersu without an OS and can't install an OS without root.
I also tried RSD lite but it somehow has a problem with my ROMs (I tried three different ones, two of them worked perfectly fine on my phone before).
I really have no idea what I could try next so hopefully you can help me!
Thanks a lot!
Related
Hello!
I have a rather annoying problem on my Motorola Milestone (NOT a Droid) permrooted with z4root.
Software on Milestone:
Firmware 2.1-update1
Kernel 2.6.29-omap1
Build: SHOLS_U2_02.36.0
OS:
Vista 64bit
latest Motorola drivers (4.8.0)
At the Moment there's still the stock rom installed, I tried to install the CM-Port for Milestones.
That's what I did in order to accomplish my goal:
First, I installed Clockworkrecovery via Rom Manager.
Rom Manager said that it worked, it also tells me that the current recovery system is actually clockwork,
but when I boot into recovery mode with Power- and camera button, it says this:
http://forum.xda-developers.com/attachment.php?attachmentid=471603&stc=1&d=1293116205
Is this still the stock recoverysystem? (except from the error. What does this mean?)
I tried updating the rom to the Cyanogenmod-port from doshaska.
After starting update.zip, it says "EOCD marker occurs after start of EOCD E:signature verification failed".
So I assume, something with clockwork hasn't worked correctly and the recovery/boot is still "protected"
I also now renamed the /system/etc/install-recovery.sh file in order to prevent the phone from restoring the original recovery.
Then, I tried flashing a vulnerable sbf via RSDLite 4.6 in order to reflash another recoverysystem: openrecovery.
The problem here is, that the phone isn't recognized at all by RSDLite when it's booted into normal android OS (computer detects phone w/o problem), in recoverymode, it isn't recognized by the computer itself at all, nothing happens. As far as I know, there is no other way to flash a vulnerable sbf without RSDLite?
It's really weird, shouldn't the phone be recognized in recovery mode aswell? My Computer does _nothing_ when I connect the phone in recovery mode. No typical USB-plugin-sound, no nothing.
So, what can I do? I tried uninstalling everything, Drivers and HW found in device manager, everything. Like it has never seen a Motorola phone before, then reinstalled everything including reboots, but nothing changed.
I would like to flash openrecovery and then the CM-port, but im kinda helpless now.
Thanks!
Try RSDlite v4.6 and 32bit XP...it should recognize your phone...and I guess you can also flash an sbf by applying it as an update.zip
Do a research on this and correct me if I'm wrong!
omg, so stupid.
USB-Debugging was disabled.
Up and running cyanogenmod now
iam very sad to say you that my phone is bricked.i will change roms in my phone frequently.u always very careful but today when i was out for a work my brother tried to install the new hyperdrive rom but he had not taken any backup and he wiped all the memory including rom zip files so he stucked the phone in recovery(he dont know about ADB side load) then he ( he observed me when updating from kk to lp) searched the files in my computer then just tried to instal stock kitkat using command prompt Nd succced but when he found lollipop update file in the computer and he placed it in phone but when the phone is updating into lollipop the low battery in the phone made the phone dead.
when i came back home i saw all the mess he does now the phone whn switched on only shows android logo with error frequently but when i went into recovery mode to sideload the rom the the fastbot devices command shows device connected but msg displays error msg showing device not found when i tried to sideload the rom.
in TWRP it displays unable to mount data :crying:
unable to mount cache
when i tired to install using external sd card the installation completes but when rebbot the phone stucks on android exclamation logo showing errror msg
please help i dont my phone to be bricked:crying::crying:
Have you tried mounting from a usb otg ?
the problem is solved partially
oisink2014 said:
Have you tried mounting from a usb otg ?
Click to expand...
Click to collapse
i used TWRP and repaired the filesystems and installed the custom rom microkatv1.zip but the rom is installed succcessfully and i wipe cache/dalvik cache and reboot the phone it will shows motorola logo and automatically moves into TWRP.can anyone help me how to boot the phone normally is there any software or any commands to solve this please lead me to solution:crying:
i saved my phone
at last i had done some file repairs in TWRP and i got installed stock kk rom by ADB then i got my moto g back
sagaremperor said:
at last i had done some file repairs in TWRP and i got installed stock kk rom by ADB then i got my moto g back
Click to expand...
Click to collapse
I'm having a similar problem. Can you elaborate on what you mean by file repairs?
solution may work for you
Eogram said:
I'm having a similar problem. Can you elaborate on what you mean by file repairs?
Click to expand...
Click to collapse
Weird, even though for me it wasn't mountable either, reformatting worked.
I don't think adb will be able to mount it if it doesn't work in CWM. I guess one thing you could try is flash TWRP via sideload and then go to wipe, check all of the partitions, and then hit "repair filesystem". Might work, :fingers-crossed:
if not worked can you tell me whats actual is your problem:silly:
Yep, probably again a noob that bricked his phone.
As there was no info on my phone that wasn't on google servers or something I was so stupid to start installing the latest official CM12 built on my XT1068 without any decent backups.
- I think the moto/google service for lost devices encrypted my phone without me really noticing it. :crying:
- I was on Lollipop, the latest update I got here from in Benelux/Europe.
- I unlocked my device, worked fine. device also tells in bootloader
"Device is UNLOCKED. Status Code: 3"
- when than having installed TWRP 2.8.0.1, os started but gave problems installing superSU.
(no prob I thought, I go immediately forward with CM12 installation, so don't have to bother with the old ROM) :silly:
- wiping everything for clean install I already saw some messages coming up. on hindsight; Difficulties with opening /data folder etc...
- tried to install CM, and several other more stock roms, but never get through the message. All bad installs.
- maximum I got is CM12 booting up, preparing some apps and than a message describing the encryption problem, asking to reboot.
TRIED:
- install from usb drive (with OTG cable)
- erase and reinstall from TWRP 2.8.0.1 and other recoveries.
- fastboot flash a standard recovery again, to wipe data from there,
(from this standard recovery installers never got through even the verification to install, so tried than installing from other recoveries, same problem.)
Can still try but hesistant:
Unlock my mothers phone (same month, same model, same place, probably same encrypted) to try backup there in TWRP, recover this on my phone, and this way flash standard rom again. From there I could probably get rid of encryption. (as found already in several places)
I would afterward immediately try to lock my mothers phone again, don't know so much of how to get recovery to standard one again though. Can I backup this before. When I try now "adb backup - all" on my phone from my mac, I get "unable to connect for backup" message though. Even when phone is saying "phone connected".
Anyone an idea of how to get out this trouble?
Greetings
Otto
[email protected]: try "fastboot erase userdata"
have the feeling I'm getting there. Gapps still don't work but rom boots. Recovery has to be standard one to make encryption to work. Thats the key.
Heya!
Totally new to all of this, so please be gentle. My M9 is now bootlooping and the past hour of research hasn't helped me.
I've just done the following with my Tmobile marshmallow M9:
1) Used HTC's dev tools to unlock the bootloader
2) Flashed twrp-2.8.7.1_CPTB-B1-hima.img using fastboot
3) Immediately after flashed BETA-SuperSU-v2.66-20160103015024.zip using twrp
4) Backed up everything using twrp
My phone is now boot looping. I tried clearing cache/dalvik/data with no luck. Honestly, I'm fine with either loading a stock rom or going to viper like I originally intended, but I don't know how - I don't have either of those on my SD card and I know that I need to get them off of my computer onto the phone, but ADB and my device manager don't see the phone when I'm in TWRP. When I'm in the bootloader, I see "My HTC" in device manager and HTC sync picks up like it sees the phone.
I just want a working phone again. I hear that SuperSU 2.65 is probably more stable, but I don't care whether I root and viper or go back to stock as long as the phone works. I would have figured driver issues if not for the perfectly functional/device manager viewable fastboot. Without ADB seeing the device in twrp, I can't sideload, push files or mount storage to get a new rom on there to fix it. I'm not even sure whether it's TWRP or the SuperSU flash that boot looped me, though I figured that by clearing /data/dalvik/cache I killed SuperSU so it might be twrp.
All solutions I've found so far assume that ADB is working/the device can be seen or assume that simple driver reinstalls will fix the problem, but I haven't had any luck with that so far even though I've tried uninstalling/reinstalling drivers a few times.
Any ideas? Please help me - I'm stumped!
Relock bootloader and run an RUU.
HTC One M9
Jtsessions said:
Heya!
Totally new to all of this, so please be gentle. My M9 is now bootlooping and the past hour of research hasn't helped me.
I've just done the following with my Tmobile marshmallow M9:
1) Used HTC's dev tools to unlock the bootloader
2) Flashed twrp-2.8.7.1_CPTB-B1-hima.img using fastboot
3) Immediately after flashed BETA-SuperSU-v2.66-20160103015024.zip using twrp
4) Backed up everything using twrp
My phone is now boot looping. I tried clearing cache/dalvik/data with no luck. Honestly, I'm fine with either loading a stock rom or going to viper like I originally intended, but I don't know how - I don't have either of those on my SD card and I know that I need to get them off of my computer onto the phone, but ADB and my device manager don't see the phone when I'm in TWRP. When I'm in the bootloader, I see "My HTC" in device manager and HTC sync picks up like it sees the phone.
I just want a working phone again. I hear that SuperSU 2.65 is probably more stable, but I don't care whether I root and viper or go back to stock as long as the phone works. I would have figured driver issues if not for the perfectly functional/device manager viewable fastboot. Without ADB seeing the device in twrp, I can't sideload, push files or mount storage to get a new rom on there to fix it. I'm not even sure whether it's TWRP or the SuperSU flash that boot looped me, though I figured that by clearing /data/dalvik/cache I killed SuperSU so it might be twrp.
All solutions I've found so far assume that ADB is working/the device can be seen or assume that simple driver reinstalls will fix the problem, but I haven't had any luck with that so far even though I've tried uninstalling/reinstalling drivers a few times.
Any ideas? Please help me - I'm stumped!
Click to expand...
Click to collapse
Go back to TWRP and flash the stable SuperSU 2.65. Beta bootlooped for me too and then I went back to TWRP and flashed 2.65 and it was fine.
When you're in TWRP you should be able to connect the device to your computer and copy the 2.65 to phone storage and then be able to flash it.
Hello to everyone.
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Its possible to fix? or my phone its ****ed, or there is one form to installl the gapps from anoter form?
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
i offer some pay.
Update:
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
Help me pls:crying:
I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli
Gravemind2015 said:
I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.
vmmiguel said:
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.
Click to expand...
Click to collapse
My windows cmputer says that my device doesnt works properly, i read all night about this and i think when i some point i made wipe /system so i delete the twrp and the rom doesnt have usb adb i think so hahaha, i think now my x4 will stuck on only aosp 9.0 without g services :crying::crying::crying:
id start with a flash all of the latest stock firmware to clean it up. then start over
edufur said:
id start with a flash all of the latest stock firmware to clean it up. then start over
Click to expand...
Click to collapse
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...
vmmiguel said:
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...
Click to expand...
Click to collapse
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.
Comby_sk said:
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.
Click to expand...
Click to collapse
Hello Buddy, i tried that but doesnt work, recently i discover that my usb default mode is gray so i think i cant switch beetwen the usb option, and i tried ADB over network, in terminal emulator to run adbd service but it crash :c
@erfanoabdiadbi plz you cant help me, i really i was enjoying you excelent deveploment, but now in stuck in this without essencial apps like whatsapp, my smartphone works like only phone without been smart jajaja:crying::good:
Anyone?
vmmiguel said:
Anyone?
Click to expand...
Click to collapse
Read through this thread carefully...
https://forum.xda-developers.com/moto-x4/development/rom-lineage-16-0-developer-preview-t3849699
I have more or less the same problem.
I am stuck in LineageOS 15.1 and for some reason Windows does not recognize my phone (it does with other x4 phone from a friend).
I also don't have GApps installed and also don't have root access. Since I can't connect my phone, I can't root or flash some custom recovery.
I really need some help.