Very very strange I've never seen this before, so I was just doing my typical day walking around at work and all of a sudden I feel my phone got hot, pulled it out of my pocket and it was stuck on boot screen. So I did a battery pull to get it back to the rom and it just stopped at the bootscreen, after that I tried a dirty flash, then a clean flash...all I see is a bootscreen never gets past it. Recently updated to new firmware 2 weeks ago and did notice it was strange when I flashed the GE Rom kept asking me to Install SU. Anyone got any idea how to fix this? Only issue i noticed was during the install of the rom i get a unable to mount /preload but besides that everything completes fine
fadentales said:
Very very strange I've never seen this before, so I was just doing my typical day walking around at work and all of a sudden I feel my phone got hot, pulled it out of my pocket and it was stuck on boot screen. So I did a battery pull to get it back to the rom and it just stopped at the bootscreen, after that I tried a dirty flash, then a clean flash...all I see is a bootscreen never gets past it. Recently updated to new firmware 2 weeks ago and did notice it was strange when I flashed the GE Rom kept asking me to Install SU. Anyone got any idea how to fix this? Only issue i noticed was during the install of the rom i get a unable to mount /preload but besides that everything completes fine
Click to expand...
Click to collapse
Use odin to go back to full stock, upgrade to MF9, do a factory reset, later root the device install recovery, do a full wipe install GE rom fix permissions. Report back on what happens. (Keep in mind this will wipe internal memory MAKE BACKUP!)
Sent from my SPH-L720
Related
Hi folks.
So after a sleepless night and a lot of guessing and clicking around with no luck, I finally decided to ask for help.
The story:
Yesterday, I decided to open up my lovely N4 to perform the thermal pad mod (that can be found on these forums), as it was going really hot around the CPU at time and it seemed like a good solution.
Now, I'm no stranger to disassembling microelectronics without breaking them (few weeks ago, I successfully resoldered a broken power button in my old T989 that I've been using before N4).
What couldn't let me sleep at night:
And here is where the problem emerged. After re-assembling my sweet little phone (yes, i did it perfectly right), I tried to boot up and all i could see was an endless and really annoying bootloop, but as the device booted up, I did not worry much. While doing some research, I read that there's people experiencing bootloops with 4.3, so I thought that after disconnecting the battery, it just might've had happened on its own (I was using stock 4.3 with faux kernel before the nightmare started)
At this point, I booted into recovery and tried to flash the rom over, but unfortunately nothing positive happened. Then I tried factory reset and flashing different roms, also with no luck. This is when things started to get really frustrating, as no matter what I flashed, the bootloop was (and is) still there. But then I tries to restore a backup that I did right after getting my N4, back in November, and it WORKED. Why do i still have a problem then? Because it was 4.1 and OTA was giving me error every time I wanted to flash the update, so I kept flashing till i get some results. And then one of the N4 toolkits wiped my entire internal memory and I ended up with only being able to use sideload. Then I tried ALL of the N4 toolkits that can be found in here, to wipe everything and bring my phone back to everything stock, but the bootloader is locked so it cant do it, and it cant unlock it because I cant boot into the system.
Conclusion:
The phone works fine, and it proved it. But no matter what I try to flash (other than the old backup), the persistent bootloop is still there smiling at me like an a****le.
Any ideas?
ATT Galaxy S4 currently running Goldeneye 6.0 and TWRP 2.6.0.0 (never installed MF3 base, but have tried both MF3 and MDL modems)
First odd thing...
[About->Status->Device Status] is listed as "Sd card" instead of the more common "Official" or "Custom".
Anybody know what that means or is telling me?
This is the latest thing I've noticed with my phone, which has been having all sorts of issues lately that I cannot seem to figure out. My main problem is, I can reinstall a new ROM, boot into the ROM, change settings around, reboot just fine, but, as soon as I install anything from the Play Store, the next reboot will hang on the initial Samsung splash screen. Wiping is the only fix I've found, and fixing permissions in TWRP errors out with an error that it cannot chown one of the new/updated .apk files.
Both Goldeneye 5 and 6 are doing this now (5.0 was installed and rock solid for several weeks before this all showed up...it started sometime after I decided to try out a couple of the aroma roms and then came back to GE).
Used ODIN to go back to factory rom, re-rooted/installed TWRP, then reinstalled GE6.0, but the same thing happened. Everything looked good until I ran updates from the store, then I was stuck again (note: used Root Explorer to check to permissions on the updated apks before rebooting and they were all correct (755)).
Other things I've noticed are:
1. Sometimes, on any reboot, the startup locks at the initial Samsung screen and I have to long press the power button to get it to reboot. It usually boots the second time around (this is before I install any additional apps and am completely unable to reboot).
2. Sometimes when wiping cache, davlik, and/or data, TWRP will seem to hang for up to a minute when trying to initialize the partition. A couple of times it even hard reboot my phone when I did a cache+davlik wipe.
3. I rolled back to a recovery image just fine; however, it was a couple months old. Everything started off looking great, but once I updated to a new ROM, my issues returned.
Trying Heimdall to go back to factory; however, I'm having issue with my laptop and getting the Zadig drivers installed. While I'm working that out, figured I'd see if anyone else has any suggestions on what else I should be trying or looking out.
thx
I would flash your phone back to MDL stock with odin using the mdl tar. This should format your paritions correctly. You could also reinstall MDL using kies since they still don't support MF3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Hey XDA, just a long time stalker who has finally given up trying to find his solution on already posted items (I think 10 hours of trail and error means I'm not gonna catch what I'm failing to see...)
When I first got my galaxy s4 I downloaded KangaBean and it was on 4.2.2 I believe. Today I decided I should upgrade to 4.4.2 since I've only been hearing good things about it, and I wanted the slight updates that came with it.
Well, I have a AT&T s4, sgh-i337 that was on CWM 6 when I tried updating to another ROM, the first one I tried was GOOGLE EDITION 4.4.2 BY DANVDH. Did a wipe, cache, dalvik, format system, flashed it, flashed loki doki, said no to re-root/root fix prompt that followed, then I came to the yellow triangle, I thought that was odd, believed I missed something.
So, I downloaded TWRP 2.5.0.2 like the thread suggested, tried again, no luck. Then I tried Unoffical Carbon KitKat, which just caused the "Samsung Custom" logo to stay on indefinitely (I let it sit for 40 minutes before giving up.) After 2 failed ROMs, I tried KangaKat, updated version of KangaBean, so it should be just dandy right? Narp, same luck. This one boots, then reboots into recovery.
At this point I considered myself to be stupid in some way so obvious that I would die before I noticed it. So, then I just flashed the stock firmware thats like 2.5 gb through odin, re-rooted and installed CWM 6.0.4.4 LOKI'd and tried to flash KangaKat, being confident it would work this time, again I got boot to the logo and then reboot into recovery.
At this point I attempted the other 2 ROMs again, multiple times.
After some sobbing, I re-did the stock firmware, tried again, failed again.
My sadness turned into rage, I just destroyed one of my micro sd to usb-s because it was being annoying and I was annoyed, I took a picture and got over it.
I tried a 3rd time with the re-flashing stock firmware and tried with twrp again, no cigar.
Now, after MANY hours and MANY false hopes... I shall be using my blackberry and hoping to return to android soon, if somebody can help me figure out what I'm missing. Many thanks ahead!
Did you do lokidoki after?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Did you doa hard reboot clear the cache and davlik after it got stuck on the lock screen ? It seems odd that it would just not boot up at all. I was about to wonder if maybe it was the CM kernel bug that will keep it from booting past the initial screen but you tried aGE rom so...
So I rooted my phone long ago when it was new just to get wifi teather which worked great and has been ever since. I never installed the AT&T update that it kept asking me to do because I did not want to lose root and the teather ability. I recently installed CWM Touch Req0very because I wanted to try a new ROM. This worked fine and I can get into CWM now. I completed a backup using CWM, thankfully. I then tried to load the LiquidSmooth ROM for this phone. Before doing so I used CWM to complete a factory reset, cache wipe, and dalvik cache. I then chose the LS zip file and it loaded and appeared to be successful. I then rebooted and got the Samsung unlock padlock image for a few seconds and then the screen went dark and the power LED turned blue. I let it sit for a few minutes but nothing changed. I pulled the battery and rebooted but got the same. I then went back into CWM and restored my backup which took my phone right back to where it was, very thankful for that. What did I do wrong and how can I get the ROM to install properly?
I tried to reinstall the ROM and when it booted it got further. It went past the LS splash screen and then started pulsing the LS ying yang type logo. It did this for about 10 minutes so I pulled the battery and tried again which it just repeated the same process. I pulled the battery and restored my backup again. Nothing seems to work as easily as the hours and hours of videos and pages I've researched. Why does this seem to work so easily for everyone else?
Hey all! I'm having a strange issue regarding boot looping that I can't seem to find an answer to on here or anywhere else, I hope you guys can help.
So my T-Mobile Samsung Galaxy S5 (SM-G900T), purchased in May 2014, while perusing Facebook the other day, randomly shut down in the middle of perfectly normal use and started bootlooping. I had never had the problem before. The device had been rooted for months (I forget what method I used) but it was running a stock Lollipop rom. The first thing I did was factory wipe and cache wipe through Android stock recovery. It worked!... for a couple hours. Then the bootloop started again.
I went and sought a new stock rom, believing that somehow mine had been corrupted, and flashed it via Odin. I also flashed TWRP. Clean wipes, new rom, dalvic/etc. wipes, and booted into stock Marshmallow. It worked!... for a couple hours. Then it started bootlooping again. I went into TWRP and tried to wipe just caches and whatnot, but it wouldn't start again. Long battery pulls sometimes allowed the phone to boot, but it started looping again after ~5-10 minutes.
So I installed the Twisted Lollipop but couldn't even get that to boot. I went back and found the earliest available firmware for my device (as I bought mine right after it came out) and flashed it. Wipe wipe flash wipe whatever, and a succesful boot. It was looking good! I was able to install a number of OTA updates. I was at Android 5.1 when I decided to call it a night and hold off on the further OTAs for today. Today I got up and got ready for work, all's well. As I'm getting ready to leave, I allow Google to update some apps, and begin installing Facebook, Spotify, Cap Metro (for my area's public transit system) and maybe something else, I don't remember. Anyway, as the updates are downloading or installing and I'm checking my email, boom, crash, bootloop.
What's going on here? I've never heard of hardware causing boot loops, but could it be that? I dropped my phone (although protected by a Spigen case) earlier this summer and it cracked the screen-- could it have messed with the motherboard in some substantial way? I had noticed it getting hotter and the battery lasting less than usual, but I attributed that to the device's age.
Any help, any advice, any direction you could give would be extremely appreciated. I don't have the capital to replace the phone right now, and I use it all the time. Thanks folks!