Database Users

LG G2 boot loop after editing build.prop What to do?

guys I changed my dpi with this app
https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi&hl=en
textdroider dpi now i am in a boot loop
my phone is rooted but i dont have any custom recovery installed on it.
I took a backup on my sdcard of that build.prop and i guess the app gets one also but is there a way I can change the faulty one?
As I said I only had stock recovery is it possible to adb with that? Or is my only chance is to flash stock rom again
as it is described on this topic http://forum.xda-developers.com/showthread.php?t=2432476
if so which rom should I download I live in Australia and got and Australian stock phone. Should I download d802 Asia?
Thanks for all the help I would really appreciate if I can save it without losing my data but if thats the only way what can I do.

I hope you have a custom ROM or the ROM you have already flashed. Just make a flashable zip with the build.prop placed in /system/ .
flash it through recovery and you are back again..

Or just flash your Rom again. Should fix the issue
Sent from my VS980 4G using XDA Premium 4 mobile app

Guys I am a complete newbie. Can you please explain it more to me.
I am currently downloading the .kdz file via this software
http://forum.xda-developers.com/showthread.php?t=1073827
also i did found this http://forums.whirlpool.net.au/forum-replies.cfm?t=2186883&p=6&#r106
so i am pretty sure I am downloading the right rom right now because the software pickup the same name.
So am I right about flashing my phone by following the steps on the topic I mentioned in my first post?
Is this what you mean by flashing trought recovery because that dude says download mode.
BTW I cant flash trought lg's utility I dont know if its related or not but windows cant install CDC driver.
Also when I flash the rom am I going to lose my data.
Thanks for your answers guys really appericate it.

Just adb the build.prop...
No, download mode it's a form of diagnostic mode, recovery doesn't matter.
You will lose everything. Read and learn, test and perform, only you can make yourself not a noob.

Steamer86 said:
Just adb the build.prop...
No, download mode it's a form of diagnostic mode, recovery doesn't matter.
You will lose everything. Read and learn, test and perform, only you can make yourself not a noob.
Click to expand...
Click to collapse
How can I adb the build.prop ?
I can only go into LG G2 Stock recovery mode and download mode. There is no custom recovery installed so I cant open debugging and adb doesnt recognize the device.
Am i doing something wrong? and believe me I have been reading for hours

I can't explain it much further, your gonna have to search forums. There was a recent thread on this with koushs driver and some lines to force recognize. I don't remember were or what.

