Related
AT&T Nexus 6, not rooted, bootloader unlocked.
I flashed the latest Android build LMY47i . Everything seemed to go fine. When the phone booted the first time i got an error "Unfortunately NFC service has stopped." click OK then get "Unfortunately phone has stopped." click ok, rinse and repeat. I cannot get past that error in the setup. eventually It just keeps re-booting.
I booted to recovery and cleared cache. Same issue.
Factory reset from recovery. Same issue.
Booted to safemode. same issue.
USB debugging is not turned on so I cannot get my computer to talk to the phone via USB.
any help much appreciated!
Berk
Berk8520 said:
AT&T Nexus 6, not rooted, bootloader unlocked.
I flashed the latest Android build LMY47i . Everything seemed to go fine. When the phone booted the first time i got an error "Unfortunately NFC service has stopped." click OK then get "Unfortunately phone has stopped." click ok, rinse and repeat. I cannot get past that error in the setup. eventually It just keeps re-booting.
I booted to recovery and cleared cache. Same issue.
Factory reset from recovery. Same issue.
Booted to safemode. same issue.
USB debugging is not turned on so I cannot get my computer to talk to the phone via USB.
any help much appreciated!
Berk
Click to expand...
Click to collapse
Boot to bootloader. Use fastboot. fastboot format userdata and fastboot format cache.
Evolution_Freak said:
Boot to bootloader. Use fastboot. fastboot format userdata and fastboot format cache.
Click to expand...
Click to collapse
I am at the bootloader but when I send fastboot commands from the console (windows7) i get "waiting for device"? USB debugging is not turned on becuase I cannot get to the menu.
Berk8520 said:
I am at the bootloader but when I send fastboot commands from the console (windows7) i get "waiting for device"? USB debugging is not turned on becuase I cannot get to the menu.
Click to expand...
Click to collapse
What happens when you type fastboot devices?
Evolution_Freak said:
What happens when you type fastboot devices?
Click to expand...
Click to collapse
no devices are listed.
Berk8520 said:
no devices are listed.
Click to expand...
Click to collapse
rebooted computer. No fastboot sees the device. Going to try a cleaning the cache and user data now.
Berk8520 said:
no devices are listed.
Click to expand...
Click to collapse
You shouldn't need USB debugging from bootloader for fastboot to work. Try installing ADB and fastboot system wide with this:
http://forum.xda-developers.com/showthread.php?t=2588979
That seemed to work. I am now trying to flash the image again. The bootloader and radio go fine.
When I flash the sytem image I get the following error
(bootloader) Permission Denied
Failed (remote failure)
Berk8520 said:
That seemed to work. I am now trying to flash the image again. The bootloader and radio go fine.
When I flash the sytem image I get the following error
(bootloader) Permission Denied
Failed (remote failure)
Click to expand...
Click to collapse
Did you reboot to bootloader after flashing bootloader and radio?
Evolution_Freak said:
Did you reboot to bootloader after flashing bootloader and radio?
Click to expand...
Click to collapse
Yes I sent "fastboot reboot-bootloader" after loading bootloader and the radio.
Berk8520 said:
Yes I sent "fastboot reboot-bootloader" after loading bootloader and the radio.
Click to expand...
Click to collapse
Just try fastboot format cache and fastboot format userdata and try to reboot to system.
Still getting the same error and boot loop after clearing the cache and user data.
Berk8520 said:
Still getting the same error and boot loop after clearing the cache and user data.
Click to expand...
Click to collapse
You sure your bootloader is unlocked? Another silly question, you are trying to flash the images individually, right? Not using flash all?
device is UNLOCKED. Status code: 3
Still stuck in the same bootloop
Berk8520 said:
device is UNLOCKED. Status code: 3
Still stuck in the same bootloop
Click to expand...
Click to collapse
Flash TWRP recovery. Wipe and format in TWRP. Download and flash ROM.
locked the bootlaoder and rebooted. Now I have the android icon with the spinning belly.
Berk8520 said:
locked the bootlaoder and rebooted. Now I have the android icon with the spinning belly.
Click to expand...
Click to collapse
Please tell me you did NOT lock the bootloader.
@rootSU @simms22
now when i try to unlock I get failed error
(Bootloader) (remote failure) Check 'allow OEM unlock' in developer options
failed (remote failure)
Berk8520 said:
now when i try to unlock I get failed error
(Bootloader) (remote failure) Check 'allow OEM unlock' in developer options
failed (remote failure)
Click to expand...
Click to collapse
evidently that was a mistake
Berk8520 said:
now when i try to unlock I get failed error
(Bootloader) (remote failure) Check 'allow OEM unlock' in developer options
failed (remote failure)
Click to expand...
Click to collapse
Yes, you may have just bricked yourself.
You can now try this:
http://forum.xda-developers.com/showpost.php?p=60591217&postcount=266
@cam30era
---------- Post added at 07:17 PM ---------- Previous post was at 07:14 PM ----------
You absolutely should NOT have locked your bootloader. Worst thing to do.
Hi!
I'm trying to install TWRP on my P10. I've unlocked bootloader on Huawei website.
Whenever I'm typing in fastboot "flash recovery twrp.img" it goes through and everything says OK
But when i try to "fastboot boot twrp.img" I get FAILED (remote: command not allowed)
"fastboot oem device-info" gives me the same error too and "fastboot oem unlock" gives me already fastboot unlocked
What do you thing "fastboot boot twrp.img" should do? This command isn't allowed because it does not exist.
If you want to boot into your flashed TWRP recovery, you have to enter "fastboot reboot" and press volume up while booting - the USB cable has to be disconnected.
Instead of "fastboot oem device-info" try "fastboot Gevtvar unlocked".
or use adb when the phone is running.
"adb reboot recovery"
you can't go direct from fastboot to recovery simply by a command
Yeah, the command was wrong, sorry xD
Anyway I thinks it's fixed now and I'm able to boot manually to recovery from phone now!
jejeje i was coming here to tell you about wrong command
I have the same problem with FAILED (remote: command not allowed). When I try to install or flash anything I see the info about FAILED (remote: command not allowed). I have FRP locked and I can't enable OEM developing option (it is inactive). I can't relock bootloader, can't instal TWRP, I have only simply erocevery where I can't wipe - only reboot and shutdown device.
I tried do update via dload, hwota - all with defeat
In ADB and Fastboot I can see my device connected.
Does anyone have any idea?
do you have instaled driver for P10, does computer recognice device like P10 ?
DiMeteo24 said:
I have the same problem with FAILED (remote: command not allowed). When I try to install or flash anything I see the info about FAILED (remote: command not allowed). I have FRP locked and I can't enable OEM developing option (it is inactive). I can't relock bootloader, can't instal TWRP, I have only simply erocevery where I can't wipe - only reboot and shutdown device.
I tried do update via dload, hwota - all with defeat
In ADB and Fastboot I can see my device connected.
Does anyone have any idea?
Click to expand...
Click to collapse
Any news? My p10+ it's in the same case
same problem im already unlock but the twr not install what is propper command
Hey guys, for all of you with "command not allowed" problem, you have to check OEM unlock setting on developer options but if you have a greyed out button, you need to flash again your stock room with a tool like dc-phoenix unlocker and bypass frp lock (on YouTube you will find tons of videos regarding this matter). Also, you can check if your Fastboot is protected (frp locked) on Fastboot screen...
There you go---> https://forum.xda-developers.com/hu...ution-bl-unlockedfrp-locked-fastboot-t3684302
PS READ the post to the END!! don't make mistakes it's really easy and fast. It works!
Hi guys.
I know this thread is pretty old but I'm getting the exact same problem as the OP except on my P20 Pro: I can flash a recovery but not boot one from fastboot.
The biggest difference is that my bootloader is unlocked and I have FRP Unlock, so according to every post I've seen it SHOULD be working.
My fastboot log:
PS C:\adb> fastboot devices
LCL0218415002142 fastboot
PS C:\adb> fastboot boot twrp-3.2.1-0-charlotte.img
downloading 'boot.img'...
OKAY [ 0.187s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.187s
Armand Bernard said:
Hi guys.
I know this thread is pretty old but I'm getting the exact same problem as the OP except on my P20 Pro: I can flash a recovery but not boot one from fastboot.
The biggest difference is that my bootloader is unlocked and I have FRP Unlock, so according to every post I've seen it SHOULD be working.
My fastboot log:
PS C:\adb> fastboot devices
LCL0218415002142 fastboot
PS C:\adb> fastboot boot twrp-3.2.1-0-charlotte.img
downloading 'boot.img'...
OKAY [ 0.187s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.187s
Click to expand...
Click to collapse
Have you try this command fasboot reboot recovery_ramdisk?
I get:
PS C:\adb> fastboot reboot recovery_ramdisk
fastboot: usage: unknown reboot target recovery_ramdisk
with "fastboot boot recovery_ramdisk" I get
error: cannot load 'recovery_ramdisk': No such file or directory
I sorted out my problem from a different angle so I no longer need to boot to TWRP from fastboot. Thanks for your help!
Question
Armand Bernard said:
I sorted out my problem from a different angle so I no longer need to boot to TWRP from fastboot. Thanks for your help!
Click to expand...
Click to collapse
Could you please tell me how did u solve this problem. thx
darkdante13 said:
Could you please tell me how did u solve this problem. thx
Click to expand...
Click to collapse
This was quite some time back so I don't remember all that well, but I think I just used the built in Huawei recovery, erecovery, to restore my whole phone and then I was able to reinstall my custom recovery and boot to it normally. I can't guarantee this as I don't remember the whole context of this. Using erecovery I didn't lose my locally stored files, only my apps and app data. Hope this helps.
Hello, please help me with the following.
My Moto X4 (XT1900-7) recently got the Android 9 (Pie) update. Since then I have problems with wifi and it's always dropping. Because of that I reset the phone, but now I can't even log into Play Store, because wifi keeps dropping all the time. I can't use the phone at all. Every guide I've tried getting back Android 8.1 back didn't work so far. Maybe the guides were **** or I simply didn't understand them. Also, my recovery mode doesn't even start.
I've downloaded "PAYTON_OPW27.57-40_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml". Would that be the correct version to install?
Please help.
Thanks in advance.
curious45 said:
Hello, please help me with the following.
My Moto X4 (XT1900-7) recently got the Android 9 (Pie) update. Since then I have problems with wifi and it's always dropping. Because of that I reset the phone, but now I can't even log into Play Store, because wifi keeps dropping all the time. I can't use the phone at all. Every guide I've tried getting back Android 8.1 back didn't work so far. Maybe the guides were **** or I simply didn't understand them. Also, my recovery mode doesn't even start.
I've downloaded "PAYTON_OPW27.57-40_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml". Would that be the correct version to install?
Please help.
Thanks in advance.
Click to expand...
Click to collapse
This one:
PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
but two things:
1) Your bootloader needs to be unlocked. If you have a locked bootloader and try to go 9 -> 8.1 you are bootlooped.
2) You will still get prompts to upgrade to Android 9. You can ignore them but they won't ever go away.
Yeah, I first need to unlock the bootloader, but that's where the problems start. I found a guide on motorola web page: motorola-global-portal[.]custhelp[.com]/app/standalone/bootloader/unlock-your-device-b
I've downloaded Android SDK (1 GB??!) and installed it. Then I've installed Motorola Device Manager. I've set my X4 to Fastboot Mode. The next step "On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)" I don't even understand. How do I "go to the directory", and what's my "$PATH"? That guide is as bad as it gets. I doesn't explain anything.
Edit: I've tried it through minimal adb fastboot command and could get my unlock-key. let's see how it goes from now on.
Thanks so far.
curious45 said:
Yeah, I first need to unlock the bootloader, but that's where the problems start. I found a guide on motorola web page: motorola-global-portal[.]custhelp[.com]/app/standalone/bootloader/unlock-your-device-b
I've downloaded Android SDK (1 GB??!) and installed it. Then I've installed Motorola Device Manager. I've set my X4 to Fastboot Mode. The next step "On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)" I don't even understand. How do I "go to the directory", and what's my "$PATH"? That guide is as bad as it gets. I doesn't explain anything.
Edit: I've tried it through minimal adb fastboot command and could get my unlock-key. let's see how it goes from now on.
Thanks so far.
Click to expand...
Click to collapse
I only get error messages when entering all the fastboot commands.
FAILED (command write failed (Unknown error))
I could flash it using my laptop now, but when turning it on it says "verity mode is set to logging" and keeps on rebooting in a loop. Then I tried using twrp and mount it using an sd card, but that gave me error messages. are you sure this version is the right one for me? How difficult can it be? I wanna smash the phone against a wall.
curious45 said:
I could flash it using my laptop now, but when turning it on it says "verity mode is set to logging" and keeps on rebooting in a loop. Then I tried using twrp and mount it using an sd card, but that gave me error messages. are you sure this version is the right one for me? How difficult can it be? I wanna smash the phone against a wall.
Click to expand...
Click to collapse
It is the correct Oreo firmware for your device.
Re-verify the commands you're entering to flash are:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash logo logo.bin
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
Bootloader is unlocked (the bottom of your fastboot screen says 'flashing_unlocked')?
Are you trying this in windows or linux?
I tried this version: PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT very often on my laptop (I guess it was a problem with the usb-ports on my normal pc), but I couldn't get my device to work. It always said "verity mode is set to logging". Then I tried installing PAYTON_OPW27.57-40_subsidy-DEFAULT_regulatory-DEFAULT once (with my laptop) and it worked without any problems. The only thing is, that the device now says it's not the correct os when booting.
curious45 said:
... It always said "verity mode is set to logging"....
Click to expand...
Click to collapse
This will display for everyone with an unlocked bootloader. I know it does for me.
jhedfors said:
This will display for everyone with an unlocked bootloader. I know it does for me.
Click to expand...
Click to collapse
But it didn't boot though. It showed this text and it kept restarting over and over again.
It's fine now with this PAYTON_OPW27.57-40_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml version, but I always get the notifications that I should update to Android 9. I don't have any wifi problems whatsoever.
Do you have a solution on how to really disable / block those?
2 days ago i woke up to my phone's screen already on, it had been frozen for 2 hours (woke up at 3:40pm but the phone lockscreen showed 1:14pm) so i held down the power button to soft reset it but when it turned itself back on the phone was now stuck in a bootloop. Been 2 days now of trial and error and a whole load of research which now leaves me here. I have unlocked the bootloader (also done critical unlock) but trying to flash stock rom (have tried multiple versions) through miflash gives me "Flash bluetooth_a error", trying to flash it manually through cmd on platform tools gives me the following:
fastboot flash bluetooth_a bluetooth.img
Sending 'bluetooth_a' (556 KB) OKAY [ 0.031s]
Writing 'bluetooth_a' FAILED (remote: 'Error flashing partition : Device Error')
fastboot: error: Command failed
Anyone know how i can fix this? It's not rooted and the bootloader had never been unlocked previously.
Why are you trying to flash the bluetooth_a? Any reason for this?
Have you tried to: fastboot boot recovery_image_name.img ? And from there try to solve it?
ricardohorta said:
Why are you trying to flash the bluetooth_a? Any reason for this?
Have you tried to: fastboot boot recovery_image_name.img ? And from there try to solve it?
Click to expand...
Click to collapse
"bluetoot_a" is the first thing it tries to flash through mi flash. Its also the first thing in the images.
I´m a bit of a newbie, but i would try to boot into TWRP with fastboot command. From there do a full wipe on the phone and try again.
You might loose all your data.
ricardohorta said:
I´m a bit of a newbie, but i would try to boot into TWRP with fastboot command. From there do a full wipe on the phone and try again.
You might loose all your data.
Click to expand...
Click to collapse
Im not able to boot into twrp, it just hangs on the splash screen.
It should load directly from the bootloader.
Maybe you can try different TWRP versions, maybe it helps.
Xiaomi Mi A2
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
There are some instructions also.
rxsta said:
Im not able to boot into twrp, it just hangs on the splash screen.
Click to expand...
Click to collapse
I had that too. You can use this twrp https://androidfilehost.com/?fid=17248734326145702860 provided by @tecknight (here in post 2: https://forum.xda-developers.com/t/...lineageos-nightly-if-i-update-the-os.4240753/)
Sorry @User699 I was out of town, but I'm back now. What's your current status ?
User699 said:
I had that too. You can use this twrp https://androidfilehost.com/?fid=17248734326145702860 provided by @tecknight (here in post 2: https://forum.xda-developers.com/t/...lineageos-nightly-if-i-update-the-os.4240753/)
Click to expand...
Click to collapse
When i boot this version of twrp, the screen goes black for a bit but then just reboots itself.
Finally booted but still hanging on splash screen.
Well, that's odd. I tried this on LineageOS, maybe it doesn't work with another OS...
Did you do
Code:
fastboot boot twrpIMG.img
and NOT
Code:
fastboot flash boot twrpIMG.img
?
User699 said:
Well, that's odd. I tried this on LineageOS, maybe it doesn't work with another OS...
Did you do
Code:
fastboot boot twrpIMG.img
and NOT
Code:
fastboot flash boot twrpIMG.img
?
Click to expand...
Click to collapse
Yes, think it's safe to assume it's a lost cause. Not sure if i want to buy from xiaomi again.
rxsta said:
Yes, think it's safe to assume it's a lost cause. Not sure if i want to buy from xiaomi again.
Click to expand...
Click to collapse
EDIT 2: Please try
Code:
fastboot getvar all
and look for
Code:
(bootloader) current-slot:a
first. It could also be slot b instead of slot a.
If it's slot a, change the slot using
Code:
fastboot set_active b
, else insert `a' instead.
Then reboot.
Maybe this helps to load your OS.
Well, if losing your data is an option, you could try to factory data reset your device via your recovery (the one that is already present, no need to boot one).
If that also doesn't help, you could try:
Code:
fastboot -w
to wipe your phone. I don't know, however, if you need to reflash everthing again after doing that fastboot wipe, but since you wanted to flash via miFlash either, it shouldn't be much of an issue.
EDIT: It should just wipe it:
Code:
-w Erase userdata and cache (and format if supported by partition type).
(from `fastboot --help')
Changed slots but still won't boot, tried doing the "fastboot -w" but got this error
fastboot -w
Erasing 'userdata' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
User699 said:
EDIT 2: Please try
Code:
fastboot getvar all
and look for
Code:
(bootloader) current-slot:a
first. It could also be slot b instead of slot a.
If it's slot a, change the slot using
Code:
fastboot set_active b
, else insert `a' instead.
Then reboot.
Maybe this helps to load your OS.
Well, if losing your data is an option, you could try to factory data reset your device via your recovery (the one that is already present, no need to boot one).
If that also doesn't help, you could try:
Code:
fastboot -w
to wipe your phone. I don't know, however, if you need to reflash everthing again after doing that fastboot wipe, but since you wanted to flash via miFlash either, it shouldn't be much of an issue.
EDIT: It should just wipe it:
Code:
-w Erase userdata and cache (and format if supported by partition type).
(from `fastboot --help')
Click to expand...
Click to collapse
User699 said:
EDIT 2: Please try
Code:
fastboot getvar all
and look for
Code:
(bootloader) current-slot:a
first. It could also be slot b instead of slot a.
If it's slot a, change the slot using
Code:
fastboot set_active b
, else insert `a' instead.
Then reboot.
Maybe this helps to load your OS.
Well, if losing your data is an option, you could try to factory data reset your device via your recovery (the one that is already present, no need to boot one).
If that also doesn't help, you could try:
Code:
fastboot -w
to wipe your phone. I don't know, however, if you need to reflash everthing again after doing that fastboot wipe, but since you wanted to flash via miFlash either, it shouldn't be much of an issue.
EDIT: It should just wipe it:
Code:
-w Erase userdata and cache (and format if supported by partition type).
(from `fastboot --help')
Click to expand...
Click to collapse
Doubt there's anything else I can do.
Think it's important I also mention that I can't get into the phone's recovery.
I see.
I'm sorry, I don't have any ideas toward it right now...
The only thing I could think of is booting into edl (emergency donwload) and reflash your os that way.
But you would have to open your device to access its hardware and since I don't have any experience with it, I couldn't help with it.
Changed slots but still won't boot, tried doing the "fastboot -w" but got this error
fastboot -w
Erasing 'userdata' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Click to expand...
Click to collapse
Does your device display anything on its screen?
User699 said:
I see.
I'm sorry, I don't have any ideas toward it right now...
The only thing I could think of is booting into edl (emergency donwload) and reflash your os that way.
But you would have to open your device to access its hardware and since I don't have any experience with it, I couldn't help with it.
Does your device display anything on its screen?
Click to expand...
Click to collapse
nope, it stays on the fastboot screen with no change. Warranty ended few days before the phone died so may as well try it.
rxsta said:
nope, it stays on the fastboot screen with no change. Warranty ended few days before the phone died so may as well try it.
Click to expand...
Click to collapse
I wish you the best of luck!
Hi guys, im posting this hoping theres a solution for my problem. I was folowing this guide to try install the stock firmware on this device and remove a virus that i wasnt able to remove even after cleaning the user data partiton (it was an anoying bar that started every time the phone booted). Well everything went acording to plan until i send a reboot command trough adb before flashing anything. Now the phone wont turn on and my computer doesnt detect it, doesnt show anything on screen and the computer plays the pluged and unplugged hardware sound constantly.
Moto E4 Guide To Full Stock Firmware Restore and Re-lock Bootloader Any Variant
Note : Do not erase/flash Bootloader file preloader.img or preloader.binfastboot erase preloader fastboot flash preloader preloader.img Do not erase/flash partition table file pgpt.img/gpt.img or pgpt.bin/gpt.binfastboot erase pgpt or gpt...
forum.xda-developers.com
fastboot erase boot
fastboot erase efuse
fastboot erase expdb
fastboot erase flashinfo
fastboot erase frp
fastboot erase hw
fastboot erase keystore
fastboot erase lk
fastboot erase logo
fastboot erase metadata
fastboot erase nvdata
fastboot erase nvram
fastboot erase oem
fastboot erase oemkeystore
fastboot erase otp
fastboot erase para
fastboot erase persist
fastboot erase proinfo
fastboot erase protect1
fastboot erase protect2
fastboot erase recovery
fastboot erase seccfg
fastboot erase secro
fastboot erase tee1
fastboot erase tee2
fastboot erase utags
fastboot erase system
fastboot erase userdata
Click to expand...
Click to collapse
I ran all of the above, searching on the forums i find some people that could get the phones back into adb using an sd card but the image files dont match my model number. Is there any way the phone can be recovered?.
R3ISEN said:
Hi guys, im posting this hoping theres a solution for my problem. I was folowing this guide to try install the stock firmware on this device and remove a virus that i wasnt able to remove even after cleaning the user data partiton (it was an anoying bar that started every time the phone booted). Well everything went acording to plan until i send a reboot command trough adb before flashing anything. Now the phone wont turn on and my computer doesnt detect it, doesnt show anything on screen and the computer plays the pluged and unplugged hardware sound constantly.
Click to expand...
Click to collapse
If you PC is making that sound, it is connecting, it may be in some kind of bootloop.
try using wall charger for a few hours.
Moto E4 Guide To Full Stock Firmware Restore and Re-lock Bootloader Any Variant
Note : Do not erase/flash Bootloader file preloader.img or preloader.binfastboot erase preloader fastboot flash preloader preloader.img Do not erase/flash partition table file pgpt.img/gpt.img or pgpt.bin/gpt.binfastboot erase pgpt or gpt...
forum.xda-developers.com
I ran all of the above, searching on the forums i find some people that could get the phones back into adb using an sd card but the image files dont match my model number. Is there any way the phone can be recovered?.
Click to expand...
Click to collapse
Not unless it's in EDL mode, PC will show it as a Qualcomm device.
sd_shadow said:
If you PC is making that sound, it is connecting, it may be in some kind of bootloop.
try using wall charger for a few hours.
Not unless it's in EDL mode, PC will show it as a Qualcomm device.
Click to expand...
Click to collapse
Thanks ill try pluggin it to the wall for a few hours, i will post back with the updates
Well i left it overnight to charge and now ive got the same unplugged and plugged hardware sound on windows but the device manager shows up a "MT65xx preloader" that pops in and out from the list.
Do you think there is good sign?
R3ISEN said:
Well i left it overnight to charge and now ive got the same unplugged and plugged hardware sound on windows but the device manager shows up a "MT65xx preloader" that pops in and out from the list.
Do you think there is good sign?
Click to expand...
Click to collapse
Yes, the MT65xx preloader means you have a MediaTek processor.
The XT1772 MediaTek version is codename is nicklaus.
Try this Flashtool
https://mirrors-obs-2.lolinet.com/firmware/motorola/2016/nicklaus/flashtool/
sd_shadow said:
Yes, the MT65xx preloader means you have a MediaTek processor.
The XT1772 MediaTek version is codename is nicklaus.
Try this Flashtool
https://mirrors-obs-2.lolinet.com/firmware/motorola/2016/nicklaus/flashtool/
Click to expand...
Click to collapse
I dont have the MediaTek DA USB VCOM driver installed, so at the moment it only shows up a unknown device. Could you help my find the correct driver? Also, if i manage to get the tool to flash the phone do i have to untick any component from the list? (like preloader) or i jus select everything?
Thank you in advance
Hey good news i finally was able to resucitate the phone! i found the drivers searching for the device id shown in device manager. I used the latest sp flash tool with my oem rom with all the firmware modules selected and got it working!. Now im trying to relock the bootloader to completly restore it to factory defaults.