Database Users

[Q] Did I brick my Nexus 4?

Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil

I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?

ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.

Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.

aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).

aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.

You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app

try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688

Okay, thanks guys. I'm on it. Will let you know when I'm done.

That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd

I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?

aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.

chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images

aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.

chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:

Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!

[Q] need help with custom recovery

Hey guys I'm new to android had an iPhone for 6 years. Just got the gs4 two months ago. I rooted the phone took out bloat ware apps using titanium back up. Have a few other rooted apps. Got Interested in ROMs and kernels so did some research looked around on here to how to do it. I downloaded infamouses newest ROM. I have ROM manager and I downloaded cwm recovery through the Rom manager. When I go to back up my current ROM and everything it boots into recovery mode but it isn't cwm recovery. The emblem doesn't come up and I believe its the stock recovery. My question is how can I get the cwm recovery so I can back up my current ROM and then wipe it and install the new one. I'm new so sorry if this is easy or anything I appreciate all the help

Download goo manager and let it install twrp then just flash cwm thru twrp . Or keep twrp and remember to flash loki doki if needed.

Wait!
What firmware is your phone currently on? MDL OR MF3?
If MF3, stop now. Do not flash anything.
Sent from my SGH-I337 using xda premium

Okay I figured out the problems. When I hit reboot and superuser is supposed to grant root permissions an error comes up saying superuser has stopped working then goes into the stock recovery mode. The only thing I found with MDL in it was the baseband version 1337UCUAMDL

Your safe to continue flashing custom recovery on MDL Baseband
Sent from my SGH-I337 using xda app-developers app

Does anyone know how to fix this problem? Its so annoying I have tried goo manager and twsp recovery. And they all do the same thing.

Division4thor said:
Does anyone know how to fix this problem? Its so annoying I have tried goo manager and twsp recovery. And they all do the same thing.
Click to expand...
Click to collapse
Going on the information you have given, if you are doing right and using the correct version for your phone, GooManager and TWRP should be working for you. However, if you go to the development section and look for OUDHS CWM recovery, directions are given in the OP about how to manually install that recovery. Again, directions are in that thread about how to do it. I do hope you are reading all of every post that contains something you are trying to do (in other words, if you use OUDHS, read the entire thread first). Good luck.

scott14719 said:
Going on the information you have given, if you are doing right and using the correct version for your phone, GooManager and TWRP should be working for you. However, if you go to the development section and look for OUDHS CWM recovery, directions are given in the OP about how to manually install that recovery. Again, directions are in that thread about how to do it. I do hope you are reading all of every post that contains something you are trying to do (in other words, if you use OUDHS, read the entire thread first). Good luck.
Click to expand...
Click to collapse
Yeah Idk I'm so over this getting so frustrated. I'm new to this I read that post. Not all 51 pages hope you didn't mean that..

This is the easiest way ever, 1 click, and everything is ready to go....try it...
http://forum.xda-developers.com/showthread.php?t=2297900
Good luck
Thank you

TheAxman said:
This is the easiest way ever, 1 click, and everything is ready to go....try it...
http://forum.xda-developers.com/showthread.php?t=2297900
Good luck
Thank you
Hey thanks for the help. I got twsp recovery through goo manager and worked perfectly. I'm having such a bad experience trying to install this rom. I went into the recovery mode after backing up my current rom and system. I wiped everything out then went into my sd card amd installed the zip that is listed in the infamous page in the developers part. I hit install and then said I'm not rooted and would I like to install superuser. I slide the thing and then went to reboot and now has been stuck saying samsung and custom with an open love under it. Pulled the batter went back into twsp and tried to reboot and still stuck. This is all after I thought I installed the rom already and nothing changed except wiped my phone. Can anyone help
Click to expand...
Click to collapse

Are you installing loki doki after the rom ?

[Q] Problem with TWRP in rooted and unlocked nexus 10

Hello guys, first time posting here, I'm pretty sure it's a silly question, sorry if it is but I couldn't find the answer anywhere. I have an unlocked and rooted device, I installed the last 4.3 update this morning, and usually TWRP let me automatically fix the root just after install the update. But this time it just installed it and booted the tablet, and when I try to enter the recovery mode to fix the root in TWRP, I only see the droid with the exclamation mark.
So the problem is that I don't have root, and I cannot enter TWRP to fix it. TWRP went away with the latest update?. For entering the TWRP I pressed vol+ vol- and power and the pick recovery... is it correct?
Thank you in advance for the great community we have in android and sorry for my english

