Related
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.
I recently obtained a Samsung Rugby Smart, my father upgraded to a new phone and I received his old Rugby, the Rugby is less than a year old and still covered under warranty. This is the first Smartphone I've owned, though I have experience with the Google Nexus 7 so I'm not completely out of the loop on how the devices works.
About a week or a little more after I got the phone and got it set up and rooted the auto-rotate function stopped working, the phone is permanently stuck in landscape regardless of whether or not auto-rotate is toggled. I've read through several threads, removed battery while the phone is on, performed a factory reset three times now, etc, and while I have downloaded an app that allows me to change the rotation I do not consider that to be a fix to the problem. I've been in contact with the manufacturer and the next time I call them I will be approved to send the phone in to be repaired or replaced. I would, however, prefer not to do that and am hoping that someone here might have different suggestions.
That said, if i do need to send it in to be replaced, I obviously need to remove root before I do that. I've been looking at the Kingo Root Android app so far this morning, but it doesn't seem to support my Rugby, what are the suggestions for the safest method of removing root from the phone? I've been reading around the forums but would like a second opinion.
RainbowMagicMarker said:
I recently obtained a Samsung Rugby Smart, my father upgraded to a new phone and I received his old Rugby, the Rugby is less than a year old and still covered under warranty. This is the first Smartphone I've owned, though I have experience with the Google Nexus 7 so I'm not completely out of the loop on how the devices works.
About a week or a little more after I got the phone and got it set up and rooted the auto-rotate function stopped working, the phone is permanently stuck in landscape regardless of whether or not auto-rotate is toggled. I've read through several threads, removed battery while the phone is on, performed a factory reset three times now, etc, and while I have downloaded an app that allows me to change the rotation I do not consider that to be a fix to the problem. I've been in contact with the manufacturer and the next time I call them I will be approved to send the phone in to be repaired or replaced. I would, however, prefer not to do that and am hoping that someone here might have different suggestions.
That said, if i do need to send it in to be replaced, I obviously need to remove root before I do that. I've been looking at the Kingo Root Android app so far this morning, but it doesn't seem to support my Rugby, what are the suggestions for the safest method of removing root from the phone? I've been reading around the forums but would like a second opinion.
Click to expand...
Click to collapse
Temp-unroot would help in this situation, I think..
MayB4ck said:
Temp-unroot would help in this situation, I think..
Click to expand...
Click to collapse
That is not something I am familiar with, how does it work?
Hi all, ok tonight/this morning at work while on my break i went to do my usual thing of having food and watching a tv show via cartoon hd about 2mins in and my phone switched off.....now i thought it was dead so plugged in the charger but no led light, or screen on to say its charging.....i did a bit of googling and find out about the bootloop thingy buuuuut mines not looping, its swtiching on to the LG logo [i did the bootloader unlocker thingy etc so it says tha in the top corner] then it goes off.......i also get pulsing blue led lights too.....if i press, hold the power button after i get nothing, i have to take the battery out and then its rinse and repeat
Hi,
Same thing happened to me today. I was taking a shot and it switched off and same scenario.It seems that we had encountered an bootloader brick in which our device enters in some special bootloader mode in which when you connect it to the computer in the device manager it shows up as Qhsusb_bulk. I read the whole internet and there is a similar brick with G3 the guys were able to fix it. Even there is a tutorial on how to do this which I think is applicable to our device. I was able to install the required drivers and etc. but there is one big problem - I followed the guide and came into one serious problem - we need a special mbn file so we can recover our device and the sad thing is nobody on the internet doesn't have it still. There are many people like us who got selfbricked G4 and cannot fix it without this file. Please if somebody can help us please share the file so we can fix our devices. THANK YOU !
Link to the g3 unbrick guide
ive seen lots about the bootloop issue, but the thing is mine isnt doing a loop [i have to take the battery out/ pop it it back in, to switch it on then after 10-20 seconds on the LOGO it turns off
thewhisper said:
Hi,
Same thing happened to me today. I was taking a shot and it switched off and same scenario.It seems that we had encountered an bootloader brick in which our device enters in some special bootloader mode in which when you connect it to the computer in the device manager it shows up as Qhsusb_bulk. I read the whole internet and there is a similar brick with G3 the guys were able to fix it. Even there is a tutorial on how to do this which I think is applicable to our device. I was able to install the required drivers and etc. but there is one big problem - I followed the guide and came into one serious problem - we need a special mbn file so we can recover our device and the sad thing is nobody on the internet doesn't have it still. There are many people like us who got selfbricked G4 and cannot fix it without this file. Please if somebody can help us please share the file so we can fix our devices. THANK YOU !
Link to the g3 unbrick guide
Click to expand...
Click to collapse
on G2 you get security boot error phone is detected as QHUSb_BULK. on G2 the fix was to enter download mode. in G2 vol up then plug usb.
using TOT method and flash tools . flash stock firmware fixed my soft brick.
not sure about the file you mention, maybe you do need it..
jamious-daywalker said:
now i thought it was dead so plugged in the charger but no led light, or screen on to say its charging.....i did a bit of googling and find out about the bootloop thingy buuuuut mines not looping, its swtiching on to the LG logo [i did the bootloader unlocker thingy etc so it says tha in the top corner] then it goes off.......i also get pulsing blue led lights too.....if i press, hold the power button after i get nothing, i have to take the battery out and then its rinse and repeat
Click to expand...
Click to collapse
I have the issue. I don't do anything special but my phone reboot and stuck on lg logo. But now my phone doesn't want to boot. Sometimes he detect when I'm trying to charge it but often not. Yesterday I boot on download mode and recovery but today it's impossible... I think I have some hardware issue ? Or software with the bootloader...
I don't know how to fix that without access to download/recovery mode :crying:
Same here. Sometimes it boots into recovery/download but most of the times it doesn't. It's a hardware problem I think as LG officially confirmed that there were problems during the building proccess of the first G4 series. I don't want to sound bad but soon or later all phones built before october last year will get into bootloop. I was hoping it won't happen to me - I'm very light user with only light standart apps with no games and other heavy stuff, so the problem wasn't caused by overheating by heavy multitasking. Anyway it happened and I'm pretty sure it's harware related but if somebody can provide the tot and mbn files I will be more than happy to try the g2/g3 unbrick method. The main problem is that these files are not available for h815. I found on other forum tot files for other variants than h815 So if somebody have the tot filesfor h815 please share so we can try to unbrick our G4. Thanks!
same thing heppened to my g4 this week. i called lg last night and they agreed to repair it. i'd just gave them a call.
I sent mine for repair today. I hope they will agree to repare it even that it's with unlocked bootloader and with rooted custom rom !!! What you think ? Will I have problems with them because of that ?
Happened with my phone as well. It was rooted so i was hella scared if they didn't accept my phone. But soon they told me phone's motherboard has gone bad and will be replaced. Got my phone with a brand new motherboard after a couple of hours.
P.s. all your data will be gone
Sent from my LG-H818 using XDA-Developers mobile app
clotveins said:
Happened with my phone as well. It was rooted so i was hella scared if they didn't accept my phone. But soon they told me phone's motherboard has gone bad and will be replaced. Got my phone with a brand new motherboard after a couple of hours.
P.s. all your data will be gone
Sent from my LG-H818 using XDA-Developers mobile app
Click to expand...
Click to collapse
So the same problem just happened to my lg H815 with unlocked bootloader, am really f***ed without my phone, gonna call LG UK tomorrow, anything in particular I should say? also looking for solutions I saw many people are starting to have this issue now too - any official comments from LG?
P.S. if you have an LG G4 you should start backing up all your data now
This literally just happened in the last 15 minutes to me as well. Random reboot right after I woke up the phone and now stuck on the LG splash screen. Light user here, never did anything with the phone that would have heavily stressed it physically or computing-wise, so I also concur it's an inevitability for earlier runs of G4 phones.
Luckily, I backed up everything through TWRP last Thursday by chance because I was updating Xposed to the latest version and swapping to a faster 128GB microSDXC. At worst, I might have lost a handful of unimportant text messages.
Not worth the time to try to figure out any cheap fixes myself, I just got done submitting a repair request to LG.
I ordered LG G4 H815 and I hope to not see any kind of these issues
irishlad99 said:
So the same problem just happened to my lg H815 with unlocked bootloader, am really f***ed without my phone, gonna call LG UK tomorrow, anything in particular I should say? also looking for solutions I saw many people are starting to have this issue now too - any official comments from LG?
P.S. if you have an LG G4 you should start backing up all your data now
Click to expand...
Click to collapse
Guy at service center said its internally communicated all LG G4's motherboard will have to be changed at least once.
And just say you dont know what happened exactly. Slept and in the morning my phone won't work
clotveins said:
Guy at service center said its internally communicated all LG G4's motherboard will have to be changed at least once.
And just say you dont know what happened exactly. Slept and in the morning my phone won't work
Click to expand...
Click to collapse
at least once?? many had sent phone , then again having bootloop after repair..???
raptorddd said:
at least once?? many had sent phone , then again having bootloop after repair..???
Click to expand...
Click to collapse
I have got my phone repaired for like 4-5 times. 3 times motherboard change, 1 time display change and 1 time volume button pannel change.
clotveins said:
I have got my phone repaired for like 4-5 times. 3 times motherboard change, 1 time display change and 1 time volume button pannel change.
Click to expand...
Click to collapse
all under warranty?? not counting display? or did you get dead pixel?
raptorddd said:
all under warranty?? not counting display? or did you get dead pixel?
Click to expand...
Click to collapse
Yup. All under warranty and counting display replacement as well. No dead pixels as well and phone was rooted once during motherboard replacement
Sent from my LG-H818 using XDA-Developers mobile app
So This is the whole story -
When I got my Redmi Note 3 I stopped using my Canvas A1 and vaguely i remember that it was having software issues, rather than fixing it I just kept it away for a lot of months, and vaguely I remember that it just needed some flashing of rom and it would've gotten fixed.
And after all these months i'm need of this phone again. I don't remember much in depth details of the processes involved with it like flashing stuff etc. But I gathered as much knowledge as I could from the docs I had stored as backup & from the internet.
I installed different stock roms And in different ways. IMO I think the flashing process was successful, but the screen is not turning on. Only once when I connected it to PC, the charging battery sign appeared(flashing thrice) that was it. Nothing after that. And whenever I connect it to PC it detects the phone.
For now I've given it to a repair guy but I don't have much hope. He was saying that it could be just software problem, but I don't agree. If a smart/expert person could comment on this thread so that we all could get some benefit out of it, in order to solve the situation or at least in my case I could research on something specific in the meantime.
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