Hi, I first did factory reset then hard reset moto e gen 1 running on android 5.1.
After booting and selecting language, phone asked for wifi connection (skip button is grayed) when I connect to any available working wifi network it stucks at (checking connection screen) and stays there only.
Please tell me how to sort this out.
Did you tried hard resetting again?
Yep! No use
rizzee said:
Yep! No use
Click to expand...
Click to collapse
Stock android 5.1 received through ota?
Man many random issues keep popping up in that.
You can always try any custom rom or if you want stock one check this out :
http://forum.xda-developers.com/showthread.php?t=2755857
-z3r0- said:
Stock android 5.1 received through ota?
Man many random issues keep popping up in that.
You can always try any custom rom or if you want stock one check this out :
http://forum.xda-developers.com/showthread.php?t=2755857
Click to expand...
Click to collapse
Was trying to install stock rom, but when I enter the command it stucks. I think phone is not getting connected. It shows conneting phone and stays like this. Motorola Driver is installed.
rizzee said:
Was trying to install stock rom, but when I enter the command it stucks. I think phone is not getting connected. It shows conneting phone and stays like this. Motorola Driver is installed.
Click to expand...
Click to collapse
In which step it's actually getting stuck?
you can check if it's your device is connected or not by this command in fastboot mode -
Code:
fastboot devices
or (if you have mfastboot)
Code:
mfastboot devices
-z3r0- said:
In which step it's actually getting stuck?
you can check if it's your device is connected or not by this command in fastboot mode -
Code:
fastboot devices
or (if you have mfastboot)
Code:
mfastboot devices
Click to expand...
Click to collapse
Hi when I enter any of these command, it says <waiting for the device>
this is the same message I get with every command.
rizzee said:
Hi when I enter any of these command, it says <waiting for the device>
this is the same message I get with every command.
Click to expand...
Click to collapse
Your device isn't detected by your pc maybe because of inappropriate drivers.
If drivers are properly installed maybe you have issues with your usb cable.
Also check on phone if it says USB Conncted in fastboot mode, after connecting the usb.
-z3r0- said:
Your device isn't detected by your pc maybe because of inappropriate drivers.
If drivers are properly installed maybe you have issues with your usb cable.
Also check on phone if it says USB Conncted in fastboot mode, after connecting the usb.
Click to expand...
Click to collapse
Yes, on phone its showing "USB Connected".
I only installed Motorola Driver kit. Do I need any other driver?
Uninstall it and then install motorola device manager. Try afterwards.
-z3r0- said:
Stock android 5.1 received through ota?
Man many random issues keep popping up in that.
You can always try any custom rom or if you want stock one check this out :
http://forum.xda-developers.com/showthread.php?t=2755857
Click to expand...
Click to collapse
i checked and did all the steps as told in the link. But after fastboot reboot the the fone displays the fastboot mode with message "failed to validate system image" and the fone does not boot up.
My device is MOTO E, XT1022. i tried with android lollipop from the stock roms.
joelfinz said:
i checked and did all the steps as told in the link. But after fastboot reboot the the fone displays the fastboot mode with message "failed to validate system image" and the fone does not boot up.
My device is MOTO E, XT1022. i tried with android lollipop from the stock roms.
Click to expand...
Click to collapse
You may check out this one :
http://forum.xda-developers.com/showpost.php?p=48802176&postcount=29
rizzee said:
Hi, I first did factory reset then hard reset moto e gen 1 running on android 5.1.
After booting and selecting language, phone asked for wifi connection (skip button is grayed) when I connect to any available working wifi network it stucks at (checking connection screen) and stays there only.
Please tell me how to sort this out.
Click to expand...
Click to collapse
I too had this exact same problem of the phone getting stuck at that screen forever. As far as I remember, I fixed it by wiping system partition. I faced this problem several times and tried hard resetting and all but wiping system partition always fixed the issue. Ofcourse you have to flash stock via fastboot following this.
Related
Hey guys, i need your help
I've unlocked the bootloader the unofficial way and now i want to go back.
I tried to flash the fastboot 7.1.8.0 global stable in edl mode according to this guide:
*sorry, not allowed to post outside links*
The max buffer size error occured, i followed the steps, replaced the files and wanted to flash again, now the error "error: receiving hello packet" occurs...
I'm stuck in edl mode right now and i cant flash. what to do now?
Thanks in advance!
//edit: okay it looks like the flash process was not completed, so i could get into fastboot and then "fastboot reboot". previous rom is still booting, what the hell ...
Try rebooting into edl mode again and flash back the rom
neme2k said:
Hey guys, i need your help
I've unlocked the bootloader the unofficial way and now i want to go back.
I tried to flash the fastboot 7.1.8.0 global stable in edl mode according to this guide:
*sorry, not allowed to post outside links*
The max buffer size error occured, i followed the steps, replaced the files and wanted to flash again, now the error "error: receiving hello packet" occurs...
I'm stuck in edl mode right now and i cant flash. what to do now?
Thanks in advance!
//edit: okay it looks like the flash process was not completed, so i could get into fastboot and then "fastboot reboot". previous rom is still booting, what the hell ...
Click to expand...
Click to collapse
Hi gus! have you solved your problem
Provide me your solution please, i'm in the same situation now with my Redmi note 3 Dual Sim
@mofazar
Hi,
Have you tried to reboot your computer? If you're not, then just try to reboot it without disconnecting your device.
And then just try it again.
Thanks.
karkand said:
@mofazar
Hi,
Have you tried to reboot your computer? If you're not, then just try to reboot it without disconnecting your device.
And then just try it again.
Thanks.
Click to expand...
Click to collapse
already try this step but still same error.
Windows must be 64bit (windows 7 or later),connect your phone to rear usb ports. In my case this was the problem (same error as yours).
Sent from my Redmi Note 3 using Tapatalk
I've the same problem. There is a solution? I've the virtualisation of Windows 7 64bit on linux, i don't know if this is the problem or not.
Got the solution....
I got the solution for all xiaomi users...
You just have to factory reset the device an then you are ready to go
if your device doesn't start then go to the fastboot menu and open cmd in the pc after connecting the phone to the pc...
then follow my steps
1. go to the adb folder.......
2. Then hold shift and right click there and click on "Open Command Prompt Here" it will open cmd .
3. The check if the device is detected or not if not the go to device manager and update the driver...
to check type : fastboot devices
4. then type fastboot -w it will wipe your whole data and do not start the phone firstly just flash the stock rom and then turn it on...
5. hurray i hope your problem will be solved.....
Thank you............
So I tried install Bliss ROM to my Moto E 1st gen. After installation its stuck at the screen where it says "Warning Bootloader Unlocked".
The phone is not detected by laptop. In Linux there are no extra messages in dmesg logs and in Windows, Device Manager shows no additional USB device. If I press power button the phone will restart and stay in the initial screen and will continue so until its battery is drained out.
I tried adb, fastboot, mfastboot and qboot but they are unable to detect phone.
What can I do to make my device functional again?
ravi.xolve said:
So I tried install Bliss ROM to my Moto E 1st gen. After installation its stuck at the screen where it says "Warning Bootloader Unlocked".
The phone is not detected by laptop. In Linux there are no extra messages in dmesg logs and in Windows, Device Manager shows no additional USB device. If I press power button the phone will restart and stay in the initial screen and will continue so until its battery is drained out.
I tried adb, fastboot, mfastboot and qboot but they are unable to detect phone.
What can I do to make my device functional again?
Click to expand...
Click to collapse
Try any different ROM (clean flash ),
It might be a ROM issue!
Sent from my Moto E using XDA-Developers mobile app
My problem to begin with is that I cannot get to a point where it is detected as by any tool on PC. So how can I flash it?
ravi.xolve said:
My problem to begin with is that I cannot get to a point where it is detected as by any tool on PC. So how can I flash it?
Click to expand...
Click to collapse
Do you have twrp? If yes, then flash using twrp. It doesn't need pc
AFAIK, it shouldn't be a rom issue. Anyways you can try to flash another rom
Afaik no issues in last build of bliss
Sent from my Moto E using Tapatalk
Solved
Solved by pressing volume down and power for very long time, booted into TWRP and flashed with factory ROM
Yesterday I tried to flash a a new rom on my Xperia Z2 (unlocked bootloader).
From TWRP I did an advanced wipe and selected basically everything except my mircoSD (because it has the new files).
After a long time of waiting I tried to flash the ZIP file and it gave me an error. I thought this had to do with the wipe so I decided to reboot my phone.
As you can imagine, it got stuck on the Sony logo (because system would be empty).
From this moment I couldn't do anything with my phone, except from the tool Emma.
I now have some clean installation of Sony their Android 6.0.1 for the Z2 (23.5.A.0.570) but Im unable to flash TWRP through fastboot.
The command adb devices shows my phone, fastboot devices gives an empty response.
When I restart to the bootloader from adb and try to flash TWRP I get the message "< waiting for device >".
I tried on three different PCs including a clean install of Windows with all kind of different drivers, yet I cant get fastboot to work.
Am I stuck with this unrooted version of Android now or do you guys have any suggestions for me?
Thanks in advance!
Install drivers correctly
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
As I said I've tried all kind of different drivers (Android tools, Sony drivers and flahstool drivers). So for me it's hard to tell what I'm doing wrong.
My computer notices the phone (if I hold volume up and attach the charger), it just doesn't show up under fastboot devices.
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
PaulusE said:
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
Click to expand...
Click to collapse
Manually boot into recovery by booting up your device normally and when you see a violet LED, press vol+.
Hello guys!
I've been looking for a solution to this problem, I have a Moto One XT1941-5 that was never rooted nor bootloader unlocked. I left it charging and after about one hour it was at Fastboot Mode, it says that it failed booting from normal mode. Even if I try to restart or start normally, it gets back to Fastboot.
What have I done until now?
- Tried to flash the whole latest STOCK ROM again (manually with fastboot tools)
- Tried with a ROM from another region (mine is OPENMX and tried with RETLA) and I get the same
- Tried with Repair Assistant from Motorola, nothing happens.
- Tried to unlock bootloader, it asks me to enable OEM unlock on Developer settings (I can't, phone doesn't power up)
* Something that gets me confused is about the slots, $fastboot getvar all reports that none of the slots are bootable, every time I flash the ROM it says that slot A is bootable and B not, or that A is not bootable and B yes, or none of the slots are bootable.
Here are some screenshots about the info I have.
You can follow these steps from https://forum.xda-developers.com/motorola-one/how-to/unroot-ota-wipe-data-tested-t3905745 and then fastboot erase userdata and try to boot again.
lucasdeeiroz said:
You can follow these steps from https://forum.xda-developers.com/motorola-one/how-to/unroot-ota-wipe-data-tested-t3905745 and then fastboot erase userdata and try to boot again.
Click to expand...
Click to collapse
Just unzipped the bat, and opened with a text editor... those are exactly the commands I manually used, nothing has worked until now.
adri_sefp said:
Just unzipped the bat, and opened with a text editor... those are exactly the commands I manually used, nothing has worked until now.
Click to expand...
Click to collapse
When did you buy this phone?
borksek said:
When did you buy this phone?
Click to expand...
Click to collapse
On June 2018, warranty is not valid any longer. Carrier just give us 1 year here in Mexico.
I never had a problem like this, I was looking forward to find the blankflash for this model but it doesn't exist yet, maybe all I can do is wait for it or hard brick it. :crying:
adri_sefp said:
On June 2018, warranty is not valid any longer. Carrier just give us 1 year here in Mexico.
I never had a problem like this, I was looking forward to find the blankflash for this model but it doesn't exist yet, maybe all I can do is wait for it or hard brick it. :crying:
Click to expand...
Click to collapse
did you manage to solve this problem?
claudiusuflea said:
did you manage to solve this problem?
Click to expand...
Click to collapse
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
adri_sefp said:
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
Click to expand...
Click to collapse
that means there's no work-arround
adri_sefp said:
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
Click to expand...
Click to collapse
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
claudiusuflea said:
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
Click to expand...
Click to collapse
Even if you do that, there's no blankflash for this model... as long as I know, I was looking forward to find it somewhere but there is none available.
claudiusuflea said:
that means there's no work-arround
Click to expand...
Click to collapse
That's correct, now my device shows nothing on screen, it is just black but when I plug the usb cable, fastboot detects it as fastboot mode, all commands are working but nothing else works.
I'm giving up now.
claudiusuflea said:
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
Click to expand...
Click to collapse
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
adri_sefp said:
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
Click to expand...
Click to collapse
works if I have the bootloader still locked?
adri_sefp said:
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
Click to expand...
Click to collapse
followed all the steps, bricking worked, but after flashing the latest software had the same problem
it would be nice if motorola would give us qfil software so we could flash it from the scratch
also, anyone any other option in this case? also found a dump of deen android 10 but I don't know what to do with it
claudiusuflea said:
followed all the steps, bricking worked, but after flashing the latest software had the same problem
it would be nice if motorola would give us qfil software so we could flash it from the scratch
also, anyone any other option in this case? also found a dump of deen android 10 but I don't know what to do with it
Click to expand...
Click to collapse
Was your device detected as Qualcomm? Did you use the blankflash file? Did yor phone boot to fastboot?
adri_sefp said:
Was your device detected as Qualcomm? Did you use the blankflash file? Did yor phone boot to fastboot?
Click to expand...
Click to collapse
Indeed, after flashing an Android 8 firmware my phone went into Qualcomm 908 EDL mode. After blankflashing and flashing the latest firmware had the same issue with "No bootable A/B slot". The same state before hardbricking the phone (AP Fastboot flash mode secure).
adri_sefp said:
Hello guys!
I've been looking for a solution to this problem, I have a Moto One XT1941-5 that was never rooted nor bootloader unlocked. I left it charging and after about one hour it was at Fastboot Mode, it says that it failed booting from normal mode. Even if I try to restart or start normally, it gets back to Fastboot.
What have I done until now?
- Tried to flash the whole latest STOCK ROM again (manually with fastboot tools)
- Tried with a ROM from another region (mine is OPENMX and tried with RETLA) and I get the same
- Tried with Repair Assistant from Motorola, nothing happens.
- Tried to unlock bootloader, it asks me to enable OEM unlock on Developer settings (I can't, phone doesn't power up)
* Something that gets me confused is about the slots, $fastboot getvar all reports that none of the slots are bootable, every time I flash the ROM it says that slot A is bootable and B not, or that A is not bootable and B yes, or none of the slots are bootable.
Here are some screenshots about the info I have.
Click to expand...
Click to collapse
maybe works "lenovo rescue and smart assistant"
Marc.os said:
maybe works "lenovo rescue and smart assistant"
Click to expand...
Click to collapse
No, lmsa would recognise the phones after A10 update, but the problem persists. Someone who has repaired this or someone who has managed to take it to the service or managed to revive the phone from this state? With locked bootloader
Marc.os said:
maybe works "lenovo rescue and smart assistant"
Click to expand...
Click to collapse
That didn't help either, there's nothing else we can do than replacing the main board.
Hello.
I have a similar problem. I have tried all of the methods listed, unfortunately nothing works. I ended up replacing the motherboard. The old PCB is waiting, maybe someday it can be repaired.
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
UnequalB said:
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
Click to expand...
Click to collapse
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
UnequalB said:
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Click to expand...
Click to collapse
You can flash the TWRP image through fastboot and then boot to it through commands.
UnequalB said:
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
Click to expand...
Click to collapse
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
SubwayChamp said:
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
You can flash the TWRP image through fastboot and then boot to it through commands.
Click to expand...
Click to collapse
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
SubwayChamp said:
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Click to expand...
Click to collapse
Weirdly enough the error i got was not listed here..
SubwayChamp said:
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
Click to expand...
Click to collapse
This method doesn't work either since the phone won't stay off for more than 7 seconds.
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
UnequalB said:
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
Click to expand...
Click to collapse
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
UnequalB said:
Weirdly enough the error i got was not listed here..
This method doesn't work either since the phone won't stay off for more than 7 seconds.
Click to expand...
Click to collapse
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
UnequalB said:
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
Click to expand...
Click to collapse
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
SubwayChamp said:
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
Click to expand...
Click to collapse
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
UnequalB said:
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
Click to expand...
Click to collapse
Well, if you interrupted the process, that's not good at all. The only you can do is keeping trying it, if your motherboard was not damaged.
hi guys i am DELTIERO from the Philippines did you allready solve the problem?
If not yet done message me on my facebook page https://www.facebook.com/del.villalobos.1/
and i will help you im here veltech san carlos negross occidental phil
Help please! I flashed a gapps zip file using flashify on my infinix smart 5 x657 (Running on lineageos gsi android 12) then the phone just went off. and it not turning on. but it shows the charging indicator light when i connect it to power.
I've tried disconnecting the battery still nothing
what possible solution is there for this?