The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.

3DSammy said:
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
Click to expand...
Click to collapse
Same for me, Starting have some problems as I tried a "reboot to recovery" apk and got it stuck in the bootloader screen and it wasnt going anywhere.. still had TWRP but reflashing things wasnt working..
Used Wug's Nexus Root Toolkit to bring it back to life..

All good
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...

prezeus said:
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
Click to expand...
Click to collapse
Nice that it is solved but please do nog use toolkits anymore. I respect the effort and time people take to make them but learning fastboot is just way better. Maybe harder but hard work pays off. Almost everyone will tell the same.
For people who want to use fastboot:
1. Flash custom recovery via fastboot.
2. Boot into recovery.
3. Flash latest supersu.
You can put solved in the title by edeting it.
Sent from my Galaxy Nexus using XDA Premium HD app

same
Good time . I have a similar problem : after a recent update missing root. I tried to flash a custom recovery by fastboot, but the process hangs at downloading recovery.img to nexus. I tried using other drivers and a different version of fastboot, but to no avail.
Ps: by same drivers and fastboot I got the root before.

[Q&A] [CM12] [Lollerpop] JFLTEATT Nightly Kangs

Q&A for [CM12] [Lollerpop] JFLTEATT Nightly Kangs
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [CM12] [Lollerpop] JFLTEATT Nightly Kangs. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

noremac258 said:
No love for the jfltecan?
Click to expand...
Click to collapse
Yea I tried even using the jflteatt philz to trick it but the data part failed and system was success. So I didn't bother trying to boot. You can still use Antares however, it is unified.
I am wondering if I can flash Antares and then dirty flash this over to get the system part, I just don't wanna have to go through Odin to stock rigamarole.

cm-12-20141124.1217-jflteatt
Can't get it to boot on my AT&T S4. It tries, black screens, then reboots into AD recovery automatically.
I'm unlocked using T-mobile, but I don't think that should matter.
TWRP v2.7.1.0-- Using stock slot with safestrap disabled (no success on making new slots with safestrap enabled, either).

Lollerpop CM12 - AT&T Samsung Galaxy S4 (SGH-i337) - Unauthorized
Hi,
I tried replying to the CM12 Lollerpop thread but even though I have been utilizing XDA for YEARS, I am still considered a noob due to lack of posts.
Anyway, I just wanted to let the awesome developers know that I tried installing CM12 Lollerpop through TWRP, on my AT&T Samsung Galaxy S4 (SGH-i337) that I have installed ROMs on hundreds of times. For some strange reason that I cannot explain, with the Beta version of CM12 right after I power on the device after installing I see an ! and "AT&T UNAUTHORIZED SOFTWARE HAS BEEN DETECTED" and device went to a black screen after 5 -> 10 seconds. Fortunately I was still able to get back into TWRP after a reboot and home + volume up and successfully completed a restore from a 4.4.4 Beanstalk complete backup I took prior to testing CM12 installation / boot, etc.
I would greatly appreciate it if someone could A) explain why this is happening with CM12 and more importantly B) how to get around this annonying blocking message.
Kind Regards,
Jason Vincent
Sr Integration & Validation Engineer
VoIP SME

jkvincent said:
I would greatly appreciate it if someone could A) explain why this is happening with CM12 and more importantly B) how to get around this annonying blocking message.
Click to expand...
Click to collapse
It sounds like you did not flash a Loki-Doki package. Search the AT&T Galaxy S4 forum and you can find it. You need to flash this after you flash your ROM (or anything else) to trick your phone into thinking you have stock software. Some ROMS have this included, which is probably why you have never had to flash this package before, but I would say that most don't. And no, even if the ROM has a Loki package included inside of it, it doesn't hurt to flash it twice so I end up flashing Loki-Doki a lot.
Sent from my GT-I9505G using XDA Free mobile app. Press "Thanks" if I helped!

