Develop Bugs

PLEASE HELP! Possible Brick?

Hey guys I have an Evo but my buddy has an Dinc and we rooted it and flashed CM6 and its never had a problem. Lately it started randomly rebooting and now it wont get past the splash screen; he cant even boot into recovery he said and an RUU doesnt even recognize the phone.
any help is greatly appreciated guys, thanks.

Hmm...
mic.mayorga said:
Hey guys I have an Evo but my buddy has an Dinc and we rooted it and flashed CM6 and its never had a problem. Lately it started randomly rebooting and now it wont get past the splash screen; he cant even boot into recovery he said and an RUU doesnt even recognize the phone.
any help is greatly appreciated guys, thanks.
Click to expand...
Click to collapse
mic, what is the model number of the device? There are 3 for the Incredible, the ADR6300, 6300VW2 and VW3. Also, how early (after the phone hit the market) is the phone?

I couldn't tell you exactly. He bought like the first one, the one that came with the OLED screen.
Sent from my PC36100 using XDA App

I see. I had one of the original ones as well, and began to have an issue similar to this. What happened was some of early models had defective hardware radio chips. To find out if this is the issue with your friend's phone, have the phone deactivated from service, and then shut off the phone for 20 minutes. If you turn it back on and it powers on with no problems, you may have a device that needs replacement. If so, at least it will make you able to unroot and flash back to stock so you can get replaced with verizon/htc.
If this doesn't change anything, let us know, we'll get to the bottom of this.

well i tried calling him and i got his google voice thing when he didnt answer. idk if that means hes back on the Dinc or not. he had to go back to the enV 3 for a working phone lol. the only problem is that if he asked Verizon for a replacement but he bought it contractless on ebay...

They'd probably just tell him no.
mic.mayorga said:
well i tried calling him and i got his google voice thing when he didnt answer. idk if that means hes back on the Dinc or not. he had to go back to the enV 3 for a working phone lol. the only problem is that if he asked Verizon for a replacement but he bought it contractless on ebay...
Click to expand...
Click to collapse
Sent from my Incredible using XDA App

mic.mayorga said:
well i tried calling him and i got his google voice thing when he didnt answer. idk if that means hes back on the Dinc or not. he had to go back to the enV 3 for a working phone lol. the only problem is that if he asked Verizon for a replacement but he bought it contractless on ebay...
Click to expand...
Click to collapse
Might be able to make a claim with HTC, but the warranty claims are made through a third party. I had some luck with calling HTC, getting them to say that they'll do something about it, and when the third party tried to charge me money, I just flipped **** and gave them the loyal customer speech. Worth a shot. If you can't get it for free, ***** and see if that helps

haha okay ill let him know to look into that. also ill ask him about the whole 20 minutes thing. thanks a lot for the help

Wonky SD Card?
CM 'interactively' uses elements of the SD card, I believe.
That said, have you tried a different SD card?
Meaning, d/l another ROM onto the 'other' SD card, put it in the device w/ power off (after unmounting SD, powering down, and removing 'first' SD card)
Load/flash new ROM from recovery off of 'other' SD after wiping everything, and see if it boots.

[Q] Help - 5 vibrates and blinking green LED

Hi, I'm having problems with my DINC.
I was running SkyRaider Athena 1.2 with the stock Kernel, HBOOT 0.92, Radio 2.15.00.09.01 and S-OFF. It was getting a little slow and bogged down so I decided to start afresh and flash a new rom. I upgraded my Custom Recovery from 2.5 to 3.5 (it had been a while since I had flashed a rom) and flashed SkyRaider Sense 3.5.
Here is where the problems start. Whenever I turn off the phone and try to turn it back on I get the "HTC Incredible" screen, which then goes to black and I get 5 vibrations and a green flashing LED. I can get to the bootloader but when I try to get to the Custom Recovery, the same thing happens. One thing that I have noticed is that S-Off is now S-ON.
The only way that I can get the phone to turn on is to press the power button, and plug the phone into a usb for power. At that point it will start up normally, however the phone will not read the SDcard or internal phone storage at all, even in when I do the same thing to get to the custom recovery, which means that I can't flash roms, or use any apps that require some sort of memory.
I don't know if this is a problem with the rom so I posted this in the general discussion.
I've also found some posts on other websites where people have had similar issues but no solution:
http://www.incredibleforum.com/foru...f-vibrates-5-times-green-light-flashes-3.html
http://www.droidforums.net/forum/dr...9959-need-help-5-vibrates-blinking-green.html
Yes. I'm QuickSilver98 on those sites too
Any help would be greatly appreciated.

