[HELP] NEXUS 4 won't start after clearing cache - Nexus 4 Q&A, Help & Troubleshooting

Hello all,
So ive been running Paranoid for a while. Today i went into recovery and wiped all the data....cleared dalvik and regular cache...
Wiped everything and clicked factory settings also.
Now when i try to reboot...It says you dont have supersu, do you want to install.....If i click YES it stays on google logo forever....If i click NO, same it stays there....
Am i doing anything wrong....I even tried to flash the ROM again...but my SDcard is empty now

What possessed you to wipe everything?
You need to fastboot flash the factory images

duddukuruprasanth said:
Hello all,
So ive been running Paranoid for a while. Today i went into recovery and wiped all the data....cleared dalvik and regular cache...
Wiped everything and clicked factory settings also.
Now when i try to reboot...It says you dont have supersu, do you want to install.....If i click YES it stays on google logo forever....If i click NO, same it stays there....
Am i doing anything wrong....I even tried to flash the ROM again...but my SDcard is empty now
Click to expand...
Click to collapse
Use ADB to push the ROM to your phones SD card, and reflash it. Theres lots of tutorials here on setting up, and using ADB.

Hey thanks ScumDroid....I used sideload option in NEXUS 4 tool kit and pushed the paranoid rom into card again and flashed it.

Related

Flashing Rom always ends in boot loop?

I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm
could that be the problem? that my cwm is just outdated already?
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.
Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!

[Q] Stuck at nexus logo, and more.

After i rooted/unlocked my phone I booted it up and it got stuck on the nexus splash screen. I did find a solution to the problem which was to put it back to factory settings. alright, great, problem solved, but when i go to do the reset i come across errors as seen in the picture. Anyone know how to fix?
I had that issue when downloading the file through the toolkit. I went and manually got the images from google, placed them in the correct folder within the kit and flashed successfully.
Sent from my Nexus 4 using xda premium
dont use a toolkit. do it manually like what ^^ said
I recommend flash SuperSu zip file via CWM Recovery.
It's totally easy and safe.
I had this issue. Factory reset/clear caches should fix it.
Sent from my Nexus 4 using Tapatalk 2
sporez said:
I had this issue. Factory reset/clear caches should fix it.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
factory resetting clears your cache, as well as dalvik cache.
Not sure what I did wrong.
Backed up phone
unlocked phone
downloaded CWM
put SU on phone
went into put loader and flashed ( I think ) CWM
then when I go into recover mode the phone gets stuck on google logo.
Cleared cache etc. but nada.
Downloading factory image now....on a very slow connection and will take 3 hours. Any way around this? What are my options.
I'm totally stuck here too. I have the exact same as the OP.
I've manually placed the stock image in the folder structure. It's starts to do stuff, reboots and then the toolkit says Waiting for Device (forever).
Nothing happens after this.
This all occurred while I was installing my Google Apps. I stupidly installed Chainfire3D, and installed the drivers. It restarted and this never ending cycle happened. I only read that they weren't compatible with ICS or Jellybean afterwards
Any help is greatly appreciated. :crying:
Hi guys
I am stuck on the google logo, I have cleared dalvik etc unmounted / mounted system but cannot get to data partion
I have wiped the SD card now I cannot connect to copy a rom back to the device... it just hangs on Google logo.
I can access recovery but still cannot access data partition to add rom.
any ideas?
thank you
ace9094 said:
Hi guys
I am stuck on the google logo, I have cleared dalvik etc unmounted / mounted system but cannot get to data partion
I have wiped the SD card now I cannot connect to copy a rom back to the device... it just hangs on Google logo.
I can access recovery but still cannot access data partition to add rom.
any ideas?
thank you
Click to expand...
Click to collapse
flash stock recovery.IMG clear caches and boot
Burroveo said:
I'm totally stuck here too. I have the exact same as the OP.
I've manually placed the stock image in the folder structure. It's starts to do stuff, reboots and then the toolkit says Waiting for Device (forever).
Nothing happens after this.
This all occurred while I was installing my Google Apps. I stupidly installed Chainfire3D, and installed the drivers. It restarted and this never ending cycle happened. I only read that they weren't compatible with ICS or Jellybean afterwards
Any help is greatly appreciated. :crying:
Click to expand...
Click to collapse
There is a file contain in the factory image download called flash-all.bat Double click on this file while your phone is connected in bootloader mode and it should automatically flash the stock image for you
Sent from my Nexus 4 using Tapatalk 2
i also have this problem.
I tried to flash stock factory image with the .bat file but no success. I am stuck at the nexus bootlogo...
Can still enter recovery and fastboot.
Edit:
solved my problem. I went to CWM Recovery, and checked in "mounts and storage" that none of the partitions were mounted. Cache was mounted in my case. I unmounted Cache and rebooted.
Phone boots fine now!

[Q] phone won't turn on and start()

