Android OS Forum banner
81 - 100 of 106 Posts

· Android Groupee
Joined
·
169 Posts
Installed the latest version last night. It's looking good and I appreciate the larger font. Flashed a couple of zips...no problem.
 

· Android Groupee
Joined
·
169 Posts
I just did a backup. It took a little over 6 minutes and was 1.02GB.
 

· Registered
Joined
·
8 Posts
can anyone help me on this i'm sure this is the wrong place but i will give it a shot anyway
i am running a samsung galaxy tab 2 7.0 pg-3113 with AOKP-b35]Galaxian-Soup[GT-P3113 and i cant play video's from web sites like the news or sports highlight is there a fix for this ?? thanks in advance for any help or ideas ..running ics web and firefox and dolphin as well and same on all ..thanks
 

· Developer
Joined
·
367 Posts
can anyone help me on this i'm sure this is the wrong place but i will give it a shot anyway
i am running a samsung galaxy tab 2 7.0 pg-3113 with AOKP-b35]Galaxian-Soup[GT-P3113 and i cant play video's from web sites like the news or sports highlight is there a fix for this ?? thanks in advance for any help or ideas ..running ics web and firefox and dolphin as well and same on all ..thanks
Did you install Flash Player from the market?

D

.
 

· Registered
Joined
·
5 Posts
I updated from stock to IML74K-P3113UEALD3 a few days ago. Today I flashed espressowifi-recovery-5-18.tar.md5 using Odin but I couldnt get into recovery using power volume down, However, I was able to get in recovery using adb reboot recovery, however, when I try to flash any zips, like the root package, stock rom or the rooted/deodexed stock rom I am getting a signature verification error for all of them. Is this caused by the update? do I need to flash an unsecured boot images using heimdall?
Thanks for the assistance.

Update: The recovery I am able to get in is stock
I guess I must flash an unsecured boot images anyone knows if I can flash unsecured boot images using Odin, Heimdall doesn't recognize my device. Please help.
 

· Registered
Joined
·
10 Posts
I updated from stock to IML74K-P3113UEALD3 a few days ago. Today I flashed espressowifi-recovery-5-18.tar.md5 using Odin but I couldnt get into recovery using power volume down, However, I was able to get in recovery using adb reboot recovery, however, when I try to flash any zips, like the root package, stock rom or the rooted/deodexed stock rom I am getting a signature verification error for all of them. Is this caused by the update? do I need to flash an unsecured boot images using heimdall?
Thanks for the assistance.

Update: The recovery I am able to get in is stock
I guess I must flash an unsecured boot images anyone knows if I can flash unsecured boot images using Odin, Heimdall doesn't recognize my device. Please help.
try plug you unit in a other usb port
 

· Registered
Joined
·
19 Posts
I updated from stock to IML74K-P3113UEALD3 a few days ago. Today I flashed espressowifi-recovery-5-18.tar.md5 using Odin but I couldnt get into recovery using power volume down, However, I was able to get in recovery using adb reboot recovery, however, when I try to flash any zips, like the root package, stock rom or the rooted/deodexed stock rom I am getting a signature verification error for all of them. Is this caused by the update? do I need to flash an unsecured boot images using heimdall?
Thanks for the assistance.

Update: The recovery I am able to get in is stock
I guess I must flash an unsecured boot images anyone knows if I can flash unsecured boot images using Odin, Heimdall doesn't recognize my device. Please help.
You enter recovery by holding "power" and "volume up" together from off untill the initial splash screen goes away. (~8 seconds)

If you have stock recovery and the update was applied ( Original - UEALCB / SEP-99 #1 New - UEALD3 / SEP-66 #1) you will need to flash unsecured boot image from this thread:
http://rootzwiki.com...very-overwrite/
Heimdall uses it's own driver found in the package you un-zipped.
Follow the text in post #7 of that thread.

You then need to use ODIN to flash root.
http://rootzwiki.com...t-galaxy-tab-2/

Sometimes the drivers get confused; monitoring them in device manager helps.
I uninstall the device/devices and then let the computer look for harware changes in device manager.
Sometimes things are really messed up and then I uninstall every instance of Samsung devices and reboot and try again, it works.

You can search the web for how to add "show hidden devices" to the view menu of device manager, it helps me sometimes.
 

· Android Groupee
Joined
·
169 Posts
i have stock + update. can you walk me through the steps to have root+cwm?

1 - flash unsecured boot image using heimdall?
2 - flash root using odin?
3 - flash cwm from from this thread?
4 - done?
Follow the instructions in this thread and you should be set. Use the recovery package from imnuts.
 

· Registered
Joined
·
7 Posts
Thank you for your work.

I had a problem while restoring data.ext4.tar:
tar: seek failure: Value too large for defined data type

I'm guessing busybox/tar just need to be compiled with large file support.
I think I did the backup with an older version of your recovery, so it is probably much larger than normal.

Not a big deal though, I'll just remove some stuff from the tar to make it smaller.
Thanks again.
 
81 - 100 of 106 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top