Database Users

[Q] Strange Rooting Problem

A friend of mine with a Google Nexus 4 attempted to root on 4.4:
"The unlocking of the bootloader went without a hitch, and I downloaded the CWM non-touch from here:http://www.clockworkmod.com/rommanager, in the "Nexus 4" row, and "Download Recovery" column, named "6.0.4.3". I placed the file on the desktop, flashed it onto the phone, and booted into it using the volume keys and the power button to select "Recovery mode" on the bootloader screen. From there, I wanted to reboot the phone, so I clicked the first option, the "reboot system now" selection. I received the message "ROM may Flash stock recovery on boot. Fix? THIS CAN NOT BE UNDONE.", and not wanted to do anything to mess up the installation, clicked the "*****Go Back*****" option. And then I received another message saying, "Root access is missing. Root device? THIS CAN NOT BE UNDONE." Again, I clicked the "*****Go Back*****" option, not wanting to mess up the recovery. It suddenly booted into the stock ROM, showing the Google screen with a little unlock symbol at the bottom. Then it moved on to the Kit Kat boot sequence, the one with the 4 different colored circles and all that. I waited for it to boot back into the stock ROM, but it stayed on that screen, a bootloop. I then proceeded to hold the power button to turn it off. I booted it again, and it bootlooped again. So I went back to CWM and wiped the data/factory reset, wiped the cache partition, and went into advanced and wiped the dalvik cache. Then I rebooted it once more, and it bootlooped once again. So now I've turned it off, and am attempting to find a solution to fix this. As a last resort, I can always unroot it and wipe the data again. But I would prefer to not to have to re-unlock and re-flash the phone, unless there is no other option. During this entire period, the phone was connected by USB cable to the computer, up until I wiped the data and caches, where I unplugged it, and allowed it to boot."
*****So overall, after installing CWM, the phone was put into a bootloop. factory reset was done, as well as wiped cache partition and dalvik cache*****
is there a way to get the device rooted, without using the traditional unroot method? I feel as if the error (if any) was simple, therefore there should be a simple solution. Thanks!

[Q] Unable to mount /cache - Stuck at CM boot Screen

Specifics first -
Device: VS980 (VZW LG G2)
Recovery: TWRP 2.6.3.2
ROM: CM 10.2 12/6 Nightly
I had a random reboot while trying to answer a phone call today. Its happened before. So I figured I would reflash the nightly to see if it would correct itself. I entered recovery from the power button menu. I tried to flash the nightly from the CyanDelta folder (tinkering around earlier, downloaded it, detected rom, and deleted from cmupdater file). For some reason I decided to wipe cache and dalvik after installing. The phone never rebooted after that. I proceeded to try and power up only to be faced with a constant CM boot screen (I knew something was wrong when I notice how long it took to get to the CM screen). I was able to get back into recovery to try and flash the 11/30 nightly, which I hadn't touched. After flashing, I noticed the "Unable to mount /cache". So instead of trying to fight with my phone to get back into recovery, I flashed a backup. It also displayed the "Unable to mount /cache". My phone was in recovery where I performed a factory reset. ADB was recognizing it and receiving commands. I unplugged it to see if I could get into download mode. Now I cant get it back into recovery. When I do "adb devices" it shows up as "unauthorized". Where do I go from here? I have very limited adb experience. 

[Q] Nexus 4 Stuck on Reboot after Android 5.1 Update Error

Hello All,
Hope you guys are doing well. I'll write in jot notes so I don't end up with an essay.
Bought Nexus 4 16GB in February 2013 from Google Store and have been running stock software since. Never had issues.
Updated from latest Kit Kat OS to Android 5.0.1 OTA yesterday and it installed fine.
Then tried updating to Android 5.1 (also through OTA) right after and encountered the "Error" message with the Android logo on its back during install. Phone is now unable to move past the swirling, coloured balls animation upon rebooting (referred to as a bootloop?).
Based on some websites' recommendations, I went into the recovery mode (hold Power+Volume Down and select from list) and wiped the cache partition (hold Power+Volume Up and select from list), which took a second. Wiped cache several times.
Tried rebooting the system after but I still get stuck on the swirling balls animation.
I'd be fine with using 5.0.1 or even going back to the latest Kit Kat as long as I can actually get my phone working again and not have to factory reset everything through the recovery mode (which, at this point, seems like my only option).
Thanks.

Check my thread, I had the same problem. 5.0.1 was fine but sensors went kaput, yes all of them. Flashed factory image 5.1, endless boot screen. After a day or two of flashing 4.4.4 (sensors were back working okay, wow big surprise), tried flashing 5.1.1 pure stock, same.
I'm back to 4.4.4 after restoring apps and data. Not sure I want to use 5.0.1 due to hte memory leak and other bugs that should be fixed with 5.1. But I'm certain that the factory image of 5.1.x won't boot on the N4.
For your problem, download the factory image, then edit flash-all.bat/sh and remove the -w from the last flash command (-w rewrites /userdata partition). Whether you use 5.0.1 or 4.4.4 is up to you.

