This is not a guide, I just wanted to point out something about the whole downgrade system.
I needed to downgrade my phone to take it to a service center, so i had to flash the original ROM in it. I was coming from the JB indian firmware.
I had read the downgrade thread and lots of people were reporting problems with CSC after downgrading, wich was a concern to me.
The thing is, just for the sake of it, I tried to flash GB without the PIT and CSC files, i just used the PDA posted on the guide and flashed away with Odin 1.85. The flash was successful to my surprise, and i was looking at the Gingerbread homescreen. At that point, 3G didn't work, and the CSC was blank.
Then i flashed my carrier firmware for GB (Movistar - Argentina) and after that 3G was working, and I had only one CSC on the list: TFG, wich I think is the correct one for this region and carrier.
I really don't know if this method can be reproduced, but maybe some of you can give it a shot and report back. At least this way you don't get the CSC problems.
Greetings from Argentina!
/edit: Just to clarify, the steps:
1) Enter download mode (wipes and formatting partitions opcional)
2) Flash with Odin 1.85 ONLY the PDA file "CODE_GT-I9070_I9070DXLD1_CL1068093_REV00_user_SEC_KEY_LD1_8G.tar" that can be found here: http://forum.xda-developers.com/showthread.php?t=2100642
Make sure the only boxes ticked are "Auto Reboot" and "F. Reset Time"
3) Wait for the phone to reboot
4) Once again enter download mode
5) Flash with Odin the GB Firmware for you country and/or carrier. Again, only use the PDA file downloaded from Sammobile, and make sure the only boxes ticked are "Auto Reboot" and "F. Reset Time"
6) Enjoy Gingerbread again!
Piachnp said:
This is not a guide, I just wanted to point out something about the whole downgrade system.
I needed to downgrade my phone to take it to a service center, so i had to flash the original ROM in it. I was coming from the JB indian firmware.
I had read the downgrade thread and lots of people were reporting problems with CSC after downgrading, wich was a concern to me.
The thing is, just for the sake of it, I tried to flash GB without the PIT and CSC files, i just used the PDA posted on the guide and flashed away with Odin 1.85. The flash was successful to my surprise, and i was looking at the Gingerbread homescreen. At that point, 3G didn't work, and the CSC was blank.
Then i flashed my carrier firmware for GB (Movistar - Argentina) and after that 3G was working, and I had only one CSC on the list: TFG, wich I think is the correct one for this region and carrier.
I really don't know if this method can be reproduced, but maybe some of you can give it a shot and report back. At least this way you don't get the CSC problems.
Greetings from Argentina!
Click to expand...
Click to collapse
I had the same problem trying to install Movistar's Firmware, I installed the argentine ARO firmware and it changed my CSC, but Kies still saying "XTC". I will try with your method later, because I want to have the original TFG CSC code.
mybe u can try 'csc changer' app at google play. but it will factory reset your data..make sure to backup important data. it work only with csc that are already inside your current firmware..
Sent from my GT-I9070 using xda app-developers app
hamzani azni said:
mybe u can try 'csc changer' app at google play. but it will factory reset your data..make sure to backup important data. it work only with csc that are already inside your current firmware..
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
I did it, and changed my CSC to ARO, but Kies still saying XTC.
Juaniblade said:
I did it, and changed my CSC to ARO, but Kies still saying XTC.
Click to expand...
Click to collapse
Kies is high as f**k with their XTC....
Well, try reflashing?
Sent from my GT-I9070 using Tapatalk 4 Beta
Jeroenvk94 said:
Kies is high as f**k with their XTC....
Well, try reflashing?
Sent from my GT-I9070 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I downgraded from XXLQE using OP's method and it works! But i'm stuck now with DBT code lol. I will try reflashing with another firmware with multiCSC.
so this proves that re-partitioning or using PIT file is not necessary for the downgrade process..
ODIN analyze and use the default partition of the phone..
this is a good information..
downgrade will be like a walk in the park..
I am now in doubt about the CSC, can anyone confirm that TFG is the correct one for Argentina (carrier: Movistar) ???
I tried to google CSC codes but TFG is nowhere to be found...
I was able to find this version of GB for Argentina:
Argentina (Movistar) | I9070VSLD1 ; I9070TFGLD1
so it seems like you got it correct
The phone showed everything correctly (CSC, Firmware version and Kernel) but when i connected to Kies, it still showed all the data from the India Firmware.....so i don't know. I think it's better than the other method, but still flawed.
Piachnp said:
The phone showed everything correctly (CSC, Firmware version and Kernel) but when i connected to Kies, it still showed all the data from the India Firmware.....so i don't know. I think it's better than the other method, but still flawed.
Click to expand...
Click to collapse
Same for me, but I think the problem is in the movistar's firmware. Try flashing a MultiCSC firm like ARO UBLK1 and it should work by doing a CSC change typing *#272*IMEI# in dialer.
Enviado desde mi GT-I9070 usando Tapatalk 4 Beta
Piachnp said:
The phone showed everything correctly (CSC, Firmware version and Kernel) but when i connected to Kies, it still showed all the data from the India Firmware.....so i don't know. I think it's better than the other method, but still flawed.
Click to expand...
Click to collapse
try to uninstall kies from your pc and re-install it again..
it might still have the data or cache of the old firmware that you are using before..
Definitively that's not the problem, I installed Kies for the first time in this laptop only now, AFTER downgrading.
At least if someone checks only the celphone, the information there will be the correct one. If someone could try what juaniblade proposed, that be great. I already gave my phone to the service center so i cant try it myself.
By the way, movistar (argentina) technicians didn't find anything fishy on the celphone. I think they just flash stock firmware and if the reported hardware malfunction is still there they approve the repair/replacement. They don't have the time to go all detective on your phone.
Conulta movistar galaxy advance!
Piachnp said:
This is not a guide, I just wanted to point out something about the whole downgrade system.
I needed to downgrade my phone to take it to a service center, so i had to flash the original ROM in it. I was coming from the JB indian firmware.
I had read the downgrade thread and lots of people were reporting problems with CSC after downgrading, wich was a concern to me.
The thing is, just for the sake of it, I tried to flash GB without the PIT and CSC files, i just used the PDA posted on the guide and flashed away with Odin 1.85. The flash was successful to my surprise, and i was looking at the Gingerbread homescreen. At that point, 3G didn't work, and the CSC was blank.
Then i flashed my carrier firmware for GB (Movistar - Argentina) and after that 3G was working, and I had only one CSC on the list: TFG, wich I think is the correct one for this region and carrier.
I really don't know if this method can be reproduced, but maybe some of you can give it a shot and report back. At least this way you don't get the CSC problems.
Greetings from Argentina!
Click to expand...
Click to collapse
Hey how are you! im also from argentina dude, and y have a galaxy advance which i udated to JB, (i have movistar) and i regret it. It works teribly, ive tried 4 different versions, today I installed de JB Claro release and still i have problems. The cellphone is slow, it freezes, i have problems uploading music to the SD card and recelntly im unable to open the photo gallery.
Were you having similar problems? or are you satisfied with JB and the cellphone?? I would like some feedback because not many people i know have this telephone flashed to JB. Are you going to upgrade to JB again once the service is over???de
Anyway, i would really appreciate your feedback men! te mando un abrazo!
I downgraded because i was having some hardware problems with the miniusb port.
Anyway, Jelly Bean was big frustration performance wise. Of course, from a features point of view is miles ahead of GB, but the awful performace is just not acceptable. JB stock is pretty much unusable. To make it even bearable you have to get custom kernel and some other mods (other dialer for instance because stock lags like a motherfu*#er). Even then is still behind GB in performance and battery life.
I haven't tried custom ROMs, but i don't think they are much different than a modded stock JB. Neither have i tried CM yet, because i watch a lot of videos and use the video recorder. If they get around this issues on CM it could be a valid choice....
Movistar will give a new phone to reeplace my faulty one, and i'm not planning to flash JB..... when I came back to GB a few days ago (before taking the cellphone to movistar service center) i realized how much JB sucked (you kind of get used to it working like crap).
So i think i will be waiting some more before i make the jump to JB/CM
Anyway, that's my experience, and my opinion. Some people find JB very usuable with some tweaks.
Argentine guy here, too. So, let's say I'd like to try GB... since I flashed JB right away when I got my SGA two months ago, and a friend showed me her SGA with GB and well, apart from the ocassional interface stutter which is always going to be there in GB, it was REALLY snappy. CM10.1-like snappy, amazing. Yes, as you said JB is head and shoulders above GB feature wise, but apart from that it's not that much of a "downgrade" considering the battery life and performance you gain, I think. When the CM guys get the video recording sorted out I'll be using that, but meanwhile I agree, JB is smooth but lags a lot, it gets on my nerves most of the time! Flashing it, doing all the wipes, installing cocore, going all the way to using 4cylturbo/directinject and crossbreeder and there's still some places where it lags, and it gets irritating.
CWM backup first, then I'll flash stock JB... then proceed to flash GB as per your experience... or I might go on with JB, I don't know, lol. What I'd like to know is exactly how you did it... If I understood you correctly, you flashed the PDA in the downgrade thread without the CSC and PIT files, and left all the odin 1.85 settings as they were (I mean, if you're not flashing the PIT file you don't need to tick the repartition box, right?) or did you do something else...?
Thank you!!
How is that possible when Odin aborts the process and asks for a PIT file?
That is right, I just flashed the PDA file from the downgrade guide like any other PDA, meaning that you don't have to check the re-partition box or anything like that. After that, when the downgrade was done, i flashed the GB firmware i wanted (movistar, argentina in my case), you could use the unbranded ARO firmware.
Odin didn't ask for any PIT file... maybe you have to uncheck the re-partition box.
Just an update, I tried this again with 2 other phones and succeded. There are people posting problems with the other method, but this thread seems to be lost in the forum. I will give another heads up on the official downgrade guide, just in case.
Piachnp said:
Just an update, I tried this again with 2 other phones and succeded. There are people posting problems with the other method, but this thread seems to be lost in the forum. I will give another heads up on the official downgrade guide, just in case.
Click to expand...
Click to collapse
So, when i'm understanding your posts, it's possible to use the PDA-file of my country to downgrade JB to GB?
If so, it would be genius. I've JB on my Samsung and it's constantly freezing, hanging and restarting my device.
The cause is of course unknown, and I don't have to count on Samsung. Even when I installed another JB (also stock) it's crappy too.
Thank you in advance, i'm wondering whether this works for me.
Related
Hi!
I have a Brazilian Galaxy Note 10.1 (firmware code: ZVV) and I want to install a ROM that I found in sammobilie that has some improvements.
However this ROM is designed for Chile (firmware code: CHO).
The both firmwares seems to be designed to the same region:
My firmware: N8000UBALGA
Firmware that I want to flash: N8000UBALI3
The difference is the CSC.
I have two questions:
1) Is it "safe" to flash this ROM using Odin?
2) How can I know if the new firmware will have support for Brazilian Portuguese?
Thanks,
Ronan
Ronis_BR said:
Hi!
I have a Brazilian Galaxy Note 10.1 (firmware code: ZVV) and I want to install a ROM that I found in sammobilie that has some improvements.
However this ROM is designed for Chile (firmware code: CHO).
The both firmwares seems to be designed to the same region:
My firmware: N8000UBALGA
Firmware that I want to flash: N8000UBALI3
The difference is the CSC.
I have two questions:
1) Is it "safe" to flash this ROM using Odin?
2) How can I know if the new firmware will have support for Brazilian Portuguese?
Thanks,
Ronan
Click to expand...
Click to collapse
Personally I prefere europian roms (first to get recent updates and have some good samsung apps not avaliable on other countries ) so you can download the Rom from Portugal and flash via Odin , it is safe and you won't lose your waranty. And about Chile , if its native language is Portuguese then its Rom will support portuguees for sure .
Sent from my GT-N8000 using xda app-developers app
hoss_n2 said:
Personally I prefere europian roms (first to get recent updates and have some good samsung apps not avaliable on other countries ) so you can download the Rom from Portugal and flash via Odin , it is safe and you won't lose your waranty. And about Chile , if its native language is Portuguese then its Rom will support portuguees for sure .
Sent from my GT-N8000 using xda app-developers app
Click to expand...
Click to collapse
The language in Chile is not Portuguese, also Portuguese from Portugal is quite different from Brazilian Portuguese.
However in my Brazilian ROM, I have option to select almost all languages in System configurations.
I'm just wondering if the ROM from Chile will also have this option...
So best idea is to go back to sammobile, find your stock rom and have that as a backup in case you decide you need to go back.
The only way you'll know for sure is to try it...
ultramag69 said:
So best idea is to go back to sammobile, find your stock rom and have that as a backup in case you decide you need to go back.
The only way you'll know for sure is to try it...
Click to expand...
Click to collapse
Ok, but it won't brick my device right
Also, I'm not sure what options do I need to set in Odin.
I saw some sites saying to do not mark Repartition. Is it right?
Thanks,
Ronan
Ok, I have flashed the firmware from Chile (CHO) without any problems.
It was almost the same... I only saw one difference: in S Note, you have a scroll bar.
Thus, I flashed my original ROM again (Vivo ROM, ZVV).
Afterwards I had a little problem with Kies. The installed ROM is really ZVV (I checked with *#1234#), but Kies was showing that I had a CHO ROM and that an uptade through Kies is not possible. I tried everything, factory reset, cache wipe, reflash the ZVV ROM, but nothing fixed the problem. Then I realized that the problem was not with my Galaxy Note, but with Kies itself. I uninstalled it and used a register cleanner to remove all entries related to Kies. Then I installed Kies again and the problem was finally fixed!! I think that Kies stored my device information with CHO ROM and did not uptade CSC when I plugged it with the ZVV ROM.
Thanks,
Ronan
Sent from my GT-N8000 using xda premium
Cool, glad everything went well.
Rule of thumb for ODIN, everything is set up when you start ODIN. All you need to do is add the files you wish to flash. Don't change any other settings and,generally, all will be well... There's always a chance of a bad flash but most times it's user error rather than anything else. It can also be a ba download of the flash file. If you have an MD5 checksum for the update, use an MD5 checker app to ensure the flash file isn't corrupted. This will lessen the chance of a failed flash...
Cheers mate...
ultramag69 said:
Cool, glad everything went well.
Rule of thumb for ODIN, everything is set up when you start ODIN. All you need to do is add the files you wish to flash. Don't change any other settings and,generally, all will be well... There's always a chance of a bad flash but most times it's user error rather than anything else. It can also be a ba download of the flash file. If you have an MD5 checksum for the update, use an MD5 checker app to ensure the flash file isn't corrupted. This will lessen the chance of a failed flash...
Cheers mate...
Click to expand...
Click to collapse
if I flash a ROM from another country, will I lose apps and settings?
PS: I anot rooted, so I cannot make backups with titanium
Depends on the update... I'v had updates that wipe ALL data then I've had others where the data is still there... I tend to find its a roll of the dice every time. This is why I root my device....
I updated one just recently, the Oz rom, and it left all data intact however it is better to clear all data otherwise you might have a problem with the new rom and old data causing issues...
My firmware: N8000ZCCMD2 4.1.2
Firmware that I want to flash:Android 4.1.2 XXCMA2 Firmware Details: is that suitable pls help
Flash a different carrier's KitKat 4.4.2 on N8000
Hi! My tablet (N8000) has the 4.1.2 version, and I don't think any KitKat update will come soon, because the device code is SEK (Ukraine / Kyivstar) and you know the situation there.
Therefore I decided to upgrade via Odin to the 4.4.2 official version from Poland, at least. Or any other country that already has the update.
Will I encounter any problems if flashing the ROM from another country? I know the answer is pretty straight forward that everything should be fine, but still, better ask.
Thank you!
Hi all
Sorry to bother you. I upgraded my UK Note to the German JB 4.1.1. a few weeks ago and it's been flying since. I noticed today though, that SamMobile had the German 4.1.2. version available for download (N8010XXUCMA5 / N8010OXACMA5), so I'm now in the process of downloading it.
What I need to know is, is it simply a case of me doing what I did to upgrade to JB before? I used Odin if I remember right, and pointed it toward the ROM I wanted to flash with. Is that all that's needed?
Also, do I need to backup my present setup or won't it affect my present apps when I flash with 4.1.2.?
Many thanks guys
Naith32 said:
Hi all
Sorry to bother you. I upgraded my UK Note to the German JB 4.1.1. a few weeks ago and it's been flying since. I noticed today though, that SamMobile had the German 4.1.2. version available for download (N8010XXUCMA5 / N8010OXACMA5), so I'm now in the process of downloading it.
What I need to know is, is it simply a case of me doing what I did to upgrade to JB before? I used Odin if I remember right, and pointed it toward the ROM I wanted to flash with. Is that all that's needed?
Also, do I need to backup my present setup or won't it affect my present apps when I flash with 4.1.2.?
Many thanks guys
Click to expand...
Click to collapse
Odin flash --> User Data/Apps is not deleted --> reroot (if you want)
Backup is always a good idea
Backing up your current setup is always a good idea, but I had no issue when I flashed it.
Assuming that your not rooted, use Odin or use Exynos Abuse to root and then...
If you are rooted then get a copy of Mobile Odin and select everroot.
Thanks guys
I'm not rooted at the moment. Do I need to root? I haven't felt the need to do so until now, so I'm not really bothered about rooting...
Naith32 said:
Thanks guys
I'm not rooted at the moment. Do I need to root? I haven't felt the need to do so until now, so I'm not really bothered about rooting...
Click to expand...
Click to collapse
No pressing need to root so if you don't want to, then just use Odin to flash it.
You do not need to root to flash using odin just go on the link on my signature to get the tutorial
Bulbous said:
No pressing need to root so if you don't want to, then just use Odin to flash it.
Click to expand...
Click to collapse
Great.
One more question. I swapped from a UK ROM to the German JB one. Is it an easy procedure to go back to the official UK ROM if and when ver. 4.1.2. is available in the UK?
Cheers
Yes it should not be a problem the same procedure but make sure you take a back up
Thanks all
11 minutes and counting before the new ROM is d/loaded...
Just had a look at the rooting guide (thanks Samir) and the first option looks very easy (ExynosAbuse app). If I was to use this method would I lose any functionality of the Note at all? Also, if I have to send my Note back, would Samsung object to the note having been rooted?
Cheers
I dont think mobile odin will flash the hidden or bootloaders, odin or heimdall is a better option
the exynos abuse patch doesn't work on the MA (4.1.2) builds, if you want root use cfautoroot through odin on those.
Rooting will cause issues with samsungs warranty. If you need to return a device to samsung then you need to restore it to stock rom, with no root, they are using a binary counter though that you can get rid of by using triangleaway.
don't forget to use the search on the forum for these topics, there's been quite a bit about them
Well I've followed the instructions like last time, but it won't update - it keeps saying the process has 'FAILED'
Can anyone shed any light on why I can't update???
Confirm that Kies is not running
Sent from my GT-N8000 using XDA Premium HD app
Can you post a screenshot ??
What version of odin are you using
Hi guys
Thanks for the quick replies. I must admit to being a plonker of the highest order - I never put the tablet in d/l mode did I
It's doing its business now. Roll on 4.1.2. goodness!!!
Thanks to all of you for your help
fards said:
I dont think mobile odin will flash the hidden or bootloaders, odin or heimdall is a better option
Click to expand...
Click to collapse
Does.... Less hassle with Mobile ODIN....
I have a very strange problem I have updated my note gt-n8000 to 4.1.2 via OTA but when I returned to 4.0.4 stock rom downloaded from sammobile using odin my mobile network disconnect when the screen is off and reconnect when the device come back from sleep (screen is on) ,I try to reflash using different firmware but the problem persist the country is XSG (UAE) and problem fixed when returned to 4.1.2 or 4.1.1
any one has solution? please help me
hossam sokkary said:
I have a very strange problem I have updated my note gt-n8000 to 4.1.2 via OTA but when I returned to 4.0.4 stock rom downloaded from sammobile using odin my mobile network disconnect when the screen is off and reconnect when the device come back from sleep (screen is on) ,I try to reflash using different firmware but the problem persist the country is XSG (UAE) and problem fixed when returned to 4.1.2 or 4.1.1
any one has solution? please help me
Click to expand...
Click to collapse
What ROMs did you used and how used it in Odin? Did you need PIT file for downgrade?
cocoe
hossam sokkary said:
I have a very strange problem I have updated my note gt-n8000 to 4.1.2 via OTA but when I returned to 4.0.4 stock rom downloaded from sammobile using odin my mobile network disconnect when the screen is off and reconnect when the device come back from sleep (screen is on) ,I try to reflash using different firmware but the problem persist the country is XSG (UAE) and problem fixed when returned to 4.1.2 or 4.1.1
any one has solution? please help me
Click to expand...
Click to collapse
Wifi settings can be set to disconnect when screen off.
My Note N8000 has a hardware problem and will prepare to send to tech service through Operator Tech service, still has N8000 in ICS 4.0.4. I would like to downgrade to ICS 4.0.4 from JB 4.1.2 but I am worry about flash using ODIN. I don't know if needed a special ICS pack or ayone would be OK. My worries are about possible repartition back to ICS and PIT needed at same time as separated PDA, CSC and modem files. Does ICS and JB partitions were the same or if different, were to find a specific distributed list of files for ICS installation and then apply a second update for my operator?
If not needed specific PIT/PDA/CSC and Modem files, could I apply a normal pack using ODIN? what for downgrade from JB?
Thanks
wifi
shaun298 said:
Wifi settings can be set to disconnect when screen off.
Click to expand...
Click to collapse
Wifi doesnot disconnect when screen is off only mobile network I didnot find any solution and I want to keep ICS 4.04 can you help me
PIT
cocoe68 said:
My Note N8000 has a hardware problem and will prepare to send to tech service through Operator Tech service, still has N8000 in ICS 4.0.4. I would like to downgrade to ICS 4.0.4 from JB 4.1.2 but I am worry about flash using ODIN. I don't know if needed a special ICS pack or ayone would be OK. My worries are about possible repartition back to ICS and PIT needed at same time as separated PDA, CSC and modem files. Does ICS and JB partitions were the same or if different, were to find a specific distributed list of files for ICS installation and then apply a second update for my operator?
If not needed specific PIT/PDA/CSC and Modem files, could I apply a normal pack using ODIN? what for downgrade from JB?
Thanks
Click to expand...
Click to collapse
I donot find any pit for gt-n8000 until now only pda file odin is safe to use but you should do clearing of cash and reset through recovery mode after flashing with odin because it may stuck to samsung logo
hossam sokkary said:
I donot find any pit for gt-n8000 until now only pda file odin is safe to use but you should do clearing of cash and reset through recovery mode after flashing with odin because it may stuck to samsung logo
Click to expand...
Click to collapse
Thanks for your support and confidence to install it, I finally decided to flash back from JB to ICS using an INU (India N8000DDALH1) version wich include boot.img, cache.img, hidden.img, modem.img, recovery.img and system.img. After installing old ICS from India, I reset user and partition data from recovery and flash my operator ICS 4.0.4 and it woks perfectly, Now it is in ICS 4.0.4 as I need.
hossam sokkary said:
I donot find any pit for gt-n8000 until now only pda file odin is safe to use but you should do clearing of cash and reset through recovery mode after flashing with odin because it may stuck to samsung logo
Click to expand...
Click to collapse
A quick search in the general section found this - http://forum.xda-developers.com/attachment.php?attachmentid=1943965&d=1367957676
You can go to this thread to verify - http://forum.xda-developers.com/showthread.php?t=2268735
Just remember flashing a pit file can potentially hard brick your device if it isn't right...Your choice to flash, not mine...
great thanks
ultramag69 said:
A quick search in the general section found this - http://forum.xda-developers.com/attachment.php?attachmentid=1943965&d=1367957676
You can go to this thread to verify - http://forum.xda-developers.com/showthread.php?t=2268735
Just remember flashing a pit file can potentially hard brick your device if it isn't right...Your choice to flash, not mine...
Click to expand...
Click to collapse
Thank you very much for replying but can you tell me other website in english that have pit and csc and modem because this website is russian and i understand nothing ,great thanks
great thanks
cocoe68 said:
Thanks for your support and confidence to install it, I finally decided to flash back from JB to ICS using an INU (India N8000DDALH1) version wich include boot.img, cache.img, hidden.img, modem.img, recovery.img and system.img. After installing old ICS from India, I reset user and partition data from recovery and flash my operator ICS 4.0.4 and it woks perfectly, Now it is in ICS 4.0.4 as I need.
Click to expand...
Click to collapse
Thank you for replying but i want to ask you about your mobile network status during device sleeping or standby It show no disconnection
hossam sokkary said:
Thank you very much for replying but can you tell me other website in english that have pit and csc and modem because this website is russian and i understand nothing ,great thanks
Click to expand...
Click to collapse
The first link is to the pit file itself, should open up a download screen...
You don't need the csc or modem as the stock rom or .tar file should contain this... Go to Sammobile to find the stock rom for your region (you will need to register)....
thanks
ultramag69 said:
The first link is to the pit file itself, should open up a download screen...
You don't need the csc or modem as the stock rom or .tar file should contain this... Go to Sammobile to find the stock rom for your region (you will need to register)....
Click to expand...
Click to collapse
yes I see thank you but it is risky to do repartition or not because i flash my country ICS 4.0.4 without repartition and the problem of mobile disconection still persist this problem is not present in jelly bean and not present in ics before updating to jelly bean and what is repartition effect ,sorry for many question and thank you in advance
Using a pit file is risky. If the pit file you use is corrupt, not the right one for your device or has any other problems you will brick your device. Most people here will tell you that you're mad to use pit file when flashing. But hey, if you cant get ANYTHING to work, you're one step off returning it to Samsung and you have a null waranty then I say go ahead and try... You can't make it any worse....
If you don't have all the above conditions then to be honest I'd do a butt ton of research before playing around with the pit file.
Just out of interest, what was so terribly bad about Jelly Bean that you wanted to revert to ICS?
I have an N8000 with XSG and JB. I cannot fault it, and I wouldn't want to go back to ICS
answer
Bulbous said:
Just out of interest, what was so terribly bad about Jelly Bean that you wanted to revert to ICS?
I have an N8000 with XSG and JB. I cannot fault it, and I wouldn't want to go back to ICS
Click to expand...
Click to collapse
My favorite browsers doesnot support flash in jelly bean and my essential using of this tablet is internet browsing so I want to downgrade in addition I donot noticed any practical difference in performance between both version thank you for replying
My reason to return back to ICS is battery drain and mobile operator tech. service visit. My Note 10.1 needs to repair a SIM card slot issue under warranty, I need to restore as operator sold it because of warranty purposes. When it return back to me I will maintain last ICS it exist in the market. It seems to be better than JB, I also have a SGS II and battery drain is terrible when using JB, I returned to ICS and it works much better.
cocoe
You do not need to return it to how the operator sold it. If there is a update to the software pushed out by the manufacturer then warranty is still valid...
If the place you bought it off told you that they're blowing smoke up your arse trying to make it hard as possible for you to return under warranty.
If the sales rep insists then speak to their manager. You can't loose warranty by upgrading the software the Manufacturer is endorsing...
As for battery, I don't know what you are running but battery is fine on JB... I tend to find it takes a day or 2 for the rom to stabilise and battery might suffer for that small amount of time but once it does its awesome...
HELP
my device is made in vietienam please help me to return to ICS
I rooted last night using SamPwn and everything was working well until today... After one of the reboots I did today my phone stopped showing service, my sim card, network operators, and it wont hold an apn.
I have tried power cycling, removing the sim, resetting network settings, and wiping all cache.
Is there any way to only reflash the network portion? I have rooted and flashed quite a few things but havent bothered going into the intricacies and I feel as though this phone has less wiggle room for error. Hopefully you guys can get me a swift answer.
Thanks in advance!
BumpinPanda said:
I rooted last night using SamPwn and everything was working well until today... After one of the reboots I did today my phone stopped showing service, my sim card, network operators, and it wont hold an apn.
I have tried power cycling, removing the sim, resetting network settings, and wiping all cache.
Is there any way to only reflash the network portion? I have rooted and flashed quite a few things but havent bothered going into the intricacies and I feel as though this phone has less wiggle room for error. Hopefully you guys can get me a swift answer.
Thanks in advance!
Click to expand...
Click to collapse
Searching the SamPWND thread should net you a literal ton of solutions, but I'll try to sum it up for you.
Extract the stock firmware for whatever version you're running (QGL,QH3, ETC), and be sure to use 7zip for all of these extraction/archiving steps, then extract the modem.bin from the CP file and NON_HLOS.bin from the BL file. Now, highlight modem and non_hlos files and use 7zip to add to archive, you'll want to keep everything default, and the end result should be a tar file with whatever name you chose for the archive. Use Odin to flash this archive in the AP slot, it should work fine, but if not, you can try using the modified Odin (all default options for both). Once done, be sure to reboot to recovery and clear the cache and also a Network factory reset from settings if you're still unable to gain signal. If you're still not getting signal, you can try flashing the entire CP file and Home_CSC file (be sure to use the HOME_CSC, as regular CSC will overwrite root and start you over from scratch) using their respective slots in odin, though if modem and non_hlos doesn't get it up and running, that may be a redundant step.
Good luck!
instead you can flash combination file COMBINATION_FA70_G955USQU1AQD8 , just google for it. that will help to get Network Signal again
IJoxer said:
Searching the SamPWND thread should net you a literal ton of solutions, but I'll try to sum it up for you.
Extract the stock firmware for whatever version you're running (QGL,QH3, ETC), and be sure to use 7zip for all of these extraction/archiving steps, then extract the modem.bin from the CP file and NON_HLOS.bin from the BL file. Now, highlight modem and non_hlos files and use 7zip to add to archive, you'll want to keep everything default, and the end result should be a tar file with whatever name you chose for the archive. Use Odin to flash this archive in the AP slot, it should work fine, but if not, you can try using the modified Odin (all default options for both). Once done, be sure to reboot to recovery and clear the cache and also a Network factory reset from settings if you're still unable to gain signal. If you're still not getting signal, you can try flashing the entire CP file and Home_CSC file (be sure to use the HOME_CSC, as regular CSC will overwrite root and start you over from scratch) using their respective slots in odin, though if modem and non_hlos doesn't get it up and running, that may be a redundant step.
Good luck!
Click to expand...
Click to collapse
Thank you for this. I did a few queries in there and didn't come up with much but that could be due to my lack of optimized searching.
I ended up reflashing the csc and it wiped all my data but restored my data. I was at work when this happened and, being that I work in a Verizon, I need my phone quite a lot. I have since backed up my EFS and noted the suggestions in this thread so it will not happen again.
Once again I appreciate the help and I am sure it will save me in the near future!
012345678 said:
instead you can flash combination file COMBINATION_FA70_G955USQU1AQD8 , just google for it. that will help to get Network Signal again
Click to expand...
Click to collapse
I will try this next time this happens, thanks!
BumpinPanda said:
I will try this next time this happens, thanks!
Click to expand...
Click to collapse
Just note that the combination firmware he referenced is a universal firmware, and if you use a vzw firmware (ie QGL), it tends to cause issues with data/connectivity. Mixing carrier firmware and universal firmware has always cause me to start fresh, after 20+ roots using SamPWND, we finally came to that consensus.
Just something to keep in mind, 955U1 and 955U do not mix, regardless of version.
IJoxer said:
Just note that the combination firmware he referenced is a universal firmware, and if you use a vzw firmware (ie QGL), it tends to cause issues with data/connectivity. Mixing carrier firmware and universal firmware has always cause me to start fresh, after 20+ roots using SamPWND, we finally came to that consensus.
Just something to keep in mind, 955U1 and 955U do not mix, regardless of version.
Click to expand...
Click to collapse
Funnily enough, besides this issue, my service improved over stock with the root.
But even if that's the case doesn't the U1 simply signify an unlocked firmware version? Why does that cause an issue?
BumpinPanda said:
Funnily enough, besides this issue, my service improved over stock with the root.
But even if that's the case doesn't the U1 simply signify an unlocked firmware version? Why does that cause an issue?
Click to expand...
Click to collapse
Well, technically, it stands for a universal firmware, but I knew what you meant. 955U firmware is carrier specific, while U1 is Universal, as in it should apply to whichever carrier you have, so long as your sim card is in working order and tells the firmware which CSC to use correctly.
For whatever reason, when rooted and flashing the U1 firmware, the csc doesn't quite stick as it should, at least in my observations. Obviously flashing the modem and non_hlos is supposed to cure this issue (no data/connectivity/modem crashes), but I find it doesn't do much but change it in prop settings. My theory is that it's something to do with the efs partition superceding the csc flashed to system after using Ufirmware for root.
Regardless, I'm still trying to find a way to alleviate this issue, but it's a known bug that should be noted when rooting and using a mixture of U and U1 firmware.
IJoxer said:
Well, technically, it stands for a universal firmware, but I knew what you meant. 955U firmware is carrier specific, while U1 is Universal, as in it should apply to whichever carrier you have, so long as your sim card is in working order and tells the firmware which CSC to use correctly.
For whatever reason, when rooted and flashing the U1 firmware, the csc doesn't quite stick as it should, at least in my observations. Obviously flashing the modem and non_hlos is supposed to cure this issue (no data/connectivity/modem crashes), but I find it doesn't do much but change it in prop settings. My theory is that it's something to do with the efs partition superceding the csc flashed to system after using Ufirmware for root.
Regardless, I'm still trying to find a way to alleviate this issue, but it's a known bug that should be noted when rooting and using a mixture of U and U1 firmware.
Click to expand...
Click to collapse
Are you staying on root or stock? The root has helped my data issue slightly over stock and apparently the update for the stock firmware to fix my issue is in the works (but not yet released).
If you do find a stable solution let me know, it's working for now but I still drop to 1x frequently (which happened before root as well).
Thanks again for your help
BumpinPanda said:
Are you staying on root or stock? The root has helped my data issue slightly over stock and apparently the update for the stock firmware to fix my issue is in the works (but not yet released).
If you do find a stable solution let me know, it's working for now but I still drop to 1x frequently (which happened before root as well).
Thanks again for your help
Click to expand...
Click to collapse
Root does seem to help if, like I said, you don't mix and match firmwares, I'm on stock at the moment but will be rerooting tonight. There is a new carrier firmware for vzw and TMO, I'll be using vzw to accomplish the second part of the root method and updating to it (QI6). I'll update with how it goes later tonight or tomorrow, but here the link for the newest vzw firmware.
http://updato.com/firmware-archive-select-model?record=E15BA006A8B211E7963AFA163EE8F90B
IJoxer said:
Root does seem to help if, like I said, you don't mix and match firmwares, I'm on stock at the moment but will be rerooting tonight. There is a new carrier firmware for vzw and TMO, I'll be using vzw to accomplish the second part of the root method and updating to it (QI6). I'll update with how it goes later tonight or tomorrow, but here the link for the newest vzw firmware.
http://updato.com/firmware-archive-select-model?record=E15BA006A8B211E7963AFA163EE8F90B
Click to expand...
Click to collapse
Ah, I see. Root helped even though I used the universal firmware in the SamPWND thread (that could just be an individual issue regarding my area/device).
I'd love to see the results of the new firmware so I am looking forward to your update! Was that the main reason you chose to remove root? That and the 80% situation are the only things bothering me so far. Appreciate the link, you saved me a search
Well... I've been an idiot.
I recently rooted my Galaxy S7 device whilest scanning the xda threads for a custom ROM.
I flashed Lineage OS 15.1 custom ROM. Everything awesome so far. Except... I didn't like the visual estate of the ROM.
So next step, I flashed the Superman ROM 3.0.1 FINAL. this is where things went wrong.
When i booted up my phone after flashing Superman ROM I lost my IMEI & baseband (both say "Unknown").
I tried to flash stock ROM and ended up with 2 "unknown" IMEI's whilest my phone is a single SIM device.
After that I wiped the lot, flashed Lineage again and still no luck. Although with lineage I have my single IMEI which is still "Unknown".
I've tried flashing stock the correct stock roms but whenever I try to flash the via Odin I get a fail after "sboot.bin".
Odin won't go any further.
So in short, I currently have my device unlocked, rooted, with lineage OS15.1 but no cell service due to
IMEI and baseband being "Unknown".
Any idea's how to fix this?
I've tried the guide with the title "[GUIDE] How to fix IMEI / DRK issues [ALL MODELS][COMBINATION UPDATE 03 NOV 2017]"
But no luck. I can't flash stock firmware due to fail after "sboot.bin" both with stock firmware and the combination file
given in the thread.
Now as part of me being an idiot, I have not made an EFS or baseband backup, nor have I got a Smart Switch backup.
I'm also not capable of finding a person with the Z3Xbox.
Kind regards!
Did you try this https://forum.xda-developers.com/galaxy-s7/help/guide-how-to-fix-efs-damaged-samsung-t3850032
Thanks for the reply! Yes,I've tried that guide too. Problem is that I can't flash anything but twrp through Odin. All the rest fails at "sboot.bin". I'm still trying to download latest stock firmware but all the sites are sooooo slow if you don't pay premium... So I'm still waiting for that file to download. I've tried to flash older stock firmware but didn't get past " sboot.bin" and I've read somewhere that since Oreo Samsung doesn't let you flash old firmware on the phone. So that is at the moment my only hope that I can think of.
Make sure you have the latest version of Odin...you can use updato for faster downloads
cippi21 said:
Make sure you have the latest version of Odin...you can use updato for faster downloads
Click to expand...
Click to collapse
I've used different versions of Odin (v3.12, v3.13, v3.11) and I can only download at 50kb/s with updato. They changed there policy. Donate for premium download speed.
I also went to a repair shop today to ask if they knew any solution. The repair guy I talked to didn't know what root or rooting was so that's a dead end...
Oh ok I am kinda running out of ideas I didn't know updato changed their policy....there is a thread on the forum with the stock roms that people shared you might get better speeds using that...also one last thing you can do is use smart switch there is an option for firmware recovery or something like that try that and see
cippi21 said:
Oh ok I am kinda running out of ideas I didn't know updato changed their policy....there is a thread on the forum with the stock roms that people shared you might get better speeds using that...also one last thing you can do is use smart switch there is an option for firmware recovery or something like that try that and see
Click to expand...
Click to collapse
Thanks for helping though! Every helping hand is welcome! Smart switch recognizes my phone but if I select to recover firmware it doesn't recognize my phone because of the lost IMEI. So downloading to recovering stock firmware from samsung is difficult!
Did you try version 3.13.1 of Odin some people that had the same problem as you said it worked for them and also what model of s7 do you have
cippi21 said:
Did you try version 3.13.1 of Odin some people that had the same problem as you said it worked for them and also what model of s7 do you have
Click to expand...
Click to collapse
Jep, exact version that I used. I have a Samsung galaxy S7 unbrandend from Belgium. (SM-G930F)
Just read through your post again the superman rom is using the new bootloader 3 and as far as I know you can't downgrade to a bootloader 2 do you get a binary error in odin when you flash? Just trying to figure out what is going on when it stops at sbin
This is the latest rom for your country I know is branded as you can see but is the new bootloader 3 ...G930FXXS3ERI1 - GALAXY S7 SM-G930F PRO BELGIUM (PROXIMUS)
Found it on Sam mobile did you flash that one?
cippi21 said:
Just read through your post again the superman rom is using the new bootloader 3 and as far as I know you can't downgrade to a bootloader 2 do you get a binary error in odin when you flash? Just trying to figure out what is going on when it stops at sbin
This is the latest rom for your country I know is branded as you can see but is the new bootloader 3 ...G930FXXS3ERI1 - GALAXY S7 SM-G930F PRO BELGIUM (PROXIMUS)
Found it on Sam mobile did you flash that one?
Click to expand...
Click to collapse
That's what I was thinking. I've read the exact same thing yesterday. So I started downloading the firmware you just mentioned and the PHN Netherlands one. If one fails I've got another to try. Problem is, with those magnificent download speeds, it takes 24hours to download one of them (yeeeey 50kb/s!!!!!) It should be on my hard drive by tomorrow.
I'll keep you posted if this gets me past the Odin troubles!
I really appreciate you thinking along with me good sir! Thanks for your suggestions!
diSke said:
That's what I was thinking. I've read the exact same thing yesterday. So I started downloading the firmware you just mentioned and the PHN Netherlands one. If one fails I've got another to try. Problem is, with those magnificent download speeds, it takes 24hours to download one of them (yeeeey 50kb/s!!!!!) It should be on my hard drive by tomorrow.
I'll keep you posted if this gets me past the Odin troubles!
I really appreciate you thinking along with me good sir! Thanks for your suggestions!
Click to expand...
Click to collapse
I did exactly the same mistake as you (Lineage, Superman ROMS) and even bricked it trying to fix it!
The reason for that error code in my experience was that I was attempting to put the original firmware on the phone. Thanks to XDA forums and about a week of reading I realised that I had the Oreo ROM on the phone before all this happened, so I did what the poster above recommends and used the latest Odin and the latest firmware for your country from Sammobile. Bam! My S7 is running better than ever!
cippi21 said:
Just read through your post again the superman rom is using the new bootloader 3 and as far as I know you can't downgrade to a bootloader 2 do you get a binary error in odin when you flash? Just trying to figure out what is going on when it stops at sbin
This is the latest rom for your country I know is branded as you can see but is the new bootloader 3 ...G930FXXS3ERI1 - GALAXY S7 SM-G930F PRO BELGIUM (PROXIMUS)
Found it on Sam mobile did you flash that one?
Click to expand...
Click to collapse
Old man android said:
I did exactly the same mistake as you (Lineage, Superman ROMS) and even bricked it trying to fix it!
The reason for that error code in my experience was that I was attempting to put the original firmware on the phone. Thanks to XDA forums and about a week of reading I realised that I had the Oreo ROM on the phone before all this happened, so I did what the poster above recommends and used the latest Odin and the latest firmware for your country from Sammobile. Bam! My S7 is running better than ever!
Click to expand...
Click to collapse
You guy's are all amazing! Thank you so much!
Today I had the chance to flash original firmware to my phone. Flashed latest stock firmware from Holland (because Belgium firmware was branded and my S7 was unbranded).
Rebooted the phone, filled in the start menu's went in to settings and BAM, lost IMEI was lost no more!
Inserted my SIM card and had 4G connection! I didn't even had to flash the COMBINATION file.
I learned from my mistakes and immediatly flashed TWRP and made an EFS en IMEI backup!
Again, thank you so much good sirs! You guys really helped me not to lose hope!
Glad you fixed your phone hopefully this will help other people
diSke said:
You guy's are all amazing! Thank you so much!
Today I had the chance to flash original firmware to my phone. Flashed latest stock firmware from Holland (because Belgium firmware was branded and my S7 was unbranded).
Rebooted the phone, filled in the start menu's went in to settings and BAM, lost IMEI was lost no more!
Inserted my SIM card and had 4G connection! I didn't even had to flash the COMBINATION file.
I learned from my mistakes and immediatly flashed TWRP and made an EFS en IMEI backup!
Again, thank you so much good sirs! You guys really helped me not to lose hope!
Click to expand...
Click to collapse
Absolutely my pleasure! This site has taught me so much, it's great to give a little back.
Hi diSke, Did you find any solution for your IMEI issue, as i also faced same issue and lost IMEI after flashing Superman ROM, and faced same issue. Please let me know steps if you resolved the issue. Thanks in advance.
tarun2k9 said:
Hi diSke, Did you find any solution for your IMEI issue, as i also faced same issue and lost IMEI after flashing Superman ROM, and faced same issue. Please let me know steps if you resolved the issue. Thanks in advance.
Click to expand...
Click to collapse
Flash the latest version firmware for your region/network provider. IMEI restored.
cooltt said:
Flash the latest version firmware for your region/network provider. IMEI restored.
Click to expand...
Click to collapse
Earlier i was trying to flash via wrong Odin version 3.14. But after using Odin 3.13 version the latest firmware was successfully flashed and IMEI is restored back successfully. Thanks a lot for your help.