Samsung Galaxy S3 - Galaxy S III Q&A, Help & Troubleshooting

Hi,
I rooted my phone back in August. I made a backup of the rooted device. I have reset it numerous times. This time it will not work. I started without gapps the first time. I re-did the backup and did gapps but my phone is stuck on android is upgrading after it optimizes apps. I have Philz touch Clock work. I also have liquid smooth but it doesn't appear when I reboot. I have the liquid smooth file on my sd so i can install ls zip and then gapps and the phone will boot up so my phone is on on. The setup wizard fails and I cant access anything. I've tried different gapps 5.1 4.4.2(orignal one), 4.4.3 not compatible. I'm assuming i didn't brick it because it does start and go to myregular phone display.I don't know if something was updated with samsung which made my backup or gapps not work correctly. Any help would be greatly appreciated. I have wiped rom, davlik, cache, installed backup...same process install liquid smooth first. Ive done my backup without gapps and it starts but all apps fail because no gapps.

Related

[Q] CM10.1 Issue - Odin solution?

Hello, I'm having a bit of an issue here I can't install a ROM after trying CM10.1.
I was using CM10, up until awhile, when I deiced to give CM 10.1 a try (Alpha build I'm aware of the risks).
I have installed CM10.1 using Rom Manager Premium. The installation progress went smooth without any errors, before installing I've made a backup of my current ROM.
Once CM10.1 finished optimizing application it started giving errors, that it can't load up Setup Wizard stopped from working, I have rebooted into CMW, wiped Dalvik cache and user data, I have booted up again, and was still was getting the same error, so I decided to restore my previous ROM.
But when I have booted up into CWM, I have discovered that the backup I made isn't there, not on the Internal memory and not on the SD card.
The issue I'm having is that I can't instal CM10 back, when ever I try to install CM10 ROM ZIP using CMW from external SD I get an error (Status 7)
Is there any ODIN CM10 installation route?
Thank you!
Update 1:
I have manged to flash The Official Rom, But it can't boot up, it seems like it's stock on the animation screen, the animation moves, but doesn't boot up. What might be the issue?
Update 2:
Solved the problem by wiping use data, and resting it to factory settings.
Update 3:
Got it fixed, everything is running like it used to be. Shame that I lost all my personal DATA, specially the DICM folder :/

[Q] Can't install any JB ROM

So was running an old version of PA 2.16 by Th3Bill and I kept having a problem where Apollo would crash. So I decided I was going to do a clean install of the newest version of PA 2.99 Final. Verify the MD5 and install with the guide on his page here: http://th3bill.com/?page_id=150
Making sure I have the proper CWM Recovery and Aroma Prep installed. At first it took the ROM, but it kept hanging a few seconds after boot and then rebooting infinitely. Tried doing a complete wipe and starting the process over. Now it CWM Recovery locks up and the screen glitches out during the ROM install at 40%. I tried the CM10 ROM it does the same thing. I tried to restore my backup of PA 2.16 and it took the files, but it just looped endlessly. Lastly I tried restoring a backup of a GB ROM and that booted and worked perfectly, but I'd prefer to get back on JB.
Anyone know what could be wrong and where I should start?

AOSP 4.3 boot issues

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.

[Q] 4.3 ROM Flashing Problem

Anyone else have problems flashing to a 4.3 ROM? (I know some people do because I've searched.)
No matter what ROM it is, if it is 4.3 it will always fail to reboot a second time after it has been flashed.
Currently on CleanROM ACE 4.9 (4.1.2) with TWRP 2.6.0.1
I've tried to go to CM10.2 and it would reboot initially but then hang on the Note II logo if I tried to reboot.
I've tried to go to Paranoid Android.. same thing.
I've tried to go to PAC-man.. same thing.
I've tried flashing from the stock 4.1.2 ROM and the same thing happens.
I've followed every instruction I could find including this: http://forum.xda-developers.com/showthread.php?t=2423057
I do a factory reset, format data, flash ROM, wipe caches, flash gapps, wipe caches, reboot. It will boot fine from TWRP and load everything normally. Then, if I reboot or power off the device, it will hang on the Note II screen and I have to nandroid back to my previous ROM.
Any insight as to why this is happening? I haven't been able to find anything besides some random instructions for wiping/flashing (which I've linked). These ROMs look great and I'd really like to move to 4.3, but I cannot figure out what the problem is.
BigBoy275 said:
Anyone else have problems flashing to a 4.3 ROM? (I know some people do because I've searched.)
No matter what ROM it is, if it is 4.3 it will always fail to reboot a second time after it has been flashed.
Currently on CleanROM ACE 4.9 (4.1.2) with TWRP 2.6.0.1
I've tried to go to CM10.2 and it would reboot initially but then hang on the Note II logo if I tried to reboot.
I've tried to go to Paranoid Android.. same thing.
I've tried to go to PAC-man.. same thing.
I've tried flashing from the stock 4.1.2 ROM and the same thing happens.
I've followed every instruction I could find including this: http://forum.xda-developers.com/showthread.php?t=2423057
I do a factory reset, format data, flash ROM, wipe caches, flash gapps, wipe caches, reboot. It will boot fine from TWRP and load everything normally. Then, if I reboot or power off the device, it will hang on the Note II screen and I have to nandroid back to my previous ROM.
Any insight as to why this is happening? I haven't been able to find anything besides some random instructions for wiping/flashing (which I've linked). These ROMs look great and I'd really like to move to 4.3, but I cannot figure out what the problem is.
Click to expand...
Click to collapse
First time installing CyanogenMod 10.2 to your Galaxy Note 2 I605, or coming from another ROM:
- Read known issues ans FAQs
- Flash the latest official ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
read the OP for CM 10.2 next time....
First - clockworkmod not twrp for 4.3 usually fixes things
Second - do a factory reset AFTER installing
Third - Dont restore apps with TiBu going to 4.3
Next time be truthful when you say you read and searched.

Boot Loop Problem persists after installing Lollipop ROM & clean install

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.

Categories

Resources