Hi I have moto G 2015 osprey XT1541, its unlocked running cyanogenmod
I recently upgraded to CM 14 experienced problems instantly, all the google apps wpuld crash.
Reverted back to CM 12 which worked and it had an error whilst upgrading in recovery,
something like
E:Failed to map file
E:Error exit from the fuse process :0
Installation Failed Installation Aborted
I have tried multiple roms, all come back with same error message. The recovery on the phone is the cyanogenmod one. Also in recovery if I do system reset I get
E: Failed to mount /data (permission denied)
I am having to try installing roms via sdcard as the phone is not recognised by my computer.
Any Ideas?
I would format userdata in bootloader then install TWRP and use that to install the next rom.
es0tericcha0s said:
I would format userdata in bootloader then install TWRP and use that to install the next rom.
Click to expand...
Click to collapse
How do I format userdata? I dont have that option in the bootloader. When I try to install anything using cyanogemod recovery including TWRP I get the same error message.
fastboot format userdata
fastboot format cache
If that doesn't work then you'll want to go back to complete stock with the original firmware for your variant (and carrier if yours came from one originally).
The phone cannot connect to PC with USB for some reason. So I cant use fastboot. I know its not the cable/PC as it works with my tablet so must be the phone.
I have tried wiping data and factory reset in recovery and this does not solve the problem, still stuck in boot loop and recovery cannot flash any roms.
AndyGLowe said:
The phone cannot connect to PC with USB for some reason. So I cant use fastboot. I know its not the cable/PC as it works with my tablet so must be the phone.
I have tried wiping data and factory reset in recovery and this does not solve the problem, still stuck in boot loop and recovery cannot flash any roms.
Click to expand...
Click to collapse
Check out the Device Manager (assuming you're using Windows...) and see if the driver is loading correctly. If not, you should be able to manually update the driver. This is the most common problem that would cause this. Even if the phone is borked, fastboot mode should work and the PC should be able to load the drivers. If that fails, try other ports on your PC or another PC altogether.
Uninstall all the Moto drivers, reboot, reinstall and look into RSD Lite if all else fails.
es0tericcha0s said:
Check out the Device Manager (assuming you're using Windows...) and see if the driver is loading correctly. If not, you should be able to manually update the driver. This is the most common problem that would cause this. Even if the phone is borked, fastboot mode should work and the PC should be able to load the drivers. If that fails, try other ports on your PC or another PC altogether.
Uninstall all the Moto drivers, reboot, reinstall and look into RSD Lite if all else fails.
Click to expand...
Click to collapse
I doesn't even show in Device Manager, I have tried another system with Win 7 on and that comes up with a notification saying a unrecognised device has been attached. But it doesn't make a difference if you install the drivers or look in device manager, had exclamation mark next to device but you cant do anything. I also have Ubuntu dual loaded on this system and that doesn't recognise it either.
Same issue on Xperia ZL... This CM14 ruined my phone.. exactly same issue... Some one help plzzzzzzzzzzzzzzzz
sahil soni said:
Same issue on Xperia ZL... This CM14 ruined my phone.. exactly same issue... Some one help plzzzzzzzzzzzzzzzz
Click to expand...
Click to collapse
did you guys solve your problem I have the same exact issues?
Related
i cant boot my huawei u8180 into recovery
i rooted it by super one click
when i tried to flash recovery with rom manager premium it restarts then freeze in boot screen
tried to reset my phone from settings ,privacy it also reboot but freeze on boot
i dont know wt to do
PLZ HELP ME WITH THIS ISSUE
plz any one tell me anything i can do with this problem
i cant even reset my phone
plz reply
thanks guys , i solved my problem alone ,, and insalled cyanogenmod 7.2
everything is ok now
how do you solved your problem with huawei u8180? i have the same isue.
Sorry to bump an old thread
I'm having the exact same problem.
Rooted the 8180 with SuperOneClick, installed Rom Manager, from Rom Manager installed CWM 8160 version with sucess, and whenever trying to boot into recovery mod the phone just hangs while showing the hourglass icon.
I tried reflashing the CWM and it still hangs
Im still running the stock firmware/rom
Can you share how you solved this problem?
Hi, I had a similar issue and did a reboot in to the CWM by holding power, volume up and the "search button" (?) the right one any way. Then did a wipe/factory reset.
Norpan70 said:
Hi, I had a similar issue and did a reboot in to the CWM by holding power, volume up and the "search button" (?) the right one any way. Then did a wipe/factory reset.
Click to expand...
Click to collapse
So you could only boot into CWM by pressing power+volume+search? The regular way (power+volume) would lock up like it does to me, is that it?
Anyway I tried your key combination and it still freezes...
Codeman666 said:
Sorry to bump an old thread
I'm having the exact same problem.
Rooted the 8180 with SuperOneClick, installed Rom Manager, from Rom Manager installed CWM 8160 version with sucess, and whenever trying to boot into recovery mod the phone just hangs while showing the hourglass icon.
I tried reflashing the CWM and it still hangs
Im still running the stock firmware/rom
Can you share how you solved this problem?
Click to expand...
Click to collapse
Bug with rom manager, you should try flashing atleast 3 times and then try and go into recovery, happened to me also, just flash again through rom amanager.
Maeur1 said:
Bug with rom manager, you should try flashing atleast 3 times and then try and go into recovery, happened to me also, just flash again through rom amanager.
Click to expand...
Click to collapse
I already flashed about 5 times and still freezes
Hi,as for the fastboot instructions - I've found this to be a great help in getting adb and fastboot to work on my Win7 x64 installs,so you might want to give it a try. Also,I'm gonna upload in a bit the earlier recovery + recovery manager (if you want to try that before you play around with adb/fastboot) to flash it to your device + the device drivers.
Edit - The link for the file - http://ubuntuone.com/14mi7lUkJelsrNBr4z5Uy2 - 12.5 MB - contains the older recovery (you can still try to flash the newer one first if you want), 2 different driver packs and the aforementioned recovery manager.
bk109 said:
Hi,as for the fastboot instructions - I've found this to be a great help in getting adb and fastboot to work on my Win7 x64 installs,so you might want to give it a try. Also,I'm gonna upload in a bit the earlier recovery + recovery manager (if you want to try that before you play around with adb/fastboot) to flash it to your device + the device drivers.
Edit - The link for the file - http://ubuntuone.com/14mi7lUkJelsrNBr4z5Uy2 - 12.5 MB - contains the older recovery (you can still try to flash the newer one first if you want), 2 different driver packs and the aforementioned recovery manager.
Click to expand...
Click to collapse
Thank you! Im trying recovery manager as I type this, I find it curious it says "Currently installed recovery: unrecognized"
As for the driver, I already had it installed from when I rooted the phone.
EDIT: So I installed the up to date recovery (recovery-clockwork-5.0.2.8-u8160) with Recovery Manager, still unrecognized and still freezes after booting into recovery.
Installed the one you supplied (ClockworkMod-u8160-v0.1) and got the exact same results, unrecognized and freeze
Codeman666 said:
Thank you! Im trying recovery manager as I type this, I find it curious it says "Currently installed recovery: unrecognized"
As for the driver, I already had it installed from when I rooted the phone.
EDIT: So I installed the up to date recovery (recovery-clockwork-5.0.2.8-u8160) with Recovery Manager, still unrecognized and still freezes after booting into recovery.
Installed the one you supplied (ClockworkMod-u8160-v0.1) and got the exact same results, unrecognized and freeze
Click to expand...
Click to collapse
In that case you might want to try the doomsday option - fastboot (not really,hell - it's actually rather useful + if you follow that website you also get adb up and working too). As for the 'unrecognized' alert,I remember getting it too once upon a time,but I have to admit - I haven't used the app myself since when I made the jump from the stock 2.2.1 ROM to a custom froyo build,so I can't recall for the moment what I did to fix that error
bk109 said:
In that case you might want to try the doomsday option - fastboot (not really,hell - it's actually rather useful + if you follow that website you also get adb up and working too). As for the 'unrecognized' alert,I remember getting it too once upon a time,but I have to admit - I haven't used the app myself since when I made the jump from the stock 2.2.1 ROM to a custom froyo build,so I can't recall for the moment what I did to fix that error
Click to expand...
Click to collapse
Will do. Besides the fastboot recovery command what else do I need to do from the phone side?
Does fastboot display any feedback or log about the flashing/installation?
Codeman666 said:
Will do. Besides the fastboot recovery command what else do I need to do from the phone side?
Does fastboot display any feedback or log about the flashing/installation?
Click to expand...
Click to collapse
Nothing specific -you just have to reboot in fastboot mode (just restart the phone while pressing Power and Volume Down. Windows should chirp and install the drivers automagically - afterwards just use that command discussed earlier and it should flash your recovery without any additional prompts (it should only print out a confirmation of a successful flash) and you should have the CWM ready to go
Edit: I put my device into fastboot mode on a clean Windows install (a Win8 Consumer Preview) and it did autodetect and install the relevant driver without restarting itself
No luck... Now it's driver issues
When booting the phone with either the vol up or down pressed and pluging in the USB my PC isn't recognizing the driver, I used both drivers you sent me.
Initially it's detected as Android 1.0 device, upon fetching the drivers it gets named "Android Sooner Single ADB Interface".
As I refresh device manager it goes back to Android 1.0 with an exclamation mark.
I think it's a driver signature issue, I'll try again in a couple of hours in a different PC
edit:in debug mode I have no driver issues and I can even detect my phone with ADB
Finally!
Tried it in another computer, auto downloaded some ASUS adb driver and installed fine.
Flashed latest CWM recovery with fastboot and now I'm able to boot into CWM!
Thank you so much for your help!
Sry for bumping.
So, i had the same trouble with the drivers. But i just downloaded HiSuite directly from the Huawei Site and these fix my problem with drivers to use adb without troubles . Hope this help someone.
BTW, Thanks bk109!
It did helped me thx man
Sent from my U8180 using xda app-developers app
sry for asking this now since 7 years iam brick free but now i think it is ...
i have root it and installed the kernel from hear so now it runs really great a long time but yesterday i get an notify for an u.date
i click on yes and and then because it doesnt start again i wi-cache and reboot soo now iam in trouble no driver no com. regognize my watch as an watch just a unknown device.
i came into downlaod mod fastboot and into recovery but when i start it stucks hours in the boot sequenz
i cant run any adb because i didnt found a adb device ... than i think the real trouble came with that that i make an factory reset ... so for all here i try out all in flash tool all is ready but when the watch goes into download mode the com. write me a unknown device in that case the flashtool found no watch and the watch rebooting...
and jet its on you all to answer me why i cant get it back to life ..##
thx and a nice evenning
ashvarkul92 said:
sry for asking this now since 7 years iam brick free but now i think it is ...
i have root it and installed the kernel from hear so now it runs really great a long time but yesterday i get an notify for an u.date
i click on yes and and then because it doesnt start again i wi-cache and reboot soo now iam in trouble no driver no com. regognize my watch as an watch just a unknown device.
i came into downlaod mod fastboot and into recovery but when i start it stucks hours in the boot sequenz
i cant run any adb because i didnt found a adb device ... than i think the real trouble came with that that i make an factory reset ... so for all here i try out all in flash tool all is ready but when the watch goes into download mode the com. write me a unknown device in that case the flashtool found no watch and the watch rebooting...
and jet its on you all to answer me why i cant get it back to life ..##
thx and a nice evenning
Click to expand...
Click to collapse
Make sure you have the Universal ADB Drivers installed, open device manager and select the unknown device that matches your watch in fastboot mode. Choose to browse from a list of drivers and the hit Have Disk, browse to the Universal ADB Driver location in Program Files and then from the list that appears after selecting OK, choose LG Android Interface (or similar) and press Next. It should install the driver and you should be able to flash back. The reason that you bricked was because you did a factory reset on the Arter kernel which seems to expect (I may be wrong here..) all filesystems to be F2FS (which it converts to when it installs, a factory reset wipes the partition back to it's stock format it seems), as I soft-bricked after factory resetting on the Arter kernel as well. Hope this helps.
ShadowEO said:
Make sure you have the Universal ADB Drivers installed, open device manager and select the unknown device that matches your watch in fastboot mode. Choose to browse from a list of drivers and the hit Have Disk, browse to the Universal ADB Driver location in Program Files and then from the list that appears after selecting OK, choose LG Android Interface (or similar) and press Next. It should install the driver and you should be able to flash back. The reason that you bricked was because you did a factory reset on the Arter kernel which seems to expect (I may be wrong here..) all filesystems to be F2FS (which it converts to when it installs, a factory reset wipes the partition back to it's stock format it seems), as I soft-bricked after factory resetting on the Arter kernel as well. Hope this helps.
Click to expand...
Click to collapse
How would you recovery after reinstalling the adb drivers? I'm in a similar situation right now with the custom kernel.
After installing the driver, you should be able to use the LG G Watch Restore Tools package on these forums to reflash the system and boot partitions. That will replace your kernel with the stock one.
ShadowEO said:
After installing the driver, you should be able to use the LG G Watch Restore Tools package on these forums to reflash the system and boot partitions. That will replace your kernel with the stock one.
Click to expand...
Click to collapse
No iam not .. i tried all out no device in fastboot no device in adb and in linux there are no drivers you need .. i think that the preloader is damaged ... i find nothing so that is sure an soft brick but no one can handle it for now ..
If you can get into Fastboot, then there is something wrong with your USB cable or your pins. Fastboot itself should appear, maybe as an unknown device that appears and disappears when you connect and disconnect. Clean your pins, try another cable and check device manager to make sure you don't have an Unknown Device sitting in there.
I was running CM12 and everything was fine. I received a notification to update to CM 13 and I selected yes. It installed OK, but no GAPPS. I tried everything I could think of to install GAPPS, and kept getting errors. IN my frustrated efforts, something happened to my TWRP and now I only have CM Recovery. I'm trying to reinstall TWRP but my phone is being recognized as a "Marshall London Bootloader Interface" ONLY when in the Fastboot and Recovery mode. I have Huawei Hisuite installed and it recognizes the phone fine when powered on, but as soon as I boot into Fastboot and Rescue mode, it reverts to the MLB interface. I am at my wits end as to how to get my PC to recognize my phone properly when in Fastboot and recovery. I did try removing and reinstalling drivers when in Fastboot, but the Marshall Interface keeps on getting inserted. Any suggestions?????? (I also seem to have erased the SD card that has my original system backup files on it. I tried to flash several downloaded stock ROMs using CM recovery, but they all error out. )
I was finally able to re load TWRP using the Huawei Hi Suite. I flashed Carbon ROM and GAPPS and everything seems to be OK but I still cannot use ADB because the phone is recognized by Windows as a Marshall device ONLY when in bootloader mode and ADB does not find the device. When I connect normally it is recognized as a Mate 2 and it connects normally to Hi Suite. I have no idea what could be wrong, but I have read of other people who have this mysterious "Marshall" device show only up when in bootloader mode. Anyone have any ideas????? Can I go back to stock from here if I don't have a saved recovery image to see if I can fix this???
I have no idea what Marshall device means. Is it possible to place the stock 5.1 ROM on a blank micro SD card and follow the flashing instructions? (boot to download mode or whatever it's called)
ScoobSTi said:
I have no idea what Marshall device means. Is it possible to place the stock 5.1 ROM on a blank micro SD card and follow the flashing instructions? (boot to download mode or whatever it's called)
Click to expand...
Click to collapse
I explained what "Marshall Device" is in the first post. I ended up going back to stock (322) and loosing root. I then updated to 5.1 using the SD card. Everything seems to be working OK. Maybe I'll root again and start over when I have more time.
Yesterday I tried to flash a a new rom on my Xperia Z2 (unlocked bootloader).
From TWRP I did an advanced wipe and selected basically everything except my mircoSD (because it has the new files).
After a long time of waiting I tried to flash the ZIP file and it gave me an error. I thought this had to do with the wipe so I decided to reboot my phone.
As you can imagine, it got stuck on the Sony logo (because system would be empty).
From this moment I couldn't do anything with my phone, except from the tool Emma.
I now have some clean installation of Sony their Android 6.0.1 for the Z2 (23.5.A.0.570) but Im unable to flash TWRP through fastboot.
The command adb devices shows my phone, fastboot devices gives an empty response.
When I restart to the bootloader from adb and try to flash TWRP I get the message "< waiting for device >".
I tried on three different PCs including a clean install of Windows with all kind of different drivers, yet I cant get fastboot to work.
Am I stuck with this unrooted version of Android now or do you guys have any suggestions for me?
Thanks in advance!
Install drivers correctly
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
As I said I've tried all kind of different drivers (Android tools, Sony drivers and flahstool drivers). So for me it's hard to tell what I'm doing wrong.
My computer notices the phone (if I hold volume up and attach the charger), it just doesn't show up under fastboot devices.
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
PaulusE said:
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
Click to expand...
Click to collapse
Manually boot into recovery by booting up your device normally and when you see a violet LED, press vol+.
I have an Infinix Note 3 X601, updated to Android N, Rooted and Philz Touch 6. 59, 0 custom recovery installed. Problem began when I tried to factory reset it from within the settings, the phone rebooted to recovery to wipe the data, and since then it wont boot to system again, whenever i try to boot it to system, it will go to recovery. if i connect it to pc, the pc wont recognise it, the pc will show a message that the USB device is not recodnisd, and the phone will boot to recovery again.
i tried to reflash the stock firmware using sp flashtool and it always fails as the system will not recognise the phone, even though i have the required mtk drivers installed.
i tried to flash this https://androidhq254.blogspot.com.ng/2017/04/mad-aosp-n-711-for-infinix-note-3-x601.html and http://bbs.infinixmobility.com/thread-149453-3-1.html custom roms using the custom recovery, they all fail mid way.
i will appreciate any help i can get in reviving this phone. thanks in advance
i have a. zuk z1 i did something like this and the phone got bricked I then tried installing other roms and also backups but the phone only boots upto recovery..
i unbricked the phone using "qpst tool" see if your phone have something like that
arn2641 said:
i have a. zuk z1 i did something like this and the phone got bricked I then tried installing other roms and also backups but the phone only boots upto recovery..
i unbricked the phone using "qpst tool" see if your phone have something like that
Click to expand...
Click to collapse
thanks for the reply, could you elaborate on the "qpst tool" pls, i dont know much about it
qpst is a kind of software
that enable us to use a port in the phone to install firmware and others software when something like this happens...
some manufacturers like Samsung manufacture in such a way that this cannot be used,
depending upon your manufacturer and the processor(it mainly support snapdragon i think) you may get if you search in Google.
arn2641 said:
i have a. zuk z1 i did something like this and the phone got bricked I then tried installing other roms and also backups but the phone only boots upto recovery..
i unbricked the phone using "qpst tool" see if your phone have something like that
Click to expand...
Click to collapse
when i try to flash a rom through recovery it shows:
mount system partition
mount: failed to mount /dev/block/platform/mtk-mdc.0/11230000.mdc.0/by-name/system at /system: no such file or directory
unmount system partition
unmount of /system failed: no such volume
format system partition
E:Error in /storage/sdcard/........
(status0)
installation aborted
what do you make of this pls?