Database Develop

[Q] Bootloop hell

I apologize in advance if this same issue has been replied to elsewhere. I'm in kind of a unique situation and couldn't find an answer anywhere.
I'm got an N1 with 2.3.6 stock ROM, rooted. Recently I downloaded Titanium Backup PRO and while attempting to integrate dalvik cache to ROM, my phone rebooted into a bootloop. I'm assuming this is a bootloop. I get the colorful splash screen, it freezes for a second of two, then continues on, and on, and on....
Is there a way to get me out of this loopwithout having to wipe all my data, so I can backup all my stuff before I flash a custom ROM?
Everything I see about bootloops, mentions unlocking the bootloader and wiping all your data. I've seen downgrading using PASSIMG and loading stock rom. I'd really just like a simple way to get out of this loop hell and get my phone back up. It's in teh ship now getting it's power button fixed.
Thanks in advance

first thing i do on bootloops is pull battery
if no go pull battery and then pwr on by pressing pwr and trackball at same time--you can then get to recovery and maybe wipe dalvik and cache and reboot
i have never used TB for anything other than backup/restores, so can't help with dalvik integration

You might be able to fix it by wiping your cache from recovery.
Sent from my Nexus One using xda premium

Thanks for the advice! I'll give it a try as soon as I get my phone back from being fixed.

Hey guys, I hope you can help. I got my phone back with new power button, Yay! When I try to boot into recovery, teh Nexus X logo comes on for a moment and then I get a white triangle with an orange exclamation point. Do I need to use ADB to try and go to recovery and wipe my cache? I've never installed a recovery image. Do I need to do that or should there be a stock image already on my phone? Am I SOL?

One more thing that might help. I notice that when I go into HBOOT, the phone searching for 4 images from my SD card and can't find them. They go by too fast to write them all down but I think some are PASSIMG, PASSDIAG, etc. Again, do I need to load a recovery like clockworkmod on my phone first and then go into recovery to attempt to wipe my cache?

I get the same passimg all the time--no problem
If your phone came back from repair, you are probably unrooted and hence the triangle. At least that is the way I remember it, but has been two years since I rooted
If that is comfirmed by someone else, you wil need to reroot and install a recovery
A good time, if you haven't, to install android sdk and root/install recovery the right way and have full adb/fastboot features
there other ways I am not familiar with
does the lock show unlocked on the screen, they could have relocked bootloader
the wiki has the instructions, just have to navigate to the htc smartphones and N1

jus to make sure that if u still got root. install su checker app from play store and confirm.
if not root using SUPER ONE CLICK ROOT.
flash recovery (4EXT is good) www.4ext.net
do a backup and then flash the rom u want
Sent from my Nexus One using Tapatalk

Thanks I'll check. I only had teh power button fixed and not by HTC so I doubt they unrooted it. I'm still in a bootloop but I can use superoneclick still, so I'll give that a try.

so what I'm trying to do is wipe my cache without wiping my data. I don't think my bootloader is unlocked. Am I screwed?I'm in a bootloop, so I can 't install anything to the phone. I probably could put a recovery image on the SD card, but if my bootloader is locked, I'm guessing that won't work. I'm rooted. When I go to HBOOT, the phone looks for passim files and doesn't find them, then when I choose recovery I get the white triangle. I've try to flash a recovery image through ADB but I get an error, failed to load image. Again, is that a bootloader issue?
I'm almost at the point of just wiping my data and hoping I can get it all back somehow.

holtonhj said:
so what I'm trying to do is wipe my cache without wiping my data. I don't think my bootloader is unlocked. Am I screwed?I'm in a bootloop, so I can 't install anything to the phone. I probably could put a recovery image on the SD card, but if my bootloader is locked, I'm guessing that won't work. I'm rooted. When I go to HBOOT, the phone looks for passim files and doesn't find them, then when I choose recovery I get the white triangle. I've try to flash a recovery image through ADB but I get an error, failed to load image. Again, is that a bootloader issue?
I'm almost at the point of just wiping my data and hoping I can get it all back somehow.
Click to expand...
Click to collapse
You really know nothing huh. The triangle is the recovery. Press power button and volume up at the same time, it will the show you some options like wipe cache.

