Hey everyone, I recently purchased a Moto e5 plus and saw there is an update available (check attachments). But strangely enough, after the phone reboots and enters the phase to update itself, around the 25% or so mark, it makes a sudden jump in progress and then fails to continue, stopping the process.
I do have a stock rom, recovery and boot sector. Only custom thing being is that the device has an unlocked bootloader.
I'm wondering if any of you have had a similar experience or if it's just me. And maybe if you have heard of any way to fix it.
I'm all ears.
Looks like the second picture didn't upload correctly? Odd.
Here is it again:
Never mind, somehow the device managed to update itself. Only difference I can remember was that this time the phone didn't have a pattern look on boot. Not sure if it made any difference. At least I'm running the latest version now.
Related
Ok.
first off, Hii!! this is my first ever time writing on XDA.
Any way, i know this is not a new issue.. but my ATIV S is rebooting every 5 seconds after the 8.1 update via preview for developers.....
i did a lot of digging before writing here and found this thread : http://forum.xda-developers.com/showthread.php?t=2718023
I followed the instructions and flashed the GT-I8750_DXBMJ1_R_signed ROM along side the GT-I8750_VJALL3_P csc (this is the only combination that gave me some results.
After flashing, my phone did manage to boot up finally but with a twist. Trying to restart the phone sends me back to the boot loop forcing me to reflash everything again.
i tried the tip from the thread to download the preview for developers app and try to update the phone again (claiming it will resolve the issue) but as soon as the phone goes to reboot before the update the boot loop comes back and we're back to squire one.... so i'm kinda stuck.... is there any kind of FIX i can try to help me sad situation? :crying::crying::crying::crying:
I've had a lot of issues with my Ativ S as well.
Your rebooting issue seems recognizable, maybe this thread will help : https://social.msdn.microsoft.com/F...ime-after-wp-81-update?forum=winphoneosissues
Anyway, I'm on the latest Developer Preview update, my Firmware version is : 2424.14.9.3
It seems the phone is much more stable now, however i'm only using this phone for development, there is no sim card present anymore.
Switched to a new Nokia for my main device.
Advice : If you want a decent Windows Phone, buy a Nokia, not a Samsung or HTC.
Thank you for the reply!
i did some more digging and found that flashing the GDR2 FW 2424 actually helps. after that the is a need to update the phone to the official GDR3 update in the phone updater in settings. i am trying that as we speak and really hope it will work
BTW this ATIV S is my backup phone and not my daily driver (i use a Galaxy s4) i just wanna fix it up to use as my work phone. my trust in windows phone is gone for now XD
EDIT: OK, so i followed the thread and applied the instructions...
at first, i flashed the GDR2 official ROM with the instructed csc file and everything booted up well. at this point they say that if the phone is to be restarted the boot loop will come back (it did when i tested it)
afterwards, i installed the preview for developers app and started updating to the official GDR3 update as instructed. it finished up and booted up well. the next step was to update to 8.1... i did and at first it worked well but as soon as i disconnected the USB cable, the loop returned again. (if i connect the USB cable back it's booting up normally)
BTW i tried doing it all from scratch and noticed that in every step of the process, if i disconnect the cable the loop come's back and disappears as soon as i plug it back in... anyone has any idea what to do next?
I absolutely hate creating yet another thread, but I've tried everything I can and I'm stuck. I was up until 4am (no lie) last night and been at it again for hours tonight. So... here are the symptoms.
Multiple bootloops/reboots at any of the following points:
1) "Preparing device" with the "Please wait" animation.
2) Force close: Unfortunately, Setup has stopped.
3) Force close: process.com.android.systemui has stopped.
4) Force close: Google search has stopped.
5) Bootloop at the bootloader warning message
Usually, the boot animation doesn't even start. Often, I'll see the "Bootloader Unlocked" warning message, then the Moto logo, then it cycles back through any of the above fail points. Sometimes, it'll stay on the bootloader warning message the whole time and then jump directly to the lock screen.
All of this started after unlocking my brand new Moto X Pure Edition and then attempting to use the "Multi-tool" to root. Or...maybe it was after trying to root using one of the Chainfire images. I can't recall. After doing so, wifi stopped working (wouldn't turn on). So, I tried (using the tool again) to flash back to stock. At that point things strange things started happening (force closes). I then tried flashing to stock and immediately flashing the OTA (all via fastboot). When I booted up, Lollipop setup wouldn't load, it'd bootloop, come back and maybe I could get to the next screen, but wifi would be dead. Or I'd get wifi to work, but it'd crash after accepting Google privacy terms.
So, after all of that, I decided I would just revert back to stock. At that point I tried a number of options including what I think is the likely best bet, @SolarTrans guide here. Oh, and somewhere along the line I flashed TWRP 2.8.3 and flashed one of the custom ROMs (LiquidSmooth). It booted, but was very unstable and also threw the same/similar systemui force close messages, occasionally would lose wifi or begin force closing like crazy. Makes me think I have a bigger issue since it happens regardless of ROM/firmware. I also tried graffixnyc's images. So... yeah... just want to get back to stock.
I've been doing this stuff with Android for many years. Not a newbie by any means. Completely comfortable using fastboot or adb command line. I'm just at a loss and feel that it's likely I'll have to send it back to Motorola. I can get into the bootloader no problem. Everything else is a toss up. The last time I flashed files via the SolarTrans guide, it eventually loaded up the home screen (after many bootloops), but wifi wasn't working and I got a strange Moto message about reverting the sensors firmware or update. I rebooted and it never booted again, so I erased cache and userdata via fastboot. That didn't help. I just flashed the original firmware again and it spent a good 20/30 minutes bootlooping before getting to the setup screens. I skipped everything. Then it bootlooped at the home screen.
Open to suggestions!
Edit 1:
Pretty much anything causes the phone to bootloop, but I was able to get a screenshot of the baseband, kernel, build, etc. It bootlooped, but worked the second time around. I think I just made things way worse by trying to turn on bluetooth. It's just bootlooping over and over. Gonna try and get some sleep!
So, before bed, I flashed the OTA from the SolarTrans thread. It booted up, threw some errors and then once I connected to wifi it bootlooped. It did this for at least 10 minutes before I plugged the phone in and went to bed. When I woke up this morning, it was sitting on the setup screen. No errors. I signed in to my Google account and it restored all my apps. I rebooted. Still no problems. Just before leaving for work, I noticed that Dropbox wasn't installed. I installed it, signed in and then it bootlooped. After that...no luck. Kept rebooting. So, I brought the phone to work and left it on my desk for a few hours. It bootlooped or hung on the bootloader unlocked warning screen for at least 3 hours. I wiped cache. Same thing. Just now, I wiped userdata and rebooted. It went through the setup process without errors. Began restoring my apps and then froze. I manually restarted and now... no dice. Bizarre.
mercado79 said:
So, before bed, I flashed the OTA from the SolarTrans thread. It booted up, threw some errors and then once I connected to wifi it bootlooped. It did this for at least 10 minutes before I plugged the phone in and went to bed. When I woke up this morning, it was sitting on the setup screen. No errors. I signed in to my Google account and it restored all my apps. I rebooted. Still no problems. Just before leaving for work, I noticed that Dropbox wasn't installed. I installed it, signed in and then it bootlooped. After that...no luck. Kept rebooting. So, I brought the phone to work and left it on my desk for a few hours. It bootlooped or hung on the bootloader unlocked warning screen for at least 3 hours. I wiped cache. Same thing. Just now, I wiped userdata and rebooted. It went through the setup process without errors. Began restoring my apps and then froze. I manually restarted and now... no dice. Bizarre.
Click to expand...
Click to collapse
So, what was the problem then? The Dropbox app? Why is that?
No. Don't think so. It was just the trigger. I'm convinced any app would have eventually caused the bootloop.
I tried one more clean install of the official image straight from Motorola last night. Same results. So, I've initiated a return/repair.
Sent from my Moto X
Have they accepted repairing your device even with unlocked bootloader and root?
Sent from my XT1097 using XDA Free mobile app
They acknowledged that I'd unlocked the phone (it was logged in the record when they looked up my phone by IMEI), though I said I did so while trying to fix it (in order to wipe partitions and flash images which I also requested via their developer resources page).
They're sending a replacement phone without any push back at all. Honestly, I expected to send it in for repair. The rep said the standard protocol was to issue me a pin to order a new phone (mine is a customized Moto Maker model with a bamboo back).
Just so you're aware, unlocking the bootloader on Pure Edition phones does not void the warranty.
So, a replacement should be in my hands in about a week, I'm told. The phone was still within the initial month and so they're sending a brand new phone.
Sent from my Moto X
So here's my story: my phone was JellyBean. I didn't tinker with it, didn't root, just used some launchers. It upgraded to KitKat. I kept using it, even though I liked JellyBean better. Then one month ago it froze and stopped responding even to physical buttons. I managed to restart it, but it wouldn't go past the intel logo. Somehow I got it to go past it and give me like two seconds on before it would freeze and become unresponsive again, so I got to enter safe mode (all following instructions on the internet, which buttons to hold to manage to get into safe mode). Once in safe mode, I deleted every app that had been recently updated or installed, one at a time, trying to turn my phone on each time, until I finally deleted facebook (that enourmous blue monstrosity taking all that internal space), and the phone seemed normal. I re-installed the other apps I had uninstalled, then one day later, it froze again. Now it wouldn't go past the intel logo. Only then I gave up and used RSDLite to re-install the firmware - BUT! The firmware I managed to find was JB, but I had been wanting to downgrade for some time, anyway, so I unlocked the bootloader and flashed JellyBean. And it worked. I was proud. Then one month later, today, it froze again. I can do the same procedure, and lose all my data again, but I fear the problem will remain unsolved and it will freeze/crash/explode one month from now. Can someone help me figure out what my problem is, or give an alternate solution to try?
TL;DR:
my razr i was stuck on the intel logo screen, I unlocked the bootloader and flashed JB, it worked, one month later it is now stuck on the WARNING BOOTLOADER UNLOCKED screen. Please help thank you.
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option to upgrade to marshmallow and an unlocked bootloader. It uses the google launcher by default. I am pretty experienced with root as i have used rooted android phones for more than 4 years now (my first one was a Samsung Galaxy S2) and haven't had any problems until now. I had recently downloaded FaceNiff, one of the sniffing apps for android, and when i pressed start, it would automatically stop. I thought it was maybe a problem of the apps compatibility with my phone, but after researching for a long time, nothing came up so i decided to try another sniffing app. I moved on to DroidSniff, yet, I had the same problem, but this one wouldn't only stop, it would crash. I researched on this app too. Nothing. So I later downloaded one called DroidSheep, and when I started this one, I was lucky that an error was displayed, it was something about Position Independent Executables (PIE), it said "Only Position Independent Executables are supported" or something around those lines. So I decided to research PIE, and I found on the XDA Forums that you could fix this by changing the system/bin/linker file for a custom linker file, which a download link was provided for. I downloaded the file, changed it for the old linker file and tried the apps again. Apparently, I didn't have root access anymore! None of the root apps worked, I thought maybe I had to reboot my phone for my root to come back or for the custom linker to work. So i powered off my phone, turned it on, but instead of turning on, it would say the "Warning unlocked bootloader" thing, and then show a picture of and Android lying down with a caution sign, with the text "No Command" underneath. It's currently in this state, and the phone won't stop repeating this until it runs out of battery. The good thing is I can hold the power and volume down button to enter the fastboot menu, and i can then go into recovery. After this happened, I went to recovery and factory reset my phone, but it still didn't work, so I factory reset it again. It still charges, with a wall plug and with a computer. I think the computer recognises the phone, and I'm pretty sure I have USB Debugging enabled.
To sum this up, I changed the file system/bin/linker for a modified version of it and my phone won't boot up.
Custom linker file: http://forum.xda-developers.com/attachment.php?attachmentid=2821644&d=1403933203
Link to the website where it said you can change the linker files to fix the PIE problem: http://forum.xda-developers.com/google-nexus-5/development/fix-bypassing-pie-security-check-t2797731/page1
AgusC said:
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option to upgrade to marshmallow and an unlocked bootloader. It uses the google launcher by default. I am pretty experienced with root as i have used rooted android phones for more than 4 years now (my first one was a Samsung Galaxy S2) and haven't had any problems until now. I had recently downloaded FaceNiff, one of the sniffing apps for android, and when i pressed start, it would automatically stop. I thought it was maybe a problem of the apps compatibility with my phone, but after researching for a long time, nothing came up so i decided to try another sniffing app. I moved on to DroidSniff, yet, I had the same problem, but this one wouldn't only stop, it would crash. I researched on this app too. Nothing. So I later downloaded one called DroidSheep, and when I started this one, I was lucky that an error was displayed, it was something about Position Independent Executables (PIE), it said "Only Position Independent Executables are supported" or something around those lines. So I decided to research PIE, and I found on the XDA Forums that you could fix this by changing the system/bin/linker file for a custom linker file, which a download link was provided for. I downloaded the file, changed it for the old linker file and tried the apps again. Apparently, I didn't have root access anymore! None of the root apps worked, I thought maybe I had to reboot my phone for my root to come back or for the custom linker to work. So i powered off my phone, turned it on, but instead of turning on, it would say the "Warning unlocked bootloader" thing, and then show a picture of and Android lying down with a caution sign, with the text "No Command" underneath. It's currently in this state, and the phone won't stop repeating this until it runs out of battery. The good thing is I can hold the power and volume down button to enter the fastboot menu, and i can then go into recovery. After this happened, I went to recovery and factory reset my phone, but it still didn't work, so I factory reset it again. It still charges, with a wall plug and with a computer. I think the computer recognises the phone, and I'm pretty sure I have USB Debugging enabled.
To sum this up, I changed the file system/bin/linker for a modified version of it and my phone won't boot up.
Custom linker file: http://forum.xda-developers.com/attachment.php?attachmentid=2821644&d=1403933203
Link to the website where it said you can change the linker files to fix the PIE problem: http://forum.xda-developers.com/goo...x-bypassing-pie-security-check-t2797731/page1
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. For the best available help, I'm going to move your question to your device's Q&A forum. Good luck!
AgusC said:
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option (...)
Click to expand...
Click to collapse
I do not know if finally you fixed the problem with your moto, but you can do a clean install of a stock rom, or maybe cm12/cm12.1...
How to, and link with the rom: http://forum.xda-developers.com/moto-x-2014/general/img-5-0-reteuall-xt1092-lxe22-46-19-t2997745
cyker31 said:
I do not know if finally you fixed the problem with your moto, but you can do a clean install of a stock rom, or maybe cm12/cm12.1...
How to, and link with the rom: http://forum.xda-developers.com/moto-x-2014/general/img-5-0-reteuall-xt1092-lxe22-46-19-t2997745
Click to expand...
Click to collapse
Hey! Thanks a lot for the advice, ill try to do what you said, although im not sure how to use fastboot. Ill tell you if it worked.
Hello,
Yesterday I unlocked and rooted my phone successfully, I then installed the super user app, and after I rebooted my phone it got stuck in a boot loop. It took me 6 hours to finally get it out of the boot loop, couldn't get my device in TWRP (only got in in TWRP mode twice but don't ask me how I did it). But now my phone is back up and running, but I noticed there we're some icons missing, like my calendar, huawei back and some other stuff. Also I can't install Huawei Back Up which I need to recover my backup to my phone. Now I've been trying again all day to fix this, looking all over the internet and digging through this forum for a solution but unfortunately I haven't found a fix.
I was hoping anyone could tell me how to fix this, and guide me a little.
Thanks! :laugh: