Database Users

[I9000B] Brazil Galaxy S, Thread/Discussion/Roms (Updated: ICS for I9000B)

READ THIS POST BEFORE ASK! USE ENGLISH ONLY PLEASE!
General Note: There are now four official models of the Samsung Galaxy S outside the US: the GT-I9000 (International), GT-I9000M (Canada), GT-I9000B (Brazil), GT-I9000T (Mexico). All information in this FAQ is based on the GT-I9000 International version. Most of them also apply to the other models. The I9000M and I9000T are virtually identical to the I9000 and are mostly compatible with I9000 software. The I9000B has an added digital television receiver and is generally not as compatible. Please check carefully before starting to mess with the firmware on your device, check for possible compatibility issues beforehand and ALWAYS make sure you have three button recovery
IMPORTANT NOTES FOR I9000B:Ok guys, now is possible find more than one modded kerner for I9000B, but you must be careful, because many of them have a lot of bugs or are't fully tested. Almost all of new moded kernel doesn't support Digital TV so if it is useful for you, don't try, until the official firmware updates are released.​
-----------------------------------------------------------------
ICE CREAM SANDWICH
-----------------------------------------------------------------​
[RELEASE CANDIDATE] Ice Cream Sandwich ROM for Galaxy S (for may models, included I9000B. Digital TV NOT supported)
[ROM][ICS][I9000] Team ICSSGS RC4.2
No 3G/HSDPA, Extreme Battery drain? you need another modem for your ICS?
Check this list, with compatible modems for CM7/MIUI/ICS/CM9 by siky_dude
[CM7/MIUI/ICS/CM9][06.01.12] Modems + Bootloaders(MD5)​
-----------------------------------------------------------------
GINGERBREAD
-----------------------------------------------------------------​
You like Gingerbread? No problem, now you can use ANY Gingerbread ROM without problems. Only you must use Mafalda Kernel for I9000B available in different flavors.
Mafalda-0.9-4-OC1200gpu.tar.md5 ODIN-1200Hz OverClock
Mafalda-0.9-4-OC1200gpu.zip CWM-1200Hz Overclock
0.9-4-Mafalda-noOC.tar ODIN -No Overclock - RS
0.9-4-Mafalda-noOC.tar ODIN -No Overclock -Multiple Mirrors
NOTE:Unfortunately, because Megaupload was closed, we lost too many links and other flavors of Mafalda Kernel. So, if you have the file, please upload and share it.​
Links
(NOTE: Not all the info provided in the following links is useful for I900B, PLEASE becareful and read with attention)
General Info for SGS I9000 (FAQ, HOWTO, TUTORIALS)
How to: Flashing your SGS
[VIDEO] Using Odin
[APP]SuperOneClick v2.3.3 (One Click Rooting-Unrooting)
How to [/COLOR]unlock/unfreeze all SGS Models

How-to Root Gingerbread 2.3.3 Stock using FuguRoot
1: Flash the stock rom
2: Download the zImage moded for Odin
3: Flash it with either Odin or Heimdall
4: Boot once, it will install root and crash/shutdown (if you let it conected to usb will loop on charging)
5. Disconnect and enter download mode
6: Reflash the ONLY original kernel (Download here)
7. DONE!
No 3G/GPRS/EDGE after flashing?
Is very common that after flashing a new firmware or kernel your device isn't conecting to 3G. WHY? Because many of the firmwares or kernels wipe all the user data includig de APN, wich contains the neccesary info to connect your device to 3G networks. But don't worry, this is not the end of the world. You could Add your APN confirgation just following this steps
1. Go to Settings
2. Go to Wireless and network
3. Then go to Mobile networks
4. You will find the Acces Point Names or APN were should be the info to connect to 3G, click here
5. After that, use the "phisical" button of menu
6. Choose New APN
7. Set the configurarion of your carrier/mobile network (This info could be found at carrier/mobile network web page or just simply googling)
8. Done! you have your SGS configurated
To prevent loose the APN data, exists many apps wich could help. One of them is APN Backup & Restore a simple FREE App to backup and restore APNs. Very usefull.
The are some devices that's not necessary to back up data or add the data again, just conecting to 3G will download and apply de data by itselfs.
Problem with SuperOneClick v1.5.5 ?
If you get stucked at any moment of the process, waiting days for getting mount path?
Here is a solution.
1. Turn on usb debugging
2. Turn off phone & plug into usb
3. Start SuperOneClick
4. When it says waiting for device, turn phone on and let SOC finish the job.
5. Enjoy root!
(source)

another one too

stickied, thank you
{
"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"
}
it was about time some one took the initiative to organize all the I9000B information

Sync Error
Hello, thanks for creating this topic. We were really needed it!
I bought an SGS in Brazil, operator Vivo, Android 2.1 (Eclair) and upgraded to the 2.2 Froyo (Live - ZVV) using Odin (no pit). Since then, I'm having problems with Orkut sync.
When orkut account is selected, "Feeds and Updates" widget always displays the error: "Service Unavailable".
Under Settings / Accounts and synchronization features: Synchronization error "Synchronization is currently having problems. They will return soon" and does not synchronize the contacts on orkut.
This has been more than a month, since when I have done several roms updates, using odin (including re-partition) and Kies.
The only thing that worked a while, was to create a new Orkut account (in fact, google account) but after a factory reset, stopped again.
Other SNSAccounts work well, I have no problems with Twitter to Facebook, only Orkut.
I posted here because I think Orkut is a SNSAccount available only in Brazil.
Does anyone have any suggestions? Thank you!

AllGamer said:
stickied, thank you
it was about time some one took the initiative to organize all the I9000B information
Click to expand...
Click to collapse
What about this thread:
http://forum.xda-developers.com/showthread.php?t=782686
Lots of related information there

try using Kies Registry patcher and choose ZTO for Vivo then update over Kies. I use to update my phone, mine was chilean Claro with Eclair. This is the official version of the operator and comes with Orkut

