Hi All,
Last week, I flashed my LG Nexus 4 (16GB) phone with stock Android 4.4 (Official Image), before that I was on CyanogenMod 10.1.3 Stable.
Now, for some reason I didn't like the stock 4.4 and tried to Flash back my CyanogenMod 10.1.3 from CWM "Install ZIP" but the problem I'm facing is that it CyanogenMod doesn't boot, hangs on "Spiral Splash Screen". Then I tried Flashing CM 10.0 stable, still loops into boot forever and at times boots (after 15-20 minutes of booting on spiral splash screen) and doesn't recognise SIM card, Camera, Storage, WIFI or anything.
Then after getting fed up with this I tried flashing MIUI V5. This also takes a 15-20 to boot and fails to recognise - SIM, WiFi, Camera etc.
So lastly like a loser I flashed back my Android 4.4 it works fine.
I've my boot-loader in unlocked state.
and Yes before flashing CM or MIUI, I did - wipe data/factory, wipe cache, wipe dalvik cache from CWM Recovery.
So I want to get back into CyanogenMod 10.1 stable. Help me out with this.
Restoring Nexus 4
prakharprasad said:
Hi All,
Last week, I flashed my LG Nexus 4 (16GB) phone with stock Android 4.4 (Official Image), before that I was on CyanogenMod 10.1.3 Stable.
Now, for some reason I didn't like the stock 4.4 and tried to Flash back my CyanogenMod 10.1.3 from CWM "Install ZIP" but the problem I'm facing is that it CyanogenMod doesn't boot, hangs on "Spiral Splash Screen". Then I tried Flashing CM 10.0 stable, still loops into boot forever and at times boots (after 15-20 minutes of booting on spiral splash screen) and doesn't recognise SIM card, Camera, Storage, WIFI or anything.
Then after getting fed up with this I tried flashing MIUI V5. This also takes a 15-20 to boot and fails to recognise - SIM, WiFi, Camera etc.
So lastly like a loser I flashed back my Android 4.4 it works fine.
I've my boot-loader in unlocked state.
and Yes before flashing CM or MIUI, I did - wipe data/factory, wipe cache, wipe dalvik cache from CWM Recovery.
So I want to get back into CyanogenMod 10.1 stable. Help me out with this.
Click to expand...
Click to collapse
Hello Prakhar,
I would suggest you to first download the official image of Nexus 4 for android 4.3 and flash it from https://developers.google.com/android/nexus/images and then you can try to flash CM 10.1.3 from the CWM Recover Console. Hope this helps!
I would also like to point you out to https://developers.google.com/android/nexus/drivers which contains drivers for your phone's camera, etc. you can download those binary and flash it one by one through your recovery console, which might fix your issues.
It worked !
Downgraded to stock 4.2.2 then Flashed CM 10.2 RC1 from CWM Recovery !
Thanks a lot U3ViaGFsbyA6UA==
Related
Hi,
I am starting from rooted stock with emmc CWM v5.0.2.8
As always before flashing any ROM I backup, wipe data/factory reset, and wipe dalvik cache.
I have tried flashing SlimBean, LiquidSmooth, CyanogenMod unofficial, and CyanogenMod nightly; all with the same result.
Cyanoboot comes up just fine, then it proceeds into the ROM boot animation, sometimes it displays the boot animation for a few seconds,freezes then loops, others it just loops.
I have tried flashing "flashable_fix_bootloop.zip"
I have also tried flashing from CWM 6.02.7 but that recovery for me is very laggy and cannot access sdcard
I am really confused I would love for my tablet to be on jellybean the stock B+N is terrible
Any help is much appreciatted,
thatsnailguy
You could always do what I describe in the topic that at this moment is right below yours. Not the most elegant, but almost fool proof! The CM10 I use is better than any 10.1 I have tried. Either way, it's better than stock.
thatsnailguy said:
Hi,
I am starting from rooted stock with emmc CWM v5.0.2.8
As always before flashing any ROM I backup, wipe data/factory reset, and wipe dalvik cache.
I have tried flashing SlimBean, LiquidSmooth, CyanogenMod unofficial, and CyanogenMod nightly; all with the same result.
Cyanoboot comes up just fine, then it proceeds into the ROM boot animation, sometimes it displays the boot animation for a few seconds,freezes then loops, others it just loops.
I have tried flashing "flashable_fix_bootloop.zip"
I have also tried flashing from CWM 6.02.7 but that recovery for me is very laggy and cannot access sdcard
...
Click to expand...
Click to collapse
To flash CM10 you need a newer version of CWM v6.x.y.z. See http://forum.xda-developers.com/showpost.php?p=43326042&postcount=123 for more pointers.
If you still cannot boot past the boot-animation try flashing Succulent's fix flash_kernel_acclaim_30MAR2013_HD.zip at posted at http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/ (under the heading "Flash this if your NT doesn’t boot newer kernel").
Thank you apparently I downloaded a wrong version of a 6.x.x.x cwm its all working now.
I've been having a problem getting any 4.3 ROM to boot after the initial boot. I've seen a few other people with the same problem and I can't figure out a fix. Thought I'd ask the general Q&A.
I've used Beanstalk and Carbon (great ROMs) a few carbon 4.3 nightlies and Beanstalk 4.3.00. I installed their 4.3 builds (after checking sums to verify download) flash gapps, wipe cahce/dalvik and boot up. Set up goes great and rom runs great. but even without installing any other apps, using no backups or anything if I reboot it sticks on samsung screen and can't get past it. Every time, I even rebooted without finishing setup and wouldnt advance past samsung.
I even flashed 4.3 rom and gapps, let it reinstall apps from market then booted to recovery and made a backup. Then could'nt reboot. But if I wipe and restore the backup it will boot fine the 1 time, but again any attempts to reboot stick on samsung screen. Wiping cache/dalvik from recovery does not help, fix permissions from recovery does not help.
Anybody have this problem and find a fix?
Ok, I tried slim bean beta 2, no luck, tried ktoons kernel, no luck. Guess I'm staying with 4.2.2 until there is some movement on this issue.
Hi to everyone!
I have a Samsung I9300T (Australian version). A few months ago I flashed my phone through CM Installer from stock Rom (Vodafone's Android 4.1.2) to CM 11 M2. And there were no problems.
A month ago I flashed CM 11 M6. And after upgrading from M2 to M6 my phone started rebooting at random times. In these moments, the display goes black, then the logo "Samsung S3" is displayed for a few seconds, then reboot again and it lasts permanently. I flashed cm m2 back, but this problem not solved.
I've made full wipe, installed M7, installed GApps, made full wipe. And it's still reboots.
I've reinstalled CWM recovery through ROM manager. And it's still reboots.
I've made full wipe. installed another ROM (not CM), made full wipe. And it's still reboots.
I've flashed default stock and recovery from vodafone (4.3) through Odin, and it's still reboots.
Please, help me with this trouble.
Thank you.
If it is still the same on a fresh install of stock firmware then it is a hardware issue.
boomboomer said:
If it is still the same on a fresh install of stock firmware then it is a hardware issue.
Click to expand...
Click to collapse
When I flashed a stock ROM, I found some files from CM ROM in phone memory. How can I make full format of all data in phone? I think some parts of old ROM make bugs. And maybe kernel was modified, may it cause these problems?
I was using my phone and all had been working fine for ages. It was in my pocket for a while and when i took it out to use it I saw that it was on the boot animation of CM11. My phone was already on when I last used it so I had assumed it had crashed. I took the battery out and turned the phone on again but it got stuck on the CM boot animation. The last time I turned on my phone before that was when I flashed a supersu zip file to make my root work as I was having some problems. After flashing the supersu zip and told my CWM recovery to restart the system, it prompted me to "fix root" or something like that, and I clicked yes and it booted normally. That was the last time it booted normally before being stuck as it is now. First thing I did after it got stuck was go into recovery and reflash my current rom ( a CM11 snapshot) I then got faced with a status 7 error and so couldnt flash the rom. So then I flashed multiple other CM11 roms, none of which worked, so I flashed a CM10.2 stable rom which worked. I then got faced with the fix root before reboot thing and so I clicked yes. Still had the stuck booting thingy. I tried many things, flashing kernals roms gapps etc and nothing made a difference. I wiped cache, dalvik cache and no difference. I even wiped the system and tried to flash roms but only the 10.2 one would work, still got a status 7 with the CM11 ones. When I wiped my data however and flashed CM 10.2, it booted. I still couldn't flash the CM11 roms though even after a factory reset. So I have the reason to believe something in the data is wrong, not cache system or anything like that. What could it be? I don't want to have to lose all my data in order to be able to use my phone again, even then, something is still wrong as my phone won't flash CM11 roms anymore. So my questions are;
What things could have caused this?
Can this be a problem from flashing the supersu zip (a root issue)
Is it possible to somehow view or copy the internal data on a computer (since I cant get into the operating system), and this would allow me to get all my pictures contacts music etc anything so I can use my phone by wiping data?
Thanks, sorry this is quite long and probably hard to understand whats going on, but help is appriciated thanks
Don't fix root if you wish to use SuperSU instead builded-in cm superuser. Also try to flash via Odin latest recovery. TWRP should be fine. You can mount partitions from recovery level to download data to your computer. Of course if it still exists. If not, if they are corrupted you need to flash stock ROM and repeat whole cm11 adventure again. If Odin successfully flash the stock then it's a chance your partition layout and user data are untouched.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Hey Guys,
I have an unusual issue when it comes to trying to flash custom ROM's onto my Nexus 9.
I have already unlocked the bootloaded, installed the latest version of TWRP which worked fine.
I then went to do the usual wiping everything off my tablet before going any further (Dalvik Cache, System, Data, Internal Storage and Cache)
Then I use MTP to move the ZIP's that I want to install onto the internal storage (I've tested CyanogenMod 12 and the latest version of LiquidSmooth (At seperate times) )
The install process goes okay and doesn't show up any errors.
Then when I go to reboot the Nexus 9, I get the static "Google" logo (the splash screen before the operating system's splash) and it just sits there for 12 hours until the battery slowly drains (litterally 12 Hours)
Any idea's how to fix this? I can boot back into fastboot and access the recovery. I can also restore using the softbrick option in the Nexus Tool Kit to boot back into a fully functioning Android 6.0 but obviously that's not the aim.
Thanks for taking the time to read this
TechKno said:
Hey Guys,
I have an unusual issue when it comes to trying to flash custom ROM's onto my Nexus 9.
I have already unlocked the bootloaded, installed the latest version of TWRP which worked fine.
I then went to do the usual wiping everything off my tablet before going any further (Dalvik Cache, System, Data, Internal Storage and Cache)
Then I use MTP to move the ZIP's that I want to install onto the internal storage (I've tested CyanogenMod 12 and the latest version of LiquidSmooth (At seperate times) )
The install process goes okay and doesn't show up any errors.
Then when I go to reboot the Nexus 9, I get the static "Google" logo (the splash screen before the operating system's splash) and it just sits there for 12 hours until the battery slowly drains (litterally 12 Hours)
Any idea's how to fix this? I can boot back into fastboot and access the recovery. I can also restore using the softbrick option in the Nexus Tool Kit to boot back into a fully functioning Android 6.0 but obviously that's not the aim.
Thanks for taking the time to read this
Click to expand...
Click to collapse
I haven't flashed either of those ROMs but perhaps you need different vendor images or something.
What build # are you on?
The latest is: mra58n
I personally am on Pure Nexus, and I didn't have to flash anything besides the ROM.
I just got the tablet on the 40% off deal a few weeks ago, it came with an early LP build, I first flashed the mra58n factory image, then I unlocked bootloader installed TWRP and rooted and made a backup.
Then I flashed Pure Nexus and all has been running smooth.
I would suggest giving that ROM a flash - it's been updated to Android 6.0 and runs great and battery is amazing.
andybones said:
I haven't flashed either of those ROMs but perhaps you need different vendor images or something.
What build # are you on?
The latest is: mra58n
I personally am on Pure Nexus, and I didn't have to flash anything besides the ROM.
I just got the tablet on the 40% off deal a few weeks ago, it came with an early LP build, I first flashed the mra58n factory image, then I unlocked bootloader installed TWRP and rooted and made a backup.
Then I flashed Pure Nexus and all has been running smooth.
I would suggest giving that ROM a flash - it's been updated to Android 6.0 and runs great and battery is amazing.
Click to expand...
Click to collapse
Thanks for the response, just tried flashing Pure Nexus to it but with the same thing happening. I know it's only been 5 mins so far but it surely should have atleast moved onto the OS's splash?
This was the version I used: pure_nexus_flounder-5.1.1-20150817.zip
I shouldn't need a working OS installed as the base due to the fact that installing a new OS would just overwrite it?
TechKno said:
Thanks for the response, just tried flashing Pure Nexus to it but with the same thing happening. I know it's only been 5 mins so far but it surely should have atleast moved onto the OS's splash?
This was the version I used: pure_nexus_flounder-5.1.1-20150817.zip
I shouldn't need a working OS installed as the base due to the fact that installing a new OS would just overwrite it?
Click to expand...
Click to collapse
that is Android 5.1.1 Lollipop
We want Android 6.0 Marshmallow
pure_nexus_flounder-6.0-20151113.zip
If this doesn't work I would personally flash the mra58n and start over.
Make sure to wipe in recovery before flashing.
andybones said:
that is Android 5.1.1 Lollipop
We want Android 6.0 Marshmallow
If this doesn't work I would personally flash the mra58n and start over.
Click to expand...
Click to collapse
Yeah, I think he's right. Sounds like you have a mishmash of android 5.1.1 and 6.0
Start clean by flashing the latest factory image (bootloader, boot, system, data, vendor). Once that's running, then you can flash TWRP (I suggest using the custom TWRP found under the FireIce kernel thread) and install an android 6.0 custom ROM.
Whichever ROM you choose, make sure to read thru its thread carefully. There are a number of things that can cause bootloops, so be sure to follow the installation instructions for that ROM.
TechKno said:
Hey Guys,
I have an unusual issue when it comes to trying to flash custom ROM's onto my Nexus 9.
I have already unlocked the bootloaded, installed the latest version of TWRP which worked fine.
I then went to do the usual wiping everything off my tablet before going any further (Dalvik Cache, System, Data, Internal Storage and Cache)
Then I use MTP to move the ZIP's that I want to install onto the internal storage (I've tested CyanogenMod 12 and the latest version of LiquidSmooth (At seperate times) )
The install process goes okay and doesn't show up any errors.
Then when I go to reboot the Nexus 9, I get the static "Google" logo (the splash screen before the operating system's splash) and it just sits there for 12 hours until the battery slowly drains (litterally 12 Hours)
Any idea's how to fix this? I can boot back into fastboot and access the recovery. I can also restore using the softbrick option in the Nexus Tool Kit to boot back into a fully functioning Android 6.0 but obviously that's not the aim.
Thanks for taking the time to read this
Click to expand...
Click to collapse
You should erase your internal storage. It happen to me I did the same steps that you did and I had to re flash the system files all over again. Once finish I only wipe dalvik cache,cache and data and it work perfectly