n1newbie said:
jus to make sure that if u still got root. install su checker app from play store and confirm.
if not root using SUPER ONE CLICK ROOT.
flash recovery (4EXT is good) www.4ext.net
do a backup and then flash the rom u want
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Did you miss the "stuck in boot loop" part?

sorry,
meant that the triangle is your stock recovery--
you install recovery thru fastboot not adb
i would still, if you haven't, install android sdk on pc-unlock bootloader (fastboot oem unlock) and fastboot recovery--all in wiki
i think it was mentioned--holding down pwr and tb will get you into fastboot mode--phone connected and usb debugging selected on phone
you'll just have more flexibility with flashing roms etc and getting out of trouble

[Q] Nexus 6 not booting up after random shut down

Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.

chg911225 said:
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
Click to expand...
Click to collapse
If your bootloader is unlocked, you should be able to either flash the stock factory image, or re-flash each partition separately through the tool-kit. Since you're getting remote errors with the toolkit, double check that you have the right drivers installed, the tookit and a search on the forum should help with that.

did you already try :
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

Don't want to raise any alarms already but I shut mine down on Sunday night (Unlocked/ Rooted/ custom kernel & rom) in order to boot in Recovery and flash a new kernel version and:
1) The sdcard looked empty, it read ~ 26 GB free (I had no more than 20 gb free before reboot) and no folders whatsoever.
2) The phone was stuck at the Google logo heating up but going nowhere.
As I said don't want to start assuming things but the phone randomly going "nuts" and losing all data is scary... I had to spent my entire day yesterday flashing stock 5.0.1 back and re-setting up everything. I followed the guide posted above (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 oh, go with Method 2 and it will work fine).
Out of curiosity how does your SD look like from recovery? Oh, but then you say you can't even boot to Recovery. Which recovery do you have? (I had/have TWRP 2.8.3.1 ). Anyway to repair it you only need to be able to boot into Bootloader properly I guess.

My Galaxy S4 active (AT&T) is bricked, tried to restore it

This is my backup phone so I don't care for the data that is on it and just want it working again. It was rooted before and I needed it unrooted in order to download an app that was blocked by root detection. I tried uninstalling the root using Super SU in its settings, when I restarted my phone it just freezes at the AT&T white screen.
I'm still able to go into the boot recovery menu, I tried putting on the I537UCUCOC7 (5.0.1) firmware found here (https://forum.xda-developers.com/showthread.php?t=2629093). I downloaded it, extracted the zip, and renamed the file "update.zip" and put the file on a microSD then in the recovery boot menu I went to install from external and selected the update.zip. It sorta kinda looked like it accepted it but I get a red error message about the sideloader and I'm still stuck at the white screen when it boots.
What else can I do from here?
P.S. I already tried wiping the cache and data/factory restore options and that didnt work.

Is there anything else that can be done?

I restored my phone to 4.4.2. How can I install 5.0.1? When I search for software updates it says theres nothing available even though I know it can go to 5.0.1 cause thats what I had before it bricked.

Please share how did you restore when I only able to boot into recovery and clearing cache and factory reset does not help. Phone just stack on boot loop

RemixDeluxe said:
I restored my phone to 4.4.2. How can I install 5.0.1? When I search for software updates it says theres nothing available even though I know it can go to 5.0.1 cause thats what I had before it bricked.
Click to expand...
Click to collapse
alex4cta said:
Please share how did you restore when I only able to boot into recovery and clearing cache and factory reset does not help. Phone just stack on boot loop
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s4-active/general/guide-update-to-i537-att-firmware-t2835481

How to recover from Verification Failed, Bootloops, and Android/Carrier logo freeze.