Unauthorized - Loki & Safestrap
Hi,
I downloaded loki-doki.zip, wiped, installed CM12*.zip, gapps-lp*.zip and applied loki-doki.zip to find the annoying "Unauthorized..." message again. I tried installing loki by itself after a clean reboot. I tried with wiping dalvik + cache and without. Same thing.
After reading up on Loki, I ran into a bit that stated Loki is designed for 4.4.2 and for 4.4.4+ I should be using Safestrap. I downloaded the Safestrap*.apk file, installed it, granted root access and installed Recovery (says Safestrap is built off TWRP).
The first thing I noticed was the TWRP version was still 2.8.1 (I also updated TWRP prior). I went through the same process without Loki. Same "Unauthorized..." message. Tried Loki after. Same message.
I am not sure at this point but I have never had much luck installing Recoveries while being booted into Android. I have always had to install from a .zip in Recovery or use Odin. I'm not convinced Safestrap updated or even if it is the right way to go. What would be really sweet is if the Devs could wrap whatever is needed to get around the "Unauthorized...", into the CM12 installation. Maybe that is asking for too much. I need to still research Safestrap and it is getting late. I do appreciate you pointing out Loki because it got me pointed in the right direction. I kind of forgot about it with the ROMs being Lok'd.
Kind Regards,
Jason Vincent
Sr Integration & Validation Engineer
VoIP SME

For those who are on AT&T, this is how I got 11-30 to work. Worked perfectly, except the battery drain.
Install cm12 using TWRP (shouldn't matter, but I used 2.8.0.1), flash gapps if you want, flash ktoonsez aosp 5.0 kernel just updated few days ago. No loki patch needed. Good luck.
Didn't get a chance to test bluetooth, but camera seemed to work.
I am using a AT&T s4 (no safestrap)

Hi, Try installing a kernel. it work for me. Alicard or ktoonz.

Question here
I have the sgh-i337 rooted on stock firmware 4.2.2 and have installed shabbyPenguin recovery (I know it's an old recovery but it seems to work fine). I am able to flash this ROM like my bootloader is unlocked or do I need to do something else like flash the loki-doki.zip file?
Thanks in advance!

StoneyJSG said:
I have the sgh-i337 rooted on stock firmware 4.2.2 and have installed shabbyPenguin recovery (I know it's an old recovery but it seems to work fine). I am able to flash this ROM like my bootloader is unlocked or do I need to do something else like flash the loki-doki.zip file?
Thanks in advance!
Click to expand...
Click to collapse
I'm not sure what you said in that last line. But I'm guessing you mean to ask if you can flash this or not. Simple answer, no.
Long answer: I'm not sure what your device exactly is, or what you have done with it. I'm guessing it's not an MDL or earlier device to which the loki-doki patch applies. So using that on your device could be bad idea. I'm assuming the recovery you listed is a modified version for safestrap users. In which case, you can only run touch wiz based roms or Google play edition (safestrap), which this is neither of.

thesummoner101 said:
I'm not sure what you said in that last line. But I'm guessing you mean to ask if you can flash this or not. Simple answer, no.
Long answer: I'm not sure what your device exactly is, or what you have done with it. I'm guessing it's not an MDL or earlier device to which the loki-doki patch applies. So using that on your device could be bad idea. I'm assuming the recovery you listed is a modified version for safestrap users. In which case, you can only run touch wiz based roms or Google play edition (safestrap), which this is neither of.
Click to expand...
Click to collapse
Sorry for my typos. I was asking if I can flash this rom like I have an unlocked bootloader since I am on the MDL firmware Android 4.2.2 and can use LOKi. I have ShabbyPenguin's version of Clockwork mod recovery installed.

StoneyJSG said:
Sorry for my typos. I was asking if I can flash this rom like I have an unlocked bootloader since I am on the MDL firmware Android 4.2.2 and can use LOKi. I have ShabbyPenguin's version of Clockwork mod recovery installed.
Click to expand...
Click to collapse
Okay, if you're on MDL, then you have a couple of options. Here's the process that has worked for me without issue. I'm also on MDL. I'm using twrp but prices should be similar. This could also be a good time to update the recovery, it's really easy.
1) download rom to external sd
2) download PA micro 5 gapps
3) download ktoonsez 5.0 att aosp 12-9 kernel
4) factory reset, wipe dalvik/cache
5) install rom
6) install kernel
7) boot then let it settle and reboot into recovery
8) install gapps
9) boot and let it settle
BTW, our bootloader isn't exactly unlocked, it's just hacked/patched/fooled to think it is. It doesn't seem any different than an unlocked one, except that it needs loki patch, patched recovery, or AT&T kernel.
Good luck.

