Related
Bricked OP2 ...
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
If you flashed a ROM that's not for you're phone you're more than likely screwed
Could you try the following:
1, plug the phone back in recovery/fastboot mode
2, Open Computer Management and delete the drivers the OS finds for the phone
3, Download the ADB driver tool from here: http://forum.xda-developers.com/showthread.php?t=2588979
Try follow the steps and let me know if u get the drivers needed for the recovery
If the tool on the above link dont work, try this one: http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Bhups said:
Could you try the following:
1, plug the phone back in recovery/fastboot mode
2, Open Computer Management and delete the drivers the OS finds for the phone
3, Download the ADB driver tool from here: http://forum.xda-developers.com/showthread.php?t=2588979
Try follow the steps and let me know if u get the drivers needed for the recovery
If the tool on the above link dont work, try this one: http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Click to expand...
Click to collapse
Thank you for your response, the issue is that it's hard bricked, so no recovery mode no led , nothing ..
i uninstalled the drivers ( even that i had the adb working before ) and the device is detectable now only with as QHSUSB_BULK
the installation of any adb usb driver don't change anything, only qualcomm usb drivers work ( i have the 9008 only but i'm think it's not compatible with OP2) i could manually change it to adb ( mobistel Cynus f4 ADB interface ) but nothing new..
Help plz
thanks again
mG!X said:
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
Click to expand...
Click to collapse
Two problems here. The first problem is that you didn't wipe properly when flashing Nethunter, that's why you ended up with Nethunter apps on your stock ROM. When flashing a ROM you must perform a full wipe, this consists of system, data, cache, and dalvik cache. This isn't what bricked your phone though. We know what bricked your phone; flashing a ROM for a completely different device. I'm not sure why you would flash a ROM from another device, maybe due to inexperience, but that's the last thing you should be doing, as you now know. Don't use the recovery tool that you have, it isn't for your chipset, it will only make matters worse. I honestly don't think there's any way to revive your device, you've pretty much rendered it useless. I'd strongly suggest you do a lot of research before deciding to mess with another phone, if you don't know what you're doing then don't do it. Venturing into unknown lands like this only ever ends in disaster.
Heisenberg said:
Two problems here. The first problem is that you didn't wipe properly when flashing Nethunter, that's why you ended up with Nethunter apps on your stock ROM. When flashing a ROM you must perform a full wipe, this consists of system, data, cache, and dalvik cache. This isn't what bricked your phone though. We know what bricked your phone; flashing a ROM for a completely different device. I'm not sure why you would flash a ROM from another device, maybe due to inexperience, but that's the last thing you should be doing, as you now know. Don't use the recovery tool that you have, it isn't for your chipset, it will only make matters worse. I honestly don't think there's any way to revive your device, you've pretty much rendered it useless. I'd strongly suggest you do a lot of research before deciding to mess with another phone, if you don't know what you're doing then don't do it. Venturing into unknown lands like this only ever ends in disaster.
Click to expand...
Click to collapse
Thanks for your response.
I made a full wipe with Twrp ( as mentionned in your tutorial ) and al steps run without issues.
The issue is that the next day i used the nethunter install tool instead of manually installing, in the steps for one plus one ( not oneplus 2) i mentionned the specific rom which can run on the phone but suddenly when i pushed next it was flashing stock for nexus ( and yes it's in the steps of oneplus1 :/ i verified ) , well i know that it's inadmissible and can brick it seriously
now i have the bulkusb when linked to windows8 and pressing on poweron+volumeup, what do you recommend please? there is no compatible driver for snapdragon 810?flashing to colorOS won't solve the issue please?
Thanks in advance
mG!X said:
Thanks for your response.
I made a full wipe with Twrp ( as mentionned in your tutorial ) and al steps run without issues.
The issue is that the next day i used the nethunter install tool instead of manually installing, in the steps for one plus one ( not oneplus 2) i mentionned the specific rom which can run on the phone but suddenly when i pushed next it was flashing stock for nexus ( and yes it's in the steps of oneplus1 :/ i verified ) , well i know that it's inadmissible and can brick it seriously
now i have the bulkusb when linked to windows8 and pressing on poweron+volumeup, what do you recommend please? there is no compatible driver for snapdragon 810?flashing to colorOS won't solve the issue please?
Thanks in advance
Click to expand...
Click to collapse
Well flashing ColorOS using the tool you have will attempt to flash ColorOS for the OnePlus One, because that tool is not for your device. As I said, don't use it, it's not for your device so it will only do more harm. I don't know if there's a recovery tool for the Two yet, I certainly haven't seen one.
Heisenberg said:
Well flashing ColorOS using the tool you have will attempt to flash ColorOS for the OnePlus One, because that tool is not for your device. As I said, don't use it, it's not for your device so it will only do more harm. I don't know if there's a recovery tool for the Two yet, I certainly haven't seen one.
Click to expand...
Click to collapse
Ok, i will search maybe the drivers come out or someone find a solution, i ill contact support and seek their help also. Thanks and i will keep you updated if i find something
mG!X said:
Ok, i will search maybe the drivers come out or someone find a solution, i ill contact support and seek their help also. Thanks and i will keep you updated if i find something
Click to expand...
Click to collapse
I just can say, your device is not hard bricked and will be recoverable.
You just need to be a bit patient. For the OPO, there was the ColorOs emergency recovery available (which helped me already 2x unbricking my OPO after I compiled a faulty kernel).
I just have not yet seen something similar for the OP2. But as you get the bulk_device still recognized via USB, this means the Qualcomm emergency boot loader is still intact and once the recovery stuff leaks somewhere, you will be able to fully recover your OP2.
Don't ask me when this will be available, think it also took weeks for the OPO before it was posted somewhere.
All the best!
Andi
mG!X said:
Thank you for your response, the issue is that it's hard bricked, so no recovery mode no led , nothing ..
i uninstalled the drivers ( even that i had the adb working before ) and the device is detectable now only with as QHSUSB_BULK
the installation of any adb usb driver don't change anything, only qualcomm usb drivers work ( i have the 9008 only but i'm think it's not compatible with OP2) i could manually change it to adb ( mobistel Cynus f4 ADB interface ) but nothing new..
Help plz
thanks again
Click to expand...
Click to collapse
You can try this (but with oxygenos), but I'm not sure if it works with OP2 snapdragon 810
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
EDIT: It seems you will need fastboot image of oxygenos and list of partitions ... anyway, good luck
yanick76 said:
You can try this (but with oxygenos), but I'm not sure if it works with OP2 snapdragon 810
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
EDIT: It seems you will need fastboot image of oxygenos and list of partitions ... anyway, good luck
Click to expand...
Click to collapse
It probably isn't the smartest idea in the world to recommend using a recovery tool from for an entirely different device unless you're 100% sure it's safe, which it probably isn't.
Heisenberg said:
It probably isn't the smartest idea in the world to recommend using a recovery tool from for an entirely different device unless you're 100% sure it's safe, which it probably isn't.
Click to expand...
Click to collapse
It's Qualcomm tool, but sadly OP2 is new device and there are no guides specific to OP2. He probably can resurrect his phone using QHSUSB_BULK device(*1)
EDIT: (*1) - It depends on correct driver and firmware files (images)
yanick76 said:
It's Qualcomm tool, but sadly OP2 is new device and there are no guides specific to OP2. He probably can resurrect his phone using QHSUSB_BULK device(*1)
EDIT: (*1) - It depends on correct driver and firmware files (images)
Click to expand...
Click to collapse
Yes, I'm aware that there is nothing specific available for the OP2. My point is that you're not even sure if this isn't going to damage the device further, let alone even help in any way.
Heisenberg said:
Yes, I'm aware that there is nothing specific available for the OP2. My point is that you're not even sure if this isn't going to damage the device further, let alone even help in any way.
Click to expand...
Click to collapse
His device is almost dead and this kind of damage is not covered by warranty. I think in this situation is not much to lose
Just to assure you that the hard brick issue on OPT is completely curable since I've revived two OPTs. No panic needed. I will update the complete procedure as well as the necessary files later today.
yanick76 said:
His device is almost dead and this kind of damage is not covered by warranty. I think in this situation is not much to lose
Click to expand...
Click to collapse
His device is not almost dead, it's in a bricked "like" state right now but it can be easily fixed with the correct tool. What you're suggesting is not the correct tool for this device at all. If you're comfortable with being so reckless with someone else's device, good for you, I'm certainly not.
Heisenberg said:
His device is not almost dead, it's in a bricked "like" state right now but it can be easily fixed with the correct tool. What you're suggesting is not the correct tool for this device at all. If you're comfortable with being so reckless with someone else's device, good for you, I'm certainly not.
Click to expand...
Click to collapse
Yes I understand you but my post was meant as suggestion to way how to fix it, not guide. If you think my post can lead him to kill his device you can delete my post (because I can't), I have no problem with it
yanick76 said:
Yes I understand you but my post was meant as suggestion to way how to fix it, not guide. If you think my post can lead him to kill his device you can delete my post (because I can't), I have no problem with it
Click to expand...
Click to collapse
I know you were trying to help, but that advice is the wrong advice. I don't want/need to delete your post. My point here is to try to help you to understand why giving advice when you're not 100% understanding the situation properly isn't a great idea. On a site like this, accuracy and knowledge are paramount because it can be the difference between helping someone revive their device or completely killing it.
mG!X said:
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
Click to expand...
Click to collapse
Tutorial posted here http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Heisenberg said:
I know you were trying to help, but that advice is the wrong advice. I don't want/need to delete your post. My point here is to try to help you to understand why giving advice when you're not 100% understanding the situation properly isn't a great idea. On a site like this, accuracy and knowledge are paramount because it can be the difference between helping someone revive their device or completely killing it.
Click to expand...
Click to collapse
From this point I agree it was wrong advice.
I hope I never will be in situation like this But if, I will try to fix it based on what I suggest him + hours of google for correct files, correct drivers and correct download tool. I think this "misunderstood" was based on my advice like "here is direction and google for more", this is forum if he can find answer himself (google) he need not to ask for help here
Hi everyone...
I have an awkward issue here with my Nexus 4...
It is in an eternal loop in bootlogo 5.1.1
I already did anything I found in Google search
Flashed ALL firmwares stock, tried some Cyanogenmod and nothing!
I already used simple .bat/.sh in stock folder, used Nexus Toolkit with bricked/bootloop ticked, SkipSoft Tookit and even a tutorial saying to use LGNPST to flash a developer version... this last one worked... but like said in tutorial, the rom is encrypted and the user can do nothing! After that, flashed stock rom and still got stucked in logo!
I did not say, but yes.. I always run ALL wipes
I do not know what else I can do! The phone seems to work normally. I can entry,
download mode, fastboot, recovery but system..
Any ideas?
Thanks for now and sorry about english!
Are you flashing the userdata.img file?
yes and no!
The same result... =/
After flashing userdata.img in fastboot, are you going into recovery using the power and volume buttons to perform a factory wipe?
yes... I already did that too!
Today in the morning, I installed a developer version 4.2 through LGNPST... The phone worked, but it is a old version, I want the last one 5.1.1 and I got the problem that internal memory shows 8GB instead of 16GB...
And I could not resolv this, even reading tutorials from xda forum
If anyone could give me a BIN file of 5.1.1 to use in LGNPST...
no one???
I'm facing the exact same issue, here my post
http://forum.xda-developers.com/nexus-4/help/nexus-4-stuck-animation-android-t3419997
Did u solved it?
No man...
unfortunately I ditched the device!
I've installed Android 4.2.2 and block OTA updates rooting the device, the problem is internally in the device, maybe is a hardware problem, I already made a test of the sensors and none works, for know I'm gonna use it just for phone calls and wapp...
thanks for answer....
Hello, guys! It's now my 2nd post asking the exact same help. I'm very desperate to fix my phone : Asus Zenfone 5.
I have been looking for solutions for a long time, I'm not easily quit on googling. So far, this problem is one that haven't been fixed and very unlikely to be fixed
I have contacted many people including that Taiwan guy who is an expert on Zenfone 5 (forgot the name) and I'm EXTREMELY DESPERATE
I know this problem might be similiar with other case, but this one seems to be rare, because I have not found the solution.
Here is the timeline before my device got soft-bricked :
1. I upgraded to Lolipop with a different version of it's recovery, but still worked.
2. One day, ANR Keeps reporting that SystemUI has stopped. Rebooted and the phone went bootloop.
3. (probably the problem) I flashed wrong version of recovery (I think it was kitkat's recovery) and after then, I'm not able to get into DROIDBOOT.
I have tried several ways :
1. Sending package to my phone over ADB Sideload (It says something like error mounting blabla)
2. Flashing with xFSTK (It says something about driver, and I googled it. Found everyone with the same problem, endless solutions)
3. Downloaded about 1 gig of files (DEBRICK Files) and still, gets stuck somewhere.
So anyone have a solution for me, please?? I'm totally desperate right now, I lost hope. Never had this kind of problem, the thing is that so far, I never had such never-solved case in my life, I will always
find a solution from Google even that would take a long time. I have been searching passively for about 8 months, and I got none of those works
I will be very thankful if anyone would try to help this problem, I will bring detailed information you want, because I don't have solutions left.
Sorry for bad English
Thank You so much!
From what I know (even though I am far from being an expert, just tried and researched a lot), there is no way to fix it.
The bottom line of the problem is that you can't repartition internal storage of zenfone 5 because of x86 architecture, there is no proper Linux partition tools for it. And the oem partitioning via bootloader just fails (gpt command failed).
this type of problem has raised extremely in last month because of some reason.
I just don't understand why but, perhaps, some error in the recent twrp version/s or flash scripts.
My zf5 is a full brick now with no chance for salvation, service can't fix it as well, says impossible to repartition because of the mentioned above.
Hope, I'm wrong
Try @dgadelha "unbrick" package what contain system in .raw format
It will not help. Because any unbrick method involves repartition, which is impossible in this case.
---------- Post added at 09:58 PM ---------- Previous post was at 09:55 PM ----------
But, @kihope12, that would be great if you post a link to that package or thread. Thanks!
Normaly i know link only for zenfone assist, what dont work anymore, so.. just try search on XDA
Well.. I'm done then.. I had so much hope with that phone after recovering it from bootloop.. Now there is no chance to get it back..
Anyway, thanks a lot for letting me know about this, otherwise I would keep looking for something impossible to fix.. And, you seem to know much about this.
Thanks again!!
This is my first post on XDA and i am in desperate need of help. I own a Asus Zenfone 6. Recently i tried unlocking bootloader and installing TWRP recovery so that i can flash a custom ROM. It went horribly wrong and i bricked my device. I managed to unbrick it and revert to Stock ROM which i also upgraded to LOLIPOP using adb sideload. I also managed to root it and have super user access. The problem is that i cannot install a TWRP or any other recovery. When i try to install a custom recovery i get and error " cannot install unsigned image on secure device" which probably suggests that the boot loader is locked. I ran the commands to unlock the boot loader and they ran successfully but i am not sure if the bootloader is locked or unlocked.
I tried running fastboot oem devices but i get an error " Unknown Oem command".
It was after hours of troubleshooting that i decided that i am OK with stock LOLIPOP rom as long as i have a rooted device. It was after sometime that i noticed that the camera wasn't working. Also the flashlight wasn't working. I uninstalled the updates and flashlight was working. However the camera just gives me a black screen for some time after which it quits with an error message " Camera is used by another application. Please reboot your device and try again". I uninstalled the updates for Camera and reverted to a previous version by also removing the camera application using super user access. However for an older version i get an error " Camera not found". I have also tried installing other camera applications but none seem to work even after making them a part of system. Currently flashlight works but only under an older version , as soon as i update it stops working. I decided to lock the boot loader again as it was just not worth it. However after running the commands and locking the bootloader i still cannot get the camera to work. I tried in safe mode and the camera won't work there either.
When i go to recovery i just have four options, there is no install from internal storage or SD card which suggests i am on stock recovery.
Currently i just want my camera to work. I am OK with the stock ROM and recovery as long as i have a rooted device. I have spent hours researching and nothing seems to work. I am in desperate need of help. Some of the friends suggested to try my luck here. I would be indebted as i dont want to purchase another device just because i screwed my camera. Also when i was under kitkat i ran the SIMI test and was getting an error 1667 and 1668 for both cameras. The test is failing under LOLIPOP as well. I dont think its a hardware issue or maybe i am wrong. Any help would be appreciated.
Thanks.
Not even a single reply. DISAPPOINTED!
You need to Lock Bootloader then reflash the rom (wipe all) to fix it. Custom ROMs sometimes cause camera not working cuz there are some devices that have different camera.... Next time, just make sure you Lock Bootloader => Flash Stock recovery => Wipe => Flash Stock ROM
qureshiburhan92 said:
Not even a single reply. DISAPPOINTED!
Click to expand...
Click to collapse
NOT EVEN A REPLY BACK
But yeah that sounds like a roller coaster.
Just picked up the Zenfone 6 to see what I could do with it, I'm going to try to flash the RR rom on here.
Just something I noticed though, I did some research myself, and a couple of sites like this one (https://zenfones.gajetzki.com/) say that you should root your original stock before doing anything. Now this wasn't a requirement at all in my experience for all other phones so I'm a bit skeptical. Anyway I thought that may help in some way.
Good luck!
LGenius3 said:
NOT EVEN A REPLY BACK
But yeah that sounds like a roller coaster.
Just picked up the Zenfone 6 to see what I could do with it, I'm going to try to flash the RR rom on here.
Just something I noticed though, I did some research myself, and a couple of sites like this one say that you should root your original stock before doing anything. Now this wasn't a requirement at all in my experience for all other phones so I'm a bit skeptical. Anyway I thought that may help in some way.
Good luck!
Click to expand...
Click to collapse
Hey buddy.
Thanks for the reply.
I am on stock rom as well as recovery and i have already gone through all these steps. Bootloader is locked as well as far as i can tell but still the camera doesn't seem to work. I am literally out of ideas now. Any help would be great!
Thanks
may zenfone 6 with stock rom 3.24.40.87 can't be unlock,pleas help me
qureshiburhan said:
Hey buddy.
Thanks for the reply.
I am on stock rom as well as recovery and i have already gone through all these steps. Bootloader is locked as well as far as i can tell but still the camera doesn't seem to work. I am literally out of ideas now. Any help would be great!
Thanks
Click to expand...
Click to collapse
Sorry for the late reply, but I'll try to help as much as I can. First things first, I know there are two different models of the Zenfone 6, the A600CG and the A601CG, but apparently this shouldn't make a difference, but it could have in this case, after all they must have different names for a reason. Also, the support for the Zenfone 6 is pretty terrible in terms of custom roms and the such, so you may even be better off with the stock experience, just root it and you'll have all the functionality you could ever dream of.
If you're still keen for the custom roms and stuff maybe check out this thread:
https://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263
Other than that, I guess Google is your friend, but so are we!
I haven't been able to hold onto my Zenfone 6, as it was a friends, so I no longer have it and never got the opportunity to have some fun with it, so I'm just going off my own experience with my HTC One M9, which is probably vastly different, but I suppose the process isn't too different. Nonetheless, I hope all goes well!
Hi Guys can somebody tell me can we install custom rom in fastboot mode without help of twrp recovery if not..then is that any possibilities to make the fastboot custom rom with twrp preflash..for moto g4 plus 1643.
"cutom" ROM, hmm that's interesting name
siddhesh9146 said:
"cutom" ROM, hmm that's interesting name
Click to expand...
Click to collapse
Ya but know one can help here
chouhanprem said:
Hi Guys can somebody tell me can we install custom rom in fastboot mode without help of twrp recovery if not..then is that any possibilities to make the fastboot custom rom with twrp preflash..for moto g4 plus 1643.
Click to expand...
Click to collapse
Can i ask you, why do you want this kind of custom ROM? TWRP flashing works fine, and it is easy to manage everything. Then why ???
____Mdd said:
Can i ask you, why do you want this kind of custom ROM? TWRP flashing works fine, and it is easy to manage everything. Then why ???
Click to expand...
Click to collapse
becz i am unable to go in twrp my moto g4 plus was hard brick and i try all this things given in this thread but after all its still stuck in bootloop in M logo..
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
but still there is no work ..so that i want it..
chouhanprem said:
becz i am unable to go in twrp my moto g4 plus was hard brick and i try all this things given in this thread but after all its still stuck in bootloop in M logo..
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
but still there is no work ..so that i want it..
Click to expand...
Click to collapse
I read it and if i remembered correctly, there was someone else too, whose phone was getting stuck on the same and flashing of nothing worked.
In such case, as echo92 said you there, service center can be better for this.
Here is the same that discussed before: https://forum.xda-developers.com/moto-g4-plus/help/device-unlocked-trusted-key-n-t3656686/page2
____Mdd said:
I read it and if i remembered correctly, there was someone else too, whose phone was getting stuck on the same and flashing of nothing worked.
In such case, as echo92 said you there, service center can be better for this.
Here is the same that discussed before: https://forum.xda-developers.com/moto-g4-plus/help/device-unlocked-trusted-key-n-t3656686/page2
Click to expand...
Click to collapse
Ok may be this is the last option for me.
One thing I can perhaps suggest is that at any point did you change the file system of your device partitions via TWRP? I recall that having cache set as f2fs formatting might cause bootloops. Cache is ext4, system is ext4 and data is f2fs on my device.
If your device is still in the same state as last time, where you flashed the stock ROM and still is bootlooping, I'd suggest take it to a service centre.
Granted, the cost of a new motherboard is expensive (up to 10000 rupees or your regional equivalent, from what I read).
Ask them first to attempt to re-flash the latest stock ROM onto your device. They may have to fully wipe your device. See if they can check the partition formatting of your device.
It sounds like when you hard bricked previously, something other than your bootloader might have been corrupted and not properly repaired, but remotely determining that won't be easy...
Besides, if the Motorola stock ROM fails to boot, what's the chances of a custom ROM, assuming you could flash via fastboot, or working?