Is there any chance to have a ROM for Claro Mobile users which I suppose is ZTA? I´ve tried KIES and Kies Registry Patcher but got my SGS frozen if I choose ZVV and got "not available update" when using ZTA.
Thanks
Edited: I've finally made it. Using KIES and patch along ZVV spoof option. Now Froyo 2.2.

Personally I recommend I9000BVJJPD fw for updates, it is unbranded and the last version know, the firmwares from operators are too old (september, october, november).
Then root the phone and download "Uninstaller for root" from market, for delete some useless apps like "Braintest" or "Asphalt 5"

2.2 JPD
Yes, I am using this too. Works pretty well, and better than JPA. I had some wifi issues with JPA, magically solved in JPD.
There is a JPY which is a work-in-progress. So, JPD is the latest and greatest.
Regards,
Marco

Cyanogen
Here is a thread I created to post everything specific related to CM and i9000B. For now, CM6 development has ended, and CM7 (Gingerbread) for i9000 is under development. Hopefully, there will be a ROM for i9000B or at least an adaptation.
http://forum.cyanogenmod.com/topic/11750-instructions-for-gt-i9000b-cyanogen/
Lovato

maglovato said:
There is a JPY which is a work-in-progress.
Click to expand...
Click to collapse
source, link or something¡

For brazilian users, yo can enter to androidz.com.br where a user (ffosilva) modified the kernell, so any ROM can work with the i9000b (the only thing that doesn´t work is the TV), for argentinian users (or from peru and chile) go to grupoandroid.com.
For example, I have my i9000b with a 2.2.1 JS3 (the last one) ROM "cooked" by me using the DOCs ROM Kitchen that is in development section

3G
Guys, i update mine with froyo and lost 3G, i have TIM and CLARO chips, neither of them get 3G connections... just Gprs and Edge..
Also the signal got a little weird, for instance CLARO signal at my house gets weak and shows the message "EMERGENCY CALLS ONLY", if i use the same chip in another phone, gets FULL signal...
If anyone has the same problem or solution please contribute!
Thanks
P.s.: Sometimes in CLARO I get FULL signal and the emergency calls only message disappears, bur when I try to make a call, it says "DATA NETWORK UNAVAILABLE"

gentefina said:
Guys, i update mine with froyo and lost 3G, i have TIM and CLARO chips, neither of them get 3G connections... just Gprs and Edge..
Also the signal got a little weird, for instance CLARO signal at my house gets weak and shows the message "EMERGENCY CALLS ONLY", if i use the same chip in another phone, gets FULL signal...
If anyone has the same problem or solution please contribute!
Thanks
P.s.: Sometimes in CLARO I get FULL signal and the emergency calls only message disappears, bur when I try to make a call, it says "DATA NETWORK UNAVAILABLE"
Click to expand...
Click to collapse
Flashed with the FW in the first post?
have you checked your APN settings?
try re config your 3G settings from network

andifds said:
Flashed with the FW in the first post?
have you checked your APN settings?
try re config your 3G settings from network
Click to expand...
Click to collapse
Yes, i tried different APNs but no success..
how do i config 3g settings?
And one tip, Samsumg has OFFICIALLY RELEASED FROYO for i9000B..
Version is JPD (same here), and is released in KIES.
Regards,

The BVJJPD version is pretty stable, but i have serious low signal wifi problems....

Help from changing VIVO froyo to unbranded froyo
I'm from Perú, and last month I upgraded to brazilian froyo (I9000B_JPA_JP3_JPA_JPA_VJ_ZVV_BRAZIL) using odin. With this version I am having issues with wireless and GPS. My question is how can I change to the unbranded version. I have lagfix and root installed. Do I have to undo the lagfix and the root first? Is it possible to install the unbranded version and don't lose the applications installed??
Please confirm
Thanks!

maticitu said:
The BVJJPD version is pretty stable, but i have serious low signal wifi problems....
Click to expand...
Click to collapse
yes, i have same problems, sometimes wifi show error and GPS is awful
a big question for all BVJJPD users is, radio have stereo or mono?
diegoquintana said:
Do I have to undo the lagfix and the root first? Is it possible to install the unbranded version and don't lose the applications installed??
Please confirm
Thanks!
Click to expand...
Click to collapse
Yes is possible
Download and flash the fw that's in first post.
Updated and with all your apps

andifds said:
Yes is possible
Download and flash the fw that's in first post.
Updated and with all your apps
Click to expand...
Click to collapse
So do I have to repartition?? What options should I select in ODIN?
Thank you very much for your help

Security warning for all Note 10.1 devices

As many of you know, all devices that have a Exynos processor have a security hole, called EXYNOS EXPLOIT.
Basically, this security hole allowes apps to have complete access to everything on your device.
For more information on this security hole, click:
http://www.google.com/search?q=samsung+exynos+exploit
Samsung has released new firmware for exynos devices, these firmwares close this security hole.
For your own security, every Note 10.1 should change to the latest 2013 firmware.
2013 firmware has a code that ends with M** for example:
N8010XXUCMA5 (4.1.2)
N8000XXCMA1 (4.1.2)
N8013UEUCMA3 (4.1.2)
You can get the newest firmware on samsung-updates.com and samfirmware.com.
Firmware on these sites is official Samsung firmware from Samsung Kies.
About country versions and OTA updates:
Experience shows that the waiting time for your country firmware version or an OTA update for your country depends on the priority your country has for samsung (waiting time of 1 day, many months or possibly never get an update for your country).
Samsung firmware for the Note 10.1 includes all languages and is almost identical in all country versions (with exception of the China version).
Also the Taiwan version offers all languages at setup. You just have to select Samsung Keyboard in your language version in settings and the firmware will be like your own country version.
You should backup all your data/apps/settings with something like Titanium backup, install the new firmware and then do a factory reset.
You can also not do the factory reset, but you may have compatibility problems.
To install firmware on your Note 10.1 you need Odin.
You can download it here:
Samsung Odin3 v1.85 for Note 10.1
http://www.mediafire.com/?8qv95ije5gd2vjk
Samsung Odin3 Manual for Note 10.1
http://www.mediafire.com/view/?7ueokoji11965ao
Direct links to the firmwares:
4.1.2 Germany for GT-N8010
http://www.hotfile.com/dl/190278866/d6b1373/N8010XXUCMA5_N8010OXACMA5_DBT.zip.html
4.1.2 Germany for GT-N8000
http://hotfile.com/dl/189226269/e9c...-GT-N8000-DBT-N8000XXCMA1-1357533079.zip.html
4.1.2 USA for GT-N8013
http://hotfile.com/dl/189276711/f83...GT-N8013-XAR-N8013UEUCMA3-1357740396.zip.html

