Post Reply

[Q] Htc mini appears to be totally dead ?

25th September 2014, 09:59 PM   |  #41  
pure.by's Avatar
Member
Thanks Meter: 6
 
54 posts
Join Date:Joined: Jan 2010
More
Quote:
Originally Posted by HTcOneV

Having the same issue. Im not on CM11 but on Candyrom (!). Installed bubba kernel and within a few hours it died. Im thinking about sending it To htc, but I dont no if They will repair it within my warrenty. Has anybody got suggestions how To boot it up or something, tell me!

Try leaving your phone on power supply for extended period of time (several hours), then try switching it on. If not working, try holding VolumeDown+Power button for like half a minute. If nothing happens, I'm afraid I've got bad news for you.

I have no idea what HTC will do if you send them the phone, but since it's is totally dead (=useless for you) and it can't be switched on (not easy to determine that you have modded it), you can try your luck.

Quote:
Originally Posted by AnGrY sCoTsMaN

I personally tested Candy Rom days before release and have been using it since without any issue so I have 100‰ confidence in this slim based Rom, I was also tester for bubba kernel....

The fact that it did not happen to you within a limited period of time does not mean the problem does not exist. "100.0% confidence" looks very ironic next to that statement.
A lot of people got their phone bricked only after several months. Developer of CM, for instance, has been developing CM on M4 for nearly half a year untill that happened to him; I got lucky and my phone died within first half an hour; all other reports are ranged somehwere inbetween those two numbers, randomly.

[IMHO]
I'm not sure specifically about CandyRom, or bubba kernel, but this is much more likely to have cause this issue rather then an Xposed module you are suggesting.

The only configuration for M4 known to be safe is a Sense-based ROM + Sense-based kernel. Anything CM-based = ticking time bomb, everything else = lottery.
[/IMHO]
Last edited by pure.by; 25th September 2014 at 10:08 PM.
25th September 2014, 10:06 PM   |  #42  
Member
Thanks Meter: 0
 
87 posts
Join Date:Joined: Dec 2012
Quote:
Originally Posted by pure.by

Try leaving your phone on power supply for extended period of time (several hours), then try switching it on. If not working, try holding VolumeDown+Power button for like half a minute. If nothing happens, I'm afraid I've got bad news for you.

I have no idea what HTC will do if you send them the phone, but since it's is totally dead (=useless for you) and it can't be switched on (not easy to determine that you have modded it), you can try your luck.


The fact that it did not happen to you within a limited period of time does not mean the problem does not exist. "100.0% confidence" looks very ironic next to that statement.
A lot of people got their phone bricked only after several months. Developer of CM, for instance, has been developing CM on M4 for half a year untill that happened to him; I got lucky and my phone died within first half an hour; all the other reports are ranged somehwere inbetween these two numbers randomly.
I'm not sure specifically about CandyRom, or bubba kernel, but this is much more likely to have cause this issue rather then an Xposed module you are suggesting.

IMHO, the only configuration for M4 known to be safe is a Sense-based ROM + Sense-based kernel. Anything CM-based = ticking time bomb, everything else = lottery. (/IMHO)


Alright guys, last hope. I will leave the phone on the wall charger for the whole night, and will try To boot it up tomorrow. To be honnest I think the motherboard Is broken, but you never know.
25th September 2014, 10:41 PM   |  #43  
AnGrY sCoTsMaN's Avatar
OP Senior Member
Flag Scotland
Thanks Meter: 115
 
261 posts
Join Date:Joined: Nov 2011
More
Quote:
Originally Posted by pure.by

The fact that it did not happen to you within a limited period of time does not mean the problem does not exist.

Hmm approx months on same Rom, I would say that's a substantial amount of time! There has been no records of "sudden death" or "bricked devices" on Candyrom (slim based) despite an overwhelming amount of downloads

.
Quote:
Originally Posted by pure.by

"100.0% confidence" looks very ironic next to that statement.

Not at all and i cant see how you would come to that conclusion?

Quote:
Originally Posted by pure.by

A lot of people got their phone bricked only after several months. Developer of CM, for instance, has been developing CM on M4 for nearly half a year untill that happened to him; I got lucky and my phone died within first half an hour; all other reports are ranged somehwere inbetween those two numbers, randomly.

Yeah im aware of this! as you can see i done the OP on this.and folloow the M4 Thread daily

Quote:
Originally Posted by pure.by

I'm not sure specifically about CandyRom, or bubba kernel, but this is much more likely to have cause this issue rather then an Xposed module you are suggesting.

Firstly i wasn't suggesting anything! merely asking the question to rule out any xposed module conflicts! as , as you will know that certain modules can have conflicts with the behaviour of certain roms, causing things to fail etc etc. also you may have noticed that i asked about modded hboots and scripts etc! These were initial questions that were leading up to further questions about there phone setup as I was trying to gain further info

Quote:
Originally Posted by pure.by

[I][IMHO]The only configuration for M4 known to be safe is a Sense-based ROM + Sense-based kernel.

Thats your opinion! But Im pretty sure there was 1 brick incident on bilals sense rom! ive also found on the GPE edition there is no incall volume (no dial tone etc). Edit in call sound fix available