In this tutorial I will inform you on three different soft bricks, and how to fix them.
You must be able to boot into TWRP and/or Odin/Download mode!​
1.) Verification Failed.
Method #1
This method will work with people whom can't reset their device, due to an unmountable /data partition, and those whom experience this error, who can reset but have valuable items, applications, videos, or photos that they don't want to lose. Must be able to boot into Odin/Download mode. (Volume Down+Home+Power)
The solution is actually pretty simple. Boot into Odin/Download mode. This has to be done correctly, not from TWRP recovery. When the prompt for "Volume Up = Continue" and "Volume Down = Cancel (Restart)" press volume down. You should no longer see verification failed, but instead be sitting on the T-Mobile logo. This is normal, and could take 30 seconds to 10 minutes, depending on the amount of data.
This method works all because of Knox. Knox is what Samsung uses to void your warranty. Companies are not allowed to void a warranty when rooting, installing roms, or recovery, unless they have direct evidence. Knox will trigger this when it isn't sure. It will try forcing you to bring it to Samsung, and they can directly find out why it was caused. This happens when it thinks that you cancelled.
Method #2
This one will require you to lose all your data, but is mainly intended for those whom cannot reset their device. Download the stock firmware from the links below. Open Odin (Jodin3 will not work! It is not fully functioning, do not try it.) and boot device into Download/Odin mode. On your computer, you should see 'Added' in the logs. If this does not show up download the Samsung USB Drivers. Select AP and then select the stock firmware. Now flash it. This can also be done through TWRP
For bootloop and frozen Android/Carrier logo just do Method 2. You usually will keep all your data.
FOR 'VERIFICATION FAILED' YOU CANNOT RESTORE FROM A BACKUP!
FOR BOOTLOOPS AND FROZEN STARTUP SCREEN, YOU CAN!​
Downloads:
Samsung USB Drivers
7.1.1 Stock Firmware
Odin3 v3.12.10

Post any bricks below that you have encountered!
I'm interested in how many variations there are, and how common they are.

One weird error I'm getting all of a sudden is "Custom binary blocked by FRP Lock" when I tried to reboot my phone. Any ideas?

Hovo said:
One weird error I'm getting all of a sudden is "Custom binary blocked by FRP Lock" when I tried to reboot my phone. Any ideas?
Click to expand...
Click to collapse
Please describe this issue in further detail. Has this been happening out of nowhere, or did you just try flashing something via Odin/Download mode or TWRP.
Also, before flashing did you enable OEM unlock
This also happens when something flashed via Odin/Download mode is incompatible.
Are you still able to boot into the default system partition? If not safe mode?

TechNash said:
Please describe this issue in further detail. Has this been happening out of nowhere, or did you just try flashing something via Odin/Download mode or TWRP.
Also, before flashing did you enable OEM unlock
This also happens when something flashed via Odin/Download mode is incompatible.
Are you still able to boot into the default system partition? If not safe mode?
Click to expand...
Click to collapse
I should have updated my post, I'm not sure what happened but I flashed stock through Odin and the problem went away, after that I was able to flash twrp and root/install other roms.
It's still weird that the problem happened out of nowhere, not sure what triggered it.

It goes away when u log in to google with the last account that is associated with the phone

Hovo said:
I should have updated my post, I'm not sure what happened but I flashed stock through Odin and the problem went away, after that I was able to flash twrp and root/install other roms.
It's still weird that the problem happened out of nowhere, not sure what triggered it.
Click to expand...
Click to collapse
Probs OTA. It happened to me my first 3 tries. Ended up factory reseting, and installing fresh via Odin, didn't fix it.
I just turned off auto reboot on Odin, and then pulled my battery on my J7. Booted up straight to Recovery from there.

TechNash said:
Probs OTA. It happened to me my first 3 tries. Ended up factory reseting, and installing fresh via Odin, didn't fix it.
I just turned off auto reboot on Odin, and then pulled my battery on my J7. Booted up straight to Recovery from there.
Click to expand...
Click to collapse
It would make sense if it was an OTA update TY