legion1911 said:
As many of you know, all devices that have a exynos processor have a serious security hole, called EXYNOS EXPLOIT. Basically, this allowes apps to have complete access to everything on your device.
Samsung has released new firmware for exynos devices, these firmwares close this serious security hole.
Every Note 10.1 should change to a firmware with code that ends with M** (that M means 2013), for example:
N8010ZSBMA1
N8000XXCMA1
N8013UEUCMA3
For GT-N8010
http://hotfile.com/dl/188458272/712...-GT-N8010-BRI-N8010ZSBMA1-1357196432.zip.html
For GT-N8000
http://hotfile.com/dl/189226269/e9c...-GT-N8000-DBT-N8000XXCMA1-1357533079.zip.html
For GT-N8013
http://hotfile.com/dl/189276711/f83...GT-N8013-XAR-N8013UEUCMA3-1357740396.zip.html
You can get the newest firmware on samsung-updates.com and samfirmware.com.
They are not mirrors, they often have one rom, that the other one does not have.
Click to expand...
Click to collapse
That's the build for 4.1.2.

Stoney60 said:
That's the build for 4.1.2.
Click to expand...
Click to collapse
Which only Germany has, as far as I know?
Officially, anyway. I'm using redemption at the mo, which I think uses the German 4.1.2... not sure though.

Stoney60 said:
That's the build for 4.1.2.
Click to expand...
Click to collapse
No. It is not related to the android version. the patch is in the boot image. Also the 4.1.1. ending with M** is fixed.

legion1911 said:
No. It is not related to the android version. the patch is in the boot image. Also the 4.1.1. ending with M** is fixed.
Click to expand...
Click to collapse
Pardon me, but:
{
"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"
}

Stoney60 said:
Pardon me, but:
View attachment 1654212
Click to expand...
Click to collapse
What you posted does not contradict me. you refered to 3 roms and say they are 4.1.2. They are not all 3 4.1.2. The fix is in the boot image, not in android. If you take your 4.1.2 and change only the boot image, you are again with security hole.

Like this
Sent from my SPH-D710 using xda app-developers app

legion1911 said:
No. It is not related to the android version. the patch is in the boot image. Also the 4.1.1. ending with M** is fixed.
Click to expand...
Click to collapse
I'm saying, I've been to both Samsung-update.com and Samfirmware.com, neither of which have the updates you have posted in the op. The hotfile links you posted take you to a d/l site that has the N8013EUCMA3 firmware that is the same as the 4.1.2 build number you can see in my screenshot.
---------- Post added at 08:54 PM ---------- Previous post was at 08:50 PM ----------
gronimo21 said:
Like this
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Yup, just like my screenprint

will there be an official update?

Legion, can you update the first post with some more specific advice. Is this THE ota exynos update? Are Sammy going to release this OTA or is this it? Is this image for ALL devices irrespective of country. How it affects region specific devices. Also, flashing details etc.
I was under the impression that Bri was for Taiwan specific devices only! But I read somewhere that this update can be flashed regardless of region.
I think a little more advice on the first post would help users here.
I'm downloading now and will update as soon as, but a lot of users won't download based on the first post being unclear.
Riki

As per I know all patches will be release via OTA, the US 4.1.2 rom is already patch the German 4.1.2 rom has received the patch via OTA. Others I am not aware of but yes it will come out in form of an OTA. The OTA should be around 10 - 20 MB

So this download is NOT needed then? Is there any point downloading the ROM Legion has linked to?

The roms he has linked are stock firmwares for regions like Germany, US which have already received the patch. If you are on stock rom for your country then wait you will receive the OTA soon, if you are on a stock rom from another region then you will not so it makes sense to flash the German rom.
Also a question to all those how many device have been harmed because of exploit till date I have not seen even a single member posting about it so I do not think it is as serious as we make out to be

Well, downloaded and installed on ma tab UK 8010. Been messing around with it for the last half hour, checking everything works as it should.
Device OFFICIAL status.
Allshare Cast works fine.
No issues with language.
Seems slightly smoother and faster.
All tested apps work as they did prior.
Still 4.1.1 as expected. Exynos exploit fixed.
So, I would say given my previous thread, IF you have issues with Kies or OTA I would download and install.
Riki

samir_a said:
The roms he has linked are stock firmwares for regions like Germany, US which have already received the patch. If you are on stock rom for your country then wait you will receive the OTA soon, if you are on a stock rom from another region then you will not so it makes sense to flash the German rom.
Also a question to all those how many device have been harmed because of exploit till date I have not seen even a single member posting about it so I do not think it is as serious as we make out to be
Click to expand...
Click to collapse
Absolutely agree with Samir. Why would you downgrade to 4.1.1 just to fix a feature which seems never to have caused a problem!
Other than allowing the Note10.1 to be much easier to root for the hundreds (probably thousands) of users who have used the simple rooting method using the Exynos Exploit?
No issues with language.
Seems slightly smoother and faster.
All tested apps work as they did prior.
Click to expand...
Click to collapse
Compared to what - original 4.1.2?

I think I would rather wait for the "official" OTA update than download from a unknown source, thanks all the same.

