Got hit with the dreaded bootloop this morning. Currently rooted+unlocked bootloader so the yellow 'your android os may be corrupted' triangle shows when restarting. Will that affect my warranty situation? Guessing yes, so has anyone been able to unroot while the bootloop is happening?
CLKeenan said:
Got hit with the dreaded bootloop this morning. Currently rooted+unlocked bootloader so the yellow 'your android os may be corrupted' triangle shows when restarting. Will that affect my warranty situation? Guessing yes, so has anyone been able to unroot while the bootloop is happening?
Click to expand...
Click to collapse
I guess I would try to get rid of that....
You can check out my topic here- Random (Hard?) Brick
Can you get into Download Mode? Recovery? Anything?
You should be able to get into USB-Download Mode by pulling the battery, putting it back in, hold down Vol-Up, and connecting your phone via USB to your PC.
If you are able to get in there, I guess I would try doing an update via LG Bridge. That put my phone 'back to normal' (except still bootlooping). I was then able to get into Fastboot as well and relock the bootloader.
Results May Vary
I wanted to bump this thread as I just went through the same issue with my phone in the same state.
My local T-mobile store got on the phone with support to confirm there was no fix and they (T-mobile) employee saw the corrupt screen and she read what the screen said to tech support, no one had an issue, they simply warranteed the phone and I paid nothing.
Not saying this will be typical but for me, it was very easy.
CLKeenan said:
Got hit with the dreaded bootloop this morning. Currently rooted+unlocked bootloader so the yellow 'your android os may be corrupted' triangle shows when restarting. Will that affect my warranty situation? Guessing yes, so has anyone been able to unroot while the bootloop is happening?
Click to expand...
Click to collapse
I had an issue where my phones charging port died. I went in with the "Corrupted OS" screen and they took it. Lady even looked at that screen for the entirety of it showing. Good luck though
CLKeenan said:
Got hit with the dreaded bootloop this morning. Currently rooted+unlocked bootloader so the yellow 'your android os may be corrupted' triangle shows when restarting. Will that affect my warranty situation? Guessing yes, so has anyone been able to unroot while the bootloop is happening?
Click to expand...
Click to collapse
I had the exact same thing happen to me while I was out of town for work. When I got back to my hotel, I kept trying to flash the stock KDZ using LGUP over and over and it would not work. I went to my local T-Mobile store once I got back home and filed a warranty claim and had a new V10 within 2 days.
You could always remove your SD card, put the phone in fastboot mode and re-lock the bootloader to remove that warning before you return it.
thnx.
Related
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Remove Kies and reinstall see if it picks the phone up and installs the drivers .
jje
OperationIvy85 said:
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Click to expand...
Click to collapse
That kernel is for the Epic touch 4g is that your phone or do you have the international version? If you flashed the wrong kernel it could cause problems.
Yes it's an Epic touch 4g from sprint.
EDIT: Uninstalled Kies, reinstalled Kies, restarted computer, still no kind of recognition of my phone in any state (powered off, at "Firmware upgrade encountered" screen it boots into, or in download mode). Starting to get nervous, I used to at least hear a sound when plugging my phone into my comp. It is like there is nothing on the other end of the USB cable.
More things I have tried:
-All of the above steps on a different computer
-Sweet talking it
-Talking dirty to it
Am I brick'd? I figure not, since I can at least get into download mode. Not sure what else I can do though. I'd go see what the Sprint store can do for me, but on the download mode screen it lists my custom binary download count as 5, I understand they will see that and tell me I'm out of luck?
OperationIvy85 said:
More things I have tried:
-All of the above steps on a different computer
-Sweet talking it
-Talking dirty to it
Am I brick'd? I figure not, since I can at least get into download mode. Not sure what else I can do though. I'd go see what the Sprint store can do for me, but on the download mode screen it lists my custom binary download count as 5, I understand they will see that and tell me I'm out of luck?
Click to expand...
Click to collapse
Try to reset your binary counter with a usb jig.
you could try and download the drivers again from here and see if it then connects
http://modem-techno.blogspot.com/2010/09/epic-4g-usb-driver-download.html
I also had a similar problem once with an old i9000 and what worked was doing this and then connecting the phone first and then opening Odin.For some reason opening Odin first and connecting wouldnt find the phone.If nothing else works try wipeing the bin counter with the jig and send it back.Youll have to say that kies crashed while updating on Win7 64bits.Samsung know that before the September 30th kies update kies wasnt fully functional with 64bit drivers and they had a few phones replaced under warranty because of crashing kies updates on Win7 64bits.
Thanks for the replies everyone.
I made a USB jig but it had no result. I checked the resistance with a multimeter and I am connected across pins 4 and 5 of the usb dongle I bought. I plug it in and nothing happens.
I can still get into download mode by the usual means, just no recognition from my computer, odin, or kies. Very frustrating. Am I going to have to buy a new one or is there another way to reset the bin counter?
EDIT: Got the USB jig to work! I was using a bad diagram and was on pins 1/2 instead of 4/5. Now I can't boot, can't get to recovery, can't get any PC to recognize my phone in download mode.. but at least my download screen says "Custom binary download: NO." So if nothing else works before tomorrow evening I'm gonna bring this thing back to the Sprint store and tell them what cooza said about kies crashing on win7 64 bit. Thanks everyone! Also I just realized there is a specific forum for Epic 4G touch.. sorry >.>
The good thing is that your bin counter is at "0" again.The Kies thing is the real deal as there are also posts here on XDA of the same thing happening.I also know its true from first hand experience as it has happened to me and when i told them about the Win7 64bit driver problem (this happened to me a couple of months back too) they had no option but to accept it cos they know its true.Also i offered to e-mail links from forums with other complaints from users on 64bit PCs but they didnt even dought my storey and in 4 days it was back in my hand.I told them that when the update finalized the programe froze and the phone rebooted to a black screen.Had to pull the battery cos it appeared to be dead and refused to reboot again.Important to say that you where on Kies prior to the update I mentioned.Ived update to the latest Kies and it works fine now on my Win7 64bit so be carefull there that date is important
Thanks cooza I really appreciate your help. I do have a couple questions though.
1. Is the update you are referring to an update to Kies software.. or an update to the Galaxy S2? Reason I ask is because my phone is the Epic 4G Touch (accidentally posted in this forum >.>), will they still believe my story?
2. Not sure if you will know the answer to this one, but should I go through Samsung tech support or can I take it back to the Sprint store where I bought it?
3. Just trying to get clear on the story I should tell them. I was using Kies to update my phone on a Win7 64bit computer, but I accidentally used the version of Kies from before the Sept. 30 update? And then the phone crashed resulting in it's current state. Correct? Anything else I should watch out for?
4. With the problem you are describing with Win7 x64, does the phone go into a soft brick where it won't boot up?
Thanks again.. you've been very helpful
OperationIvy85 said:
Thanks cooza I really appreciate your help. I do have a couple questions though.
1. Is the update you are referring to an update to Kies software.. or an update to the Galaxy S2? Reason I ask is because my phone is the Epic 4G Touch (accidentally posted in this forum >.>), will they still believe my story?
2. Not sure if you will know the answer to this one, but should I go through Samsung tech support or can I take it back to the Sprint store where I bought it?
3. Just trying to get clear on the story I should tell them. I was using Kies to update my phone on a Win7 64bit computer, but I accidentally used the version of Kies from before the Sept. 30 update? And then the phone crashed resulting in it's current state. Correct? Anything else I should watch out for?
4. With the problem you are describing with Win7 x64, does the phone go into a soft brick where it won't boot up?
Thanks again.. you've been very helpful
Click to expand...
Click to collapse
Kies via to its Sep 30th update was not fully compatable with 64bits and gave a lot of problems to a lot of people.I had a few problems with it when I got a new laptop (HP Win7 64bit) so started searching the web for solutions and found that kies was designed mainly to support the windowsXP versions 32bit and had caused Samsung to accept various repairs under warranty because of crashing Kies updates mainly on android running phones.For some reason Bada didnt seam to affected.Maybe cos there arnt to many around like android.In the 4G forum there is post from someone who has bricked their phone using Kies to update and a reply from another with the same problem.Take it into where you bought it to start with and if its not there problem then they might send it back to Samsung for you.All you need to say is that you where updating your firmware via kies and on completion it froze and the phone booted to a black screen like mine did.You had to pull the battery and restart your PC to close Kies cos it wouldnt close or minimize or anything.Tell them that you searched on the net for possible causes and found what i told you about Kies and since you have a Win7 64bits PC then thats most likely to have been the cause.Your bin counter is at 0 so there is no way they can counter-attack your story.
OperationIvy85 said:
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Click to expand...
Click to collapse
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Who told you that the exclamation point means you voided your warranty?
bajaber said:
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Click to expand...
Click to collapse
The exclamation point on a normal boot up screen (Galaxy S II splash screen) means there is a custom rom installed. This can be removed with a USB jig, which will also reset your custom binary counter.
I have absolutely no idea still what [phone]....!....[computer] means though. I ended up taking my phone back to the Sprint store and they replaced it for a small service charge while telling me next time I won't be so lucky. My next step was going to be to try calling Samsung with the story cooza suggested. I told that same story to the people at Sprint but they definitely didn't buy it, but you may have better luck with Samsung. If you get this resolved I'd be curious to hear how, but I am not optimistic for you
bajaber said:
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Click to expand...
Click to collapse
The sign you see means that your phone is semi-bricked and that you needed a jig to force the phone to boot into download mode.You can buy one on ebay for a couple of bucks.Best you do cos it could may mean that your warranty is void.Let me explain,no one can actually say that your warranty is void because of this sign but being only "semi-bricked" the service centre are still able to enter the phone and see the bin counter.So if you semi-bricked flashing a non official firmware or you have done so earlier and your bin counter is not at 0 then YES your warranty is void.Semi-brick is not so bad as you can normally fix it yourself but Hard-brick is a dead phone and you gotta pay for a jtag .In your case buy a jig force the phone into download mode and re-flash it yourself.You shouldnt need to go anywhere.Semi-bricking is something you save yourself.Just wait till the jig arrives in the mail.
EDIT:there have been posts of people pulling the battery for 10min and re-trying and it has booted to download.They say they have had to do so 4 or 5 times for it to finally work but if youve got time on your hands then give it a try.
---------- Post added at 04:48 PM ---------- Previous post was at 04:22 PM ----------
OperationIvy85 said:
The exclamation point on a normal boot up screen (Galaxy S II splash screen) means there is a custom rom installed. This can be removed with a USB jig, which will also reset your custom binary counter.
I have absolutely no idea still what [phone]....!....[computer] means though. I ended up taking my phone back to the Sprint store and they replaced it for a small service charge while telling me next time I won't be so lucky. My next step was going to be to try calling Samsung with the story cooza suggested. I told that same story to the people at Sprint but they definitely didn't buy it, but you may have better luck with Samsung. If you get this resolved I'd be curious to hear how, but I am not optimistic for you
Click to expand...
Click to collapse
Well at least you got a phone now hope they didnt charge to much!!!!Good on ya mate
Update on my issue....
It turns out the problem is because I tried to flash an I1900 firmware while my phone is a G variant (I900G).
After using the right firmware, it worked.
OperationIvy85 said:
Thanks for the replies everyone.
I made a USB jig but it had no result. I checked the resistance with a multimeter and I am connected across pins 4 and 5 of the usb dongle I bought. I plug it in and nothing happens.
I can still get into download mode by the usual means, just no recognition from my computer, odin, or kies. Very frustrating. Am I going to have to buy a new one or is there another way to reset the bin counter?
EDIT: Got the USB jig to work! I was using a bad diagram and was on pins 1/2 instead of 4/5. Now I can't boot, can't get to recovery, can't get any PC to recognize my phone in download mode.. but at least my download screen says "Custom binary download: NO." So if nothing else works before tomorrow evening I'm gonna bring this thing back to the Sprint store and tell them what cooza said about kies crashing on win7 64 bit. Thanks everyone! Also I just realized there is a specific forum for Epic 4G touch.. sorry >.>
Click to expand...
Click to collapse
Hi, I'm having an exactly same problem with you and I just got a USB jig in mail, but even though I am following the instructions for the USB jig the counter is still not going back to 0 :/
This is the instruction I followed: take battery out for like a minute -> put the battery in but don't turn phone on -> put the usb jig in -> it's supposed to boot up with 0 flash count?
Mine still says 4... Can anyone please help?
sfoksn said:
Hi, I'm having an exactly same problem with you and I just got a USB jig in mail, but even though I am following the instructions for the USB jig the counter is still not going back to 0 :/
This is the instruction I followed: take battery out for like a minute -> put the battery in but don't turn phone on -> put the usb jig in -> it's supposed to boot up with 0 flash count?
Mine still says 4... Can anyone please help?
Click to expand...
Click to collapse
Is yours a i9100? If so is your firmware the latest 2.3.5 KI3 or KI8?
Could be your device has the new bootloader. If so check intratechs original firmware thread in original development section and install his old bootloader via Odin. Have a read while your there to get the latest info.
Good luck
Sent from my GT-I9100 using XDA App
aceofclubs said:
Is yours a i9100? If so is your firmware the latest 2.3.5 KI3 or KI8?
Could be your device has the new bootloader. If so check intratechs original firmware thread in original development section and install his old bootloader via Odin. Have a read while your there to get the latest info.
Good luck
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yeah, I got stuck while flashing 2.3.5 Gingerbread... Yeah I think it has a new bootloader, as I remember Odin updating the bootloader section before messing up.
Is there any way I can get the USB jig to work? My phone is no longer recognized by the USB anymore so I can't even flash another bootloader or anything.
Is there anythign I could do to make the USB jig work without connecting it to the computer?
Can you get into download mode using the buttons?
Volume down+home+power
If so try and flash another Rom from intratechs thread to get back to stock.
If that works you can try again.
Sent from my GT-I9100 using XDA App
Anybody has an idea how to fix an HTC rezound phone that is stock never rooted, went thru the ICS OTA update, after restart is just restarting over and over again. Only shows HTC white display and keeps restarting.
I can go into Hboot, tried factory reset, even downloaded ruu ran it but it keeps bootlooping!!!..
Any ideas?
mpmorph said:
Anybody has an idea how to fix an HTC rezound phone that is stock never rooted, went thru the ICS OTA update, after restart is just restarting over and over again. Only shows HTC white display and keeps restarting.
I can go into Hboot, tried factory reset, even downloaded ruu ran it but it keeps bootlooping!!!..
Any ideas?
Click to expand...
Click to collapse
Perhaps it is the network bootloop issue, had that issue with the first OTA, try diagnosing that:
http://forum.xda-developers.com/showthread.php?t=1394659
mpmorph said:
Anybody has an idea how to fix an HTC rezound phone that is stock never rooted, went thru the ICS OTA update, after restart is just restarting over and over again. Only shows HTC white display and keeps restarting.
I can go into Hboot, tried factory reset, even downloaded ruu ran it but it keeps bootlooping!!!..
Any ideas?
Click to expand...
Click to collapse
mpmorph, let us know if your problem was same as the network boot looping issue, so we can assist others that get it with this OTA.:good:
....Sadly that is not the case. I tried to follow the instructions on that link but never managed to enter the code. The phone never got that far. The device just displays the white screen with the HTC green logo and then it dims the light a bit, and......it shutdowns, just to restart again. Removed everything, SIM card, microSD card, and nothing.
Received a replacement from verizon today, but before i send the other one back if anybody has any ideas to try.....now is the time....please?
Draw all over it to make VZW mad.
On a serious note, it would be nice if the internal sd was a real micro sd that you could remove and stick in a computer to get all of your files back.
mpmorph said:
....Sadly that is not the case. I tried to follow the instructions on that link but never managed to enter the code. The phone never got that far. The device just displays the white screen with the HTC green logo and then it dims the light a bit, and......it shutdowns, just to restart again. Removed everything, SIM card, microSD card, and nothing.
Received a replacement from verizon today, but before i send the other one back if anybody has any ideas to try.....now is the time....please?
Click to expand...
Click to collapse
Run the OTA RUU on it
I had the same issue with my OTA update. But Verizon won't warranty my 5 month old phone because it was not purchased on my line. Grr... Anyone that has any suggestion of how to fix it, please let me know/.
AshtonTS said:
Run the OTA RUU on it
Click to expand...
Click to collapse
Tried it. RUU ran then on restart same thing. No go.
I think S-OFF and running a GB RUU might work, don't wanna risk getting 500 dollar spike on my Verizon bill Cuz it was hacked.
Thanks for trying guys.
I had a similar problem, if you are able, wipe everything and reinstall the update. It worked for me.
Is the stock recovery installed?
Bootloader is locked/relocked ?
Did you remove the PH98IMG.zip file from your SD card?
Did you try booting with the back cover removed?
mpmorph said:
Tried it. RUU ran then on restart same thing. No go.
I think S-OFF and running a GB RUU might work, don't wanna risk getting 500 dollar spike on my Verizon bill Cuz it was hacked.
Thanks for trying guys.
Click to expand...
Click to collapse
Lol they won't bill you $500 for "hacking" your phone. Jailbreaking / rooting / etc. is all legal; the most they can do is void your warranty.
shadytech said:
I had the same issue with my OTA update. But Verizon won't warranty my 5 month old phone because it was not purchased on my line. Grr... Anyone that has any suggestion of how to fix it, please let me know/.
Click to expand...
Click to collapse
Contact HTC; see if they can warranty it if VZW won't.
Hello all, got a bit of a strange issue here. So I was using the 30b release from runningnak3d, https://forum.xda-developers.com/tmobile-lg-v10/development/h901-t-mobile-nougat-v30b-twrp-t3639203
I was selling my v10, so I did a reset, skipped or hit next to everything, and verified that all was working. I sold the phone and a couple days after the buyer got it, he told me it was bootlooping. I asked what he did and of course the first time he said nothing, just turned it on. After more conversation, he said when he got it it booted and after a while told him an upgrade was available. He said he accepted the upgrade, and afterwards got the bootloop.
I got the phone back today to try to fix it and give it back to him. Here's what I have found. Definitely bootlooping, stops at T-Mobile logo and reboots. It does still have the unlocked bootloader, still shows the warning right at boot. TWRP is gone! I booted to recovery, answered Yes to those 2 questions, and it did a reset instead of loading TWRP.
I really have no idea what he did, whether is was an OTA update or maybe he tried to load something on his own.
So, is there any hope of getting this thing going again? So far I was able to boot it into download mode, but it won't respond to any fastboot commands. My computer detects it, but in computer management it says LGE USB modem or something like that. When I try to regular boot, the computer does detect the phone, but it doesn't get far enough along to issue ADB commands. I'm thinking it's a paperweight at this point, so I'm game to try whatever.
I recently purchased two new VS988 for an elderly friend of mine who loves his current G6 and was worried about LG getting out of the phone business. Trying to get the phones all set up for him I tried running the OTA updates which kept failing. After the OTA update process failed a dozen times or more I decided to try using the Windows VZW update utility. Finally, after a dozen tries the VZW utility finally managed to DL the FW to my computer but when it tried to install the FW it booted the phone into FW Update Mode and then failed to install. I have tried all of the listed methods of button presses to reboot the phone into any other mode but it always comes back to FW update mode. This morning I learned about the LGUP program and have given that a try and it stops at 4% with an error message that says "Error: 0x700A, ManipulateBootPT Failed"
I'm not sure what else to try. I'm using the cable that came in the box and a USB port on the back of my computer.
Any help/advice will be greatly appreciated.
Maybe turn of recovery mode
How am I supposed to do that? No matter what buttons I try pressing when rebooting the phone it always comes back into FW Update Mode. I tried running the recovery process and the Verizon updater program and that had the same problem.
Spazebar said:
How am I supposed to do that? No matter what buttons I try pressing when rebooting the phone it always comes back into FW Update Mode. I tried running the recovery process and the Verizon updater program and that had the same problem.
Click to expand...
Click to collapse
I had an old tablet before, that did the same thing turning off recovery fixed it
Ilikeandroidics said:
I had an old tablet before, that did the same thing turning off recovery fixed it
Click to expand...
Click to collapse
How do I turn off recovery?
Spazebar said:
How do I turn off recovery?
Click to expand...
Click to collapse
I don't recommend advice from that guy
The problem your having is stuck in download mode.
As long as you're not connected to a PC via USB and actively transferring a firmware file, you should be able to force shutdown by removing the battery and placing it back in (if possible) or pressing and holding Power for about 20 seconds. Then power on again normally.
Droidview said:
I don't recommend advice from that guy
The problem you having is stuck in download mode.
As long as you're not connected to a PC via USB and actively transferring a firmware file, you should be able to force shutdown by removing the battery and placing it back in (if possible) or pressing and holding Power for about 20 seconds. Then power on again normally.
Click to expand...
Click to collapse
Thanks I'll try that tomorrow
Spazebar said:
Thanks I'll try that tomorrow
Click to expand...
Click to collapse
Hey, did my information help?
Unfortunately nothing has worked I just ended up with two bricked phones. Thankfully they were just supposed to be back up phones for somebody that is unlikely to need them and can afford buying another replacement if something ever actually does happen to his primary. He has a lot of accessibility issues in a really prefers having the the buttons on the back of the phone so he doesn't keep turning it off accidentally.
Spazebar said:
Unfortunately nothing has worked I just ended up with two bricked phones. Thankfully they were just supposed to be back up phones for somebody that is unlikely to need them and can afford buying another replacement if something ever actually does happen to his primary. He has a lot of accessibility issues in a really prefers having the the buttons on the back of the phone so he doesn't keep turning it off accidentally.
Click to expand...
Click to collapse
If your android was stuck in recovery mode (as i know it), you could of just factory reset right?
forgive me it's been a couple of months since I bothered messing around with them but I believe it's not a generic recovery mode you know where you've got those four text options at the top you know and the Android with the exclamation point coming out of its chest but instead it's a firmware update mode. No amount of software tools or button key presses and we'll get the phones to do anything else. Both phones are dead right now cuz I just wanted to confirm what I was telling you whatever they managed to charge up later I will make sure what I'm saying is correct and I will let you know otherwise
If this is the screen you see, then i regret to inform you that your phone might have been bricked the entire time and you couldn't save it (unless you get new firmware for you device and install it). Trust me i had this experience before.
This is what I get. I try running the the Verizon LG update utility on the computer and after it reaches 11% or something like that it fails
Spazebar said:
This is what I get. I try running the the Verizon LG update utility on the computer and after it reaches 11% or something like that it fails
View attachment 5502673
Click to expand...
Click to collapse
Welp, my last geuss at this is that the previous owner got something like a virus to prevent the firmware update to continue. i've only worked with lg phones a few times, but those phones where very old (2008) and did not run android
Thanks for trying. I've given up and my friend didn't even get upset about it. Whatever went wrong happened when I tried to manually update them because the OTA kept failing. If he buys any more backups in the future I'll find him something a little more recent.
I have a pixel 6a that I successfully rooted but when I tried to unroot it something went wrong. When I restarted the phone I got a message saying
Your device is corrupt. It can’t be trusted and may not work properly.” then it was stuck on the Google logo. I managed to get it unstuck but then when it restarted I got the error message again and it shut off. Now the phone will not turn on at all. I tried charging it for hours. I tried forcing it to turn on with every ossible button configuration I could think of. It is completely unresponsive. Please help. I literally just reviewed it from Google Fi a week ago
Cheesymatt661 said:
I have a pixel 6a that I successfully rooted but when I tried to unroot it something went wrong. When I restarted the phone I got a message saying
Your device is corrupt. It can’t be trusted and may not work properly.” then it was stuck on the Google logo. I managed to get it unstuck but then when it restarted I got the error message again and it shut off. Now the phone will not turn on at all. I tried charging it for hours. I tried forcing it to turn on with every ossible button configuration I could think of. It is completely unresponsive. Please help. I literally just reviewed it from Google Fi a week ago
Click to expand...
Click to collapse
Are you on A13?
Did you have, at the minimum, the A13 bootloader on both slots?
What method did you use to uninstall Magisk?
What happens when you connect phone to computer?
Will Android Flash Tool recognize it? If so, use that to flash back to stock.
Try holding the power button down for at least 30 seconds?
If you were on A13 and didn't have the A13 bootloader on both slots, when bootlooping your phone may have reverted to the A12 slot. If so, your device may be a brick due to the new ARB and you should probably RMA it.
Yes it was A13. And nothing happens when I connect it to my laptop. And I'm not sure what you mean by "both slots". My apologies... This is my very first time rooting and trying to unroot a device
I am also using Linux. So I don't really know what other tools I could or should try other than sdk platform tools.
Cheesymatt661 said:
Yes it was A13. And nothing happens when I connect it to my laptop. And I'm not sure what you mean by "both slots". My apologies... This is my very first time rooting and trying to unroot a device
Click to expand...
Click to collapse
Did you do this after updating to A13?
It's a hard brick as per the link in the above post.
But why root, then unroot?
What steps did you take?
It would be helpful to others to find out where you went wrong.
Cheesymatt661 said:
I have a pixel 6a that I successfully rooted but when I tried to unroot it something went wrong. When I restarted the phone I got a message saying
Your device is corrupt. It can’t be trusted and may not work properly.” then it was stuck on the Google logo. I managed to get it unstuck but then when it restarted I got the error message again and it shut off. Now the phone will not turn on at all. I tried charging it for hours. I tried forcing it to turn on with every ossible button configuration I could think of. It is completely unresponsive. Please help. I literally just reviewed it from Google Fi a week ago
Click to expand...
Click to collapse
Why not post this in Pixel 6a forum?
@Cheesymatt661 Okay so you have unlocked bootaloder + fastboot is working right? One of my friend also faced this and what he did was flashed latest (A13) factory images to both A & B slots separately and that's it. It was simple as that for him.