Cyanogen-11 stuck while booting (yes, I googled) - Nexus 4 Q&A, Help & Troubleshooting

Hi, everybody!
I am stuck with the problem, I cannot solve, and cannot google.
I saw a lot of similar, but none of the directions helped me to fix my phone.
I've got my Nexus 4 which was a great phone until I updated it to 4.3, some of the screen portions became senseless on some applications (starting from SMS, to some game apps).
I was suggested to downgrade or change ROM, which I am trying to figure out right now.
I've rooted my phone with SuperSU-v1.85 and installed Clockwork-6.0.4.3.
Once I've done it, I was trying to load an images of cm-11 and gapps-4.4 with
adb push
it finished all operations in cmd, however, I got
E: Can't mount /sdcard
Thus, I've tried to install all zips from sideload and my cmd.
I didn't touch kernel.
Once I've done this, I tried to reboot, but Cyanogen stuck, running circles.
I've tried to do factory reset, clear cache and dalvik, however none of those worked.
I also have been doing this with a more stable release (cm-10.2.0), but I got same thing.

bagelisnotaname said:
Hi, everybody!
I am stuck with the problem, I cannot solve, and cannot google.
I saw a lot of similar, but none of the directions helped me to fix my phone.
I've got my Nexus 4 which was a great phone until I updated it to 4.3, some of the screen portions became senseless on some applications (starting from SMS, to some game apps).
I was suggested to downgrade or change ROM, which I am trying to figure out right now.
I've rooted my phone with SuperSU-v1.85 and installed Clockwork-6.0.4.3.
Once I've done it, I was trying to load an images of cm-11 and gapps-4.4 with
adb push
it finished all operations in cmd, however, I got
E: Can't mount /sdcard
Thus, I've tried to install all zips from sideload and my cmd.
I didn't touch kernel.
Once I've done this, I tried to reboot, but Cyanogen stuck, running circles.
I've tried to do factory reset, clear cache and dalvik, however none of those worked.
I also have been doing this with a more stable release (cm-10.2.0), but I got same thing.
Click to expand...
Click to collapse
Try another rom besides CM.

scream4cheese said:
Try another rom besides CM.
Click to expand...
Click to collapse
Tried MIUI.
Same thing.
Did I brick it?

scream4cheese said:
Try another rom besides CM.
Click to expand...
Click to collapse
I've tried stock ROM 4.2.2, flashed it with flashall.bat, stupidly, it works.
However, what is the problem with the custom ROMs?
Do I do something wrong?
ps. screen is still unresponsive in some areas.

Maybe you'll have better luck with TWRP 2.6.3.3.

audit13 said:
Maybe you'll have better luck with TWRP 2.6.3.3.
Click to expand...
Click to collapse
Just tried it.
Didn't work out with MIUI.

Just put the files directly onto the phone either by downloading them on it or transferring normally over USB.
Reboot into recovery
From here you got options but to make it simple do a full wipe. A full wipe is deleting everything but your internal storage. That includes / system /data and everything else your recovery shows but the internal storage. Then just flash the ROM zip and gapps zips from your internal storage after the wipe and reboot
If you delete your internal storage you will wipe out the zips you just put there. Along with your media. Pictures music and whatever else is on there
Wiping your data will wipe your apps. So if you want, back them up with something like titanium backup prior. They will still be there after you flash the custom rom as long as you don't wipe your internal storage.

Related

Installing ROMs

