Related
As I said, the phone is not currently bricked. I can do a normal boot into the OS and Download Mode, however recovery is a different story.
I believe the issue stems from the latest OTA update to version VS98026A. I had a custom ROM on here before, but the developer stopped support so I went back to stock doing a complete wipe through TWRP, including both caches, system, data, and internal storage. I then flashed the stock Verizon ROM for version 24A, rooted, temp unrooted to take the OTA for VoLTE, restored root, and installed TWRP. I have been unable to boot into recovery AT ALL. I have tried through the TWRP manager app and ADB. Both times I was simply presented with a fastboot screen stating processing commands eternally, I let it sit there for a good 10 minutes to be sure. I also tried different versions of TWRP, but they all either failed entirely and just rebooted normally or gave me fastboot.
I have access to ADB terminal on my PC, the TWRP manager app, fastboot (I know, not ideal), and download mode. I can flash most parts of the system through ADB, with a little help. I have the basics down.
I've got backups of everything from when I had TWRP on here before, even my EFS. Any suggestions, no matter how drastic, are welcome.
UPDATE: I've used fastboot to replace my boot, aboot, laf, and recovery partitions. Now when I enter recovery, I'm presented with the android with the red exclamation triangle, but no recovery options.
Just to try it I put TWRP back on and I still get fastboot.
Starcruiser322 said:
As I said, the phone is not currently bricked. I can do a normal boot into the OS and Download Mode, however recovery is a different story.
I believe the issue stems from the latest OTA update to version VS98026A. I had a custom ROM on here before, but the developer stopped support so I went back to stock doing a complete wipe through TWRP, including both caches, system, data, and internal storage. I then flashed the stock Verizon ROM for version 24A, rooted, temp unrooted to take the OTA for VoLTE, restored root, and installed TWRP. I have been unable to boot into recovery AT ALL. I have tried through the TWRP manager app and ADB. Both times I was simply presented with a fastboot screen stating processing commands eternally, I let it sit there for a good 10 minutes to be sure. I also tried different versions of TWRP, but they all either failed entirely and just rebooted normally or gave me fastboot.
I have access to ADB terminal on my PC, the TWRP manager app, fastboot (I know, not ideal), and download mode. I can flash most parts of the system through ADB, with a little help. I have the basics down.
I've got backups of everything from when I had TWRP on here before, even my EFS. Any suggestions, no matter how drastic, are welcome.
UPDATE: I've used fastboot to replace my boot, aboot, laf, and recovery partitions. Now when I enter recovery, I'm presented with the android with the red exclamation triangle, but no recovery options.
Just to try it I put TWRP back on and I still get fastboot.
Click to expand...
Click to collapse
Was there ever a resolution to this?
I believe I might be having the same issue.
Sent from my LG-VS980
Well, it was sort of resolved for me. If you follow the steps in THIS THREAD, you better hope you have enough battery to last through the process. If you do, great, you'll have your phone back in running order soon enough. A bit of Linux experience helps with this.
After my battery died it refused to come back on, and I brought it to the Verizon store and told them I woke up one day and it wouldn't turn on.
They replaced it under warranty.
I assume other major carriers would do the same.
Is your phone still under warranty? What model and carrier?
After a bit of searching, I did confirm that the 26A update locks the bootloader and implements tighter security policies.
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
mediaman123 said:
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
Click to expand...
Click to collapse
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
jeromechrome1 said:
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
Click to expand...
Click to collapse
Please! Anyone!
by manually do you mean flashing all the separate parts of the stock image separately, system, boot, recovery, cache and so on..........
I don't know what else to do after going through with that process.....
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
I'm a total newb here so take what I tell you with a grain of salt. I had your exact same problem on my Nexus 5. Every single thing you just described is what happened to my N5. And just like your N6...I was able to boot up into recovery (stock and TWRP), I was able to flash all the things manually and even used Wug's NRT. But then whenever I tried to actually boot up the device it could never pass the Google logo....basically EVERYTHING THAT IS HAPPENING TO YOU.
What I did to fix everything? Changed my battery. Sounds stupid and totally irrelevant but that did the trick. When I opened up my phone I noticed my battery had a nasty bulge and realized it was defective. Bought a new one for $25 and have never had any issues ever since. I suggest you look at your battery and see if that is the root of your problem. I have heard of the N6 having some batteries expanding and causing the back covers to pop off...this could be related to your problem.
Like I said I am a newb and thought I'd share my experience in the hopes it solves your problem.
Good luck buddy! :good:
my N6 is actually away getting repaired for the exact issue you described, expanding battery [assumed], and cover coming away from the bezel.....
I believe though that if you keep the device plugged into the wall when trying to boot up with this battery defect it will get through the boot, at least in the beginning anyway....
I believe also that if it was a battery issue the device would power off first, as opposed to just sticking on the Google logo.........
ldkud50 said:
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
Click to expand...
Click to collapse
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
jeromechrome1 said:
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
Click to expand...
Click to collapse
Thats too bad. Maybe the device is hosed. RMA for a new one.
Same thing happened to me. As soon as I updated to the newest version of fastboot on my computer, everything worked...
jeromechrome1 said:
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
Click to expand...
Click to collapse
I know, it's been a long time, but coud you tell me what happened to the phone?
Hello everyone!
I have just recently installed TWRP recovery on my L-09 and attempted to install OpenKirin's RROS from around here. Although the installation seemed to work fine at first, the device was stuck on the roms bootanimation. As such, I did what I would always do in this case, and try to recover my backup that I made through TWRP. Unfortunately though, that dos not boot up either.
Since then I have spent literal hours trying to find a way to make the phone boot , including trying to flash Moonlight and Magic Rainbow to no avail. I tried everything, flashing back to stock recovery, or the inbuilt erecovery or however it is call, nothing works. I have also tried to flash with the dload method, the installation fails with the file I found.
TWRP still seems to work, as does Fastboot mode and everything, so I have a feeling the situation should be salvagable.
Anyone with any better ideas? I have spent sooo long on this and I am on the end of my sanity
Thanks in advance!
Ok, Update: I have found an image that seemed to work with the dload method, but it is still stuck on the "Your device is booting now" screen..
Hello Friends,
Yesterday I was chatting on whatsapp and suddenly my le2 restarts, and then a blue splash screen appears and device keeps on booting,
hence I went to recovery and clear the data, but that also didnt help me,
Then i flash the 13s rom via Flashone 1.9 then also same problem happens, sometimes it went to optimizing apps 3 of 4 and again restarts with blue LED, i were unable to switch it off,
after draining the whole battery I keep mobile to charge but now it is not charging, it only showing Red Solid LED Continuously.
Now I am also Unable to boot into recovery or fastboot mode.
I again flash the stock 13s rom via flashone 1.9 , i got success msg but then also mobile is not booting nor it is charging.
Note: I am on complete stock rom on locked bootloader, never unlocked or rooted, used as come in box.
Please give me a solution on this, I have searched everywhere but not getting any solutions.
Thanks in advance
Try to check your USB cable, most of the time charging issue is due to cable
shubham1358 said:
Try to check your USB cable, most of the time charging issue is due to cable
Click to expand...
Click to collapse
Cable is ok. I have another Le2 and it is charging with that cable very well
I am facing same problem. How you solve this issue? Blue led blinks after flashing any rom and bootloop.
xerol said:
Hello Friends,
Yesterday I was chatting on whatsapp and suddenly my le2 restarts, and then a blue splash screen appears and device keeps on booting,
hence I went to recovery and clear the data, but that also didnt help me,
Then i flash the 13s rom via Flashone 1.9 then also same problem happens, sometimes it went to optimizing apps 3 of 4 and again restarts with blue LED, i were unable to switch it off,
after draining the whole battery I keep mobile to charge but now it is not charging, it only showing Red Solid LED Continuously.
Now I am also Unable to boot into recovery or fastboot mode.
I again flash the stock 13s rom via flashone 1.9 , i got success msg but then also mobile is not booting nor it is charging.
Note: I am on complete stock rom on locked bootloader, never unlocked or rooted, used as come in box.
Please give me a solution on this, I have searched everywhere but not getting any solutions.
Thanks in advance
Click to expand...
Click to collapse
I also have the exact same problem. Phone started rebooting as soon as it booted up. Somehow i managed to unlock the bootloader, but to no avail. Can't seems to find any rom which can boot up. So practically i have a bricked device with trwp. Formatted the system and other partitions with twrp, flashed many roms. Still the result is same. Bootloops.
Hi,
try to to reimage your phone with QFIL from this site:
https://www.techpoison.in/2017/12/how-to-flash-letv-le-2-x526-stock.html
I downloaded everything from there, QFIL, Sparse image and drivers. My phone was bricked, but its working normally now. After you flash the image your phone should charge normally, just try to boot it up. In my case i had issues with baseband, not detected, no sim function and no wifi and phone was restarting each 3-4 minutes, but it was operable. Basedband issues can be solved by hard reseting the phone and updating it to 21s using the local update, just put the 21s stock renamed to update.zip to internal storage and run system update. When you get the error - APK missing, just boot it up again and retry the local update, should work fine the second time, i just deleted the update.zip and put back again and ran the update.
---------- Post added at 03:24 PM ---------- Previous post was at 03:18 PM ----------
Forthe55 said:
I also have the exact same problem. Phone started rebooting as soon as it booted up. Somehow i managed to unlock the bootloader, but to no avail. Can't seems to find any rom which can boot up. So practically i have a bricked device with trwp. Formatted the system and other partitions with twrp, flashed many roms. Still the result is same. Bootloops.
Click to expand...
Click to collapse
Flash the 21s bootloader + modem, one ZIP file, should work fine. Not sure what ROM did you install last time. You can give it a shot with with MIUI 10 - its nougat.
I had similar issues, see my topic, maybe it helps a bit.
https://forum.xda-developers.com/le-2/help/x526-bricked-unknown-baseband-4g-t3838093
Modem + bootloader 21s.
https://drive.google.com/file/d/0B_R...FxTGxlMHM/view
Brother same thing happened to me, a week ago. I cant say about your problem but my problem was due to faulty power button. Actually due to that reason my phone actually kept restarting itself. It showed red light blinking while charging and wasn't able to bypass the optimizing app screen. I also thought it was a software issue but actually it wasn't. I spent about 2 hours figuring out what the actual problem was. The problem was: As we know when power button is hard pressed for about 10-15 seconds it reboots itself.
Although the repair shop guy didn't put new power button but he added a tiny piece of paper in between the power button and body housing to prevent the issue and voila the problem was solved.
delltech1 said:
Hi,
try to to reimage your phone with QFIL from this site:
https://www.techpoison.in/2017/12/how-to-flash-letv-le-2-x526-stock.html
I downloaded everything from there, QFIL, Sparse image and drivers. My phone was bricked, but its working normally now. After you flash the image your phone should charge normally, just try to boot it up. In my case i had issues with baseband, not detected, no sim function and no wifi and phone was restarting each 3-4 minutes, but it was operable. Basedband issues can be solved by hard reseting the phone and updating it to 21s using the local update, just put the 21s stock renamed to update.zip to internal storage and run system update. When you get the error - APK missing, just boot it up again and retry the local update, should work fine the second time, i just deleted the update.zip and put back again and ran the update.
---------- Post added at 03:24 PM ---------- Previous post was at 03:18 PM ----------
Flash the 21s bootloader + modem, one ZIP file, should work fine. Not sure what ROM did you install last time. You can give it a shot with with MIUI 10 - its nougat.
I had similar issues, see my topic, maybe it helps a bit.
https://forum.xda-developers.com/le-2/help/x526-bricked-unknown-baseband-4g-t3838093
Modem + bootloader 21s.
https://drive.google.com/file/d/0B_R...FxTGxlMHM/view
Click to expand...
Click to collapse
Hi, Thanks. I actually did that first, flashing through qfil the same rom. it helped me to go to settings after umpteen attempts to go past language selection screen, and i was just able to oem unlock and enable usb debugging (actually after a 2nd partial failed flashing). the phone kept freezing within seconds of booting up. Now After i unlocked the bootloader and installing twrp and flashing many roms thru twrp, i am still having the same problem of booting up and freezing at start-up. cant flash again through qfil, as i will again loose the unlocked bootloader and twrp.
At least , now i can try different roms to see which can unbrick it. last one used was the twrp flashable rom based on eui (small eui by aurel) but it also freezes on language selection screen or beyond.
I am running out of ideas, lets see.
2nd partial failed flashing? any issues during the flash process? i had some issues when i used usb 3.0, 2.0 worked fine for me. If you have also charging issues stay in twrp and let the phone charge properly, its slower but should work fine. You can try to flash the 21s bootloader with modem, maybe it will boot properly. But try it only when you are able to enter the fastboot mode, longpress volume down and power for 10-15 seconds, if that is working you should be able to flash twrp via fastboot and you can experiment a bit. Try to find the chinesse twrp 3.0.2.0 and try to flash the stock 21s version. Should be also an image file, in standard twrp go to install - image, after selecting the image file click on recovery and install, after installation go back, reboot, recovery. Copy 21s to storage, wipe data, cache, dalvik and flash it, chinesse twrp will skip version check and will let you install the stock image, after install reboot but click on do not replace recovery button - this will keep the chinesse twrp installed.
If nothing helps it can be only a HW failure, maybe the power button, try usb 2.0 port during the flash process, i had issues with 3.0 on my pc, if that doesnt help.try a different cable, no more suggestions, sorry.
delltech1 said:
2nd partial failed flashing? any issues during the flash process? i had some issues when i used usb 3.0, 2.0 worked fine for me. If you have also charging issues stay in twrp and let the phone charge properly, its slower but should work fine. You can try to flash the 21s bootloader with modem, maybe it will boot properly. But try it only when you are able to enter the fastboot mode, longpress volume down and power for 10-15 seconds, if that is working you should be able to flash twrp via fastboot and you can experiment a bit. Try to find the chinesse twrp 3.0.2.0 and try to flash the stock 21s version. Should be also an image file, in standard twrp go to install - image, after selecting the image file click on recovery and install, after installation go back, reboot, recovery. Copy 21s to storage, wipe data, cache, dalvik and flash it, chinesse twrp will skip version check and will let you install the stock image, after install reboot but click on do not replace recovery button - this will keep the chinesse twrp installed.
Click to expand...
Click to collapse
My phone has been flashed multiple times by qfil method. And always it hangs at initial setup (so it boots up, but hangs at language selection or further up screens, before setup can complete and launcher could be loaded).
While trying to flash again with qfil once it stopped at 25 percent (because the battery went dead). Charged the battery and booted up the phone, and i was surprised it booted up. After 2-3 attempts i was able to reach the launcher screen and immediately enabled developer options and oem unlock / usb debugging. Only had few split seconds to do this and the phone froze again. After that i installed twrp and hence treying different roms. Most fail at setup.
Just tried MIUI 9PRO ROM. It also froze at setup multiple times, but once i was able to complete the setup and miui launcher is up , but it reboots or turn off the phone just after that. So cant do anything with the phone. Unsure of whether a newer bootloader will help in these freezing issues as i have been able to boot up at least in some roms only if for few seconds. Will try to tinker the settings of miui rom (if the phone let me do it before freezing/hanging). Lets see. Thanks for suggestions. More suggestions welcome, because i am still unsure weather this is a software or hardware related problem. I am guessing that it may have something to do with Google security as earlier i was getting msg that phone has been wrongly resetted and needs to verify with Google (but i couldn't get a chance to use the same account, as phone kept freezing at setup).
Did you fully charge the battery, if not let it fully charge in twrp. Flashing the roms in twrp works everytime or do you see any errors? Before you flash anything disconnect the usb cable.
---------- Post added at 09:54 PM ---------- Previous post was at 09:47 PM ----------
Try to flash the 21s bootloarder with modem, one zip using twrp. Go to fastboot mode and wipe modems. fastboot erase modem1st fastboot erase modem2st. Put the phone to flash mode and reimage with qfil. Before you do it write down both imeis, you can find them also on the original package on the backside. Also try to remove all sim cards from the phone and try a different cable. If nothing helps, hw issue, maybe the power button mention earlier in this thread.
After reflash skip everything at setup and reset phone to factory defaults. OEM is already unlocked, you dont have to do it again.
I have charged the phone fully before any flashing after that error. I can flash the phone through twrp without any error msg. The phone boots up most of times in various roms but hangs at or after the initial setup screens show (like language selection etc). Flashed the modem+bootloader, success, but it showed bootloader version as 20s (not 21s). Tried the commands u mentioned to erase modems, it say error failed, no such partition found. I had checked the partitions with parted and 56 partitions are there including the modemst1 & 2.
Now re flashed via qfil , did as advised but again the same problem of hanging / freezing at or after initialization screens of various roms.
Forthe55 said:
I have charged the phone fully before any flashing after that error. I can flash the phone through twrp without any error msg. The phone boots up most of times in various roms but hangs at or after the initial setup screens show (like language selection etc). Flashed the modem+bootloader, success, but it showed bootloader version as 20s (not 21s). Tried the commands u mentioned to erase modems, it say error failed, no such partition found. I had checked the partitions with parted and 56 partitions are there including the modemst1 & 2.
Now re flashed via qfil , did as advised but again the same problem of hanging / freezing at or after initialization screens of various roms.
Click to expand...
Click to collapse
Yeah sorry i screwed the command its fastboot erase modest1 modemst2, my bad.
Just now i was able to complete the initialization (setup screen) of sparse image india rom. I can reach the launcher and settings for few seconds before the device freezes or reboots.
So the same problem , with which i started, the only good thing is that i have been able to set oem unlock to on, so that i can flash trwp and various roms (but all fail with the same freezing issues)
Forthe55 said:
Just now i was able to complete the initialization (setup screen) of sparse image india rom. I can reach the launcher and settings for few seconds before the device freezes or reboots.
So the same problem , with which i started, the only good thing is that i have been able to set oem unlock to on, so that i can flash trwp and various roms (but all fail with the same freezing issues)
Click to expand...
Click to collapse
So you erased modems and reflashed with qfil right? If so i assume its a HW problem. Try the fix with the power button, i ran out of ideas
Last thing which can help maybe: https://www.youtube.com/watch?v=LH3VOIlLfvo&t=135s
Download 21s stock image + the chinesse twrp, links should be under the video, i think so, or look somewhere in the forum for new links. Try to reflash the 21s, some people reported that freezing issues were gone after installing the latest EUI. Basically you can do the same after QFIL reflash but you need enough time to copy the ZIP file as UPDATE.ZIP to the internal storage and run the local update via setting, system update and local update, i hope that TWRP will work for you, just follow the video tutorial.
delltech1 said:
Last thing which can help maybe: https://www.youtube.com/watch?v=LH3VOIlLfvo&t=135s
Download 21s stock image + the chinesse twrp, links should be under the video, i think so, or look somewhere in the forum for new links. Try to reflash the 21s, some people reported that freezing issues were gone after installing the latest EUI. Basically you can do the same after QFIL reflash but you need enough time to copy the ZIP file as UPDATE.ZIP to the internal storage and run the local update via setting, system update and local update, i hope that TWRP will work for you, just follow the video tutorial.
Click to expand...
Click to collapse
Did that also, the same problem. The phone freezes after the os is booted. I was wondering what is that isnt touched by flashing ( in download mode or fastboot mode or through twrp). I may need to tinker that. The roms are all fine in the sense they all stop at the same points. Something in the phones partition, which isnt touched by flashing? (There must be, as i flashed with qfil, the oem unlock remains, the bootloader didn't lock, and it remains unaffected by re-imaging)
Try this, maybe it helps:
https://forum.xda-developers.com/le-2/help/issues-installing-twrp-rom-le-s3-x522-t3618662/page2
Hello everyone, how do you do?
I've got this phone that was running perfectly the stock rom, but I have that addiction to customize every phone I land my hands into (I guess some of you either haha).
But
This time something horrible happened, and I just can't back this phone to work. I'll tell what did I've done and I'm hopping you to help me (just paid a lot to fix the broken screen, don't want to buy a new board...)
Here we go: yesterday, several times I've tried to unlock the phone, and figure out that the fastboot command to do that have changed to fastboot oem unlock (at least in this phone), and had no need to copy that code into Motorola's page. After unlock, tried to install TWRP Recovery, several times, and finnaly got one that worked here. Okay. Ready to go. Also had difficulty to find a ROM that is compatible with this phone (I wanted some with Android 9, or 8.1, at least). I was capable to install the Lineage OS 15 Unnoficial for Nicklaus, but got stuck in Lineage OS Logo Screen. Fine. Downloaded the Lineage OS 14 Unnoficial (Android 7.1), flashed, and everything went fine! The ROM was installed, configured, but... My phone has the OnScreen Buttons for Navigation... And this ROM doesn't appear to get this to work... Every time I went to settings page and tried to enable this feature, the Settings Application stucks and phone restarts. So, at this point, I thought that the ROM was with some code problem, whatever, decided to download another. And (that was a HUGE MISTAKE). Downloaded the DotOS ROM here.
After flash, the ROM loaded up fine. Settings, ok, system, ok. But, the same problem with the Navigation Buttons. What? Again? Yes. Tried to enable via settings, but I realized that some configurations of Lineage OS installation is still there - forgot to wipe data before flashing ROM... But at this time (I guess it was 2AM) I had no patience to reboot, wipe, boot, configure, and decided to factory reset using the option in Settings menu. The DotOS shows me a logo saying "Wiping data". The phone reboots. And reboots. And reboots. But, the TWRP stills working, and tried many, many times to flash all sort of ROMs with no success at all.
I was going insane, you know, WHY I CAN'T FLASH THE ROM I'VE JUST FLASHED MINUTES AGO?? Got a clue: somehow when wiping data, DotOS bugged my /data partition (in TWRP, when wiping data, got an error in this partition, and cant fix it using TWRP fix menu). Tried a lot of tutorials over the internet to fix that partition, with no success. And, unfortunately, at that point my /system and /cache partition got broken too.
But, I had my secret weapon: THE STOCK ROM. Yes. Everytime all went wrong, is quite simple: just install the factory's ROM, and you will be fine. Right? Wrong. Really don't know why, I was not able to flash some images of the ROM (boot, recovery, system also). Thought I've downloaded the wrong Stock ROM. Tried another. And another. No success. What the hell? At this point my mind was not lucid enough, and decided to STUPIDLY FORMAT PARTITIONS BY MY SELF. Reboot Bootloader. Connect Cable. Fastboot.
fastboot devices -> OK
fastboot erase boot -> OK
fastboot erase userdata -> OK
fastboot erase system -> OK
That's it! Fixed! Now is just reboot, and... Reboot. Reboot. Reboot. Reboot.
Ok, Vol Down + Power. Nothing. Ok, Vol Up + Power. Nothing. Ok, Vol Up + Vol Down + Power, Vol Power + Dow Up, Fingerprint + Screen + Two Punches + Power. Nothing.
Stuck in boot loop. My worse nightmare. Thinked: okay, lets remove the battery, and... Remember I've just fixed the broken screen? Yeah. Out of lucky, the assistance tried THREE TIMES to change my screen, because the screen's provider at first provided a screen with ghost touches, at second a screen that had light glitches. At third, a correct screen. Don't want to loose my warranty, you know. If this third screen has some problem either? The assistance put that tag over the screw, you know. Can't take my battery off. But I really don't know if removing the battery will really help, because I've erased my boot partition. I hate me. My wife too (but she hated before). Now, got this tutorial: Ultimate Guide for [Bootloop Recovery] Noob Friendly, that is a little outdated, and can't help me. But gave me some hope: So, my phone isn't bricked yet! I can fix it!
But I really don't know how.
I hope someone helps me, and that this topic can be useful for any one who got stuck in Boot Loop from here to eternity.
Regards,
Fernando Garcia (sorry for my bad english, I only speak JavaScript)
fernandocg30 said:
Hello everyone, how do you do?
I've got this phone that was running perfectly the stock rom, but I have that addiction to customize every phone I land my hands into (I guess some of you either haha).
But
This time something horrible happened, and I just can't back this phone to work. I'll tell what did I've done and I'm hopping you to help me (just paid a lot to fix the broken screen, don't want to buy a new board...)
Here we go: yesterday, several times I've tried to unlock the phone, and figure out that the fastboot command to do that have changed to fastboot oem unlock (at least in this phone), and had no need to copy that code into Motorola's page. After unlock, tried to install TWRP Recovery, several times, and finnaly got one that worked here. Okay. Ready to go. Also had difficulty to find a ROM that is compatible with this phone (I wanted some with Android 9, or 8.1, at least). I was capable to install the Lineage OS 15 Unnoficial for Nicklaus, but got stuck in Lineage OS Logo Screen. Fine. Downloaded the Lineage OS 14 Unnoficial (Android 7.1), flashed, and everything went fine! The ROM was installed, configured, but... My phone has the OnScreen Buttons for Navigation... And this ROM doesn't appear to get this to work... Every time I went to settings page and tried to enable this feature, the Settings Application stucks and phone restarts. So, at this point, I thought that the ROM was with some code problem, whatever, decided to download another. And (that was a HUGE MISTAKE). Downloaded the DotOS ROM here.
After flash, the ROM loaded up fine. Settings, ok, system, ok. But, the same problem with the Navigation Buttons. What? Again? Yes. Tried to enable via settings, but I realized that some configurations of Lineage OS installation is still there - forgot to wipe data before flashing ROM... But at this time (I guess it was 2AM) I had no patience to reboot, wipe, boot, configure, and decided to factory reset using the option in Settings menu. The DotOS shows me a logo saying "Wiping data". The phone reboots. And reboots. And reboots. But, the TWRP stills working, and tried many, many times to flash all sort of ROMs with no success at all.
I was going insane, you know, WHY I CAN'T FLASH THE ROM I'VE JUST FLASHED MINUTES AGO?? Got a clue: somehow when wiping data, DotOS bugged my /data partition (in TWRP, when wiping data, got an error in this partition, and cant fix it using TWRP fix menu). Tried a lot of tutorials over the internet to fix that partition, with no success. And, unfortunately, at that point my /system and /cache partition got broken too.
But, I had my secret weapon: THE STOCK ROM. Yes. Everytime all went wrong, is quite simple: just install the factory's ROM, and you will be fine. Right? Wrong. Really don't know why, I was not able to flash some images of the ROM (boot, recovery, system also). Thought I've downloaded the wrong Stock ROM. Tried another. And another. No success. What the hell? At this point my mind was not lucid enough, and decided to STUPIDLY FORMAT PARTITIONS BY MY SELF. Reboot Bootloader. Connect Cable. Fastboot.
fastboot devices -> OK
fastboot erase boot -> OK
fastboot erase userdata -> OK
fastboot erase system -> OK
That's it! Fixed! Now is just reboot, and... Reboot. Reboot. Reboot. Reboot.
Ok, Vol Down + Power. Nothing. Ok, Vol Up + Power. Nothing. Ok, Vol Up + Vol Down + Power, Vol Power + Dow Up, Fingerprint + Screen + Two Punches + Power. Nothing.
Stuck in boot loop. My worse nightmare. Thinked: okay, lets remove the battery, and... Remember I've just fixed the broken screen? Yeah. Out of lucky, the assistance tried THREE TIMES to change my screen, because the screen's provider at first provided a screen with ghost touches, at second a screen that had light glitches. At third, a correct screen. Don't want to loose my warranty, you know. If this third screen has some problem either? The assistance put that tag over the screw, you know. Can't take my battery off. But I really don't know if removing the battery will really help, because I've erased my boot partition. I hate me. My wife too (but she hated before). Now, got this tutorial: Ultimate Guide for [Bootloop Recovery] Noob Friendly, that is a little outdated, and can't help me. But gave me some hope: So, my phone isn't bricked yet! I can fix it!
But I really don't know how.
I hope someone helps me, and that this topic can be useful for any one who got stuck in Boot Loop from here to eternity.
Regards,
Fernando Garcia (sorry for my bad english, I only speak JavaScript)
Click to expand...
Click to collapse
Hey, download the stock rom for your from here:
https://motostockrom.com/motorola-moto-e4-plus-xt1773
And follow this process to flash the rom on to your phone:https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Warning for this phone flashing process:
In SP flash tool, "do not" select 'format all+ download'(the phone will be bricked). Only select 'Download only'.
Secondly deselect preloader after adding scatter file(flashing it will also brick the device).
This all warnings are already given in the flash guide, i just want you to give proper attention while doing it.