Sorry to say but I have yet to see a solution other then a insurance claim. I hope someone smater then I can help.

Just do a battery pull when that happens.
It has happened to me before a couple times, but after a battery pull everything works fine.

thanks for the suggestion, I've tried tons of battery pulls, but there's no change.

I've never heard of this problem but, then again, I've only been in the Android community since September and am far from an authority. I do have one thought though which I'm guessing is not a cure all for your problem but, could possibly be a part of the problem. Is it possible that maybe your SD card has crapped out on you? Have you tried putting it in a card reader to see if it is still readable? Just a thought, as I said. Good luck with your problem, in any case.
Sent from my ADR6300 using XDA App

I had this problem, I took the phone back to Verizon and they gave me a refurb. But this may help you
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/

c_live_lee said:
I've never heard of this problem but, then again, I've only been in the Android community since September and am far from an authority. I do have one thought though which I'm guessing is not a cure all for your problem but, could possibly be a part of the problem. Is it possible that maybe your SD card has crapped out on you? Have you tried putting it in a card reader to see if it is still readable? Just a thought, as I said. Good luck with your problem, in any case.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I thought of that, the memory card does work in other phones and other memory cards can't be read by the incredible. So it's definitely the phone.

Yeah, I figured it was something more. Just wanted to put it out there because of the possibility of more than one issue going on simultaneously. I know it's rare to have multiple problems at once but it does happen on occasion. Any luck zeroing in on your problem?
Sent from my ADR6300 using XDA App

Hey there, You linked to my post. I ended up having to get a refurb from verizon. my situation was the same and I was able to get the phone to "s-off" before I called them up and went through verizons troubleshooting routine.
they overnighted a refurb for free.
Best of luck with your phone.

Ixa said:
Hey there, You linked to my post. I ended up having to get a refurb from verizon. my situation was the same and I was able to get the phone to "s-off" before I called them up and went through verizons troubleshooting routine.
they overnighted a refurb for free.
Best of luck with your phone.
Click to expand...
Click to collapse
I'm thinking of going that route as well. I haven't been able to find any solutions anywhere and that seems like the best option.

My brand new Inc did this out of the box. I could get it to boot if it was plugged into USB, but even then things weren't quite right (Bluetooth didn't work, WiFi was wonky, internal storage was not recognised, etc). Apparently this is a Qualcomm hardware error code, and a warranty replacement is your only real option. Good luck!

fix
ok this happens all the time and all i have to do is pull out the battery and wait 20 seconds then i just either boot the phone up or boot it into hboot and then boot into recovery and reboot the phone.

[Q] DHD brick and guarantee help

Hi Everyone !
I have a Desire HD and it bricked last sunday evening. It's only half year old, so I took it back to T-Mobile (I bought it from them). But it's rooted and Radio S-OFF-ed when died. Can the service establish that I rooted and S-OFF-ed my phone, or no ?
Thanks in advance !

If it's totally dead (no bootloader access or charge light) then they won't be able to tell. They'll fix it without any knowledge of software changes.
Sent from my Motorola Startac running Atari 2600 software!

Yep if its completely dead they wont bother repairing it, they'll just replace the motherboard. That way they have no knowledge of what you did to it.

Thanks for the answers,I'm happy right now,because you have the point:absolutely no sign of life. No charging light,no bootloader and no any happening when I press the power button (same with another battery too).

how did you manage to do that? It will be good for others to know so that they dont make such a mistake .

meeru said:
how did you manage to do that? It will be good for others to know so that they dont make such a mistake .
Click to expand...
Click to collapse
I don't know. Here's what happened:
1.: I use Opera Mobile for web browsing and the past few days it's become very slow. Sometimes the only way to close it is press the Home button and close it in task manager. I thought it's a software problem, so I made a hard reset, but it's not resolved my problem. Mean while I saw the news that HTC will not refresh the Desire HD to ICS in the first line, so I downgraded it and flash the latest NDT MIUI ROM.
2.: Next day I connected my phone to my PC and realised there is no communication between, only charging. I tried it in other computers and other USB cables, same result, so I wanted to back to stock. My only problem was the Radio system. I was still S-OFF-ed. I searched so many forums and I tried to get back Radio S-ON in Terminal Emulator, but it didn't work.
3.: Tried some instructions without any result and finally after a reboot procedure the phone didn't wake up anymore. No reaction for the charger, no reaction for any button pushed. Nothing. Took it back to T-Mobile and they check the battery because they thought maybe that caused this and they said it discharged over.
And now I'm waiting for an SMS or call how is my phone now

goodluck with that

