Develop Bugs

[ATT] Probably bricked my device

So the old ROM I was on (a super outdated Android Revolution) needed to be updated because my battery was draining a lot and I figured I would update everything. Apparently I flashed a bad or wrong version of TWRP, so I can't get into recovery. It just sits there trying to get into recovery but it keeps failing. Then I tried using MultiRom recovery and installing that through the app in the play store. Now my phone won't go into recovery and just boot loops. I can get into the HBOOT menu but I can't get into recovery or boot the device at all. Does anyone have any ideas to get a working recovery or working ROM? I already backed up my pictures and videos and stuff, but I forgot to transfer my titaniumbackup files I've been trying to look around and see how to fix it but I don't want to do something that will cause more damage than I've already done. I did all this to update my firmware so that I can use the newer ROMs. Anyway if anyone has any ideas I'm all ears.
Thanks in advance.

You didn't mention whether or not you are S-off and/or bootloader unlocked.
Since you already have a custom ROM, you must have unlocked your bootloader at some point, so if it is STILL unlocked, just reflash the correct recovery from fastboot. If it is not, unlock it with HTCdev first, then reflash the correct recovery.
Alternately, if you just want the phone fixed, you can always re-run the AT&T RUU - though that will trash any files you have on the phone.

Yeah that's what I did yesterday thanks for the response!

V410 7.0 LTE bricked

Ok guys I am pretty sure I fubar'd my tablet.
I am stuck in a recovery loop. When I start the tablet it just goes back into recovery. Which if I still had TWRP I think I could still do something, but I flashed cyanogen recovery trying to flash cm13 since I cold not get anything else to work. I cannot boot into download/firmware update screen. The screen just flickers a little and goes dark.
A little background:
Started when tablet forced install of 5.0 update and I was in a recovery loop. I flashed 410 test build, rooted, flashed twrp, installed stock rooted ROM. Everything was fine. Then tablet did it again, this time I just flashed rooted ROM and factory reset. Even took the steps to fix the white lines and storage issues. Was working fine. Got home a few days ago and I was in a recovery loop again. But now I don't have the bootloader screen/download mode/firmware update screen (whatever you want to call it) so last night i tried to download cm13, Gapps and cyanogen recovery with no avail.
I can access adb on my PC while in recovery, but when I try to access ADB shell I get unauthorized something or other. Because I cannot authorize USB debugging, because ROM won't boot. I tried to flash stock rooted ROM from cyanogen recovery and it says not signed or something like that.
Does anyone have any ideas? I really think I have screwed the pooch here.
sent from a device using an app

title
if you have a stock recovery image flashing it is easy, i had a LOT of troubles with my v410 and still am working with it. i have mine rooted, just with TWRP though, i cant use xposed framework, which negates why i rooted this in the first place. anyway, through much grit and determination flash your stock image after wiping what needs to be wiped and doing all other necessary things. Then, you must download kingo root, supersu, superuser. flashify would help with the flashing i hear, but it has troubles with the v410. kingo root was an apk i managed to find buried under a million viruses on the 34th page of google..or something. rooted mine in one click, from stock to reboot to twrp root.. many glitches.
I need help myself, deleted my "Phone" system app, causing me to lose connectivity with my data plan. cant seem to restore it, and flashify nor twrp has been able to flash a custom recovery, or a backup, im at a loss.
Help? We seek the same thing.

Ok but how do I flash the stock recovery image. I can't use fastboot. ADB says I am unauthorized.
sent from a device using an app

Anyone have any other ideas?
I am at a complete loss. I am by no means a developer, but I do know my way around. I really think I have FUBAR'd this one.

Kind of stinks, I give up. Anyone want a bricked v410?
Sent from my Galaxy Tab 2 using Tapatalk

Tried to unroot with SuperSU, please help.

I tried to unroot my phone with SuperSU.
My phone reset and all I get is a google logo screen and another screen that says "Your device is corrupt, it can't be trusted and may not work properly."
I can get into TWRP through recovery mode. Can anyone walk me through the steps to get my phone working again. I don't care if everything gets deleted and it's unrooted. I was trying to factory reset and unroot anyway.
Thanks for reading and any help or knowledge you can pass down.

