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
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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
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.
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
Good job mate! I will be adding this to my help thread soon! :good:
immortalneo said:
Good job mate! I will be adding this to my help thread soon! :good:
Click to expand...
Click to collapse
Thank You Just updated
Help Please
I have a VIZIO VTAB1008 that is not turning on. when i plug it in the screen stays off and only the soft keys blink. i cant get into recovery and have no idea what to do.
Dose anyone know how to correct this problem?
or any programs that can help me recover it from a usb?
i am using windows 7 ulmimate 32-bit
DustinGrinder said:
I have a VIZIO VTAB1008 that is not turning on. when i plug it in the screen stays off and only the soft keys blink. i cant get into recovery and have no idea what to do.
Dose anyone know how to correct this problem?
or any programs that can help me recover it from a usb?
i am using windows 7 ulmimate 32-bit
Click to expand...
Click to collapse
How long have you had it? Is it rooted? And What happed before this happed?
You Can Try This
1. Before starting, make sure that the tablet is powered off. Not just in sleep mode. Now press & hold both the UP and DOWN volume buttons at the same time. You may find it easier to hold the tablet in the landscape position on a table or on your lap while you hold down both buttons.
2. Next press and hold the power button until the tablet buttons light up. It will take a minute to happen, but when they do immediately let go of the power button ONLY. Keep holding down both the UP and DOWN volume buttons. You only have a second to do this other wise the tablet will continue boot up as normal and you will have to start again from step one.
3. After a bit of holding down both volume keys the screen will show the Vizio logo. Then the logo will change to a TRIANGLE with an exclamation mark.
4. Now you can let go of the volume buttons.
5. Tap the home button to pop up the boot recovery menu. Follow the instructions to reset your tablet. Pressing the up/down volume buttons allow you to scroll up and down the list. A quick press on the power button will accept your selection.
6. Wait for the tablet to come up.
good luck. and post results
soft brick
keifus.rahn said:
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
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.
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.
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.
Connect the phone to computer via USB and click on “unsoft brick” button to recover your bricked android phone.
DOWNLOAD LINKS
CLOCKWORKMOD RECOVERY & ROMS Phone Selection
http://www.clockworkmod.com/rommanager
ANDROID SDK
http://developer.android.com/sdk/index.html
ADB GUIDE
http://developer.android.com/tools/help/adb.html
CLOCKWORKMOD-HELIUM
http://http://www.clockworkmod.com/carbon
Click to expand...
Click to collapse
For samsung do you have to use the stock rom or after wipe can use a custom? I'm in a soft loop after rooting and then I forgot something and did a twrp restore after wipe. I really want to use jedi now but it seems like I hv to use stock rom n then re root ?
Cannot go into download mode or fastboot mode No access to recovery
I'm using Karbonn titanium s9 and had just caused bootlooop problem in my phone as i was attempting to intsall a custom rom..
I have no access to the recovery , my phone just go to the comapany logo and then reboot ...
plzzz tell me how to flash a fresh custom rom into it using computer....
please mention all keys for differnt modes..
Thanks in advance and wanted help as soon as possible becuase i have brought phone 5 days before a biricked it...
THanks.....☺
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.
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.
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”
Figure D: List of Recovered Data
Step 5: You can preview recovered data using Preview option and save it to any location.
Figure E: Preview Recovered Data
DOWNLOAD LINK http://www.remorecover.com/download/remorecover-android.exe
My phone is stuck in a boot loop after trying to update it. I only just bought it and cache wipes, factory reset don't work. For some reason it won't connect to the computer or kies even after reinstalling drivers and using multiple different usb ports. It was working fun before I updated it. Anyone have any ideas? I'm pretty desperate right now
help! for flashing ROM from similar device
hi @keifus.rahn,
I have got an MTK6589 16gb rom 1 gb ram 5.5 inch HD display karbonn s9 device. I have found that it is similar to star 7599 and alps n9202 in configuration. Problem is that I have bricked my phone 1 month earlier and since then have been trying to flash ROMS from devices like mentioned above.There is no official firmware for the device till now.Every time SP flash tool returns error and does not flash.
Is there any way I can alter these roms from other similar devices to make it flashable through SPTool on my device (example, like using similar kernel etc.).Porting would not help me as the phone is bricked.
Please help me as I could not get any help from anyone.I would be very grateful to you.
Other option
This thread was really helpful. I updated my ROM, running legacy AOSPA on Xperia S. Last update had me stuck on the manufacturer logo and I couldn't roll back to the previous ROM, CM wouldn't let me install older software. I tried the steps but it didn't work for me, finally decided to wipe system as a result and reinstall everything. This got it to work. I suppose my point is that sometimes it's best to format/wipe the system.
Master Limbe said:
This thread was really helpful. I updated my ROM, running legacy AOSPA on Xperia S. Last update had me stuck on the manufacturer logo and I couldn't roll back to the previous ROM, CM wouldn't let me install older software. I tried the steps but it didn't work for me, finally decided to wipe system as a result and reinstall everything. This got it to work. I suppose my point is that sometimes it's best to format/wipe the system.
Click to expand...
Click to collapse
I'm glad to hear that this thread helped you out. I do a full wipe every time i flash a new Rom and always remember to make a backup
Bootloop after repartition
I've a rooted ZTE V972M. I tried to increase internal storage following instructions in
"Re-Partition any MTK6589 Phone, Without A PC! (More /Data Storage!)"
When I reboot my phone, it stucks at logo screen.
What I've done trying to fix it:
1. Enter the recovery mode; it's a stock recovery (Android system recovery <3e>); wipe data/factory reset, wipe cache partition.
Result: still stuck at logo when rebooting.
2. Flash a stock ROM in recovery mode.
Result: Update aborted. In the log file, it says "failed to mount /cache (No such file or directory)" detailed in attached file. The stock rom I used is for ZTE LEO S1, while my phone is DTAC LION HD which is a house brand of my phone carrier. So, there may be also a problem of ROM signing.
3. I cannot use ADB or Fastboot because I didn't enable USB debugging (My phone's OS is android 4.2).
Please guide me to fix this problem.
Hi, sorry for reviving this topic, but I'm stuck in a bootloop on my Galaxy Note 10.1 2014 edition (SM-P605).
The problem is that the battery of my Note is built-in and can't be removed without some serious hardware modifications.
Also, when I try to shut it down (hold the Power button), it starts up on its own immediately afterwards...
And its battery is not going to run out soon at this pace. Anything I could do?
Need Help. 100% dont know what to do..
keifus.rahn said:
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
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.
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.
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.
Connect the phone to computer via USB and click on “unsoft brick” button to recover your bricked android phone.
DOWNLOAD LINKS
CLOCKWORKMOD RECOVERY & ROMS Phone Selection
http://www.clockworkmod.com/rommanager
ANDROID SDK
http://developer.android.com/sdk/index.html
ADB GUIDE
http://developer.android.com/tools/help/adb.html
CLOCKWORKMOD-HELIUM
http://http://www.clockworkmod.com/carbon
Click to expand...
Click to collapse
Hello SIr, please help me with my Android Phone, its brand is not familliar to you.. but here it is.
Myphone Agua Hail
the problem is that, after I rooted my device is that, I cannot do Factory Reset anymore. And when I try to do the ff.
1. recovery mode, I cannot do recovery mode too,
What I do is, hold "down volume" and then click "power button" Together. Even I tested the volume up, and Vice Versa.. All that I research about recovery mode, is I'eve done, but none has work, Even the Boot Loop you teach others, I do that too, But it only open Normally and there is a Name that is SAFEMODE, SouthWest of the screen.
Please help me fix my beloved only One phone.
Summary of Problems:
Cannot get to Recovery mode with every reason. \\\\\ A T R O T N
Cannot do Factory Reset. ///// F E R O I G[/SIZE]
im new and have absolutely no clue how to use this site,lol sorry
okay im using lg optimus f6..i noob rooted it :/(rooted with out backing anything up) ive heard of hard bricks where the phone wont turn on,soft bricks where it gets stuck in boot loop or recovery mode..my problem is i installed a font that put me into boot loop,i master reset the phone and IT WORKED turned back on perfectly,until the screen went to sleep :| every time the screen turns off it boot loops..now since i can turn it on i know theres got to be a way to fix it please help someone
i have s2 gt-i9100g i am running on cm11 nightlies i tried flashing blazing kernel v7 when i reboot it says that i may have lost root access so i pressed to fix but it boots into recovery over and over please i need help
Poet432012 said:
okay im using lg optimus f6..i noob rooted it :/(rooted with out backing anything up) ive heard of hard bricks where the phone wont turn on,soft bricks where it gets stuck in boot loop or recovery mode..my problem is i installed a font that put me into boot loop,i master reset the phone and IT WORKED turned back on perfectly,until the screen went to sleep :| every time the screen turns off it boot loops..now since i can turn it on i know theres got to be a way to fix it please help someone
Click to expand...
Click to collapse
Can you list the fonts of your device? As your device is already rooted, go to /system/fonts folder and see if any system font is missing.
I am using Spice Mi-504 (MT6572) at present.
Thanks very much
Bootloop - looking for much needed help
keifus.rahn said:
I'm glad to hear that this thread helped you out. I do a full wipe every time i flash a new Rom and always remember to make a backup
Click to expand...
Click to collapse
Please help. I find your site and this noob's thread is so informative but I couldn't find a way to fix my boot loop. The XDA is full of dev tech jargon, and felt exhausted that I seek help finally here.
My xperia tab z (sgp321 with LTE+WIFI, European version) got into bootloop after flashing CWM 6.0.3.2 (TabZ_DooMLoRD_AdvStkKernel_FW-253-v01.img). The flashing went fine I was able to boot into recovery mode and made a backup. But after the backup is over, and rebooting it prompted Reboot > root access is missing. Root? I selected 'YES' thinking I could root the device. Then bootloop started. I followed all the steps in your thread, Factory reset, Wipe cache, Delvik cache, fix permission etc but still into bootloop.
The device is boot-loader unlocked. It was running KK 4.4.2. Not rooted. I have CM-11-20140723-Nightly-pollux.zip in the external SD card of which I was planning to flash using CWM recovery.
1. What options remain for me to get the device back into original state ? back into 4.4.2.
2. I was able to pass ADB calls. But now since into bootloop, how can I make fastboot/ADB calls to device consistently to do anything realted to reset, recover?
3. In addition to ADB/fastboot, I have Flashtool 0.9.16 by Androxyde with SGP321_10.4.1.B.0.101_CE.ftf stock firmware. Can I flash this Stock ROM while in bootloop ? How can flashtool help in this situation ?
4. The Tablet Z battery is built-in. Does it charge while in bootloop? How can I power-down/shutdown the device without restarting using CWM (it has only reboot option), so that I could fully charge the device ?
Any helpful advise is very much appreciated.
Thank you very much for great work you are doing and the very purpose for XDA - Knowledge Sharing.
---------- Post added at 11:04 AM ---------- Previous post was at 10:41 AM ----------
Master Limbe said:
This thread was really helpful. I updated my ROM, running legacy AOSPA on Xperia S. Last update had me stuck on the manufacturer logo and I couldn't roll back to the previous ROM, CM wouldn't let me install older software. I tried the steps but it didn't work for me, finally decided to wipe system as a result and reinstall everything. This got it to work. I suppose my point is that sometimes it's best to format/wipe the system.
Click to expand...
Click to collapse
Please, can you tell me what steps you made during recovery? My xperia tab z SGP321 (LTE+WIFI European version) is now into bootloop; it was unlocked but not rooted, has CWM 6.0.3.2 and I can boot into recovery mode. Please tell me where to start from ? Can I make ADB/fastboot calls without resolving bootloop or can I flash any stock ROMs using flash tool still with bootloop issue unfixed ? How Can I get the device back into work ?
Much appreciate your help. I have posted details in the same thread.
Thank you.
This is now DEPRECATED and NOT SUPPORTED ANYMORE since there is an easier method to do it! Links won't get updated! You can still use the written info!
If you want rooted kitkat head to my friend's thread @maxx_hr (THANK YOU FOR ALL YOUR WORK!) HERE: http://forum.xda-developers.com/optimus-l3-l5-l7-l9-ii/development/kk-kk-kdz-p710-root-t2950532
Hello to you all!Warning:
Code:
[COLOR="Red"][SIZE="4"]Your warranty is now void. I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about all contained in this tutorial
before you follow it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
But since i'm a nice dude i will try to guide you anyway:)[/SIZE][/COLOR]
In this tutorial we will learn how to:
- achieve root on our L7 II (Both single and dual-sim, so P715/P710 and all the derivated phones from them) by LG running a Custom Rom or Stock KK Rom.
FOR THIS FOLLOW ALL STEPS.
- unbrick/flash to a specific firmware using Lg Flash Tool (In this tutorial there are only 2 KDZ files stock JB for P710 and P715. If you want to recover from a brick or want a different KDZ file you can find them over here: http://lg-phone-firmware.com/)
FOR THIS FOLLOW STEP 1 AND STEP 2 (install all drivers including adb and download the files that are needed at Step 2).
- flash with CWM (There are 3 methods I describe. Use the one that suits you the best. You can flash any *.zip that is suitable for your device.)
FOR THIS FOLLOW STEP 5.
Save your data you need, you will lose all data so backup with Titanium Backup or a program you like the info you need.
ALL DOWNLOADS ARE AT THE BOTTOM OF THE POST!
This tutorial will be split in steps as the following:
1. Preparing the Windows machine with the right drivers and software.
2. Reverting back to Jellybean Stock Rom.
3. Rooting on Stock Rom (Jellybean).
4. Installing Unlocked Bootloader and ClockWorkMod Recovery (CWM).
5. Flashing KitKat or a Custom Rom through CWM.
6. Flashing Root through CWM.
So let's start the job.
1. Preparing the Windows machine with the right drivers and software.
Uninstall everything related to LG from Control Panel (Drivers, PC Sync etc).
Restart your PC.
Download and unrar the archive "LG Drivers.rar".
Install both files inside and restart your computer.
Download "adb-setup-1.4.2.exe" and install it (answers should be y y y and install the drivers when prompted).
Download "Framaroot-1.9.1.apk".
Download "LG Flash Tool 2014.rar".
Download "Free LG P710.rar"
Download "P710 Stock KK.zip". -> Stock KK image with Stock KK kernel in it made from the original V20 KDZ (Open Europe).
Download SuperSU
*Download "P715 Stock KK.zip" and "LG P715 (JellyBean).kdz" if you are running a dual-sim version of the phone.
*Download all the files you need!
From now on I will consider you have this files and I will just call their names when to use them.
2. Reverting back to Jellybean Stock Rom.
Open the back cover of your phone and pull the battery out. Wait about 10 seconds. Put the battery back in.
While HOLDING (keep pressed) the VOLUME DOWN BUTTON insert the USB Cable in the phone (you need to have your USB cable inserted in an USB 2 port from the back of your PC).
When you see the yellow screen with emergency mode stop pressing the button.
Unplug the USB from the phone and then plug it in again.
Unrar "LG Flash Tool 2014.rar" and open "LGFlashTool2014.exe" with right-click Run As Admin.
*If you cannot open this program you need to install "VC_RedistInstaller.exe". You are missing some libraries of visual C++*
*IF YOU HAVE ANOTHER PHONE (another LG or P715) DO THE SAME INSTRUCTION AND REPLACE JUST THE KDZ FILE ON "Select KDZ File" TO THE ONE YOU DOWNLOADED AND IS SUITABLE FOR YOUR OWN DEVICE.
Move PhoneMode from DIAG to EMERGENCY. Select KDZ File: you have a file called "V10J_00.kdz" in the same folder as the tool. Select that. Press CSE Flash (CAUTION!!! This will reflash the phone and YOU WILL LOSE ALL YOUR DATA SO BE WARNED).
Another screen will open and press START.
Another screen will open once again press OK.
At a point you will get an error like "Offline BLA BLA". DON'T DO ANYTHING DO NOT PRESS OK.
Wait until your phone reboots and then you can close this tool.
Remove USB cable.
IMPORTANT STEP:
Pull out the battery. Wait 10 seconds put it back. While holding VOLUME DOWN + HOME BUTTON press POWER BUTTON. Wait until you see LG logo and stop pressing POWER. Keep pressing the other 2 until you see android robot doing things. Wait until the phone boots.
CONGRATZ you are on JELLYBEAN (Or the KDZ you chose).
3. Rooting on Stock Rom (Jellybean).
When you see the welcome screen just fast forward everything.
Go to system settings->security->tick Unknown sources->OK.
Go to system settings->developer options->OK->tick USB debugging->YES.
With an SD card reader or with your USB connected as Media Sync (MTP) copy the "Framaroot-1.9.1.apk" to your SD Card.
Using the phone's FILE MANAGER go to external_SD and click the Framaroot you just copied. Run it using Package Installer Just Once and Install.
When finished press OPEN. At the first choice choose Install SuperSU and then press on "Gandalf". You will get Success. Press OK and reboot.
You will see SuperSU in you apps.
YAY! IT'S DONE.
4. Installing Unlocked Bootloader and ClockWorkMod Recovery (CWM).
*SAME FILE YOU NEED FOR LG P715
Earlier you have download "Free LG P710.rar" and in the first step you installed ADB. We will use that now.
Unrar the "Free LG P710.rar" and place the 2 files ON THE ROOT (only on root) of the SD card using device mounted in MTP mode or SD card reader. Put back the card if you use the second option.
WARNING!!!
This can mess up you device so just do what i say step by step!
Plug the USB Cable in the Phone once again and use MTP connection mode.
Click Start+R type CMD and press ENTER.
Run the Following with copy paste to CMD.
Code:
adb devices
You will see your device.
*IF YOU CANNOT MAKE YOUR DEVICE BE RECOGNIZED IN "adb devices" do this:
Install this: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=ro
Open terminal and continue with the steps down below.
Code:
adb shell
You will see something ending with $.
Code:
su
Unlock the dvice if it is locked and your phone will ask for superuser permission press GRANT.
Code:
dd if=/storage/external_SD/APPSSBL.bin of=/dev/block/mmcblk0p5
This will copy the unlocked bootloader to the bootloader partition.
Code:
dd if=/storage/external_SD/recovery.img of=/dev/block/mmcblk0p17
This will copy the CWM to recovery partition.
Code:
reboot recovery
This will reboot your phone in CWM if you followed all steps correctly.
GREAT SUCCES we have an unlocked bootloader and CWM.
Close your CMD.
Unplug USB.
5. Flashing KitKat or a Custom Rom through CWM.
*IF YOU WANT TO FLASH ANOTHER ZIP FILE OR YOU ARE ON P715 JUST USE THE ARCHIVE YOU NEED AS REFERENCE, NOT "P710 Stock KK.zip". CHOOSE THE FILE THAT IS MOST SUITABLE OR YOU THINK IT'S BEST FOR YOU
I made "P710 Stock KK.zip" you downloaded. This is the stock image for KK Open Europe. Here you can either flash mine or search for a Custom Rom for your device. Either way you will follow the exact same steps but with a different archive. I will take for reference the "P710 Stock KK.zip".
Plug USB in.
You Navigate using Volume Up Button (UP) and Volume Down Button (DOWN). The Power Button is OK.
Do this:
- Go to "wipe data/factory reset" and OK. Go to YES then OK. Wait until done.
- Go to "mounts and storage" and do the following: "format /cache" and "format /system" everytime with YES as second option. Press "go back" once.
- Go to "advance" and then "wipe dalvik cache" and YES. Press "go back".
Here you have 3 options.
OPTION 1.
Use an SD card reader copy the Zip file to the root of the SD card or copying using CWM. Using CWM you navigate with Volume Up and Volume Down to "mounts and storage" press POWER BUTTON (OK). Go to "mount USB storage" and your SD card will appear in windows and you can copy. After that you press "go back" 2 times to get to the main menu.
Go to "Install zip" and then "choose zip from sdcard". Search for the zip file and press OK then go to "YES" and press OK. Wait until done.
Go to "wipe data/factory reset" and OK. Go to YES then OK. Wait until done.
Press "Reboot System Now" and "yes" if asked (if you are asked about some fix or anything after you press reboot now choose the positive thing like the answer that is not no).
OPTION 2.
Copy the file using adb push. Open a CMD window in Windows (Start+R type CMD press ENTER). Copy this:
Code:
adb push
With the space. After space go where you downloaded the zip file highlight it and drag it in the CMD. Leave a space after that and type /sdcard (without space after).
Wait until done and close CMD.
After you copied the file to your sdcard go to "install zip" -> "choose zip from sdcard" -> search for the "P710 Stock KK.zip" press OK then go to "YES" and your installation will beging. Wait until it is done. Go to "wipe data/factory reset" and OK. Go to YES then OK. Wait until done.
Press "Reboot System Now" and "yes" if asked (if you are asked about some fix or anything after you press reboot now choose the positive thing like the answer that is not no).
NOTE: In the zip i made i don't know why i couldn't sideload it but usually you do not have to copy to SD card to flash something. You can sideload it. All you have to do is:
-Go to "install zip" -> "install from sideload"
On your computer open a CMD and copy this :
Code:
adb sideload
Copy with space and after what you copied grab the zip you want to flash and drag it to CMD. Hit ENTER. Sideload will send the zip to phone and process of flashing will start. After it is done reset to factory again.
Press "Reboot System Now" and "yes" if asked (if you are asked about some fix or anything after you press reboot now choose the positive thing like the answer that is not no).
CONGRATZ YOU ARE NOW ON KITKAT. I HONESTLY THINK THAT YOU SHOULD GO FOR THIS CUSTOM ROM OVER HERE BECAUSE IT IS LIKE 10 TIMES BETTER THAN THE STOCK KK. TO INSTALL JUST DOWNLOAD THE ZIP FILE FROM THERE (V2) AND FOLLOW THE TUTORIAL WITH JUST REPLACING THE ZIP WITH THE OTHER ZIP.
LINK TO ROM: http://forum.xda-developers.com/optimus-l3-l5-l7-l9-ii/development/l7-ii-p710-amigakitkat-t2890092
LINK TO DOWNLOAD: http://d-h.st/GSh
6. Flashing Root through CWM.
On some ROMS root will not be there. To avoid this we will flash the SuperSU zip.
To get to recovery you have 2 ways:
- From you ROM connect USB as MTP or in a way that ADB recognizes it (device gets detected by adb devices) type adb reboot recovery.
- Close your phone. At the same time press VOLUME DOWN + HOME BUTTON + POWER BUTTON. When you see the LG logo stop pressing POWER BUTTON. Keep the others 2 until you are in CWM.
Install the SuperSU zip with one of the ways you learnt at step 5.
You are rooted now.
Hope everything worked out fine for you and you are happy. Have a really nice day.
CREDITS:
riskey95 -> his work for CWM recovery and Hacked Bootloader
Chainfire -> for making SuperSu possible
Snoop05 -> for the amazing 15 seconds ADB Installer
alephzain -> making Framaroot, such an easy root method
santhoosh -> for the tutorial of making CWM flashable zip from KDZ
Amiga500 -> for super cool KK Rom
airidosas252 -> best kernel on the market
ME -> for putting everything together and writing this
Everyone i forgot just PM me
Lg Flash Tool 2014 : http://tinyurl.com/kggahet
P710 Stock KK.zip: http://tinyurl.com/p7q7d75
P715 Stock KK.zip: http://tinyurl.com/nllkxfm
P713_CIS_KK.zip: http://tinyurl.com/nv3uzop
LG P715 (JellyBean).kdz: http://tinyurl.com/lwv29xr
adb-setup-1.4.2.exe: http://tinyurl.com/qca8abd
VC_RedistInstaller.exe: http://tinyurl.com/n98r7wg
LG Drivers: http://tinyurl.com/l3mgf49
CHANGELOG:
- added support for P715
- added P713 CIS
- added new version of SuperSU
This is fantastic! I've been looking for how to convert KDZ to a CWM Zips because of trouble rooting the P713 Firmware
Dennydap said:
This is fantastic! I've been looking for how to convert KDZ to a CWM Zips because of trouble rooting the P713 Firmware
Click to expand...
Click to collapse
Does P713 have NFC?
This method actually works for dual sim too,you just have to use P715 kdz's.
KWG V2 said:
This method actually works for dual sim too,you just have to use P715 kdz's.
Click to expand...
Click to collapse
Yeah it does. Maybe this weekend I will mod it. It is usefull for recoverying from soft bricks also just Step 1 and 2.
it was great till i get stuck on boot loop ,,, now how to solve ?
thanks for the useful guide.
I have a problem though, I cannot go after kdz extraction.
LG Tools stops with an cryptic error like [009.400.120.120.120]PC????? and looking at the log it seems there are troubles in unpacking the kdz file.
I have tried with different roms but still the same.
Does anyone has the same problem ?
xak-fr said:
it was great till i get stuck on boot loop ,,, now how to solve ?
Click to expand...
Click to collapse
Where exactly did you get a boot loop?
thanks for the useful guide.
I have a problem though, I cannot go after kdz extraction.
LG Tools stops with an cryptic error like [009.400.120.120.120]PC????? and looking at the log it seems there are troubles in unpacking the kdz file.
I have tried with different roms but still the same.
Does anyone has the same problem ?
Click to expand...
Click to collapse
Did you run as administrator? Do you have drivers installed? Tell me exacly what you did and what happened.
xak-fr said:
it was great till i get stuck on boot loop ,,, now how to solve ?
Click to expand...
Click to collapse
the problem is on V10J,, i dont know where you find it but it stucks,,, i used the lg flashtool for flashing kit kat i got the original one and the phone starts running but the thing that made me curious is that nothin on phone changed,, it is the same as it was when i had stock kit kat,, no factory reset, no nothing,,, can anyone explain please ?
xak-fr said:
the problem is on V10J,, i dont know where you find it but it stucks,,, i used the lg flashtool for flashing kit kat i got the original one and the phone starts running but the thing that made me curious is that nothin on phone changed,, it is the same as it was when i had stock kit kat,, no factory reset, no nothing,,, can anyone explain please ?
Click to expand...
Click to collapse
I can't really understand you. The point of this guide is to get root on kitkat so flashing with lg flashtool will not work if you want kit kat rooted. I tested that V10J on my own l7 2 (p710). Also if you flashed Jellybean did you press CSE Flash not Normal Flash?
scholars nxperan
christi9503 said:
I can't really understand you. The point of this guide is to get root on kitkat so flashing with lg flashtool will not work if you want kit kat rooted. I tested that V10J on my own l7 2 (p710). Also if you flashed Jellybean did you press CSE Flash not Normal Flash?
Click to expand...
Click to collapse
sorry for my english ,, let me explain,, i had stock kit kat on my P710,, I flashed JellyBean (V10J that was on flashtool folder). after the flash (CSE Flash) finishes i got stuck on boot loop,, so after many tries to revive the phone i used to flash the stock kit kat again and the phone started working but in the phone nothing changed like nothing happened ,, i know it is not rooted , i flashed stock kit kat (V20A.KDZ)
so the problem is the boot loop i got after flashing V10J i found in folder,,,
xak-fr said:
sorry for my english ,, let me explain,, i had stock kit kat on my P710,, I flashed JellyBean (V10J that was on flashtool folder). after the flash (CSE Flash) finishes i got stuck on boot loop,, so after many tries to revive the phone i used to flash the stock kit kat again and the phone started working but in the phone nothing changed like nothing happened ,, i know it is not rooted , i flashed stock kit kat (V20A.KDZ)
so the problem is the boot loop i got after flashing V10J i found in folder,,,
Click to expand...
Click to collapse
What model you have P710?
christi9503 said:
What model you have P710?
Click to expand...
Click to collapse
yes, Lg optimus L7II P710
xak-fr said:
yes, Lg optimus L7II P710
Click to expand...
Click to collapse
Ok do that step again. Flash with that tool using the image i provided. After the last ok. Even when you get the offline error don't touch it until phone reboots. If you get bootloop do this.
1. Pull out battery. Wait 10 seconds. Push battery back in.
2. While holding POWER DOWN + HOME BUTTON press POWER BUTTON. Wait until you see LG logo then stop presing POWER. You will get to see android guy doing stuff. Then tell me if it's ok.
christi9503 said:
Ok do that step again. Flash with that tool using the image i provided. After the last ok. Even when you get the offline error don't touch it until phone reboots. If you get bootloop do this.
1. Pull out battery. Wait 10 seconds. Push battery back in.
2. While holding POWER DOWN + HOME BUTTON press POWER BUTTON. Wait until you see LG logo then stop presing POWER. You will get to see android guy doing stuff. Then tell me if it's ok.
Click to expand...
Click to collapse
yes, i get the boot loop but after the reset is ok,, now will go on other steps ,, thank you
xak-fr said:
yes, i get the boot loop but after the reset is ok,, now will go on other steps ,, thank you
Click to expand...
Click to collapse
Don't forget to press the thx button it's in the right . I will add this to the tutorial I didn't need it but who knows.
I managed to do the "root" step, but somehow cannot proceed with the next step.
When I check "USB debugging", the phone doesn't connect to the computer for some reason. I tried multiple computers, with no luck. The "adb devices" says just empty "List of devices attached".
If I disable the USB debugging, the phone gets connected just fine, if I enable it again, it gets stuck on "Connected as installer", and doesn't connect as MTP....
Any idea how to fix this?
Do you have drivers installed? Also when you press MTP cancel if your phone wants to install anything.
Sent from my LG-P710 using XDA Free mobile app
christi9503 said:
Do you have drivers installed? Also when you press MTP cancel if your phone wants to install anything.
Click to expand...
Click to collapse
I tried everything, without luck. I ended just using terminal emulator to copy the files on phone directly (might be cool to add this to your tutorial, as someone else can also have this problem). So, now I'm on Amigas ROM - makes a HUGE difference! Thanks, looking forward for some other custom ROMs for this phone..
vasikgreif said:
I tried everything, without luck. I ended just using terminal emulator to copy the files on phone directly (might be cool to add this to your tutorial, as someone else can also have this problem). So, now I'm on Amigas ROM - makes a HUGE difference! Thanks, looking forward for some other custom ROMs for this phone..
Click to expand...
Click to collapse
Strange huuummm. I don't know. Yeah i will add Terminal Emulator also in weekend. Never happened to any of my phones before... Maybe driver conflict on your PC or something like that.