Got it back from repair service. They changed its motherboard,so almost I have a brand new phone now I'm so lucky I guess ... huhh ... sweating a lot,but now I'm happy

SsZzliMm said:
Got it back from repair service. They changed its motherboard,so almost I have a brand new phone now I'm so lucky I guess ... huhh ... sweating a lot,but now I'm happy
Click to expand...
Click to collapse
Good job mate
Sent from my Desire HD using xda premium

SsZzliMm said:
Thanks for the answers,I'm happy right now,because you have the point:absolutely no sign of life. No charging light,no bootloader and no any happening when I press the power button (same with another battery too).
Click to expand...
Click to collapse
If you plug it into your computer in that state, does it ask for qload usb drivers? if so, Its a true brick, and there's no way they'll know what you had going on. I had mine replaced in June this year after mine was bricked.

[Q] tried flasing rom and phone is dead..

i got a samsung gs3 yesterday, i loved everything but battery life, lastnight i used George Holtz's "towel root" and rooted my phone, added super user and rom toolbox, upgraded my recovery to clockwork mod basic, and proceded to flash to "flashingdroid version 2.2" it went thru everything and installed the rom, when it tried to reboot, it went black... now it does nothing, computer tries to recognize it, abut i cant get it to download mode, and i cant get it into recovery mode... it does not show charge picture when plugged in and if i take the battery out, plug it in, then insert the battery i get a red light... PLEASE HELP!!!!!!!

noobbrokes3 said:
i got a samsung gs3 yesterday, i loved everything but battery life, lastnight i used George Holtz's "towel root" and rooted my phone, added super user and rom toolbox, upgraded my recovery to clockwork mod basic, and proceded to flash to "flashingdroid version 2.2" it went thru everything and installed the rom, when it tried to reboot, it went black... now it does nothing, computer tries to recognize it, abut i cant get it to download mode, and i cant get it into recovery mode... it does not show charge picture when plugged in and if i take the battery out, plug it in, then insert the battery i get a red light... PLEASE HELP!!!!!!!
Click to expand...
Click to collapse
What model is your phone? You flashed a i9300 ROM, this is the sub-forum for the i747.

its the i747, i before looking today never knew there were more than 1 model of the GS3, is it possible to fix it?

This may help:
http://forum.xda-developers.com/showthread.php?t=2549068

