Posting this because I spent 2 days trying to get my phone back up and running after I changed some system setting that caused an endless bootloop. Marking is solved as the issue is solved and maybe it will show in the searches.
I followed the instructions on the guides i found on this site. I had all sorts of problems. ROM not installing, TWRP not sticking, TWPR not flashing modules, error messages all along the way. I have flashed this phone several times already without issues, other than the 1st run.
I stumbled across a random post on an Xiomi forum somewhere where the guy was having similar issues. The solution was DON"T use "the latest version" of TWRP.
All the guides insist you use the latest version. That's what I was doing to TWO days. I went back about 3 versions and BOOM, phone was set up, flashed OOS 10.3.3, Magisk flashed, new kernel flashed, xxxNoLimits flashed and everything working in under an hour.
This may have been specific to my Tmobile, international conversion, but I doubt it as I was already running OOS 10.3.3. Nowhere on this site, at least from the searches I did could I find this suggestion that turned out to be my solution so I am posting in hopes it might help someone else and save the frustration I went through.
For those that are going to post search results that didn't show up when I searched( which seems to happen when you say you couldn't find something here).....cool....the extra info may help someone.
Thanks for posting! I've been having issues flashing Xtended! The phone shuts off right in the middle of the boot animation. Fastboot recovering to oos worked fine though.
Is that similar to what you experienced?
Related
Hello all.
I was having major crashes and issues with the latest two versions of the Samsung OS, so I decided to use CyanogenMod... Well, that didn't go too well; I had issues with the camera and Youtube apps which made them unusable (others weren't suitable either). I had a number of problems with how apps and the OS worked and couldn't find solutions to all of the problems, so I decided that I'd go back to the stock firmware, but from a few months ago before I had any issues.
So, as I've done before, I plugged the phone in, opened ODIN and selected the official ROM that I downloaded, started the thing and 10 minutes later, I was back on official firmware. But I kept getting "Google Play Services has crashed", along with a couple of other services occasionally crashing too. So, I tried stopping the Google Play Service and somehow made it worse.
Not only that, but it didn't seem to clear anything; all of my apps were still installed, all of my files were still there and I think that may have had something to do with the crashes.
I guess the above two issues were something to do with the fact that I went from CM on 4.4.4 and went back to Official on 4.4.2.
So without doing any research, I just decided to press "Nand erase all" and tried again, thinking that it might simply wipe the old OS and data. Now it's stuck at the SAMSUNG logo (starts just fine but stops after a second or two). So, I went to Google!
I found a few threads with similar issues, but I can't seem to find things that have a solution.
This one seems most helpful, but I can't find any "PIT" files, or anything of the like.
http://forum.xda-developers.com/galaxy-s4/help/help-nand-erase-t2863345
What would you experts suggest?
Thanks in advance.
Do you even read before you start messing with your phone?
All the errors you had could be solved by wiping properly in the recovery.
You can find the .pit file here.
http://forum.xda-developers.com/showthread.php?t=2265477
I would suggest following the same steps as the member in the thread you posted.
Lennyz1988 said:
Do you even read before you start messing with your phone?
All the errors you had could be solved by wiping properly in the recovery.
You can find the .pit file here.
http://forum.xda-developers.com/showthread.php?t=2265477
I would suggest following the same steps as the member in the thread you posted.
Click to expand...
Click to collapse
Thank you. Unfortunately, no, I didn't read much. It seemed so simple; perhaps too simple.
I shall just try it now and see how it goes.
EDIT: Works perfectly now, thanks!
If this has been answered somewhere in this forum I apologize and please direct me to the answer. Back when I got my phone in march I rooted my phone using one of the guides on this discussion page so I could have open wifi tethering. While I did have some hiccups not the least of which being soft-bricking my phone and having to flash what I thought was a stock rom but ended up being a android 7.0 rom that seemed to work fine on my phone. Learning my lesson I made a backup right then and there of the stock install as well as two afterwords once I got everything set up the way I wanted. Flash forward to today my phone is bugging me for a seemingly benign system update and after ignoring it all day I dumbly install it without thinking. Now no matter what I do booting my phone only takes me to the TWRP recovery menu. I have tried running all of my backups and nothing is working. Of course because this has been a couple months the image I used is gone so I can't use that. Would that even work, wtf did I do. Let me know if anyone has an answer I will be eternally grateful
Ok problem solved.... after whiping my phone several times I attempted an install of cypherOS. and well.... it worked. I think I'll stick to this . Just let this post die I guess... I am going to set my alarm and go to bed I am very tired and have work in the morning
I received an update push from Motorolla that installed Nougat. After that, my phone would crash every 3-10 minutes. I did all the troubleshooting I could find online. I contacted support and they wanted me to spend $150 to get it "refurbished." Of course, it sure seems like a software problem, so that wouldn't help me anyways...
I turned to custom. After rooting, installing SuperSU and TWRP, I couldn't get several versions of AICP or Lineage to ever boot (stuck on loading screens). I also tried all the advice from this thread.
I went back and installed the stock Rom using f2fs , and the phone would get to the "hello moto" part of the boot up, then crash and reboot. I tried again using EXT4, and it worked, but just like before I ever begun, my phone was crashing every 3-10 minutes. However, the first crash wasn't until after I made a phone call, and my phone had been crash free for about 20 minutes before that call.
I'm a I.T. guy, but I'm not a "phone" guy. But it seems to me that there must be some other software that was modified during the update that is causing the problems that isn't part of ROMs. Something in the Kernal, or a driver folder or something?
Also, is there a way to get crash reports? So maybe if I at least go back to the default ROM and wait for it to crash, I have some info to work with?
Any help is greatly appreciated, thanks!
Flash full stock 6.0x for your model/region.
Important:
Without bootloader, gpt. Don't try locking BL.
Links you can find in my signature.
Try normal boot and after success any custom.
You cannot allow any ota update after it.
Some customs are only for Nougat modem/radio - don't flash it. @Kaivian
Ok, I got most of that, except I don't know what gpt refers to and am not getting any hits on search.
My signature - flashing stock - without bootloader & gpt.
So, I installed a 6.0 stock ROM and got tons of errors. I tried a 2nd time, still got tons of errors. Needless to say, stock 6.0 didn't boot. I decided, "The heck with it" and tried installing Lineage 7.1 again... and it worked! It finally booted up entirely. However, now I get a "Sim card missing" notification. Can I just reinstall part of something... like the modem? so I can keep this "working" lineage boot? Or am I starting over yet again?
Repeat
from
fastboot flash modem ...
to
...fsg.
dzidexx said:
Repeat
from
fastboot flash modem ...
to
...fsg.
Click to expand...
Click to collapse
This caused it to not boot.
I went back to 6.0 and turned off auto-updates. I'll try again sometime when I have time. I did like the custom rom a lot, just couldn't use it as a phone xD
Hello,
I have an odd problem I need to iron out. . . Recently I installed the NeculaROM mostly without a hitch, however I was having issues not being able to make outgoing calls, so I wanted to switch back to my old Rom. Normally this wouldn't be an issue however when attempting to wipe anything on the phone, it starts vibrating and shuts off in TWRP. I can flash things fine still, back things up, yada yada. I tried reflashing TWRP, and that didn't help either.
So now I am stuck on this rom, and I can't do anything in TWRP. Is there any way to fix this? I can't seem to find much information on this particular issue. Any help would be great.
Thanks!
I believe this is caused by f2fs changes with rebasing this device to nougat.
Have you tried using the TWRP linked to the OP of the NucleaROM thread? You might have to format internal storage to get things working right again.
If that doesn't work out for you I'd recommend searching around more recent discussions in the TWRP thread and LineageOS thread. These issues with wiping and differences between unofficial TWRP, official TWRP, and what works with what ROM/firmware combinations have been covered in both.
Sorry I'm not more help on exactly what to do. I've just stuck with marshmallow firmware and custom roms based on it. I'm waiting for the dust to settle on this nougat rebase business.
Had same issue. I ended up just reflashing all the firmware images. Fixed my problem (for the most part.)
Hey everybody, I need help. I have a J320P that is stuck in a boot loop, when it was found like this by my friend they came to me and asked if I could help. I have no information on how this happened other than they took a shower and when they came back it was like this. I have tried installing stock firmware 3 times to no luck. I might have an sd card somewhere with the backup for this phone but finding it would take some time so in the mean time I am turning to the forums. If anyone could help that would be amazing. I will provide more information and answer questions as they come.
Steps I have taken:
1. dirty flash of stock latest firmware
1. wiping the phone completely
2. Installing latest stock firmware
3. Still bootlooped
Not solved
So after triple wiping through TWRP and installing the stock firmware again it was still looping so i left to run to the store quickly and when I returned I tried powering it on and it loaded normally and I am still setting it back up.
Leaving the original comment. After coming home from work my friend said it had started doing it again, and it is. This time there was no root and no system anything messed with, does this mean there is a hardware problem?