Sooooooo..... I have a problem. I am using AOSPK, and everything went very well, I was very happy with my new custom ROM. The Equalizer App kept crashing, so I installed Viper4android. That didn't really work, so I tried to fix it by installing APKs, Magisk Modules, which all resulted in the driver not being enabled. But then I stumbled across this thread here on XDA and there was a Module for Magisk I could flash which supposedly fixed the Error, but of course, that didn't work. As usual, I removed it with Magisk and rebooted it.
Now. The thing is, I am pretty much stuck on an endless Bootloop. I already had a Bootloop once, but those always led me back to TWRP. To get out of the AOSPK Kraken loading GIF, I had to let it like that overnight and let it drain its battery. Now, this morning I plugged the Phone in and tried again, but it didn't work. I let the battery drain itself again, but It only took like 10 minutes as it was plugged in for a short time. I only now found out I can press on Power + VolDown to force reboot.
I would REALLY love some help here, how do I get out of this mess? Do I plug into a PC and try to boot to TWRP? What do I do next? Please explain to me step by step, I am really in a sticky situation right now.
UPDATE: I can get into TWRP, not what? I wiped chache and dalvik, did nothing. What now?
Hi. I am also using Kraken rom. Check out this post if you want.
[GUIDE] Go back to stock - Galaxy S10 series
Hi 🙂 So you have bricked your Samsung S10 series handset and you need it fixed. Sometimes we try to modify our phones and it goes wrong, fret not it can be restored. DOWNLOADS Frija Microsoft Visual C++ 2008 Microsoft Visual C++ 2010 Phone...
forum.xda-developers.com
puul said:
Sooooooo..... I have a problem. I am using AOSPK, and everything went very well, I was very happy with my new custom ROM. The Equalizer App kept crashing, so I installed Viper4android. That didn't really work, so I tried to fix it by installing APKs, Magisk Modules, which all resulted in the driver not being enabled. But then I stumbled across this thread here on XDA and there was a Module for Magisk I could flash which supposedly fixed the Error, but of course, that didn't work. As usual, I removed it with Magisk and rebooted it.
Now. The thing is, I am pretty much stuck on an endless Bootloop. I already had a Bootloop once, but those always led me back to TWRP. To get out of the AOSPK Kraken loading GIF, I had to let it like that overnight and let it drain its battery. Now, this morning I plugged the Phone in and tried again, but it didn't work. I let the battery drain itself again, but It only took like 10 minutes as it was plugged in for a short time. I only now found out I can press on Power + VolDown to force reboot.
I would REALLY love some help here, how do I get out of this mess? Do I plug into a PC and try to boot to TWRP? What do I do next? Please explain to me step by step, I am really in a sticky situation right now.
UPDATE: I can get into TWRP, not what? I wiped chache and dalvik, did nothing. What now?
Click to expand...
Click to collapse
Hi, don't know if it's too late but I did have the same problem before and all I did was boot into TWRP. When you wipe make sure to check everything from Dalvil to Internal Storage and format data as well. Also if you are going to install Magisk try to do it after your phone boot into os otherwise it will stuck in bootloop again. I hope that's can help!
Related
Last night, I downloaded InnovationsOS v3 from the Nexus One Android Development forum. Prior to this I was using FRF50, and I have a rooted Tmobile Nexus One. I wiped the phone back to factory settings and also wiped the Dalvik cache (as I've been told in the past). Flashing went just fine and within a few minutes I had InnovationsOS after a reboot. (Let me just say, with this one minor exception, InnovationsOS looks incredible and I loved every minute of it).
After install, I set up AdFree which removes ads. I decided to do a quick reboot. The reboot wasn't so quick, and it stuck on the startup screen (the Nexus One/Google logo with the unlocked symbol below) for about 3 minutes. I didn't think this was good, so I tried a battery pull hoping for a normal reboot. Instead, what I got was the android falling out of the box. I tried a battery pull again and attempted to enter recovery, which worked. I wiped, and reloaded FRF50, and rebooted. I got the android and the box image, which wouldn't let me even boot into recovery anymore after several battery pulls. After a couple minutes of being completely stumped (and scared lifeless) I let the phone sit, and somehow it booted into recovery, where I wiped (again) and flashed InnovationsOS (again). After it loaded, it rebooted, and it's been working great since then, with the exception of one minor screen/keyboard bug...I press S, and get Z, or I press delete, and I get enter, etc. Plus hitting OK or Cancel on dialog boxes is impossible and need to use the trackball.
So, I would like to reboot to fix this problem and want to know what will happen, and I want to know what I did wrong above. I know all this sounds completely noob for this forum but I'm willing to learn, which is why I've been experimenting with rooting and flashing roms.
Thanks a lot, any help is appreciated.
My sincerest apologies if this has been discussed elsewhere, but I've searched high and low in Google and XDA without result.
I recently rooted my P3 and then flashed CM10. Took me a few goes (first time 3G wasn't working etc.), but each time I factory reset, wiped cache and dalvik cache before and after flashing. I eventually got it working just fine, except for the battery not displaying properly. It always said it was charging, even when it wasn't, and it wouldn't charge to 100%, instead stopping at 99%. I used the battery calibration mod, and tried to wipe the battery stats via CWM recovery, but to no avail.
Other than that, and the auto rotation flipping to the opposite side you turn (I understand this is a known bug), everything was running smoothly so I decided to do a backup via CWM recovery. Once everything was completed I booted back up. It all was working as it had before, until I tried to power down. The screen went black, but shortly the Samsung Galaxy splash screen came on and it booted up again. I tried wiping the cache and dalvik cache, wiping battery stats, but it still will not stay powered down. The only exception is when I have it plugged in and charging, then it will stay on the battery charging animation instead of rebooting.
Any help would be much appreciated. I really don't want to have to revert to base CWM after tasting the awesomeness of CM10!
Xanthippus said:
My sincerest apologies if this has been discussed elsewhere, but I've searched high and low in Google and XDA without result.
I recently rooted my P3 and then flashed CM10. Took me a few goes (first time 3G wasn't working etc.), but each time I factory reset, wiped cache and dalvik cache before and after flashing. I eventually got it working just fine, except for the battery not displaying properly. It always said it was charging, even when it wasn't, and it wouldn't charge to 100%, instead stopping at 99%. I used the battery calibration mod, and tried to wipe the battery stats via CWM recovery, but to no avail.
Other than that, and the auto rotation flipping to the opposite side you turn (I understand this is a known bug), everything was running smoothly so I decided to do a backup via CWM recovery. Once everything was completed I booted back up. It all was working as it had before, until I tried to power down. The screen went black, but shortly the Samsung Galaxy splash screen came on and it booted up again. I tried wiping the cache and dalvik cache, wiping battery stats, but it still will not stay powered down. The only exception is when I have it plugged in and charging, then it will stay on the battery charging animation instead of rebooting.
Any help would be much appreciated. I really don't want to have to revert to base CWM after tasting the awesomeness of CM10!
Click to expand...
Click to collapse
Which version are you using? It was a known bug in an older ROM, which should have been fixed in the newer ones.
Using the 20120816 version that I got from the link in this thread: http://forum.xda-developers.com/showthread.php?t=1803593
I've also had this problem for awhile, with several different ROM's.
Does fastboot work for you? Cause it doesn't for me, but not sure if related.
Xanthippus said:
My sincerest apologies if this has been discussed elsewhere, but I've searched high and low in Google and XDA without result.
I recently rooted my P3 and then flashed CM10. Took me a few goes (first time 3G wasn't working etc.), but each time I factory reset, wiped cache and dalvik cache before and after flashing. I eventually got it working just fine, except for the battery not displaying properly. It always said it was charging, even when it wasn't, and it wouldn't charge to 100%, instead stopping at 99%. I used the battery calibration mod, and tried to wipe the battery stats via CWM recovery, but to no avail.
Other than that, and the auto rotation flipping to the opposite side you turn (I understand this is a known bug), everything was running smoothly so I decided to do a backup via CWM recovery. Once everything was completed I booted back up. It all was working as it had before, until I tried to power down. The screen went black, but shortly the Samsung Galaxy splash screen came on and it booted up again. I tried wiping the cache and dalvik cache, wiping battery stats, but it still will not stay powered down. The only exception is when I have it plugged in and charging, then it will stay on the battery charging animation instead of rebooting.
Any help would be much appreciated. I really don't want to have to revert to base CWM after tasting the awesomeness of CM10!
Click to expand...
Click to collapse
Are you using the correct recovery? Not sure that you would be able to get as far as you if it were wrong but ...
I caused myself heartache at some point as a result of using the wrong recovery. It gave my weird results too. I am other 16 Aug ROM and I find it pretty damn good.
Here is the right one
http://droidbasement.com/galaxy/roms/cm10/p3/recovery.tar.md5
GaryWS said:
Are you using the correct recovery? Not sure that you would be able to get as far as you if it were wrong but ...
I caused myself heartache at some point as a result of using the wrong recovery. It gave my weird results too. I am other 16 Aug ROM and I find it pretty damn good.
Here is the right one
Click to expand...
Click to collapse
I got the recovery from the same thread I linked above, so pretty sure it was the right one. Just to be sure I downloaded and flashed the one you linked with Odin, but it's made no difference. However, I have (finally) had success in getting the battery to charge to 100%. I kept wiping the battery stats every time I booted up, and powered it down while plugged in and left it on charge when I wasn't using it. After a couple of days (with it on and off charge) it finally said it was fully charged when I powered it on. I have used the battery calibration app with it at 100%, so hopefully it shall begin indicating properly, although it still says it's charging all the time, and the charging animation when it is powered down does not indicate its actual charge level.
As for it not powering down when it's not plugged in... I am still new to rooting and ROMs, but would it be of help if someone who has no problems powering down uploaded their kernel and I flashed that?
Xanthippus said:
As for it not powering down when it's not plugged in... I am still new to rooting and ROMs, but would it be of help if someone who has no problems powering down uploaded their kernel and I flashed that?
Click to expand...
Click to collapse
Re-download the lastest ROM and flash it; the latest ROM does not have that problem.
pruano said:
Re-download the lastest ROM and flash it; the latest ROM does not have that problem.
Click to expand...
Click to collapse
Where would I get that ROM from? The latest one from the link above at the Droid basement is the 16th August version I already have.
Xanthippus said:
Where would I get that ROM from? The latest one from the link above at the Droid basement is the 16th August version I already have.
Click to expand...
Click to collapse
I would recommend you re-download and re-flash it, since others (myself included) have no such problem with that version.
Didn't work. Redownloaded, reflashed, same problem. I even tried to unroot it so that I could flash it all again fresh, but somewhere along the way something has gone wrong. Odin is not working anymore. I can transfer files to and from my tablet, the computer still recognises it when plugged in, and Odin recognises the USB connection too, but if I try to flash something with it, it always says it is unable to open the COM port.
Tried this many different ways, with different roms, nothing seemed to work. Finally, tried AOKP milestone 6 (based on CM9) and it works perfectly. Go figure...
So since I didn't read anything of xposed being "BAD" for the new CM beta, i figured i'd give it a shot.
The current gist is this:
Powers on, can't get into TWRP, if I get into the Download Mode and go to "Send_Command.exe \\.\COM4" and do "#id" it just comes back with "#" or it may take a long time, then it'll just come back with "#". Fastboot devices, shows nothing. ADB Devices same thing. I'd love to do a HardReset, or anything that could be done, but the only button config that works is Pressing Up when plugging the phone in.
Any ideas?
Yes I've seen others are having bootloops, noone seems to be having them due to what I've done (xposed + CM).
UPDATE: Problem solved. http://forum.xda-developers.com/showpost.php?p=63674157&postcount=3
Got a bit further thanks (i'll probably regret that word) to the LG Flash Tool.
Followed the instructions, flashed the KDZ, then I guess the flash tool error'd out because the Download Mode still showed 0% but the tool had a **** ton of ????? ??????
Needless to say, TWRP is booting up now!....but "unable to mount '/system'.
Attempted the H81110N Bootstack and Image, but that didn't work. due to the /system.
Retrying again with the LGTool, this time choosing English -_-
Looks like im at 52%, that error message i received i guess should have ben ignored.
\
Edit: wasn't looking good with LGTool crashing. but I've successfully gotten the phone back to stock it looks like. Just going through some reboots. I did get a glimpse of the LG setup screen
So I've had this issue on three separate Pixel 4 XL phones now and I'm pretty sure this is due to my error somehow.
My issue is after the phone passes the Google logo, a black screen pops up with the status bar flashing on and off, and occasionally the back button like this: https://imgur.com/iRzD1Jk
I've installed Magisk and EdXposed to use GravityBox and FingerFace, however I haven't done much more than that.
Flashing the factory image over while retaining data does not fix it, although I'm not sure why.
Factory resetting seems to fix it for a short time, but it seems to always come back, even if I don't install EdXposed.
Safe mode does not help.
I had also recently tried updating by flashing the February image over the January (without wiping data), and that seemed to let it boot. But unfortunately I decided to continue with the exchange as I had requested one before the update was released.
Does anyone have any similar experiences or any ideas for me to try?
Finally I found someone with the same bug that happened to me 2 times. I can't understand why this happens.
The first time happened when I rebooted my phone when dark mode was active, but looks like it happens randomly. I got that in november and then 2 days ago, without an apparent reason.
Looks like some UI related crash/bug, but I really can't undestrand what's causing that. Removing root/mods with a dirty flash of the rom doesn't fix it, only wiping.
Hope someone can point out a way to fix this really annoying bug, or a way to prevent it. It's really frustrating.
Have you tried uninstalling magisk then, if necessary, flashing system images? Fastboot boot the modified boot.img from my boot recovery thread that removes magisk. I believe it is due to a bad or incompatible flash as I've gotten this same thing before.
DarkusRattus said:
So I've had this issue on three separate Pixel 4 XL phones now and I'm pretty sure this is due to my error somehow.
My issue is after the phone passes the Google logo, a black screen pops up with the status bar flashing on and off, and occasionally the back button like this: https://imgur.com/iRzD1Jk
I've installed Magisk and EdXposed to use GravityBox and FingerFace, however I haven't done much more than that.
Flashing the factory image over while retaining data does not fix it, although I'm not sure why.
Factory resetting seems to fix it for a short time, but it seems to always come back, even if I don't install EdXposed.
Safe mode does not help.
I had also recently tried updating by flashing the February image over the January (without wiping data), and that seemed to let it boot. But unfortunately I decided to continue with the exchange as I had requested one before the update was released.
Does anyone have any similar experiences or any ideas for me to try?
Click to expand...
Click to collapse
This happened to me too, I originally thought if was the Rom however dirty flashing the Rom again didn't fix it nor did dirty flashing stock image
What I do know is, this happened to me as soon as forced stopped gms services and removed GMS dose from magisk. As soon as I rebooted, this happened
Tulsadiver said:
Have you tried uninstalling magisk then, if necessary, flashing system images? Fastboot boot the modified boot.img from my boot recovery thread that removes magisk. I believe it is due to a bad or incompatible flash as I've gotten this same thing before.
Click to expand...
Click to collapse
It's kinda strange because I didn't touch anything for some days, and after a normal reboot this happened.
I tried restoring the stock boot.img from fastboot -> same issue
Reflash entire factory image without the "-w" so without wiping -> same issue
Even reboot in safe mode -> same issue
I don't think it's magisk fault because happened randomly the last 2 times, but I'll give your method a try if this happens again
It sure is giving off system UI crashing vibes. I definitely agree that this is an issue caused by something you did, not something inherent to the Pixel 4. Like suggested already, I would uninstall magisk as a next logical step since you've tried many of the other things I would have suggested. I wholeheartedly agree with Tulsa that this is a bad flash. Since you didn't wipe userdata when you flashed the factory image, the bad flash is still present so it's pretty safe to assume that you have a bad module installed or a bad combo of modules that don't like working together.
Tulsadiver said:
Have you tried uninstalling magisk then, if necessary, flashing system images? Fastboot boot the modified boot.img from my boot recovery thread that removes magisk. I believe it is due to a bad or incompatible flash as I've gotten this same thing before.
Click to expand...
Click to collapse
It was the last link on this thread correct? https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
I tried booting that and all it did was try to boot, restart before it finished, and boot back into the flashing UI.
Was this the correct image?
DarkusRattus said:
It was the last link on this thread correct? https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
I tried booting that and all it did was try to boot, restart before it finished, and boot back into the flashing UI.
Was this the correct image?
Click to expand...
Click to collapse
Yes. What is the flashing UI? I just ran it on my Pixel 2. It ran just fine. Yes it reboots during flashing as the script reads "rm-rf /data/adb/* && reboot" After it reboots, click on magisk manager. It should say you need to install additional files. It will then your phone will reboot again. Modules should be gone.
Tulsadiver said:
Yes. What is the flashing UI? I just ran it on my Pixel 2. It ran just fine. Yes it reboots during flashing as the script reads "rm-rf /data/adb/* && reboot" After it reboots, click on magisk manager. It should say you need to install additional files. It will then your phone will reboot again. Modules should be gone.
Click to expand...
Click to collapse
Check the link in my first post. That's what it looks like when it boots. I cannot get through that screen. It stays that way even if I dirty flash the factory image.
DarkusRattus said:
Check the link in my first post. That's what it looks like when it boots. I cannot get through that screen. It stays that way even if I dirty flash the factory image.
Click to expand...
Click to collapse
Is your phone rooted still? You must have root. Flash the magisk_patched.img again to make sure and try again.
You could also try the other boot image that installs a .disable-cache file.
Tulsadiver said:
Is your phone rooted still? You must have root. Flash the magisk_patched.img again to make sure and try again.
You could also try the other boot image that installs a .disable-cache file.
Click to expand...
Click to collapse
I flashed both of your images as well as my original generated magisk_patched, and the original boot.img from the factory image. They all lead to the same booting issue.
I can tell when the Magisk modules are disabled because the modules that affect the clock position in the header returns it to its original position from center to left. But that's the only thing that changes. I can reflash the whole factory image and the issue still persists.
DarkusRattus said:
I flashed both of your images as well as my original generated magisk_patched, and the original boot.img from the factory image. They all lead to the same booting issue.
I can tell when the Magisk modules are disabled because the modules that affect the clock position in the header returns it to its original position from center to left. But that's the only thing that changes. I can reflash the whole factory image and the issue still persists.
Click to expand...
Click to collapse
What order did you flash them in?
1. Flash magisk_patched.img then reboot.
2. Boot back to fastboot and boot one of my boot images.
If you have done this and still have a problem you will probably have to do a factory reset.
Tulsadiver said:
What order did you flash them in?
1. Flash magisk_patched.img then reboot.
2. Boot back to fastboot and boot one of my boot images.
If you have done this and still have a problem you will probably have to do a factory reset.
Click to expand...
Click to collapse
I appreciate you trying to help me.
I did this with the same results.
I am totally fine with doing another factory reset. My issue is that I've been having this issue across three different phones, and I believe the issue has happened a total of about 10 times, the longest time I've gone without anything happening appears to have been almost two months. I'm trying to understand what I'm doing that is leading to this problem more than anything.
When I install Magisk, I believe everything installs to partition B.
The issue is not caused by EdXposed because it has happened some times without it being installed.
I believe the modules I've used each time are:
-IOS 12 Emojis
-Systemless Hosts
-Call Recorder - SKVALEX
I believe I was also using FDE.AI, but I don't think that would cause this until after I pass the unlock screen, which I can't.
I've been using ElementalX as the kernel.
The issue comes up randomly, and sometimes I can reboot several days without anything happening. I can't see anything I'm doing between the final successful reboot and the issue coming up where this starts to happen that could be causing this.
The ONLY time this seemed to have been fixed was when I updated to the February factory image. However I already had a replacement phone coming, so I decided to still send the old one in.
DarkusRattus said:
I appreciate you trying to help me.
I did this with the same results.
I am totally fine with doing another factory reset. My issue is that I've been having this issue across three different phones, and I believe the issue has happened a total of about 10 times, the longest time I've gone without anything happening appears to have been almost two months. I'm trying to understand what I'm doing that is leading to this problem more than anything.
When I install Magisk, I believe everything installs to partition B.
The issue is not caused by EdXposed because it has happened some times without it being installed.
I believe the modules I've used each time are:
-IOS 12 Emojis
-Systemless Hosts
-Call Recorder - SKVALEX
I believe I was also using FDE.AI, but I don't think that would cause this until after I pass the unlock screen, which I can't.
I've been using ElementalX as the kernel.
The issue comes up randomly, and sometimes I can reboot several days without anything happening. I can't see anything I'm doing between the final successful reboot and the issue coming up where this starts to happen that could be causing this.
The ONLY time this seemed to have been fixed was when I updated to the February factory image. However I already had a replacement phone coming, so I decided to still send the old one in.
Click to expand...
Click to collapse
That is a weird issue, for sure. I know of people that recommend flashing factory images and magisk to both slots but I've never have and have not had these issues on any of my Pixels (except on a bad flash).
Tulsadiver said:
That is a weird issue, for sure. I know of people that recommend flashing factory images and magisk to both slots but I've never have and have not had these issues on any of my Pixels (except on a bad flash).
Click to expand...
Click to collapse
Question that may be related. Is it normal that I can never boot from when it's set to slot A? Even manually flashing boot.img and magisk_patched to that slot doesn't work. The factory image seems to install everything to slot B and only seems to reference A a few times.
DarkusRattus said:
Question that may be related. Is it normal that I can never boot from when it's set to slot A? Even manually flashing boot.img and magisk_patched to that slot doesn't work. The factory image seems to install everything to slot B and only seems to reference A a few times.
Click to expand...
Click to collapse
I don't know how old your phone is but the slots are used for when you receive firmware updates and don't change unless you receive one over the air. You can change it manually in fastboot
fastboot --set-active=a
Try that then install your firmware again. It should now just reference B a few times.
TENN3R said:
Finally I found someone with the same bug that happened to me 2 times. I can't understand why this happens.
The first time happened when I rebooted my phone when dark mode was active, but looks like it happens randomly. I got that in november and then 2 days ago, without an apparent reason.
Looks like some UI related crash/bug, but I really can't undestrand what's causing that. Removing root/mods with a dirty flash of the rom doesn't fix it, only wiping.
Hope someone can point out a way to fix this really annoying bug, or a way to prevent it. It's really frustrating.
Click to expand...
Click to collapse
Did you have FDE.AI installed by any chance? And what kernel were you using?
DarkusRattus said:
Did you have FDE.AI installed by any chance? And what kernel were you using?
Click to expand...
Click to collapse
Yes, I had FDE installed for 2 or 3 days, and I was using Kirisakura kernel.
Edit: I just found out that there's a pretty big discussion going on with the FDE module on it's thread, same on the arter account on twitter. It's possible that this is the cause of the issue
TENN3R said:
Yes, I had FDE installed for 2 or 3 days, and I was using Kirisakura kernel.
Edit: I just found out that there's a pretty big discussion going on with the FDE module on it's thread, same on the arter account on twitter. It's possible that this is the cause of the issue
Click to expand...
Click to collapse
I also feel that it's the issue, although I was using the FDE.AI app, so I guess both methods of installation can cause it. After the nth time resetting my phone, I just changed kernels and uninstalled FDE.AI and for a solid week now I've been booting fine.
Edit: wow I just looked at the thread and it looks like something went down over there.
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.