[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
>>>>>Fixes and Additional Resources<<<<<

Post #2 will, as it claims, contains further useful information and links that will hopefully restore your device and continue to make your device-modding travels safe, smooth and fun. Please do not disregard the initial purpose of this thread and all the useful steps and information listed above. Post #2 is for those who have encountered common issues and errors, and are comfortable and familiar with all the required procedures for successfully modifying their devices. Cheers!​

Latest AOSP/CM/AOKP flash error - Updating Your Bootloader

For continued support and updates, read mrhaley30705's bootloader advisory first, then follow the Task's directions outlined in this thread. This is intended for those not on the necessary Jelly Bean bootloaders, allowing them to flash future [CM] builds.

Bootloops

Bootloops are mainly caused because system files are conflicting and interfering with each other. This instability causes crashes at the boot sequence.

To find the cause of a bootloop you have to think about what you did before the issue began. After flashing a new rom, stock firmware, kernel or restoring a system backup?

Method 1

1. Boot into recovery

2. Wipe Cache

3. Wipe Dalvik cache (custom recovery only)

4. Reboot your phone

If the problems still exists and you're sure it's not related to the ROM, then you need to wipe data as well:

Method 2

1. Boot into recovery

2. Wipe Data

3. Wipe Cache

4. Wipe Dalvik cache (custom recovery only)

5. Reboot your phone

Method 3 - This last method involves restoring your backup in order to correct the conflicting software by replacing it with a functioning platform

1. Boot into recovery

2. Wipe Data

3. Restore backup

4. Wipe Cache

5. Wipe Dalvik cache

6. Reboot your phone

Setting the wrong permissions or not adjusting permissions can also induce this error. Android is very dependent on the right permissions. If you adjust file permissions incorrectly you could find yourself in a bootloop. An easy fix is performing the "Fix permissions" option in recovery under Advanced. Be sure to mount the partitions before running the fix.

Status 7 error

When you receive a Status 7 error in CWM or TWRP, the most common reason for most users is that their recovery is not as up-to-date as the ROM requires it to be in order to install. There are a couple different ways to fix this, depending on each persons situation.

You've wiped everything on your device, removing your OS, and now you're receiving the error:

If you have a micro SD card, this fix is simple. You can download an up-to-date flashable CWM or TWRP recovery zip, place the file on your micro SD, flash the zip, go to Advanced and reboot recovery.

You've simply tried dirty flashing a ROM or ROM update and have only wiped data, cache and dalvik:

Use the above technique to update your recovery or boot back into your S3 to update. For CWM users, head to Rom Manager. If you use TWRP, hop into the Goo Manager app. Once you've applied the update, boot into recovery and flash the desired software.

Soft brick - Stuck at glowing Samsung logo

There are two types of bricks – the softbrick and hardbrick. The softbrick can be recovered if you can still get into download and recovery mode. Additionally, getting stuck at the Samsung logo is another one our most common issues seen. When you flash a stock ROM with Odin, your /data will be kept. This means your old dalvik cache is still being used for the new system files. If this is still possible, then boot into recovery and try these methods first:

Method A: Wipe

1. Wipe Data

2. Wipe Cache

3. Wipe Dalvik Cache

Method B: Wipe and Restore

1. Wipe Data

2. Wipe Cache

3. Wipe Dalvik Cache

4. In

CWM

: Select Mounts and Storage and format /system. In

TWRP

: Wipe System

5. Restore your backup

6. Wipe Data again

7. Wipe Cache

If neither of these methods has got your device back up and running, you will need to restore the phone with stock firmware via Odin. Make sure the battery is fully charged and follow these steps:

1. Download and run Odin on your PC

2. Download the stock firmware for your device

3. Boot into download mode and, when prompted with the warning, press Volume Up to continue. To access download mode, power down the phone and hold down the Volume Down + Home + Power buttons

4. Connect the phone to PC via USB. Make sure you can see the highlight COM:ID box once the device is detected

5. In the tickable option boxes, ensure ‘RE-Partition’ is unticked. Only ‘Auto Reboot’ and ‘F. Reset Time’ need to be checked off

6. Now click the PDA button and select the tar you downloaded

7. Click on “Start” to flash the stock firmware

8. Wait until the flashing successfully finishes and you see a word ‘PASS’

9. Unplug your device, pull the battery, replace and immediately press Volume Up + Home + Power to enter stock recovery. Release the power button when the device vibrates and you see the blue script in the top left corner

10. Wipe data, cache and wipe Dalvik cache (under advanced). Reboot

Low internal memory / Multiple "0" folders

This is a common issue when flashing a 4.2 ROM. Android 4.2 has multi-user support. The 0 folder is user 1. The best way to avoid this multiple folder problem is to always flash from the latest CWM or TWRP recoveries, whichever you prefer. The duplicate folders issue can be solved via the install method listed under the Reverting to 4.1 ROMs? section or as follows, if you've already flashed your 4.2 ROM:

Staying on 4.2+ ROMs?

1. Copy your sdcard data to /data/media/0 and then delete the /0/0 folders

2. When prompted, choose merge

3. Verify there is nothing in the other 0 folder, then you can delete it

4. Repeat with other /0 folders, if applicable

5. Reboot

Reverting to 4.1 ROMs?

1. In the event you are planning on returning to a 4.1.X ROM, I encourage users to make a backup and save/backup everything on the device that they wish to have on their device again after flashing. Save/move everything either to a micro SD card or to your computer.

2.*When you are in recovery and preparing to flash, wipe: data/factory reset, cache, dalvik, format /system, format /data & /media

This will eliminate the OS and all traces of the previous 4.2 data and folders, allowing you to boot into your device with the full amount of available memory and no duplicate "0" folders.

Simple and Fast Wiping Mods

In this thread by Upndwn4par, there are three recovery-flashable wiping tools that you can use while working on your device. They can be incredibly useful tools that save some power button & volume rocker mashing. With the snappy flashing of these zips, you can easily perform a

Cache & Dalvik Cache wipe

, a

Full Wipe

or a

Full Wipe Factory Reset

. These are handy and will ensure you perform the necessary wipe to best optimize your ROM, mods and troubleshooting. Per-wipe details in the link.

Unroot your device

Need to get your S3 ready to return to the manufacturer? Follow this link and you'll be squared away in under 10 minutes. You'll need:

- Triangle Away installed

- The official stock firmware for your device

- Odin installed on your PC

- Your Samsung USB cable, if possible

- Samsung drivers installed on PC

Build your own Must Have toolkit

In the world of rooted phones running custom ROMs, you will find the simple micro SD card to be the best $10 you've ever spent. I would strongly encourage everyone to purchase one of these and build themselves their very own emergency-response toolkit, stored right on the device. To do this, grab yourself a micro SD card and place these files on it:

- Your stock Nandroid backup

- Your most recent or preferred Nandroid running your current custom ROM

- The ROM/gapps you're currently running

- A current flashable CWM 6.0.3.0 / 6.0.3.1 or TWRP 2.4.4.0 / 2.5.0.0 custom recovery

- A flashable stock ROM