I hadn't touched my tab for a couple weeks since I only really use it in my car as a GPS and Entertainment center but when I grabbed it to charge it up, it was completed drained. No problem here since this has happened before and I'd just charge it up. So I boot it after the full recharge and it's stuck on the Samsung Galaxy Tab logo. After a little while I check it again and I'm like, "Crap, it's bricked. I'll need to reset it with Odin."
I proceed with Odin and nothing. It's still bricked. I do a factory reset and this is where I notice my big problem. When I do a factory reset or reboot I get
E:Can't open /data/log/recovery.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernel_log.txt
I tried reflashing the kernel, pit and firmware and I'm getting nowhere. What gives?
try removing the SD card and see if it boots up.
DigitalMD said:
try removing the SD card and see if it boots up.
Click to expand...
Click to collapse
Still no go but this did give me an idea. I just tried a simple reboot from recovery WITHOUT the SD card and got the error:
E:Failed to mount /sdcard
E: is the SDcard so I will create the directory with the files I mentioned above. I found the files on a different thread regarding a Samsung Galaxy phone. This may work.
I'm also going to try another flash without the SD installed to see if I have any luck there.
Thanks.
Issue is fixed
I decided to reflash while the SD card was removed and it got passed the initial splash screen. It was stuck at some wierd lock screen asking for a password. I went into recovery to do a wipe and factory reset and that brought the tablet back to life on reboot.
All is good again.
Background:
I was using stock rom CM11S and franco.kernel, updated to r9 two days ago. everything worked fine, until the vibration suddenly stopped working after I picked up a phone call (where the phone did its "last vibrate").
Issue:
I have searched through this forum and xda and found that there is a solution in https://forums.oneplus.net/threads/vibration-suddenly-not-working.76462/page-2.
So I followed the steps. When I ran "fastboot -w", it stopped and a warning window popped up.
fastboot_error.png
In English it says that "0x00403927 command referencing 0x00000010 memory. That memory cannot be read. Click "OK" to end the program". It actually stops every time when I format "userdata".
I have tried
1. Any other wiping/formatting methods e.g. TWRP or Philz recovery
2. Reflashing the rom and stock recovery.
3. Lock and Unlock bootloader.
But the vibration did not come back......
I believe the only way to get rid of it is to wipe through fastboot (MY ONLY HOPE). Can somebody please help me?
Anyone HELP?
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
Hello,
Earlier this week my nexus 5 refused to boot after i powered it down while at work. The phone begins to boot up but hangs at the spinning colored circles, i have left this over 24 hours and there is no change.
The device is stock and unrooted, I have tried a factory reset from recovery mode which completed OK however did not fix the problem.
At this point i would of normally just RMAd the device however i bought it on amazon, and the seller appears to have imported it from Hong Kong, so there was no valid warranty for me to claim under. Lesson learned there for the future but not a great help for me at the moment.
Because the device would still power up and since the warranty was already invalid i decided to try flashing it to factory. I unlocked the bootloader and flashed a factory image to the device in hopes this would resolve the fault but again just had the same results, I am however totally new to doing this so may have made a mistake here, but from what i can tell i followed the process correctly as i did not receive any errors.
The phone still boots to the same point, and i am still able to access the bootloader, is there anything else you think i can try or is the device bricked?
Flash the factory image with fastboot. See this, http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app
So i attempted to flash again, followed method 2 on the linked post this time.
It all appeared to go through OK until i came to do the final factory reset when i noticed an error on the screen this time.
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (invalid argument)
E: can't mount /cache/recovery/command
E: failed to mount /cache (invalid argument)
E: can't mount /cache/recovery/last_locale
locale is [(null)]
stage is []
reason is [(null)]
After running the factory reset and rebooting the phone it is still stuck at boot
So today after reading around I've found a number of people with similar issues that made some progress by reverting to Kitkat, so i re-flashed the phone to 4.4.4.
The phone now boots up again however i have no reception at all, Google Play store and the camera also appear to not work. All other functions I've tried seem to be OK so there's at least some progress.
I let the phone update back to 5.0.1 but just ended up not booting again so i downgraded once more.
I would be perfectly happy to remain on 4.4.4 so long as my phone actually worked, but at the moment nothing I've tried has managed to correct the lack of reception. I've not found anything online to solve the problem even though some people have mentioned the same issues after downgrading.
Can anyone point me in the right direction?
TigerDude said:
So today after reading around I've found a number of people with similar issues that made some progress by reverting to Kitkat, so i re-flashed the phone to 4.4.4.
The phone now boots up again however i have no reception at all, Google Play store and the camera also appear to not work. All other functions I've tried seem to be OK so there's at least some progress.
I let the phone update back to 5.0.1 but just ended up not booting again so i downgraded once more.
I would be perfectly happy to remain on 4.4.4 so long as my phone actually worked, but at the moment nothing I've tried has managed to correct the lack of reception. I've not found anything online to solve the problem even though some people have mentioned the same issues after downgrading.
Can anyone point me in the right direction?
Click to expand...
Click to collapse
You should try this http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Thank you so much, for a while there i thought i owned a £300 paperweight but everything's running again, you sir are a legend.
TigerDude said:
Thank you so much, for a while there i thought i owned a £300 paperweight but everything's running again, you sir are a legend.
Click to expand...
Click to collapse
Indeed he is! :good: Saved my phone too. I had the exact situation as you http://forum.xda-developers.com/goo...p-lollipop-t3098632/post60491129#post60491129
I am wondering though: In my case the error I got was "failed to mount /persist" , and bitmodo's guide is exactly for that. In your case it was the cache partition. Is there a different command to fix the cache partition?
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