Ultimate Guide For [BOOTLOOP RECOVERY] Noob Friendly

Search This thread

keifus.rahn

Senior Member
Jun 30, 2013
357
158
Midland Tx
RECOVERY FROM BOOT LOOP/BRICK​

Most people use the term "bricked" improperly. A bricked phone means one thing: your phone won't turn on in any way, shape or form, and there's Probably nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they're a lot more common than a truly bricked phone. If your phone is actually bricked, you Probably won't be able to fix it yourself.
BOOTLOOP GUIDE
(#:1)
Start by removing the device's battery and wait for a few minute's before putting it back in your phone.
OR Switch off for non-removable battery phones for five to ten minutes so it can remove any charge that is left in the phone and to initiate a complete power-cycle once you insert the battery.
Now Boot the device into Recovery Mode by pressing and holding the relevant shortcut keys for your device. For instance, most Samsung devices can boot into Recovery Mode while pressing the key combination Volume Up, Home and Power (for tablets it is Volume Up and Power). If using a HTC phone, boot into HBOOT first by tapping Volume Down and Power button together and then browse to Recovery using Volume Up/ Down buttons. If you cant get it to boot in Recovery you can always use (ADB) and type in the command] > adb reboot recovery <--- Hit Enter now your Device will reboot into recovery mode. If your not familar with adb or even know what adb is there is a link on the bottom of this page for the sdk download and a gude on the adb.