I've tried installing roms 4 times, and each time the same thing happens:
Boot into Clockwork
Wipe everything
install zip from sd card
choose the one i want
choose yes
then the only things it does :finding update package and opening update package, and then, BOOM, back to recovery, lasted only 1 second.
then i reboot system and nothing has changed. i am really confused and quite frustrated, can anyone help or give me some tips?
keen28 said:
I've tried installing roms 4 times, and each time the same thing happens:
Boot into Clockwork
Wipe everything
install zip from sd card
choose the one i want
choose yes
then the only things it does :finding update package and opening update package, and then, BOOM, back to recovery, lasted only 1 second.
then i reboot system and nothing has changed. i am really confused and quite frustrated, can anyone help or give me some tips?
Click to expand...
Click to collapse
Are you sure you're actually rooted? When you say "wipe everything" does that include cache/dalvik cache? If you wiped everything then rebooting the system shouldn't give the result "nothing has changed". Have you checked the MD5 of the ROM zip against the MD5 that it should "be"? If you can, boot into the phone and install terminal emulator and type "su" and tell me what it says...
i'm assuming you followed the steps in this tutorial to get rooted? did everything go as it was supposed to?
also, make sure when booting into recovery that you are not plugged in via usb.
zervic said:
Are you sure you're actually rooted? When you say "wipe everything" does that include cache/dalvik cache? If you wiped everything then rebooting the system shouldn't give the result "nothing has changed". Have you checked the MD5 of the ROM zip against the MD5 that it should "be"? If you can, boot into the phone and install terminal emulator and type "su" and tell me what it says...
Click to expand...
Click to collapse
Hah, yes, it is rooted. i put wipe everything to shorten the steps. I just installed terminal emulator, but when i typed "su" it just forms a new line with a #
am i doing something wrong now?
also, i realized that when i downloaded cm7, my computer (mac) unzipped the file, and then i rezipped before loading to sd card. if that doesn't make a difference then disregard this
keen28 said:
Hah, yes, it is rooted. i put wipe everything to shorten the steps. I just installed terminal emulator, but when i typed "su" it just forms a new line with a #
am i doing something wrong now?
also, i realized that when i downloaded cm7, my computer (mac) unzipped the file, and then i rezipped before loading to sd card. if that doesn't make a difference then disregard this
Click to expand...
Click to collapse
Okay...well try downloading it straight to your SD card from your phone browser. Also, see post above yours regarding having your phone plugged into USB when you boot into clockwork. If you've been doing this with your phone plugged in, that is your problem right there.
zervic said:
Okay...well try downloading it straight to your SD card from your phone browser. Also, see post above yours regarding having your phone plugged into USB when you boot into clockwork. If you've been doing this with your phone plugged in, that is your problem right there.
Click to expand...
Click to collapse
Ok, so i am not plugged in when trying to do this, so thats not the problem. i downloaded CM7 to my sd card, and i followed the instructions to install it, and now it is stuck on Installing update... but its only been here for about a couple mins, so im not sure whether its frozen or it just takes a while to install.
Ok, so it finially loaded, and it said it was complete. but now, i reboot and it goes from the HTC screen to the android intro thing, where the blue android is riding on a skateboard, but it goes about 3/4 across the screen then freezes, and a few seconds later restarts, but keeps doing the same thing over and over again. what should i do now?
Sounds like you are trying to flash a CM7 nightly without formatting system. In addition to wiping data, cache partition, Dalvik, you should go into Partitions menu from Clockwork Recovery and choose format system.
That was a wrinkle that tripped up many including myself when trying out the CM7 nightlies. After you have CM7 running, you don't have to format system again. ie. you can flash a more recent nightly just by clearing both caches.
stone_ship said:
Sounds like you are trying to flash a CM7 nightly without formatting system. In addition to wiping data, cache partition, Dalvik, you should go into Partitions menu from Clockwork Recovery and choose format system.
That was a wrinkle that tripped up many including myself when trying out the CM7 nightlies. After you have CM7 running, you don't have to format system again. ie. you can flash a more recent nightly just by clearing both caches.
Click to expand...
Click to collapse
hah, yes, that was exactly the problem. i figured it out tho. thanks, but now with cm7 i don't have Market, and i can't sync my google account to my phone. any suggestions?
Yea download the gapps package for 2.3 and flash it just like you ddid the rom minus wiping data and caches. That's if you're on CM7. Check the development section
Sent from my Liberty using XDA App

[Q] Problems flashing roms