poptrunks said:
I tried to unroot my phone with SuperSU.
My phone reset and all I get is a google logo screen and another screen that says "Your device is corrupt, it can't be trusted and may not work properly."
I can get into TWRP through recovery mode. Can anyone walk me through the steps to get my phone working again. I don't care if everything gets deleted and it's unrooted. I was trying to factory reset and unroot anyway.
Thanks for reading and any help or knowledge you can pass down.
Click to expand...
Click to collapse
Download the factory image that matches your OS. Use fastboot to flash the system and boot images. Follow section 9 of my guide:
https://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk

Thanks for the quick reply. Working on it, I'll check back in when I'm finished or if I have any problems.

I entered in the commands into my command promp listed in your guide #9.
It responds with "waiting for any device". I don't know if my path system is wrong or what. My computer does recognize my phone when it's plugged into the USB port but I cannot access any files to it directly from my PC.
Also, I do have an old back up on my PC I could restore. I just don't know how to transfer it from my computer onto my phone via TWRP.

Update. I flashed the factory image and fixed my phone. Just took some troubleshooting on moving some files around and using the command prompt.
Thanks SlimSnoopOS!

need your thoughts on twrp recovery

hi all
im experiencing some weird situations on my razer phone.
flash magisk via recovery works how ever if i try to do a factory reset or backup my phone via recovery or even restore from that backup the phone refuses to boot, it gets stuck on the razer screen for about 2 mins before rebooting into download mode.
manually changing the active partition doesn't help and the only way to fix it is to re-flash the stock firmware.
bootloader is unlocked and i have ran the "fastboot unlock-critical" command as well
has anyone had the same or similar issue

Try to follow the root instructions again, making sure you flash stock multiple times in the process like it says to. Otherwise I don't know what happened.

"Your device is corrupted and cannot be trusted" error. Nothing happens when connecting to PC

Please need urgent help. I had unlocked bootloader. While trying to update Magisk, my phone rebooted and got stuck on fastboot loop. Then while trying to flash TWRP using fastboot this "Your device is corrupted and cannot be trusted" error occured. I can't go into recovery, it just loops into this message. And my PC can't recognise the phone now at all. Please I need help. I have been trying to resolve this issue for hours now.

This is for Google Pixel 2 XL.

SonyXperiaSP said:
Please need urgent help. I had unlocked bootloader. While trying to update Magisk, my phone rebooted and got stuck on fastboot loop. Then while trying to flash TWRP using fastboot this "Your device is corrupted and cannot be trusted" error occured. I can't go into recovery, it just loops into this message. And my PC can't recognise the phone now at all. Please I need help. I have been trying to resolve this issue for hours now.
Click to expand...
Click to collapse
As long as you can get into the bootloader you're not dead in the water. Download the last factory image - NOT OTA image - from Google and flash it while in bootloader mode using ADB and Fastboot. That will return your device to its factory state. From there you can boot - NOT install - TWRP and install a custom ROM as well as root.

Strephon Alkhalikoi said:
As long as you can get into the bootloader you're not dead in the water. Download the last factory image - NOT OTA image - from Google and flash it while in bootloader mode using ADB and Fastboot. That will return your device to its factory state. From there you can boot - NOT install - TWRP and install a custom ROM as well as root.
Click to expand...
Click to collapse
First of all thank you for the reply. I don't know but I left the phone alone for couple of hours and right before seeing your post got into bootloader by pressing volume down and power key. Tried to flash TWRP and as soon as it flashed I got the exact same error like last time. I will now be following your method and install factory image. "NOT install - TWRP and Install a custom ROM", so I will not be installing TWRP this time.
I will post updates on what goes and hopefully will be able to flash the factory image without errors.

Thank you very much for the help Strephon. Really, really appreciate it. I am now able to boot into the OS and hopefully installing custom rom or rooting afterwards won't be an issue, Again, thank you very much.