My S3 is setting backup recovery file dates that show as 1970, yet the system date/time seems to be correct. I found some older backup files stored on my laptop (moved from the phone long ago) that had correct dates--so this is something that apparently changed somewhere along the way (OS upgrade?).
Does anyone know of this problem cause and a fix?
If you're using TWRP 2.6.x then it is a known issue. From what I hear updating TWRP fixes that but a lot of people have said problems arise with creating or restoring backups with it. Probably the problems with KitKat and the storage changes. I just amend the date when I make backups.
pre4speed said:
If you're using TWRP 2.6.x then it is a known issue. From what I hear updating TWRP fixes that but a lot of people have said problems arise with creating or restoring backups with it. Probably the problems with KitKat and the storage changes. I just amend the date when I make backups.
Click to expand...
Click to collapse
I am on CWM 6.0.4.7. I hadn't thought about it being an issue with the recovery, but that makes sense; since the backup is done in recovery with the OS not running, and the only time in the phone comes from the network, then there may not even be a software call that can access current time when recovery is trying to make a backup.
But I did have some older ones that had a then-current date on them. ????
Now very puzzled.
Yeah that happened to me too. It got to a point where I couldn't even name them via ROM manager. I had to do the backup in recovery, reboot, then name it myself. Otherwise I never knew which were which.
ZehelSitchel said:
Yeah that happened to me too. It got to a point where I couldn't even name them via ROM manager. I had to do the backup in recovery, reboot, then name it myself. Otherwise I never knew which were which.
Click to expand...
Click to collapse
I *BELIEVE* it is because a time is not available to the backup code while in recovery (OS not running), but I don't see why, when the backup is commanded from within ROM Manager (OS is running), that the date/time could not be stored in a file to be used in the filename by the recovery code running the backup.
1970-01-01 is time 0 in the POSIX time system on linux. Its presence suggests that either the recovery app didn't define the system clock to make it available, or didn't give the file system commands permissions to use it.
The system clock can be available in recovery. I use Philz custom with CWM. Both the backup folders and files have correct dates and times.
You can choose to use TWRP format under Philz and the files are supposed to be available to TWRP, in the default folder. I don't know if that will fix the date issue. I'll try on my S3 and report back.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Proper date when using TWRP format under Philz - It's open source, so the TWRP team should look at what he does.
Here's a screen shot from xplore, looking at the backup folder,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Philz thread
http://forum.xda-developers.com/showthread.php?p=39433458
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Thank you for that reply--very helpful!
Quick question: does Philz recovery put boot-to-recovery entry in the long-press-power menu?
LATER:
Drilled through things starting at the link you provided. Apparently I am supposed to use the d2lte version for my ATT S3. But when I get to the (appropriate, I think) download page, there are 'tons' of files listed...
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
????
Also, for completeness, I am running rooted, but standard ATT ROM at 4.1.2; the 4.3 OTA update always fails to install.
Yes, you want d2lte version. Should work on any JB rom, including 4.1.2.
If you have option to boot to recovery from long press power button, then it will still be there and should work. That's how I do it, avoiding power down and button combo. Philz doesn't add that reboot to recovery option. It's an option on some roms, like cyanogen, or you can find a free app on Google play to do it.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
laughingT said:
Yes, you want d2lte version. Should work on any JB rom, including 4.1.2.
If you have option to boot to recovery from long press power button, then it will still be there and should work. That's how I do it, avoiding power down and button combo. Philz doesn't add that reboot to recovery option. It's an option on some roms, like cyanogen, or you can find a free app on Google play to do it.
Click to expand...
Click to collapse
I do not have it now--I thought the Recovery added it. I always enter recovery from within ROM Manager--don't even remember the key technique. Will doing it from ROM Manager still work if I go to Philz?
I don't know. You could check the thread in the link I posted above. If you search the thread, I expect you find the answer.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Related
okay, i've searched the forums and couldnt find anything on this, so don't flame me for posting this. I just tried to backup a ROM in CWM Recovery on my permrooted and S-off G2. it got to "Backing up system" and then said "Can't mount /system/!" and stopped the backup. is there something i'm not doing right here? Any help would be appreciated.
Mardenator said:
okay, i've searched the forums and couldnt find anything on this, so don't flame me for posting this. I just tried to backup a ROM in CWM Recovery on my permrooted and S-off G2. it got to "Backing up system" and then said "Can't mount /system/!" and stopped the backup. is there something i'm not doing right here? Any help would be appreciated.
Click to expand...
Click to collapse
Which ROM are you using?
i was using a Gingerbread ROM, and i booted into recovery to make a backup so i could try a MoDaCo ROM. i tried doing the backup and it said "can't mount /system/!".. but i havent been able to reproduce the issue. maybe it was a one-time thing.
I have been experiencing this problem for over a week now. Same error I receive when I try to flash a file using Rom manager.
This problem happened to me after running fix permissions in Rom manager. I've had no luck on this good thing I have my phone stable.
Thanks for any help on this.
I'm runninng ROM CM 6.1.1
Mardenator said:
i was using a Gingerbread ROM, and i booted into recovery to make a backup so i could try a MoDaCo ROM. i tried doing the backup and it said "can't mount /system/!".. but i havent been able to reproduce the issue. maybe it was a one-time thing.
Click to expand...
Click to collapse
Your problem is that the Gingerbread ROM uses EXT as its format instead of yaffs. CWM was written with yaffs in mind. I had the same problem with the Gingerbread ROM, but I was able to get the Froyo ROM back on and CWM worked again.
ThuggishSouljah said:
I have been experiencing this problem for over a week now. Same error I receive when I try to flash a file using Rom manager.
This problem happened to me after running fix permissions in Rom manager. I've had no luck on this good thing I have my phone stable.
Thanks for any help on this.
I'm runninng ROM CM 6.1.1
Click to expand...
Click to collapse
Try flashing it through recovery. I only use ROM Manager to download the ROMs in question.
I am having the exact same problem. Gingervillian 1.5. So the solution is to go back to the froyo rom and this will fix itself? Forgive me I am a noobie.
you need to flash CWM3.0 or above. flashing ginerbread formats system into ext4. earlier versions of CWM on read up to ext3.
thanks button at the bottom.
I want to tap the thanks button -- i really do -- but I am running version 3.0.0.7, I am not sure if that is the answer. Thanks for the fast response by the way.
Now the recovery is listed as clockworkmod 2.5.1.3 -- but I cant find any later versions.
ncmish said:
I want to tap the thanks button -- i really do -- but I am running version 3.0.0.7, I am not sure if that is the answer. Thanks for the fast response by the way.
Now the recovery is listed as clockworkmod 2.5.1.3 -- but I cant find any later versions.
Click to expand...
Click to collapse
No that is not the awnser, you are running Rom Manager 3.0.0.7, you need to install ClockWorkMod Recovery 3.0.0.5 they are two diffrent things, you will know if you have flashed ClockWorkMod Recovery 3.0.0.5 by booting into recovery and if the letters are green you do not have the right recovery for GingerBread, the letters will be orange if you have CWM recovery 3.0.0.5(GingerBread Recovery) installed.
Here is a LINK to the CWM recovery for Gingerbread 3.0.0.5
You need to flash the new recovery (CWM 3.0.0.5) in Fastboot mode or use the Flash_image method(this will work for any of the Gingerbread Roms CM7, GingerVillian, etc.).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is CLockWorkMod Recovery 3.0.0.5 for Gingerbread 2.3 Roms.
This is ClockWrokMod recovery 2.5.1.3 for Froyo 2.2 Roms.
You are a $%^# animal! Damn that worked like a champ. This android stuff is like greek to me but I am amazed at what many in these forums know.
Thanks again and here is your thanks!
I tried the flash_image method but it did't work (got stuck at white screen with htc logo when rebooted). I was lucky to be able to reflash 2.5.1.3 from Rom manager. I'm running a gingerbread rom (which I love) but I dont have the guts to try out the fastboot method (eng hboot is scary stuff..).
Huh... if u of clock work u should download a rom then mount ur sdcard put the rom in ur sdcard and flash the new rom with clockwork.
Sent from my HTC Vision using XDA App
lainvalenajr said:
Huh... if u of clock work u should download a rom then mount ur sdcard put the rom in ur sdcard and flash the new rom with clockwork.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
It doesn't matter now. ROM Manager is flashing 3.0.0.5, which now works with Gingerbread and Froyo ROMs.
Ok, maybe a stupid question, but I'm running 2.5.1.3 and I clearly need to update my Rom Manager. I've tried redownloading it, but it always launches as 2.5.1.3. I notice that there is an option when I launch it which says Flash ClockworkMod Recovery. Is that what I need to choose to update to the latest version? I don't want to click it and find out it reformats to phone or something.
EDIT: I figured I might as well click it and find out what happens. Turns out that is the solution. I'm now able to back up CM 7.0.3. Whew!!
Okay, so i don't think this is a hardware issue (it could be), because the phone is brand new. I flashed the omega rom to my hone and what i think happened, is somehow when i was recovering my data with titanium backup, the drivers that read the sim card and allow the s pen to work got corrupted. Now, i tried to flash the stock att rom to my phone, but every time i do that, a CWM based recovery by X____ (dont know the name) runs and re roots my phone, cancelling the flash.
In titanium backup did you restore system+user apps or just user? And try to use ODIN to get back to stock. The stock images can all be found in the note II toolkit thread
im not sure what i did, but all the data from titanium backup is gone. what im really trying to do is restore my phone to what it was when i first got it.
also, i have a backup of my phone before i flashed the omega rom on TWRP recovery, but i cant figure out how to boot my phone into TWRP recovery.
To get into recovery just hold power home and volume up. But if you just want to get back to stock odin is your best bet
I know how to get into recovery, but i have CWM and TWRP, and i want to get to TWRP, but my phone automatically goes to CWM
You cant have TWRP and CWM... you only have one recovery partition
hmm, well the TWRP backup files are still on my phone, which i need..
I think CWM can restore TWRP backups but i may be wrong. Otherwise you can put the CWM flash able TWRP install file on your card and do it that way
could you maybe explain how to do that?
Download the zip here http://goo.im/devs/OpenRecovery/t0lteatt then flash it from CWM
i put the img on my phone..how do i flash it from CWM?
nevermind, did it with goomanager
so even when i install twrp recovery, it still boots to CWM..hmm any ideas?
That means that TWRP didnt install. Just use odin seriously its pretty simple
Dude ive tried multiple times, every time i flash the stock rom, the cwm based recovery comes up and says something like "cancelling flash" and it reroots my phone and nothing ends up happens
Can you get a picture of it?
got one
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
K how did you root initially? Because it looks like it is encountering an error and falling back to the root exploit. Anyone else feel like chiming in about this?
i followed all steps on this video http://www.youtube.com/watch?v=O6BweCW5ck8 including initiallly installing TWRP recovery. I also installed the omega rom, which was when i starten experiencing issues. I made a backup prior to the flashing of the omega rom, but that was on TWRP, and as you already know i cant seem to install twrp.
Omega... isnt that a N1700 rom? cant seem to find it on the i317 forms. That may be your issue
Okay, so here's the story.
I was using clockworkmod to flash a new ROM on my E4GT; I accidentally flashed a file which I thought was a 'safe' recovery so I could go back to ICS from JB. Well it was not a safe recovery as I thought. Before doing this, I did a format all as usual, so I now have no ROM on the phone. When the phone rebooted, it came up to the Android System Recovery <3e> menu. Normally this wouldn't be a problem for me since I could just put it in download mode and fix this via Odin, however, my USB port on the phone does not work. I charge the phone using an external battery charger.
Is there anything I can flash on the stock recovery via the external SD that will rectify my issue, without USB?
I will continue to Google this problem, but I would appreciate any additional help.+
So far, it's looking like my only option is to JTAG this huh? Hoping there is something out there I can flash from stock recovery, I mean it's not like I tried to flash an international ROM or anything....hmm
I had success flashing this in stock recovery once-http://forum.xda-developers.com/showthread.php?t=2059714
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloading now... Will report back my findings. Thanks for the help!
bilgerryan said:
I had success flashing this in stock recovery once-http://forum.xda-developers.com/showthread.php?t=2059714
Click to expand...
Click to collapse
I tried downloading and flashing the CWM Flashable FL16 Pure Stock ROM (Odexed) to no avail. It sat for a minute like it was going to do something, then came back with the signature verification failed message and rebooted. This is the ,zip you were referring to, correct?
mangomango said:
I tried downloading and flashing the CWM Flashable FL16 Pure Stock ROM (Odexed) to no avail. It sat for a minute like it was going to do something, then came back with the signature verification failed message and rebooted. This is the ,zip you were referring to, correct?
Click to expand...
Click to collapse
No, GB27, and like I said it worked once. It really depends on what recovery you flashed. You need to flash the matching ROM.
bilgerryan said:
No, GB27, and like I said it worked once. It really depends on what recovery you flashed. You need to flash the matching ROM.
Click to expand...
Click to collapse
I see what you mean. Unfortunately, same thing there. Hung for a bit then signature verification failed. I'll see what else I can find, but I appreciate your help thus far.
My recovery show the following:
----------------------------
Android System Recovery <3e>
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
#manual mode#
--Applying multi-CSC-...
Applie the CSC-code : unknown
Sucessfully applied CSC
--------------------------
This is before I even attempt to flash anything. Anyways. I'll keep looking, but thanks again!
mangomango said:
I see what you mean. Unfortunately, same thing there. Hung for a bit then signature verification failed. I'll see what else I can find, but I appreciate your help thus far.
My recovery show the following:
----------------------------
Android System Recovery
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
#manual mode#
--Applying multi-CSC-...
Applie the CSC-code : unknown
Sucessfully applied CSC
--------------------------
This is before I even attempt to flash anything. Anyways. I'll keep looking, but thanks again!
Click to expand...
Click to collapse
Do you know what recovery file you flashed? That would help more, every stock recovery says all that stuff.
bilgerryan said:
Do you know what recovery file you flashed? That would help more, every stock recovery says all that stuff.
Click to expand...
Click to collapse
I get exactly what you're saying now. For some reason I flashed GB08_STOCK_NOCWM.zip or something along those lines. Now I am searching for a GB08 zip file and I think I should be good. Everything I can find is in exe format though...
It all makes sense now though. I'm used to HTC phones where I can just use whatever recovery to flash a ROM and not have to worry about different modems/kernels etc. I am crossing my fingers that this works. You've been a tremendous help today.
mangomango said:
I get exactly what you're saying now. For some reason I flashed GB08_STOCK_NOCWM.zip or something along those lines. Now I am searching for a GB08 zip file and I think I should be good. Everything I can find is in exe format though...
It all makes sense now though. I'm used to HTC phones where I can just use whatever recovery to flash a ROM and not have to worry about different modems/kernels etc. I am crossing my fingers that this works. You've been a tremendous help today.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=38271954
Hello, I was flashing a couple roms last night and I decided after trying Paranoid Android Legacy and CarbonROM that I just wanted to do a clean wipe and go back to Cyanogenmod. Doing a full wipe has never been a problem for me except now in CWM I can't get root to stick, no matter what I do, and whenever I'm in recovery, I can't adb push or sideload anything to my device. I even tried installing drivers through Zadig to make a connection and that didn't work. Anyone know how I can get root to stick?
PandaDan said:
Hello, I was flashing a couple roms last night and I decided after trying Paranoid Android Legacy and CarbonROM that I just wanted to do a clean wipe and go back to Cyanogenmod. Doing a full wipe has never been a problem for me except now in CWM I can't get root to stick, no matter what I do, and whenever I'm in recovery, I can't adb push or sideload anything to my device. I even tried installing drivers through Zadig to make a connection and that didn't work. Anyone know how I can get root to stick?
Click to expand...
Click to collapse
Use Philz Recovery. It is the best one out there. Even has an option to push root in Philz Settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My ROM: WICKED X
bilgerryan said:
Use Philz Recovery. It is the best one out there. Even has an option to push root in Philz Settings.
My ROM: WICKED X
Click to expand...
Click to collapse
Am I going to have to use Odin or Heimdall? I'm not really good with either one of those, but it seems like the only choice I have.
PandaDan said:
Am I going to have to use Odin or Heimdall? I'm not really good with either one of those, but it seems like the only choice I have.
Click to expand...
Click to collapse
Neither. Download the recovery that ends in ".zip" (there are three different files, another is .tar) then go into recovery and flash it. Then go to the "Reboot Recovery" option. And once it reboots you'll be in Philz Recovery.
My ROM: WICKED X
bilgerryan said:
Neither. Download the recovery that ends in ".zip" (there are three different files, another is .tar) then go into recovery and flash it. Then go to the "Reboot Recovery" option. And once it reboots you'll be in Philz Recovery.
My ROM: WICKED X
Click to expand...
Click to collapse
But the problem is that I can't get anything pushed over to my phone while in recovery. Adb says it can't find my device, even though I have drivers installed for it.
PandaDan said:
But the problem is that I can't get anything pushed over to my phone while in recovery. Adb says it can't find my device, even though I have drivers installed for it.
Click to expand...
Click to collapse
Then use Mount USB under Mounts & Storage or boot the phone and download the file and go back to recovery and flash it.
My ROM: WICKED X
bilgerryan said:
Then use Mount USB under Mounts & Storage or boot the phone and download the file and go back to recovery and flash it.
My ROM: WICKED X
Click to expand...
Click to collapse
I don't have that in my CWM. All I have is mount system, cache and data, and then format those along with data/media. I formatted everything, literally everything, all I have is recovery. Its never been an issue before though, so I dunno what the issue is.
PandaDan said:
I don't have that in my CWM. All I have is mount system, cache and data, and then format those along with data/media. I formatted everything, literally everything, all I have is recovery. Its never been an issue before though, so I dunno what the issue is.
Click to expand...
Click to collapse
So flash a ROM or restore a backup.
My ROM: WICKED X
bilgerryan said:
So flash a ROM or restore a backup.
My ROM: WICKED X
Click to expand...
Click to collapse
I can't flash a rom because I can't push or sideload and I don't really make backups hah
PandaDan said:
I can't flash a rom because I can't push or sideload and I don't really make backups hah
Click to expand...
Click to collapse
then you have no choice but to Odin back to stock cause you didn't make a backup
6th_Hokage said:
then you have no choice but to Odin back to stock cause you didn't make a backup
Click to expand...
Click to collapse
Actually, I just got Heimdall to work with flashing PhilZ and now I'm able to mount USB storage. I personally think Odin is garbage but that's just me
PandaDan said:
Actually, I just got Heimdall to work with flashing PhilZ and now I'm able to mount USB storage. I personally think Odin is garbage but that's just me
Click to expand...
Click to collapse
At least you got Philz installed now just make backups ever so often....
Yeah, make at least one of backup so you don't get stuck in this situation again. Really, you should be making a backup before you flash anything, every time.
My ROM: WICKED X
bilgerryan said:
Yeah, make at least one of backup so you don't get stuck in this situation again. Really, you should be making a backup before you flash anything, every time.
My ROM: WICKED X
Click to expand...
Click to collapse
Truer words were never spoken... ☺
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Just a quick question. I flashed a stock build then went to 5.0 with zero issues. I'm under the assumption this wiped your device as stated in the directions but for some reason I'm missing a ton of storage. Should have any 24gb of free space after a clean flash. I don't have Google+ photos synced or anything.
Anyone else see that?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FormeriPhoney said:
Just a quick question. I flashed a stock build then went to 5.0 with zero issues. I'm under the assumption this wiped your device as stated in the directions but for some reason I'm missing a ton of storage. Should have any 24gb of free space after a clean flash. I don't have Google+ photos synced or anything.
Anyone else see that?
Click to expand...
Click to collapse
Were you using factory images? Just curious. Stock recovery? Wipe data/factory reset. TWRP? Format data. Or... fastboot format userdata. That's the options that I remember hearing of but I've not had the problem myself. Any of those options will of course wipe your storage.
wantabe said:
Were you using factory images? Just curious. Stock recovery? Wipe data/factory reset. TWRP? Format data. Or... fastboot format userdata. That's the options that I remember hearing of but I've not had the problem myself. Any of those options will of course wipe your storage.
Click to expand...
Click to collapse
I actually used wugfresh toolkit bc I had a problem with adb for some reason.
I got some help from the nexus 7 community on google+ and it was as simple as just doing a factory reset. Lol. Showed up 26.9gb free after that.
Sometimes it is just the easiest stuff right under your nose ?
FormeriPhoney said:
I actually used wugfresh toolkit bc I had a problem with adb for some reason.
I got some help from the nexus 7 community on google+ and it was as simple as just doing a factory reset. Lol. Showed up 26.9gb free after that.
Sometimes it is just the easiest stuff right under your nose ?
Click to expand...
Click to collapse
Good deal!
I flashed a rom that I found here and I didn't check my storage, but ES file explorer showed a complete lack of sd card... I coulnd't take pictures or download files, but I could download apps..
jastonas said:
I flashed a rom that I found here and I didn't check my storage, but ES file explorer showed a complete lack of sd card... I coulnd't take pictures or download files, but I could download apps..
Click to expand...
Click to collapse
Try a factory reset.. Easy and hopefully the answer
FormeriPhoney said:
Try a factory reset.. Easy and hopefully the answer
Click to expand...
Click to collapse
I flashed the stock image using flashboot again..
Do we have root and twrp on the nexus 7 yet?
Yes. Go to the Android Development thread [http://forum.xda-developers.com/showthread.php?t=2856920 ], post 441. You need a modified boot image for root. You can fastboot flash twrp and fastboot flash the kernel. Or, there is a zip of the kernel. Or, you could use Wug's newly updated toolkit.
Sent from my Nexus 7 using Tapatalk
ritchea said:
Yes. Go to the Android Development thread [http://forum.xda-developers.com/showthread.php?t=2856920 ], post 441. You need a modified boot image for root. You can fastboot flash twrp and fastboot flash the kernel. Or, there is a zip of the kernel. Or, you could use Wug's newly updated toolkit.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yup.. As soon as I saw wug update the program I jumped on it. Rooted and twrp in less than 5 min.
[emoji106]