warning no file_contexts cwm error - General Questions and Answers

I tried to make whatsapp., my system app and rebooted the device and apparently lost my rom(custom) itself. NOW... when i try to flash my backup it just stuck in bootloop. I tried flashing different ROM's(custom) but its still stuck in bootloop. I am also not able to restore system through my CWM nor able to format system it just says that its "formatting system..." but nothing happens i even kept my phone idle for 20 minutes or so. Help please.

Related

Stuck at boot animation after installing factory image

Hi there
I wanted to install the Android L developer preview on my Nexus 5. For this I had to unlock the bootlader because it was still locked. That worked fine.
I then downloaded the Android L image for my Nexus 5 tried to install it, got stuck at the google logo and then thought to just roll back to Android 4.4. So I downloaded the factory image from google, switched into fastboot mode, and executed the flash-all.sh script (running on Ubuntu). That seemed to work, device restarted a few times but got stuck on the boot animation logo again.
I wanted to switch into recovery mode to wipe the cache, but the red triangle appears. As quick solution, I just downloaded the clockworkmod-recovery and installed it using the fastboot flash recovery clockworkmod.img command. That worked, I was able to get into the clockworkmod recovery, wiped everything and restarted, but I'm still stuck at the boot animation.
While wiping I had the following messages in the log:
Code:
Formatting /data
Error mountin /data
Skipping format
Formatting /cache
Formatting /sd-ext
E: unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure
Error mounting /sdcard/.android_secure !
Skipping format..
Data wipe complete.
When rebooting from clockworkmod it asks me if I want to root my device because it seems to be unrooted. I've tried accepting and declining that message, but I can't still boot up my device. Anyone got any idea what might be wrong here?
Thanks alot!
Edit: Allright, somehow, after hours of spending with reflashing, it seemed to work. I can't remember to have done anything special. Only thing I did different was that I executed every command from the flash-all.sh by hand instead of executing the flash-all script.

[HELP] Problems just after official lollipop update.

Let me start form the beginning.:-
My bootloader was locked and I was on stock 4.4.4 . I faced no problems at that time. I saw OTA notification for lollipop 5.0.2 update, downloaded it, installed it, device gets restarted, I saw new bootlogo and then bootanimation. Just after the bootanimation, the screen goes blank(back-light is still on). I waited for about 40-50 minutes, but the screen is still blank with backlight on. Tried rebooting 3-4 times but stuck after bootanimation. 1 time it booted successfully and I was presented with the lockscreen. I swiped unlock the screen but suddenly services was stopping one by one and various applications also getting force closes, even the launcher also got force closed. So I rebooted again, and again got stuck after bootanimation, getting only a blank screen with backlight on.
Now I booted my phone into recovery, factory reset it(also wiped cache manually) and then booted into system, still no good. I was getting the same blank screen after bootanimation. I tried rebooting 4-5 times and at one time, it got past the bootanimation. There I saw that the device didn't get factory reset(wallpaper, home screen icons were at that place only where it was before). Now again service got stopped and apps got force closed.
Now, I downloaded stock firmware images from here on xda and flashed it from bootloader. I was still getting blank sceen after bootanimation and occasionally it got booted and everything force closes again.
After trying everything, I unlocked my bootloader and tried flashing a custom recovery (so that i can try installing custom roms). But after successfully flashing custom recovery, I booted into recovery and find that it didn't got flashed (I was still on stock recovery). I tried flashing different custom recoveries 7-8 times, but the stock recovery persists!.
So, now the bootloader is unlocked, stock recovery is persisting after flashing any custom recovery, even the user data is persisting after factory reset, and I am unable to boot to system properly. I don't know what to do after this. Please let me know if this all means that some part of the hardware is failing in my moto g or if it can ever be come back to life.
Edit:- I have just booted into twrp Recovery(not flashed, only booted) and found that I am unable to wipe internal storage. Everything else like, dalvik cache, data, cache and system do not give error on wiping. Also, I am unable to delete any file or folder using twrp file manager
Thank you.

Boot loader corrupted

Hi
My OPO is stuck at bootloader...after few mins it say "Process system isn't responding" and it restarts and again get stuck on boot logo.
My phone is rooted....I have tried recovery mode ----wipe cache etc etc but same thing.....where am i going wrong. I have also tried fixing it thru ADB method but that didnt fixed the issue as well.
Please help.
Flash stock ROM, Or reflash any ROM. Bootloader isn't corrupt, it's ROM/addons issue

Encryption unsuccessful

Hey there!
I have a problem: My wife's WIKO rainbow 3g suddenly showed this message:
She pressed the button several times, but nothing happened.
I booted the phone into stock recovery and tried to wipe /data, but then it says "mount /data error! Force format /data". It looks like it starts to format, but after a few seconds it ends with no message at all. Tried to reboot afterwards, but now it is stuck in the "Rainbow"-bootscreen.
Tried to update the phone using the WIKO software, but the phone isn't recognized anymore.
It's still on stock recovery, as it isn't rooted yet.
Is it possible to root the phone and install a custom recovery in stock recovery mode? Or is there any other way to make the /data partition accessible again?

Accidently wiped /dev/block/sda, now won't get past boot logo

So i was trying to create a bootable usb for linux from my phone. I'm 90% sure my usb was mounted at /dev/block/sda, i did my "dd" command and unplugged the usb only to notice it was unchanged and my device was frozen. After powering off, i was brought directly to the download boot.
So first I tried flashing mu stock firmware, then i tried flashing Lineage Os with twrp. The boot logo just continues. I tried formatting with twrp, wiping cache with default recovery. I tried recovery. I just keep getting an error about EFS not mounting, but i thought that only affects radios/modems.
I don't know what to do Any ideas?

Categories

Resources