Database Info

Failed Flash

I am updated on 4.1.2 on my razr maxx hd. I dont know what happen, but I lost root, I use moto chopper 1.1 used matts utility and i still cant get root back. I already have a Super user app on, but every time i try to root with the programs mention above it says its complete then after reboot i open up super user to update binary and it fails.
So anyways I figured well i might as well return to stock to get rid of the original root app and start over fresh.
Well I download the stock version of razr maxx hd rom. I get rid of getvar in the xml file, I open up RSD Lite (newest version) put my phone in fastboot mode. and try to flash back to stock. After I many failed attempts i always get this error
"Failed flashing process. 5/27 flash tz "tz.mbn" -> Phone returned FAIL.
On your phone:
Security downgraded version
update TZ version failed
preflash Validation failed for TZ "
My bootloader is locked never messed with it, I am on 4.1.2 android. I have downloaded all the stock roms and I always get this error

I would use THIS utitlity to flash back to stock. Then I would use that utility to root. Then I would use Voodoo root keeper to backup and disable root. Then I would update. Then I would use Voodoo to restore root. Then I would jump for joy. Then I would go about my life as usual.

mentose457 said:
I would use THIS utitlity to flash back to stock. Then I would use that utility to root. Then I would use Voodoo root keeper to backup and disable root. Then I would update. Then I would use Voodoo to restore root. Then I would jump for joy. Then I would go about my life as usual.
Click to expand...
Click to collapse
I look forward to jump for joy tonight when I can try this, I appreciate the help(fingers crossed) I'll try this tonight.

greatnesstx said:
I look forward to jump for joy tonight when I can try this, I appreciate the help(fingers crossed) I'll try this tonight.
Click to expand...
Click to collapse
Let us know how it goes. Another tip: If you are unable to get it to work, its the drivers. Even if you have downloaded them and installed them before, do it again.

Omg , that totally worked, I did get errors, but just left it alone and it flashed. Only thing thing that didn't work was the unlocked boot loader. But I am fine with that, since I don't flash roms on this phone
Sent from my Razr maxx hd

greatnesstx said:
Omg , that totally worked, I did get errors, but just left it alone and it flashed. Only thing thing that didn't work was the unlocked boot loader. But I am fine with that, since I don't flash roms on this phone
Sent from my Razr maxx hd
Click to expand...
Click to collapse
Since you took the OTA you are sol and will not be able to unlock your bootloader... ever. Sorry. However you do have a rooted phone and can say a dios to the bloatware and such.
Sent from my DROID RAZR HD using Tapatalk 4

Can't seem to get phone unbrick
mentose457 said:
Let us know how it goes. Another tip: If you are unable to get it to work, its the drivers. Even if you have downloaded them and installed them before, do it again.
Click to expand...
Click to collapse
So i'm getting this same error, but I have a Razr Hd, and its after i used that same utility to try and flash my phone back to stock rom.
Do you have any advice for me? I can't get out of it i try to power off my phone it goes back to the same Ap fastboot flash mode screen. Says "Fastboot Reason: Flash Failure"
Any help would be greatly appreciated

partial root?
STuGGG said:
So i'm getting this same error, but I have a Razr Hd, and its after i used that same utility to try and flash my phone back to stock rom.
Do you have any advice for me? I can't get out of it i try to power off my phone it goes back to the same Ap fastboot flash mode screen. Says "Fastboot Reason: Flash Failure"
Any help would be greatly appreciated
Click to expand...
Click to collapse
I rooted my RAZR HD using the latest Samsung method and got it to root on 4.1.2 build 9.30 but it got sick on the same screen. Happens every time I reboot my phone. I get past this by doing the following from the ap fast boot screen:
Press and hold power and both volume buttons. When phone turns off release power and keep holding both volume buttons. It will boot into recovery. Release volume buttons when this screen appears and wait a few seconds. Phone will boot like normal.
Still trying to search firms to find a reason for this but closest I can come to is either moto drivers or an issue with rooting and build 9.30. Hope this helps!

fix is here .. use option B method it works
http://forum.xda-developers.com/dro...-bricked-razr-m-4g-xt907-hd-preflash-t3135462
for only razr m xt907

vysionsTEchGHana said:
http://forum.xda-developers.com/dro...-bricked-razr-m-4g-xt907-hd-preflash-t3135462
for only razr m xt907
Click to expand...
Click to collapse
Wrong device, wrong forum, and the thread was dead 10 months ago.

De-bricking time!

Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!

killboredom said:
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
Click to expand...
Click to collapse
I think that's right. It's ridiculous that by locking things down and preventing us from unlocking bootloader Verizon actually causes bricks of this nature to occur. If you had an unlocked bootloader you'd be 100% fine right now.
Sent from my Nexus 7