Steamer86 said:
I can't explain it much further, your gonna have to search forums. There was a recent thread on this with koushs driver and some lines to force recognize. I don't remember were or what.
Click to expand...
Click to collapse
but even that needs custom recovery I dont have custom recovery unfortunately ((

It does not...

capuagenclik said:
guys I changed my dpi with this app
https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi&hl=en
textdroider dpi now i am in a boot loop
my phone is rooted but i dont have any custom recovery installed on it.
I took a backup on my sdcard of that build.prop and i guess the app gets one also but is there a way I can change the faulty one?
As I said I only had stock recovery is it possible to adb with that? Or is my only chance is to flash stock rom again
as it is described on this topic http://forum.xda-developers.com/showthread.php?t=2432476
if so which rom should I download I live in Australia and got and Australian stock phone. Should I download d802 Asia?
Thanks for all the help I would really appreciate if I can save it without losing my data but if thats the only way what can I do.
Click to expand...
Click to collapse
I bootlooped changing my dpi as well. I was stock rooted with no custom recovery. I followed the instructions here http://forum.xda-developers.com/showthread.php?t=2471370&highlight=unbrick and was able to get my phone to work again. FYI, it may install the latest firmware for your phone, even if it's not OTA yet, and ioroot might not support it yet if it does. I have a d801 and it installed the latest firmware, although it wasn't OTA yet. Hope this helps.

Howie Dub said:
I bootlooped changing my dpi as well. I was stock rooted with no custom recovery. I followed the instructions here http://forum.xda-developers.com/showthread.php?t=2471370&highlight=unbrick and was able to get my phone to work again. FYI, it may install the latest firmware for your phone, even if it's not OTA yet, and ioroot might not support it yet if it does. I have a d801 and it installed the latest firmware, although it wasn't OTA yet. Hope this helps.
Click to expand...
Click to collapse
Ahh mate it would probably helped because my support tool couldnt recognize my device as d802 but instead l02e or l20e sth like that with united driver but I reckon those are the drivers I was looking for unfortunately I dont have the phone anymore.
I turned the phone back to the warranty today not giving any explanation to try my luck. they may just do this same procedure and just flash stock rom on the service and send it back to me or they might just say this is rooted its out of warranty either case I will let them deal with it if they say this is out of warranty I will ask them to fix it and I am willing to pay if they quote me something reasonable if they dont I will try this.
Thank you very much for your answer.

If they say rooted and stuff and outa warranty! Just get it back home.. I will help you via teamviewer!

Jishnu Sur™ said:
If they say rooted and stuff and outa warranty! Just get it back home.. I will help you via teamviewer!
Click to expand...
Click to collapse
Thank you heaps man how nice of you. I would let you guys know how it goes. Its only soft bricked so i think technical support would be able to flash the stock firmware on it but I hope they wont decide to give me hard time. If they do i am planning to play the fool
I will definitely pm you if I get it back unfixed. Thank you for the offer.

Jishnu Sur™ said:
If they say rooted and stuff and outa warranty! Just get it back home.. I will help you via teamviewer!
Click to expand...
Click to collapse
Hello i think my lg g2 is bootlooping will you be able to help through teamviewer plz thanks a lot

pilo99 said:
Hello i think my lg g2 is bootlooping will you be able to help through teamviewer plz thanks a lot
Click to expand...
Click to collapse
Please tell me how it happend??
Sent from my GT-N7000 using xda app-developers app

Jishnu Sur™ said:
Please tell me how it happend??
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
was playing with dpi density and it start doing the bootloop , i try to get back to stock through the lg flash utiliy and it did but no system setting and it keep turning on and off i can get to download mode ,,,,but the recovery it just show the green android man and then boot staright to the home screen

pilo99 said:
was playing with dpi density and it start doing the bootloop , i try to get back to stock through the lg flash utiliy and it did but no system setting and it keep turning on and off i can get to download mode ,,,,but the recovery it just show the green android man and then boot staright to the home screen
Click to expand...
Click to collapse
Check PM!

Jishnu Sur™ said:
Check PM!
Click to expand...
Click to collapse
cool am online now

Guys I just wanted to give you update on the matter. Today I called the repair centre and they told me they have fixed the phone and send it back yesterday so I should be able to get it in couple of days maybe this friday or next week monday something like that. They didnt say anything about root or warranty or stuff like that. When I get the phone back what can I do prevent this from happening again? Do I need to flash a custom recovery on the phone? What is the risk of doing that? Or should I just root the phone and not mess with the system files ever again
Thanks heaps for all your inputs.

Got the phone today they changed the motherboard. I am not sure if it is a good thing or a bad thing :/ On the good side it is fixed for good on the flipside the phone has been opened now so thats not so good. I have checked the body coudlnt find too many stracthes or sth like that they did a clean job but still.
Anyway that was the last update.

D802 bricked?

Hey guys, i dont know if its bricked or not, but i have download mode and recovery, i am on stock, but ... my modem is unknown, and after several kdz upgrade stills so .. could it be that my partitions are wrong? i rooted and changed recovery, and my recovery is not properly functional ... sometimes looking via explorer I see the "0" folders but should they dont be removed by turning back to stock via lg support tool?
Thanks for help!
Greetings

vyrus973 said:
Hey guys, i dont know if its bricked or not, but i have download mode and recovery, i am on stock, but ... my modem is unknown, and after several kdz upgrade stills so .. could it be that my partitions are wrong? i rooted and changed recovery, and my recovery is not properly functional ... sometimes looking via explorer I see the "0" folders but should they dont be removed by turning back to stock via lg support tool?
Thanks for help!
Greetings
Click to expand...
Click to collapse
now it works, damn wtf asigjkalö but what have i to do now? Root does not work so i cant do a full recovery

vyrus973 said:
now it works, damn wtf asigjkalö but what have i to do now? Root does not work so i cant do a full recovery
Click to expand...
Click to collapse
still totally buggy .. any ideas please? How much would it cost to reset the chip at a LG centre? g
ty

@vyrus973 dont use lg flashtool now, read the go back to stock guide and flash your phone with .tot or kdz again, root the phone, install recovery and if your modem is still unknownnyou flash it from this forum.

wulsic said:
@vyrus973 dont use lg flashtool now, read the go back to stock guide and flash your phone with .tot or kdz again, root the phone, install recovery and if your modem is still unknownnyou flash it from this forum.
Click to expand...
Click to collapse
flashed with kdz to 4.2.2, rooted, flashed recovery, flashed baseband, still buggy ... now i did the same and toggled the ROOTED status from download mode and i upgrade to the latest, so maybe I can say to LG centre that after ota bricked, its in warranty, or should i do something else?
greets

@vyrus973 so whats now buggy then? The 0 folder is actually not a big deal, I had it also from custom roms. Is the modem still unknown? Could your efs partition maybe bad?
If its really an hardware issue non fixable then I would send it to LG if its not your fault. But if its an easy to fix software issue then I would try to fix it myself.
Could you explain more about your issue.

wulsic said:
@vyrus973 so whats now buggy then? The 0 folder is actually not a big deal, I had it also from custom roms. Is the modem still unknown? Could your efs partition maybe bad?
If its really an hardware issue non fixable then I would send it to LG if its not your fault. But if its an easy to fix software issue then I would try to fix it myself.
Could you explain more about your issue.
Click to expand...
Click to collapse
i just played on my efs backup 1 week ago, but did anything, is there any other method to fix it?
greets

wulsic said:
@vyrus973 so whats now buggy then? The 0 folder is actually not a big deal, I had it also from custom roms. Is the modem still unknown? Could your efs partition maybe bad?
If its really an hardware issue non fixable then I would send it to LG if its not your fault. But if its an easy to fix software issue then I would try to fix it myself.
Could you explain more about your issue.
Click to expand...
Click to collapse
i just played on my efs backup 1 week ago, but did anything, is there any other method to fix it?
the bug is that he dont start the service, he does not even try to read my sim card, still no connection, and he self restarts like a loop, so i cant even use it really long time, sometimes he gets connection but even than with really bad signal, when i put on fly mode and return back he does not connect more, even the data connectivity than does not work, since i flashed the optimus v3 rom, i tried each kdz for my phone but no one did really fix it, sometimes at the first runtime it function and than after restart still buggy aaaaa its make me crazy, actually i am using a 6inches big china phone and that cant be a permanent solution.
greets

@vyrus973 so you still have the backup? If so then you can try to restore it. You can also google about g2 efs recovery to restore it but I am not sure if it is possible. I think that your efs partition is corrupted or got removed.

wulsic said:
@vyrus973 so you still have the backup? If so then you can try to restore it. You can also google about g2 efs recovery to restore it but I am not sure if it is possible. I think that your efs partition is corrupted or got removed.
Click to expand...
Click to collapse
i restored it many times, i backuped it on 4.2.2 and on 4.4.2 but anyone does properly function, i went in the assistent center and they are going to sent it to labor, at the end i restored all, i hope that they cant see that i played with the root/bootloader, in download mode is written UNROOTED, hopes thats all ahah, in 7 days I update
greets

@vyrus973 ahh okay, if you flashed back to stock and removed root temper flag then you should be okay. If you live in europe then it didnt matter that you had rooted your phone I thought. But your download mode said unrooted so the temper flag got resetted.
Goodluck with your phone and have fun with it, dont brick it

wulsic said:
@vyrus973 ahh okay, if you flashed back to stock and removed root temper flag then you should be okay. If you live in europe then it didnt matter that you had rooted your phone I thought. But your download mode said unrooted so the temper flag got resetted.
Goodluck with your phone and have fun with it, dont brick it
Click to expand...
Click to collapse
ahahah i were not happy with the g2, nice design but mhhh don´t know ... i think after i´ll sell it, and yes i live in italy so ehehe *finger crossing* hope it will go all right ahah at the end i dont think they have to repair hardware, just plug it in their universal computer and flash all again, at the worst case they have to open it and flash on board yey

[Q] Why I bricked my phone with LG Flash tool?

I have LG G2 D802 32GB. When I bought it, there was Android 4.4.2 KitKat installed.
Then I rooted it using ioroot25 and installed custom recovery using AutoRec.
I flashed CloudyG3 v1.2 rom by @Cloudyfa using TWRP.
It was working really good except the VOIP calls, thus I wanted to revert back to stock.
I found this guide: http://forum.xda-developers.com/showthread.php?t=2432476
I tried to flash it using some Europe Open KDZ from this page: http://storagecow.eu/index.php?dir=Xda%2FLG+G2%2FStock%2F
The flashing started and stucked at I think 4%. I rebooted the phone and it appeared as qhsusb_dload.
I can't remember if I clicked on Normal or CFE flash. But I think it was normal.
I tried to unbrick it with this guide: http://forum.xda-developers.com/showthread.php?t=2582142
After that I got only LG logo and no recovery, no fastboot, no download mode, no qhsusb_dload mode, no nothing.
Now I got board replacement. The board have rooted Android 4.2.2 Jelly Bean installed.
As I want to have CloudyG3 installed. I tried to do that by installing custom recovery and then flashing the CloudyG3 rom and KitKat baseband. But I think I have a battery drain issue, as Cludyfa already said. I also tried with flashing the Cust and Persist partitions from the KitKat KDZ, but my battery didn't got any better.
The question is, why I bricked my phone with LG flash tool? What should I do to make sure that this won't happen again?
I made backup of entire phone nand (mmcblk0). Should I DD it if I get the bulk mode (qhsusb_dload) again?
Thank you in advance for your answers.

@mss1988 if the phone is stuck at 4% just let it still for some time cause the program could might be bugged or some other error, just leave the phone on dont restart it cause the phone has first removed the stuff and didnt copied the bootloader etc yet.
If you get qhsusb_dload mode then I suggest to use the unbrick guide and also Pick the right files for your phone. You can DD your backup to your phone but using the unbrick guide seems safer to me.
Also check when you can use that qhsusb dload that all files are copied good.
Tip to prevent brick after root and custom recovery: Flash an stock rom through recovery or an stock rom which got modified under the hood.

wulsic said:
@mss1988 if the phone is stuck at 4% just let it still for some time cause the program could might be bugged or some other error, just leave the phone on dont restart it cause the phone has first removed the stuff and didnt copied the bootloader etc yet.
If you get qhsusb_dload mode then I suggest to use the unbrick guide and also Pick the right files for your phone. You can DD your backup to your phone but using the unbrick guide seems safer to me.
Also check when you can use that qhsusb dload that all files are copied good.
Tip to prevent brick after root and custom recovery: Flash an stock rom through recovery or an stock rom which got modified under the hood.
Click to expand...
Click to collapse
When phone stucked there was also some message box on LG Flash Tool. Something like that: ?????? ??? ????????.
Sent from my LG-D802 using XDA Free mobile app

Broken usb cable or port? Problems on pc?

siggey said:
Broken usb cable or port? Problems on pc?
Click to expand...
Click to collapse
As far as I know none of that.
Sent from my LG-D802 using XDA Free mobile app

That something like ????? Was probably in some asian language which your pc couldnt read. Some pc's makes boxes from it some ?. I cant tell you what that ???? Means since they have no meaning without any real symbols from some language of asia (I dont know where the dev comes from)
If it was stuck at 4% you could ask it on the thread of the lg flashtool since the dev of it and or other users may know the problem.

mss1988 said:
What should I do to make sure that this won't happen again?
Click to expand...
Click to collapse
Read the tutorial in detail & HAVE some patience man.

We now have LOLLIPOP for F400K!! Yayyy! Download link in thread

Here, guys. Linking to a thread from a Chinese forum.
And it's not a troll thread! I decided to be brave and flash it! Yayyy! I now have Lollipop on my G3 F400K version but WiFi doesn't turn on as of now. And no root.
Shall use it for the better part of the day and post here.
http://www.cnanzhi.com/romdetail/4919

I cannot understand how to use that... can u help me?

It's pretty straightforward.. Download the three files in the link provided above and flash them from your custom recovery.
Use Google translate for every link.
I've got this on my phone since the last 5 hours and I haven't used it much for bug testing. But the phone works perfectly and the software is a daily driver for sure!

Did you flash modem? Is WiFi working well?

Didn't flash any extra modem. Wifi not turning on. See the first post.
That's only bug I see as of now.

I think modem can help that problem... I ll try. I hope this file won't wreck my recovery partition as 19c did...
And sorry for my bad English

DokdoIsKoreanTerritory said:
I think modem can help that problem... I ll try. I hope this file won't wreck my recovery partition as 19c did...
And sorry for my bad English
Click to expand...
Click to collapse
you will see the modem and mods in the info translate it theirs a link there for modems ,patches and mods sorry for my bad english ehehe

is it really for F400K ? I dont think that, it look like a ported from D855
I also saw a ported package from F400S at http://www.fshare.vn/file/1CMRFVXM4A/ (I flashed and it worked - 1 week ago - I back to stock 4.4.2 to wait for OTA)

where did you get that link can u share the forums?

i lost root. And now I can't flash a new ROM. Any heads up?

frankmehta said:
i lost root. And now I can't flash a new ROM. Any heads up?
Click to expand...
Click to collapse
I think you're screwed since you're running the new bootloader (or kernel, not sure) you can't downgrade, and since there isn't lollipop for f400k you need to wait

frankmehta said:
i lost root. And now I can't flash a new ROM. Any heads up?
Click to expand...
Click to collapse
Have you tried a "adb reboot recovery"? My f400k on cloudy won't enter bump recovery with any of the usual start up sequences I have found. The only way I can do it is with reboot to recovery on the restart menu or "adb reboot recovery" maybe yours is the same?

Mine boots into stock recovery.
I don't even have root.
Kdz method doesn't work because Flash toll recognizes the phone has a d855.
Flashing a d855 dll is suicide.

frankmehta said:
Mine boots into stock recovery.
I don't even have root.
Kdz method doesn't work because Flash toll recognizes the phone has a d855.
Flashing a d855 dll is suicide.
Click to expand...
Click to collapse
Have you had a look at the return to stock guide? http://forum.xda-developers.com/showthread.php?t=2785089
I haven't done it from Lollypop nor do I know much about this kind of thing so make sure you do some research first.

daveaus said:
Have you tried a "adb reboot recovery"? My f400k on cloudy won't enter bump recovery with any of the usual start up sequences I have found. The only way I can do it is with reboot to recovery on the restart menu or "adb reboot recovery" maybe yours is the same?
Click to expand...
Click to collapse
Heyy mine is like yours, I can't enter recovery when on boot. But can enter with a app or menu (tweakbox).
How do I fix this? I am afraid of bootloops and want to get into recovery when I get one.

KingOfDope said:
Heyy mine is like yours, I can't enter recovery when on boot. But can enter with a app or menu (tweakbox).
How do I fix this? I am afraid of bootloops and want to get into recovery when I get one.
Click to expand...
Click to collapse
Please let me know if you find out.
I asked the super helpful guys in the bump IRC chat room but no luck. I am going to be super careful about what I flash until a method is found.

HardBrick By Flashing Recovery Only !!! Showed QHSUSB_Bulk Help Please

hi
i just flash the Android N Preview it worked normaly then i flash TWRP through Temporary Recovery then i reboot and BAM . Nothing there.
Black display , no bootloader,nothing
just when pluging the device it showed qhsusb_Bulk Driver on Windows
Any Help ?
and if i send it back to google does it cover the Warranty?

Google probably won't do anything for you as you installed it at your own risk

mustafa alzubaidy said:
hi
i just flash the Android N Preview it worked normaly then i flash TWRP through Temporary Recovery then i reboot and BAM . Nothing there.
Black display , no bootloader,nothing
just when pluging the device it showed qhsusb_Bulk Driver on Windows
Any Help ?
and if i send it back to google does it cover the Warranty?
Click to expand...
Click to collapse
No it won't be covered by warranty. What do you mean you flashed TWRP through temporary recovery? Exactly what TWRP did you flash? The filename please.

Good news: your phone is not dead. I've had this issue once with my OnePlus One and I was able to get if fixed.
Bad news: process was a little bit harder than standard flashing, unlocking, etc. stuffs.

Heisenberg said:
No it won't be covered by warranty. What do you mean you flashed TWRP through temporary recovery? Exactly what TWRP did you flash? The filename please.
Click to expand...
Click to collapse
i use the NRT toolKit to flash TWRP (it provide temporary Recovery to flash any zip then it goes back to stock , i did this earlier its not the cause) it boot the recovery and i flashed this file :
twrp-3.0.0.0-s2vep-20160208 (then i realized it is the wrong file in the wrong folder)
after that i reboot the device and got bricked.

anmar21 said:
Good news: your phone is not dead. I've had this issue once with my OnePlus One and I was able to get if fixed.
Bad news: process was a little bit harder than standard flashing, unlocking, etc. stuffs.
Click to expand...
Click to collapse
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)

mustafa alzubaidy said:
i use the NRT toolKit to flash TWRP (it provide temporary Recovery to flash any zip then it goes back to stock , i did this earlier its not the cause) it boot the recovery and i flashed this file :
twrp-3.0.0.0-s2vep-20160208 (then i realized it is the wrong file in the wrong folder)
after that i reboot the device and got bricked.
Click to expand...
Click to collapse
Yeah, wrong recovery, big mistake.
mustafa alzubaidy said:
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)
Click to expand...
Click to collapse
You need special Qualcomm tools to recover, I haven't seen such a tool for this device yet though.

