Hello all, so after reading a post on how to change your boot animation on the Samsung Galaxy S6 (G920-F But applies to other variants)
I gave it a try, and I decided to use the method where you transfer three files to system\media. So I did, and upon restarting the phone, it wouldn't restart, but instead black out for a few seconds then go back to the lock screen. After this, I panicked (Thinking that I broke it) and reverted the old files to where they were (From a backup I made previous to changing it) and it still does not work. Is there something I can do without reinstalling the ROM (Which in question is the stock ROM) or a method without posing my data? If not, they'd be the last resort. I do have root access (Rooted with CF-AUTOROOT)
Side note: The exact same thing happens when you try shut it down as well, and the only way to shut it down is to use an app that executed a script to shut it down, or booting to the recovery and shutting it down from there. I'm using TWRP recovery. version 3.0.2-0-zerolte (That is the name of the TAR I used to flash)
I was thinking about this for a while and I have this question; Is there a way to log everything the phone does before running into errors, causing it to go back to the lock screen after restarting/shutting down?
If there is any other way to restore it or troubleshoot it, please tell me. I'm reinstalling the ROM as a last resort if anything else lets me down
Other than the boot animation errors I've been having, the phone has been working just fine. Just it boots up way faster then it is meant to do when powering on (No one's complaining about that)
Related
I got the device two days ago and rooted it the night I got it but remained stock to get use to it a little (came from MT4G) and still not use to the lack of physical menu buttons.
Anyways, after rooting and going through the process CWM, SU, ect. everything looked good for a while but today I had two random reboots from locked screen (went to unlock the device and it rebooted, the same way both times but not full reboots they were short and quick) and I was wondering if anyone else had this same issue and if so how to correct it.
There was another thing, when I boot into recovery it loads fine but when I reboot back to ROM it says there was an improper boot and wanted to send crash log to HTC. Not sure if this is going to be the normal thing but if anyone else is having this every time they go into recovery is there a way to opt out of it by default?
Thanks for reading.....
Orical said:
I got the device two days ago and rooted it the night I got it but remained stock to get use to it a little (came from MT4G) and still not use to the lack of physical menu buttons.
Anyways, after rooting and going through the process CWM, SU, ect. everything looked good for a while but today I had two random reboots from locked screen (went to unlock the device and it rebooted, the same way both times but not full reboots they were short and quick) and I was wondering if anyone else had this same issue and if so how to correct it.
There was another thing, when I boot into recovery it loads fine but when I reboot back to ROM it says there was an improper boot and wanted to send crash log to HTC. Not sure if this is going to be the normal thing but if anyone else is having this every time they go into recovery is there a way to opt out of it by default?
Thanks for reading.....
Click to expand...
Click to collapse
If you boot into recovery or hard reset by holding the power button. It will always ask to send crash report
OK cool so it's normal, thanks for the information.
While I was playing with my TF700 the other day I accidentally put it upside down resulting in pressing (& holding) the power bottom & volume down .. the device restarted into "Safe Mode"
I tried to get rid of it, but apparently I did something stupid which resulting in boot logo loop (the device is stuck at the second ASUS screen and refuses to boot)
* Note my device is Unlocked & I'm running the latest CleanRom version and I am kinda' experienced user :silly:
Anyway I googled this and I tried the following steps with NO success:
- Cold boot
- Wiping caches
- I also tried to re-flash a rom
which left me only with formatting & wiping data, BUT I tried this thing and it actually worked!
From TWRP I restored my last back up (which was a bit old) But whatever, It actually worked! and I have no problems whatsoever, everything seems to run as before, I also tried to reboot the device and it's still working!
I felt I should share this info with you, it might help someone :highfive:
Alright, so yesterday I tried to root my tablet (Samsung Galaxy Tab 3 10.1 Wifi) yesterday by installing TWRP and then loading the Superuser zip found in their link in the play store. It worked fine--I had root access and all was going fairly well. I then tried to make a small tweak to the build.prop file by changing ro.build.version.codename from REL to L.
When I rebooted to apply that change, I could not start up, so I did a factory reset (not a big deal, no essential files on there). It then booted fine, but when I reinstalled/updated all my apps, the Google services were crashing like mad. So I reverted the build.prop file back to REL and again it would reboot, so I did another factory reset and all was good; the Google apps were fine.
Well I was still rooted and I wanted to take advantage of all that time I spent doing it, so I downloaded the bootanimation zip found on this thread and replaced my bootanimation.zip that was already on there. I restarted to see the animation, and this is when the real nightmare started happening. I could not boot now at all.
I did another factory reset, and still it wouldn't boot. I then used TWRP to do a full reset, and still nothing. I did an advanced reset and somehow managed to delete the operating system files (I have no idea how), causing TWRP to say that no operating system was installed. I still couldn't boot, of course.
Finally, I decided I had had enough of this rooting ****. I searched all over the internet looking for a North American version of my stock ROM, and finally found one posted on this forum post. I wouldn't normally trust any random file, but I was getting desperate here. I used Odin to flash that ROM, and there were no errors. Now when I go into recovery, it gives me stock and not TWRP, so I know that was probably successful.
However, I still cannot boot. I get stuck on the screen that says Samsung Galaxy Tab 3, which sometimes goes away and then comes back. I can't send it in for warranty, because it still says "custom" in the recovery mode. How can I fix this? any ideas?
I really want my tablet back :crying:
Hi, I bought a used Nexus 5 and it has been causing quite some problem when booting. I flashed Cyanogenmod in it and it works fine for a few days. After that it keeps having the same problems in the following order:
- It would restart on its own, sometimes some random app will fail functioning (it's never the same app).
- Turns off on itself without restarting. Can still be turned on normally.
- From there it gets worse and start bootlooping. On CM it loops around the part where it initialises the apps. On stock its the colourful stuff that happens right after the Google logo.
- Finally it just gets stuck in boot. On CM it's stuck where it initialises apps while for stock it turns off right after the Google logo appears.
I have tried the following:
- The persist partition fix described at https://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
- Cleaning the power button and made sure it wasn't stuck.
- Re-flashing CM, did a checksum to make sure the files are okay
- Went back to stock, did a checksum too.
It's a used phone so I have no idea what it went through in the past. Anything I can do to fix it?
Try running the phone with a stock ROM without root. If the problem still happens, it's probably a hardware problem.
It didn't have root but I flashed a factory image (plus another round of factory reset too) and even locked the bootloader + reset the tamper flag this time. It's working fine now but the problems normally start a few hours/days later so I can't be sure at the moment.
If it does fail again which hardware is the one with the problem? The warranty's long gone so will it be easy to buy a new part and replace it myself?
The cheapest solution may be to buy a used Nexus 5 with a smashed screen and working internal components to swap out components.
Objective: I am hoping to be able to boot my existing system to recover data such as SMS, call logs, app data, and so on - obviously it was inadvisable to start messing around without backing up my data, particular with my amateurish capabilities. But that's the situation I am in. For some reason I thought that just replacing the Recovery was not going to risk my data. Its been over 5 years since the days when I would regularly flash my new phones with cyanogenmod, and my abilities were very basic even then.
Context: G930FD with stock rom, baseband ETC? - apparently for Dubai, which does not allow VoLTE or WiFi calling, which is what I was trying to fix when I got myself into this.
the Events:
- I enabled ADB and used Heimdall on Windows 7 to flash twrp-3.3.1-0-herolte.img
- initial attempts failed to complete download. I booted back into the system and applied OEM Unlock. Flashed successfully.
- chose the 'allow modification' option or whatever it says, not the Read-only option
- I did NOT check at that point to see if the system would reboot properly. I instead right away made a full back-up to my external SD.
That's all I did. After the back-up was complete I rebooted, and arrived at "SAMSUNG Galaxy S7" endless boot loop.
best guess: this is related to samsung encryption? TWRP file manager says that DATA is 0MB.
Again, I am desperately hoping that someone can help me recover my existing system. The threads I found on this subject all lead to wiping the phone and flashing a new rom.
thanks.
digging in deepr
I went ahead and rooted by loading SuperSU otg through TWRP.
Now I get passed the first splash screen that was previously boot looping (Galaxy S7, powered by Android), and I get to the 2nd splash screen (glowing SAMSUNG logo). It does not boot loop, just glows in and out endlessly and never loads.
Is that progress? Or maybe its worse.
t.krug said:
I went ahead and rooted by loading SuperSU otg through TWRP.
Now I get passed the first splash screen that was previously boot looping (Galaxy S7, powered by Android), and I get to the 2nd splash screen (glowing SAMSUNG logo). It does not boot loop, just glows in and out endlessly and never loads.
Is that progress? Or maybe its worse.
Click to expand...
Click to collapse
Reflash TWRP with Odin, boot TWRP, wipe cache, reboot.
Thanks.
I think greenman at sammobile had the answer --> NEW: S7 5 file firmware options (this forum wont let me post a link).
But I botched the execution and the CSC file overwrote my data. Crushing blow. I would say lesson learned, except that I already knew better and risked my data anyway. Sad.
I have a backup I made at the first launch of TWRP - but I assume its worthless since TWRP was not reading the encryption. Its only 3.7GB.
Side note - I did achieve the original goal of replacing the Emirati rom with one that activates WiFi calling and VoLTE.
Has this issue been solved?
I never recovered my data if that's what you mean. Did you look up greenman at sammobile? It sounds like someone followed his directions and was able to flash just the system files without overwriting their data. I think you had to modify the csc_home file. It was a bit beyond my skill level.
Oh, I was just wondering if your phone was still bricked. I didn't read your last message properly before replying lol. My bad.
I'm not personally having issues with a device, I was just curious if I could help at all.