audit13 said:
This may help:
http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
my problem is my phone does NOT vibrate when power button is pressed, it isnt doing ANYTHING at ALL, the red charging light only comes on when battery is left out and the phone is plugged in, light turns off after a minute or so of the battery being installed, to me it seems like less rom flash related, and more failure in the board, but im not good at this stuff so im probably wrong, i bought a verizon one (i535) for 50 bucks (pretty banged up touchscreen is cracked in several places i got it without a back cover,but it works,) to get me by but i miss my 4g on straight talk =( i wish i had just left it alone, it was clean just 1 crack in the touch screen wires ans such for lcdanddigitizer got cut by accient while trying to modify midframe for verizon board, i sure as hell cant afford the att version for a while 150-260 for a decent i747, is it possible that a JTAG service would be able to bring it to life or even one of those dongles to force recovery?

noobbrokes3 said:
my problem is my phone does NOT vibrate when power button is pressed, it isnt doing ANYTHING at ALL, the red charging light only comes on when battery is left out and the phone is plugged in, light turns off after a minute or so of the battery being installed, to me it seems like less rom flash related, and more failure in the board, but im not good at this stuff so im probably wrong, i bought a verizon one (i535) for 50 bucks (pretty banged up touchscreen is cracked in several places i got it without a back cover,but it works,) to get me by but i miss my 4g on straight talk =( i wish i had just left it alone, it was clean just 1 crack in the touch screen wires ans such for lcdanddigitizer got cut by accient while trying to modify midframe for verizon board, i sure as hell cant afford the att version for a while 150-260 for a decent i747, is it possible that a JTAG service would be able to bring it to life or even one of those dongles to force recovery?
Click to expand...
Click to collapse
It could be a board failure but it happened right after you flashed the ROM which leads me to believe it is software related.
A dongle is not going to help since the phone won't even power up. A jtag service would be your best and quickest option. You should try and find a shop that will guarantee to revive the phone or you pay nothing.
This might help with your current phone: http://www.xda-developers.com/android/how-to-make-your-verizon-galaxy-s-iii-a-world-phone/

noobbrokes3 said:
my problem is my phone does NOT vibrate when power button is pressed, it isnt doing ANYTHING at ALL, the red charging light only comes on when battery is left out and the phone is plugged in, light turns off after a minute or so of the battery being installed, to me it seems like less rom flash related, and more failure in the board, but im not good at this stuff so im probably wrong, i bought a verizon one (i535) for 50 bucks (pretty banged up touchscreen is cracked in several places i got it without a back cover,but it works,) to get me by but i miss my 4g on straight talk =( i wish i had just left it alone, it was clean just 1 crack in the touch screen wires ans such for lcdanddigitizer got cut by accient while trying to modify midframe for verizon board, i sure as hell cant afford the att version for a while 150-260 for a decent i747, is it possible that a JTAG service would be able to bring it to life or even one of those dongles to force recovery?
Click to expand...
Click to collapse
Flashing an i9300 rom is guaranteed to hard brick the device and cause exactly what you described. If you follow the instructions in the thread linked in an above post it probably has a 90% chance of fixing it.
I am 99% certain it is not a hardware failure. Others have done the exact same thing and were able to fix it by using the instructions in that thread.

audit13 said:
It could be a board failure but it happened right after you flashed the ROM which leads me to believe it is software related.
A dongle is not going to help since the phone won't even power up. A jtag service would be your best and quickest option. You should try and find a shop that will guarantee to revive the phone or you pay nothing.
This might help with your current phone: http://www.xda-developers.com/android/how-to-make-your-verizon-galaxy-s-iii-a-world-phone/
Click to expand...
Click to collapse
i found one on ebay, full refund short of a 5 dollar shipping cost for return shipping, once i have money that i can spend ill sure as hell be giving it a shot

Or you can attempt to fix it for free.....but I suppose that is up to you.

DocHoliday77 said:
Or you can attempt to fix it for free.....but I suppose that is up to you.
Click to expand...
Click to collapse
either way its gonna cost me a little cash, i dont have a 16 gig sd card, forgive me for being so noob but the sd card trick CAN work for my case?? i know for a fact i cant do anythingto my phone right now as it wont even power on, but if you BELIEVE it will work ill gove it a try

Unless you updated with the kk ota, you are probably on 4.3 firmware. I cannot guarantee it will work, but I believe the chances are pretty good that it will.
Just remember, if it doesn't work, dont give up on the first try. Many have had to run through the process several times before it would actually boot up again.
The only other tip I can think to give is to make sure you buy a decent sd card. It doesn't have to be top of the line, but there are tons of fake ones out there that would be less likely to work. If you can, try to buy one from an authorized dealer for whatever brand you are considering. This greatly reduces the chance of getting a bad card.

DocHoliday77 said:
Unless you updated with the kk ota, you are probably on 4.3 firmware. I cannot guarantee it will work, but I believe the chances are pretty good that it will.
Just remember, if it doesn't work, dont give up on the first try. Many have had to run through the process several times before it would actually boot up again.
The only other tip I can think to give is to make sure you buy a decent sd card. It doesn't have to be top of the line, but there are tons of fake ones out there that would be less likely to work. If you can, try to buy one from an authorized dealer for whatever brand you are considering. This greatly reduces the chance of getting a bad card.
Click to expand...
Click to collapse
4.0.x was the last firmware, i never got to update it. i bought a PNY 16gb microSD HC class 4, it was 25 bucks at the local drug store, i was hoping for a class 6 - 10 but i believe it is a good quality card, maybe you would know better?

I won't lie, I am not a big fan of PNY, but as long as its the real thing, I think it should work. Class 6 or better is recommended, but it has worked on class 4 cards too. At this point, the only thing left to do is give it a shot. Good luck!

Question *Urgent Help* Bricked Pixel 6 Pro

I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.

Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.

Lughnasadh said:
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.
Click to expand...
Click to collapse
Ahhh I'm from the UK. I only got the phone just a month ago too and now this has happened. I checked on the their Uk site i can take it to a local mobile carrier and they've stated that they will do the repair next day. I might just do that tomorrow if not then I'll speak to Google.

Tombo12 said:
Ahhh I'm from the UK. I only got the phone just a month ago too and now this has happened. I checked on the their Uk site i can take it to a local mobile carrier and they've stated that they will do the repair next day. I might just do that tomorrow if not then I'll speak to Google.
Click to expand...
Click to collapse
Good luck! Let us know how things go.

roirraW edor ehT said:
Good luck! Let us know how things go.
Click to expand...
Click to collapse
Some News for everyone!
So I spoke to Google and they was fine about it phone not working went through some troubleshooting tricks neither of the options worked. The rep on the phone gave me two options Send it into Google for a repair and they'll send me over a replacement 6 Pro whilst its being worked on. If they can't fix it they'll let me keep the phone but if all is well with the phone then I'll need to return it back otherwise I'll get charged for it.
The second option is sending it in for a repair at a local authorized repair center. Luckily there is one 10-15 minutes away from me but the annoying thing is all bookings are available during my working hours but the place has 5* reviews and can get the phone repaired within the same day.
So I might just go for my second option tbh seems alot more convenient and less hassle of having to send a phone away to Google and wait 10 days for a repair which can be done within a day by a repair center that is less than 10 mins away from me and has all parts available to hand out.
Btw the repair center near me is called Ismash. There's one nearby me in London.

Awesome news! There are at least a handful of other users who have reported getting bricked since Android 13 came out August 15th, and I believe all of them reported good news from Google for repairs, but I don't have any idea if any of them were in the UK, so glad it's going to work out there too.

Tombo12 said:
Some News for everyone!
So I spoke to Google and they was fine about it phone not working went through some troubleshooting tricks neither of the options worked. The rep on the phone gave me two options Send it into Google for a repair and they'll send me over a replacement 6 Pro whilst its being worked on. If they can't fix it they'll let me keep the phone but if all is well with the phone then I'll need to return it back otherwise I'll get charged for it.
The second option is sending it in for a repair at a local authorized repair center. Luckily there is one 10-15 minutes away from me but the annoying thing is all bookings are available during my working hours but the place has 5* reviews and can get the phone repaired within the same day.
So I might just go for my second option tbh seems alot more convenient and less hassle of having to send a phone away to Google and wait 10 days for a repair which can be done within a day by a repair center that is less than 10 mins away from me and has all parts available to hand out.
Btw the repair center near me is called Ismash. There's one nearby me in London.
Click to expand...
Click to collapse
Great to hear! If you end up taking it to the repair shop, please let us know what repairs they did (I'm guessing replacing the motherboard) and what they said was wrong with it (e.g. If it was an eFuse problem). Thanks and good luck!

Lughnasadh said:
Great to hear! If you end up taking it to the repair shop, please let us know what repairs they did (I'm guessing replacing the motherboard) and what they said was wrong with it (e.g. If it was an eFuse problem). Thanks and good luck!
Click to expand...
Click to collapse
i am also very curious if it actually needs a motherplace replacement or simply a reflash using a JTAG (or similar specialized tool) to get it out of the bricked state.

Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
My 6 pro did this last weekend, when I was rooted I decided to flash a file to change the font and I missed the part it would work on 13 as long I deleted a certain file for the lock screen, it boot looped a few times, apparently it tried to load from slot B where android 12 was still flashed, and it hard bricked, no button combo would work, completely bricked, it was fully charged when this happen, so I RMA`d with google and my old device is suppsoed to be delivered to Texas today, then hopefully tomorrow my if I`m lucky that my replacement gets shipped.

2015Ducatimulti said:
My 6 pro did this last weekend, when I was rooted I decided to flash a file to change the font and I missed the part it would work on 13 as long I deleted a certain file for the lock screen, it boot looped a few times, apparently it tried to load from slot B where android 12 was still flashed, and it hard bricked, no button combo would work, completely bricked, it was fully charged when this happen, so I RMA`d with google and my old device is suppsoed to be delivered to Texas today, then hopefully tomorrow my if I`m lucky that my replacement gets shipped.
Click to expand...
Click to collapse
Great. If you try again to be on the safe side, download this app and install font manager
GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
A module manager for Magisk because the official app dropped support for it - GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
github.com
Just use termux and type
Code:
su -c manage_fonts
Tbh I'm not 100% it works on A13, but I tried it on the a13 beta and it worked.

verszipo said:
i am also very curious if it actually needs a motherplace replacement or simply a reflash using a JTAG (or similar specialized tool) to get it out of the bricked state.
Click to expand...
Click to collapse
I can almost 100% guarantee that they fix it through the USB port. When its going into the bricked mode, it is no doubt going into a special recovery mode that isn't documented publicly.

96carboard said:
I can almost 100% guarantee that they fix it through the USB port. When its going into the bricked mode, it is no doubt going into a special recovery mode that isn't documented publicly.
Click to expand...
Click to collapse
bro any idea how to alive again with usb port even hard brick and show only usb serial port

Any update? I have the same issue, anti-rollback has caused my phone to become soft bricked and experiences WebView crashes, along with other problems.

Lughnasadh said:
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.
Click to expand...
Click to collapse
What does RMA stand for??

liammmmnnnn said:
What does RMA stand for??
Click to expand...
Click to collapse
Return Merchandise Authorization.

Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
When I bricked my device, I had to hold power + down or up, I don't remember, for like two minutes straight while it was connected to my pc, try