Related
So I have been a long time follower of XDA, did all sorts of things with my Vibrant and just recently got the SGS2 from Sprint. A few days ago I flashed Calkulin's E4GT v2.6 and since then everything has gone down hill:
> The phone started acting like it was "charging" with nothing plugged in, red LED light stayed on and the battery had the charge symbol.
> Car mode began coming on over and over again.
> The phone would freeze and after I took out the battery it would automatically restart with me pushing the power button once the battery was re-inserted.
In hopes to just be down with it I flashed it back to stock with ODIN and everything seemed fine...
Now the phone is constantly freezing, Displaying that I have no service, The touch screen becomes unresponsive while charging, Car mode is still trying to launch.. not as frequently but it has happened. Other minor issues was the pattern lock would display when I woke up the phone even though I never set one...but I could do anything with the pattern to unlock it, even just touching a circle. Worse part in my opinion is either the phone will not recognize the PC or the PC will no longer recognize the phone so I can try ODIN again, same PC, drivers and USB cord being is.
Any suggestions on how I can remedy the situation?
Same thing happened to me, when I tried flashing an AIO over Calkulins you're pretty much done. You'll have to unroot and go to sprint. I ended up getting a new one since I was within the 2 week exchange.
monk3yguy said:
So I have been a long time follower of XDA, did all sorts of things with my Vibrant and just recently got the SGS2 from Sprint. A few days ago I flashed Calkulin's E4GT v2.6 and since then everything has gone down hill:
> The phone started acting like it was "charging" with nothing plugged in, red LED light stayed on and the battery had the charge symbol.
> Car mode began coming on over and over again.
> The phone would freeze and after I took out the battery it would automatically restart with me pushing the power button once the battery was re-inserted.
In hopes to just be down with it I flashed it back to stock with ODIN and everything seemed fine...
Now the phone is constantly freezing, Displaying that I have no service, The touch screen becomes unresponsive while charging, Car mode is still trying to launch.. not as frequently but it has happened. Other minor issues was the pattern lock would display when I woke up the phone even though I never set one...but I could do anything with the pattern to unlock it, even just touching a circle. Worse part in my opinion is either the phone will not recognize the PC or the PC will no longer recognize the phone so I can try ODIN again, same PC, drivers and USB cord being is.
Any suggestions on how I can remedy the situation?
Click to expand...
Click to collapse
What exactly did you use when you did this? I flashed it back to stock with ODIN
Maybe link to the file(s) you used?
Also maybe the exact steps you took. None of this sounds right. And if you flashed the complete EG30 tar you would be back exactly to when you purchased the phone. Everything would be overwritten so there really wouldn't be anything left to linger and cause issues.
Try a ##786# reset
Just_s said:
What exactly did you use when you did this? I flashed it back to stock with ODIN
Maybe link to the file(s) you used?
Also maybe the exact steps you took. None of this sounds right. And if you flashed the complete EG30 tar you would be back exactly to when you purchased the phone. Everything would be overwritten so there really wouldn't be anything left to linger and cause issues.
Click to expand...
Click to collapse
Once the device started acting funny, I basically pulled out the battery until I got home where I could flash it back.
This is the stock files I have saved to my computer:
http://forum.xda-developers.com/showthread.php?t=1351761
The phone is still somewhat usable, 3G, voice calls, everything works as normal until some of the symptoms start up again. Primarily the issues I am having is the phone completely freezing and occasionally displaying no service and of course not recognizing any PC connection.
Try a ##786# reset from dialer.
To get your MSL, in adb shell, type "getprop ril.MSL" without the quotes. If you use Android Terminal make sure you aren't using the Swype keyboard or it'll auto capitalize the "I" despite being told not to.
Initially, sounds like the USB port has some **** in it or damaged ;p
First off thank you everyone who has replied, I have definitely looked into all of your suggestions throughout the day. Here is what I have come up with.
I tried the ##786# for a clear reboot, all the symptoms still continued =(
I started figiding with the micro USB port and finally was able to get my computer and phone to connect to each other, I have also been reading that the port also causes the phone to spontaneous "ghost" charge and activate car mode.
So I am pretty sure it is a hardware issue, in particular the usb port. Tomorrow I am going to get the parts and make a jig to reset the binary counter and just take it in to Sprint and get an exchange.
Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.
You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.
Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin
Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.
Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.
Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.
I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.
"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.
Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.
15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.
Hi!
First of all i got AOKP + Franco kernel for 2w without any problem and I didn't change any option since last week.
This morning i rebooted it, it switched off and it didn't start again.
I cannot switch one my nexus again since then. I have always a black screen, also if I try to enter in download mode or in the recovery.
I tried to connect to my computer and smt times my laptop see a omap4400 (i'm not sure about the name) but after few second it disappears.
Tomorrow I'm going to the service center... But I have a big doubt:
What the hell happened this morning?
Thanks
Remove the battery for 5 minutes and try again.
If that doesn't work,
Follow this guide:
1. Download the zip file from http://forum.gsmhosting.com/vbb/f634...eeeee-1465412/, created by Legija
2. Extract zip to whatever location you're comfortable with (I used Android directory)
3. Open up Device Manager (Hold down Windows Key, press R, the type in devmgmt.msc and press OK)
4. Go to actions menu, select Add Legacy Hardware
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process
9. Once completed, unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Click to expand...
Click to collapse
biscuitownz said:
Remove the battery for 5 minutes and try again.
If that doesn't work,
Follow this guide:
Click to expand...
Click to collapse
This, if OP can't reach fastboot.
Sent from my i9250
I'm having the exact same problem. I saw my phone at maybe 10% battery in the AM, said screw it and let it die, woke up this morning and plugged the phone in and nothing. No LED light, black screen, completely unresponsive. I've tried every trick in the book, and the only one that seemed to work marginally even was using a different battery, which got my phone to boot to the encryption screen, but then shut off again. It did that twice, and now both batteries are useless.
I used Legija's program to try and bring some life back to my gnex, even though it's not the international version, just in hopes of getting some of my data back (I have already started the replacement process with Verizon since the phone was insured), but I got no luck there either.
It's extremely disappointing and annoying to me that this phone survived all sorts of ROM installations (I was also using AOKP on 4.1 if someone wants to start making connections), reformatting, tweaking, almost every setting on that phone was modified by me.
Not only that but almost any software or hardware problem I did run into I could solve in maybe an hour, but I let my charge run out and the phone just up and bricks itself? Now, that's just bull****... I would be very curious as to an explanation as to WHY on earth this would happen. Very confusing.
Not to hijack the thread, but my interest here is not restoring the phone to working condition but just seeing if I can pull my data off of it. I wouldn't even be posting here had I been able to have an SD card with my gnex, which I figured was unnecessary at the time I bought it since I knew the space on their was enough for me already, and the added branding of "Nexus" brand which had me under the impression it was maybe stable enough by itself. Not a mistake I'll make again..
Is it at all possible to get the data off of my phone at this point? At least partially? I believe encryption makes it impossible but I'm rather stubborn. Any help would be greatly appreciated..
owlieowl said:
I'm having the exact same problem. I saw my phone at maybe 10% battery in the AM, said screw it and let it die, woke up this morning and plugged the phone in and nothing. No LED light, black screen, completely unresponsive. I've tried every trick in the book, and the only one that seemed to work marginally even was using a different battery, which got my phone to boot to the encryption screen, but then shut off again. It did that twice, and now both batteries are useless.
I used Legija's program to try and bring some life back to my gnex, even though it's not the international version, just in hopes of getting some of my data back (I have already started the replacement process with Verizon since the phone was insured), but I got no luck there either.
It's extremely disappointing and annoying to me that this phone survived all sorts of ROM installations (I was also using AOKP on 4.1 if someone wants to start making connections), reformatting, tweaking, almost every setting on that phone was modified by me.
Not only that but almost any software or hardware problem I did run into I could solve in maybe an hour, but I let my charge run out and the phone just up and bricks itself? Now, that's just bull****...
Not to hijack the thread, but my interest here is not restoring the phone to working condition but just seeing if I can pull my data off of it. I wouldn't even be posting here had I been able to have an SD card with my gnex, which I figured was unnecessary at the time I bought it since I knew the space on their was enough for me already, and the added branding of "Nexus" brand which had me under the impression it was maybe stable enough by itself. Not a mistake I'll make again..
Is it at all possible to get the data off of my phone at this point? At least partially? I believe encryption makes it impossible but I'm rather stubborn. Any help would be greatly appreciated..
Click to expand...
Click to collapse
So just to be clear... You've been able to get it to boot all the way up to the encryption screen, right? If so you should be able to get into fastboot (Holding down BOTH volume rockers and the power key.) From there you could relock/unlock the bootloader to do a full factory wipe which might solve your boot issue.
As far as the data loss from the wipe, you could then try this: http://forum.xda-developers.com/showthread.php?t=1994705
TomBall718 said:
So just to be clear... You've been able to get it to boot all the way up to the encryption screen, right? If so you should be able to get into fastboot (Holding down BOTH volume rockers and the power key.) From there you could relock/unlock the bootloader to do a full factory wipe which might solve your boot issue.
As far as the data loss from the wipe, you could then try this: http://forum.xda-developers.com/showthread.php?t=1994705
Click to expand...
Click to collapse
I was able to get it to the encryption screen with my old battery that had a little bit of charge left in it twice, but it shut itself down on me both times. So now both batteries are useless.. I took it to the Verizon store hoping they would maybe try one of their batteries, but they just called customer service and told me they're just going to replace it at this point.
I have a feeling the charging mechanism is somehow damaged, because when I did get it to the encryption screen I had it plugged into a wall outlet and it wasn't charging at all. So, I can't turn the phone on whatsoever anymore.. if I could turn it on I could solve this problem... but it simply refuses to boot. The closest I came to interfacing with it was the OMAP Flash script, which did work, but didn't fix the problem.
So maybe if I could get the phone working enough to use ADB with it I could get my data back, but not even that seems possible..
owlieowl said:
I was able to get it to the encryption screen with my old battery that had a little bit of charge left in it twice, but it shut itself down on me both times. So now both batteries are useless.. I took it to the Verizon store hoping they would maybe try one of their batteries, but they just called customer service and told me they're just going to replace it at this point.
I have a feeling the charging mechanism is somehow damaged, because when I did get it to the encryption screen I had it plugged into a wall outlet and it wasn't charging at all. So, I can't turn the phone on whatsoever anymore.. if I could turn it on I could solve this problem... but it simply refuses to boot. The closest I came to interfacing with it was the OMAP Flash script, which did work, but didn't fix the problem.
So maybe if I could get the phone working enough to use ADB with it I could get my data back, but not even that seems possible..
Click to expand...
Click to collapse
If the phone isn't charging then there's something wrong with the USB port. One way to test that would be to use a battery charger. Also, try a different cable. I've had issues with a few different cables that for whatever reason started to not fit properly in the phone.
If you're USB port has gone bad then you'll need to either A) Always use an external battery charger. B) Get a replacement. C) Fix it yourself (Good guide here: http://www.ifixit.com/Guide/Repairi...+LTE)+Micro+USB+Charge+Port+&+Main+Mic/9641/1 )
I'm having a huge problem with my T-Mobile Galaxy S2, and not it won't even completely boot up. The issue had already been around, but never this bad. Usually, when I would use my phone, it would just randomly reboot on it's own. Now, I can't even get to the main home screen or menu. When the battery is inserted, the phone will automatically try to turn on. I'll get the Samsung screen, then the "Samsung Galaxy SII Android 4G T-Mobile screen", then the phone will glitch for a second, black screen, and it'll almost have a seizure from then on. When I say that, pretty much what happens is that the screen will go black, and it'll pulse with vibrations. It'll vibrate, stop for two seconds, vibrate some more, etc. That's all it'll do from there on. It won't try to turn on when I hold the power button, and the vibrations won't stop until I take the battery out. There is no water damage, and there's just normal wear on the phone. I've had the phone since the drop, and for the most part, it's been great until now.
The phone is not rooted, and I have not installed anything crazy. Come to think about it, I didn't really even have too many apps installed on it to begin with. The phone is under warranty, so I had T-Mobile send me a replacement. My main issue now is that I have content on there that wasn't on my SD card, but on the internal hard drive that I find extremely important, and want to keep. When I connect the phone to my computer, nothing comes up because I didn't "connect" it to the computer as you normally would have to do from the phone, before the extra drives pop up on the computer. Without getting into the main menu and manually connecting the phone to the computer so that the drive will pop up, what can I do?
I've tried taking the battery, sim card and memory card out, letting it sit for a few hours, and plug it back in, but it does the same thing. The battery isn't bad, because it plugs into the replacement phone that was sent to me, and works just fine. I've also plugged into my additional batteries, and it does the same thing. I can't do the "hard reset" where you hold volume up & down, then the power button because what happens is the phone will restart itself before I can get to that point. I tried it when I was on the phone with T-Mobile, and the associate at one of the retail locations tried when I went to get a loaner. I've tried hooking up the phone to the Kies software, but it won't recognize the old phone. It will recognize the new one with no problems though.
I am in no way am I well versed with the process of flashing it or installing different things on the phone. I just used it casually for phone calls, texts, web, and an occasional game or app. I'm just stating this so that if there are any specific tips that anyone could recommend, please if possible, explain in a bit more depth, because after I posted my title, I found the related threads, and most of the steps that were recommended to others that had problems sound a bit foreign to me. I just really want to recover the photos and documents that I had on the phone before I send it back to T-Mobile.
These are the threads that I've somewhat referenced so far:
http://forum.xda-developers.com/showthread.php?t=1948094
http://forum.xda-developers.com/showthread.php?t=1457458x
http://forum.xda-developers.com/showthread.php?t=1813866
I can't seem to find anything with the same symptoms as my phone though. If anyone could let me know, that would be great. I just really want to get the content off my old phone, it's just extremely important to me. I'll be waiting on any replies. If you need and more information about what the phone is doing, or what I should try, please mention it. I will try to update this as I get replies, since I am supposed to send the phone back pretty soon. Thank you in advance.
You have a stuck or broken power button. Stick a toothpick or something into the power button whole and take out any gunk if there is. If that doesn't help, then you have a broken power button and you have to get your phone fixed.
Sent from my SGH-T989 using xda premium
So from what I understand your phone does not boot up to the home screen at all and you are trying to recover all the files from the internal storage? I've been in the same situation as you, although, with my previous android (Samsung Captivate) and I know how hectic this situation is...
If you can enter recovery mode still without the phone restarting itself and if you're willing to flash a custom rom that should help you get into the home screen to recover your files, as it shouldn't remove anything from the internal storage (just as long as you don't format the internal storage/system in recovery).
The phone 'seizure' you are experiencing may also be caused by physical damage, such as the internal memory becoming defective (hopefully not the case).
You mentioned that you can't turn on the phone with the power button and the phone only turns on when you place the battery... that's the same thing that happened with my old phone and it turned out that I had to disassemble the phone and clean/replace the power button. After that the phone turned on like normally again, however, I had to flash a new rom for it to properly boot up.
As a last resort, if you can enter 'Download Mode' via button combo or usb jig you can use Odin to flash a stock rom. However, the files you originally have in the phone will be removed, which you definitely do not want. But at least your phone will possibly work again.
At the moment, I don't think there is any way to recover the files you need from the internal memory without being able to boot up the phone to get it connected to your computer. If you do manage to boot to the home screen, but can't connect your phone to your computer. You can always do a wireless transfer to a cloud based storage such as Dropbox (you can use the android app) and just transfer your files from your phone through that.
I hope I am of some help to you, if I find any other solutions I'll let you know. Good luck!
So, unluckily today i find myself here lookin' for help with my phone. I had already took a look on other brick threads, but i can't find an appropriate answer to my problem.
I'm (i was) running lineage-14.1-20170602-nightly, i had ne0zone75's TWRP 3.1.0.0-0, and that's how the brick came in a strange way; i was simply on XDA Labs app browsing the forum, when i received a call. I've answered, and when i shut off the call the phone shut off immediately after. I thought it was a reboot, but keeping pressed the power button didn't switched on the phone anymore. So i've tried to remove the battery and re insert it after some minutes, but the only thing i can get is the screen with the samsung logo that goes all black after 5 seconds. I already had other bricks due some errors of mine in the past, but this time it's really difficult.
1: I can't access recovery mode. Ow, how i wish i could.
2: I can access download mode, but after that i reach the ODIN MODE screen with the details of product binary, KNOX, ecc. the phone shuts off again.
3: If i keep the power button pressed, the phone doesn't starts. It only starts if i replug the battery in, but after some seconds it shuts off again.
4: How could a call as another mess up the whole phone?
5: I didn't installed nothing new from at least a week... yesterday an automatic update of the Play Store took place, but except that nothing has been changed. Nothing of nothing! No settings, no apps...
What could i do? Installing Kies with Samsung drivers could help me flashing a stock rom for example? Because at the moment, there isn't too much that i can do with the phone in this state... I hope this little jewel won't have to become a stone to be thrown away. Any help would be great, and really appreciated. Thanks in advance...
Things has got worse. Now my device doesn't starts at all; no vibrations, no signs of life, nothing. I've tried even to put it for 6 hours in my refrigerator, because i've read that the cold temperature could be helpful to fix some broken contacts on some component, but i'm losing hope 'bout it. I supposed that at this point is something hardware-based and not software, because it's just impossible that a call like an other one could be the cause of this hard brick... The only thing is that if connected to my PC, it is being showed as QHSUSB_LOAD. I'll try some methods that i've seen in other forums, like softwares that tries to fix this, but i think that i'll be forced to buy a new device. Neither an usb-jig could help me to force the download mode if the phone is dead in every aspect... the only thing that i still didn't understood, is if a debrick.img on my SD card (sadly i've read that a microSD class 10 with at least 16 GB is required, and i don't have one) could help somehow on a situation like this one of not. Still no one could advice me with some tip, guys
Edit - feel free to close this thread, I have another phone now