Develop Bugs

2 things CSC and MODEM

i just did an upgrade thorugh KIES for XEF (french national, not locked)
I got pda: xwjpa
phone: i9000xxjpp
csc: i9000xefjp3
the last time I have used doc's v8 and I had a really bad phone emission pb. everybody whom i called on older phones (not 3G) had a lowsy reception.
that was fixed after the a.m. upgrade.
thus it would be good if any installs of new roms, the phone and csc could be preserved. Obviously something in either of those 2 is particular to the corresponding country/operator.
It would even be great if odin could make a backup from the former installation, thus in case of, it can be reinstalled, at least partially, or a mixe up of Code, phone and CSC.
I am now running xwjpa with the YA-OK kernel (latest version with the corruption fix) and ext4/ext2 advanced lagfix without binds and it works beautifully without any problems and battery lasts. i did not install SetCPU or anything else because it could also cause problems.
by the way.
for the french.
If you want to do KIES upgrade and installation, do the following:
install KIES the latest version, or update it.
remove all LAGFIXES
flash I9000XXJF3 using PIT 512 (this is for the french version only XEF).
the only thing I don't know is if you have to reflash it with or without RE-PARTITIONING.
I did just repartion with the PIT loaded and nothing else. waited for 10 minutes. Then removed the battery for another 15 minutes, and the restarted it in download mode.
Don't be scared you phone is not bricked even if it remains black for a while.
don't care if your SIM is not recognised properly, and you can't enter the code.
start KIES, connect your phone, and you will receive your update without any problems and everything work fine afterward.
The other thing now is the themes.
Before I was using V2 DENA, and i loved it. but it requires a lot of changes in the java files in the framework. I am a little scared that this f...... up my phone again. so i leave it alone for the moment.
Know i have a bench Quadrant of 21xx and the phone os fluent and smooth.

can u up ur modem & csc ? just to see whats in the csc and if the jpp modem is the same as the jpp one found on xda

if you can tell me how to get it of the phone, no pb
especially the phone.
for CSC i can send you my system/csc contents.

dd if=/dev/block/bml12 of=/sdcard/modemjppfr
csc, the directory

Samsung GT-I5510 bad odin flash/wrong region?

So I decided to try a custom rom on my GT-I5510M - I followed the available directions which implied I needed to flash a clean stock rom before proceeding.
I accidentally flashed a rom for the GT-I5510(No "M"), which is for europe(I'm in canada) and now no matter what rom I use, it keeps saying roaming, and randomly stops working or receiving texts. if you put it into airplane mode or restart it, it works for a while, then stops working again randomly.
From what I understand, this is due to the AMSS file which is part of the stock roms, which apparently defines the radio rules/standards/frequencies/etc
I tried to downgrade the phone using ODIN back to the stock rom(which is froyo - the rom I flashed was gingerbread) but the phone failed to boot(and even seemed mostly bricked. it was difficult to get back into download mode)
So now I'm stuck with a rom that isn't for my phone, which thinks its in a different country.
Any ideas on how I can downgrade to froyo again, or find an AMSS which is compatible with gingerbread and my phone?

TLDR:
Basically, I flashed a rom with the wrong AMSS. Now I can't get back to a rom with the proper AMSS. and the only available AMSS for my country is for froyo. whereas the rom I'm stuck with is Gingerbread - apparently the file is incompatible between versions.
I need to either figure out how to get the phone back to froyo, or get a compatible gingerbread AMSS for my country.

Cannot downgrade to 4.2.2 (gt p5210), what should I do?

Hi,
After upgrading OTA to kitkat (australia version) one of my favourite apps stopped working and caused constant reboots to my tab3.
I tried to downgrade with odin to the stock 4.2.2 (auatralia, from sammobile) but I could not. After flshing, the "samsung galaxy tab 3" logo appeared but the tab never turned on, it kept rebooting and rebooting from ours. I tried the same with other 4.2.2 roms with the same results. However I was able to flash any 4.4.2 rom from sammobile.
After that I tried to flash some 4.2.2 roms using twrp and bindroid, I had the same rebooting problems. However, with twrp I can flash 4.4.2 based roms as pimpdroid.
So, I do not why, apparently my tab only accepts 4.4.2 roms... Any suggestions about what should I do to go back to 4.2.2?
Thanks for your time,
A.

Bootloop in P5210
Hi I'm trying to get back to 4.4.2 to 4.2.2 works because although there are excellent applications like Facebook that are causing me problems. But in trying to make the retoroceso as I usually do with ODIN stock form and I was left in a permanent reboot and does not pass the SAMSUNG logo .... solution? Thank you!:crying:

@planinsky, Have you tried a firmware for another region in the world? I live in the United States but have found firmware for the United Kingdom or Canada works best when I flash. There should not be any difference in the firmwares except for regionalization, but it seems some work and some don't work for me. Regional settings can always be tweaked in the Settings panel after install. Do you have a nandroid backup made in TWRP? Those usually always recover a device. I too had a problem having anything flash when I first started making my rom. 3 weeks I had a device that would not boot. So it is recoverable. Odin will save your device.
@planinsky and @MDCB try to download this firmware from Sammobile. This is for the UK 4.2.2 version. http://www.sammobile.com/firmwares/download/28243/P5210XXUANB4_P5210BTUANB1_BTU.zip/
I usually use ODIN 3.07. I assume you know the following but just in case. Remember to flash it in the PDA slot. Only have "Auto reboot" and "F. Reset time" checked.
Using Odin will reset anything the 4.4.2 builds have done to the partitions. If it doesn't work, I can only suggest to try again. When it comes to flashing, sometimes the TWRP builds for our device can be a little goofy in writing. I have not investigated completely. In the 4.2.2 roms I have flashed pimpdroid and cagrom, they seem to flash good with Moonbutt77's philz recovery with very little problems. I however cannot get 4.4 roms to flash in philz but only in TWRP. So sometimes the recovery itself seems to have a problem with the android version, or so it seems.
The above is only written from my experience on this device and cannot predict every situation.
Good luck.

Hi! Thanks for the tips.
Ufortunately, I have already tried 4.2.2 ROMS from different countries (from Sammobile): Australia (the original country of my Tab), UK, New Zealand, Belgium and US. None of them worked. I'm still downloading other ROMS but I'm startin to lose the faith... The custom ROMS I have tried, neither work and get into the bootloop.
The backup I have from TWRP is from a 4.4.2 so it's not a solution.
On the other hand, I can flash almost any 4.4.2 ROM with odin and/or TWRP. So I'm afraid I'll soon give up and I will accept that my Tab will not longer run the app I loved (Movistar TV)... Hopefully with the arrival of lollypop the developers will update the app and the bug which causes the crash will disappear.

How to get from CM10 alpha to CM10.2 stable to CM13 nightly - some info and steps

[This isn't a request for help, I managed to muddle my way through it, but the info needed seems to be scattered and disjointed, so I thought I'd post it here for others.]
Started with a AT&T Galaxy S III phone running a beta version of CM10 (which could never get OTAs). Wanted to get to a stable or more recent version of CM. This phone is referred to as a SGH-i747 or d2att.
Trial and error:
1st Attempt - Flashed TWRP 3.0.2, flashed CM12.1 release, phone boots gets to starting applications and then dies (poweroff).
2nd Attempt - Flashed CM10.3.1 -> fails to flash ro.bootloader does not match expected values
3rd Attempt - Flashed CM10.1 -> fails to flash ro.bootloader does not match expected values
4th Attempt - Flashed CM10.0 -> Works
So, what's going on?
ro.bootloader is the baseband (cellular radio firmware). My phone had "I747UCDLK3", CM10.1 and require Jellybean compatible radio baseband... CM10.1 advise are trying to tell you that your baseband is too old (ro.bootloader is a misleading name for your baseband). In Android you can see your baseband under "About Phone" in settings, or by opening a terminal and typing "getprop ro.bootloader". In TWRP, you can open the terminal and type "getprop ro.bootloader" to get the value.
Fixing it:
I tried lots of different flashes until I found one that uses JOdin3 to flash the radio. The links for JOdin3 are all long dead, but someone mirrored the JAR files here: http://3of5.com/builds.casual-dev.com/files/JOdin3/. In any case, this got CM to see my baseband as I747UCALEM, however TWRP still saw my baseband as I747UCDLK3. This update was enough to get CM10.3.1 running with cellular signal (did not test calling).
Next thing was applying CM12.1, which flashed and started this time, however "Sim card is missing" was reported. CM12.1 + require still newer baseband firmware to work. I was able to find a list of baseband/radio firmwares here: http://forum.xda-developers.com/gal...are-update-t2808654/post53984772#post53984772, the link there (https://www.androidfilehost.com/?w=files&flid=10522) allows you to download flashable packages. I flashed the I747UCUEMJB baseband/radio firmware and then reflashed CM13.0 nightly and Open GApps using TWRP so I could give the phone to my father.
With I747UCUEMJB, CM13 boots and recognizes the sim card. Once we are no longer roaming we'll test to see if further baseband firmware updates are necessary.

undetected sim, Unknown baseband, Rogers, d2can, cm14.1

I recently installed cm14.1 on a Rogers d2can phone and I got unknown baseband and sim card stopped working. I tried flashing different modems which made the situation worse as now even old cm11 roms show unknown baseband.
Can someone please tell me where I can download modem zip file that works for Rogers and for cm14.1?

I recommend flashing the latest KK stock ROM from sammobile.com which will restore your phone back to stock and ensure the bootloader and modem/baseband are matched. After flashing stock and confirming that the imei is correct, then flash twrp, cm14.1, and gapps.

I was downloading from sammobile.com very slow and the download was interrupted in the middle. I will try again later.
Is there a better site to download firmware from?

So I downloaded it and flashed using odin. Flashing took a while but it passed. The phone got stuck on bootloop though.
So I booted to stock recovery and performed a factory reset. Booted again. Now it works!
I'm going to stay on Touchwiz 4.4.2 for a while.

Glad you got it working.

I would not call "staying on Touchwiz 4.4.2", "working" more like opening yourself to a long list of known exploits.
Others are having the same issue (cyanogenmod is dead so I removed the link, hope LineageOS fixes the issue some day.)
Using the last good CM-13 build is probably the best for now.

sim not provision ed MM#2...... easiest fix ....please n thanks;;;;

We'll need more information in order to help solve the sim problem like model #, ROM, etc.