Quote:
Originally Posted by pure.by

Anything CM-based = ticking time bomb,

Yes its documented that cm11 has an issue, but is being worked on...still, many users that have this installed have had no issue whatsoever !

Quote:
Originally Posted by pure.by

everything else = lottery

That again is your opinion, and TBH is scaremongering. No reports at all on slim based roms...(i think this has been discussed at length in other threads so im not going to go into it again, but if you knew how to compile a rom from source then i think that would give you a valuable insight)

edit: there are also alot of reports out there about unrooted, unmodified, totally stock M4s going into bootloop, wont turn on etc...... just FYI

CHEERS
Last edited by AnGrY sCoTsMaN; 26th September 2014 at 07:03 AM.
The Following User Says Thank You to AnGrY sCoTsMaN For This Useful Post: [ View ]
26th September 2014, 08:13 PM   |  #44  
Member
Thanks Meter: 0
 
87 posts
Join Date:Joined: Dec 2012
So I had no luck with boothing the thing up. I decided To send it for a repair. I hope they wont find out That it was rooted and stuff...
Do you guys think they will?
26th September 2014, 08:32 PM   |  #45  
AnGrY sCoTsMaN's Avatar
OP Senior Member
Flag Scotland
Thanks Meter: 115
 
261 posts
Join Date:Joined: Nov 2011
More
Quote:
Originally Posted by HTcOneV

So I had no luck with boothing the thing up. I decided To send it for a repair. I hope they wont find out That it was rooted and stuff...
Do you guys think they will?

Depends on what part of the world your from? So countries deem rooting your device as voiding warranty. (there's a link in this thread somewhere that I posted about your eu rights) Also depends on if your sending it to HTC direct or one of there 'trusted' repair centers. When you unlock bootloader at HTC Dev it's a unique code against your phones serial number ... The third party repair centre are not as thorough in there checks!

Edit- read this link (does not apply in UK as local (uk) laws take presidence ) http://forum.xda-developers.com/show....php?t=2666925
Last edited by AnGrY sCoTsMaN; 26th September 2014 at 08:36 PM.
26th September 2014, 09:17 PM   |  #46  
Member
Thanks Meter: 0
 
87 posts
Join Date:Joined: Dec 2012
Quote:
Originally Posted by AnGrY sCoTsMaN

Depends on what part of the world your from? So countries deem rooting your device as voiding warranty. (there's a link in this thread somewhere that I posted about your eu rights) Also depends on if your sending it to HTC direct or one of there 'trusted' repair centers. When you unlock bootloader at HTC Dev it's a unique code against your phones serial number ... The third party repair centre are not as thorough in there checks!

Edit- read this link (does not apply in UK as local (uk) laws take presidence ) http://forum.xda-developers.com/show....php?t=2666925


As i'm from the Netherlands I think That this also applies To me. I sent it To Dynafox reapair center. This morning I chatted with HTC about what happend. I told them that I rooted the device, and they answered me That my warrenty was gone (!). They told me That I should send it to Dynafox. As they say this, I guess That its not a third party repair center. I didn't tell Dynafox about the rooting thing as I hope the will not find it out . And yeah I unlocked it with HTC dev.
27th September 2014, 09:05 AM   |  #47  
LQi's Avatar
Member
Thanks Meter: 20
 
60 posts
Join Date:Joined: Apr 2013
Quote:
Originally Posted by HTcOneV

As i'm from the Netherlands I think That this also applies To me. I sent it To Dynafox reapair center. This morning I chatted with HTC about what happend. I told them that I rooted the device, and they answered me That my warrenty was gone (!). They told me That I should send it to Dynafox. As they say this, I guess That its not a third party repair center. I didn't tell Dynafox about the rooting thing as I hope the will not find it out . And yeah I unlocked it with HTC dev.

I also sent mine to dynafix, they took 2 months to repair nu phone but they fixed it for free. On the resume they said they replaced the mainboard, so I guess with your phone in this state, they arent even able to check wether it is s-off or not
The Following User Says Thank You to LQi For This Useful Post: [ View ]
27th September 2014, 11:02 AM   |  #48  
Member
Thanks Meter: 0
 
87 posts
Join Date:Joined: Dec 2012
Quote:
Originally Posted by LQi

I also sent mine to dynafix, they took 2 months to repair nu phone but they fixed it for free. On the resume they said they replaced the mainboard, so I guess with your phone in this state, they arent even able to check wether it is s-off or not


Alright good To hear That but I dont wanna wait two months[emoji27]
27th September 2014, 11:32 AM   |  #49  
LQi's Avatar
Member
Thanks Meter: 20
 
60 posts
Join Date:Joined: Apr 2013
They had to order new parts from Taiwan, thats why it took so long.
29th September 2014, 04:06 PM   |  #50  
pure.by's Avatar
Member
Thanks Meter: 6
 
54 posts
Join Date:Joined: Jan 2010
More
Quote:
Originally Posted by HTcOneV

Alright good To hear That but I dont wanna wait two months[emoji27]

I would be happy to wait for two months to get a $380-device-which-warranty-I-knowingly-voided replaced for free

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes