Is there a way to learn when you last changed rom or flashed an image ?
I would like to know how long I stayed on one rom but I can't remember when I flashed it.
So I would like to know if there's a way to know when the OS was installed (similar to the uptime in fact)
There are probably several ways to do this, like checking when a system folder was created or edited, but I think the easiest way is to just check your Google account security settings for when your device was authorized, assuming you logged into your account the same day you set up your new ROM.
And by the way, questions should be posted in the Nexus 5 Q&A, Help & Troubleshooting subforum
The ROM you flashed, if it was current when you flashed it, will have a build date in settings/about device.
Related
This has probably been covered before but I couldn't find the topic and I apologize if there is a specific area for these sorts of questions and I ask that this topic be moved there if need be. Anyway, I have an unlocked Galaxy S3 which I purchased off Ebay and activated on MetroPCS. The activation went fine, the IMEI is clean, but my question is, if I install a custom ROM will it change my IMEI? And if so, what sort of problems could that cause for my phone being able to use data or make phone calls? I've never flashed a custom ROM to a phone before so I'm not sure if it CAN change the IMEI, I was just warned by a friend that after he flashed his, the last few digits for his changed and he had to call his provider and it voided his contract. I have installed custom ROMs before but they were on an android based MP3 player so I never had to worry about an IMEI, however I enjoyed the special features that ROM had compared to the stock ROM and was wanting to have similar features on my phone.
Also on an unrelated note, my girlfriend had an old Galaxy S2 that sat in her closet for about 2 years. It had stopped working so she packed it up and was about to throw it away until I decided to fiddle around with it. It's model number is SPH-D710 so it doesn't look like a traditional Galaxy phone, so holding the home button does not help me boot into download or recovery mode. My problem with it, it doesn't boot up, it stays at the Galaxy SII screen and doesn't move passed that, Odin fails when attempting to flash a ROM onto it (Custom or recovery), and holding vol up+home+pwr does not boot it into recovery. She told me her brother previously rooted it with a custom ROM (No idea which) and it worked for some time before ****ting the bed. My theory is that he did a poor job at flashing and somehow removed the recovery menu completely and so the phone is stuck as a soft brick. That would mean my only option to save it would be to flash it but it fails every time. Is there anything more I can do to save it or should I just scrap it for parts?
EDIT: I went for it and installed it. IMEI is still the same and phone works fine as a phone. Currently my only issue is that it can't read my SD card nor can I copy files to or from my SD card to my computer. I have windows 8 and it says unspecified error when I try. Is this a problem with cyanogenmod or did I kill my SD card when I flashed?
Hi there,
You'd be best served asking for help from the experts who own your device here:
[Q&A][SGS2][Newbies][Experienced Users][RCs] New members friendly Q&A thread
Good luck
Hello,
I've searched high and low and I'm not having any luck with this so I thought I would post here to see if anyone can point me in the right direction.
I have an AT&T Galaxy S6 Active (I got it last night) and I can't get it to update to Android 5.1.1 . The current Android version is 5.0.2 Baseband version G890AUCU2AOF4
My wife's phone, which is exactly the same as mine (only the color is different) has updated to 5.1.1 so I know it exists.
Things that I have tried:
1. I have updated all of my apps.
2. I have done a factory reset and tried again.
3. I have gone into settings>device>applications>application manager>all>Google Services Framework Cleared the data, forced stop & cleared cache and tried to update. Doesn't work.
4. I've tried turning off the auto date and time and set the date 24 hrs in the future to try and spoof the AT&T server into letting me have it. I'm told that "Current software is up to date" "You may check again in: 167 hours"
Other than downloading the image myself, and trying to manually update... Is there anything I can do to make it update on its own? What am I missing?
Thanks in advance for your time and consideration!
Adam
Hello,
Welcome to XDA.
Post your question in the forum linked below.
http://forum.xda-developers.com/galaxy-s6/galaxy-s6-active
The experts there may be able to help.
Register an XDA account to post and reply in the forums.
Good day, my potential saviors,
I really couldn't find a better fitting forum, maybe I'm just blind but...
I'm not that "all-knowing" when it comes to this rooting thing which might be the reason the thing that happened did happen...
I updated my Nexus 6 (shamu) from CyanogenMod 12.1 (Android 5.x) to Version 13 (Android 6.0.1) yesterday and had Wi-Fi the whole day. This morning I went out to do my daily thing when I found that I didn't have connection to my cellular network.
Because there are only nightlies at the moment I thought I maybe should try the next version, some bugs are normal after all.
So I was home, downloaded the update and tried to install it just like always but when I arrived in my Recovery it wanted me to enter some pattern I can't recall to have ever entered and it wants it every time I try to get into Recovery. So here lies the problem... How did that get there? And how can I bypass this?
I thought maybe I could re-flash my Recovery to get that pattern deleted or something but I can't even flash anything because I don't have access. I can see all my settings but I don't see the device on my PC.
Please help me!
Greetings, Null.
Edit: Found the reason... Seems like CM13 found it necessary to use my Lockscreencode for everywhere... and since it was 4x4 TWRP was unable to let me put it in I guess.
NullFünf said:
Good day, my potential saviors,
I really couldn't find a better fitting forum, maybe I'm just blind but...
I'm not that "all-knowing" when it comes to this rooting thing which might be the reason the thing that happened did happen...
I updated my Nexus 6 (shamu) from CyanogenMod 12.1 (Android 5.x) to Version 13 (Android 6.0.1) yesterday and had Wi-Fi the whole day. This morning I went out to do my daily thing when I found that I didn't have connection to my cellular network.
Because there are only nightlies at the moment I thought I maybe should try the next version, some bugs are normal after all.
So I was home, downloaded the update and tried to install it just like always but when I arrived in my Recovery it wanted me to enter some pattern I can't recall to have ever entered and it wants it every time I try to get into Recovery. So here lies the problem... How did that get there? And how can I bypass this?
I thought maybe I could re-flash my Recovery to get that pattern deleted or something but I can't even flash anything because I don't have access. I can see all my settings but I don't see the device on my PC.
Please help me!
Greetings, Null.
Edit: Found the reason... Seems like CM13 found it necessary to use my Lockscreencode for everywhere... and since it was 4x4 TWRP was unable to let me put it in I guess.
Click to expand...
Click to collapse
Hi
Thanks for using XDA Assist.
Maybe this post will be helpful
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
Click to expand...
Click to collapse
If you're still having issues then point your question here > Nexus 6 > Nexus 6 Q&A, Help & Troubleshooting or in the friendly > Nexus 6 > Nexus 6 Q&A, Help & Troubleshooting > Noob Friendly Q and A Help Thread. Experts there may be able to help you.
Good luck
Thread closed.
First of all, i hope I'm not the only one in this forum!
I just found my old cellphone and want to get most of it, and good to mention now, there is almost noway to use any application because this is an old Android rooted version. I even not able to use my google account to get google play!
I know what download and recovery mode are, but it's shame to say i don't know how to get there in this phone! believe or not there is no file manager here! Now I'm thinking how did i pass days with this phone!?
I did a reset factory and hoped to see some improvements, but nothing got better!
So if anyone here and read my post please help me to get a fresh start
Android Version: 2.3.3
HTC Sense Version: 2.1
Baseband Version: 12.56.60.25U_26.10.04.03_M
Kernel Version: 2.6.35.1-gd2564fb
Best advice: start reading the threads in the General section. There should be multiple threads on how to root and to get S-Off on this device.
Custom ROMs up to Android 6.0.1 are available, and I currently have Android 5.1.1 on my roommate's old phone. However, on these old devices bootup times run nearly ten minutes, not including app optimization, and overall performance suffers. Android 6.0.1 will not install at all unless the /data partition is moved to the MicroSD card as the /system partition is too small.
If looking to tinker, the unofficial build of Cyanogenmod 12.1 for this device is likely the best option, as there's no need to move the /data partition.
EDIT: Did not notice the date of the original post.
Not sure if this really should be going to the noob friendly thread, but since it is a couple of questions covering various Android related issues, I figured that I will make it a separate thread after all.
1. Sometime updating an Android version would also end up updating the bootloader, at time rendering it impossible to downgrade again. Can this also happen in custom ROM (e.g. Lineage). I am asking this because I am thinking of custom ROM with newer Android version on my Galaxy S7, but may want to revert to a relatively old Android 7.0 after I am done testing.
2. Do file systems (the way application, application data are stored in the system and other information) etc. tend to stay the same as stock for a given Android version? For example between stock Android 7.1 and Lineage 14.1.
3. Same question as question 2., but between major Android versions (e.g. stock 7.1 and stock 8.0).
4. On rooted devices, can you usually update major version update without losing any data, and is it usually trouble free?
Feel free to skip reading this part, but for some background information, the reason I am asking all those questions is because one of the app I tried to restore via Titanium Backup and Swift Backup both failed. The application itself launches properly, but as soon as I restore the data, it would instantly crash and close. My guess is that this is probably caused by attempt to go from Android 6.0 to 11.0. Maybe it is the backup software or maybe something changed in the way files are stored, but whatever the reason, it just won't work.
So I am thinking that my best option is to try it to restore it on an Android 7.0 phone that I have (also on the way to be retired, and if it works, update to Android 8.0. Since Android 8.0 was the last officially released major version for that phone, and I was thinking that if it does work, perhaps I could alternatively go for an early Lineage ROM, then make gradual updates up to Android 11.0 and see if it helps the app remain unbroken. And then if it does work, perhaps I could then make a backup then restore it on the other new Android 11.0 phone that I have.
All in all, it is a silly amount of work to do just for one app.. but it is important to me, so I will exhaust every option that I can think of to find a solution.
Thanks!