(#:2)
Now browse and select the option Wipe Data/Factory Reset in Recovery Mode.Check if the device can now boot into the newly installed ROM or firmware. If not, then perform Wipe Cache Partition And Return to the main Recovery menu and reboot the device by choosing Reboot System Now option.After Flashing or Installing a New ROM and If the device is already rooted with ClockworkMod Recovery (CWM) installed, then do the following steps (1) Remove you'r battery and reinsert it after 30 seconds. (2) Boot the device into CWM Recovery by pressing and holding Volume Up, Home and Power buttons together. NOTE: The key combination may vary depending on your device model.So, CONFIRM BEFORE YOU PROCEED. (3) Now Go to Advanced option in Recovery menu and choose Wipe Dalvik Cache. Then perform Wipe/cache under Mounts & Storage. Reboot the device and check if the boot loop issue is resolved. If not repeat the above three steps, but perform both Wipe/data and Wipe/cache under Mounts & Storage before rebooting.

(#:3)
After Setting an Incorrect File Permission.The Android operating system (OS) works on file permissions and hence incorrectly set file permissions may permanently damage or soft brick your device. Here are some of the commonly used file permissions:- 644 (RW-R-R) - (this is most common system permission, it exists in /system/app, /system/framework, /system/etc, /system/lib and allot of separate files) - 755 (RWX-RX-RX) - (mainly used for /system/bin) - 777 (RWX-RWX-RWX) - (used for scripts inside /system/etc/init.d and busybox files)
To fix or reset any of these file permissions, do the following:Boot the device into CWM or TWRP recovery Go to Advanced option.Click Fix Permission and confirm the action. After Restoring a Backup.If the bootloop error occurs immediately after restoring a Nandroid Backup, follow the steps on -(#:2)- to fix it. If everything else fails, just try re installing the original ROM or flash the first official firmware.

Using ADB BY Samantha
DB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the manufacturer logo. (In new CWM versions it’s possible to use adb)
The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is different from every device, but normally it’s after the manufacturer logo that the partitions get mounted. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible.

I use this script for example, called ondemand.bat (requires adb.exe and the 2 dlls)


1 @ECHO off
2 cd /d %~dp0
3 echo.
4 echo Waiting for device…
5 adb wait-for-device
6 echo.
7 adb -d shell stop
8 adb push mycwmfix.zip /sdcard/mycwmfix.zip
9 adb reboot recovery


Linux Version (ondemand.sh):


1 #!/system/bin/sh
2 echo " "
3 echo "Wating for device..."
4 ./adb wait-for-device
5 echo " "
6 ./adb -d shell stop
7 ./adb push mycwmfix.zip /sdcard/mycwmfix.zip
8 ./adb reboot recovery

This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push the specified cwmfix zip to your sdcard, and after that it will reboot in recovery so you can install the cwm fix you made. You can also make an batch script that pushes the files automatically to your phone, here is an example:


(1 @ECHO off
(2)cd /d %~dp0
(3)echo.
(4)echo Waiting for device...adb wait-for-device
(5)echo.
(6)adb -d shell stop
(7)adb -d shell su -c "mount -o remount rw /system"
(8)adb push framework-res.apk /system/framework/framework-res.apk
(9)adb -d shell chmod 644 /system/framework/framework-res.apk
(10)adb push SystemUI.apk /system/app/SystemUI.apk
(11)adb -d shell chmod 644 /system/app/SystemUI.apk
(12)adb reboot

(13)Linux version:

1#!/system/bin/sh
2echo " "
3echo "Waiting for device..."
4./adb wait-for-device
5echo " "
6./adb -d shell stop
7./adb -d shell su -c "mount -o remount rw /system"
8./adb push framework-res.apk /system/framework/framework-res.apk
9./adb -d shell chmod 644 /system/framework/framework-res.apk
10./adb push SystemUI.apk /system/app/SystemUI.apk
11./adb -d shell chmod 644 /system/app/SystemUI.apk
12./adb reboot
This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push framework-res.apk and SystemUI.apk to the directory it belongs to, after that it changes the permissions of the files to RW-R-R (644) and then it will reboot.

Please note that on some devices the command “su -c” cannot be used after using the “stop” command, it gives an error then (Segmentation Fault).
What you can do to prevent this is adding “adb remount” just under the “adb wait-for-device” line, and remove the “adb -d shell su -c “mount -o remount rw /system” line.
Save the script and run it again.



For HTC Phones: HTC phones can flash stock ROMs, known as RUUs, right from the phone's bootloader. You'll need to Google around for your device's specific RUU file, but once you download it, save the ZIP file to your SD card, and rename it (to something like PG05IMG.zip—the download page for the RUU file should specify which filename is required), booting up your phone should automatically flash the stock ROM from HBOOT, HTC's bootloader. Video http://www.youtube.com/watch?feature=player_embedded&v=tE8BiIFUOpk

For Samsung Phones If you're using a Samsung Galaxy phone, you can use a tool called Odin to reflash an OPS file, which is a stock ROM that will return your phone to factory settings. You'll need a Windows machine and a copy of Odin, which you can find by Googling around the net (as its not an official tool) check out The Unlockr's guide to using Odin to familiarize yourself. You may need to Google around for your specific device's OPS file and instructions.
Video http://www.youtube.com/watch?feature=player_embedded&v=5s70dwNgdD8

Verizon Galaxy S3 Bootloop fix using Odin

The Verizon Galaxy S3 has to be the most problematic variant of the Galaxy S3. If the locked bootloader on it wasn’t enough, many users have seen their Verizon Galaxy S3 get bricked and stop booting after trying to flash a custom ROM.​

To start off there will be a little bit of downloading:p

Samsung USB Driver V1.5.14.0 For Android Mobile Devices

ODIN

VRALEC.bootchain.tar.md5

BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5

stock.vzw_root66.

Now lets Start
Make sure phone is off. Boot into download mode. To do so, hold down the Volume Down, Home and then the Power buttons together until a Warning!! message is displayed on the screen. Here, press Volume Up to enter download mode. A green Android and the text Downloading will be displayed on the screen.
Now, open Odin by clicking on the Odin3 v3.07.exe file in the Odin307 folder which you obtained after extracting Odin307.zip
In Odin, click on the PDA button, then select the VRALEC.bootchain.tar.md5 file that you downloaded.
Important Untick every option under the “Option” section (on the top left of Odin), except F. Reset Time. Check the screenshot below for reference.
unbrick-vzw-s3-ss-11-700x517.jpg


Then, connect the phone to the computer with the USB cable and wait for Windows to finish installing drivers. Odin will say Added!! in the message box on the bottom left if the phone is detected successfully. If not, make sure the drivers are installed and also try using a different USB port – preferably a USB port on the back if using a desktop computer.
Click on Start to start flashing the VRALEC.bootchain.tar.md5 file on the phone.
Wait till flashing is complete and you get a PASS message in Odin. When that happens, disconnect the phone from the computer, but DON’T turn it off and let it stay in download mode. Also close Odin.
Reconnect your phone to the computer (while it is in download mode). Open Odin again.
This time, click the PDA button and select the BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar.md5 file that you download
Also, again untick every option except F. Reset Time in Odin. Then, click on the Start button to start flashing the BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar.md5 file on the phone.
When flashing is complete and you get a PASS message, disconnect the phone and close Odin. But keep the phone in download mode, don’t turn it off.
Open Odin again and also reconnect the phone to the computer.
Click the PDA file and select the stock.vzw_root66.tar file that you Downloaded
[Important] Select the following three options in Odin on the top left: Auto Reboot, F. Reset Time, Nand Erase All. Check the screenshot below for reference.
unbrick-vzw-s3-ss-2-700x515.jpg


Click Start to start the flashing process. Once the flashing is complete and you get a PASS message, the phone will automatically reboot. Disconnect the phone from the computer.
The phone will still not boot up completely. Now, remove the battery on the phone, then re-insert it. Don’t turn it on.
Now, boot into recovery. To do so, press and hold the Volume Up + Home + Power buttons together till the screen turns on, then let the buttons go. The phone will boot into recovery in a few seconds. You will see a few error messages in recovery, which is normal.
In recovery, use the volume buttons to scroll up/down and the home button to select options.
Select wipe data/factory reset, then select Yes on next screen to confirm. Wait a while till the data wipe is complete (this will NOT delete your personal files on the SD cards).
Select wipe cache, confirm, then wait for cache wipe to be completed.
Then, select reboot system now to reboot the phone.
The phone will now boot up properly into Android and is fixed, and you will be able to use it now.

Your Verizon Galaxy S3 is now fixed, and saved you from sending it in for repair to Verizon. Do let me know how the procedure works!


HOW TO UNBRICK YOUR DEVICE​

REQUIREMENTS TO UNBRICK YOUR PHONE

First install java on your pc if you haven’t java go to Java site and install it.
download one-click Unbrick tool
window users will need .rar/.zip extractor software , you can download free all in one 7zip extractor form here.

FOLLOW THESE INSTRUCTIONS CAREFULLY

1. Right-click on the One-Click.jar file, move down to option “7-zip” and then select “Extract to OneClick”.

2. Now you will get a ‘OneClick’ folder.

3. Now copy ‘OneClick.jar’ file and paste it into the ‘OneClickheimdalloneclickresourcesHeimdallPackage’ folder.

4. Right-click on ‘oneclickloader.exe’ file and choose ‘Run as Administrator’.
5. Proceed with the installation of Heimdall.

6. After the installation is complete, you will see the the One-Click UnBrick interface.
OneClick.jpg

Connect the phone to computer via USB and click on “unsoft brick” button to recover your bricked android phone.







Factory Rom's


Factory Images for Nexus Devices
https://developers.google.com

SAMMOBILE
http://www.sammobile.com/

ROM DOWNLOADS FOR HTC
http://www.htc.com/us/support/rom-downloads.html

HTC UNLOCK BOOTLOADER
https://www.htcdev.com/

Motorola
https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth

UNLOCK YOUR Motorola BOOTLOADER
https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth

RE-LOCK YOUR Motorola BOOTLOADER AND FACTORY IMAGES FOR DEVELOPER EDITION DEVICES
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images

Moto Support
https://motorola-global-portal.custhelp.com/app/home/

LG Software & tools Download
http://www.mylgphones.com/lg-software-tools-download

CLOCKWORKMOD RECOVERY & ROMS Phone Selection
http://www.clockworkmod.com/rommanager

TeamWin - TWRP
https://twrp.me/

ANDROID SDK
http://developer.android.com/sdk/index.html

ADB GUIDE
http://developer.android.com/tools/help/adb.html
 
Last edited:

islandmixed

Senior Member
May 4, 2012
414
22
Root should have been removed when you flashed the firmware via Odin.

I figured that you'd get the errors with the Google apps.

Try booting to stock recovery by holding the volume up+home+power, the opposite of download mode, you'll see a list of options in recovery, use volume up/down to move up or down the list, select the factory reset option, press power to confirm, after the reset finishes, select the option to wipe cache partition, after that finishes, reboot the device.

Don't login to your Google account during setup, just bypass all of that, don't open any apps at all. Give it a few minutes to see if it starts the errors again, if it doesn't, go to system settings>accounts and add your Google account to get signed into the device. Once logged in, don't open any apps, give it a few minutes to see if the errors start, if they don't, open the Playstore app, look for app updates, update all listed Google related apps. If it won't update or starts giving errors, you'll have to download updated versions of your Google apps from the internet or from this website if they are linked here, you can also go to apkmirror .com and download them if they have updated versions that work for your device. Make sure you only download apps that are compatible with ARM devices, download them using PC then move them to an sdcard then put the sdcard in the device. Then go to system settings>security, find the "unknown sources" option and enable it, this will allow you to install the updated apps from the sdcard. Then, using your devices file manager, you can go to the sdcard and install the apps from there by tapping on them and selecting install.

If you have difficulty with any of this, we'll take a step back and go one step at a time so I can get a sense of what is going on at each step along the way.

Sent from my LGL84VL using Tapatalk



Great help! Errors all seem to be gone and I have updated most if not all of the google apps. My only issue is that I cannot ring out or use WhatsApp. It’s telling me that my phone is registered to a network? I have tried to do some troubleshooting but still no luck. Not sure how I can get it to recognise my T mobile network, something must have become corrupted.

Thanks [emoji3][emoji106]


Sent from my iPhone using Tapatalk
 

Droidriven

Senior Member
Jan 27, 2014
15,432
10
5,361
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
Great help! Errors all seem to be gone and I have updated most if not all of the google apps. My only issue is that I cannot ring out or use WhatsApp. It’s telling me that my phone is registered to a network? I have tried to do some troubleshooting but still no luck. Not sure how I can get it to recognise my T mobile network, something must have become corrupted.

Thanks [emoji3][emoji106]


Sent from my iPhone using Tapatalk
Check your network settings, you might need to configure your Access Point Name(APN) settings. Find the required APN settings for your carrier and then edit an existing APN profile on your device or create a new set of APNs

Also, try booting to stock recovery and select the option to wipe cache partition, but DO NOT factory reset, then reboot. If it doesn't help, try calling your carriers customer support(I know it's a drag but they may can help). Just tell them that you updated the device and it started network issues.

Sent from my LGL84VL using Tapatalk
 

islandmixed

Senior Member
May 4, 2012
414
22
Check your network settings, you might need to configure your Access Point Name(APN) settings. Find the required APN settings for your carrier and then edit an existing APN profile on your device or create a new set of APNs

Also, try booting to stock recovery and select the option to wipe cache partition, but DO NOT factory reset, then reboot. If it doesn't help, try calling your carriers customer support(I know it's a drag but they may can help). Just tell them that you updated the device and it started network issues.

Sent from my LGL84VL using Tapatalk



Hi, thanks for all your help. I contact my carrier which is T mobile and they told me that my number was axed months ago as T mobile has moved to a new network. But up until I did a factory reset, I could use whatsapp using my old number, although they told me it was cut off back April which is odd! All those contacts that were in my WhatsApp I have probably lost now, as I won’t have my older number. If only I would have known....

Cheers [emoji119][emoji106][emoji106]


Sent from my iPhone using Tapatalk
 
G

GuestD0710

Guest
stuck at boot mtk device

Hey guys I have a mt6735 device which is stuck in boot with orange state your devices has been unlocked and cant be trusted Your device will boot in 5 seconds but keeps on rebooting every 5 sec to same state
Have been googling every possible solution and haven't come up with any
All i did was unlock the bootloader and without rebooting installed twrp since its all been trouble trouble trouble

your help would be greatly appreciated
 

Droidriven

Senior Member
Jan 27, 2014
15,432
10
5,361
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
Hey guys I have a mt6735 device which is stuck in boot with orange state your devices has been unlocked and cant be trusted Your device will boot in 5 seconds but keeps on rebooting every 5 sec to same state
Have been googling every possible solution and haven't come up with any
All i did was unlock the bootloader and without rebooting installed twrp since its all been trouble trouble trouble

your help would be greatly appreciated
Can you get the device to boot into fastboot?

If so, flash your stock firmware.

Sent from my LGL84VL using Tapatalk
 

Droidriven

Senior Member
Jan 27, 2014
15,432
10
5,361
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
I wanna ask one question, I flashed twrp 2.8.6.0 with xzrecovery in my rooted lollipop 5.1.1 z3c
Now if I flash mm 6.0.1, will it be there or just disappear like foam of soap.
You can flash whatever ROM you want, it shouldn't change or remove your TWRP recovery, the only way it would change your recovery is if there is a recovery built into the ROM.

99.5% of the time, ROMs don't have a recovery built in, that is a very rare thing, the only device I've ever flashed that had recovery and ROM compiled together was on my Sprint S2 years ago.

Sent from my LGL84VL using Tapatalk
 
  • Like
Reactions: PioneerSeeker

Brooksey24

Member
Dec 25, 2018
11
1
What device and what issue occured that required flashing the stock firmware. What you did before this might be causing specific issues which are interfering with flashing stock firmware.

Sent from my LGL84VL using Tapatalk

Xiaomi Redmi 5 Plus. I can't remember what exactly caused in to bootloop but it only started once I installed orange recovery and formated data to decrypt it. now no matter what I flash it bootloops. the stock rom can get into the menu but instantly ask for my mi password and i cant connect to wifi at all. On my miui9 rom it says encryption can't be completed and suggects a factory reset yet returning to stock recovery and factory resetting does nothing

Edit: Okay just disabled all ota settings and flashed rom from fastboot mode and now it's loaded into stock recovery saying that this miui version can't be installed on this device (Miui10).
 
Last edited:

Droidriven

Senior Member
Jan 27, 2014
15,432
10
5,361
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
Xiaomi Redmi 5 Plus. I can't remember what exactly caused in to bootloop but it only started once I installed orange recovery and formated data to decrypt it. now no matter what I flash it bootloops. the stock rom can get into the menu but instantly ask for my mi password and i cant connect to wifi at all.
Can you get to fastboot mode? If so, when you're in fastboot and you connect your device to PC, what does it show in device manager? Does it recognize your device correctly or does it say something like "qhus-dload"

I'm not very familiar with Xiaomi devices, but I can still try to help. Once I understand exactly what state your device is in, I'll have a better idea of what kind of information/tools you need.

Sent from my LGL84VL using Tapatalk
 
Last edited:

Brooksey24

Member
Dec 25, 2018
11
1
Can you get to fastboot mode? If so, when you're in fastboot and you connect your device to PC, what does it show in device manager? Does it recognize your device correctly or does it say something like "qhus-dload"

I'm not very familiar with Xiaomi devices, but I can still try to help. Once I understand exactly what state your device is in, I'll have a better idea of what kind of information/tools you need.

Sent from my LGL84VL using Tapatalk

Can't find my device in device manager. Only thing i can find even relatable is the android bootloader interface. In terms of state it's unlocked and i can boot into fastboot, stock recovery and can flash twrp and push files to it to flash. Been using orange recovery
 

Droidriven

Senior Member
Jan 27, 2014
15,432
10
5,361
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
Can't find my device in device manager. Only thing i can find even relatable is the android bootloader interface. In terms of state it's unlocked and i can boot into fastboot, stock recovery and can flash twrp and push files to it to flash. Been using orange recovery

Why orange recovery? TWRP is the best version of custom recovery to use on android devices.

If you're in fastboot when you connect to PC then it's working correctly.

It seems to me that you're having issues with compatibility between orange recovery and the ROMs you're flashing. Is the orange recovery and the ROMs you're trying to flash made for your specific model number? Are you flashing gapps alongvwith the ROM? What size gapps are you using(full, micro, mini, nano, pico)?

When you flash via orange recovery, are you factory resetting and wiping cache after flashing the ROM? If not, that would cause a bootloop.



Sent from my LGL84VL using Tapatalk
 
Last edited:

Brooksey24

Member
Dec 25, 2018
11
1
Why orange recovery? TWRP is the best version of custom recovery to use on android devices.

If you're in fastboot when you connect to PC then it's working correctly.

It seems to me that you're having issues with compatibility between orange recovery and the ROMs you're flashing. Is the orange recovery and the ROMs you're trying to flash made for your specific model number? Are you flashing gapps alongvwith the ROM? What size gapps are you using(full, micro, mini, nano, pico)?

When you flash via orange recovery, are you factory resetting and wiping cache after flashing the ROM? If not, that would cause a bootloop.



Sent from my LGL84VL using Tapatalk

Well somehow trying to flash a miui9 rom has re locked my device. How screwed am I?
 

Droidriven

Senior Member
Jan 27, 2014
15,432
10
5,361
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
Well somehow trying to flash a miui9 rom has re locked my device. How screwed am I?
If you mean it relocked the bootloader, have you tried unlocking it? A locked bootloader would definitely prevent flashing anything custom.

Sometimes, you actually have to corrupt the device in order to force it into qhus-dload mode, then unbrick it from there. But I wouldn't try that until all other possibilities are exhausted.



Sent from my LGL84VL using Tapatalk
 
Last edited:

Brooksey24

Member
Dec 25, 2018
11
1
If you mean it relocked the bootloader, have you tried unlocking it? A locked bootloader would definitely prevent flashing anything custom.

Sometimes, you actually have to corrupt the device in order to force it into qhus-dload mode, then unbrick it from there. But I wouldn't try that until all other possibilities are exhausted.



Sent from my LGL84VL using Tapatalk

unlock oem/flashing unlock both failed so i think deepflash/testpoint is my next option? no other way of unlocking the bootloader. I think it's because i unbound the phone from my mi account yesterday, that was dumb
 
Last edited:

Droidriven

Senior Member
Jan 27, 2014
15,432
10
5,361
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt

Brooksey24

Member
Dec 25, 2018
11
1
Yeah, see if any of these instructions get you anywhere.

https://xiaomifirmware.com/guides-and-tips/how-to-restore-redmi-5-plus-and-fix-bootloop/

Sent from my LGL84VL using Tapatalk

Okay i just used the testpoint flash method and got the flash to go through with the official redmi 5 plus fastboot rom on their website, yet it bootloops into recovery mode and still shows the error message "this miui version can't be installed on this device". What is going on?!

Edit: One guy says it's only going to boot if you have the original 9.5.3.0 miui fastboot version yet all websites have the link coming soon. Guess i have to wait before trying the next method?
 
Last edited:

Droidriven

Senior Member
Jan 27, 2014
15,432
10
5,361
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
Okay i just used the testpoint flash method and got the flash to go through with the official redmi 5 plus fastboot rom on their website, yet it bootloops into recovery mode and still shows the error message "this miui version can't be installed on this device". What is going on?!

Edit: One guy says it's only going to boot if you have the original 9.5.3.0 miui fastboot version yet all websites have the link coming soon. Guess i have to wait before trying the next method?
I think you need to find some active members in the Redmi 5 plus forum, they are more familiar with your device. You've got some device specific issues and this is a "general" bootloop guide. You're going to need some device specific guidance from members experienced with that device.

Sent from my LGL84VL using Tapatalk
 

Top Liked Posts

  • There are no posts matching your filters.
  • 48
    RECOVERY FROM BOOT LOOP/BRICK​

    Most people use the term "bricked" improperly. A bricked phone means one thing: your phone won't turn on in any way, shape or form, and there's Probably nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they're a lot more common than a truly bricked phone. If your phone is actually bricked, you Probably won't be able to fix it yourself.
    BOOTLOOP GUIDE
    (#:1)
    Start by removing the device's battery and wait for a few minute's before putting it back in your phone.
    OR Switch off for non-removable battery phones for five to ten minutes so it can remove any charge that is left in the phone and to initiate a complete power-cycle once you insert the battery.
    Now Boot the device into Recovery Mode by pressing and holding the relevant shortcut keys for your device. For instance, most Samsung devices can boot into Recovery Mode while pressing the key combination Volume Up, Home and Power (for tablets it is Volume Up and Power). If using a HTC phone, boot into HBOOT first by tapping Volume Down and Power button together and then browse to Recovery using Volume Up/ Down buttons. If you cant get it to boot in Recovery you can always use (ADB) and type in the command] > adb reboot recovery <--- Hit Enter now your Device will reboot into recovery mode. If your not familar with adb or even know what adb is there is a link on the bottom of this page for the sdk download and a gude on the adb.

    (#:2)
    Now browse and select the option Wipe Data/Factory Reset in Recovery Mode.Check if the device can now boot into the newly installed ROM or firmware. If not, then perform Wipe Cache Partition And Return to the main Recovery menu and reboot the device by choosing Reboot System Now option.After Flashing or Installing a New ROM and If the device is already rooted with ClockworkMod Recovery (CWM) installed, then do the following steps (1) Remove you'r battery and reinsert it after 30 seconds. (2) Boot the device into CWM Recovery by pressing and holding Volume Up, Home and Power buttons together. NOTE: The key combination may vary depending on your device model.So, CONFIRM BEFORE YOU PROCEED. (3) Now Go to Advanced option in Recovery menu and choose Wipe Dalvik Cache. Then perform Wipe/cache under Mounts & Storage. Reboot the device and check if the boot loop issue is resolved. If not repeat the above three steps, but perform both Wipe/data and Wipe/cache under Mounts & Storage before rebooting.

    (#:3)
    After Setting an Incorrect File Permission.The Android operating system (OS) works on file permissions and hence incorrectly set file permissions may permanently damage or soft brick your device. Here are some of the commonly used file permissions:- 644 (RW-R-R) - (this is most common system permission, it exists in /system/app, /system/framework, /system/etc, /system/lib and allot of separate files) - 755 (RWX-RX-RX) - (mainly used for /system/bin) - 777 (RWX-RWX-RWX) - (used for scripts inside /system/etc/init.d and busybox files)
    To fix or reset any of these file permissions, do the following:Boot the device into CWM or TWRP recovery Go to Advanced option.Click Fix Permission and confirm the action. After Restoring a Backup.If the bootloop error occurs immediately after restoring a Nandroid Backup, follow the steps on -(#:2)- to fix it. If everything else fails, just try re installing the original ROM or flash the first official firmware.

    Using ADB BY Samantha
    DB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the manufacturer logo. (In new CWM versions it’s possible to use adb)
    The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is different from every device, but normally it’s after the manufacturer logo that the partitions get mounted. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible.

    I use this script for example, called ondemand.bat (requires adb.exe and the 2 dlls)


    1 @ECHO off
    2 cd /d %~dp0
    3 echo.
    4 echo Waiting for device…
    5 adb wait-for-device
    6 echo.
    7 adb -d shell stop
    8 adb push mycwmfix.zip /sdcard/mycwmfix.zip
    9 adb reboot recovery


    Linux Version (ondemand.sh):


    1 #!/system/bin/sh
    2 echo " "
    3 echo "Wating for device..."
    4 ./adb wait-for-device
    5 echo " "
    6 ./adb -d shell stop
    7 ./adb push mycwmfix.zip /sdcard/mycwmfix.zip
    8 ./adb reboot recovery

    This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push the specified cwmfix zip to your sdcard, and after that it will reboot in recovery so you can install the cwm fix you made. You can also make an batch script that pushes the files automatically to your phone, here is an example:


    (1 @ECHO off
    (2)cd /d %~dp0
    (3)echo.
    (4)echo Waiting for device...adb wait-for-device
    (5)echo.
    (6)adb -d shell stop
    (7)adb -d shell su -c "mount -o remount rw /system"
    (8)adb push framework-res.apk /system/framework/framework-res.apk
    (9)adb -d shell chmod 644 /system/framework/framework-res.apk
    (10)adb push SystemUI.apk /system/app/SystemUI.apk
    (11)adb -d shell chmod 644 /system/app/SystemUI.apk
    (12)adb reboot

    (13)Linux version:

    1#!/system/bin/sh
    2echo " "
    3echo "Waiting for device..."
    4./adb wait-for-device
    5echo " "
    6./adb -d shell stop
    7./adb -d shell su -c "mount -o remount rw /system"
    8./adb push framework-res.apk /system/framework/framework-res.apk
    9./adb -d shell chmod 644 /system/framework/framework-res.apk
    10./adb push SystemUI.apk /system/app/SystemUI.apk
    11./adb -d shell chmod 644 /system/app/SystemUI.apk
    12./adb reboot
    This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push framework-res.apk and SystemUI.apk to the directory it belongs to, after that it changes the permissions of the files to RW-R-R (644) and then it will reboot.

    Please note that on some devices the command “su -c” cannot be used after using the “stop” command, it gives an error then (Segmentation Fault).
    What you can do to prevent this is adding “adb remount” just under the “adb wait-for-device” line, and remove the “adb -d shell su -c “mount -o remount rw /system” line.
    Save the script and run it again.



    For HTC Phones: HTC phones can flash stock ROMs, known as RUUs, right from the phone's bootloader. You'll need to Google around for your device's specific RUU file, but once you download it, save the ZIP file to your SD card, and rename it (to something like PG05IMG.zip—the download page for the RUU file should specify which filename is required), booting up your phone should automatically flash the stock ROM from HBOOT, HTC's bootloader. Video http://www.youtube.com/watch?feature=player_embedded&v=tE8BiIFUOpk

    For Samsung Phones If you're using a Samsung Galaxy phone, you can use a tool called Odin to reflash an OPS file, which is a stock ROM that will return your phone to factory settings. You'll need a Windows machine and a copy of Odin, which you can find by Googling around the net (as its not an official tool) check out The Unlockr's guide to using Odin to familiarize yourself. You may need to Google around for your specific device's OPS file and instructions.
    Video http://www.youtube.com/watch?feature=player_embedded&v=5s70dwNgdD8

    Verizon Galaxy S3 Bootloop fix using Odin

    The Verizon Galaxy S3 has to be the most problematic variant of the Galaxy S3. If the locked bootloader on it wasn’t enough, many users have seen their Verizon Galaxy S3 get bricked and stop booting after trying to flash a custom ROM.​

    To start off there will be a little bit of downloading:p

    Samsung USB Driver V1.5.14.0 For Android Mobile Devices

    ODIN

    VRALEC.bootchain.tar.md5

    BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5

    stock.vzw_root66.

    Now lets Start
    Make sure phone is off. Boot into download mode. To do so, hold down the Volume Down, Home and then the Power buttons together until a Warning!! message is displayed on the screen. Here, press Volume Up to enter download mode. A green Android and the text Downloading will be displayed on the screen.
    Now, open Odin by clicking on the Odin3 v3.07.exe file in the Odin307 folder which you obtained after extracting Odin307.zip
    In Odin, click on the PDA button, then select the VRALEC.bootchain.tar.md5 file that you downloaded.
    Important Untick every option under the “Option” section (on the top left of Odin), except F. Reset Time. Check the screenshot below for reference.
    unbrick-vzw-s3-ss-11-700x517.jpg


    Then, connect the phone to the computer with the USB cable and wait for Windows to finish installing drivers. Odin will say Added!! in the message box on the bottom left if the phone is detected successfully. If not, make sure the drivers are installed and also try using a different USB port – preferably a USB port on the back if using a desktop computer.
    Click on Start to start flashing the VRALEC.bootchain.tar.md5 file on the phone.
    Wait till flashing is complete and you get a PASS message in Odin. When that happens, disconnect the phone from the computer, but DON’T turn it off and let it stay in download mode. Also close Odin.
    Reconnect your phone to the computer (while it is in download mode). Open Odin again.
    This time, click the PDA button and select the BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar.md5 file that you download
    Also, again untick every option except F. Reset Time in Odin. Then, click on the Start button to start flashing the BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar.md5 file on the phone.
    When flashing is complete and you get a PASS message, disconnect the phone and close Odin. But keep the phone in download mode, don’t turn it off.
    Open Odin again and also reconnect the phone to the computer.
    Click the PDA file and select the stock.vzw_root66.tar file that you Downloaded
    [Important] Select the following three options in Odin on the top left: Auto Reboot, F. Reset Time, Nand Erase All. Check the screenshot below for reference.
    unbrick-vzw-s3-ss-2-700x515.jpg


    Click Start to start the flashing process. Once the flashing is complete and you get a PASS message, the phone will automatically reboot. Disconnect the phone from the computer.
    The phone will still not boot up completely. Now, remove the battery on the phone, then re-insert it. Don’t turn it on.
    Now, boot into recovery. To do so, press and hold the Volume Up + Home + Power buttons together till the screen turns on, then let the buttons go. The phone will boot into recovery in a few seconds. You will see a few error messages in recovery, which is normal.
    In recovery, use the volume buttons to scroll up/down and the home button to select options.
    Select wipe data/factory reset, then select Yes on next screen to confirm. Wait a while till the data wipe is complete (this will NOT delete your personal files on the SD cards).
    Select wipe cache, confirm, then wait for cache wipe to be completed.
    Then, select reboot system now to reboot the phone.
    The phone will now boot up properly into Android and is fixed, and you will be able to use it now.

    Your Verizon Galaxy S3 is now fixed, and saved you from sending it in for repair to Verizon. Do let me know how the procedure works!


    HOW TO UNBRICK YOUR DEVICE​

    REQUIREMENTS TO UNBRICK YOUR PHONE

    First install java on your pc if you haven’t java go to Java site and install it.
    download one-click Unbrick tool
    window users will need .rar/.zip extractor software , you can download free all in one 7zip extractor form here.

    FOLLOW THESE INSTRUCTIONS CAREFULLY

    1. Right-click on the One-Click.jar file, move down to option “7-zip” and then select “Extract to OneClick”.

    2. Now you will get a ‘OneClick’ folder.

    3. Now copy ‘OneClick.jar’ file and paste it into the ‘OneClickheimdalloneclickresourcesHeimdallPackage’ folder.

    4. Right-click on ‘oneclickloader.exe’ file and choose ‘Run as Administrator’.
    5. Proceed with the installation of Heimdall.

    6. After the installation is complete, you will see the the One-Click UnBrick interface.
    OneClick.jpg

    Connect the phone to computer via USB and click on “unsoft brick” button to recover your bricked android phone.







    Factory Rom's


    Factory Images for Nexus Devices
    https://developers.google.com

    SAMMOBILE
    http://www.sammobile.com/

    ROM DOWNLOADS FOR HTC
    http://www.htc.com/us/support/rom-downloads.html

    HTC UNLOCK BOOTLOADER
    https://www.htcdev.com/

    Motorola
    https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth

    UNLOCK YOUR Motorola BOOTLOADER
    https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth

    RE-LOCK YOUR Motorola BOOTLOADER AND FACTORY IMAGES FOR DEVELOPER EDITION DEVICES
    https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images

    Moto Support
    https://motorola-global-portal.custhelp.com/app/home/

    LG Software & tools Download
    http://www.mylgphones.com/lg-software-tools-download

    CLOCKWORKMOD RECOVERY & ROMS Phone Selection
    http://www.clockworkmod.com/rommanager

    TeamWin - TWRP
    https://twrp.me/

    ANDROID SDK
    http://developer.android.com/sdk/index.html

    ADB GUIDE
    http://developer.android.com/tools/help/adb.html
    3
    Good job mate! I will be adding this to my help thread soon! :good:

    Thank You :) Just updated
    2
    You sir, are a lifesaver. I downloaded the oldest stock firmware possible in samobile and flashed it and finally worked. It was on the samsung logo again but after a few minutes it finally made it through. I actually didn't think I would be able to fix it since most people gave up doing the same thing as me. Again, many thanks.
    :highfive:
    Now update it with the newest stock firmware

    Sent from my SCH-I535 using Tapatalk
    2
    Lost Data Karbonn Titanium S9 Recovery
    Karbonn Titanium S9 is an amazing gift of technology using which you can do lot more than just communicating. This Smartphone is developed on most popular and used operating system i.e. Android and built-in with fantastic features, which keeps you busy enjoying all time. But Karbonn Titanium S9 too has sinister sides as one might lose data from it due to some uncontrollable reasons. Since it’s not just a normal phone, it might contain large amount of your valuable data such as images, audios, videos, games, applications, documents, etc., and losing one of it might create panic. Relax..! Need not to panic, since Karbonn Titanium S9 recovery is possible with trustworthy recovery software.

    It’s pretty common to suffer data loss from Smartphones, since it is an entirely unpredictable scenario. But one should also know about its causes so that he / she might avoid it in possible circumstance. Just go through the below section to know more about these scenarios:

    Use of factory restore / reset option accidentally might invite the data loss
    When SD card or any other memory card mounted on S9 phone gets corrupt or become inaccessible
    Severe infection of spyware, malware and virus may lead to data loss
    Abrupt switching off the Karbonn Titanium S9 numerous times might make few files go missing
    Unintentional formatting, deleting of data by wrong touch
    Unwanted changes after rooting Karbonn Titanium S9 may contribute to data crisis

    What to? What not to?

    Data recovery experts recommend you some tips and advice you certain things to stay away from in order to perform complete recovery of Karbonn Titanium S9 data. First let’s see what to do, when you come across data loss on your Karbonn Titanium S9.

    Keep backup of the data and files that are important to you, so as to avert data disasters
    Immediately discontinue the use of Karbonn Titanium S9 as soon as you come across data loss
    Opt of reliable and safe recovery tool without wasting much of the time

    Here are some things, which you need to avoid after facing loss of data:-

    Do not even attempt tasks like rooting, formatting, etc., until you know the complete process
    Do not add or edit data on your Karbonn Titanium S9 Smartphone
    Do not carry out task like updating the software or version of phone

    Well by following these tips you can avert data overwriting and increase the chances of safe and complete Karbonn Titanium S9 data recovery.

    What’s next?

    Next is Remo Recover..! Yes, it is a smart tool that is designed for Smartphone data recovery using which you can effectively recover Karbonn Titanium S9 data in few simple clicks on mouse button. Software is ahead of its competition as it is integrated with hi-tech data retrieval procedures and assists you to restore Karbonn Titanium S9 data from all severe data crisis. Remo Recover is pre-scanned for faulty and dangerous items and certified as absolutely safe and reliable to use.

    Few striking attributes of Remo Recover..!

    Makes an entire scan of both internal and external memory of phone and help you to retrieve lost data from Karbonn Titanium S9
    Trouble free and easy to understand GUI helps a novice to execute Karbonn Titanium S9 recovery on its own
    Its smart searching algorithms examines complete drive in just one scan
    Tool has the caliber of recognizing Android application files with (.apk) and recovering it along with photo, video and audio file formats
    Authorize you to sort recovered data after completion of lost data recovery from Karbonn Titanium S9
    Prior look of recovered files can be seen using “preview” option.
    You can perform lost data Karbonn Titanium S9 recovery on all types of Android version and from all Windows OS based computers

    Step 1: Connect your Karbonn Titanium S9 to Windows computer using a USB cable and wait until connection gets established.
    android-device-detected.jpg


    Figure A: Detecting Device

    Step 2: Now Main screen gets open from were you can select either “Recover Deleted Files” or “Recover Lost Files” option as per your requirement.
    remorecover-android-main-screen.jpg


    Figure B: Main Screen

    Step 3: Select Karbonn Titanium S9 drive and click “Next” button for software to begin scanning process.
    http://www.remorecover.com/images/android/remorecover-android-select-physical-drive.jpg

    Figure C: Select Karbonn Titanium S9 Drive

    Step 4: Once Remo Recover completes the scanning process you can view list of recovered data/files in two types of view which are “File Type View” and “Data View”
    remorecover-android-file-type-view.jpg


    Figure D: List of Recovered Data

    Step 5: You can preview recovered data using Preview option and save it to any location.
    remorecover-android-preview-recovered-file.jpg


    Figure E: Preview Recovered Data

    DOWNLOAD LINK http://www.remorecover.com/download/remorecover-android.exe
    2
    I'll just leave this here:


    5. Create a thread or post a message only once.

    As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer. (Also refer to Rule 16)

    Cheers

    Magnum_Enforcer
    FSM