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?
Related
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 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==
Help guys. So my problem is that, my SG3 I9300 is keep on rebooting. It'll just boot to my desktop for about 2-3 seconds then it will reboot again and again. I have to remove my battery for about half an hour and put it back on to reboot successfully. Another thing is that after it reboots successfully, when I use applications like FB / COC it also reboots on its own so as the stock camera application. Apollo is a system app like the camera right? But Apollo works without any problem unlike the camera.
I thought it is a bootloop problem, just like what I've said on my previous post. Sorry for that.
So here are the things I've tried:
1. Flash stock rom (from Sam mobile) thru Odin
2. Delete cache and factory reset in custom recovery
3. Factory reset on TWRP - Wipe everything including Internal sd - Flash Megawipe
4. Flash other custom roms thru TWRP/CWM
5. Flash stock rom thru Kies
The problem still occurs after everything I've done. So please help me
Thanks! :good:
Current rom: cm11 m12
Android version: 4.4.4 KK
Kernel: boeffla 2.7 NG
JohnRod said:
Help guys. So my problem is that, my SG3 I9300 is keep on rebooting. It'll just boot to my desktop for about 2-3 seconds then it will reboot again and again. I have to remove my battery for about half an hour and put it back on to reboot successfully. Another thing is that after it reboots successfully, when I use applications like FB / COC it also reboots on its own so as the stock camera application. Apollo is a system app like the camera right? But Apollo works without any problem unlike the camera.
I thought it is a bootloop problem, just like what I've said on my previous post. Sorry for that.
So here are the things I've tried:
1. Flash stock rom (from Sam mobile) thru Odin
2. Delete cache and factory reset in custom recovery
3. Factory reset on TWRP - Wipe everything including Internal sd - Flash Megawipe
4. Flash other custom roms thru TWRP/CWM
5. Flash stock rom thru Kies
The problem still occurs after everything I've done. So please help me
Thanks! :good:
Current rom: cm11 m12
Android version: 4.4.4 KK
Kernel: boeffla 2.7 NG
Click to expand...
Click to collapse
Try another battery if not it is a faulty power button or other hardware problem. I see you have tried other roms so this rules out a software problem....
tallman43 said:
Try another battery if not it is a faulty power button or other hardware problem. I see you have tried other roms so this rules out a software problem....
Click to expand...
Click to collapse
I'm hoping it is a battery problem alone. I'll note that for now bud, thanks! :good:
I was using the Blekota Note 4(based on Kitkat) on my i9300 when it one day suddenly it restarted on its own and went into a bootloop and heated up. So I took out the battery and tried starting it again by clearing cache and dalvik cache. But it was still stuck at bootloop. After about 3 hours, somehow it came back on its own, but all the data and settings were lost. The downloaded apps were present, but their settings were lost.
Since I would have to again set up all apps, I wanted to try a new rom, Lollipop based. I downloaded the latest RESURRECTION REMIX (5.5.7) apps and downloaded the OpenGapps micro package. But after trying a clean install, the boot loop problem was still there. I tried with a different Gapp package, from OmniRom thread (all were for Android 5.1) but still no help. Even flashing the ROM alone would be of no help. I remembered I had a similar problem after flashing Boeffla kernel and the solution in that case was flashing a new version of the kernal. I tried that also. But no help.
I changed my recovery from CWM to TWRP as someone in some thread mentioned that it could help. But still No avail. In doing a clean rom, I tried almost 3 roms, cleaned cache, system, dalvik cache and even the internal storage and tried all other combinations. BUT THE SAME BOOT LOOP PROBLEM REMAINED.
As a last resort I had to flash the original 4.3 JellyBean firmware hoping that performing a clean install from that would help. But even after that the boot loop remains. Someone please help me flash a Lollipop based rom. This thing is driving me crazy now.
There's still 1 basic procedure: flash a 3part firmware with PIT-file for repartition.
Pit files should only be considered as a last resort.
Clear data and reflash stock rom and repeat once more. I have had cases where the rom didnt fully clear on a normal single flash.
Dont let it boot to rom. Do the two data wipes from recovery only.
I wish I stole my HTC M9.
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