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.
Related
I'm predicting 8/1/2011
anyone bets bets? 5 dollars on June 23
I think it'll be a lot quicker than that.. Probably even before July. All the great Evo devs are switching to the 3VO says myn.
it will either be really quick or quite a while.
June 26th
This way they have a weekend to work on it.
dont really care since im keeping the phone root or not.
Tomorrow!
Sent from my PC36100 using XDA App
I bet it's already rooted and those responsible are keeping a tight lip about it.
erikivy said:
I bet it's already rooted and those responsible are keeping a tight lip about it.
Click to expand...
Click to collapse
If I had it rooted I'd post some proof without actually giving away the way it was rooted.
firemedic1343 said:
If I had it rooted I'd post some proof without actually giving away the way it was rooted.
Click to expand...
Click to collapse
Good point. It would be fun to tease the masses.
erikivy said:
Good point. It would be fun to tease the masses.
Click to expand...
Click to collapse
Got the ***** rooted
READ THIS GUIDE CAREFULLY SEE POST TWO FOR FAQ OR SEARCH THE THREAD.
Presenting the ONE AND ONLY surefire root method that backs up your RSA KEYS prior to rooting !!!!
Also I am aware that unrevoked has out their new tool. However while I was sitting in IRC, I saw many that it wasnt working for. So Until there is a surefire, easy method, I will keep this thread updated.
Credit goes to:
amoamare (Initial method)
toast (fake recovery and script)
unrevoked (thanks for your app)
amon_ra (fixed custom recovery)
chris1683 (thanks for the rom) (sprintlovers)
ryanza (z4root)
illogos, epicroot, xHausx, TrevE, Chubbzlou (Testing)
BooDaddy (RSA Backup Info)
and who ever else I missed
Help me finance my Vette!
zikronix
Disclaimer and well a little fun:
This has been tested on many phones and it worked fine...but if it breaks your **** dont come cry to me about it...you knew the risks! No one here is responsible if you break, brick, set fire, punch, smash, stab, destroy, your self, computer or your phone. The only person responsible is you! Just because it worked for me and others does not mean it will for you. Anytime you flash something its a risk.
Ladies and gentlemen... I've traveled over half our forum to be here tonight. I couldn't get away sooner because I had a POST coming in and I had to see about it. That phone is now rooted at and running well. I have two others comming in and this method has rooted many on the board. So, ladies and gentlemen... if I say my guide works you will agree. You have a great chance here, but bear in mind, you can lose it all if you're not careful.
Out of all methods that beg for a chance to root your phone, maybe one in twenty will work; the rest will be trolls-that's posters trying to get between you and the guide-to get some of the root action that ought by rights come to you. Even if you find one that has a simpler guide, and means to root, he'll maybe know nothing about helping. This is... the way that this works. This method is reliable like no other in this field and that's because its been tested and tested time and time again. I assure you, whatever the others promise to do, when it comes to the showdown, they won't be there...
Downloads
================================================== ====
STOP HERE READ THIS
This Method soley uses Amon_RA Recoveries....Period. A poor soul that lost his RSA keys (broken 4g forever) by recent clock work shenanaigans here
VX - Updated Amon Ra Recovery. Download Here: hboot_2.xx_soff-VX.zip
MD5: 27eb4a36ba01078193975fc93723dd60 <---VERIFY YOUR MD5, IF ITS NOT THIS REDOWNLOAD
Lets Get Rooted!
================================================== ====
Prerequsites:
Extract only the main zip file to a folder of your choice. I recommend the root of C:\ into a folder of your choice or on the desktop. Make sure you have the drivers installed for your phone (recommended: SDK Drivers or unrevoked hboot drivers) and USB debugging is on. This was setup for people running windows, if you have access to it do it on a 32bit version. I can't stress this enough you must use the adb.exe included with the package This is command line based do NOT double click the exe. Assume nothing, and cut and paste or type the commands EXACTLY as listed, they are case sensitive and each line is a seperate command. Oh and Read the FAQ and Warnings for f-sakes
1) Connect your phone to the computer (Rear USB Port Perferred) make sure the computer detects the phone (DO NOT MOUNT USB) If it doesnt install the drivers. Now master Reset your Phone (Menu>settings>Sd & Phone Storage>Factory Data Reset). Your phone will reboot. While your phone is rebooting it ctrl+alt+delete on your computer and open up task manager and click the processes tab look for anything that says adb.exe click it and hit end process.
2) Your phone should be booted and in the rom. You can skip the setup. On your phone enable install applications from unknown sources.(menu>settings>applications>unknown sources) and turn on usb debugging.
3) Open a command prompt (do NOT click adb.exe) and change to where ever you extracted the files to.
4)Type the following (this must be excuted from the folder you extracted to)
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip
adb push root/flash_image /data/local/
5) Now were gonna install z4root. When its done look at your phone z4root should be running. Select temporary root... It will go thru the process will eventually come to a white screen *Wait* after a sec or so screen will come up saying temp root was a success. Ok so now type the following
adb -d install -r root/z4root.apk
adb shell am start -a android.intent.action.MAIN -n com.z4mod.z4root/com.z4mod.z4root.z4root
6) Your command should still be open and you should be in the directory where you extracted the files. Once you have typed "su" command below look at your phone and click allow for SuperUser...Ok so now type the following from the command prompt
adb shell
su
6A) REQUIRED RSA BACKUP This will back up your RSA keys just in case something goes wrong in that department. You should still be in your command window inside the shell with a #. (The following came from this thread)
mkdir -p /sdcard/nandroid/RSA-PR-BACKUP
cat /dev/mtd/mtd0 > /sdcard/nandroid/RSA-PR-BACKUP/wimax.img
This saves it in a file that can actually be restored. This next step is another type of backup just for good measure
busybox sed -n '/BEGIN CERTIFICATE/,$p' /dev/mtd/mtd0 > /sdcard/rsa_OEM.key
This will dump the RSA keys to a text file on your SD Card named rsa_OEM.key
Mine was about 4575 KB in size, but the size could vary. Go ahead and switch the phone's USB connection over to "Disk Drive" and then browse to your SD Card and verify that the file rsa_OEM.key is indeed on the card.
Proceed to Step 7
7) You Should still be at a "#". This means you have root if you see a "$" or some other error message. Reboot your phone, check your drivers, usb debugging and cable and start over. If you got a "#" You can Proceed. You should still be in the shell at a "#" If not start over...Otherwise
chmod 0755 /data/local/flash_image
./data/local/flash_image misc /sdcard/mtd-eng.img
sync
8) Now we are going to reboot your phone into the boot loader to flash the first PC36IMG.zip. You should still be in the shell So Type:
reboot bootloader
9) Once your phone is in the boot loader highlight bootloader, and press the power button. It will load the PC36IMG File...When it ask you to flash press VOL-UP. You will notice that it says bootloader bypassed and maybe some other errors. Dont worry this is normal. Once the flash of the file is done it will ask to reboot, Select NO by Pressing VOL-DOWN. Now some people have gotten some errors here and there during the flashing just continue as normal.
10) You should still be in the boot loader at this point. Scroll down to recovery and press the power button. It Should take you to a red triangle. If not and you get stuck at a white htc screen pull the battery and then repower the phone with power + vol down and select recovery. When you see the red triangle. Type the following (IF YOU GET STUCK HERE CHECK THE FAQ):
adb push recovery /
adb shell busybox --install /sbin
adb shell nohup /sbin/recovery &
With any luck you should be at a recovery (green screen with text)
11) Select enable USB-MS. This will mount your sdcard. Look in the root of your sdcard and you should have two files. One named PC36IMG.zip and one named PC36IMG-MR.zip. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip when your done follow the instructions on your phone to disable usb (press power) then proceed to step 12
12) Now Select flash zip from the menu and choose unrevoked-forever.zip. Wait for it to complete. Select Reboot from the menu.
Now pay attention. It might kick you back into:
BOOT LOADER: See 12A
ROM: See 12B
WHITE HTC SCREEN: See 12C
12A) Ok so you got kicked to the boot loader. It should scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
12B) Ok so the phone booted into a rom. Power the phone off. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
12C) Ok so the phone is stuck at a white htc screen. Power the phone off by pulling the battery. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
13) Ok your phone is rooted now, and you should be inside the rom. The rom you just flashed is Sprint Lovers rom with the modified recovery. Download a rom of your choice copy it to the root of your sd card and flash it. But type the following first
adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip
adb reboot recovery
14) You Should be in the recovery menu now (green text screen). Do a backup by navigating to backup/restore press power to select then do a Nand backup in the next menu. Once thats done, select return, then reboot or flash a rom of your choice. If you flashed a different custom rom than the one thats included in the package cool. If not no big deal eitherway. Do a PRL/Profile update while in the rom after the phone is done rebooting. Your Done.
15) Read the FAQ for questions
jk jk
You are joking about it being kept quite right? with how many people like to be the HERO and post anything and everything first? trust me once root people wish rush to post IM THE FIRST TO HAVE IT ROOTED HERE IS PROOF.
TRUST ME THE HERO EFFECT NEVER FAILS.
root
toast has said we are good .....we have eng hboot and he did root the og evo ...... if he said anything htc could patch the exploit with ota ..... we will have root s-off really soon
...............
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
http://www.mediafire.com/?gcenefqc3khcc0c
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Please DO NOT ask Questions in the Development forum
Moving to General
When i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
It is alive again. Thanks all who helped out
renedg said:
when i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
Click to expand...
Click to collapse
it is alive again. Thanks all who helped out
You are the man! My IO Galaxy Tab 10.1 is alive again!
Thanks!
Hi All,
I am done the ODIN step, but it still in bootloop mode. I dont know how to do with the Fastboot recover mode. I tried with my Windows 7 and it can't recognized my fastboot driver and stay in the <waiting for device>. Is there any solution for me. Thank you so much.
ericc191 said:
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
Click to expand...
Click to collapse
Hello, I have also followed these directions however I am having issues rebooting into recovery using adb.
When I execute adb devices no devices are found.
Any additional help would be appreciated. Thanks
UPDATE:
Success!! I was able to correct the boot loop problem by installing fastboot on a linux machine and running sudo fastboot -w. Also my tablet was in fastboot mode (Power + Volume down, then Select the usb symbol).
Instructions for installing fastboot were found here http://forum.xda-developers.com/showpost.php?p=14675422&postcount=2
boot looping SOLVED! Honeycomb 3.1 google i/o galaxy tab 10.1
[IO TAB] Boot looping? Try this to get your tab back...
I had an issue with my IO 10.1 Tab boot looping. I imagine that this would work for retail as well but have not tried it.
This process will factory reset your device.
You will need fastboot and recovery.img to boot into recovery in order to perform a factory reset.
Fastboot & Stock IO recovery comes from this post as an attachment at the bottom.
You need adb to continue (windows).
1. Extract files to where adb resides (platform-tools folder in android SDk main folder) e.g
C:\Program Files\Android\android-sdk\platform-tools .
2. Plug your tab in to a power source and then hold down the power button until it shuts down. Wait until the tab displays the charging battery.
3. Press and hold the volume down (left button in landscape) and power buttons until the usb and odin icons show up. Volume down to move left and volume up to select the usb logo. Now you should be in fastboot. Plug the usb into your computer.
4. Time to fire up adb!
Start / run / cmd , cd\,
Than, cd to your platform-tools folder or wherever your adb is at. (should be in platform-tools inside of android-sdk-windows)
5. In cmd type "adb start-server" without quotes to start adb. All comands should exclude quotes.
6. Type "fastboot devices" your device serial should appear!If not:
Edit the “<PATH TO ANDROID SDK>\extras\google\usb_driver\android_winusb.inf” file and copy/paste the following lines and add them to the [Google.NTx86] section (for 32bit Windows) and/or [Google.NTamd64] (for 64bit Windows).
NO Empty line above this set, though galaxy tab 10.1v but works for all variants!(tab detected as adb xxx device)
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
;
Download the fastboot zip attached to this post (includes both Win and Linux version) and extract the files to your “<PATH TO ANDROID SDK>\platform-tools” folder
7. Now, type "fastboot boot recovery.img"
8. Now you should boot into recovery. For "adb command lines" to work boot with clockworkmod recovery img (Command and files here: http://droidbasement.com/db-blog/?p=2032)
If you want to try other stuff like push a system restore, kernel or whatever, now you can. If you fail at it, you can always repeat the steps leading up to this point to get back to recovery.
9. Time to just get the tab back! Select "wipe data/factory reset" and confirm, clear cache.
10. After that is done select "reboot device".
Credits to JASKRU from rootwiki, with some additions and modifications extracted from different sources!
for rooting the tab install the zip file from this post in recovery mode (loading recovery.img from fastboot):
http://droidbasement.com/db-blog/?p=2054
P.S don't reboot into recovery with adb command "adb reboot recovery" as it doesn't work, correct way is with fastboot command as mentioned in step 7!
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
FIRST STEP: add the attached fastboot files into the container folder of adb (in sdk folder)
This is mine:
C:\Program Files\Android\android-sdk\platform-tools
of course I did that and mine is in the same folder as yours
I get to step six and thats when it gives me the error
E:\android-sdk-windows\platform-tools>fast boot devices
'fast' is not recognized as an internal or external command,
operable program or batch file.
also when I go to the left instead of odin this is my pic (in attachment)
NOW if I hit the power button and the right on in landscape mode I do get the android system recovery options says Android System Recovery <3e> (pic attached)
I have tried wiping date clearing cache as far as fastboot goes it still doesnt let me in fastboot eventhough im not sure at this point what fastboot even is
I finally got CWM 4.0.0.4 on it but now what because somehow im on 3.0.1 on my tab it wont charge and idk what to do
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
tried this route but it cannot find my device via ADB - used the PDANet driver - note i did not get a driver in the extras folder
ideas?
mughalgxt said:
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
Click to expand...
Click to collapse
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
animatechnica said:
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
Click to expand...
Click to collapse
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
yes and i should add your method was very effective ! thanks
what threw me off initially was not finding the fastboot.exe which was in a different folder and the usbdriver - which needed to be installed separately and can be found by launching SDK manager, selecting Available packages-Third-party Add ons-Google Inc - Google USB Driver Package revision 4
mughalgxt said:
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
Click to expand...
Click to collapse
Thanks!!!
This totally worked!
vokhoa408 said:
Thanks!!!
This totally worked!
Click to expand...
Click to collapse
Is this thing getting Ice cream sandwich?
that might solve all these problems.
Samsung Galaxy Tab 10.1 boot loop
Edit: *Fixed!* Ok, so here is my advice to all you other noobs who bricked your tablet, be AWARE that your tablet actually is conscious, it chooses when it wants to work. Just do everything it says on here, all the fixes I have listed, reboot a bunch of times, yell at it, and when you cry a true tear of pain and remorse, and it splashes down on the surface, it will recognize this and all of a sudden work. Booted to 3.0.1 and going to update, that all that is holy.
Hi Guys, I am having the same problem and need some expert advice please, I have a Samsung Galaxy Tab 10.1 with Android Honeycomb 3.1, running Windows XP Pro SP3
I've gone over every solution to this problem on xda over two days and none have worked for me, either that or i'm not doing it correctly.
I successfully rooted my Tab a few days ago, then tried to install a 'boosted' theme and everything is messed up now. When I boot it just hangs on the samsung loading screen, and it reboots to the same screen.
I have tried wiping data/factory reset in cwm
I have tried wiping cache partition
I have tried running Odin through downloading mode
I have adb and fastboot installed on my computer
I have Samsung Android adb interface driver in Device Manager
I have PDAnet installed
When I boot holding the volume down and power button to get the two options, the only two options I have are the Odin Downloading green guy on the right, and an icon with a box and an arrow coming out of it that takes me to CWM on the left.
So I cannot choose fastboot mode on the Tab, when I try to run 'fastboot flash system new.img' through cmd.exe it just says < waiting for device >
I"m a total noob to this and should have left well enough alone when I successfully rooted it, i'm sure I must be just missing a small step, if I could get a bit of guidance it would be greatly appreciated, thanks.
My phone has a major problem. I'll explain the steps I took to screw it up this badly.
1.) Root phone and install a ICS rom
2.) Market doesnt work so I reinstall another market/vending.apk app from mediafire
3.) Market still didnt work so I install another rom
4.) Then I use that rom and rom manager is gone so I install another one I downloaded form mediafire.
5.) That rom manager only verifies my phone as a optimus c but i still installed clockwork mod
6.) The version Clockwork mod does not work
7.) I installed Xionia recovery instead
8.) I accidentally, in xionia, do a factory reset that bricks my phone.
9.) I could still use adb to force files on and try to recovery the phone by flashing files
10.) I flash a recovery image file and now here is the HUGE problem
11.) MY PHONE WONT BOOT UP AT ALL, ALL THAT SHOWS IS THE LG SYMBOL AND THEN BLANK SCREEN. WHEN I HOLD DOWN,POWER,HOME IT DOES THE SAME THING (BLANK SCREEN). AND WHEN I TRY TO USE ADB I GET THAT MY PHONE IS CONECTED BUT,
c:\adb devices
List of devices attacched
A100001944D988 recovery
Then I try ADB shell
C:\adb shell
But I get
/ #
and i cant complete any commands
when i try adb remount
C:\adb remount
remount failed: Invalid Argument
Can Someone Please Help
Same issue
Maybe the Virgin Mobile Store will just give me a new phone cause there is no actual proof that I rooted the phone.
Before trying this method be 100% sure that recovery is not working hold volume down + power + home continuously for around one minute if u get fastboot error, follow this - http://forum.xda-developers.com/showthread.php?t=1088046thread but still if u see nothing u have to use kdz method http://forum.xda-developers.com/showthread.php?t=883314 or see this link for a picture guide - http://forum.xda-developers.com/showthread.php?t=1060121
Sent from my LG-P500 using Tapatalk
Sent from my LG-P500 using Tapatalk
Hi. New to this device. Just to check has anyone successfully root this device on the Marshmallow 6.0?
I did read around for a solution but only saw the lollipop-root-method.
Thanks in advance!
Sent from my ASUS_T00N using Tapatalk
Still no solution found. Anyone?
Sent from my SM-G900FD using Tapatalk
I can't figure out root on 6.0.1 either. I just upgraded from rooted 5.0.1 to 6.0.1 using TWRP on WW version of firmware with Padfone S. I immediately flashed SuperSU from TWRP after flashing the update, but the update still broke root. Tried both Kingroot APK and Kingoroot APK + PC without success.
Thanks for that update martingriffis! At least we know that didn't work.
Anyone else has any other solution?
Sent from my ASUS_T00N using Tapatalk
https://forum.xda-developers.com/showpost.php?p=69715735&postcount=2
Nice! Will try that out.
Sent from my ASUS_T00N using Tapatalk
Systemless root?
Enviado desde mi Moto G (4) mediante Tapatalk
The binarie not update
Enviado desde mi ASUS_T00N mediante Tapatalk
itsme1st said:
https://forum.xda-developers.com/showpost.php?p=69715735&postcount=2
Click to expand...
Click to collapse
I recently tried doing this. To no avail. DLs not working. Been trying to push twrp can't too.
Anyone successfully done this recently? Care to share the dls here?
Sent from my ASUS_T00N using Tapatalk
My problem ist - i can`t get the TWRP 2.8.7.8. - the HP seems to be shut down. So I cannot try it. And I need urgent root, cause I have a Synology Server save Clod also on the Asus. Anyone an Idea?
Is here anybody who has coincidentally the TWRP 2.8.7.8. still on his PC and cand send it per mail??
Asus Padfone S Marshmallow Rooted *Working*
If you like me 'get the device and direct update to latest MM', then you need to do something like this.
First you need the device and a computer.
Next is get all files from here https://forum.xda-developers.com/showpost.php?p=62352276&postcount=2 and skip the old supersu and use the new version here https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
After that enter the device into fastboot mode (Turn on while hold vol up and it will vibrate once and stuck at Asus logo)
Connect the usb to computer, open adb (extract fastboot and adb.rar to new folder, inside it right-click on empty place while holding [Shift] on keyboard, and see for 'Open command window here')
Write first 'fastboot devices' (without quote) to check if the computer detect your device with '(font+number) fastboot' in cmd.
If is working, then you can go to the next step. If not maybe need to get some adb driver to make it working.
Next is extract twrp_2.8.7.0.rar into the adb folder, make sure it is .img file.
At cmd, write 'fastboot flash recovery twrp_2.8.7.0.img' and press enter. If you see some line like this 'remote: can't flash unsigned image' is actually working.
After that write 'fastboot reboot' and press vol down so the device will immediately enter the recovery mode. If working the device will enter TWRP perfectly (opening sometime it will say something about 'read-only', just press 'Back' to get the actual TWRP menu) but if the device just straight boot normally, you need to do the flash recovery back because it failed.
At TWRP menu choose mount, and put some CrowLock_RC3.zip and SuperSU-v2.79-201612051815.zip from your computer to your device folder.
Press back at TWRP and flash the CrowLock_RC3.zip to unlock bootloader first (if you do not see this file, just press 'storage...' at top and choose the actual storage). After done you need to reboot the device and enter fastboot mode again (If you want to make sure your device still working, can just reboot it normally but do back fastboot mode again after that)
Next is flash the old recovery asus_t00n_twrp_2_7_1_1.img. Same step as before. After your reboot the device and enter recovery mode, your screen device will go to black. Actually is working, you just need to press power on once or twice to make the TWRP screen visible.
Next is flash the SuperSU-v2.79-201612051815.zip just like how you flash the CrowLock_RC3.zip before. You can wipe dalvik/cache after that or maybe not, then reboot. Your device will bootloop once and after that you can enjoy your device with root working.
To make sure your device have rooted, use Root Checker. For the first time, supersu will make a long time to prompt it but after that it should working normally like the previous day you use.
Has to be SuperSu 2.79, any higher won't work.
After finished instal twrp 2.7.1.1 and sucess i try to sigin twrp again and My screen change black and i press power once or twice but keep black no change
Can you help me..thx
If your have linux, you can install android-tools, then use fastboot from there.
HEZAiKU said:
At TWRP menu choose mount, and put some CrowLock_RC3.zip and SuperSU-v2.79-201612051815.zip from your computer to your device folder.
Click to expand...
Click to collapse
You can also got to /data/media/0 to access to your Downloads directory.
HEZAiKU said:
Press back at TWRP and flash the CrowLock_RC3.zip
Click to expand...
Click to collapse
The button is not named "flash" but "install".
HEZAiKU said:
Next is flash the old recovery asus_t00n_twrp_2_7_1_1.img. Same step as before. After your reboot the device and enter recovery mode, your screen device will go to black. Actually is working, you just need to press power on once or twice to make the TWRP screen visible.
Click to expand...
Click to collapse
Oops, I forgot that step ...
@wric01 is it true then? Thou when im download the SuperSU.zip that time its still the latest so i thought any latest version should be working.
@Paidi86 just make sure you follow the tutorial correctly.
@xdej well, cuz for smartphone android device, im actually too prefer with 'flash' instead 'install', well for me its still the same meaning.
I got root with my personnal open-source files:
Code:
# /system/bin/id
uid=0(root) gid=0(root) groups=0(root), context=u:r:init:s0
How I got there:
(1) install Termux from Google Play
(2) in /data/data/com.termux/files/home, put "CrowLock_RC3.zip" and "SuperSU-v2.79-201612051815.zip".
(3) Install version v19 (will be uploaded soon) of https://sourceforge.net/p/gentooandroid/wiki/InstallingInstructions/ using EPREFIX=/data/data/com.termux/usrex.spartacuside/gentoo_armv6l and PLACE_LD=/data/data/com.symli/n/3 following all instructions (that took me half a day, this installs Gentoo on your phone; if you want I can make an easier way). Don't add any package with emerge, this is not needed at this point.
(4) Download twrp_2.8.7.0.rar from https://mega.nz/#!GwRRBBjT!8ms39GK62...aKA816Cg4lsQr0
checksums with sha1sum:
8dc6b577d04fbd05ff31d3dedca7cf51d7bfef22 twrp_2.8.7.0.img
1d784bde5339054ed27ff38fb17e1368f95d6dcb twrp_2.8.7.0.rar
(5) Connect it to a computer, then power Off the phone, keep "vol up" button pressed before it switches off.
(6) If you did not connect it to a computer, press "power" button
(7) the phone powers on, vibrate a bit, you can release the buttons "power" and "vol up".
(8) you now need another computer. If it is a linux computer, install package android-tools , then run, as root: fastboot flash recovery twrp_2.8.7.0.img ; if it is a windows computer, issue the equivalent instruction with fastboot.exe downloaded from https://forum.xda-developers.com/showpost.php?p=62352276&postcount=2 (checksums with sha1sum:
e01c22dc34e915bca88de2c73966b807b2b39f26 fastboot.exe
eb9ce15bebcfb63a5cb4c24913aba76c8d319287 fastboot_and_adb.rar) ; whether you have a mac or no, also download fastboot from https://wiki.lineageos.org/adb_fastboot_guide.html You can ignore the erro "remote: can't flash unsigned image' is actually working": it nevertheless did works.
(9) keep "vol down" pressed on the phone.
(10) on linux, execute: fastboot reboot ; on windows, fastboot.exe reboot I guess
(11) after it vibrates, you can now release "vol down". select "enter recovery mode", then validate with the power button. The phone boots twrp, which is a sort of equivalent of init=/bin/sh on linux.
(12) in twrp, select "keep read-only", then use "install", then select "/data/data/com.termux/files/home/CrowLock_RC3.zip", validate, then repeat steps (5) to (11).
(13) in twrp, select "keep read-only", then use "install", then select "/data/data/com.termux/files/home/SuperSU-v2.79-201612051815.zip", validate, then repeat steps (5) to (11) (if you skips entirely step (13), the phone will not be able to boot).
(14) in twrp, select "advanced", then "terminal command", then select directory /data/data/com.termux/usrex.spartacuside/gentoo_armv6l/usr/local/bin as working directory
(15) execute: mount /system
(16) execute: mv /system/bin/app_process32 /system/bin/app_process.wrapped (you will first need to use backspace to remove characters of previous command, "mount /system")
(17) execute: cp app_process_wrapper /system/bin/app_process32
(18) execute: chgrp shell /system/bin/app_process32
(19) execute: umount /system
(20) use back button three times, and select reboot, then select system.
(21) it should boot normally. It did on my asus padfone S and on my asus padfone S+ (the only padfone with 3GB of RAM).
(22) open tmux, inside it, execute:
Code:
ssh -p 64000 [email protected]
(23) you will be asked the root password that you used at step (2)
if you want to add packages, remember to use
Code:
ssh -p 64000 [email protected]
before using Gentoo's installer:
Code:
PORTAGE_BINHOST=http://sourceforge.net/projects/gentooandroid/files/packages/packages emerge --autounmask-write -GKv firefox
xdej said:
I got root without unlocking, with my personnal open-source method:
Code:
# /system/bin/id
uid=0(root) gid=0(root) groups=0(root), context=u:r:init:s0
How I got there:
(1) install Termux from Google Play
(2) Install version v19 (will be uploaded soon) of gentooandroid.sf.net
Click to expand...
Click to collapse
You can replace step (2) with any other provider of sshd binary:
(2bis) ignore step (2),
(2ter) put any binary you want to be executed with selinux context u:r:init:s0 at /data/data/com.termux/usrex.spartacuside/gentoo_armv6l/usr/local/bin/sshd_root
(2quater) download app_process_wrapper binary
/data/data/com.termux/usrex.spartacuside/gentoo_armv6l/usr/local/bin/app_process_wrapper from the attachment in this message
Then proceed from step (3) onwards.
This may work for other phones supported by twrp, I did nothing asus-specific.
No need to install old recovery. just fastboot your device (power on and vol up) and then do `.fastboot boot asus_t00n_twrp_2_7_1_1.img` it'll boot the old recovery.
Make sure to put supersu in device memory, not sdcard.
The method you give is much simple then the rest. Just want to know if the custom recovery mode is able to enter without unlocked bootloader?
Does somebody have a step by step guid to install this on my device?
I found this and this but I dont know if this can be used to install the rom on my device.
I just know you need to unlook your bootloader first before to do anything.
I already checked and my device can be unlooked.
Go ahead man those guides are just fine. This is what I did to install Carbon.
Read all the steps first then do it, and also definitely read the note* at the end
Write down your IMEI somewhere safe
Unlocked bootloader. Get unlock code from Sony's official site. Just Google it it's easy to find. Don't follow unofficial websites, apps.
Turn the phone off.
Hold down the vol-up button.
While holding, attach the usb cable, wait a few sec.
Release the button. On laptop issue the command
Code:
fastboot devices
(download the fastboot from here on the forum if not already). You should see you'r device serial number.
If not, instead of attaching usb cable use the power button to turn the phone on (nothing happens on the phone screen) then attach usb cable.
Issue the command
Code:
fastboot oem unlock 0xTHE_CODE_YOU_GOT_FROM_SONY
Reboot perhaps?
Code:
fastboot reboot
If you rebooted, go back to fastboot mode as described above.
Flash TWRP (recovery.img). Download it's image from here on the forum. Use the command
Code:
fastboot flash FOTAKernel recovery.img
Detach USB cable, reboot, turn the phone off.
Hold down the vol-down key and power key. Phone turns on, when you see sony logo, release the buttons. The phone boots into TWRP.
There's a backup button. Make a backup. DO IT!
Attach the usb cable. Transfer the backup to laptop.
Back to main screen, choose wipe. wipe everything, internal, system, blabla.
Transfer the carbon ROM to phone.
Choose what was it on twrp? install? flash? it's the first option.
Choose the zip file.
Look for open-gapps and magisk here on the forum. Install them just the way you installed the ROM if you wish.
Reboot. Phone might reboot itself while loading the carbon once or twice.
If you have wifi and network, congrats. if not, look for z2 baseband patch here on the forum.
Boot back into the TWRP, transfer the file to phone, flash it. Reboot. Hopefully you have network.
If you have not bricked the phone by now, congrats you have carbon on your phone, have your guaranty voided, and all your personal data wiped from the phone.
There's just one catch that after flashing the baseband, you get carrier network back but wifi stops working. Which I'm strggling to fix yet.
note*:
Before installing the carbon, after you have unlocked the bootloader, installed TWRP, and made a backup, on your laptop run the following commands to have your current firmware, in cast the baseband patch doesn't work:
While in the TWRP, go to mount section, mount the system.
On the laptop:
Code:
adb shell
cd /sdcard
cp -r /system/etc /sdcard
tar cf original_rom_etc_backup.tar /sdcard/etc
exit
Then transfer the original_rom_etc_backup.tar file created on the phone to your laptop and store it safely.
Later you can extract this file and chery pick the modem files and replace carbon modem firmware with the original see if yo get lucky :shrug