thesummoner101 said:
Okay, if you're on MDL, then you have a couple of options. Here's the process that has worked for me without issue. I'm also on MDL. I'm using twrp but prices should be similar. This could also be a good time to update the recovery, it's really easy.
1) download rom to external sd
2) download PA micro 5 gapps
3) download ktoonsez 5.0 att aosp 12-9 kernel
4) factory reset, wipe dalvik/cache
5) install rom
6) install kernel
7) boot then let it settle and reboot into recovery
8) install gapps
9) boot and let it settle
BTW, our bootloader isn't exactly unlocked, it's just hacked/patched/fooled to think it is. It doesn't seem any different than an unlocked one, except that it needs loki patch, patched recovery, or AT&T kernel.
Good luck.
Click to expand...
Click to collapse
Awesome! Thanks dude. Since I am partial to CWM, I was going to flash PhilZ touch recovery, but from what I have read the ShabbyPenguin recovery is supposed auto loki upon flashing. I also have the loki-doki.zip file for flashing as well just in case.

How do I even flash CM12 on my device?
My SGH-I337 has Lollipop 5.0.1 and it is rooted no custom recovery.
Please help

ahmedbatty said:
How do I even flash CM12 on my device?
My SGH-I337 has Lollipop 5.0.1 and it is rooted no custom recovery.
Please help
Click to expand...
Click to collapse
How you installed custom recovery in S4 i337 at & t?

Jordan Gonzalez said:
How you installed custom recovery in S4 i337 at & t?
Click to expand...
Click to collapse
I found out that I can't flash any custom ROM or recovery if I have the latest bootloader, so it's locked

Help needed. Urgently

I had installed cm 13 and tried installing a new kernel but i guess since i was on a old version it didn't work out. So i proceeded with putting the old kernel back *sandy kernel* however now when the phone opens up i put my pass code it shows the background for a split second with a system ui crashed error and back to lock screen. hence i tried installing a recovery again (twrp hybrid) since the latest roms use that and I wanted a new rom anyway. But i thought id back my stuff up but alas the system ui error doesn't allow me to do so. Finally i ended up by using fastboot to flash the new recovery but even after it said OK ! my phone won't boot into recovery.
So now i am stuck with a OP2 that boots into cm13 but cant get past the lockscreen, a recovery that won't load and a fastboot mode that is the only working thing.
God I really shouldve backed it up i know. But is there a way I can resolve this without losing my data?
I have an exam and the notes are in them.
Help is appreciated !

rogermax said:
I had installed cm 13 and tried installing a new kernel but i guess since i was on a old version it didn't work out. So i proceeded with putting the old kernel back *sandy kernel* however now when the phone opens up i put my pass code it shows the background for a split second with a system ui crashed error and back to lock screen. hence i tried installing a recovery again (twrp hybrid) since the latest roms use that and I wanted a new rom anyway. But i thought id back my stuff up but alas the system ui error doesn't allow me to do so. Finally i ended up by using fastboot to flash the new recovery but even after it said OK ! my phone won't boot into recovery.
So now i am stuck with a OP2 that boots into cm13 but cant get past the lockscreen, a recovery that won't load and a fastboot mode that is the only working thing.
God I really shouldve backed it up i know. But is there a way I can resolve this without losing my data?
I have an exam and the notes are in them.
Help is appreciated !
Click to expand...
Click to collapse
Please use the following Guide. Method 1 should be your answer. https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

toxicore said:
Please use the following Guide. Method 1 should be your answer. https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
sir thats a 1gb file and im on data net right now. I'll download it but are you sure it will resolve my issue ?

Just download latest oxygen or cyanogenmod recovery and flash in fastboot it will sure boot to recovery

paradise220 said:
Just download latest oxygen or cyanogenmod recovery and flash in fastboot it will sure boot to recovery
Click to expand...
Click to collapse
thank you for your help sir, even though i tried flashing all kinds of recoveries via fastboot, it says the flash was successful but it still doesn't boot into recovery. Any other suggestions ?

rogermax said:
thank you for your help sir, even though i tried flashing all kinds of recoveries via fastboot, it says the flash was successful but it still doesn't boot into recovery. Any other suggestions ?
Click to expand...
Click to collapse
As I said. the method i showed you is most certainly the solution. But you need a Computer and yes, 1gb is propably too much for mobile data
Maybe, just maybe if you flash OOS-Firmware it might help. But i dont know for sure.

So i finally managed to get into twrp 2.8.7 (lollipop)by this http://forum.xda-developers.com/devdb/project/dl/?id=16684
thanks a lot for all your hard work guys ! (cant boot into os still but twrp will help atleast)