Has there been any news on progress for the moto e4 Sperry and the update date locked issue would like to get this thing with custom rom working
Take it to where purchased and explain it died following a routine OTA update (don't volunteer you unlocked, rooted and attempted to install a custom ROM). Might score a warranty exchange. Otherwise sell it for parts.I feel so stupid
So long story short, I tryed installing a custom rom on my moto e4 xt1768, then went back to a stock rom, after a software update came my phone bricked. It won't even go into fastboot. I thought the battery was dead but I got a new batery and still won't do anything.
Is my phone bricked and is there anything I can do about it. If you need any other info, I am happy to give it to you
Thanks Ace : )
I already tried. I got it from us cellular and they some how figured out that I did that and can't do anything. I am assuming theirs nothing that can be done. One idea I had was buying a logic board on eBay for the moto e4. Would that fix it or notTake it to where purchased and explain it died following a routine OTA update (don't volunteer you unlocked, rooted and attempted to install a custom ROM). Might score a warranty exchange. Otherwise sell it for parts.
You don't really explain anything that allows anyone to help you :I already tried. I got it from us cellular and they some how figured out that I did that and can't do anything. I am assuming theirs nothing that can be done. One idea I had was buying a logic board on eBay for the moto e4. Would that fix it or not
Try to use the boot from sd option too like this guy says helped his xt1766You don't really explain anything that allows anyone to help you :
_was it on stock or not ? that isn't very clear
_which update ?
_before it died had you unlocked the bootloader & enabled adb and authorizd your pc AGAIN if you went from root to stock
_have you even tried the basic of installing official drivers on your pc and plugging it in to see if it charges
_if you plug it into pc and the pc tries to install drivers what does your pc say
Or literally ..the screen is black and the pc doesn't recognize it when you plug it in and it doesn't charge
In your situation there are no quick fixes anyone can give you
Start downloading official Qualcomm drivers (FOR YOUR CHIP )
start downloading official rom
Start dowmloading qfil
Start downloading official moto drivers
Install adb & fastboot
google & read everything you find about
"Test point" "qfil" "driver9008"
_Install QFIL FLASH TOOL
_Take out battery
_hold volume up in all the time
_plug in usb cord
_see if a driver installs
_put battery back in
https://androidmtk.com/use-qualcomm-flash-image-loader-qfil
If you have tried this and the computer recognises phone & install driver then it's obvious you can save your device ..post the outcome here with screenshots and what you did exactly
If that doesn't work you will have to create a "short" on your board using test point method then recover from Qcomm device 9008 driver ..watch video on youtube ..
If you are too lazy buy a new phone :good:
Sorry for not being clear. to answer your questionsYou don't really explain anything that allows anyone to help you :
_was it on stock or not ? that isn't very clear
_which update ?
_before it died had you unlocked the bootloader & enabled adb and authorizd your pc AGAIN if you went from root to stock
_have you even tried the basic of installing official drivers on your pc and plugging it in to see if it charges
_if you plug it into pc and the pc tries to install drivers what does your pc say
Or literally ..the screen is black and the pc doesn't recognize it when you plug it in and it doesn't charge
In your situation there are no quick fixes anyone can give you
Start downloading official Qualcomm drivers (FOR YOUR CHIP )
start downloading official rom
Start dowmloading qfil
Start downloading official moto drivers
Install adb & fastboot
google & read everything you find about
"Test point" "qfil" "driver9008"
_Install QFIL FLASH TOOL
_Take out battery
_hold volume up in all the time
_plug in usb cord
_see if a driver installs
_put battery back in
https://androidmtk.com/use-qualcomm-flash-image-loader-qfil
If you have tried this and the computer recognises phone & install driver then it's obvious you can save your device ..post the outcome here with screenshots and what you did exactly
If that doesn't work you will have to create a "short" on your board using test point method then recover from Qcomm device 9008 driver ..watch video on youtube ..
If you are too lazy buy a new phone :good:
---------- Post added at 08:49 AM ---------- Previous post was at 08:26 AM ----------
Try to use the boot from sd option too like this guy says helped his xt1766
_______XT1766 hardbrick stuck in 9008 mode would normally require a blankflash. However, as is common in most Motorola models there is a boot from SD option that is automatically defaulted to in the case that the bootloader has been deleted or damaged. To use this boot from SD option you simply extract the bootloader to a blank sd card and insert it into the phone then reboot
___Here is a bootloader provided to me (Untested)
mediafire.com/file/t2su47wbd3dizue/XT1766-BOOTLOADER.img/file
Yes ,from the photo your device is recoverable with rdslite or qfilSorry for not being clear. to answer your questions
My phone was on stock
I didn't see what update it was before my device died but I'm almost sure it was the most recent update
The bootloader was unlocked
I followed your instructions
I downloaded the qualcom usb drivers and the qfil tool. I took the battery out. I held volume up and plugged the device into the computer. My computer detected it and qfil showed me this.
https://photos.app.goo.gl/WwJbd9rh1wmhaHjp9
and I have downloaded the stock rom from https://firmware.center/firmware/
I'm not sure what the next step is. But this has me hopeful that it's not lost.
btw thank you sooooo much for your help and sorry for not being clear
(also I tried the sd card method before you replied and that didn't work just so you know)
is there an easy place to get blank flashes or is that hard/impossible to findYes ,from the photo your device is recoverable with rdslite or qfil
You need the "blank flash" file for your device in .mbn format
One day on google ought to do it ..sorry bro ..i am using a Nexus 5 right now and gave my moto e4 ( mtk) to my daughter so i don't have those files on my pc .......so not impossible but might be hard ...try to ask around in dedicated Qcom E4 threads around here ...have you tried with rsdlite and stock roms for Qcom devices floating around ?is there an easy place to get blank flashes or is that hard/impossible to find
Airplane mode indicator is likely a symptom of the underlying problem vs root cause. Mucking with a settings editor will get you nowhere.I've been working to figure this data issue radio off after update and I've came to the conclusion that it is not the radio off but airplane mode on all signs point to that I first noticed after clean flash and going thru the set up that power button menu shows air plain mode on and when you cut it off it just turns Grey not sure if any one knows how to fix I've tryed set editing but no luck any thought would be great still have a reword for a fix thanks
Recalling actions recommended in this post. Effort required to recover a E4 in this state is huge with uncertain outcomes. Has nothing to do with being "lazy" unless you're a hard core geek with no life.is there an easy place to get blank flashes or is that hard/impossible to find
Just connect to pc while twrp is bootedHey peoples. Accidentally i wiped my system. I have a backup in pc. I dont have sd card right now. How can i put the backup wich is in pc back to TWRP backup folder in order to restore ?
I did and had no access to internal memory. Anyway I got a SD card and put the backup in it then restored through Twrp.Just connect to pc while twrp is booted
try a clean install of busybox FROM INSIDE magisk using the download section ..you might have to flash loop around fix first ...I'm using magisk manager showing that BusyBox is not installed correctly I am using the pro version of Root checker root is installed correctly BusyBox binary file was not found in the system