Dont worry his source are geniune as they are the samfirmware stock rom links so do not worry about the source

pwatkins said:
Absolutely agree with Samir. Why would you downgrade to 4.1.1 just to fix a feature which seems never to have caused a problem!
Other than allowing the Note10.1 to be much easier to root for the hundreds (probably thousands) of users who have used the simple rooting method using the Exynos Exploit?
Compared to what - original 4.1.2?
Click to expand...
Click to collapse
I agree, but I was on 4.1.1 anyway. So closing a potential issue is a no brainer for me. It may well be the best/easiest way to root the tab but having such a potentially dangerous exploit there is not worth the risk.
Just because no one has been affected (or reported having been affected, or even knows they are affected) doesn't justify keeping it open. Especially IF you use the tab for banking, or other financial or work purposes!
My thoughts anyway.

Well its not that someone can use the exploit by magic they need a disguise to do that in form of an app or something else so if you are using it for banking then you would anyways be extra sure of the source of apps you install or website you browse.
Also once you patch it does not mean that your device cannot be hacked there are many other ways to it may be the above one was the easiest.
Again I am in no advocating not to patch the exploit but just putting some facts. Infact there was an article which said there were may fishing apps on google play itself

Way I see it is simple. The tab has a major exploit, the option to fix that exploit is now available. Folks can argue semantics/doomsday scenarios all day long, but it don't change the facts!
Peace

[Official Lollipop 5.1.1] Galaxy Note 10.1 (2014 Edition) SM-P607T Firmware Update

{
"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"
}
T-Mobile has just released the first official Android 5.1.1 Lollipop for the Samsung Galaxy Note 10.1 2014 Edition (SM-P607T). The update is currently Available Over-the-air (OTA) and via KIES in the United States. (screenshots attached)
Galaxy Note 10.1 Lollipop Firmware Details:
- Model Name: Samsung Galaxy Note 10.1 2014 Edition
- Model: SM-P607T
- Country: T-Mobile US (TMB)
- Firmware Version: P607TUVUBOI2
- OS: Android Lollipop
- OS Version: 5.0.2
- Build Date: September 09, 2015
- Changelist: 5777857
- PDA: P607TUVUBOI2
- CSC: P607TTMB1BOI2
Click to expand...
Click to collapse
Firmware Download: http://forum.youmobile.org/downloads/?sa=view&down=6351
Source: http://www.youmobile.org/blogs/entr...fficial-Android-5-1-1-Lollipop-is-Rolling-out
Regards,

Anyone know how to flash Twrp and have it stick?

*Note 10.1 2014 LTESM-P605NEEP605XXU1EOI5 5.1.1 19.09.2015 5849447

Anyone got a mirror that's faster than Sammobile or the youmobile link? I'm on the road and have to do this over my mobile network

md1008 said:
Anyone know how to flash Twrp and have it stick?
Click to expand...
Click to collapse
I flashed TWRP 2.8.7.0_4.4 with ODIN and had no issues getting it to stick. When the device reboots after the ODIN flash, make sure you are immediately holding the home button and volume up button. As long as you can get it to boot into TWRP immediately after the flash, it will stick.
However, flashing SuperSU resulted in a bootloop immediately after. Guess we need a new root for this firmware. If you care, http://forum.xda-developers.com/galaxy-note-10-2014/help/twrp-4-4-build-5-1-1-rom-t3216561 is a thread I started for this. Post there and subscribe, maybe some experts will come along to help us...

Any feedback on whether it includes the new snote and new spen features like smart clip from Note 4 or Note 5

In p605 now is possibile write a note in lockscreen

arbit12 said:
Any feedback on whether it includes the new snote and new spen features like smart clip from Note 4 or Note 5
Click to expand...
Click to collapse
The pen window has these commands now:
Air Command (no change)
Smart Select (where old Scrap Booker was)
Image Clip (where old Screen Write was)
Screen Write (where old S-Finder was)
Pen Window (no change)
So I think the answer is "Yes" depending on what you mean by "Smart Clip"

Root!
karthikrr said:
I flashed TWRP 2.8.7.0_4.4 with ODIN and had no issues getting it to stick. When the device reboots after the ODIN flash, make sure you are immediately holding the home button and volume up button. As long as you can get it to boot into TWRP immediately after the flash, it will stick.
However, flashing SuperSU resulted in a bootloop immediately after. Guess we need a new root for this firmware. If you care, http://forum.xda-developers.com/galaxy-note-10-2014/help/twrp-4-4-build-5-1-1-rom-t3216561 is a thread I started for this. Post there and subscribe, maybe some experts will come along to help us...
Click to expand...
Click to collapse
I tried the instructions on Post 144 here: http://forum.xda-developers.com/gal...lollipop-5-1-1-galaxy-note-10-t3215876/page15
It works without doing Step 1 (i.e. on the Stock Tmobile ROM)! All credit goes to @bluecat for doing the work and @M3r71n0 for the English translation!

sandibhatt said:
I tried the instructions on Post 144 here: http://forum.xda-developers.com/gal...lollipop-5-1-1-galaxy-note-10-t3215876/page15
It works without doing Step 1 (i.e. on the Stock Tmobile ROM)! All credit goes to @bluecat for doing the work and @M3r71n0 for the English translation!
Click to expand...
Click to collapse
Were you able to install the SuperSU beta via TWRP? I just get that the file is corrupt and can't go any further. I was able to flash the new ROM and TWRP using the first few steps.

Yes. I am not sure if a final version has been released.

Has anyone here observed that ever since updating to lollipop that it won't store Wi-Fi credentials through reboots? It seems every time I reboot my tablet I have to reconnect to my Wi-Fi...
Edit... it seems that it's not just reboots that causes the WiFi to forget the saved networks. Turning WiFi off and then back on again will also cause it to forget all saved networks. Not sure what to do to fix this this time...
Just tried a factory reset to see if maybe I just had a dirty flash or something... Didn't help. Is anyone else having this problem?

Should have asked first, are you on stock, or did you try to root using the P605 guide? If you are rooted, then open up /system/build.prop and change ro.securestore.support from true to false to fix the wifi issue... If you are on stock, read on for some suggestions...
I do not have this problem. Based on other people discussing something similar on OTHER devices, few things you may want to try are below ... Please note that I am NOT an expert and there is a good chance I am citing discussions that have NOTHING to do with your problem. 1 and 2 should be safe and not do any damage to your device, but 3 might be risky. So, please try solutions at your own risk ...
1) Forget/Delete the connection once and connect to it again from scratch by entering the password. Right now you reenter the password when the device forgets it, but some people seemed to be discussing how deleting a working connection and reentering password manually seems to fix it. No idea why this would work!
2) Since you already did a factory reboot, one suggestion I saw elsewhere was to flash the new ROM with ODIN, then reflash it again right away. Again, absolutely no idea if or why this might ever work!
3) Are you sure you updated to the RIGHT LL ROM for your device? The most frequent reason I see for this is if you flashed the wrong device/region ... For example, if you are on the P607T (T-Mobile) and flashed the Nordic (NEE) ROM that is listed in the root guides on this site, that might mess up your wi-fi. Some discussion I saw on this suggested flashing the correct MODEM file manually.
If you ever figure it out, please come back and share your solution!
dharvey4651 said:
Has anyone here observed that ever since updating to lollipop that it won't store Wi-Fi credentials through reboots? It seems every time I reboot my tablet I have to reconnect to my Wi-Fi...
Edit... it seems that it's not just reboots that causes the WiFi to forget the saved networks. Turning WiFi off and then back on again will also cause it to forget all saved networks. Not sure what to do to fix this this time...
Just tried a factory reset to see if maybe I just had a dirty flash or something... Didn't help. Is anyone else having this problem?
Click to expand...
Click to collapse

karthikrr said:
Should have asked first, are you on stock, or did you try to root using the P605 guide? If you are rooted, then open up /system/build.prop and change ro.securestore.support from true to false to fix the wifi issue...
Click to expand...
Click to collapse
I actually have the SM-P607T and I downloaded the stock ROM from Youmobile and flashed with Odin because Kies and Smart Switch kept locking up on me. I started fresh and only restored apps after flashing an unsecured boot and rerooting.
This suggestion worked perfectly. Stored WiFi passwords now survive reboots and turning WiFi on and off.
I would have quite literally found that. Thank you SO much! That little problem was wildly inconvenient but it's fixed now.
Thanks again.

dharvey4651 said:
I actually have the SM-P607T and I downloaded the stock ROM from Youmobile and flashed with Odin because Kies and Smart Switch kept locking up on me. I started fresh and only restored apps after flashing an unsecured boot and rerooting.
This suggestion worked perfectly. Stored WiFi passwords now survive reboots and turning WiFi on and off.
I would have quite literally found that. Thank you SO much! That little problem was wildly inconvenient but it's fixed now.
Thanks again.
Click to expand...
Click to collapse
No problem! This is apparently quite a common issue and you would have bumped into a discussion sooner or later... I noticed that even the thread with the unsecured boot image has now been updated with this information
Thanks for that link btw ... Does everything else work alright with that kernel on the P607T? The P605 is AT&T, if I am not mistaken and I am unsure what changes exist between that and the T-Mo version. Its strange that Samsung has released so much on its opensource portal for the 605, but literally just one source for the 607T. Perhaps because the base code is the same? No idea, but if you are happy with your performance out of this kernel, let us know...

karthikrr said:
No problem! This is apparently quite a common issue and you would have bumped into a discussion sooner or later... I noticed that even the thread with the unsecured boot image has now been updated with this information
Thanks for that link btw ... Does everything else work alright with that kernel on the P607T? The P605 is AT&T, if I am not mistaken and I am unsure what changes exist between that and the T-Mo version. Its strange that Samsung has released so much on its opensource portal for the 605, but literally just one source for the 607T. Perhaps because the base code is the same? No idea, but if you are happy with your performance out of this kernel, let us know...
Click to expand...
Click to collapse
I'm actually quite pleased with performance and usability of my P607T with the stock 5.1.1 ROM installed. Everything works as expected except for that wifi issue and that's now fixed thanks to your info a few posts up.
I can't speak to whether or not the base code is the same or not I would imagine that the code is likely very similar if not the same because I had "[ROM][P605][5.0.2] Besonderes; a Touchwiz Lollipop ROM for Galaxy Note 10.1 2014 LTE" which is made for the P605 installed on my P607T and everything worked except wifi direct which is actually very important to me because my work program requires it.
Now I can't keep my tablet rooted because the program I use for work won't load with the tablet rooted. This has been the case since 4.4.4 too so no big deal..
What I have to do is go into supersu and turn root on and off as needed. A bit inconvenient but it works...

dharvey4651 said:
I'm actually quite pleased with performance and usability of my P607T with the stock 5.1.1 ROM installed. Everything works as expected except for that wifi issue and that's now fixed thanks to your info a few posts up.
I can't speak to whether or not the base code is the same or not I would imagine that the code is likely very similar if not the same because I had "[ROM][P605][5.0.2] Besonderes; a Touchwiz Lollipop ROM for Galaxy Note 10.1 2014 LTE" which is made for the P605 installed on my P607T and everything worked except wifi direct which is actually very important to me because my work program requires it.
Now I can't keep my tablet rooted because the program I use for work won't load with the tablet rooted. This has been the case since 4.4.4 too so no big deal..
What I have to do is go into supersu and turn root on and off as needed. A bit inconvenient but it works...
Click to expand...
Click to collapse
Good to know everything works well ...
Blue Cat has been sharing his source files and config and suggested some ways to compare P605 with P607T to figure out if they are the same or how similar they are. Its been a while since I tinkered with linux, but as and when I learn something, will update.

