• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Verizon] Wrong time on TWRP

valorian

Android Expert
I recently rooted my SGS3 and am using TWRP recovery. Along the to of the TWRP screen it has the wrong time even though I have the correct time zone selected. It also uses the wrong date and time when using the time stamp when doing a backup.

Anyone know how to correct this? I'm not able to find any place to adjust the date and time in TWRP.
 
As I understand it no recoveries can have the correct time because access to the network doesn't exist in recovery mode and therefore the correct time cannot be accessed.
 
One of the prices we pay for embracing "the cloud". Without the cell network the phone doesn't even know the time of day. At least with TWRP you can name the nandroid you are making, so I encode the date and time into the file name. :)
 
Also makes sense . . .

Thanks. I switched from Clockworkmod to TWRP specifically because TWRP lets me name the nandroid before I make it. With CWM I had to remember to go into the clockworkmod folder and find the nandroid with the "wayback machine" name and rename it after the fact. ;)
 
I agree. TWRP seems a far superior recovery. Actually if you have RomToolbox installed, you can go into rom management & flash recovery`s right from the app meaning that you can flash the latest TWRP or switch to CWM if you want, without the need to flash from recovery to do so.
 
Can you also tell Rom Toolbox to create a nandroid, rather than having to boot into TWRP and do so manually? That would be a handy feature. I have not tried Rom Toolbox.
 
Absolutely . . . That's how I create & manage my backups. Romtoolbox is a great root user's tool. From the rom management section, you can create,rename(I think),manage & recover to any of your existing backups. The app even has a built in terminal emulator. You should definately get it !
 
While I agree that Rom Toolbox is a great app, personally I prefer to do backups/restores/flashes etc thru recovery.
I'm not quite comfortable to let an app do that yet :) But that's just me.
 
So far all of the recovery's I've done with Romtoolbox are present & accounted for . . . Fortunately I haven't had to recover from any of them yet so I can't advise on the quality/reliability of the recovery process. I can only assume that it would work fine.
 
While I agree that Rom Toolbox is a great app, personally I prefer to do backups/restores/flashes etc thru recovery.
I'm not quite comfortable to let an app do that yet :) But that's just me.

Certainly nothing wrong with that line of thinking. There is something to be said for having important processes such as these happening directly under control and supervision. I have used nandroids many times to recover in situations ranging from instabilities trying out a ROM to fixing a device that has become nearly unusable.

I've also experienced more than one SD Card suddenly deciding to be "corrupt" and refusing to even be reformatted. So I also keep copies of my nandroids and full SD Card content on a PC and on Bluray so I can replace a dead SD card. It always just "happens" suddenly out of the blue, with no warning whatsoever. I'm always careful about dismounting USB connections, so I have no idea what causes the cards to suddenly die. It has happened across multiple devices.
 
I recently rooted my SGS3 and am using TWRP recovery. Along the to of the TWRP screen it has the wrong time even though I have the correct time zone selected. It also uses the wrong date and time when using the time stamp when doing a backup.

Anyone know how to correct this? I'm not able to find any place to adjust the date and time in TWRP.

I had the same problem, but I guess it starts when flashing TWRP on a device that has not the right date/time set before flashing TWRP. (I was too eager to change ROM on my device, so I never bothered to set time/date on the device's initial system before flashing TWRP - That's why many other users do not have any problem at all with time/date of TWRP, they simply used their device already with the right time set before flashing TWRP).
So after flashing TWRP I noticed that the time was wrong (and when making a backup I saw that even the date was wrong). It showed that it was the 1st January of 2014 (default date when not seting date on this specific device).
So, after some time I found out, that you have to FISRT SET TIME/DATE on your device's system and THEN flash TWRP. TWRP will then get the (right) time/date of the system on your device.
Another thing that was interesting though, is that TWRP's wrong date/time would even show in the system of the device, if the device was set to get time/date from the network but couldn't connect to it.
So it seems that TWRP get's its time/date setting from the device's system when it's initially flashed, but then the system of the device takes the date/time from TWRP, as it is like a layer "before" the system.
So to cut things short, if you have TWRP flashed and it shows wrong time, try flashing another recovery (CWM) or a stock ROM (over Odin), set the right time on your device and then finally flash TWRP again. (TWRP is much smoother than CWM in my opinion and worth the hussle).
All the above were executed on a Galaxy S5 SM-900F and by system I mean the android version installed on the device.
Good luck!
 
I had the same problem, but I guess it starts when flashing TWRP on a device that has not the right date/time set before flashing TWRP. (I was too eager to change ROM on my device, so I never bothered to set time/date on the device's initial system before flashing TWRP - That's why many other users do not have any problem at all with time/date of TWRP, they simply used their device already with the right time set before flashing TWRP).
So after flashing TWRP I noticed that the time was wrong (and when making a backup I saw that even the date was wrong). It showed that it was the 1st January of 2014 (default date when not seting date on this specific device).
So, after some time I found out, that you have to FISRT SET TIME/DATE on your device's system and THEN flash TWRP. TWRP will then get the (right) time/date of the system on your device.
Another thing that was interesting though, is that TWRP's wrong date/time would even show in the system of the device, if the device was set to get time/date from the network but couldn't connect to it.
So it seems that TWRP get's its time/date setting from the device's system when it's initially flashed, but then the system of the device takes the date/time from TWRP, as it is like a layer "before" the system.
So to cut things short, if you have TWRP flashed and it shows wrong time, try flashing another recovery (CWM) or a stock ROM (over Odin), set the right time on your device and then finally flash TWRP again. (TWRP is much smoother than CWM in my opinion and worth the hussle).
All the above were executed on a Galaxy S5 SM-900F and by system I mean the android version installed on the device.
Good luck!

That's an interesting fix you have. But I can attest that I have never rooted or flashed a recovery on an Android device until after I ran it for several days to make sure I didn't have to return it. That means I did have the right date and time set when I eventually rooted and installed the recovery. I've used both CWM and TWRP (preferring TWRP) over several devices and never had the recovery date and time right. Having asked both the teams who write these recoveries about this issue more than once, they have always told me there is no way to get the date and time correct. So when I make my weekly nandroids I rename them (when possible) or use the screwed up cryptic name as a way to keep track of which ones I am doing that week. The date and time in TWRP does change over the passage of real time, it's just wrong.
 
Back
Top Bottom