Heisenberg said:
Yeah, wrong recovery, big mistake.
You need special Qualcomm tools to recover, I haven't seen such a tool for this device yet though.
Click to expand...
Click to collapse
i search the net i found that for lG G2 , LG G3
any idea
how much time should i wait if such a tool appears?
thanks for you help

mustafa alzubaidy said:
i search the net i found that for lG G2 , LG G3
any idea
how much time should i wait if such a tool appears?
thanks for you help
Click to expand...
Click to collapse
It's impossible to say if or when it might become available.

@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )

sjandroiddeveloper said:
@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )
Click to expand...
Click to collapse
It corrupts the partition table which affects the other partitions.

mustafa alzubaidy said:
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)
Click to expand...
Click to collapse
For my OPO I used a tool and as @Heinsenberg mentioned I've never seen such a tool for the 6P yet. RMA would be the best solution, just say your not able to turn your phone on (which is true) .

sjandroiddeveloper said:
@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )
Click to expand...
Click to collapse
me too!
i have flashed many rom with many devices , i even flashed a rom by enterning a download rom on a black screen and it worked!
but flashing wrong recovery i dont think it will cause such brick
FYI when i connect it to the PC it is recognized and when i contiously press the power buttuon it re-connected to the pc

If he really sends the device in and Google finds out HOW exactly the phone died, he might face severe consequences. It´s dishonest after all.
If you flash the wrong recovery for a different device, it´s your own bad luck. Now here´s the deal, you can still repair the device if a) Huawei would fix it or b) find a phone shop which could replace the motherboard. Once the Bootloader is bricked, there´s barely anything a regular user could do except for some complicated methods which require the knowledge and the special tools which most people don´t have.
anmar21 said:
For my OPO I used a tool and as @Heinsenberg mentioned I've never seen such a tool for the 6P yet. RMA would be the best solution, just say your not able to turn your phone on (which is true) .
Click to expand...
Click to collapse

mustafa alzubaidy said:
me too!
i have flashed many rom with many devices , i even flashed a rom by enterning a download rom on a black screen and it worked!
but flashing wrong recovery i dont think it will cause such brick
FYI when i connect it to the PC it is recognized and when i contiously press the power buttuon it re-connected to the pc
Click to expand...
Click to collapse
Flashing the wrong recovery can and does cause such a brick, this is what you're experiencing. I've seen it happen on many devices, it borks the partition table.

mustafa alzubaidy said:
but flashing wrong recovery i dont think it will cause such brick
Click to expand...
Click to collapse
You can tell yourself this all day long, but the phone that is in your hands that is now a doorstop, is proof otherwise.
Very crappy situation, but this is why toolkits stink, and why you need to be VERY careful when you mess w the device.