There is a way. I posted in previous forum.
Use fastboot
Fastboot wipe cache
Fastboot wipe user data
Try this if not pm me and I will help you out one on one
That should fix your issue
Sent from my XT1080 using xda app-developers app

phositadc said:
I think that's right. It's ridiculous that by locking things down and preventing us from unlocking bootloader Verizon actually causes bricks of this nature to occur. If you had an unlocked bootloader you'd be 100% fine right now.
Sent from my Nexus 7
Click to expand...
Click to collapse
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too

codito said:
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
Click to expand...
Click to collapse
Ha...well there is that But what fun would that be?
The sad part is that the manufacturers could care less about giving us an unlocked bootloader. Android is a great ecosystem to play with and learn with and improve with. It's the carriers that are so paranoid about taking any tiny dent in their enormous profits that want to keep us locked out. So shame on them.
But, to be fair, I know the risks of the world we live in and this is my first brick in four Android phones, so I'm fine with it.

codito said:
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
Click to expand...
Click to collapse
My point was merely that it's somewhat ironic that, by trying to prevent bricks by locking bootloaders, Verizon actually causes some bricks that would be avoided with an unlocked bootloader.
Not saying anything about whether what he was doing is right or wrong, or whether Verizon prevents more bricks than it causes.
Sent from my Nexus 7
Edit: but you've got to wonder. Are you more likely to brick using one of these crazy complicated methods we have to use to get around Verizon security? Or using fastboot OEM unlock + flash superuser. I bet per hundred rooted phones, less Nexus's (and other unlockable phones) are bricked than phones that are tightly locked down. Pure speculation of course.

killboredom said:
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
Click to expand...
Click to collapse
It sounds like you're actually stuck partially on JB, partially on KK, hence why you're bootlooping. I had a very similar issue when I tried to install the KK update through update.zip .......... after a couple hours, I finally got it back up and running.
My method - use the Method 2 Manual flash steps I posted in Dev section here - http://forum.xda-developers.com/showthread.php?t=2580060
Let me know if it works. I had problems at first, but that should cover it. Getting system to flash was actually the hardest part

Pixel XL Verizon bricking problems.

I'm currently on my 4th replacement from Verizon. Everytime the phone has either went into an endless bootloader loop where clicking start takes me back to the bootloader and when going to recovery it says "failed to boot to recovery" or turned off and wouldn't turn back on and essentially becomes a bricked phone. Is there anyone else with this problem?
Edit- I'm on stock Android 7.1.1 and not rooted.

Timtube said:
I'm currently on my 4th replacement from Verizon. Everytime the phone has either went into an endless bootloader loop where clicking start takes me back to the bootloader and when going to recovery it says "failed to boot to recovery" or turned off and wouldn't turn back on and essentially becomes a bricked phone. Is there anyone else with this problem?
Click to expand...
Click to collapse
Did it work in the Verizon store? I've perhaps seen this once or twice but a replacement device usually worked. But 4 devices? That just doesn't seem real. Not that you're making it up but you need to explain what you are doing before the device goes into a boot loop. Worst case scenario, go to a store and make sure the phone works before you leave.

Weird sounds like you are trying to use depixel8 on an unsupported firmware? And you are bootlooping the phone ?

happened to me on my first device, partly why i havent SU or TWRP yet....just unlocked for future fun...
Mine bricked inbetween twrp and SU....but im sure i messed up somewhere. TWRP worked but as soon as i did SU, it all went wrong for me.....Figured id wait to more stable stuff is out, before messing around again.
mine did the same thing as what your describing...
peace
byte

I did not unlock the bootloader. I am not rooted. I am using stock Verizon Pixel XL 7.1.1.

well that changes everything, sounds like just bad luck dude

bytethegroove said:
well that changes everything, sounds like just bad luck dude
Click to expand...
Click to collapse
I know it sucks. I really like the phone when it works.

I think i killed my device

