I got bored and so decided to root my phone again . I used the same old engineering boot image as always but results come back somewhat different then expected. Purpose for why I rooted again was simply to determine if Samsung or AT&T made any changes in the recent OTA's that would have fixed the root method. I was on the latest official Android N before rooting. Prior to rooting, I went and flashed official odin image to my samsung g930a version was the QF3 one. After doing the official flash i did the same old engineering boot AP flash before running the root batch file. Surprisingly it's rooted and working fine without the common expected battery drain issues or lag problems. Any ideas why the engineering boot would suddenly be working fine without any noticeable battery drain issues. I rooted at battery level of 100% and it is now 17 hours later and my phone's battery is still at 90% without having made any changes to the CPU like changing it to ondemand. Last time I had rooted my phone it would have needed recharging already and that's with all the tweaks.
Related
So I have been running CM11 since January and finally got around to updating to KitKat to see what was new and because CM11 wasn't using the kitkat kernel which I assume is what caused all the SoDs and instabilities in all the ROMs. Well now I'm on stock and I'm suffering horrible battery life in comparison (17 hours with 4 screen on vs 36 hours with 8 screen on). I tried flashing CM11 and it worked but after a day or two I wanted to try a new ROM. Carbon was one that I saw near the top of one of the G2 development forums so I decided to try that. Went through the normal process to flash a ROM and it bootlooped when I rebooted. My backup also boot looped and I had to use some method to go back to 12B since I had no ROM or anything on my phone. Got back to 24A and I tried flashing Malladus to see if a stock based ROM would work and it looped. Restored my backup and tried CM11 and it also looped. Now I'm sitting on stock with Verizon's bloat hogging resources and battery and a phone that won't flash and boot successfully. Is there any way I can fix this? Has anyone seen this before?
TLDR: phone won't flash a ROM without bootlooping since 24A update
Only gonna bump this once but I really hope the right person sees this. Really confused as to why my phone won't properly boot after a clean ROM flash
So, just to preface, I am a rooting beginner. I'm not sure if the damage that has obviously been done is a result of some sort of incompatibility or a failure on my part.
In short, I'm using an N910F (Vodafone, UK), and I attempted to root my device after becoming somewhat impatient waiting for Vodafone / Samsung to pull thumbs out of relative asses and release Marshmallow.
I rooted using CF Root, version LMY47X.N910FXXS1COK2 - going onto a device running 5.1.1. After this, I installed Resurrection Remix, which ran for a small period of time.
After this, I started experiencing black screens, and failures to boot, as well as boot loops.
So, after this, I flashed stock 5.0.1 back to the phone, which wasn't 100% stable in the beginning. So, I factory reset, and flashed again, and here I am.
I am currently suffering from major hanging issues, as well as random shutdowns, which can only be solved by removing the battery, it might seem.
Model Number - N910F
Android Version - 5.1.1
Build Number - LMY47X.N910FXXS1CPC6
Knox 2.4.1
All Rom's were flashed with Odin on a Windows PC.
Thanks in advance, all.
Bread:silly:
Hi,
I recepty run into a problem that I can not fix by myself.
My galaxy s7 started to overheat (it overheats during normal usage, browsing Web etc.)
1. I was using the phone rooted with CF autoroot without a problem for a month or so
2. I installed TRWP and then Xposed framework (all the correct files following guides from this forum) and it worked all OK.
3. 2 days after the above installation I decided to make a fresh clean install of ROM. I found a new updated ROM (June update) of the stock XEO ROM that I was using.
I made a data reset and factory reset with TRWP (wiping all) and then flashed the new ROM with Odin.
I rooted it and installed xposed.
4. Phone started to overheat during normal usage.
5. I tried to flash the new ROM without installing xposed, then trying flashing ROM without even rooting it later. I finally even flashed the "old" ROM from before the June update, with no rooting or touching anything, and it still overheats.
The clues I found as far:
1) i read somewhere that xposed can cause overheat like I described but I don't understand how it could be after I wiped de device so many times and running stock unmodified rom?
2) i read somewhere that there is some Google account backup bug that makes devices overheat which seems to be connected with the 3rd point
3) it seems that Android System battery usage is higher than normal
4) the device overheat mostly on the right middle part of the phone, along the right edge of the phone a little below the power button.
5) i don't belive it's user app related because the problem exist even after fresh install of rom without additional apps installed
I would really need some advice, because I ran out of ideas what to do.
Hello, our situation is similar... I've googled the issue and I've found no solution. My overheating problems started after I installed Xposed framework. Few minutes before, I rooted my phone with Odin and installed TWRP. After I used a module on Xposed, my phone began overheating on the right part of my phone below the power button as you described. I immediately uninstalled Xposed.... nothing worked, flashed my phone back to the stock rom....still the same. IF EVER FIND A SOLUTION, PLEASE SHARE IT WITH ME... I'M SO WORRIED. THANKS.
Possibly a long shot, but I would be opening the occulus app and seeing if it needs to update.
That issue was causing a bunch of phones to overheat last week. Solved by opening the app and letting it update.
Sent from my SM-G935F using XDA-Developers mobile app
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).
For no reason my phone just restarted. It used to restart from time to time and all was fine but this time its in bootloop. I currently don't have any recovery installed on it but I can enter in download mode. Is there any way to fix it without losing any data? I have some pretty valuable stuff that I can't really afford to lose
Its the LTE version and its running stock kitkat
I had different roms before but in the end I came back to this as everything else had bugs and wasn't stable
Also lately my battery life went to ****. From an average of 5hours SOT I can barely have a bit over 2 hours, sometimes not even 2. And I changed the battery with a new one and still no change. For some reason bellow screen I have android system as 2nd main consumer but I have no idea what could be using it. Could it be hardware??
Suggest flash custom recovery via Odin if you have no backup .
You may then be able to recover data .