Related
After towelrooting and adding safestrap, I found that Sammy's TW os is cemented into any of the roms I may want to use. So, I am returning my rooted phone to ATT and getting my money back. Getting a Nexus 5.
I need to factory image this *****. Is there a factory Kitkat image available that I can use with Odin?
Any chance of it not being detected?
Thanks for the help.:good:
The image for KK for the Note 3 has been posted here. It's rooted, so you'll have to unroot (remove busybox first) after you install it. Oh - uninstall Safestrap first. (You'll have to read threads to find the 4.4.2 file - I don't keep links to threads I don't need, but try the Odexed version at this thread. Aside from being rooted, it should look exactly like stock. You can't back up an image of the ROM without being rooted, so any image you find will be a rooted one. But SuperSU will remove most signs of root. [If Samsung wants to investigate every byte of internal memory, they might be able to detect that you once did something. But if your luck is that bad never get out of bed. The stores will turn the phone on, look around a bit and accept it as stock, even if you've put your name and email address in it, although you SHOULD do a factory reset before returning any phone.
As far as your original post, yes, you'll find the original ROM in the stock slot in Safestrap after you install it. That doesn't mean that you can't successfully run some ROMs in other slots (no guaranties yet, Hashcode is still working on the problem) or you can back up the stock slot, wipe it, install any ROM there that you like (the "plain vanilla" method of using Safestrap in Kit Kat right now).
If you can't wipe the stock slot, uninstall Safestrap, reboot to recovery, do a factory wipe, reboot normally and reinstall Safestrap. (Make sure you're using 3.75, or even 3.72. 3.71 is for 4.3, and it won't work on Kit Kat.)
The Nexus is a nice phone, but Safestrap has saved me from a few stupid blunders that normally would have required that I buy a new phone. (Try flashing a keyboard in recovery. Then boot. If you boot to the slot you flashed the keyboard in you have a pretty good soft brick. With Safestrap, just reboot into Safestrap and reflash a real ROM. Total panic - 5 minutes of my life I'll never get back, instead of $700, due to my own inattention.) I actually don't want a phone without Safetstrap or something equivalent any more. It's like a desktop you can't install an OS to that comes with multi-boot. If you screw one up, just boot into another one. Even if you only ever run one ROM, it's worth it for the safety alone.
Thread Cleaned. The childish trolling has gone far enough. An honest question was asked, honest answers should be given. Any further trolling will be met with moderator actions.
Thank you for the updates. This will be great. Just need to sit down and make sure it's done right. I appreciate the cleanup and trolling wasnt my intention.
I'm beginning to understand how good safestrap is for me. I did a little checking on how to use it further and yes, it is a good safeguard against blunders.
I'm thinking if I can get a working rom that I like that isnt so touchwiz based but still gives me good s-pen functionality, maybe the phone is worth keeping. I just hate samsung and how they've really f-ed up the os in general, not to mention the amount of crapware that comes with it.
cwis said:
I'm beginning to understand how good safestrap is for me. I did a little checking on how to use it further and yes, it is a good safeguard against blunders.
I'm thinking if I can get a working rom that I like that isnt so touchwiz based but still gives me good s-pen functionality, maybe the phone is worth keeping. I just hate samsung and how they've really f-ed up the os in general, not to mention the amount of crapware that comes with it.
Click to expand...
Click to collapse
Don't blame Samsung for the bloat. Blame at&t! You can also blame at&t for locking the bootloader and not allowing us to have an factory image restore. Praise to the almighty safestrap!
Finding a non touchwiz rom with good s-pen integration is going to be hard. You can blame Samsung for that!
Digital Kat Extreme is good but the s-pen sucks. I may try this one instead: http://galaxynote3root.com/att-gala...r-att-galaxy-note-3-download-booster-working/
Tested the S5 rom works beautifully.
Tested the Note 3 rooted rom works slow, but so did the factory image. WTF???
cwis said:
Tested the S5 rom works beautifully.
Tested the Note 3 rooted rom works slow, but so did the factory image. WTF???
Click to expand...
Click to collapse
So is it fast with S5 ROM? I agree with you that our AT&T Note3 is POS.
I tried many different ROMs. After installing everything I normally use, it's always a dog. Taking 1 second to turn on the screen from sleep should not happen on a Snapdragon 800. I tried removing xposed mod, it becomes bit faster but still found it lagging a little time by time.
I'm going to try the S5 ROM now that you suggest it.
edit: S5 ROM is really fast! I hate touchwiz to death, but this one is fast for real. Instant on from standby. I might actually stick with touchwiz on this instead of Nova Launcher.
edit2: Because the bootloader is locked, there is a bug where the phone never goes into deep sleep mode. I don't really mind because the battery still lasts 24 hours with 1:30 screen-on time. No lag turning on the screen is the thing I really like. I did experience another bug where the screen won't turn on for more than 30 seconds, and I had to force reboot.
So I finally got me a sweet deal and got a second hand XT1053.
Unlocked its bootloader, then flashed T-Mobile´s 4.4.3 and finally the OTA to 4.4.4, because here in Mexico all I was able to get was 4.4.2.
Now, I want to try custom ROMs, and Ive been reading about the procedure.
As any sane person would, I want a nandroid backup before messing around. Im guessing flashing TWRP will take care of this, like it did with my LG L9, right?
Is it wise to do this on the verge of Android L being ported to our Moto X?
How difficult is it to get the phone to a fully stock state (minus the bootlader, of course)? As far as I know, I only need to flash my nandroid backup then flash the stock recovery. Is it as simple as that?
I read somewhere that flashing custom ROMs messed up with Motorola´s active display/voice control, and I assumed they meant that custom ROMs lacked these features because of their proprietary nature. Am I correct? Or does some kind of unrepairable damage will forever afflict these features, even if I get back to stock?
And lastly, what ROM do you recommend? I´d like the active display feature if possible, guess I can do without it. CM theme chooser would be nice too.
Thanks in advance, eagerly awaiting some answers before I take a step forwards.
Attached a screenshot of my phone´s info.
You are right about everything you've mentioned. Good research done for sure! ?
Do a backup with twrp. And yes, you can restore it and flash the stock recovery and you're good for the OTA.
Aosp/cm roms don't have the Moto features. But yes, you can return to stock and have them again. There's a few stick based custom roms that of course still have the features. The other roms, unless something changed, do come with some bugs unfortunately as well.
Most use stock, with gravity box for customizing.
And in case you missed it.... Never try to downgrade from 4.4.4....or you risk your device bricking. You can flash lower version custom roms, cause they won't try to change the bootloader. But don't downgrade stock firmware. Ever. ?
Enjoy!
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
no_un_bot said:
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
Click to expand...
Click to collapse
Until there's a 4.4.4 SBF, yes. That's the safest bet.
newbie needs details
no_un_bot said:
So I finally got me a sweet deal and got a second hand XT1053.
Unlocked its bootloader, then flashed T-Mobile´s 4.4.3 and finally the OTA to 4.4.4, because here in Mexico all I was able to get was 4.4.2.
Now, I want to try custom ROMs, and Ive been reading about the procedure.
As any sane person would, I want a nandroid backup before messing around. Im guessing flashing TWRP will take care of this, like it did with my LG L9, right?
Is it wise to do this on the verge of Android L being ported to our Moto X?
How difficult is it to get the phone to a fully stock state (minus the bootlader, of course)? As far as I know, I only need to flash my nandroid backup then flash the stock recovery. Is it as simple as that?
I read somewhere that flashing custom ROMs messed up with Motorola´s active display/voice control, and I assumed they meant that custom ROMs lacked these features because of their proprietary nature. Am I correct? Or does some kind of unrepairable damage will forever afflict these features, even if I get back to stock?
And lastly, what ROM do you recommend? I´d like the active display feature if possible, guess I can do without it. CM theme chooser would be nice too.
Thanks in advance, eagerly awaiting some answers before I take a step forwards.
Attached a screenshot of my phone´s info.
Click to expand...
Click to collapse
hello, i a newbie to all of this
i have the same device as yours, how did you do that? details if it not much trouble
sherif2015 said:
hello, i a newbie to all of this
i have the same device as yours, how did you do that? details if it not much trouble
Click to expand...
Click to collapse
Hi there, Im at work and cannot explain in much detail, but when I get home i will help you out.
You can send me a private message if you want me to explain in español.
no_un_bot said:
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
Click to expand...
Click to collapse
SBF.Droid-Developers.org hasn't been updated in a while, at least as far as the X (2013 or 1st Gen edition) Roms.
Another possible source is -> http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 however, they don't have a 4.4.4 SBF for the XT1053 either.
And you can keep an eye on https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images since Moto should post the 4.4.4 SBF for the Developer Editions. Eventually an XT1053 (GSM) and an XT1060(VZW) 4.4.4 should pop up there, whenever Moto finally gets around to it.
no_un_bot said:
Hi there, Im at work and cannot explain in much detail, but when I get home i will help you out.
You can send me a private message if you want me to explain in español.
Click to expand...
Click to collapse
Hi sorry for bothering you but i really need your help.
English will be fine .
other users might get here so it will be nice to help them as well
thanks for your time
sherif2015 said:
Hi sorry for bothering you but i really need your help.
English will be fine .
other users might get here so it will be nice to help them as well
thanks for your time
Click to expand...
Click to collapse
Alright, guess everything is out there but I don´t mind.
Can you tell me what system version have you got?
Its displayed under Settings > About phone
reply
no_un_bot said:
Alright, guess everything is out there but I don´t mind.
Can you tell me what system version have you got?
Its displayed under Settings > About phone
Click to expand...
Click to collapse
Kitkat 4.4.2 xt1053
same phone, problems loading roms
I have the same phone, I also recently got second hand.
Moto x xt1053 (gsm) carrier unlocked, currently in kitkat4.4.2, running Kangakat 2 rom (came with it), unlocked bootloader, rooted and using SuperSU, newest version of twrp like 2.8 or something like that.
I want to load a custom rom but am having problems, downloaded P.A.C. and AOKP (two i have tried to use) for the device msm8960 using there stable versions not the nightlies. Went into twrp, created backup, factory wiped, flashed rom and g-apps, was "successful" no errors but on reboot of phone it gets stuck in boot loop and won't start up. for the P.A.C i was able to get into twrp and reflash my back up, for the AOKP twrp kept getting stuck on that teamwin image and i could only finally access it by having the usb cable plugged into my computer. I am not a noob, but definately not an expert.
So did you have any luck flashing a new rom to your phone? Does anyone have any advice for me? I really would like to try some different roms.
Thanks
[emoji15]
I hate Tapatalk for all the time spent writing a quick reply and its gone.
Anyways, first of all, make sure you have the latest recovery available, I remember back with my old phone, funky installations happened if you weren't on the latest recovery. I recommend philz one, has support for some pesky partitions that sometimes get messed and other recoveries won't back up.
Now, in my particular case, I first upgraded my 4.4.2 Nextel stock to 4.4.3 T-Mobile stock using RSDLite, then took the OTA to 4.4.4, and until then I figured I'd play with ROMs. Have had no issues other than something I've addressed on another thread and I ultimately fixed.
My suggestion is going back to full stock then doing everything yourself so you know what's actually going on.
You'll have to flash a custom recovery and then root it again but with an unlocked bootloader that's ezpz.
Remember never to downgrade (that is, flashing a lower android version than what you currently run) stock official images (such as the ones from sbf-developers) because you WILL brick your phone. People say you can downgrade when flashing custom ROMs but I wouldn't risk it, and I don't really see why I'd want that.
Double check whatever file you'll try to flash, always use stuff intended for your model, and when that's not possible verify if other users with your model have reported it works for them. As per the version thing, I believe the most recent development unified models under the GHOST parameter but take my words for what they are, that is, my view on things, you should always make one for yourself.
Ask if you don't completely understand a step BEFORE doing it, there's good people willing to help you out.
Best of luck.
Oh boy I really hope I am just too tired to look and info I've got so far is incorrect. My i337 Got stolen today and I managed to get Galaxy S 4 Active from ATT i537. I looked up only 1 thing before I did because only system I can use is CM11, I mean stock Samsung makes me uneasy if I am on it for more then 15 seconds. Sounds, UI, just feel and look, totally garbage. So now I see that bootloader is locked AND there is no solution to unlock it. Only then we can install some kind of Dual boot thing ? I really hope this is not true. Can I just get rid of everything Samsung and stock and get CM11 ? I don't want to waste space with stock as "not used" system.
Please let me know because like I said I had really bad day with two thugs stealing my phone, spend money on new one and now this. I just rooted it and was thinking like always I get Rom Manager and from there I install recovery ..... but phone is not listed .... I am freaking out a bit right about now. Please let me know if possible on where to start getting custom recovery cause ODIN + tar recovery files gave me magic error or something like that just now.
Thank you guys !
UPDATE: Couldn't sleep.
So I have my new phone rooted with "towel", I install Safestrap and backed up my current ROM (I am on NE3) I see now reason why this dual system needed and stuff. I mean too bad Samsung locking bootloaders and oh well. I have only 2 questions. 1 can I just install latest build from https://download.cyanogenmod.org/?device=jactivelte in to rom SLOT-1 and use it or no. And how much space I can allow for my current ROM and CM I mean I am not planning to have anything on stock so I don't need space at same time I cant make it that when I do want to go on stock I'd have a problem with running it because of not enough space.
Thank you guys once again. I mean If you know few lines ..that's all I am asking. Cause I do see some pros and cons but .. I need straight up answer. Thanks !
Your frustration is understand. Swearing or bad language is not excused in this forum for any reason. Moderate at least title or be prepared to get warning and/or thread locked down.
russiandivxclub said:
Oh boy I really hope I am just too tired to look and info I've got so far is incorrect. My i337 Got stolen today and I managed to get Galaxy S 4 Active from ATT i537. I looked up only 1 thing before I did because only system I can use is CM11, I mean stock Samsung makes me uneasy if I am on it for more then 15 seconds. Sounds, UI, just feel and look, totally garbage. So now I see that bootloader is locked AND there is no solution to unlock it. Only then we can install some kind of Dual boot thing ? I really hope this is not true. Can I just get rid of everything Samsung and stock and get CM11 ? I don't want to waste space with stock as "not used" system.
Please let me know because like I said I had really bad day with two thugs stealing my phone, spend money on new one and now this. I just rooted it and was thinking like always I get Rom Manager and from there I install recovery ..... but phone is not listed .... I am freaking out a bit right about now. Please let me know if possible on where to start getting custom recovery cause ODIN + tar recovery files gave me magic error or something like that just now.
Thank you guys !
UPDATE: Couldn't sleep.
So I have my new phone rooted with "towel", I install Safestrap and backed up my current ROM (I am on NE3) I see now reason why this dual system needed and stuff. I mean too bad Samsung locking bootloaders and oh well. I have only 2 questions. 1 can I just install latest build from https://download.cyanogenmod.org/?device=jactivelte in to rom SLOT-1 and use it or no. And how much space I can allow for my current ROM and CM I mean I am not planning to have anything on stock so I don't need space at same time I cant make it that when I do want to go on stock I'd have a problem with running it because of not enough space.
Thank you guys once again. I mean If you know few lines ..that's all I am asking. Cause I do see some pros and cons but .. I need straight up answer. Thanks !
Click to expand...
Click to collapse
You cannot install CM. Since you have a locked bootloader, it is not possible to install any custom kernels, so ROMs that require a custom kernel (CM, AOSP, or any ROM based off those) will not work. Using SafeStrap you can flash TouchWiz-based ROMs since they can use you stock kernel.
Look in the AT&T S4 forums for ROMs that say they are compatible with SafeStrap, you should be able to use most of those. Since they are meant fir a different phone you'll have to flash the MasterPatch afterwards. A lot of people seen to like the Hyperdrive ROM.
O-T said:
Your frustration is understand. Swearing or bad language is not excused in this forum for any reason. Moderate at least title or be prepared to get warning and/or thread locked down.
Click to expand...
Click to collapse
My bad you're 100% correct I see how to edit op but not tutle.
Devo7v said:
You cannot install CM. Since you have a locked bootloader, it is not possible to install any custom kernels, so ROMs that require a custom kernel (CM, AOSP, or any ROM based off those) will not work. Using SafeStrap you can flash TouchWiz-based ROMs since they can use you stock kernel.
Look in the AT&T S4 forums for ROMs that say they are compatible with SafeStrap, you should be able to use most of those. Since they are meant fir a different phone you'll have to flash the MasterPatch afterwards. A lot of people seen to like the Hyperdrive ROM.
Click to expand...
Click to collapse
Got it. Thanks. I remember back in a day I've been using "theme" that allowed me to have Google stock feel u guess I need to look in this but for now I guess I'll just remove what I can and will suffer until Nexus 6 is in stock and I can afford it. Love that phone. Also I see 5.0 will be out for active next year so it's not that bad. Meanwhile should I do Ota update to latest stock firmware ?
russiandivxclub said:
Got it. Thanks. I remember back in a day I've been using "theme" that allowed me to have Google stock feel u guess I need to look in this but for now I guess I'll just remove what I can and will suffer until Nexus 6 is in stock and I can afford it. Love that phone. Also I see 5.0 will be out for active next year so it's not that bad. Meanwhile should I do Ota update to latest stock firmware ?
Click to expand...
Click to collapse
If you want, you can still root the latest firmware so you have nothing to lose.
My title was abit too long, cause it was copied from a reddit post I made on Cyanogenmod's reddit. R/s means "Receive or Send"
I tried going to Cyanogenmod's Reddit, asking for help with this issue, but there was no luck at all, one user did respond to me and tried to help me out, but hasn't responded for the past 3 days. Looking around for more help, I was directed here to ask. If at all, I'm doing something wrong, can you please tell me.
FYI: My Nexus 6 is using Cyanogenmod 13.0 NIGHTLY, running 6.0.1
Besides that, the reddit post is basically this:
"Please direct me in the correct area, at the moment I don't see much to go to for some help, but I felt like making post.
After a while, I've been using Bell Canada on my phone without any issues, but I never tried voicemails or calls. Recently, trying to get into my telegram account cause they won't send a SMS (For what ever reason), the app offered to call my phone, waiting for the timer to tick down before they call my phone, it just shut it's self off.
I was aware of my phone crashing due to voice mails, cause before I activated my sim card, I had a voicemail that wouldn't go away, trying to view it, the phone would crash. I was hoping this would've been fixed after a couple updates, but it doesn't seem like it was fixed at all. I can't even tell if this issue is my problem (the phone/sim card) or cyanogenmod.
If anyone knows any fixes for this, I'd be really happy, because currently my phone is useless to most things I'd use it for, other than SMS."
On the reddit post, the user that was replying to it did mention something about c-apps not being compatible with Cyanogenmod 13.0 and told me to try to uninstall it, but when I tried to uninstall it through adb, apparently such a directory doesn't exist. I do hope I can get some help here, because I'm currently on a plan with unlimited text and calls, paying alot of money for it, but one feature is completely useless.
--Something I want to add, I tried the same sim card in my HTC One M7 running Android 5.1 with Cyanogenmod 12, calls worked perfectly fine with it.
Please do correct me if I'm doing something wrong, but reading the forum rules, I don't see anything about "bumping", so... Here's my bump.
I haven't had a reply for 5 days now, the possible answer to why my topic wasn't replied to, is most likely because noone knows how to fix this or why this might be happening.
But, I do wish I could get a post or something to show that people do see this, or maybe a post telling me that my issue has a unknown fix.
Edit; I see this rule #5, but, I don't know if that applies to bumping, I don't know how else I could explain my issue. I've explained it the best I've could.
I'm on Bell, and no issues. I don't use CM or CM based Roms though, so the simple way to know if it's rom related is to flash stock, or another non CM based rom.
Other than that, not sure at else to tell you.
Darth said:
I'm on Bell, and no issues. I don't use CM or CM based Roms though, so the simple way to know if it's rom related is to flash stock, or another non CM based rom.
Other than that, not sure at else to tell you.
Click to expand...
Click to collapse
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
MoonieHorse said:
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
Click to expand...
Click to collapse
The procedure to flash any rom is nearly the same. Or use fastboot to flash a stock image.
Just do a nandroid backup before flashing another rom, to be safe. And pic an aosp rom, not cm based.
MoonieHorse said:
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
Click to expand...
Click to collapse
Look in the Nexus 6 Android Development and Nexus 6 Original Android Development subforums, there are tons of options available.
Read over this- [HOW-TO] The Nexus 6 All-In-One Beginner's Guide. A brief guide to clean flashing ROMs. Using TWRP, wipe everything except internal storage (system, data, cache, dalvik). Flash the ROM and then gapps package (some ROMs based on stock don't require gapps so look in the thread). There you go, you have a clean flash of a new ROM.
If you have issues with CM13, try ROMs based off of AOSP like Chroma, Pure Nexus, Dirty Unicorns, AOSiP, etc...
Darth said:
The procedure to flash any rom is nearly the same. Or use fastboot to flash a stock image.
Just do a nandroid backup before flashing another rom, to be safe. And pic an aosp rom, not cm based.
Click to expand...
Click to collapse
I'll keep this in mind for the near future then. I don't really want to flash a different rom on my phone cause of... Well, the known risks of doing so aka possibly turning your phone into a brick or losing all the data.
What I'll do is, I'll hold on abit with Cyanogenmod, see if they release any fixes and go from there, maybe even bump them about said issues to see if this is known or not.
Thank you for your help though, I'm sure I'd come back here again if I needed some help again.
MoonieHorse said:
I'll keep this in mind for the near future then. I don't really want to flash a different rom on my phone cause of... Well, the known risks of doing so aka possibly turning your phone into a brick or losing all the data.
What I'll do is, I'll hold on abit with Cyanogenmod, see if they release any fixes and go from there, maybe even bump them about said issues to see if this is known or not.
Thank you for your help though, I'm sure I'd come back here again if I needed some help again.
Click to expand...
Click to collapse
You will not "brick" flashing a rom. You can have issues, sure, but that's what the nandroid backup is for.
Honestly, if you're that worried, I'd restore the stock image and not tinker with it.
But if you leave it as is, I doubt you'll fix your issue.
Hi there, Merry Christmas to y'all everywhere( We don't have Christmas here in my country, anyway.
Ok. Here we go:
I wanted to give my Mi A2 to someone else( completely working and smooth like it should be, has AICP Rom for long time), since that person doesn't like totally vanilla ROM, I decided to flash a more feature packed ROM on mi a2(in this case Pixel Experience), I do this, clean flash,following the usual procedure since I'm used to flashing ROM and stuff
after booting up, everything is sluggish and laggy, even in Phone Setup Wizard, started using phone, setup the apps needed, still laggy and sluggish.. Until that person starts complaining that phone is seriously slow, I say "OK, maybe I did something wrong or maybe this ROM has problems that I'm not aware of" I flash another ROM (Lineage OS), I do the previous stuff, still sluggish, just like previous ROM, exactly same scenario, it doesn't even matter if I have installed apps or just flashed phone, still lags.
Frustrated, why A2 became like this? Did it hit number of flashing rom attempts?(LOL, such thing exists? Flashing cant slow down the phone unless that ROM has problems) decided to go back to stock ROM, successfully flahed stock, boot up, still sluggish and laggy.. I don't know wth is going on...
My mind is racing:
"what is happening?"
"The phone was just fine when on AICP, after flashing, what happned?"
"Is it my fault? "
"Should I have just used factory reset instead of flashing ROM?"
Guys, there is something wrong
,will update the post with logcat and recording if needed and I have the time to do it. Feel free to ask questions.
TIA
Encrypted? Maybe encryption has some problems.
Kernel? Tried to flash just another kernel?
And how about frequencies? Are they ok? Phone is getting hot?
It's risky, but the last thing to do is to reflash other partitions too, like vendor or others (if you have them), maybe one of them get corrupted.
Ps: I'm currently on Android 12 DerpFest (Build of 26Nov) and I can tell you that after 2 months of usage my UI is getting really laggy and I'll change ROM soon. Maybe it's because Android 12, but I'm just letting you know.