On my nexus 7 8gb model I tried flashing mmuzzyrom for grouper. No success. So I thought it was twrp that was causing the problem, so I flashed cwm and tried that. Also not successful. So then I thought it might be the roms, so I tried to flash cyanogenmod nightly and it didn't work. I noticed when I try to flash a rom it doesn't mount /system or anything but when I flash gapps it mounts /system and I think it actually works. Any ideas? Thanks
Did you run factory reset in recovery before flashing the rom?
Sent from my Galaxy Nexus
Pirateghost said:
Did you run factory reset in recovery before flashing the rom?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Won't that delete the rom? And my nandroid?
skiman10 said:
Won't that delete the rom? And my nandroid?
Click to expand...
Click to collapse
no. in fact you have to run factory reset in your custom recovery (CWM or TWRP) before flashing any rom....otherwise you get EXACTLY what is happening to you now. This is a well documented thing when flashing roms.
running FACTORY RESET in a custom recovery will wipe everything but /data/media where your 'sdcard' resides
Pirateghost said:
no. in fact you have to run factory reset in your custom recovery (CWM or TWRP) before flashing any rom....otherwise you get EXACTLY what is happening to you now. This is a well documented thing when flashing roms.
running FACTORY RESET in a custom recovery will wipe everything but /data/media where your 'sdcard' resides
Click to expand...
Click to collapse
Ah I get it now, actually I was trying to perform a dirty flash but I guess that isn't gonna work
Well thanks for your help
if you want your new rom to be performing well, its best NOT to do a dirty flash. some roms you can dirty flash between, but most require a factory reset.
you can almost ALWAYS do a dirty flash when upgrading from one version of the same custom rom to the next, but completely different custom roms will require a reset
Pirateghost said:
if you want your new rom to be performing well, its best NOT to do a dirty flash. some roms you can dirty flash between, but most require a factory reset.
you can almost ALWAYS do a dirty flash when upgrading from one version of the same custom rom to the next, but completely different custom roms will require a reset
Click to expand...
Click to collapse
Ok thanks for that info ill see what happens.
I did it!
Thanks so much! I'm a frickin idiot for thinking I could dirty flash.
skiman10 said:
Thanks so much! I'm a frickin idiot for thinking I could dirty flash.
Click to expand...
Click to collapse
You can get away with it when the ROM you are coming from is quite closely related to the ROM you are going to. For instance, if you were flashing CM 10.1 nightlies over the course of a few weeks. But in general, it's not really a great idea - it is a terrible idea for unrelated ROMs.
The best practice is probably to use something like TiBu or Carbon, and ONLY back up market apps and their data - never pre-installed system apps (e.g. gapps). For home screens, you can just use a launcher that allows backup/restores of it's home screen configurations.
Even in this case, you can still run into UID issues restoring market apps & data - it appears that the Android boot process assigns UIDs in a serial fashion (without any gap between system apps and market apps), so as soon as it runs through all the .apks it finds in /system/app, it continues with the next (+1) UID available for the .apks found in /data/app. The net result of this is if you install a ROM that has more .apks in /system/app than your prior ROM did, it is likely you will have common-uid collision issues. The custom recovery "fix permissions" can try and fix this up - I'm not sure if they cover all the bases though (multiple user accounts, stuff in /data/app-secure, etc).
good luck

Need help - freezes and restarts

I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?
Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.
jcxmej said:
I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?
Click to expand...
Click to collapse
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.
RikRong said:
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.
Click to expand...
Click to collapse
Like I said on first post Im using TWRP now. Previously I was using safestrap. I removed it and installed TRWP. Anyways thanks.
PantherVT said:
Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.
Click to expand...
Click to collapse
Thanks man. I will upgrade TWRP or reinstall it first. Thanks for that tip. Will post again if it doesnt work.
Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.
jcxmej said:
Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.
Click to expand...
Click to collapse
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)
jco23 said:
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)
Click to expand...
Click to collapse
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.
jcxmej said:
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.
Click to expand...
Click to collapse
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"
jco23 said:
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"
Click to expand...
Click to collapse
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?
jcxmej said:
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?
Click to expand...
Click to collapse
which ROM are you trying to install?
jco23 said:
which ROM are you trying to install?
Click to expand...
Click to collapse
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.
jcxmej said:
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.
Click to expand...
Click to collapse
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.
jco23 said:
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.
Click to expand...
Click to collapse
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.
jcxmej said:
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.
Click to expand...
Click to collapse
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692
jco23 said:
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692
Click to expand...
Click to collapse
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.
jcxmej said:
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.
Click to expand...
Click to collapse
I don't think changing the kernel will do it.... I suspect the issue is with your recoveries - will respond in other thread....

LG G2 ADB unauthorized device (unable to get into system)

