Related
Please help urgently! So I just S-OFF'd my phone (right after unlocking my bootloader via htcdev) and I was excited to finally manually flash a 5.1 update to my EE UK One m9. I sort of made it a European version by changing one of its update numbers to [BLANK].401.[BLANK]. I then spent the whole night booting my phone into download mode and using fastboot commands: "htc_fastboot flash zip...".
Each zip was the previous update to the other, I.e. I was already on 1.32.401.6, so I used fastboot to get to 1.32.401.8 as the cmd. prompt said that it was successfully installed on my phone (p.s. I didn't have an sd card big enough to exfat 32 and put the update zips on it). I then repeated the steps again, but then fastboot flashed "2.10.401.", this was the update that would hopefully bring my phone to 5.1 . The cmd. prompt said that it was a success so I booted my phone up as normal, but I went to the settings to check software information and it was still on 1.32.401.6! It then said an update was ready to install so I just installed it as normal. Once it went into the bootloader it flashed it without any problems and tried to boot back up again. It then lit up a blue screen for 10 seconds and then went into the black HTC RUU screen with the grey htc logo. My phone has now, for the last hour, been stuck in this infinite loop of blue screen, vibrate, ruu screen and REPEAT. I've tried pressing vol. down and power as well as up to get into other modes like download mode, but it doesn't work. I CAN'T EVEN TURN IT OFF! I HAVE TO WAIT FOR IT TO RUN OUT OF BATTERY! MORE IMPORTANTLY, ADB DOESNT RECOGNISE IT, NOR DOES FASTBOOT!!!! SO I CAN'T EVEN FLASH A STOCK RECOVERY, SYSTEM IMG, ETC! PLEASE IF ANYONE CAN, HELP ME. I REALLY DON'T WANT TO HAVE TO BUY A NEW ONE AND PAY S-OFF AGAIN!
Louis118 said:
Please help urgently! So I just S-OFF'd my phone and I was excited to finally manually flash a 5.1 update to my EE UK One m9. I sort of made it a European version by changing one of its update numbers to [BLANK].401.[BLANK]. I then spent the whole night booting my phone into download mode and using fastboot commands: "htc_fastboot flash zip...".
Each zip was the previous update to the other, I.e. I was already on 1.32.401.6, so I used fastboot to get to 1.32.401.8 as the cmd. prompt said that it was successfully installed on my phone (p.s. I didn't have an sd card big enough to exfat 32 and put the update zips on it). I then repeated the steps again, but then fastboot flashed "2.10.401.", this was the update that would hopefully bring my phone to 5.1 . The cmd. prompt said that it was a success so I booted my phone up as normal, but I went to the settings to check software information and it was still on 1.32.401.6! It then said an update was ready to install so I just installed it as normal. Once it went into the bootloader it flashed it without any problems and tried to boot back up again. It then lit up a blue screen for 10 seconds and then went into the black HTC RUU screen with the grey htc logo. My phone has now, for the last hour, been stuck in this infinite loop of blue screen, vibrate, ruu screen and REPEAT. I've tried pressing vol. down and power as well as up to get into other modes like download mode, but it doesn't work. I CAN'T EVEN TURN IT OFF! I HAVE TO WAIT FOR IT TO RUN OUT OF BATTERY! MORE IMPORTANTLY, ADB DOESNT RECOGNISE IT, NOR DOES FASTBOOT!!!! SO I CAN'T EVEN FLASH A STOCK RECOVERY, SYSTEM IMG, ETC! PLEASE IF ANYONE CAN, HELP ME. I REALLY DON'T WANT TO HAVE TO BUY A NEW ONE AND PAY S-OFF AGAIN!
Click to expand...
Click to collapse
hold power and vol up and vol down all at the same time will get you to bootloader, we hope
Aldo101t said:
hold power and vol up and vol down all at the same time will get you to bootloader, we hope
Click to expand...
Click to collapse
That helped thanks, but I still can't boot into anything else... I'm pretty sure I can't install anything through fastboot without download or run mode...
Louis118 said:
That helped thanks, but I still can't boot into anything else... I'm pretty sure I can't install anything through fastboot without download or run mode...
Click to expand...
Click to collapse
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Aldo101t said:
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Click to expand...
Click to collapse
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Aldo101t said:
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Click to expand...
Click to collapse
what you should do is if you can restore a backup, put a 5.1 rom on your sd card and after you flash the latest firmware 2.10.401.xx. then boot to recovery and install the 5.1 rom.
---------- Post added at 07:43 PM ---------- Previous post was at 07:41 PM ----------
Louis118 said:
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Click to expand...
Click to collapse
you still have TWRP INSTALLED, do you have a backup.
Aldo101t said:
what you should do is if you can restore a backup, put a 5.1 rom on your sd card and after you flash the latest firmware 2.10.401.xx. then boot to recovery and install the 5.1 rom.
---------- Post added at 07:43 PM ---------- Previous post was at 07:41 PM ----------
you still have TWRP INSTALLED, do you have a backup.
Click to expand...
Click to collapse
How do you expect me to boot into it? I told you, pressing any other mode besides power off, causes the blue screen loop
Louis118 said:
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Click to expand...
Click to collapse
try powering it off then go back to bootloader and try to get to recovery again
Aldo101t said:
try powering it off then go back to bootloader and try to get to recovery again
Click to expand...
Click to collapse
Nope, still does the blue loop.
Louis118 said:
Nope, still does the blue loop.
Click to expand...
Click to collapse
well, that's the sh^ts, I don't know at this point.maybe someone else can chime in here that can help.
I've seen this before, and there is no fix that I'm aware of. You've corrupted something important in your firmware, probably by flashing all those firmware packages.
You made several mistakes here, the first in thinking you needed to flash every firmware for your phone. All you needed was the last one. The other mistake was confusing your OS version with your firmware version. You were still on 1.32 base but your firmware was updated.
The last mistake, and the one that probably did the damage, was trying to take an OTA after all that. You were stock enough for it to run, but since your firmware was already updated, the OTA broke something.
As far as I know, the only thing you can do is return it to HTC for service.
Sent from my HTC One M9 using Tapatalk
iElvis said:
I've seen this before, and there is no fix that I'm aware of. You've corrupted something important in your firmware, probably by flashing all those firmware packages.
You made several mistakes here, the first in thinking you needed to flash every firmware for your phone. All you needed was the last one. The other mistake was confusing your OS version with your firmware version. You were still on 1.32 base but your firmware was updated.
The last mistake, and the one that probably did the damage, was trying to take an OTA after all that. You were stock enough for it to run, but since your firmware was already updated, the OTA broke something.
As far as I know, the only thing you can do is return it to HTC for service.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help anyway. Also, I got this under contract from EE, so do I have UH OH protection automatically from htc? Or will it cost me to get it serviced?
Louis118 said:
Thanks for trying to help anyway. Also, I got this under contract from EE, so do I have UH OH protection automatically from htc? Or will it cost me to get it serviced?
Click to expand...
Click to collapse
Uh Oh protection isn't available in the UK.
As you unlocked your bootloader and got S-OFF, they will almost certainly charge you for repairs as this isn't a hardware issue and was actually caused by you flashing your phone.
Sent from my HTC One M9 using Tapatalk
Questions............
Did u install any recovery like twrp?
Did you root?
Post pictures of bootloader/try to post any other screen you may be able to enter
LLegion said:
Questions............
Did u install any recovery like twrp?
Did you root?
Post pictures of bootloader/try to post any other screen you may be able to enter
Click to expand...
Click to collapse
I'm able to enter the boot loader menu (with the options to reboot, power down, download mode and bootloader). Unfortunately, clicking any of the options (apart from power down) causes the blue screen boot loop to continue.
This wasn't really Crazy you now All You have to do is go to the bootloader menu and from there Ashley you can actually flash the Recovery ebusiness Leave me and if you don't believe me godaddy redirect link to the Team Win recovery project Website Just follow the instructions to flash recovery as they say
---------- Post added at 05:17 PM ---------- Previous post was at 05:13 PM ----------
You can flash recovery from bootloader menu i did that way when by mistake did erease all my internal card including system.img.....i was lost my phone didnt boot line yours also getting the bluescreen and voilaaa!!! I did flash on bootloader menu but download the 2.8.7.1 beta here the proof link....https://twrp.me/devices/htconem9.html
LLegion said:
This wasn't really Crazy you now All You have to do is go to the bootloader menu and from there Ashley you can actually flash the Recovery ebusiness Leave me and if you don't believe me godaddy redirect link to the Team Win recovery project Website Just follow the instructions to flash recovery as they say
---------- Post added at 05:17 PM ---------- Previous post was at 05:13 PM ----------
You can flash recovery from bootloader menu i did that way when by mistake did erease all my internal card including system.img.....i was lost my phone didnt boot line yours also getting the bluescreen and voilaaa!!! I did flash on bootloader menu but download the 2.8.7.1 beta here the proof link....https://twrp.me/devices/htconem9.html
Click to expand...
Click to collapse
I flashed the recovery file successfully (according to the command window) but when I click the "reboot recovery mode" option it brings up the red development text and then goes back into the bluescreen loop.
Louis118 said:
I flashed the recovery file successfully (according to the command window) but when I click the "reboot recovery mode" option it brings up the red development text and then goes back into the bluescreen loop.
Click to expand...
Click to collapse
You said before that fastboot wasn't working. It's working now? Does it show up in fastboot devices?
If so, you might try running a RUU from bootloader.
The trixk is to flash and just after reboot press power and down vol to wnter immediatly into rexovery twrp just as it says in the link...just do it and will go into twrp once you have entered justflash any nandroid or flash a zip ruu from sd card in a sexond boot
I'm not able to enter RUU mode...
Hi all,
I apologize if opening a new thread as first post but I did that after an extensive research and I noticed the questions in the sticky are 4 days old.
I purchased a soft bricked Asus Zenfone 2 ZE551ML Z00AD for fairly cheap as I needed a decent dual-sim phone.
Initially it was just stuck on the first asus screen and nothing more - not even spinning wheel. It would not go in recovery mode with vol+ and power, nor vibrate.
Tried to adb / fastboot but even when adb was listing the device ok, fastboot would just say "Waiting for device"
Leaving the phone connected to PC I noticed it was rebooting by itself after a few minutes and leaving it alone for about 15 mins it went in a TWRP 3.0.0.0 screen - was probably installed before....
From there I wiped everything and managed to install latest image that I downloaded from Asus site - UL-Z00A-WW-2.20.40.183-user.zip by using an SD card. Nothing else installed
The phone booted up just fine after this - I had some troubles with the Asus Cover screen going on/off every second but I managed to turn it off - proximity sensor and light sensor tested ok. It is not rooted now.
I have a few problem though and I need your expertise and advice.
1. There is absolutely no sound from it. Speaker test in normal and Safe mode stays silent. There is sound through the headset.
2. I does not detect any SIM card in either Slot 1 or 2
2. Screen never goes off unless I press the power button - display set to 1 min and lock to swipe.
3. Storage only shows 16Gb while it should show 64GB
Given the issue described I would suspect this is still a firmware/software issue but I would like someone with experience to confirm and hopefully advise a few steps.
Thanks!
Can you get into bootloader now?
Sent from my SM-T710 using Tapatalk
---------- Post added at 09:26 PM ---------- Previous post was at 09:15 PM ----------
I agree that this sounds like a software issue and if it was my phone I would take the following steps.
1. hard reset
2. Download the pre rooted software that shakalaka provides, you'll find it in the thread for flashing from cn to ww in this forum it also gives all instructions for downloading, prep & flashing.
3. Flash through bootloader everything but the bootloader
4. Reboot and it should work fine, this is the procedure I have always had to follow whenever my Zenny won't find the Sim card.
5. Let us know how that worked for you?
Sent from my SM-T710 using Tapatalk
yes I can - TWRP is still active - I installed an older firmware from Asus website - 139 but the cover flicker is much worse and I got it stuck on now
I have to reload it again
Thanks for the tip = I will try that as well if older firmware fails too
Edit - older firmware did not fix anything - trying your route next
EDIT2 - after another 3h on 2 PC's still cant make fastboot to work. I will try tomorrow on another one
What are you getting with fastboot? Error msg? You need to flash .183, if you want to flash earlier you have to change the boot loader to earlier edition
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 12:39 PM ---------- Previous post was at 12:39 PM ----------
Forget term it will not help you it is part of the problem
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 12:40 PM ---------- Previous post was at 12:39 PM ----------
Not term, twrp
Sent from my ASUS_Z00AD using Tapatalk
so far I tried:
UL-Z00A-WW-2.20.40.183-user.zip - the only one usable with the original problems - sound, SIM, storage space, screen
UL-Z00A-WW-2.20.40.139-user.zip - Asus cover flicker makes it aamost imposible to reach the normal screen
UL-Z00A-WW-2.12.40.11-user.zip - not booting - stuck at first android screen then rebooting itself until it goes in TWRP
cm-13.0-20160512-NIGHTLY-Z00A.zip - won't install from TWRP
things got worse though
Used xFSTK - and after a few unsuccessful tries I got stuck on the TV 4 color screen with no bootloader anymore and cannot reach fastboot anymore and TWRP is gone. FW will load in xFSTK but not the OS image - seems problem is more common - and the issue is that there is no proper file with signature for my Z00AD available anywhere.
I tried Asus Flash tool as well - there are only 3 raw images I was able to find but none will match the device and it will not show up.
Also tried Intel Flash tool - That will see the phone but could not find any flash.xml for it.
Now I don't have any way to use adb and will have to wait until a proper droidboot_dnx.img.POS_sign.bin or .raw image is released somewhere...
If I find any other solution I will post it here
I do not understand why you continued to try to flash a zip through twrp, I specifically told you that it would not work and you have now made fastboot, you're only way to solve this problem, inaccessible. If you have any hope of rescuing now it will have to be with flashing the raw image, but frankly I think you have little possibility of that working now.... situations such as yours can almost never be solved with recovery, you almost always have to use fastboot, so good luck, I have no other solutions and you are likely in need of a new device.
Sent from my ASUS_Z00AD using Tapatalk
@jimchee I am also having a "no sim-no sound error". My device is YU YUREKA +, Tried to flash it with custom rom 'firehound' but didn't got any luck with the issue.
Jimchee what do you suggest(please answer in little detail as i am kinda noob when it comes to this) I flashed using twrp
Thanks in advance
Don't know that device at all and never heard of that rom so I have no advice for you sorry
Sent from my LG-D693n using Tapatalk
So i flashed beta 8, then flashed superSU but for some reason it didnt detect my sim card. I then tried to flash oos 3.2.7,wiping everything but now its stuck at "formating cache using make_ext4fs" or something like that (my TWRP is not in english). It doesnt react to anything,turning off with the power button or anything like that.
Also the screen doesnt react. Is there any way for me to even turn it off?
You can force shut off the phone by holding the power button for around 10 seconds or so! If you're able to get into TWRP, you could do a standard wipe and then flash the latest stable OOS, and work from there. If you can't even get into TWRP, then refer to Mega Unbrick Guide. That's the be-all-end all solution though, so if anyone's got any better ideas fire away.
After shutting off, can you get into the bootloader by holding volume up and power? If so, could try reflashing your recovery. Also idk if beta 8 is the same as cm14.1 but I had to get a community build of twrp because official twrp broke after installing it. I don't have a link, will search, or maybe one of the nice folks here will get a link up for you before I manage to
Sent from my ONEPLUS A3000 using Tapatalk
https://drive.google.com/file/d/0BxwctkW79popV09feDJFX2RUT2M/view?usp=drivesdk
Thank ya JazzieBoi. Let me know how it goes Zsomer, feel free to pm me also
Edit: jazzyboi linked to 3.0.2-1.22, here is a link to 3.0.2-1.28
http://forum.xda-developers.com/devdb/project/dl/?id=21835&task=get
Sent from my ONEPLUS A3000 using Tapatalk
My Pixel XL is now dead. Won't turn on when pressing or long pressing or long pressing the power button for 5 minutes.
Long pressing the volume down and power button leads to vibration feedback but the screen is black, can't even get to the bootloader.
Last thing before it bricked is browsing through my photos, my phone suddenly froze as usual. And then it powered off automatically. After that, I can't get into the system, neither the bootloader.
Anybody know how to fix hard bricked Pixel?
Thx.
Queentus said:
My Pixel XL is now dead. Won't turn on when pressing or long pressing or long pressing the power button for 5 minutes.
Long pressing the volume down and power button leads to vibration feedback but the screen is black, can't even get to the bootloader.
Last thing before it bricked is browsing through my photos, my phone suddenly froze as usual. And then it powered off automatically. After that, I can't get into the system, neither the bootloader.
Anybody know how to fix hard bricked Pixel?
Thx.
Click to expand...
Click to collapse
try this one here
if not, call harware support for a possible rma
reyscott said:
try this one here
if not, call harware support for a possible rma
Click to expand...
Click to collapse
Won't work cause I can't even get to the bootloader. Thx anyway.
call google support to initiate RMA.
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
CZ Eddie said:
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
Click to expand...
Click to collapse
Thanks for the reply.
My Pixel is already on it's way to RMA.
My Pixel XL shut down this morning. After several attempts to restart, it hung on the Google splash screen. I got into bootloader and tried to reflash OPR3 with flash-all.bat. It got a little ways but quit with “remote: flash write failure”. I got into bootloader again and tried the reflash again. It got the same error earlier in the process and ever since, no button combinations will get it to turn on and I get no lights or battery image when plugged in.
When I plug it into my computer, I get the connection beep from the computer, but no evidence of a connection in Device Manager or in remove media. Since my computer recognizes the phone somehow, is there a way to retrieve data from my phone? I have seen many references to programs that can do this, but I am skeptical. My warranty replacement has been ordered, but I'd like to get whatever I can before it gets here.
Same thing happened to me last night. RMA is on its way, but this month old Pixel XL is dead.
CZ Eddie said:
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
Click to expand...
Click to collapse
do you have an advanced guide to fix it? I have pixel past warranty that has the same problem
JimSmith94 said:
My Pixel XL shut down this morning. After several attempts to restart, it hung on the Google splash screen. I got into bootloader and tried to reflash OPR3 with flash-all.bat. It got a little ways but quit with “remote: flash write failure”. I got into bootloader again and tried the reflash again. It got the same error earlier in the process and ever since, no button combinations will get it to turn on and I get no lights or battery image when plugged in.
When I plug it into my computer, I get the connection beep from the computer, but no evidence of a connection in Device Manager or in remove media. Since my computer recognizes the phone somehow, is there a way to retrieve data from my phone? I have seen many references to programs that can do this, but I am skeptical. My warranty replacement has been ordered, but I'd like to get whatever I can before it gets here.
Click to expand...
Click to collapse
There are 2 things you can try 1.) Go-to you folder where you have adb & fastboot. Download factory zip and unzip into adb & fastboot folder. Plug phone into PC. Open a cmd window that's NOT the administrator one try adb devices, then fastboot reboot bootloader. Click once to advance in cmd, then double click flash-all.bat and let it run through the install process. It will stop a few time, but just ignore, may even spit out an error, just ignore and let it keep installing, it may keep doing this stop and start thing,let it run. It will eventually boot up. It will wipe phone and you will have to do a new phone install. Then you can go into bootloader mode and fastboot twrp and twrp installer and go back and install super su go back and install suhide 109.
When installing TWRP I would recommend the previous version of December 1, I think and not the Dec. 15 version. Same with twrp installer.
The other thing you can try is to (if you can turn phone off) hold down power button for 5 seconds then press volume UP , that should put you in the Android on it's back and say No Command. Then you can use the options given you.
Good luck
fiverings said:
There are 2 things you can try 1.) Go-to you folder where you have adb & fastboot. Download factory zip and unzip into adb & fastboot folder. Plug phone into PC. Open a cmd window that's NOT the administrator one try adb devices, then fastboot reboot bootloader. Click once to advance in cmd, then double click flash-all.bat and let it run through the install process. It will stop a few time, but just ignore, may even spit out an error, just ignore and let it keep installing, it may keep doing this stop and start thing,let it run. It will eventually boot up. It will wipe phone and you will have to do a new phone install. Then you can go into bootloader mode and fastboot twrp and twrp installer and go back and install super su go back and install suhide 109.
When installing TWRP I would recommend the previous version of December 1, I think and not the Dec. 15 version. Same with twrp installer.
The other thing you can try is to (if you can turn phone off) hold down power button for 5 seconds then press volume UP , that should put you in the Android on it's back and say No Command. Then you can use the options given you.
Good luck
Click to expand...
Click to collapse
My post was over three months ago and as I said, I got a refurb replacement, which I have since sold and have a Pixel 2 XL. Guess I should have said that although my computer recognized it, adb didn't. That's why I was asking if there was any other way to retrieve the data. I ended up using a week old backup so it wasn't too bad.
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
---------- Post added at 07:30 PM ---------- Previous post was at 06:53 PM ----------
perfectswanson said:
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
Click to expand...
Click to collapse
I was able to get it to boot into twrp. Should be OK from here. Thank you.
perfectswanson said:
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
---------- Post added at 07:30 PM ---------- Previous post was at 06:53 PM ----------
I was able to get it to boot into twrp. Should be OK from here. Thank you.
Click to expand...
Click to collapse
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
I'm sorry I should have responded sooner. I don't remember much, but I had a feeling that it was still running because it was warm so I left it alone for a couple hours to see if it would die and then I could try to boot it again it's exactly what I did but what was funny was that it still had battery life when I turned it back on I hope you had some some luck.
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
Son of a gun. I did it again! Today. I followed a guide telling me to uninstall magisk with twrp before flashing 9.0. Now I have the same problem again. Goddamn TWRP. It told me no OS installed. Then I realized I forgot to put the magisk uninstaller file on my Verizion Pixel XL. Last time I just let my phone sit for a few hours or so, and it boot again. Not sure if it needs to run out of power, so it can boot again or what. Do you remember what you did when it happened to you?
perfectswanson said:
Son of a gun. I did it again! Today. I followed a guide telling me to uninstall magisk with twrp before flashing 9.0. Now I have the same problem again. Goddamn TWRP. It told me no OS installed. Then I realized I forgot to put the magisk uninstaller file on my Verizion Pixel XL. Last time I just let my phone sit for a few hours or so, and it boot again. Not sure if it needs to run out of power, so it can boot again or what. Do you remember what you did when it happened to you?
Click to expand...
Click to collapse
I couldnt switch it on at all. I'm planning to take it to Ubreakifix store, I guess they are the official google pixel repair people.
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
nikinnikin said:
I couldnt switch it on at all. I'm planning to take it to Ubreakifix store, I guess they are the official google pixel repair people.
Click to expand...
Click to collapse
You gotta be kidding me. Last time I left the phone alone, and my hunch was that it would run out of power, and then you can atleast get into the bootloader. I fixed it before. I wish I could get a hold of software those guys use to repartition, or however they do it. We have Pixel 3 leaks, but no repair software. All I did was install TWRP, and it said no OS installed. It just kept booting up into TWRP. Then I switched slots to see if that would change it, but I think that might have been what screwed it up.
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
What version of TWRP did you use?
---------- Post added at 01:50 PM ---------- Previous post was at 01:37 PM ----------
I just got back into the bootloader. After a dozen times I just held down and power for like five seconds. Should I try recovery and try to remove Magisk, or should I just try to flash 9.0?
---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------
What I did this time that was different, and I don't know if this is what helped or what, but this time I plugged in headphones and held power and vol down.
Putting the headphones in worked, or maybe it was just a fluke, but it worked on the first try. I got into Bootloader, "fastboot boot twrp.img", then I flashed the magisk uninstaller zip, the booted back to bootloader, and did flash-all.bat. It said it failed on the vendor partition, but everything still works.
https://forum.xda-developers.com/showpost.php?p=74525204&postcount=16
How do i fix this? My phone is working and i can use it but when i boot the phone i get the "your device is corrupt" I cannot get fastboot to boot to twrp so i cannot root.
So to be extremely polite, you posted your issue(s) in different posts and different sub-forums. Everyone has been extremely helpful but it seems you are doing something wrong somewhere. Please start from scratch with the factory images and the newest platform tools and follow carefully the guide by Nathanchance
https://forum.xda-developers.com/showthread.php?t=3702418
Then if doesn't work read some then come back with screen caps, detailed procedure, failures....etc.
Also it seems your are trying to use TWRP to root, since it's in beta and messing things up for you, root without it. And don't use any toolboxes.
Sent from my Pixel 2 XL using Tapatalk
equlizer said:
https://forum.xda-developers.com/showpost.php?p=74525204&postcount=16
How do i fix this? My phone is working and i can use it but when i boot the phone i get the "your device is corrupt" I cannot get fastboot to boot to twrp so i cannot root.
Click to expand...
Click to collapse
I had this issue when using outdated ADB to flash Google factory image. If you did this, redo with updated ADB software.
Sent from my Pixel 2 XL using XDA Labs
---------- Post added at 03:39 PM ---------- Previous post was at 03:39 PM ----------
equlizer said:
https://forum.xda-developers.com/showpost.php?p=74525204&postcount=16
How do i fix this? My phone is working and i can use it but when i boot the phone i get the "your device is corrupt" I cannot get fastboot to boot to twrp so i cannot root.
Click to expand...
Click to collapse
Update your ADB software files - that seems to be the issue.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
I'm using version 27 from November already
equlizer said:
https://forum.xda-developers.com/showpost.php?p=74525204&postcount=16
How do i fix this? My phone is working and i can use it but when i boot the phone i get the "your device is corrupt" I cannot get fastboot to boot to twrp so i cannot root.
Click to expand...
Click to collapse
I had This same issue but got it solved using Skipsoft and Deuces tools after about 5 tries
I had to factory reset and delete everything on the phone
You should try these tools
if the message is displayed on your phone, at each boot, the ONLY way to fix it, is to relock your bootloader.
I fixed it!!!!!!!!!! If anyone gets the red triangle and its saying "your device is corrupt, hit power button to continue", flash the boot img from the rom you are currently on. That's it!!
I got twrp installed and magisk installed now.
I'm getting that same exact error. My phone will boot up but I am definitely getting "your device is corrupt" in red letters when I start it. My bootloader is not unlocked because I have the Verizon version. Any ideas?
ClassickWORLD said:
I'm getting that same exact error. My phone will boot up but I am definitely getting "your device is corrupt" in red letters when I start it. My bootloader is not unlocked because I have the Verizon version. Any ideas?
Click to expand...
Click to collapse
Did you do anything to cause it, or did it just show up on it's own??
Just took an OTA update. But maybe the person who had it before me did something. I dont know. I don't see how. The bootloader is still locked.