Database Info

Android 4.1-Jellybean

Hey guys can anyone help me out? I recently updated my Samsung Galaxy Tab 2 from ICS to Jellybean. However, I dont really like Jellybean's interface and want to rollback to ICS. Is there anyway I can do this?
Thanks,
Akshat

iValueTech said:
Hey guys can anyone help me out? I recently updated my Samsung Galaxy Tab 2 from ICS to Jellybean. However, I dont really like Jellybean's interface and want to rollback to ICS. Is there anyway I can do this?
Thanks,
Akshat
Click to expand...
Click to collapse
You could try to download the ics Odin dump and flash it onto your device. Your post doesn't contain the model number so I couldn't find the specific one for you. (Wifi or wifi +3G)

Wifi+3g

Model No. GT-P3100

You could try downloading a launcher and then finding a similar interface as to the ICS one.

iValueTech said:
Model No. GT-P3100
Click to expand...
Click to collapse
Here is a 4.0.4 (probably)leaked firmware found on xda:
http://forum.xda-developers.com/showthread.php?t=1790381
Your device has also an active sub forum in which you can find custom roms and other stuff.

Can you flash any custom ROM ?

Hello
I was wondering if I could flash galaxy S 3 international version with any carrier specific custom rom like Verizon /at&t etc and vice versa. I see there are many ROMs which aren't available for international variant but for some carrier.
I know there must be some carrier differences and little other small security patches, but does that mean I can use any ROM or I would face problems like glitches/soft brick etc?
I know in Sony, HTC it is not a problem but how about Samsung ?

Hnk1 said:
Hello
I was wondering if I could flash galaxy S 3 international version with any carrier specific custom rom like Verizon /at&t etc and vice versa. I see there are many ROMs which aren't available for international variant but for some carrier.
I know there must be some carrier differences and little other small security patches, but does that mean I can use any ROM or I would face problems like glitches/soft brick etc?
I know in Sony, HTC it is not a problem but how about Samsung ?
Click to expand...
Click to collapse
I wouldn't even attempt to flash a rom that's meant for a Verizon phone for an international S3. The phones are similar yes but they are different in so many ways. You could hard brick your phone if you attempt to flash a rom that's not meant for your phone
Sent from my SCH-I535 using Xparent ICS Tapatalk 2

Hnk1 said:
Hello
I was wondering if I could flash galaxy S 3 international version with any carrier specific custom rom like Verizon /at&t etc and vice versa. I see there are many ROMs which aren't available for international variant but for some carrier.
I know there must be some carrier differences and little other small security patches, but does that mean I can use any ROM or I would face problems like glitches/soft brick etc?
I know in Sony, HTC it is not a problem but how about Samsung ?
Click to expand...
Click to collapse
There are a few good threads on XDA for porting roms. Porting between Verizon and international shouldn't take to long. As long as you stay in the s3 family most of the porting is copy past stuff.

S2 roms on S2plus?

Hey people.
Just recently someone told me that we can flash S2 roms on S2plus. Only problem would be NFC.
Now I feel this isn't possible as both the phones have different CPUs.
But still is it true anyways ?

afaquekhaja said:
Hey people.
Just recently someone told me that we can flash S2 roms on S2plus. Only problem would be NFC.
Now I feel this isn't possible as both the phones have different CPUs.
But still is it true anyways ?
Click to expand...
Click to collapse
That's not true.You can brick your phone.I suggest you not to do that.

afaquekhaja said:
Hey people.
Just recently someone told me that we can flash S2 roms on S2plus. Only problem would be NFC.
Now I feel this isn't possible as both the phones have different CPUs.
But still is it true anyways ?
Click to expand...
Click to collapse
don't do that you'll brick it
and i dun understand why can't you just choose one from so many of these awesome roms from our development sections!

[Completed] samsung s2 gt i9100 dropping wifi issues kitkat 4.4.4

