Hello, been a long time since I even used this site. Retired from rooting flashing etc but now I have a problem. I play a lot of cod mobile and will be entering the championship but since updating ota to android 11 I have a lot of game crashes, worse framerate and even worse thermal throttling. Is it safe to revert back? Everything ran great on android 10. I tried flashing a stock rom via adb but it just failed, then again my adb is hit and miss with whether it wants to work
Related
Hey guys,
i have been using Ivan Mehler's cm 5.1 rom and since early this year i am on his 6.0 rom and everything was fine until mid june. Since than i have the 'sleep of death' syndrom (phone won't wake up from deep sleep until hard reset). I can keep it from freezing when i stop it from going into deep sleep via apps like 'Safecharge' or having muted music playing in the background. It could be a hardware issue. I have dropped it twice pretty hard, once in 2014 and a second time 2 weeks before the sods started. Else it runs without issues. I reverted to a backup, installed another cm 6.0 rom and reverted back to stock, to no avail.
First, how do i best diagnose whats causing this?
And secondly, are there any leftovers from older roms that could interfere when i install a new rom via twrp and doing a complete wipe including reformatting the file system etc? What i like to know is whether when installing the latest stock rom via odin, does that mean that every bit on every storage/memory of the phone is being completely wiped and newly written, or are there some basic parts of android/linux that would not be touched?
So like many of you, I have been really frustrated with T Mobile that they are the only carrier not to upgrade their Note 2 to Android 4.4, and they probably never will. There are more an more apps that I cannot run, some of which are important to me. So I gave up with calling T Mobile, and struck out on the custom ROM trail, seeing that CM has a 4.4 mod for this phone. After rooting and attempting to unlock (not necessary) and changing to custom recovery, I managed to get the CM mod loaded and running, after many hours of learning by trying everything, I got the phone running on the CM 4.4 mod, only to find that I could not make any calls, as there are no mods, anywhere, that support T Mobiles WiFi calling. I guess T Mobile uses that because their network is weak, but hey, I have used Sprint, AT&T and Verizon over the years, and every network has holes, especially inside buildings. It so happens that both where I work and at my home is spotty, so I cannot survive as a phone without WiFi calling. After all, for all of the bells and whistles, a Smart Phone is first and foremost a Phone. So after all that, I started on a new trail, unrooting and installing a stock mod.
There are lots of help out here that tell how to unroot and go back to stock, and they are all trash, every one of them. I tried stock mods from several sources (SAMMOBILE and others) and only found two out of six update versions that even functioned on my phone, and only one of those actually worked like it should, and that was the very first 4.1.1 version T889UVALJ1 that came with my phone years ago. No LTE and more apps that would not install at this level. I was hoping to at least get to the T889UVCOH4 version of 4.3, which is the current latest version from T Mobile.So here I was, an older version of ROM on my phone, no LTE, Flash counter not at zero, and Knox telling the world the phone was modified, excluding any chance of help. Why in the world did I even step into these problems. And then I made a startling discovery.
As I tried to at least restore the data backup I did before this whole thing started by using Smart Switch from Samsung, I found that not even that would recognize my phone because of the older version of android so I could not even get to my backups. When I got the phone it used Kies, but with the 4.3 version of android, Samsung changed over to Smart Switch. So at that moment I felt I was completely screwed. Then I saw the little "More" button on the Smart Switch dialog that was telling me my phone was not supported, and I clicked it. It brought me to some other options, and one was emergency recovery, which allowed for an initialization after a failed upgrade. I did not expect much, as my phone was not supported anymore, but I could not see any other option, so I chose to initialize the phone for recovery.
Well guess what, everything ran perfect, and when the process was completed, my phone was just like new, no flash record, no Knox report, a completely authorized phone. It was if I had never rooted it at all, and I had flashed a dozen ROMs. So for everyone that has a bricked or soft bricked Samsung phone or find out the custom ROMs are not what you were hoping for, all you need to do to get it back is install Samsung's Smart Switch on your computer and click the little "more" button on the screen and reinitialize your phone. It will be like the whole rooting and ROM experience was a bad dream, And yes, the backup did load when I was finished. It is that simple. This should work for any Samsung with Android 4.3 or higher on any carrier.
So about a few years ago, I tried to root my galaxy note 4 (n910aucu2doi3), but I guess it rejected the root because it instantly bricked my phone, to the point where I had to completely wipe it using android recovery. The only way to get my operating system back was to download it online and install it through my PC (I had to find the exact version for my phone as well, 5.1.1 at the time, because it rejected every single other version).
Everything seemed to be working fine, except that I couldn't install software updates on my phone anymore. It was permanently stuck on 5.1.1. It was a bit of an annoyance but I didn't think much of it at the time.
Fast forward to now, and I'm getting several signs that my OS may be corrupted. My phone is constantly freezing, crashing and restarting. Maneuvering through applications causes the phone to freeze for a few seconds before either restarting or crashing the app. I want to say it's definitely a software issue, but I did install a new battery recently and it was working fine for a few weeks, could that be the issue?
If not, I want to start over, but I'm not sure how, and I don't know if it's safe to do a factory reset on this OS. Is there anyway I can get a fresh stock version of an android OS that can also update?
Any help is appreciated, I'm pretty much desperate.
I manually updated to 6.0.1 with the help of this thread https://forum.xda-developers.com/note-4-att/general/updates-thread-t3663943
It seems to have fixed the issues so far, and my phone can automatically update again
Hi team
I recently purchased an ex Demo HTC One M9 as a cheap replacement to my broken Galaxy S7 Edge, as soon as I received it I decided to flash TWRP and a new ROM on it. I was able to unlock the bootloader via HTCDEV.com easily enough and I was able to flash TWRP onto it without issue but when it came to the ROM's I ran into many problems.
Any version of Android that is Nougat or lower would not boot, the phone would go straight to the white bootloader screen every time. Oreo and Pie ROMs were able to boot but I ran into separate issues with them, I could not make or receive phone calls as the whole phone would freeze and there was no audio in from the speaker. I was also unable to play any videos in Facebook, YouTube, Snapchat etc.
I tried every single ROM available here on XDA and ran into these issues. I stupidly also did not make a TWRP backup of my system so it was quite hard to revert back to what it came from factory, I managed to get a stock Marshmellow running thanks to a User here posting a TWRP backup so thanks.
Is anyone able to help me with upgrading to Nougat? I would really like to get the Viper ROM working if possible, is it a known issue getting stuck in the bootloader menu every time?
I've tried just updating through the OTA process in the menu but it says there is no update file available.
Cheers
I'm absolutely losing my mind please help
A little story time, skip to the end for my question;
So, how to start - One day I unlocked my bootloader, went for some android 11 rom and all was fine. Then android 12 was released and I downloaded the crdroid 12 rom, where I was experiencing some battery drain issues. So I downloaded pixel experience rom. The Bluetooth died because of this rom's cursed source code. I flashed the latest miui fastboot rom and the Bluetooth issue still persisted (remember this for later - not all the drivers flash with the Rom). I fixed the Bluetooth issue by switching several miui roms, also made a guide if you're interested. That fixed the Bluetooth issue and I went for pixel plus ui rom. It was a bit laggy, so I switched to the shiny new Evolution X rom. It was amazing, so much stuff co customize, etc. Well, i experienced another battery drain issues, so I just went for the stock miui with magisk pixelify module. Im pretty fine with this rom, and I thought the problems are gone, because it stock and everything should be fine. Well no. The battery drain issue persists. I was wondering what even is happening, so I opened battery settings. That said that the top apps wasting my battery is screen, Google services and android system. I downloaded a CPU usage stats app, which showed me that the cpu usage is at 99% (I think it's correct as the phone is overheating). The app with most cpu usage was using only 1%. I don't know if this is a firmware bug or whatever, but I think some rom broke it and the latest stock miui didn't overwrite that driver, as written above with the Bluetooth issue.
So, how can I make my phone be as it was released from xiaomi with all the drivers to actually use the hardware correctly?
Thanks in advance for any replies, I'm seriously going to throw my phone out of the window
Also the way how I install the stock Rom is by downloading the latest fastboot rom, extracting it and executing ./flash_all.sh file.
SOLVED! My problem was because of my credit card. I have my cc in the phone case. The cpu was going insane because it was constantly detecting the card and loading info from it. Literally turning off NFC fixed this whole issue. Bruh.