Hey guys. Nexus S won't boot. ClockWork allows me to play around, but says Can't mount Cache. Is there anywhere I can download the files to start fresh? Clockwork won't allow me to install anything because it can't mount cache.
please help out! I'm sorta panicking.
Which Clockwork recovery did you flash? Also next time post in the correct section please
Sent from my Nexus S
I'm such a tool it's amazing. CWM 3.0.0.0 doesn't work Thanks for the support though!
Flash the latest CWM (3.0.2.4) via fastboot, wipe everything (data, cache, dalvik), flash a rooted ROM and reboot.
I have the same issue. Solved it by booting into recovery and manually selecting roms/kernels.
Stock 2.3.4 deodexed with Netarchy 1.3.0.12
Which Nexus S have you got ? i9020 or i9023 ? Did you flash the correct CWM for your phone ?
I've got a i9023 and experienced this issue flashing a CWM for i9020 ... Resolved flashing CWM 3.0.2.5 for i9023 ...
Sent from my Nexus S using XDA App
Related
Alright, I rooted my Nexus S 4G this guide. My phone was running 2.3.5 but I figured that these steps in Terminal wouldn't really change. When I flashed the "recovery-clockwork-3.0.0.5-crespo.img" it didn't install properly (I assume because it was out of date/wrong version) Anyway, I flashed this instead with no problems.
In my euphoria over solving my clockwork problem, I forgot to flash the "su-2.3.6.1-ef-signed.zip" and flashed the current version of MIUI. I am now stuck in a bootloop and I cannot enter recovery by using power+volume. I cannot turn the phone off. I can load the bootloader screen using Terminal while I plug it into my computer, but I don't know what to flash to fix the phone, and start over/end up with a Nexus running MIUI.
i dont know much about macs but you can flash the img files through fastboot.
imgs files are here
thank buglesspete
chewbz said:
i dont know much about macs but you can flash the img files through fastboot.
imgs files are here
thank buglesspete
Click to expand...
Click to collapse
I can handle the mac part if you can show me which files to flash in which order to make my phone work again.
Okay this will take your phone back to stock. Download the grj22 image files. When you open it up it should have like 4 or 5 img files. After that open up cmd and type in the commands buglesspete has in his first post. It should be under "return to stock" or sometime like that.
Sent from my Nexus S 4G using XDA App
XikkeN said:
Alright, I rooted my Nexus S 4G this guide. My phone was running 2.3.5 but I figured that these steps in Terminal wouldn't really change. When I flashed the "recovery-clockwork-3.0.0.5-crespo.img" it didn't install properly (I assume because it was out of date/wrong version) Anyway, I flashed this instead with no problems.
In my euphoria over solving my clockwork problem, I forgot to flash the "su-2.3.6.1-ef-signed.zip" and flashed the current version of MIUI. I am now stuck in a bootloop and I cannot enter recovery by using power+volume. I cannot turn the phone off. I can load the bootloader screen using Terminal while I plug it into my computer, but I don't know what to flash to fix the phone, and start over/end up with a Nexus running MIUI.
Click to expand...
Click to collapse
Just a general hint... if oyu own a Nexus S 4G, Crespo isn't the right codename to look for.. it's crespo4g. Get the cwm recovery from here and flash the 4G version via "fastboot flash recovery <recoveryname>.img": http://forum.xda-developers.com/showthread.php?t=988686
rentaric said:
Just a general hint... if oyu own a Nexus S 4G, Crespo isn't the right codename to look for.. it's crespo4g. Get the cwm recovery from here and flash the 4G version via "fastboot flash recovery <recoveryname>.img": http://forum.xda-developers.com/showthread.php?t=988686
Click to expand...
Click to collapse
I know. I linked to that thread in my first post. What step am I skipping to run MIUI without a bootloop?
XikkeN said:
I know. I linked to that thread in my first post. What step am I skipping to run MIUI without a bootloop?
Click to expand...
Click to collapse
I have no experience with the 4G version of this phone but I can tell your that bootloops are usually caused by failing permissions (fix permissions in cwm rec) or missing wipes before isntalling the actual rom.
So I'd go back to start, flash the 4g recovery, wipe everything (including "mount and storage"'s /boot and then flash MIUI for 4g from here afterwards.
Basically, that MIUI (and most other custom roms) includes superuser.zip aka root. No need to root the devices before, all you need is an unlocked bootloader.
rentaric said:
I have no experience with the 4G version of this phone but I can tell your that bootloops are usually caused by failing permissions (fix permissions in cwm rec) or missing wipes before isntalling the actual rom.
So I'd go back to start, flash the 4g recovery, wipe everything (including "mount and storage"'s /boot and then flash MIUI for 4g from here afterwards.
Basically, that MIUI (and most other custom roms) includes superuser.zip aka root. No need to root the devices before, all you need is an unlocked bootloader.
Click to expand...
Click to collapse
What he said, I always wipe 3x everything just to make sure it is a clean install. And some people will also suggest to let the rom boot up normally before flashing a different kernel.
Sent from my Nexus S 4G using XDA App
chewbz said:
What he said, I always wipe 3x everything just to make sure it is a clean install. And some people will also suggest to let the rom boot up normally before flashing a different kernel.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
wiping 3 times is senseless! and the kernel should be flashed right after the rom install!
oh and wiping the dalvik cache and chache after a rom-update is also senseless! the updater-script do this automatic!
Sent from my Nexus S using XDA Premium App
Borky_16 said:
wiping 3 times is senseless! and the kernel should be flashed right after the rom install!
oh and wiping the dalvik cache and chache after a rom-update is also senseless! the updater-script do this automatic!
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
your assuming that the devs took the time to make sure to include that
Hey everyone,
I'm a new-by to the tech world. I have a "google nexus s" running on ICS 4.0.4, I recently rooted my phone, flashed clockworkmod recovery and tried to install CM9 on my device. After the installation was completed through the clockworkmod, the boot image had showen up and continued to boot throughout the night and never showed up the home screen nor did the custom ROM open itself.
Can anyone give me a lil help as to about what this problem is or the reason why this is happening?
Any help would be really appreciated.
Thanx!
Did you do a full wipe and cache wipe? My suggestion is to do that and reinstall. You could also try a different ROM.
But wouldnt I loose my phone data if I do that?
Sent from my Nexus S using xda premium
i'm having the same problem for every ROM i try on my phone! what to do?
You have a bootloop, this appears because of kernel (boot.img) problems and/or inconsistent cache.
Please wipe/erase cache and Dalvik cache (this can be found in the Advanced menu). Wiping cache partition and Dalvik cache won't erase your personal data.
Make sure the previously flashed CM zip contained a boot.img file. If not, please flash a proper/recommended boot.img (kernel; which is in a zip file) or another rom (with boot.img).
When you flash a new rom over your stock.. first make a backup, then you need to wipe data, cache and dalvik cache..
Sent from my Nexus S using XDA app
Got a backup and mods are running cool! Thanx for the help!
Sent from my Nexus S using xda premium
Hi there all. Trying to get CM9 alpha 12 to run on my HTC Ville EU.
Currently im running trickdroid 4.4 without any problems.
Wanted to try this room as this is CM9. but with only bootloop.
Tested AOKP this works with no bootloop. Flash process i did is as folloing.
Reboot recovery.
Backup
Wipe Data
Wipe Cache
Wipe Dalvik
Flash room (Tested in CMW and TWRP)
Flashed Gapps (and gapps fixed for Hybrid rom)
Flashed Boot.img when using CMW
Bootloop
Rebooted in recovery
Wiped Cache
Dalvik
Rebooted now bootlooped for 15 min
Hope anyone can help me.
Don't think you can flash boot.img in CWM, must flash separately using fastboot. This is a limitation in CWM for now if your phone is S-on. Not sure why AOKP worked for you, should have been same result unless it worked with your old trickdroid kernel, or your phone was fastboot booted into CWM.
Try using Twrp (recovery) it flashes boot.IMG without problems.
Sent from my HTC VLE_U using xda app-developers app
frdd said:
Don't think you can flash boot.img in CWM, must flash separately using fastboot. This is a limitation in CWM for now if your phone is S-on. Not sure why AOKP worked for you, should have been same result unless it worked with your old trickdroid kernel, or your phone was fastboot booted into CWM.
Click to expand...
Click to collapse
frdd is completely right- you must use fastboot for boot.img flashing.
Hi there,
I am currently installing Cyanogenmod 10.1 for my HTC Sensation. I'm stuck in the blue circle loading screen. (image below)
I don't know what should I do.
Help will be highly appriciated.
Sent from my HTC One using xda app-developers app
idomohr25 said:
Hi there,
I am currently installing Cyanogenmod 10.1 for my HTC Sensation. I'm stuck in the blue circle loading screen. (image below)
I don't know what should I do.
Help will be highly appriciated.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
probably you are on S-ON am i right?
if yes use 4ext recovery
enable smatflash from it
flash the rom
done
otherwise flash the boot.img of the rom via fastboot command
My device is S-OFF.
I am trying to flash firmware again, and clear cache and dalvik.
idomohr25 said:
My device is S-OFF.
I am trying to flash firmware again, and clear cache and dalvik.
Click to expand...
Click to collapse
Most of the time there is no need to re-flash firmware. Did you wipe data beforehand? maybe you can try another build (the from an earlier/later date). This might help.
Sometimes a complete wipe is needed...
Hi,
Sometimes when moving from one ROM to another a complete wipe and format of all partitions (except sdcard) is needed in order for it to work. Have you wiped and formatted all your partitions before flashing the ROM? I use Titanium pro to backup my apps before doing this.
You should be able to do this with any of the recovery programs. 4EXT is really good and easy to use for this. Also, if you don't already know this, you should flash the correct GAPPS for your ROM after you install the update. That way you will have everything you need on your first boot after your flash.
Good luck!
when i updated my firmware from 3.32 to 3.33 i got stuck at the same screen. Just booted to recovery and used 4EXT Recovery touch to wipe cache and dalvik, after that everything was fine
Hi Guys. As my title shows I can't flash any other rom other than the official CyanogenMod 9.1. I do a full wipe of data, cache , and Dalvik Cache before I try a flash and as soon as I reboot I go into a bootloop. Any help would be great.
Boot to bootloader and write down everything from that screen
Boot to recovery and write down what version
Also name ROM you tried
Sent from my Nexus 4 using XDA Premium 4 mobile app
[email protected] said:
Hi Guys. As my title shows I can't flash any other rom other than the official CyanogenMod 9.1. I do a full wipe of data, cache , and Dalvik Cache before I try a flash and as soon as I reboot I go into a bootloop. Any help would be great.
Click to expand...
Click to collapse
Be sure to flash the boot.img, I currently have KitKatDS and any other rom will black screen on start up without first flashing.
Good Luck, Conner.
If not boot.img, your recovery may be out of date. Have you tried using one of these?
CWM: http://www.rootfiles.org/pub/mirror/silverl/cwm6046.img
TWRP: http://www.rootfiles.org/pub/mirror/silverl/twrp2630.img