This might just piss everyone off but I am not a seasoned poster so here it is.
I rooted my phone using framaroot then installed CWM via rom manager then tried, neatrom, spirit, pacman, cyanogenmod. all are kitkat 4.4.4 based.
My problem is the wifi keeps disconnecting and connecting spasmodically, after that occasional behaviour though it tends to become dormant, with the toggle tile showing a grey colour. I dont know how to identify the cause, I have checked for hardware problems like the bat500 leak issue, tried setting manual ip settings etc. I am not familiar with all the settings in these more modern versions of android so maybe there is something basic I am missing.
I have done a bug report but have no idea what to look for
Phone specific details
Model: GT-I9100T
Country: New Zealand
Version: Android 4.1.2
Product Code: TNZ
PDA: I9100TDVLSH
CSC: I9100TTNZLSA
MODEM: I9100TDVLS3
was it because the phone has been rooted? or flashed with the incorrect recovery module. Can I recover from this and go back to the jelly bean 4.1.2 stock that was on there originally (i forgot to nandroid after rooting, in the haste of new rom fun, I know what a dickhead) I cant find any original stock JB files for my location.
Any help would be most valued.... Im not retarded but definately feel like it now that Ive been 24hrs trying to solve it.
Thanks in advance

Hi, thank you for using XDA Assist. Not all Wi-Fi issues are device related. Many of them are router related. Have you rebooted your router? Also, is it's firmware up to date?

jd1639 said:
Hi, thank you for using XDA Assist. Not all Wi-Fi issues are device related. Many of them are router related. Have you rebooted your router? Also, is it's firmware up to date?
Click to expand...
Click to collapse
It appears that this is a device specific issue, I have searched but cannot find any actual solutions to the problem...
When samsung put out the jb 4.1.2 update they did a crappy job with the modem and then pulled device support.
This issue as far as I can tell is to do with the modem and its drivers (I think) this issue developed with the upgrade to the new 4.1.2 JB stock rom. there were plenty of people having problems on a stock rom platform.
I am guessing that the custom roms dont fix this issue in kit kat 4.4.4 does anyone know if there is progress with the lollipop releases.
Does anyone know what I can do about it? should I open up some of the old threads?
thanks for your reply

tumeke said:
It appears that this is a device specific issue, I have searched but cannot find any actual solutions to the problem...
When samsung put out the jb 4.1.2 update they did a crappy job with the modem and then pulled device support.
This issue as far as I can tell is to do with the modem and its drivers (I think) this issue developed with the upgrade to the new 4.1.2 JB stock rom. there were plenty of people having problems on a stock rom platform.
I am guessing that the custom roms dont fix this issue in kit kat 4.4.4 does anyone know if there is progress with the lollipop releases.
Does anyone know what I can do about it? should I open up some of the old threads?
thanks for your reply
Click to expand...
Click to collapse
It would be best to ask in the device specific threads. They are the experts on your device.
Sent from my Nexus 5 using XDA Free mobile app

Thread closed.

How is AOSP now possible on the S7?

I am using Android phones since several years and had no problems finding ROMs and flash them. Bootloader Unlock was no problem back then on Galaxy S1, HTC One S, Nexus 5 and Galaxy S5 but it kinda surprised me that the S7 is my first phone which will "probably never" see an AOSP ROM because of the locked bootloader and the unknown software architecture of Exynos processors.
What has happened that pretty functional and stable AOSP ROMs are now blowing up on XDA?

Uwe303 said:
I am using Android phones since several years and had no problems finding ROMs and flash them. Bootloader Unlock was no problem back then on Galaxy S1, HTC One S, Nexus 5 and Galaxy S5 but it kinda surprised me that the S7 is my first phone which will "probably never" see an AOSP ROM because of the locked bootloader and the unknown software architecture of Exynos processors.
What has happened that pretty functional and stable AOSP ROMs are now blowing up on XDA?
Click to expand...
Click to collapse
Yeah, how is that possible?

Uwe303 said:
S7 is my first phone which will "probably never" see an AOSP ROM because of the locked bootloader and the unknown software architecture of Exynos processors.
Click to expand...
Click to collapse
What locked bootloader? Did you not know that aosp and exynos doesn't mix before you got the s7?

peachpuff said:
What locked bootloader? Did you not know that aosp and exynos doesn't mix before you got the s7?
Click to expand...
Click to collapse
see the Exynos development forum there's a bunch of AOSP ROMs there now.
I'm also wondering what changed to facilitate all these ROMs working on the Exynos S7.

magic dude, im telling ya, in a period of 2 months, they already made it bootable and stable enought, not for daily usage, but really near to!

I think some devs were working to get aosp on exynos and Samsung.
Sent from my SM-G930F using Tapatalk

maddada said:
see the Exynos development forum there's a bunch of AOSP ROMs there now.
I'm also wondering what changed to facilitate all these ROMs working on the Exynos S7.
Click to expand...
Click to collapse
Good to hear, still unrooted so i barely visit that section. When i bought the phone when it came out i knew it probably wouldn't get aosp, but after using touchwiz i really don't miss it.... omg i've said it!