Okay so i was on Marsh mellow 6.0.1 and then the tablet died due to battery running out. Once i rebooted it, it was stuck at the LG logo and said something like "No Secure Booting". It just froze. Then i got into download mode, opened LG Support Tool and tried Updating Software as i have had this exact problem before and this worked last time. However this time it got to around 83% then the tablet lost connection. Ive tried this multiple times now and every 4-5Mins it just disconnects.
However after many failed attempts it now doesn't enter download mode, doesn't make sound when connected to PC and doesn't show any life.
also cannot access TWRP
any help would be appreciated!
In Windows' Device Manager, does the tablet show up in the Modem or Ports section? If it shows up as "QHSUSB_BULK 9008", Google that and at least if you have a TOT file available for your particular model and variant, then you should be able to recover using directions/program you can find.
I have the same problem with a G Pad of mine. It was working fine, boot looped (with 50% battery) then switched off. No life at all, no amount of button combinations or charged plugging in will bring it back. I've resorted to finding a donor motherboard to see if it'll work with a new motherboard or if some other component is at fault!
Rackers said:
I have the same problem with a G Pad of mine. It was working fine, boot looped (with 50% battery) then switched off. No life at all, no amount of button combinations or charged plugging in will bring it back. I've resorted to finding a donor motherboard to see if it'll work with a new motherboard or if some other component is at fault!
Click to expand...
Click to collapse
Did you check what I said in my post previous to yours?
roirraW "edor" ehT said:
Did you check what I said in my post previous to yours?
Click to expand...
Click to collapse
Hi,
Yes, nothing in device manager under Modem or Ports. I don't get any noise when I plug or unplug it either so the computer isn't seeing it.
Rackers said:
Hi,
Yes, nothing in device manager under Modem or Ports. I don't get any noise when I plug or unplug it either so the computer isn't seeing it.
Click to expand...
Click to collapse
That sucks, mate. Sorry to hear that! Good luck with the motherboard angle.
Thanks, fingers crossed!
roirraW "edor" ehT said:
That sucks, mate. Sorry to hear that! Good luck with the motherboard angle.
Click to expand...
Click to collapse
Just to confirm; new motherboard has worked, tablet is now back to life. Not sure what could have happened to the old one but I did buy this second hand and it was a prone crasher and the tablet had already been opened so who knows what they did to it.
Rackers said:
Just to confirm; new motherboard has worked, tablet is now back to life. Not sure what could have happened to the old one but I did buy this second hand and it was a prone crasher and the tablet had already been opened so who knows what they did to it.
Click to expand...
Click to collapse
Good! Thanks for the update!
Rackers said:
Just to confirm; new motherboard has worked, tablet is now back to life. Not sure what could have happened to the old one but I did buy this second hand and it was a prone crasher and the tablet had already been opened so who knows what they did to it.
Click to expand...
Click to collapse
I'm curios where you and aprox how much did you pay for the new hardware? Hopefully you it's not too rude of me to ask...
Thanks in advance
Sparks639 said:
I'm curios where you and aprox how much did you pay for the new hardware? Hopefully you it's not too rude of me to ask...
Thanks in advance
Click to expand...
Click to collapse
Not at all; I paid £50 for the new motherboard. Just luck of the draw somebody was selling a G Pad with a broken screen on eBay.
Thanks
Thank you, I'll keep an eye out.
Sent from my Nexus 6 using Tapatalk
Update!!
Currently got the tablet back into working order no replacement hardware needed.
Problem:
Tablet not responding to any user input or software detection. not charging and no life of any sort.
Solution:
( 1 )Charge tablet with a powerful legitimate LG charger (not a cheap Chinese knockoff).
( 2 )Leave on charge for at least 1 and a half days.
( 3 )Press power button to check if device powers, if not continue.
( 4 )Connect USB to PC, Press and hold Volume Up and Down simultaneously and insert USB into charger port.
( 5 )Download mode should appear and you'll be able to flash stock from LG Support Tools or LG Flash Tool
Disclaimer:
May not work for all as some problems may occur for different reasons.
~Happy Un-Bricking!
Related
Hello friends,
My apologies if I have posted in the wrong section.
My Nexus 7 2013 has Android 4.4.4 on it, it's unlocked, rooted, and has the ElementalX-N7-2.13 custom kernel. It ran flawless until a few days ago, Adaway updated definitions, and asked for a reboot. I have done this several times before without issue. This last time, the screen went black, and no matter what button press combinations, will not boot even into recovery. Tried everything I know of. Last of which, was plugging it into my pc, and utilizing the Wugs tool kit "soft bricked" script. Of course it doesn't work, because I don't have adb/fastboot status. My pc no longer even recognizes the tablet. All that shows up, is Qualcomm HS-USB QDLoader 9008 Com3.
Fully charging it, and unplugging the battery for a few hours, has done nothing. Do you think the bootloader got damaged? Why would Adaway do that??
You guys are my last hope, before it hits the trash, as I am not turning it into Asus for warranty replacement. I have way too much sensitive stuff on it (no it's not porn) for it to fall in someone else's hands.
Take pitty on a pathetic noob. Greatly appreciate any info. THANK YOU!
DaveImagery said:
Hello friends,
My apologies if I have posted in the wrong section.
My Nexus 7 2013 has Android 4.4.4 on it, it's unlocked, rooted, and has the ElementalX-N7-2.13 custom kernel. It ran flawless until a few days ago, Adaway updated definitions, and asked for a reboot. I have done this several times before without issue. This last time, the screen went black, and no matter what button press combinations, will not boot even into recovery. Tried everything I know of. Last of which, was plugging it into my pc, and utilizing the Wugs tool kit "soft bricked" script. Of course it doesn't work, because I don't have adb/fastboot status. My pc no longer even recognizes the tablet. All that shows up, is Qualcomm HS-USB QDLoader 9008 Com3.
Fully charging it, and unplugging the battery for a few hours, has done nothing. Do you think the bootloader got damaged? Why would Adaway do that??
You guys are my last hope, before it hits the trash, as I am not turning it into Asus for warranty replacement. I have way too much sensitive stuff on it (no it's not porn) for it to fall in someone else's hands.
Take pitty on a pathetic noob. Greatly appreciate any info. THANK YOU!
Click to expand...
Click to collapse
Since its showing this Qualcomm HS-USB QDLoader 9008 Com3. Its bricked. Sorry
Btw stop using toolkits. Maybe using that bootloader got corrupted.
varuntis1993 said:
Since its showing this Qualcomm HS-USB QDLoader 9008 Com3. Its bricked. Sorry
Btw stop using toolkits. Maybe using that bootloader got corrupted.
Click to expand...
Click to collapse
Thought I read on another thread, someone recovered theirs, by using QPST? Or is that just wishful thinking?
Sorry to see this dude, you might want to check this dude out. I have ever heard nothing but good things about his jTag work, not sure if he can help but worth a try good luck!!! http://mobiletechvideos.mybigcommerce.com
Sent from my Nexus 7 pimpin AOSPA 4+
When it launched the original Nexus 7 was a landmark device. It was the first of the budget tablets that actually delivered a premium experience and the 7-inch form factor made it the perfect bridge between phones and tablets making it both a pleasure to interact with while remaining (jacket) pocketable. However just over one year on and people are complaining that it’s become slow to the point of unusable.
snipe2nite said:
Sorry to see this dude, you might want to check this dude out. I have ever heard nothing but good things about his jTag work, not sure if he can help but worth a try good luck!!!
Sent from my Nexus 7 pimpin AOSPA 4+
Click to expand...
Click to collapse
Thanks, but it appears this thing is dead. I know not to use Adaway ever again though. Adaway did something to the bootloader.
Did you contact him? That dude can do magic with bricks!!! You can check his YouTube channel at http://www.youtube.com/user/MobileTechVideos/videos
Sent from my Nexus 7 Pimpin AOSPA 4+
DaveImagery said:
Thanks, but it appears this thing is dead. I know not to use Adaway ever again though. Adaway did something to the bootloader.
Click to expand...
Click to collapse
No.
mindmajick said:
No.
Click to expand...
Click to collapse
No what? It can't be a coincidence, it bricked immediately after Adaway updated, and required a reboot.
DaveImagery said:
No what? It can't be a coincidence, it bricked immediately after Adaway updated, and required a reboot.
Click to expand...
Click to collapse
Adaway does nothing to the boot loader. It was either:
A. A coincidence
B. Your device is bricked from adaway but the bootloader is fine.
DaveImagery said:
Hello friends,
My....!
Click to expand...
Click to collapse
Okay, here's what you do.
Use a DIT guide and open it. I have taken the back case off myself with my nail. It's not hard.
Take out the battery and disconnect it.
Reconnect the battery and try to turn it on.
Use power+volume down for 2 minute , and see if it powers up.
Secondly hold power+ volume down for a minute and then power+volume up for a minute before disconnecting the battery. See it it powers up. If not try opening the back case, there are many guides, I have one in general section but use fixit guide which is more clear and professional.
Good luck.
mindmajick said:
Adaway does nothing to the boot loader. It was either:
A. A coincidence
B. Your device is bricked from adaway but the bootloader is fine.
Click to expand...
Click to collapse
Oh I see what you're saying. Ok, thank you for info.
Hnk1 said:
Okay, here's what you do.
Use a DIT guide and open it. I have taken the back case off myself with my nail. It's not hard.
Take out the battery and disconnect it.
Reconnect the battery and try to turn it on.
Use power+volume down for 2 minute , and see if it powers up.
Secondly hold power+ volume down for a minute and then power+volume up for a minute before disconnecting the battery. See it it powers up. If not try opening the back case, there are many guides, I have one in general section but use fixit guide which is more clear and professional.
Good luck.
Click to expand...
Click to collapse
I'm not even sure at this point, if the battery isn't stone dead. I messed around with it so much, trying to get it working again. I tried all the button combinations, though not exactly as you have detailed. I think I will charge it via the wall charger for a while, then disassemble it again, and try your suggestion.
Several people told me, it's beyond recovery, so put it in the closet and forgot about it.
Thank you, stay tuned.......
DaveImagery said:
I'm not even sure at this point, if the battery isn't stone dead. I messed around with it so much, trying to get it working again. I tried all the button combinations, though not exactly as you have detailed. I think I will charge it via the wall charger for a while, then disassemble it again, and try your suggestion.
Several people told me, it's beyond recovery, so put it in the closet and forgot about it.
Thank you, stay tuned.......
Click to expand...
Click to collapse
Don't get too excited. There're small delicate parts and ribbon is also very fragile so use fixit guide
https://www.ifixit.com/Teardown/Nexus+7+2nd+Generation+Teardown/16072
Just disconnect the battery like this. Don't do anything more
https://d3nevzfk7ii3be.cloudfront.net/igi/T1bQFwmsYTXKYX11.medium
Hnk1 said:
Don't get too excited. There're small delicate parts and ribbon is also very fragile so use fixit guide
https://www.ifixit.com/Teardown/Nexus+7+2nd+Generation+Teardown/16072
Click to expand...
Click to collapse
Why is it necessary to remove the battery? Isn't it enough, just to unplug it? That way you don't mess with the ribbon cables?
DaveImagery said:
Why is it necessary to remove the battery? Isn't it enough, just to unplug it? That way you don't mess with the ribbon cables?
Click to expand...
Click to collapse
Just UNPLUG IT, DON'T DO ANYTHING MORE!
THATS EXACTLY WHAT I SAID showing you second picture .
Remove battery is a term, we usually use for phone to take it out in order to disconnect kits power source . That's exactly what we want here. unplug it!
Hnk1 said:
Just UNPLUG IT, DON'T DO ANYTHING MORE!
THATS EXACTLY WHAT I SAID showing you second picture .
Remove battery is a term, we usually use for phone to take it out in order to disconnect kits power source . That's exactly what we want here. unplug it!
Click to expand...
Click to collapse
Yeah that makes sense. As I outlined in my initial post, I have unplugged the battery already, with no luck. There didn't seem to be any real consensus on the button press procedure. I've read 30 seconds, 1 minute, press power and both volume up and down at same time, as well as what you have suggested, just not for the length of time you said. Worth a try I suppose, I'll be shocked if it actually works.
Right now I have no way of knowing how much charge (if any) the battery has. Guess I could put a meter on the battery leads. I think I'll just let it wall-charge for a few hours.
Thanks again, stay tuned...........
DaveImagery said:
Yeah that makes sense. As I outlined in my initial post, I have unplugged the battery already, with no luck. There didn't seem to be any real consensus on the button press procedure. I've read 30 seconds, 1 minute, press power and both volume up and down at same time, as well as what you have suggested, just not for the length of time you said. Worth a try I suppose, I'll be shocked if it actually works.
Right now I have no way of knowing how much charge (if any) the battery has. Guess I could put a meter on the battery leads. I think I'll just let it wall-charge for a few hours.
Thanks again, stay tuned...........
Click to expand...
Click to collapse
Lad,
Just try the button trick first of all.
Power+ up
Power + down
Power+ up n down
Plug the charger to nexus and then try these combinations for two minutes each and report.
Only then you should start with taking off the back cover!
I suppose about should take you 15 minutes so I'm waiting for good news!
Hnk1 said:
Lad,
Just try the button trick first of all.
Power+ up
Power + down
Power+ up n down
Plug the charger to nexus and then try these combinations for two minutes each and report.
Only then you should start with taking off the back cover!
I suppose about should take you 15 minutes so I'm waiting for good news!
Click to expand...
Click to collapse
Not having any luck. Thanks anyway
DaveImagery said:
Not having any luck. Thanks anyway
Click to expand...
Click to collapse
Now try the battery method !
Good luck
Hi to all, After two years of good working S4 mini is giving up. The last time when the problem is occured, the phone was „forced“ swiched off because of low battery. It was put on charger to charge normally and it did it as usual. But, when it was swiched on again it stayed in the boot loop on the Samsung logo over and over again. When I tried to come into recovery, it shows as normally when it starts to go into recovery with text that it has, as last, succesfully loaded CRC and then it shows for a short text: „There is no command“ and immediately reboot and come out of recovery. I went to „Download mode“ and I flashed in Odin, with no problem, the newest S4 mini official ROM but it didn't fix the problem. Any expiriance or sugestions are welcome... Thanks in advance !
If someone knows... Is it possible that some hardware component inside the phone which is responsible for recovery to work, that is burned out or something like that... ? And if so, could it be replaceable ? Thanks in advance !
Someone with a similar problem and some solution, maybe ?
Sent from my GT-N7000 using XDA-Developers mobile app
Boombastical said:
Hi to all, After two years of good working S4 mini is giving up. The last time when the problem is occured, the phone was „forced“ swiched off because of low battery. It was put on charger to charge normally and it did it as usual. But, when it was swiched on again it stayed in the boot loop on the Samsung logo over and over again. When I tried to come into recovery, it shows as normally when it starts to go into recovery with text that it has, as last, succesfully loaded CRC and then it shows for a short text: „There is no command“ and immediately reboot and come out of recovery. I went to „Download mode“ and I flashed in Odin, with no problem, the newest S4 mini official ROM but it didn't fix the problem. Any expiriance or sugestions are welcome... Thanks in advance !
Click to expand...
Click to collapse
Did you solve it? I'm having the same problem
Hi Danaidh, Sorry but not at all. I have spoken with some smartphone repairing technician and he told me that it is a hardware problem and that he has to solder some chip and to replace it with a new one. Because it was all happening abroad (Central East Europe), I thought that I will find some software solution here on XDA. Here where I live (West Europe) I didn't try to bring my smartphone to some smartphone repairing centar because they will simply swap a motherboard and they will charge me a full price what means is much better to buy a new smartphone then repairing this one. Even worst, after five months my phone doesn't charge any more and doesn't start at all and all this „smelt“ now on the real hardbrick. I have regulary charged a baterry to keep my S4 mini i9195 in life, but it could be also that it has swiched on it self during transport in my bag and that I didn't notice this and that it has used all battery power by swichining on and off in the infinite loop... But I will check it later if it will be visable on my PC without battery... If you find some other solution send me a message, please... Thanks in advance... Cheers !
Sent from my GT-N7000 using XDA-Developers mobile app
I just checked if it will be „seen“ on my PC and it has installed drivers and it's seen as „Qualcomm HS-USB QDLoader 9008“ on COM6 port... So it means that battery died...
But fortunatelly it means there is still hope for this „little bug“(S4 mini)...
Sent from my GT-N7000 using XDA-Developers mobile app
Same problem here.. Did they say at least which chip should be replaced?
Same problem here.
Same problem, any resolution?
Gianasy, he didn't say which chip particularly should be replaced, but he mentioned the one who's responsible for recovery ... Or something like that... So, if you have some news on it, it will be nice to share it with us later on... Thanks !
Sent from my GT-N7000 using XDA-Developers mobile app
Similar problem here
Boombastical said:
Someone with a similar problem and some solution, maybe ?
Sent from my GT-N7000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Similar problem here but still no solution :/
Link to thread here
Boombastical said:
Hi Danaidh, Sorry but not at all. I have spoken with some smartphone repairing technician and he told me that it is a hardware problem and that he has to solder some chip and to replace it with a new one. Because it was all happening abroad (Central East Europe), I thought that I will find some software solution here on XDA. Here where I live (West Europe) I didn't try to bring my smartphone to some smartphone repairing centar because they will simply swap a motherboard and they will charge me a full price what means is much better to buy a new smartphone then repairing this one.
Click to expand...
Click to collapse
Interesting. I have the very same problem like you (and two friends of mine have the same problem with their s4 mini). I went to a phone repair shop and he told me, that it is "a known problem of the s4 mini" and some part of the motherboard has to be "reparied"/replaced, but he has to send it somewhere and this will take about ten days.
I have ordered a second hand (used - refurbished) mainboard for S4 Mini from China for € 22 - so I'll write here and update you what is going on in about three - four weeks from now... Till then... Cheers !
Boombastical said:
I have ordered a second hand (used - refurbished) mainboard for S4 Mini from China for € 22 - so I'll write here and update you what is going on in about three - four weeks from now... Till then... Cheers !
Click to expand...
Click to collapse
Where did you buy it? I'm searching for a shop selling mainbords for the i9192 version of the S4 Mini.
I have a phone with the same problem.
Do you think i can use adb's pull to extract something from the phone? So far nothing worked.
In order to use adb I should be able to put the phone in recovery
Birtieddu said:
Do you think i can use adb's pull to extract something from the phone? So far nothing worked.
In order to use adb I should be able to put the phone in recovery
Click to expand...
Click to collapse
If you had installed some cyanogenmod, maybe you can use adb while the phone is in recharge mode (=off). I've written a guide, how to extract your data, here.
sumeruter said:
If you had installed some cyanogenmod, maybe you can use adb while the phone is in recharge mode (=off). I've written a guide, how to extract your data, here.
Click to expand...
Click to collapse
No cyanogenmod, it's all stock.
I've tried your guide but as soon as I connect the phone (off), it turns on and keep booting (loop).
Birtieddu said:
No cyanogenmod, it's all stock.
I've tried your guide but as soon as I connect the phone (off), it turns on and keep booting (loop).
Click to expand...
Click to collapse
Interesting, it shouldn't start just by plugging the charge cable in. Someone in another thread mentioned that a defective power button might cause similar symptoms. Have you tried just holding menu and vol-up or -down while it keeps restarting?
When in windows cmd, type
Code:
adb wait-for-device
and plug in the cable then. Does it wait forever or does the command come back?
sumeruter said:
Interesting, it shouldn't start just by plugging the charge cable in. Someone in another thread mentioned that a defective power button might cause similar symptoms. Have you tried just holding menu and vol-up or -down while it keeps restarting?
When in windows cmd, type
Code:
adb wait-for-device
and plug in the cable then. Does it wait forever or does the command come back?
Click to expand...
Click to collapse
Same story, unfortunately.
I made a little video. So you can better see what's going on.
After I plug the cable the phone starts and never stop until I remove the battery.
Here the video: vid .me/9hCh (remove the space after vid)
sumeruter said:
Where did you buy it? I'm searching for a shop selling mainbords for the i9192 version of the S4 Mini.
Click to expand...
Click to collapse
Update: So, after more then one month and half of waiting, I have finaly recieved my 'secondhand' (used - at least so is stated by the seller) ordered mainboard for i9195 lte Europe S4 mini and I swapped it and it works perfect.
Site where I bought it is: Aliexpress.com - Search under: „100% work EU version i9195 unlocked motherboard full function logic board“ Succes !!!
Cheers !
Sent from my GT-N7000 using XDA-Developers mobile app
Hi folks,
I own a LG G4 AT&T version. Today, after charging to to 100%, I'd been using it normally, texting my friend. After taping the send button, I placed my G4 nearby and continued doing other stuff. & after sometime when I picked it up and double tapped the screen, it just didn't responded.
I pressed back button, I tried plugging charging cable to see whether LED is working or not, that was not working. I pushed out the battery and then put it back and tried turning on again and nothing happened at all. Its like still. Not responding at all. I tried the volume and power button combinations, tried hard reset, even tried connecting to PC and LG UP was unable to recognize, though it has all the necessary drivers installed.
I'm stuck badly, it was my daily driver, no warranty or official support in Pakistan, unfortunately.
is there any way at all to get it working or I should digest the bitter fact that its no more and move on?
Thanks.
Exact same thing happened to my wife's today... I'm at a loss. Still googling and searching this site.
Some reports of the ilapo bootloop have been the same. No nothin ded phones. In pc does it say unreconized.device or nothin at all or anything
420SYN said:
Exact same thing happened to my wife's today... I'm at a loss. Still googling and searching this site.
Click to expand...
Click to collapse
Sad to know, I, myself is at lost. Helpless.
TheMadScientist420 said:
Some reports of the ilapo bootloop have been the same. No nothin ded phones. In pc does it say unreconized.device or nothin at all or anything
Click to expand...
Click to collapse
Connected to PC, PC does not say anything at all. As if device was never connected.
any other expert who can look into and can help us? any one ?
saaqibameen said:
any other expert who can look into and can help us? any one ?
Click to expand...
Click to collapse
Apke device bricked ha take it technician motherboard replace hoga karcha 20000 tak hota ha iska
jinderation said:
Apke device bricked ha take it technician motherboard replace hoga karcha 20000 tak hota ha iska
Click to expand...
Click to collapse
seriously? in 20k, one can get a used LG G4. That's a huge loss
saaqibameen said:
seriously? in 20k, one can get a used LG G4. That's a huge loss
Click to expand...
Click to collapse
Repaired n refurbished set Korean models only for 20k good condition factory stock cost aroud 24 international 25k ...take it technician see what he says
It does sound like a bootloop issue. Mine packed up last week and it is now on the way to LG repair centre here in UK. I was taking photos and put my phone into the pocket and when i took out I couldn't even turn it on. The phone was totally dead. However taking the battery out, putting it back in and trying to start the phone for numerous times it did eventually get into booting but of course it never goes past it due to motherboard failure. Try connecting to the charger and leave it for some time and maybe you'll get to boot screen but one thing for sure is that you can say all your data goodbye no matter how sad it is and LG bastards do not take any responsibility for it apart from replacing motherboard if it is within warranty.
on saturday my phone suddenly shut off and shows no signs of life except the lg logo and then a blue screen sometimes. can anyone confirm the whole "putting the mainboard in the oven" thing to actually work? and if yes, how exactly should i do it?
Quote100 said:
on saturday my phone suddenly shut off and shows no signs of life except the lg logo and then a blue screen sometimes. can anyone confirm the whole "putting the mainboard in the oven" thing to actually work? and if yes, how exactly should i do it?
Click to expand...
Click to collapse
That sounds a little extreme TBH with you. I've only heard of people doing the oven trick for the flickering LCD fix, but I haven't paid too much attention lately so I could be wrong.
Please provide more info:
d850 rt? still on fulmics? can you manually boot into recovery(doubt it if you're blue screened but had to ask)? have you tried flashing a TOT or KDZ and going back to stock yet?
startswithPendswithOOH said:
That sounds a little extreme TBH with you. I've only heard of people doing the oven trick for the flickering LCD fix, but I haven't paid too much attention lately so I could be wrong.
Please provide more info:
d850 rt? still on fulmics? can you manually boot into recovery(doubt it if you're blue screened but had to ask)? have you tried flashing a TOT or KDZ and going back to stock yet?
Click to expand...
Click to collapse
yes d850 and yes i am still on fulmics but according to numerous other threads on different forums, this isn't a software issue. I can't get into download mode at all as the phone shows no signs of life when the power button is pressed or when its plugged in
Board expired
Quote100 said:
yes d850 and yes i am still on fulmics but according to numerous other threads on different forums, this isn't a software issue. I can't get into download mode at all as the phone shows no signs of life when the power button is pressed or when its plugged in
Click to expand...
Click to collapse
It's time to move on.same happened to me a week ago.and I found the reason that my charger was at fault .the charger damaged one of the ics.it causes the board to draw a lot of current and causing severe heating issue within seconds.
So,better buy a new phone.
Quote100 said:
yes d850 and yes i am still on fulmics but according to numerous other threads on different forums, this isn't a software issue. I can't get into download mode at all as the phone shows no signs of life when the power button is pressed or when its plugged in
Click to expand...
Click to collapse
Welp...that doesn't sound good. One last question(i think you already answered, but double checking)- so with power off, plugging the usb cable into a pc & holding vol up does nothing at all?
I guess if you're in "last resort mode" the oven may be the way to go, but I have not done it myself so I can't help much there. Here's a post from someone who had success using the oven... http://forum.xda-developers.com/showpost.php?p=68235296&postcount=7
I'd be nervous and would do it as the absolute last resort, but you could be at the "what do I have to lose, so why not?" point by now. You may want to PM the poster(or anyone else who has had success) for more info if you need it & to see if it is a lasting fix or not.
Good luck! :fingers-crossed:
startswithPendswithOOH said:
Welp...that doesn't sound good. One last question(i think you already answered, but double checking)- so with power off, plugging the usb cable into a pc & holding vol up does nothing at all?
I guess if you're in "last resort mode" the oven may be the way to go, but I have not done it myself so I can't help much there. Here's a post from someone who had success using the oven... http://forum.xda-developers.com/showpost.php?p=68235296&postcount=7
I'd be nervous and would do it as the absolute last resort, but you could be at the "what do I have to lose, so why not?" point by now. You may want to PM the poster(or anyone else who has had success) for more info if you need it & to see if it is a lasting fix or not.
Good luck! :fingers-crossed:
Click to expand...
Click to collapse
I also ventured for the oven.and within 2 seconds.my board was gone...oven trick is just a sarcasm.don't go for it.
You can extra life of 30 minutes by giving it a Sunbath for some time.
My bad - misquoted a poster.
I kind of forgot about this thread whoops
Well I have news for you guys, I got a used g3 from eBay and wanted my apps from my old phone back and you know what I did?
I stuck it into the oven. I **** you not, after 375 for 5 minutes it started working again and I was able to get my apps and data to an SD card. Its still working but I took the battery out of it to use with the replacement. Can't believe it worked tbh
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