Hey guys, I was running 4.3.x for a while with the loki twrp solution and all was well, after many attempts to flash 4.4 I finally decided to ditch twrp and go to CWM, that went without a hitch and brought me into the latest nightly of CM, yet I wanted a fresh install (No accounts, no pictures media etc etc) so I tried to do factory reset from within the OS and it wouldn't let me. so I then went into recovery and tried to format things from there...
Since then I have been unable to get past the spinning CyanogenMod boot screen and though adb sees there is a device, it is telling me it is "unauthorized". Of course since I can't get into the OS the RSA confirmation thing can't come up and I can't select any system preferences. Before I went messing around in recovery formatting things ADB was working flawlessly.
Any ideas on where to go from here?
Thanks guys,
Lokin
HellaBester said:
Hey guys, I was running 4.3.x for a while with the loki twrp solution and all was well, after many attempts to flash 4.4 I finally decided to ditch twrp and go to CWM, that went without a hitch and brought me into the latest nightly of CM, yet I wanted a fresh install (No accounts, no pictures media etc etc) so I tried to do factory reset from within the OS and it wouldn't let me. so I then went into recovery and tried to format things from there...
Since then I have been unable to get past the spinning CyanogenMod boot screen and though adb sees there is a device, it is telling me it is "unauthorized". Of course since I can't get into the OS the RSA confirmation thing can't come up and I can't select any system preferences. Before I went messing around in recovery formatting things ADB was working flawlessly.
Any ideas on where to go from here?
Thanks guys,
Lokin
Click to expand...
Click to collapse
I had an issue with my adb, it was out dated. I updated the sdk system, and it detected the lg g2, this could possibly help you.
osugsxr said:
I had an issue with my adb, it was out dated. I updated the sdk system, and it detected the lg g2, this could possibly help you.
Click to expand...
Click to collapse
Yeah I considered that but no everything is up to date. It seems more like the RSA auth fingerprint is not being recognized. Plus it does recognize the phone, it just tells me it is unauthorized.
Get back into Recovery mode and use ADB from there
votinh said:
Get back into Recovery mode and use ADB from there
Click to expand...
Click to collapse
How do I get into recovery without being able to "adb reboot recovery"?
unomicu how
Bump. Anything guys? Really struggling here....
Can you get in recovery using button combination?
votinh said:
Can you get in recovery using button combination?
Click to expand...
Click to collapse
Nope, doesn't seem like it. Though I can get into download mode no problem.
Alright guys, since it seems like not many people out there know whats going on with me I'll dow what i can to keep an update.
Finally got back into Recovery using this super convenient little trick I did not know existed.
Though now I am unable to mount anything at all from recovery "E:Can't mount /cache.. etc"
HellaBester said:
Alright guys, since it seems like not many people out there know whats going on with me I'll dow what i can to keep an update.
Finally got back into Recovery using this super convenient little trick I did not know existed.
Though now I am unable to mount anything at all from recovery "E:Can't mount /cache.. etc"
Click to expand...
Click to collapse
I've never been able to mount anything using the recovery. Not sure if it because of the LG phone or of my recovery. But I've tried different ones (CWM, TWRP, Philz Touch), none was able to mount my phone from recovery. Your best bet right now is to flash the files from a OTG cable and flash drive. Also when you said you formatted the phone from the recovery, did you format the system partition as well? TWRP has that option so I assume CWM has it as well
super114 said:
I've never been able to mount anything using the recovery. Not sure if it because of the LG phone or of my recovery. But I've tried different ones (CWM, TWRP, Philz Touch), none was able to mount my phone from recovery. Your best bet right now is to flash the files from a OTG cable and flash drive. Also when you said you formatted the phone from the recovery, did you format the system partition as well? TWRP has that option so I assume CWM has it as well
Click to expand...
Click to collapse
Heyoo, just in the last hour or so I've got it all fixed!
I did a full system, data and cache format om CWM after that there was no OS or amnything of the sort, then I was able to mount the SD and adb push cm11 + gapps-kk to the sdcard, I flashed those two zips restarted, failed, then i did a system reset (resets everything but the OS) and I popped out in CM11 with a perfectly fresh install. got all that setup and am golden now ::
Congratz
Check the .android folder
My problem started when I tried to connect another phone which happened to be the same type of phone as the previous one. Not sure if that's actually related, but my working hypothesis is that ADB gets confused in this scenario. I tried everything listed here and in many other places, and nothing seemed to work. Finally, I did this:
1. Rename .android folder in your user directory (~/username/.android on Mac OSX) to .android_bak (for safe keeping).
2. Restart the adb daemon: "adb kill-server" followed by "adb start-server"
After that, I got the authentication confirmation on the phone (don't forget that part, of course) and all was well.
These steps merely recreate the .android folder and get rid of any authentication credentials you already have. Note of course that this will impact all other phones you may be connecting.

[Q&A] [ROM][LOLLIPOP][5.0][LRX21T][UNTOUCHED PURE STOCK][Nexus⁴]

Q&A for [ROM][LOLLIPOP][5.0][LRX21T][UNTOUCHED PURE STOCK][Nexus⁴]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][LOLLIPOP][5.0][LRX21T][UNTOUCHED PURE STOCK][Nexus⁴]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
So i kinda figured it out.
well, I sort of did something(i think) and its now working fine... I went to twrp.. did a factory reset. Then went for advance wipe and wiped system cache and dalvik. Then followed the same procedure. Bootloader-->radio-->Rom-->Kernel. It worked just fine. The first boot took some 15 minutes.
does the internal storage work for you? it works only on twrp for me :/
i can't see anything in file explorer and canìt restore from twrp :/ that's a big problem guys.
If you can not see your old nandroid backups
After rooting If you can not see your old nandroid backups
Via file explorers try to enable usb debuging from
dev. opt. if not worked (Recovires or SuperSU issue)
But you can see and restore your old or new backups via recovery (TWRP tested)
New recoveries and superSU may fix this issues.
Want to ask? SuperSU XDA Thread here
Note: SE Linux Mod Changer may help to fix this issue
Recommended Recovery is TWRP 2.8.1.0
​
HunterAtXDA said:
I also got this message
Code:
unmount of /system failed: no such volume
followed by
Code:
unmount of /data failed: no such volume
a few minutes later. The process finished a few minutes later without any more output but I'm booting now after wiping the cache and everything seems fine.
Click to expand...
Click to collapse
I had the this same problem. After installing everything, I let it sit for 20 minutes and it finally showed the Android logo. After that it was stuck on a black screen. I wiped everything and repeated the install procedure again, minus the kernal, and got the same "unmount of /system failed: no such volume" while flashing the rom zip. It booted after a while and everything works except my storage is FUKT. I cant see any of my pictures, music, etc, and the only thing I see via PC is the DCIM folder which is empty. Not cool
mattgrantlackey said:
I had the this same problem. After installing everything, I let it sit for 20 minutes and it finally showed the Android logo. After that it was stuck on a black screen. I wiped everything and repeated the install procedure again, minus the kernal, and got the same "unmount of /system failed: no such volume" while flashing the rom zip. It booted after a while and everything works except my storage is FUKT. I cant see any of my pictures, music, etc, and the only thing I see via PC is the DCIM folder which is empty. Not cool
Click to expand...
Click to collapse
Recommended Recovery is TWRP 2.8.1.0
mattgrantlackey said:
I had the this same problem. After installing everything, I let it sit for 20 minutes and it finally showed the Android logo. After that it was stuck on a black screen. I wiped everything and repeated the install procedure again, minus the kernal, and got the same "unmount of /system failed: no such volume" while flashing the rom zip. It booted after a while and everything works except my storage is FUKT. I cant see any of my pictures, music, etc, and the only thing I see via PC is the DCIM folder which is empty. Not cool
Click to expand...
Click to collapse
Nothing wrong with my storage. I installed the bootloader, radio, and rom on top of my existing 4.4.4 rom by sideloading in CWM. Wiped caches and rebooted to make sure everything was working, then back to CWM to sideload the kernel. I haven't rooted yet.
HunterAtXDA said:
Nothing wrong with my storage. I installed the bootloader, radio, and rom on top of my existing 4.4.4 rom by sideloading in CWM. Wiped caches and rebooted to make sure everything was working, then back to CWM to sideload the kernel. I haven't rooted yet.
Click to expand...
Click to collapse
Did you have the "unmount of /system failed: no such volume" while flashing the rom zip?
mattgrantlackey said:
Did you have the "unmount of /system failed: no such volume" while flashing the rom zip?
Click to expand...
Click to collapse
Yes, and a similar error about /data
JaMeVu said:
Recommended Recovery is TWRP 2.8.1.0
Click to expand...
Click to collapse
Same error after using ADB to flash v2.8.1.0 TWRP, full wipe, and reinstall of everything in the correct procedure. My storage is still not working.
mattgrantlackey said:
Same error after using ADB to flash v2.8.1.0 TWRP, full wipe, and reinstall of everything in the correct procedure. My storage is still not working.
Click to expand...
Click to collapse
try this
enable usb debuging via dev opt.
connect phone to pc
put files to your sd card then reboot to recovery then flash
JaMeVu said:
try this
enable usb debuging via dev opt.
connect phone to pc
put files to your sd card then reboot to recovery then flash
Click to expand...
Click to collapse
I always enable usb debugging, didn't help. And as far as the file transfer, it won't let me. I can only access it while in TWRP. All my files are there, its just android can't see them, and wont show under windows either. Not sure what the issue is there, I've tried everything I know of. I'll just flash CM12 that I was using before. Let me know if you figure out this problem, as I'm curious as to what is causing it (and I'm not the only one having it).
mattgrantlackey said:
Wont let me. I can only access it while in TWRP. All my files are there, its just android can't see them, and wont show under windows either. Not sure what the issue is there, I've tried everything I know of. I'll just flash CM12 that I was using before. Let me know if you figure out this problem, as I'm curious as to what is causing it (and I'm not the only one having it).
Click to expand...
Click to collapse
re plug usb cable take it of then plug
no we do not have this kind of problem here many phones we tested and flashed
JaMeVu said:
re plug usb cable take it of then plug
no we do not have this kind of problem here many phones we tested and flashed
Click to expand...
Click to collapse
Same problems as me:
spupuz said:
does the internal storage work for you? it works only on twrp for me :/
i can't see anything in file explorer and canìt restore from twrp :/ that's a big problem guys.
Click to expand...
Click to collapse
spupuz said:
big big problem can't see the internal storage partition at all.
Click to expand...
Click to collapse
mattgrantlackey said:
Same problems as me:
spupuz said:
big big problem can't see the internal storage partition at all.
Click to expand...
Click to collapse
try re flash everything but not autoroot using..
Click to expand...
Click to collapse
try re flash everything but not autoroot using..[/QUOTE]
All of this was without autoroot. Don't worry about it man, I just installed my old rom. For some reason this ROM doesn't like me and spupuz's phone. Thanks for trying to help me, I appreciate your time. Let me know if someone else has the issue and you figure it out, I'm very curious as to what it might be.
mattgrantlackey said:
try re flash everything but not autoroot using..
Click to expand...
Click to collapse
All of this was without autoroot. Don't worry about it man, I just installed my old rom. For some reason this ROM doesn't like me and spupuz's phone. Thanks for trying to help me, I appreciate your time. Let me know if someone else has the issue and you figure it out, I'm very curious as to what it might be.[/QUOTE]
ok but we test it many phones and 1500+ downloads
may be u are using multirom ? or multirom twrp ?
JaMeVu said:
ok but we test it many phones and 1500+ downloads
may be u are using multirom ? or multirom twrp ?
Click to expand...
Click to collapse
Nope, no multirom or multirom twrp. I have no idea.
After rooting If you can not see your old nandroid backups
Via file explorers try to enable usb debuging from
dev. opt. if not worked (Recovires or SuperSU issue)
But you can see and restore your old or new backups via recovery (TWRP tested)
New recoveries and superSU may fix this issues.
Want to ask? SuperSU XDA Thread here
Note: SE Linux Mod Changer may help to fix this issue
Recommended Recovery is TWRP 2.8.1.0
​
I flashed this ROM this morning, and I initially had the weird can't unmount /system error. I rewiped, using twrp to ensure that /system was wiped too. Install went fine. I have a weird glitch or something on my recent apps list, though. I attached a picture. Anyone know what this is? It doesn't seem to be causing any functional problem, but it looks bad.
Edit: I cleared the cache for google now launcher, and restarted recovery and wiped my cache partition and the error went away.

Categories

Resources