hello,
i have posted the question on this forum but i didn't received any solution that works
please see here
http://forum.xda-developers.com/showthread.php?p=40700200#post40700200
check page 2 too
please help me!!! i'm desperate !!!:crying:
i wanted to install a new version of slim mako update, but first i wanted to wipe ALL my nexus 4
so i entered to CWM--> mount and storage--> and " format system, format data, format cache, format sdcard".
basically i deleted all my phone files, and now when i turning it on i see only the google logo and no any change.
please someone help me
thanks for the helpers
You have wiped your ROM, that's why it won't boot. You need to flash a new ROM now. Can you get into the bootloader/recovery?
Sent from my Nexus 4
steviewevie said:
You have wiped your ROM, that's why it won't boot. You need to flash a new ROM now. Can you get into the bootloader/recovery?
Sent from my Nexus 4
Click to expand...
Click to collapse
i don't have recovery. bootloader i have
i tried from sideload to push recovery and it works, i pushed roms(google's and other) but the phone turns on showing the google logo
show the rom logo and then for a hour nothing happens.
SherDroidx said:
i don't have recovery. bootloader i have
i tried from sideload to push recovery and it works, i pushed roms(google's and other) but the phone turns on showing the google logo
show the rom logo and then for a hour nothing happens.
Click to expand...
Click to collapse
After you flash the mako image you need to boot into recovery and clear cache/factory reset. Then it will boot past the X.
Sent from my Nexus 4 using Tapatalk 4 Beta
SherDroidx said:
i don't have recovery. bootloader i have
i tried from sideload to push recovery and it works, i pushed roms(google's and other) but the phone turns on showing the google logo
show the rom logo and then for a hour nothing happens.
Click to expand...
Click to collapse
Do a data/factory reset in recovery and it should reboot.
gee2012 said:
Do a data/factory reset in recovery and it should reboot.
Click to expand...
Click to collapse
sounds that easy but it doesn't work to wipe again
i tried adb, sideload and only the google and the rom logo blink and nothing more

4.3 Update: Stuck on Nexus Boot screen

I am stock everything and bootloader unlocked, I flash the 4.3 update via adb, but now it doesn't boot into the os, it get's stuck on the 'Nexus' boot screen.
Can someone assist me, thanks! I don't want to wipe data or reflash the rom.
Same problem here. Searching the forum for a solution... :/
Deeco7 said:
I am stock everything and bootloader unlocked, I flash the 4.3 update via adb, but now it doesn't boot into the os, it get's stuck on the 'Nexus' boot screen.
Can someone assist me, thanks! I don't want to wipe data or reflash the rom.
Click to expand...
Click to collapse
Go into custom recovery and factory reset
From my BLACKED OUT N4
spaceman860 said:
Go into custom recovery and factory reset
From my BLACKED OUT N4
Click to expand...
Click to collapse
I don't think you read my first post. I don't want to wipe data and have no custom recovery installed.
Deeco7 said:
I don't think you read my first post. I don't want to wipe data and have no custom recovery installed.
Click to expand...
Click to collapse
Did you try wiping cache
From my BLACKED OUT N4
I actually have the same problem. I had root, but I wasn't using a custom recovery. The OTA appeared as available in the notifications so I chose to install it. I set it aside and it appeared to install, but when it went to boot up, it got stuck on the X animation. I left it there while I tried to research the issue, but after 20 minutes of looking at the X I tried doing a factory reset with the stock recovery. It said it succeeded, so I rebooted. I've now been looking at the X animation for 7 minutes.
naxir said:
I actually have the same problem. I had root, but I wasn't using a custom recovery. The OTA appeared as available in the notifications so I chose to install it. I set it aside and it appeared to install, but when it went to boot up, it got stuck on the X animation. I left it there while I tried to research the issue, but after 20 minutes of looking at the X I tried doing a factory reset with the stock recovery. It said it succeeded, so I rebooted. I've now been looking at the X animation for 7 minutes.
Click to expand...
Click to collapse
edit: ^^^ same here. Root, no custom recovery.
After the update mine was stuck on the loading screen for a while, maybe a half hour. Gave up on that, did a factory reset from the recovery menus, but it still won't start up.
Any suggestions?
spaceman860 said:
Did you try wiping cache
From my BLACKED OUT N4
Click to expand...
Click to collapse
Yes, same problem.
Try reflashing, maybe something went wrong during the flash.
Sent from my Nexus 4 using Tapatalk 4 Beta
You use the stock recovery to clear cache, format I think is what recovery says, if that doesn't work then you have to do a factory reset weather you want to or not. This worked for me.
This is from efrant's guide to flashing in general section:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this.
andyabc said:
Try reflashing, maybe something went wrong during the flash.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried reflashing, still no go.
kzoodroid said:
You use the stock recovery to clear cache, format I think is what recovery says, if that doesn't work then you have to do a factory reset weather you want to or not. This worked for me.
This is from efrant's guide to flashing in general section:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this.
Click to expand...
Click to collapse
Looks like a factory reset is the only viable option. What is the best way to back everything up, if I cannot boot into OS?
Folks,
After trying a lot of option, I did a full restore flashing the entire 4.3 new image.
Worked, but lost everything on the phone.
kzoodroid said:
You use the stock recovery to clear cache, format I think is what recovery says, if that doesn't work then you have to do a factory reset weather you want to or not. This worked for me.
This is from efrant's guide to flashing in general section:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this.
Click to expand...
Click to collapse
Deeco7 said:
Tried reflashing, still no go.
Looks like a factory reset is the only viable option. What is the best way to back everything up, if I cannot boot into OS?
Click to expand...
Click to collapse
You can backup data using adb, its a simple command to copy the internal storage but I'm not sure what the exact command is as I never had to use it.
I flashed 4.3 following efrant's guide, no dice. I tried erasing boot/recovery and formatting cache/system/userdata and then doing so again, no dice. I did a factory reset and then flashed using flash-all.sh, no dice. It hangs on X animation. I've been letting it go for 5+ minutes each time, should I be waiting longer? Is there something else I can try?
kzoodroid said:
You can backup data using adb, its a simple command to copy the internal storage but I'm not sure what the exact command is as I never had to use it.
Click to expand...
Click to collapse
Code:
adb backup-f boot boot.img
adb backup-f system system.img
adb backup-f data.img date
Would this be the commands?
kzoodroid said:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
Click to expand...
Click to collapse
My 'phone couldn't get past the X so I followed the above. Wiping the cache didn't work so I chose wipe data/factory reset, answered yes to delete all user data and the screen showed "Wiping data ... Formatting /data ... Data wipe complete". The menu then returns with reboot system now highlighted. What's supposed to happen next?
If I choose reboot system now, the 'phone just reboots to the bootloader. If I choose wipe data/factory reset, the data is wiped again and the menu returns again, same as before. If I do nothing, nothing happens, at least according to the screen. What am I missing?
I was able to use flash-all.sh in 4.2.2 and it booted fine. I tried the ota again and same issue. Some apps autoinstalled when I installed 4.2.2, so I guess I can re-flash 4.2.2, make sure no apps download, then try the OTA again, but I'm not sure what else I can try to get 4.3 to install.
Yeah I also had the same problem. Tried to apply OTA from rooted stock. I flashed 4.2.2 via fastboot without wiping user data and got it to start in 4.2.2 again. Backed up all the important files and app data with Titanium, factory reset and then flashed 4.3. Rooted and then restored all the app data. Had a small issue with the r/w permission on some of the folders that affected the Gallery app not being able to work properly but did a fix and it all works fine now.
Sent from my Nexus 4 using Tapatalk 4 Beta
Deeco7 said:
Code:
adb backup-f boot boot.img
adb backup-f system system.img
adb backup-f data.img date
Would this be the commands?
Click to expand...
Click to collapse
No that's not it. I saw a tutorial somewhere on how to backup the Nexus 4 using adb but I can't find it. Someone in here knows how to do it and/or there is already a thread on it.
it would be something like --- adb pull all storage/emulated/0 --- to get all your data off the sdcard but I'm not sure of the syntax I used plus you need to designate where to put the data you just pulled. I only looked at the how to once and very briefly as I didn't need to use it. I'm not sure how you backup user data but you would need to pull the image off the device.
I have most of my data backed up to either Google or in my Box account using Helium backup so I don't care about losing any doing a factory restore so I have no need to know how to do an adb backup.
---------- Post added at 09:24 PM ---------- Previous post was at 09:17 PM ----------
This isn't the guide I saw before but I think it will work. I cut out the relevant section from the article.
http://www.dotkam.com/2013/01/16/backup-and-reset-nexus-4-cracked-and-locked-screen/
One thing I knew I could do for sure is to backup the “sdcard”. I knew this because of two things: I have “USB Debugging” on, which means I can use adb, and “sdcard” is not owned by root, which means it can be “pulled”/”read” by adb. Hence the first step is clear:
./adb pull /sdcard/ /destination
At this point all the pictures / videos / music, etc.. are backed up. Now I need to backup my SMS, contacts, etc.. Information that lives in Android “databases”. For example contacts usually live here “/data/data/com.android.providers.contacts/databases”. Which can’t be simply “pulled” as pitures, since they are protected, and hence cannot be read by adb directly.
---------- Post added at 09:34 PM ---------- Previous post was at 09:24 PM ----------
I found this thread in the galaxy nexus forum and maybe it will work, it was using syntax similar to what you posted.
http://forum.xda-developers.com/showthread.php?t=1420351
So I have tried many things to flash 4.3, but none have worked. Flashing 4.2.2 works and it's how I recover from getting stuck on the nexus boot screen which happens whenever I flash 4.3.
I have tried:
Simple OTA. Performed when I had root and also from fresh 4.2.2 install.
Flash using fastboot and all .img files separately, wiping the cache afterwards.
Flash using flash-all.sh script included with the factory image.
I have tried doing the above wiping cache before/after and doing a factory reset before/after. The MD5 checksum of the .tgz is correct, so the file downloaded correctly. However, all roads lead to being stuck on the "X" animation during boot up. I always allow 5+ minutes for it to progress beyond, but it hasn't.

Cyanogen-11 stuck while booting (yes, I googled)

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.

Categories

Resources