dharvey4651 said:
I'm actually quite pleased with performance and usability of my P607T with the stock 5.1.1 ROM installed. Everything works as expected except for that wifi issue and that's now fixed thanks to your info a few posts up.
I can't speak to whether or not the base code is the same or not I would imagine that the code is likely very similar if not the same because I had "[ROM][P605][5.0.2] Besonderes; a Touchwiz Lollipop ROM for Galaxy Note 10.1 2014 LTE" which is made for the P605 installed on my P607T and everything worked except wifi direct which is actually very important to me because my work program requires it.
Now I can't keep my tablet rooted because the program I use for work won't load with the tablet rooted. This has been the case since 4.4.4 too so no big deal..
What I have to do is go into supersu and turn root on and off as needed. A bit inconvenient but it works...
Click to expand...
Click to collapse
What process did you use to root p607t with 5.1.1?

dmunjal said:
What process did you use to root p607t with 5.1.1?
Click to expand...
Click to collapse
I followed the instructions from this linked thread, substitute p607t firmware for the p605 in step 1.
Key is to not let it auto reboot after Odin flashes twrp, if you miss that step then you have to reflash it as it will be overwritten.
Once you are in twrp then you flash supersu and boot up.
sandibhatt said:
I tried the instructions on Post 144 here: http://forum.xda-developers.com/gal...lollipop-5-1-1-galaxy-note-10-t3215876/page15
It works without doing Step 1 (i.e. on the Stock Tmobile ROM)! All credit goes to @bluecat for doing the work and @M3r71n0 for the English translation!
Click to expand...
Click to collapse
I was never able to get Knox disabled from supersu and was constantly getting the security check notification(I had frozen parts of it in the past and now it won't thaw no matter what I have tried, FULL wipe and reflash, check w tibu and still frozen... No idea). I used titanium backup to freeze "securitylogagent" and everything has been fine since, including WiFi credentials sticking
Sent from my SM-P607T using Tapatalk

jayman350 said:
I was never able to get Knox disabled from supersu and was constantly getting the security check notification(I had frozen parts of it in the past and now it won't thaw no matter what I have tried, FULL wipe and reflash, check w tibu and still frozen... No idea). I used titanium backup to freeze "securitylogagent" and everything has been fine since, including WiFi credentials sticking
Sent from my SM-P607T using Tapatalk
Click to expand...
Click to collapse
Same here. Disabled the log agent.

Future of Yotaphone 2

Hi guys,
This thread is for speculation and discussion mostly. I'm wondering what the likelihood of us getting any significant android updates in the future is? Yota seems to have gone pretty quiet as regards the 2. It's pretty likely their focussing their limited resources on the Yota 3. I would say it's pretty certain that that will come out running marshmallow so it should be feasible that mm comes to the Yota 2 as well.
I'm also wondering about the 3. If it comes out with better relative specs than last time then I'm going to consider it seriously; if it's to the yota 2 what the yota 2 was to the 1 then it should be a pretty good phone.
Lastly is there any chance of some custom ROM development for this phone? Tempted to look into it myself but won't be able to for a while due to life schedule and whatnot. Could CM be ported? What features do we think we could add? Is it just too much work due to the second screen or is a custom version of the stock ROM possible?
Hope there's still some decent attention going to this. Shame about the US launch being cancelled, we could have done with the recruits .

After the US failure, I thought they would abandon YP2 pretty soon too, but they're are least still developing 5.0 further, so I think there will a nice 5.0 update soon. They have a version lined up with some candy in it: double tap to wake, new widgets, and some other stuff I can't remember. Battery life seems OK-ish too. They pathed stagefright and stagefright 2.0 bugs as well, and include a google android (security) patch level reference in the about screen.
I don't know about 5.1 or 6.0, but I think their US marketing manager has said in the past they've been testing 5.1 at least.
About custom firmware: I have made some small steps in the past (initially targetting AOSP 5.0) but I nor others have invested enough time in it to grow it into a complete firmware. Once AOSP would build nicely, CM is not that far away.
Full EPD functionality is something else though. It's been discussed before: The low-level EPD driver stuff (to draw stuff on the backscreen) is included in the kernel sources that Yota released last may, and so it would be available in a custom firmware as well. However it would not be usable by anything but custom built apps (not the current apps/widgets), that would access the EPD interface directly. The framework adaptions and SDK support that Yota did (screen mirroring, backscreen manager service to display widgets and covers etc) is not open source, so it cannot easily be ported. It might run as-is on a 5.0 custom ROM, but not likely on 5.1 or 6.0. So on top of creating a Custom ROM, there would need to be designing and coding effort to make the EPD actually usable. With the current level of interest from devs chances are pretty slim. Maybe a bounty system might work if there are enough people interested in contributing, but looking at the level activity in the Yotaphone subforum, I doubt that enough people are interested to make it worthwhile. (Or do we have a rich Russian Oil Company mogul in our midst ?
Anyway, I expect a Yota firmware update pretty soon with some nice improvements, still remaining at lollipop 5.0 though.
Edit: forgot to mention that I'm having trouble installing Xposed with newer versions, can't get it to work, hangs at boot animation. So if you're attached to Xposed, be careful when upgrading once the new firmware becomes available.

LRX21M.5.0.0-HK1.1.66 update
I just got an OTA system update request on my phone for downloading version LRX21M.5.0.0-HK1.1.66 today. I have not installed it yet, because my phone is rooted and I'm hoping someone else will take the plunge and report results before I try. (I'd hate to lose root entirely.)
I checked the official firmware repository (ftp://fw.ydevices.com/YotaPhone2/Firmwares/) and this version hasn't appeared there yet. There seems to be a similar new one for the APC region though. (Incidentally, I'm in the US, but I bought the phone online and apparently it was HK region. Works fine for me, so I don't care.)
I took screenshots and stitched them together so I could share the complete update description. I apologize for the ridiculously large image, but I didn't want to have to type all this stuff up, and I wasn't aware of a way to copy and paste it as text.
{
"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"
}
I was considering downloading it, but I'm not sure if I can do that and not have it auto-update once the download is finished. If I could get the file, I'd be happy to post it somewhere online if it would be useful. I've got ES File Explorer and root, and I assume it will be stored in /cache, but I don't want to risk updating right now.

9
MichaelA said:
I just got an OTA system update request on my phone for downloading version LRX21M.5.0.0-HK1.1.66 today. I have not installed it yet, because my phone is rooted and I'm hoping someone else will take the plunge and report results before I try. (I'd hate to lose root entirely.)
...
I was considering downloading it, but I'm not sure if I can do that and not have it auto-update once the download is finished. If I could get the file, I'd be happy to post it somewhere online if it would be useful. I've got ES File Explorer and root, and I assume it will be stored in /cache, but I don't want to risk updating right now.
Click to expand...
Click to collapse
Nice that they included a releasenotes, I have the impression that not everything is in there (like selecting a background photo for yotahub panels). It's nice to see that they're still improving on YP2 firmware.
I tested a version close to this one (but for another region) and it had a bad bug in the touchscreen functionality: when holding the phone (and thereby touching the backscreen) the front screen would not register taps or gestures correctly anymore. Not saying that this version has that bug too, but it might be worth testing this. Yota's got versions beyond 1.66 already, which include double tap to wake (and double tap to open specific apps on the backscreen while locked)
With TWRP you can backup your phone (including system, boot and data) and try the new firmware out. You can easily restore the backup if not satisfied, you'll be on your previous version again, including root.
There's a good chance that your firmware update will fail if you're rooted (as the original files on /system are different than expected by the update). So you should probably unroot, then update, then root again by flashing supersu through (TWRP) recovery.
The firmware file you might be able to capture is probably of limited use as it will likely be an incremental update from your specific previous version to 1.66.
So, backup first then try it out!

Thanks for the suggestions! I'll try to set aside some time this weekend and do a backup/update. Once I do, I'll post my findings here. Hopefully this update doesn't have that touchscreen bug you mentioned. I haven't had any major problems with my phone on the current version, but I'm curious to try what the update has to offer.
I hadn't thought about TWRP for rolling back. I never flashed it directly to the device, but I assume I can still do it by booting up as described in the post on here. And even if rooting somehow changed or was locked down, I'm assuming I can still boot the TWRP image and re-flash my backup. My bootloader is unlocked, and I assume will stay that way.

MichaelA said:
Thanks for the suggestions! I'll try to set aside some time this weekend and do a backup/update. Once I do, I'll post my findings here. Hopefully this update doesn't have that touchscreen bug you mentioned. I haven't had any major problems with my phone on the current version, but I'm curious to try what the update has to offer.
I hadn't thought about TWRP for rolling back. I never flashed it directly to the device, but I assume I can still do it by booting up as described in the post on here. And even if rooting somehow changed or was locked down, I'm assuming I can still boot the TWRP image and re-flash my backup. My bootloader is unlocked, and I assume will stay that way.
Click to expand...
Click to collapse
Your bootloader status and TWRP recovery should be fine by this update, haven't seen attempts to mess with any of that with recent firmwares.

Which ROM is for where?
Can anyone tell me which ROM is for what area, and if possible what the differences are.
Read all the Yotaphone posts and have a pretty good idea but 1 stumps me.
CN China YD206 Best radio
APC Asia Pacific?
EU Europe YD201
HK Hong Kong 4.43 What I just bought.
Has an OTA app but no update yet.
Planning to root, TWRP then EU 5.00 with CN radio but I'd sure like to know what ME is for.
RU Russia
ME No idea since Mexico is the same as the US.

Middle East?

Need help updating baseband/modem on I9505

Hey guys,
I've had my S4 for a while now and I've been happily switching around between ROMs and getting the newest versions of Android ever since Jelly Bean. Now I've recently been noticing that my wifi and 3G is acting up. I constantly lose the connection (shows up as a small exclamation mark on the wifi/3G symbol) and while sometimes I can fix it simply by switching to airplane mode and back, it often requires a reboot to get things working again.
While I have been updating my ROMs quite frequently, I've never actually touched the modem firmware, which makes me think that it's probably the reason for these problems. Which leads me to the following questions I have:
1) Where can I find the right firmware version? All I know is that my phone is a I9505 from the German carrier 1&1 and that the baseband is XXUEMKF (I vaguely remember that it may have been a different baseband in the past, I may have fooled around with it back when I was completely new to custom ROMs).
2) Is there any way of updating the baseband without using Odin? My USB connection has a loose contact. Charging still works, but data transfer only works if the phone is ABSOLUTELY not moving. Even so much as breathing on the phone will cause it to lose connection. I do most of my data transfers over wifi with Airdroid, so this hasn't bothered me until now. Any way to get around using Odin?
Any help would be greatly appreciated.
EDIT: Forgot to mention I'm running Resurrection Remix 5.5.7 (Lollipop 5.1.1)