Hi, I tried to root my phone and I got this error, I don't mind restarting the phone, but isn't there a way for me to backup my data (photos mainly) first?

Nightwinter said:
Hi, I tried to root my phone and I got this error, I don't mind restarting the phone, but isn't there a way for me to backup my data (photos mainly) first?
Click to expand...
Click to collapse
Sorry I didnt respond.
Looks like you didnt flash encryption breaker. Keep this on your SD Card as its a great way to recover from these errors, and you will need it when you flash ROMS.
Just boot in recovery, flash ashix no verity no encrypt, then reboot into system. You shouldnt have this error.

TechNash said:
Sorry I didnt respond.
Looks like you didnt flash encryption breaker. Keep this on your SD Card as its a great way to recover from these errors, and you will need it when you flash ROMS.
Just boot in recovery, flash ashix no verity no encrypt, then reboot into system. You shouldnt have this error.
Click to expand...
Click to collapse
Keep what in the SD card? the is no file in your quote.

Nightwinter said:
Keep what in the SD card? the is no file in your quote.
Click to expand...
Click to collapse
He's referring to the encryption breaker file ("no-verity-no-encrypt_ashyx.zip") in his first sentence. That is assuming you already had it and should be keeping it on your SD card all the time for flashing ROMs

graevon said:
He's referring to the encryption breaker file ("no-verity-no-encrypt_ashyx.zip") in his first sentence. That is assuming you already had it and should be keeping it on your SD card all the time for flashing ROMs
Click to expand...
Click to collapse
Thanks for explaining that to him.

TechNash said:
Thanks for explaining that to him.
Click to expand...
Click to collapse
how to remove Verification Failed or root in the TWRP file manager without losing data

Mujeeb64 said:
how to remove Verification Failed or root in the TWRP file manager without losing data
Click to expand...
Click to collapse
Flash ashyx-no-verity-no-encrypt.zip in twrp.
Reboot

TechNash said:
In this tutorial I will inform you on three different soft bricks, and how to fix them.
You must be able to boot into TWRP and/or Odin/Download mode!​
1.) Verification Failed.
Method #1
This method will work with people whom can't reset their device, due to an unmountable /data partition, and those whom experience this error, who can reset but have valuable items, applications, videos, or photos that they don't want to lose. Must be able to boot into Odin/Download mode. (Volume Down+Home+Power)
The solution is actually pretty simple. Boot into Odin/Download mode. This has to be done correctly, not from TWRP recovery. When the prompt for "Volume Up = Continue" and "Volume Down = Cancel (Restart)" press volume down. You should no longer see verification failed, but instead be sitting on the T-Mobile logo. This is normal, and could take 30 seconds to 10 minutes, depending on the amount of data.
This method works all because of Knox. Knox is what Samsung uses to void your warranty. Companies are not allowed to void a warranty when rooting, installing roms, or recovery, unless they have direct evidence. Knox will trigger this when it isn't sure. It will try forcing you to bring it to Samsung, and they can directly find out why it was caused. This happens when it thinks that you cancelled.
Method #2
This one will require you to lose all your data, but is mainly intended for those whom cannot reset their device. Download the stock firmware from the links below. Open Odin (Jodin3 will not work! It is not fully functioning, do not try it.) and boot device into Download/Odin mode. On your computer, you should see 'Added' in the logs. If this does not show up download the Samsung USB Drivers. Select AP and then select the stock firmware. Now flash it. This can also be done through TWRP
For bootloop and frozen Android/Carrier logo just do Method 2. You usually will keep all your data.
FOR 'VERIFICATION FAILED' YOU CANNOT RESTORE FROM A BACKUP!
FOR BOOTLOOPS AND FROZEN STARTUP SCREEN, YOU CAN!​
Downloads:
Samsung USB Drivers
7.1.1 Stock Firmware
Odin3 v3.12.10
Click to expand...
Click to collapse
I have a samsung j700t ud that had the 7.1.1 update installed from tmobile or samsung and it caused the to remain in a continual reboot loop until the battery of the phone dies. Will the methods above repair the issue?
Stuff I've tried:
1. Wipe cache
2. Called samsung and tmobile
3. Used samfirm to download firmware to use with odin that was successfully done but the reboot loop still remains.

