My wife's stock moto g phone went into what I can only guess was some sort of bootloop this morning. I have been playing with it all evening with no luck. I could get into fastboot, but selecting recovery I would end up in another sort of loop where I could see the distress "no command" image briefly flashing on the screen every 5-10 seconds and there was no way to use the volume/power buttons to get into the recovery screens. No warranty left on the phone so I decided to play.
I was able to use adb to unlock the boatloader, root the phone and flash TWRP, I could push over a copy of a slimkat rom I chose, but whenever I attempt to wipe cache and what not I keep getting mount errors (can't mount /data, /system, etc.) Trying to format gives me mount errors as well, and using file manager all directories appear empty except for anything I push over to /sdcard
I since flashed using adb (Philz Touch 6) and once again all I see are mount errors....
I guess my question is, is it possible that this could be a hardware issue and and will never get passed this ? Or have I accomplished enough above to prove there is still life in the phone and just need to keep searching and trying things?
If you think there is a chance, any ideas of what I could try next?
Thanks
Morgan
Related
Hi guys newby here and certainly newby on the android custom firmware user.
So i recently acquired a G3 (free) that was (and still is) in a bad shape. Can't use the side volume buttons as they were ripped off the motherboar
Also the stock firmware was a locked (by password).
So i decided to upgrade firmware to a custom rom. Tried the M12 rom but in the recovery could not do wipe (due to volume buttons) and although it worked, everytime i turn phone off then on i have to enter all the preferences from afresh.
Flashed a kernel with touch recovery (v5.0.2.8) and this helped a lot and i am now able to do wipe/reset wipe cache but after that an error comes with E: can't mount cache... can't mount etc etc etc and when it gets to do wipe dalvick cache it does not give me even the option to do that!
Any help? thank you in advance.
phonesurgeon said:
Hi guys newby here and certainly newby on the android custom firmware user.
So i recently acquired a G3 (free) that was (and still is) in a bad shape. Can't use the side volume buttons as they were ripped off the motherboar
Also the stock firmware was a locked (by password).
So i decided to upgrade firmware to a custom rom. Tried the M12 rom but in the recovery could not do wipe (due to volume buttons) and although it worked, everytime i turn phone off then on i have to enter all the preferences from afresh.
Flashed a kernel with touch recovery (v5.0.2.8) and this helped a lot and i am now able to do wipe/reset wipe cache but after that an error comes with E: can't mount cache... can't mount etc etc etc and when it gets to do wipe dalvick cache it does not give me even the option to do that!
Any help? thank you in advance.
Click to expand...
Click to collapse
Actually, i had some similiar issues, some months ago... i actually ignored it, because it didn't bother me that much, but then once after restarting all my apps were gone...
so i guess it has something to do with the filesystem, because in g3mod.log there was an error on booting because fsck (the filesystemcheck of android) didn't return a clean filesystem...
i experimented a little and formated cache from recovery, that seemed to do the trick once, but not always...
running e2fsck forced with all yes through adb shell repaired my filesystem and since then i didn't have any problems anymore, but i don't know if that's so good doing with an installed rom, because maybe some systemfiles are ruined after that, who knows?
could you maybe post the exact errors from recovery...
Does your phone boot? How did you manage to get into download mode and recovery without using your volume buttons?
Rhala said:
Actually, i had some similiar issues, some months ago... i actually ignored it, because it didn't bother me that much, but then once after restarting all my apps were gone...
so i guess it has something to do with the filesystem, because in g3mod.log there was an error on booting because fsck (the filesystemcheck of android) didn't return a clean filesystem...
i experimented a little and formated cache from recovery, that seemed to do the trick once, but not always...
running e2fsck forced with all yes through adb shell repaired my filesystem and since then i didn't have any problems anymore, but i don't know if that's so good doing with an installed rom, because maybe some systemfiles are ruined after that, who knows?
could you maybe post the exact errors from recovery...
Does your phone boot? How did you manage to get into download mode and recovery without using your volume buttons?
Click to expand...
Click to collapse
The phone does boot and works as it should now... albeit i can't get any sim card to work with it.Although there is a possibility that this phone is actually blacklisted (reported lost or stolen).
I used odin to flash different kernels, at the moment i am using G3Mod kernels and that supports touch recovery, and i ve also got CM9 as the main operating system. after that i use the reboot in recovery options from phone, thats the only way.
try making a fs.convert file
try making a custom fs. convert file n putting it in ur SD. else try this app g3mod configuration from play store n convert the filesystem as required by ur rom n kernel. U should check the dev page for supported file systems. Even I faced similar problems b4 on kyorarom. But now everything is fine.
https://play.google.com/store/apps/...ogle&utm_medium=organic&utm_term=g3mod+config
http://forum.xda-developers.com/showthread.php?p=18868074
Hey, I need some help.
CyanogenMod doesn't mount my sdcard anymore. I mean its mounted but cannot be used (sdcard is in /data/media/0 are the files but there's no /storage/emulated/0). My Recovery is also showing after every operation that its unable to mount 'persistent'. And then my sim is not working and the camera force-closes.
That all started by me dropping my phone - Crack in the glass. So I saw some tutorials on how to switch the screen. Shouldnt be really difficult and just to try I opened the back of the n5 and closed it with not even really touching any of the hardware I closed it. Then I tried to boot from my CyanogenMod so I got my bootanimation and then a **** ton of pop ups telling that probably everything is crashing. Pressed ok, ok, ok and it showed the boot animation again. Same again and again. It didn't even asked to decrypt the phone >.<
So I turned it off and started the recovery (TWRP), which was showing E: Unable to mount 'persistent'. Had no idea what to do and why soooo
- Factory Reset - flashed another version of cm back on
Same ****
- Complete wipe (Backuped my files) - flashed
I got to the GUI but no sdcard mounted
- Tried to flash Stock ROM from Google - Bootloop and of course no recovery
- Another Factory Reset plus cm flash
Same as after the wipe
- Tried another version of TWRP
Same
So what should I do? Did I broke my phone by opening the back?
I hope not so it would be awesome if you could help a kinda noob like me
I have a Samsung Galaxy tab 2 GT-P5110 which I had successfully installed CM12 onto. I decided to set up work email which insisted that I encrypt the device. I believe that the process completed successfully.
At that point I decided that I would like to flash the device with CM12.1. Restarted the process (Factory reset, Wipe Cache, Wipe dalvik cache) and flash the new CM12.1 zip file from external SD card.
I cannot now get to the recovery mode and the device doesn't always boot into anything recogniseable. The screen goes black and blacker! I have manaed to get to the CM logo and then a screen asking me for the PIN for the encryption. The next screen tells me that the PIN is right but the data is corrupt. It gives me the option to "RESET TABLET" but that really doesn't do anything and won't let me in to the recovery menu.
I can get into the Download mode and connect Heimdall up to it.
Is there anything that anyone can point me at that will help me to unbrick it?
I hope I've passed on enough information to help. It seems to me I need to somehow re-format the internal SD but I can't get to any menu that will allow me to do that.
Any thoughts anyone?
Ta
Fixed It
I seem to have fixed it. I flashed the CWM Recovery rather than the recovery that I had been trying to use and I got control of the device back. Not sure why that made a difference but this time the Android Robot came on screen with the 3D polygon rotating inside it and it seems to be running correctly now and updated to Android 5.1 ... Magic!
Hi everyone,
I have a Nexus 5 that, up until recently, was unlocked and rooted. However, my power button started giving me issues, and after looking around online I determined it was a hardware issue. My phone is still within the warranty period, so I decided to unroot, re-lock, and reset the warranty flags. To do so, I used WugFresh's Nexus Root Toolkit. This seemed to work fine.
However, later on my battery died while I was out away from home. When I plugged it in overnight to charge, I woke up to find that it was stuck on the flying dots boot animation. I haven't been able to get it to start up since then.
All the solutions I find require flashing a custom recovery, or the factory image. However, I can do neither, since my bootloader is now locked.
I've also tried re-unlocking the bootloader using both the NRT and the manual method described here. The final reboot never progresses past the flying dots animation, and when I hard reset and relaunch into fastboot mode, it tells me that the bootloader is still locked.
As an alternative, I tried booting into recovery mode/recovery menu and doing a factory data reset there. I get the following error messages:
Code:
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recover/log
... and so on for every folder it tries to access on the cache partition. Afterwards, when I reboot, same problem. Flying dots and that's it.
Note regarding all of the above: in each case I've tried to let the boot animation run for as long as possible just to make sure. At minimum, I've let each method go for at least an hour and a half, but it never progresses any further.
So. How screwed am I? Does anybody have a solution to get my phone working again?
You can still try to flash to stock image with Julian OS tool (script)
http://forum.xda-developers.com/goo...o-flash-5-0-lrx21o-flash-5-0-n5-tool-t2957801
This script unlocks your bootloader, flashes os 5.0/5.01 and relocks your bootloader, all within 2 minutes. I have tried it and it works fine. At the end you have a stock unrooted device.
Trying to root my phone. Flashed TWRP in Odin, then installed SuperSU through TWRP. At the end it gives me the error in the title, and I get a 'failed integrity check' when booting into the system.
Help?
I've always read you have to do a factory reset after TWRP installation due to encryption, but apparently you don't have to
It still says you lose your OS though.
https://forum.xda-developers.com/galaxy-s7/help/root-twrp-flashing-t3535545
AzzyC said:
No factory reset required. Basically, the file system of your Data partition is incorrect and that is why it can't be mounted on to.
Go to 'Wipe'->'Advanced Wipe'->Click on the Data box->'Partition Options'->(You may be seeing values like 0mb for most of the information displayed and why you can't mount to it; if you are not let me know!)->'Change File System'->(Try out different File Systems until you being to see true values for the sizes, but avoid using EXT2 and EXT3 if you can)
Doing all this you will be able to Mount to your Data partition, however your OS will be deleted! So get your phone into Download mode, open up Odin program on your PC, and flash a Bootloader (BL) and your phone will be fine.
Then flash the 'no-verity-encryption-opt.zip' and then your SU Binary and Xposed Framework etc.
Good luck again Buddy!
---------- Post added at 05:41 PM ---------- Previous post was at 05:12 PM ----------
Wait Install the No-verity zip first then, then flash a BL
Click to expand...
Click to collapse
It's a brand-new phone so I don't really care about the OS.
Also I tried restoring my Nandroid backup, but the drive appears empty when I go to the "Restore" option in TWRP. Not sure if I need to fix the data thing first anyway, but surely it should show up?
EDIT: Now that I think about it wasn't there some requirement to clear a cache at some point? I vaguely remember that from the last time I rooted an S7.
I've tried formatting, and the readout says "formatting" and then "Done.", but there's still a progress bar and the title area still says "Formatting...".
EDIT 2: It's plugged in but the battery is still dropping, and it only started at 8%. So it might just die anyway.
I recently went back and forth between Oreo and a TWRP Nougat backup, and was flashing TWRP each time I went up to Oreo because I was installing it via Odin which was blowing away TWRP.
I must have had to factory reset and flash the dm-no verity.zip a few times each TWRP install before I got /system and /data to not return an error. I was probably doing something out of order, but it always seemed finnicky.
How does one do the factory reset?
TWRP still reckons it's formatting, even though it says "Done.", but the battery has just hit 0% so it won't last much longer anyway.
EDIT: Or not...battery still going strong at apparently 0%. But it's been formatting for over two hours now.
Advanced wipe with data, cache, and davlik cache checked should be enough
When was I supposed to do that step? It rings a bell but it isn't in the instructions I found.
The phone finally died, and now I cant' seem to get past the TWRP splash screen.
EDIT: Just plugging it in results in the TWRP splash screen. None of the buttons seem to do anything, so I can't get into download mode and reflash TWRP or anything...
Okay, so I left it on the charger for a couple of hours.
Pressing and holding the power button turns it off. A few seconds after plugging it in, I get the Galaxy splash screen followed by the TWRP splash screen, and then the latter just stays there. Forever.
Once I turn it off, I'm unable to turn it back on at all - standard boot, recovery or download. I pressed and held the buttons for a full minute, made no difference.
EDIT: Leaving it off the charger results in the screen turning off a few minutes later. Again, no amount of pushing the buttons will do anything.
EDIT 2: Got it into download mode by plugging it in and holding the buttons down while waiting for it to automatically boot. Next step? Flash a bootloader, or reflash TWRP, or both?
Tried reflashing TWRP, changes nothing. Also tried flashing a BL and CP from the last time I installed SupermanROM, but it failed in Odin. Not sure if they're just too old or something, I have no idea how that stuff works or how updated my software is or anything.
It's the same handset I had before, but it had to go back to Samsung for repair because the battery blew up, so they very kindly wiped everything, reset Knox, etc.