I'm in Sweden and wishing someone with experience made it easier to find most up to date firmware and maybe even a brief explaination on fixes. Also I'd like to know for all these roms if there is a possible ROM + FIRMWARE package possible so you always have the correct firmware for your rom, i.e running Lollipop 5.0.1 or 5.0.2 or 5.1 or 5.1.1 seems to be needing different f/w's (or am I completely wrong?)
I'm currently running [JDCTeam][STABLE][5.1.1][1 November] Optimized CyanogenMod 12.1 build with latest update and I'm getting the "known" black screen in calls which is so annoying.
But when I run Aurora S6 Port 5.2 [OTA Update 1.6 by JASONRR] I have NO ISSUES what so ever.
Please someone explain this!
[irsidewinder]
Check PM
Thank you all

irsidewinder said:
Hey guys,
I've had my S4 for a while now and I've been happily switching around between ROMs and getting the newest versions of Android ever since Jelly Bean. Now I've recently been noticing that my wifi and 3G is acting up. I constantly lose the connection (shows up as a small exclamation mark on the wifi/3G symbol) and while sometimes I can fix it simply by switching to airplane mode and back, it often requires a reboot to get things working again.
While I have been updating my ROMs quite frequently, I've never actually touched the modem firmware, which makes me think that it's probably the reason for these problems. Which leads me to the following questions I have:
1) Where can I find the right firmware version? All I know is that my phone is a I9505 from the German carrier 1&1 and that the baseband is XXUEMKF (I vaguely remember that it may have been a different baseband in the past, I may have fooled around with it back when I was completely new to custom ROMs).
2) Is there any way of updating the baseband without using Odin? My USB connection has a loose contact. Charging still works, but data transfer only works if the phone is ABSOLUTELY not moving. Even so much as breathing on the phone will cause it to lose connection. I do most of my data transfers over wifi with Airdroid, so this hasn't bothered me until now. Any way to get around using Odin?
Any help would be greatly appreciated.
EDIT: Forgot to mention I'm running Resurrection Remix 5.5.7 (Lollipop 5.1.1)
Click to expand...
Click to collapse
bingoofsweden said:
I'm in Sweden and wishing someone with experience made it easier to find most up to date firmware and maybe even a brief explaination on fixes. Also I'd like to know for all these roms if there is a possible ROM + FIRMWARE package possible so you always have the correct firmware for your rom, i.e running Lollipop 5.0.1 or 5.0.2 or 5.1 or 5.1.1 seems to be needing different f/w's (or am I completely wrong?)
I'm currently running [JDCTeam][STABLE][5.1.1][1 November] Optimized CyanogenMod 12.1 build with latest update and I'm getting the "known" black screen in calls which is so annoying.
But when I run Aurora S6 Port 5.2 [OTA Update 1.6 by JASONRR] I have NO ISSUES what so ever.
Please someone explain this!
[irsidewinder]
Check PM
Thank you all
Click to expand...
Click to collapse
You guys probably need to update bootloader and modem. You can manually flash them or flash a stock Lollipop rom.
http://samsung-updates.com/device/?id=GT-I9505
Try this version. I9505XXUHOJ2
It doesn't matter from which country. Flash it using Odin (you can only update modem and bootloader using Odin). Afterwards you can restore you rom.
i.e running Lollipop 5.0.1 or 5.0.2 or 5.1 or 5.1.1 seems to be needing different f/w's (or am I completely wrong?)
Click to expand...
Click to collapse
You are wrong. It doesn't matter which firmware you came from.