PermissionToPanic said:
Hello All,
Hope you guys are doing well. I'll write in jot notes so I don't end up with an essay.
Bought Nexus 4 16GB in February 2013 from Google Store and have been running stock software since. Never had issues.
Updated from latest Kit Kat OS to Android 5.0.1 OTA yesterday and it installed fine.
Then tried updating to Android 5.1 (also through OTA) right after and encountered the "Error" message with the Android logo on its back during install. Phone is now unable to move past the swirling, coloured balls animation upon rebooting (referred to as a bootloop?).
Based on some websites' recommendations, I went into the recovery mode (hold Power+Volume Down and select from list) and wiped the cache partition (hold Power+Volume Up and select from list), which took a second. Wiped cache several times.
Tried rebooting the system after but I still get stuck on the swirling balls animation.
I'd be fine with using 5.0.1 or even going back to the latest Kit Kat as long as I can actually get my phone working again and not have to factory reset everything through the recovery mode (which, at this point, seems like my only option).
Thanks.
Click to expand...
Click to collapse
Try doing this
Let's be clear about how to wipe cache, you can't do it in the bootloader.
Power off
Hold Power and VOL DOWN => bootloader
VOL to select Recovery
Power to enter Recovery.
In stock Recovery "fallen Android" icon, hold POWER and VOL UP => Recovery menu
Now use vol and power buttons to select Wipe cache partition.
My final attempt after doing factory reset/wipe data in stock recovery, using the factory image flash-all.bat and NOT removing the -w switch (so /userdata/ is overwritten as well), the N4 didn't boot after waiting > 30 minutes.
Hope that helps

PermissionToPanic said:
Hello All,
Hope you guys are doing well. I'll write in jot notes so I don't end up with an essay.
Bought Nexus 4 16GB in February 2013 from Google Store and have been running stock software since. Never had issues.
Updated from latest Kit Kat OS to Android 5.0.1 OTA yesterday and it installed fine.
Then tried updating to Android 5.1 (also through OTA) right after and encountered the "Error" message with the Android logo on its back during install. Phone is now unable to move past the swirling, coloured balls animation upon rebooting (referred to as a bootloop?).
Based on some websites' recommendations, I went into the recovery mode (hold Power+Volume Down and select from list) and wiped the cache partition (hold Power+Volume Up and select from list), which took a second. Wiped cache several times.
Tried rebooting the system after but I still get stuck on the swirling balls animation.
I'd be fine with using 5.0.1 or even going back to the latest Kit Kat as long as I can actually get my phone working again and not have to factory reset everything through the recovery mode (which, at this point, seems like my only option).
Thanks.
Click to expand...
Click to collapse
I don't think that the factory reset will solve the problem. Have you tried waiting for 10-15 minutes for the phone to boot up? After OTA's and clearing cache the phone usually takes a while to boot up. If that doesn't work, factory reset using a custom recovery (this will delete your /data folder but not /data/media so your internal storage won't be wiped)

Blacksmith5 said:
.. Let's be clear about how to wipe cache, you can't do it in the bootloader.
Power off
Hold Power and VOL DOWN => bootloader
VOL to select Recovery
Power to enter Recovery.
In stock Recovery "fallen Android" icon, hold POWER and VOL UP => Recovery menu
Now use vol and power buttons to select Wipe cache partition.
My final attempt after doing factory reset/wipe data in stock recovery, using the factory image flash-all.bat and NOT removing the -w switch (so /userdata/ is overwritten as well), the N4 didn't boot after waiting > 30 minutes.
Click to expand...
Click to collapse
My, that text looks familiar....

lost my usb storage during twrp flash

I have no USB storage when in TWRP, hence i can't wipe/flash/restore....here is how i got where I am!
Started with my bone stock OPT 64GB on Oxygen 2.1.1.
in developer options i enabled boot loader unlock
unlocked my boot loader [fastboot oem unlock]
restarted into tarp and installed SuperSU
wiped and factory reset, rebooted and setup and all is well....except...
I decided to factory reset again about 20 minutes later and all wipes failed. So i can not factory reset.
downloaded the factory signed zip to my usbstorage and rebooted into tarp, but there is no usb...no mounts. I though well mount it, but sorry, nothing to mount...
So it appears I have lot my mount points.
I was really hoping that OnePlus had posted a big archive of there OS with an install.bat file, but i can't find it.
Anyone know where its hiding>??
(i will edit this as i get more info together)
You guy and gals all rock.

unable to mount anything at /data
so i can't wipe Dalvik or Cache or Data

Failed encryption, the phone doesn't boot up anymore

Hello. This morning my phone was off (2014813, 2 GB RAM, 16 GB storage), and I turned it on. When it booted up, it greeted me with a text, saying something like "the encryption was unsuccesful, so all your data is now inaccessible, you have to reset the device". now the problem is that I've NEVER wanted to do a full device encryption, and now the recovery was unable to mount the partitions, and even though I can access fastboot, I can't flash any image with MiFlash, beacuse it says "failed to write partition". If I power on the device now, it gets to the boot animation, and it never goes through that, it constantly shows the boot animation.

I'm able to boot a recovery from fastboot, but the recovery can't mount /data and /cache, but it can mount /system. So I can't format /data and /cache now. My phone is currently unusable because of this

I'm having this exact same problem. Where you able to fix it? I have tried countless method but nothing seems to be working
I'm afraid that the internal storage might have died.

gabika1941 said:
Hello. This morning my phone was off (2014813, 2 GB RAM, 16 GB storage), and I turned it on. When it booted up, it greeted me with a text, saying something like "the encryption was unsuccesful, so all your data is now inaccessible, you have to reset the device". now the problem is that I've NEVER wanted to do a full device encryption, and now the recovery was unable to mount the partitions, and even though I can access fastboot, I can't flash any image with MiFlash, beacuse it says "failed to write partition". If I power on the device now, it gets to the boot animation, and it never goes through that, it constantly shows the boot animation.
Click to expand...
Click to collapse
Did you flashed custom ROM too many times?
This may be the cause of Storage failure..
Around How much time did you flashed your device..
Any rough estimate..?