So its been a while since I've been to xda so I hope I'm posting this in the right section.
Just so you know, I realize that what I did I will probably never be able to fix, I just want to make sure before I go before google on my knees and beg for mercy. I'm also aware that what I did is so stupid and unforgivable that I should never be allowed to root a device ever again. With that out of the way, here is my problem.
I just had my pixel replaced after my previous one had hardware problems, that are irreverent to this topic. I was setting it up to be my daily driver again, so I unlocked the bootloader, rooted it, loaded a few systemUI mods and the elementalx kernel. I had it working really well, but one thing was bugging me. That stupid notification that you get every time you boot up with the bootloader unlocked. I hated it. I got to thinking about it today, and I thought "Could it be possible to relock the bootloader with the changes that I made and have it still work?" I was thinking that once the mods were put in, it shouldn't matter whether or not the bootloader was unlocked or not cause the changes were already made. So I did the unthinkable and relocked my bootloader after I did all the stuff listed above.
So yes I major bricked my device by doing this, and yes I'm a major idiot for thinking that locking the bootloader was an OK thing to do. I can still get into fastboot mode, but thats it. When I try to boot into the system, it flashes the splash screen for about .5 seconds then goes black for 2 seconds then repeats. It does the same thing in recovery mode so adb side loading firmware is out of the question. I can't use fastboot boot whatever.img cause the bootloader is locked. I can't fastboot wipe userdata or mess with the system in any way via fastboot. And to top it all off, I cant reunlock the bootloader because it requires that an option be checked in the system that I now can't boot into.
This is a last ditch effort to see if I can fix this device myself, or if I need to go to google and pray they let me rma my device a second time
Any Ideas?

-MightyMouse- said:
So its been a while since I've been to xda so I hope I'm posting this in the right section.
Just so you know, I realize that what I did I will probably never be able to fix, I just want to make sure before I go before google on my knees and beg for mercy. I'm also aware that what I did is so stupid and unforgivable that I should never be allowed to root a device ever again. With that out of the way, here is my problem.
I just had my pixel replaced after my previous one had hardware problems, that are irreverent to this topic. I was setting it up to be my daily driver again, so I unlocked the bootloader, rooted it, loaded a few systemUI mods and the elementalx kernel. I had it working really well, but one thing was bugging me. That stupid notification that you get every time you boot up with the bootloader unlocked. I hated it. I got to thinking about it today, and I thought "Could it be possible to relock the bootloader with the changes that I made and have it still work?" I was thinking that once the mods were put in, it shouldn't matter whether or not the bootloader was unlocked or not cause the changes were already made. So I did the unthinkable and relocked my bootloader after I did all the stuff listed above.
So yes I major bricked my device by doing this, and yes I'm a major idiot for thinking that locking the bootloader was an OK thing to do. I can still get into fastboot mode, but thats it. When I try to boot into the system, it flashes the splash screen for about .5 seconds then goes black for 2 seconds then repeats. It does the same thing in recovery mode so adb side loading firmware is out of the question. I can't use fastboot boot whatever.img cause the bootloader is locked. I can't fastboot wipe userdata or mess with the system in any way via fastboot. And to top it all off, I cant reunlock the bootloader because it requires that an option be checked in the system that I now can't boot into.
This is a last ditch effort to see if I can fix this device myself, or if I need to go to google and pray they let me rma my device a second time
Any Ideas?
Click to expand...
Click to collapse
Well I'm not sure of this, but can't you unlock your bootloader through adb? If so then just flash the stock image.. I also saw a post somewhere about restoring your phone with a locked bootloader. Again this is just a suggestion but worth looking into.

-MightyMouse- said:
Any Ideas?
Click to expand...
Click to collapse
I'll not chastise you for what you did, I've locked the bl after making changes too although I never did care about the splash screen. I just don't look at it after a reboot, hold it until it vibrates and then log in. But I understand you not liking is since I've seen other posts about trying to get rid of it. But... your only mistake was flipping the OEM unlock switch. You could have relocked the bl with that switch still enabled and not have the splash screen any longer.
So at this point you have to beg for a replacement. I don't think they'll give you a hard time about it if you're honest as you were here. You might get some suggestions from others so good luck. You did try to factory reset in recovery right? Oh just looked and you can't get into recovery. What happens when you try from bl menu? You don't even see the android little guy saying "no command"?

quinejh said:
Well I'm not sure of this, but can't you unlock your bootloader through adb? If so then just flash the stock image.. I also saw a post somewhere about restoring your phone with a locked bootloader. Again this is just a suggestion but worth looking into.
Click to expand...
Click to collapse
Thanks for answering. I had looked into this, but the only way that you could do that is adb sideloading an ota from google. That can only be done by the recovery which is now borked.
bobby janow said:
I'll not chastise you for what you did, I've locked the bl after making changes too although I never did care about the splash screen. I just don't look at it after a reboot, hold it until it vibrates and then log in. But I understand you not liking is since I've seen other posts about trying to get rid of it. But... your only mistake was flipping the OEM unlock switch. You could have relocked the bl with that switch still enabled and not have the splash screen any longer.
So at this point you have to beg for a replacement. I don't think they'll give you a hard time about it if you're honest as you were here. You might get some suggestions from others so good luck. You did try to factory reset in recovery right? Oh just looked and you can't get into recovery. What happens when you try from bl menu? You don't even see the android little guy saying "no command"?
Click to expand...
Click to collapse
What makes me really mad is that I never disabled OEM unlock. That being said, I did see that is was disabled in settings and didn't think anything of it. I can't get into recovery at all, even through the bootloader. My guess is I borked the image that the recovery was put on as well as the system and probably a couple others. Something I know I could fix if the boot loader wasn't locked. Well I think I will get the ball rolling on an RMA then.

