Guest rangeoshun Posted June 16, 2014 Report Share Posted June 16, 2014 (edited) Hi all! On a bright monday morning last weak I checked my phone for how late I was from work. I saw I was F'in late, put the phone in my pocket, hurried on my way. In the office I took it out to put it on the desk. In an hours time or so I tried to check messages, and such but the phone was off, and unresponsive since... It happen out of nowhere, and it was still so young, and had so much ROMs ahead of it. I already tried to: - take out battery and reinsert. - put it on charger with or without battery. - charge it for a while and try again. No response.. not even a led blink :/ Anyone had similar issues or heard of such? Any advice I could try my self? Thanks for any (constructive) advice, except for rectal application :) Edited June 16, 2014 by rangeoshun Link to comment Share on other sites More sharing options...
Guest alekcacko Posted June 17, 2014 Report Share Posted June 17, 2014 Hmm what was last flashed rom? Cyanogenmod11 or? . The similar situation was here(the phone is huawei with the same processor) Link to comment Share on other sites More sharing options...
Guest rangeoshun Posted June 19, 2014 Report Share Posted June 19, 2014 It was the previous build of KonstaT's CM11 or the one before that.. Thanks, I'll take a deep look of the post you linked here! Link to comment Share on other sites More sharing options...
Guest rangeoshun Posted August 18, 2014 Report Share Posted August 18, 2014 (edited) Hi all! I had time to read the post too, but it can't be done here, because it's in DLOAD mode. Now! I have the drivers, and the qualcom config program, but couldn't find anything to flash, in hope of a resurrection.. I only managed to get it recognized. Other devices were recovered by flashing something called a "hboot.img", but i couldn't find out exactly what it is :D So, if anyone knows about these stuff I would really apprechiate the help, or just pointing me in the right direction! Or this won't help? I was given the infromation, it could have been an internal memory corruption, so maybe a fresh flash could solve it I thought. And excuse my potential ignorance :) Edited August 19, 2014 by rangeoshun Link to comment Share on other sites More sharing options...
Guest rangeoshun Posted August 21, 2014 Report Share Posted August 21, 2014 It seems I would need a complete memory dump from a working blade3 to even start trying! :D Anyone could make me a raw dump? Thankz!! Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now