smirk24 said:
I have a samsung j700t ud that had the 7.1.1 update installed from tmobile or samsung and it caused the to remain in a continual reboot loop until the battery of the phone dies. Will the methods above repair the issue?
Stuff I've tried:
1. Wipe cache
2. Called samsung and tmobile
3. Used samfirm to download firmware to use with odin that was successfully done but the reboot loop still remains.
Click to expand...
Click to collapse
Was the update sent out to you, or did you download it from SamMobile?
If the update was sent out to you I'm afraid I cannot help, but if you flashed it from SamMobile use an older version like Marshmallow or Lolipop.
EDIT: Make sure you factory reset device and wipe cache after installing from SamMobile.

TechNash said:
Was the update sent out to you, or did you download it from SamMobile?
If the update was sent out to you I'm afraid I cannot help, but if you flashed it from SamMobile use an older version like Marshmallow or Lolipop.
EDIT: Make sure you factory reset device and wipe cache after installing from SamMobile.
Click to expand...
Click to collapse
Id love to but i dont know how to get the marshmallow software and install it to the phone but id like to learn how.

How to recover from Verification Failed without losing data ?​Does installing TWRP via Oddin Works and does it able me to transfer my data after installing TWRP ? I dare not try doing it as i have never did it b4

Issue returning N6 to stock - I've done it all

Trying to give the mother in law my old N6. It was rooted / bootloader unlocked. First attempt was to factory reset from within the OS. That worked fine, until I rebooted... it wouldn't boot.
I then downloaded the Shamu factory images from Google's website (shamu-n6f27m-factory-bf5cce08) and ran the flash-all.bat script. Multiple errors showed up during the script... but I chalked it up to ADB looking for boot slots etc, whereas this one has none.
Phone booted fine. Installed apps, set up the phone, power cycled it and promptly entered a bootloop.
Ran flash.all again, phone booted fine. Flashed TWRP, booted into recovery, checked things out in there (didn't do anything but flash the TWRP) tried to reboot, phone bootloops.
Flashed TWRP, booted into Recovery, tried to erase system, etc.... multiple errors again. Booted into bootloader, ran Flash-all... phone boots. Installed some apps, rebooted phone and bootloop again.
Then I did something REALLY stupid, I locked the bootloader from ADB. Now I'm on the bootloader, but can't OEM unlock because it's asking me to boot into the OS and enable the ability from Developer options.
I've no idea why this phone is doing this - booting fine into the OS once and then getting into a bootloop every time thereafter.
If anyone can shed some light on this, I'd appreciate it. Also, how in the hell do I unlock the bootloader now that I've locked it and I can't boot into the OS or run the Flash-all.bat anymore since it's locked?

Is your recovery stock? If it is, sideload the last OTA from Google and that should get you back into Android so you can toggle the OEM Unlock button.

Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.

usafle said:
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
Click to expand...
Click to collapse
So did you finally figure out what it could have been that you were doing wrong?

Strephon Alkhalikoi said:
So did you finally figure out what it could have been that you were doing wrong?
Click to expand...
Click to collapse
No. I could only assume I had messed something up when I was using it back in the day and really hosed something up. System wouldn't wipe, cache wouldn't wipe, userdata wouldn't wipe in "fasboot" just kept getting "unable to find XXXX".
So multiple flashes into TWRP and bootloops trying to really REALLY wipe the device finally fixed it. I just kept erasing / wiping every partition I could find in Stock Recovery, TWRP, and with fastboot commands. Finally I got them all wiped/cleared and was able to flash the stock OS back on and have it 'stick'.