@-MightyMouse- When you have bootloader unlocked the option is grayed out and thereby disabled. But it does say bootloader is already unlocked so no action is needed. If you didn't switch it back over then there really is no reason that it should be disabled in the settings. When did you see it disabled if you can't get into the system? And what happens when you type the unlock command from bootloader menu? I'm locked but I think it's something like fastboot oem unlock or maybe it's changed. What does the screen say? I'm sure you tried it but I'm just curious.

bobby janow said:
@-MightyMouse- When you have bootloader unlocked the option is grayed out and thereby disabled. But it does say bootloader is already unlocked so no action is needed. If you didn't switch it back over then there really is no reason that it should be disabled in the settings. When did you see it disabled if you can't get into the system? And what happens when you type the unlock command from bootloader menu? I'm locked but I think it's something like fastboot oem unlock or maybe it's changed. What does the screen say? I'm sure you tried it but I'm just curious.
Click to expand...
Click to collapse
That was the first thing I tried. I forget what it said, but I do remember that it wouldn't let me. No matter, I already got it RMA'ed but have to wait till Monday to ship it off.

-MightyMouse- said:
That was the first thing I tried. I forget what it said, but I do remember that it wouldn't let me. No matter, I already got it RMA'ed but have to wait till Monday to ship it off.
Click to expand...
Click to collapse
Ok cool. Good luck.
Sent from my Pixel using XDA-Developers Legacy app

-MightyMouse- said:
That was the first thing I tried. I forget what it said, but I do remember that it wouldn't let me. No matter, I already got it RMA'ed but have to wait till Monday to ship it off.
Click to expand...
Click to collapse
So, what error shows up when you try - fastboot flashing unlock ?
After you somehow manage to unlock BL, you could try using the flash-all.bat script to quickly begin to push the images....
Edit: nvm. I see you have gone through a RMA again.

NoobInToto said:
So, what error shows up when you try - fastboot flashing unlock ?
After you somehow manage to unlock BL, you could try using the flash-all.bat script to quickly begin to push the images....
Edit: nvm. I see you have gone through a RMA again.
Click to expand...
Click to collapse
The error was something like option unavailable. Went through the RMA process which was surprisingly good. Every time I've gone through it, they never ask more than one or two questions before they ask for my imei and tell me that my device could be replaced, which is great, because if I can't fix it, it just needs to be replaced anyways. In other news I got my third pixel just a couple hours ago so hopefully this one lasts me longer than a day.

Sprint version bricked?

Recently tried to unroot due to issues with the vibrate motor not working for any notifications or anything. Also, apps started to fail more frequently it was all just becoming a big headache. I had thought for sure I enabled OEM unlocking but at this point its obvious I did not. Currently I can not get phone to boot besides to the encryption page and no idea what pin code would be. I have tried everything imaginable under the sun. In adb I ran the oem unlock string which caused all these issues. If I try to boot into recovery I get the message "Your device is corrupt. It cant be trusted and will not boot". If I try to boot normally i get the message "Your device has loaded a different operating system" then boots to the encryption lock page. I have placed the RUU and other files and attempted the SD card way of running the files to no avail. Does anyone have any other advice to getting this thing back on?
Edit: this can be closed. I flashed nearly every file I could find but nothing would take. Doing it both the adb and SD card method. Finally, I found the zip that the phone finally liked and it finally flashed. OH man cant be any happier to finally have my baby back on. Anyone else become stuck in this issue, just do as others have said, find the correct zip, flash it, and all will be ok.

