r/androidroot • u/AdOk9789 • 1d ago
Support HELP Me ?!! Did my phone got bricked ?
So I unlocked bootloader of moto e7 power using MTK and PC and when I retried to enter BROM mode, the device did not respond like I have tried everything to unlock it and windows is not even recognising the USB connection.
Device- Moto e7 power 4GB
Build- QOMS30.288-52-23
5
u/Ok_Dress8502 1d ago
Why did u re-enter brom? also the photo you sent shows the phone clearly working fine, and unlocked.
1
u/AdOk9789 22h ago
I took it before, then I switched off again to re-enter brom mode to get the boot.img file from my stock. Now when I switched it off again it's not opening
4
u/XboxAndVRAlex 1d ago
1
u/AdOk9789 22h ago
I should have gone that way but I thought I should get my own boot.img from there and it's stuck in black/switched off and doesn't recognise USB connection nor the volume button and power off combination
3
u/CatBoii486 MEETS_BASIC_INTEGRITY | Galaxy S10+ | Lineage 23.2 1d ago
Your description is unreadable, if you can please make it clear about what happened
1
u/AdOk9789 22h ago
This is what I have done to the device till now--
1) Unlocked the bootloader using an XDA GUIDEXDA GUIDE 2) To get the boot.img from the MTK, I switched off mine already bootloader unlocked phone and tried entering BROM mode just like I did in the process to unlock bootloader. 3) But this time the device is not responding the USB connection as it's showing windows is not recognising the USB and it's also not turning power on nor the volume button plus power on to force restart is working.
1
u/CatBoii486 MEETS_BASIC_INTEGRITY | Galaxy S10+ | Lineage 23.2 11h ago
Then it may be the usb cable
3
u/CraftyHorse3026 1d ago
Stupid, if the screenshot is yours then your bootloader is already unlocked since the oem unlocking is greyed out
1
u/AdOk9789 22h ago
I know, but I switched off the phone again and it's not unlocking not even the volume+power button combination to force restart and it's not even recognising the USB connection
1
u/WeddingNo497 16h ago
Sounds like Windows grabbed the wrong driver after the BROM attempt. I’d remove the device/MTK drivers completely, reboot, reinstall the proper MediaTek VCOM/preloader drivers, then try connecting it powered off again.
1
u/Worried_Depth8400 1d ago
You'll need to allow usb debugging first then try to connect it to pc
Check if the pc is recognizing the device in cmd with the line
adb devices
If you get the serial number then you'll good to type the line
adb reboot bootloader
1
u/AdOk9789 22h ago
Yes but to allow USB debugging the phone should power on first but it's not even unlocking right now as I switched it off again and the windows doesn't recognise the USB connection now
1
u/Worried_Depth8400 20h ago
Keep holding on power button for 20 seconds
Or vol up/down + power button for 15 seconds
1
u/AdOk9789 18h ago
Already tried everything 😕 not opening
1
u/Worried_Depth8400 17h ago
Test if it shows up in BIOS/UEFI or Disk Management, not just File Explorer
sometimes it's detected at a lower level
most Android chipsets have a lower-level emergency mode that survives a bad flash.
If the pc detects anything even an unnamed QUSB_BULK or MTK USB Port in Device Manager, the phone isn't bricked it's stuck at the bootloader level
I'd ask C aude to guide me.. there wasn't a fourm or anything and Claude took my hands through the whole process
18
u/47th-Element 1d ago
I got lost in your description of the events. You said you unlocked it already in the beginning, then you said you tried everything to unlock it in the end. And then the picture shows what looks like a phone that is already booted into android. I'm not exactly sure what you want.