Lennyz1988 said:
You guys probably need to update bootloader and modem. You can manually flash them or flash a stock Lollipop rom.
http://samsung-updates.com/device/?id=GT-I9505
Try this version. I9505XXUHOJ2
It doesn't matter from which country. Flash it using Odin (you can only update modem and bootloader using Odin). Afterwards you can restore you rom.
You are wrong. It doesn't matter which firmware you came from.
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------
Thank you Lennyz1988
Since I'm still less then 10 posts I can't post external links...I have that and "sammobile dot com", but what I didn't know was that you could flash from different countrys, this is new to me. So a new question arises and that is why in several posts here on XDA there are lists with multiple selections depending on location like this thread [ http://forum.xda-developers.com/showthread.php?t=2192025 ].
Thanks

bingoofsweden said:
------------------------------------------------------------------------------------------------------------------------------
Thank you Lennyz1988
Since I'm still less then 10 posts I can't post external links...I have that and "sammobile dot com", but what I didn't know was that you could flash from different countrys, this is new to me. So a new question arises and that is why in several posts here on XDA there are lists with multiple selections depending on location like this thread [ http://forum.xda-developers.com/showthread.php?t=2192025 ].
Thanks
Click to expand...
Click to collapse
It's only used as a reference to know where a firmware was released. It doesn't matter if you pick a firmware released in for example Germany or one released in Sweden. Same firmware but different label. Just ignore it.
ps the black screen will be solved after you update modem+bootloader.

Lennyz1988 said:
It's only used as a reference to know where a firmware was released. It doesn't matter if you pick a firmware released in for example Germany or one released in Sweden. Same firmware but different label. Just ignore it.
ps the black screen will be solved after you update modem+bootloader.
Click to expand...
Click to collapse
*Update*
Updated the Bootloader (BL_UHOJ2.tar) and Modem (CP_UHOJ2.tar) but blackscreen in calls persists
And since I know that it works 100% in Aurora ROM I'm guessing it's a software issue (I presumed it was fw but maybe not). Running "Proximity Fix" doesn't fix it either, sensor still shows 0cm! It isn't a bad sensor i.e no air blowing issue!
Please advice!!
Thank you

bingoofsweden said:
*Update*
Updated the Bootloader (BL_UHOJ2.tar) and Modem (CP_UHOJ2.tar) but blackscreen in calls persists
And since I know that it works 100% in Aurora ROM I'm guessing it's a software issue (I presumed it was fw but maybe not). Running "Proximity Fix" doesn't fix it either, sensor still shows 0cm! It isn't a bad sensor i.e no air blowing issue!
Please advice!!
Thank you
Click to expand...
Click to collapse
If you go to settings > about phone, what does it say your smallband version (your modem) is?

Lennyz1988 said:
If you go to settings > about phone, what does it say your smallband version (your modem) is?
Click to expand...
Click to collapse
@Lennyz1988
Baseband (modem) I9505XXUHOJ2
{
"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"
}
Thanks

Sorry for the late reply, but I'm still a little intimidated by all this. Which firmware version should I flash? There's the HOJ2 version that seems to exist for many different countries and carriers and some are described as being for branded (simlocked?) phones. My phone is unlocked and I'm using the carrier 1&1 in Germany. Which version do I download? And why is it a 1.5GB file? I thought this was just the modem and bootloader? Or does it only come in combination with a full stock ROM?
Also, any tips on where to download, all the links I find are for filesharing sites that throttle non-premium downloads to ridiculously low speeds.