mbaseball3 said:
Recently tried to unroot due to issues with the vibrate motor not working for any notifications or anything. Also, apps started to fail more frequently it was all just becoming a big headache. I had thought for sure I enabled OEM unlocking but at this point its obvious I did not. Currently I can not get phone to boot besides to the encryption page and no idea what pin code would be. I have tried everything imaginable under the sun. In adb I ran the oem unlock string which caused all these issues. If I try to boot into recovery I get the message "Your device is corrupt. It cant be trusted and will not boot". If I try to boot normally i get the message "Your device has loaded a different operating system" then boots to the encryption lock page. I have placed the RUU and other files and attempted the SD card way of running the files to no avail. Does anyone have any other advice to getting this thing back on?
Edit: this can be closed. I flashed nearly every file I could find but nothing would take. Doing it both the adb and SD card method. Finally, I found the zip that the phone finally liked and it finally flashed. OH man cant be any happier to finally have my baby back on. Anyone else become stuck in this issue, just do as others have said, find the correct zip, flash it, and all will be ok.
Click to expand...
Click to collapse
I'm in this predicament at the moment. I am not able to find the zip file with the same OS as my phone (2.42.617.6)
I am looking at this spreadsheet to locate the correct zip file. Could anyone help me, please? Thanks.
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0

mauiblue said:
I'm in this predicament at the moment. I am not able to find the zip file with the same OS as my phone (2.42.617.6)
I am looking at this spreadsheet to locate the correct zip file. Could anyone help me, please? Thanks.
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
38 or 39 should work. The last octet doesn't matter as that is just sub version. So long as the first 3 octets match ie 2.42.617, your good to go.

shivadow said:
38 or 39 should work. The last octet doesn't matter as that is just sub version. So long as the first 3 octets match ie 2.42.617, your good to go.
Click to expand...
Click to collapse
Thanks shivadow for responding to my post. So I downloaded one of the one of the latest versions (from the zip variant link) and renamed it "firmware.zip" I am using ADB to do the process (https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048) and I get this error:
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 2399200000 bytes
error: cannot load 'firmware.zip'
I renamed it a couple other times and I still get that error above. My phone (U11) is in the download mode. Just for giggles when I type in on the command prompt "fastboot oem rebootRUU" I get to a screen that has HTC on it and says and the warning "Security Warning. If you flash this phone with any ROM that was not officially released by HTC you take the risk of releasing...." When I give the command to flash the zip file I get the same error as above.
I am hopeful that I can get this phone back to normal running status. I just need to get the right commands and files to do this.
I appreciate any and all help to get my phone back to normal again. Aloha.

Sorry just saw all the updates. Notifications turned off apparently. Since I was able to get phone back on I can say it's not like it used to. I've tried to run the RUU which fails every time. And my signal has turned to absolute crap; constant dropped signal and barely any LTE. So, I'm no help since all I've done is get the phone on but not working properly lol.
mauiblue said:
I'm in this predicament at the moment. I am not able to find the zip file with the same OS as my phone (2.42.617.6)
I am looking at this spreadsheet to locate the correct zip file. Could anyone help me, please? Thanks.
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
Sent from my 2PZC5 using Tapatalk

mbaseball3 said:
Sorry just saw all the updates. Notifications turned off apparently. Since I was able to get phone back on I can say it's not like it used to. I've tried to run the RUU which fails every time. And my signal has turned to absolute crap; constant dropped signal and barely any LTE. So, I'm no help since all I've done is get the phone on but not working properly lol.
Sent from my 2PZC5 using Tapatalk
Click to expand...
Click to collapse
Aloha and thanks for taking the time to respond. Well you got farther than me as I was not able to get my phone out of trouble. Tomorrow will make two weeks since I sent my phone out to HTC. I just got the new HTC U12+ yesterday as I can't go without a reliable set because I need one for my jobs.
Next time if I do unlock the bootloader on any phone I will figure out how to do the process of rooting, updating, and not bricking the phone.
I hope you sort things out with your phone.
Sent from my HTC U12+ using Tapatalk

I'm not sure about getting further when it feels messed up still, ha. Yeah I get ya though, had the same experience freaking out that I wouldn't have a phone for work. Fortunately I had my cracked screen m10 that served as a backup until I was able to get the u11 to boot. I swear the last phones I rooted were less hassle than these more complex devices. Hope HTC can get it figured out for you.
mauiblue said:
Aloha and thanks for taking the time to respond. Well you got farther than me as I was not able to get my phone out of trouble. Tomorrow will make two weeks since I sent my phone out to HTC. I just got the new HTC U12+ yesterday as I can't go without a reliable set because I need one for my jobs.
Next time if I do unlock the bootloader on any phone I will figure out how to do the process of rooting, updating, and not bricking the phone.
I hope you sort things out with your phone.
Sent from my HTC U12+ using Tapatalk
Click to expand...
Click to collapse
Sent from my 2PZC5 using Tapatalk

I agree that the past phones were not so hard to unlock, root, update, and tweak. Now with the U12+ dual A/B slot partition and multiple files that are needed to root the phone it can be overwhelming.
I'm sure HTC will be able fix the phone but at what cost? I'm just waiting it out and hoping for the best.
Aloha!
Sent from my HTC U12+ using Tapatalk