[Q] Lost signal after kernel flashing - Galaxy S Advance I9070 Q&A, Help & Troubleshooting

I'm asking this here as it seems I can't post in the development section.
I have a Galaxy Advance I9070 Stock 4.1.2. And flashed CoCore-E kernel 6.8 (http://forum.xda-developers.com/showthread.php?t=2140597) using Universal Kernel Flasher. After this the signal was lost, luckily changing back to the backuped original kernel restored the signal.
Additional info: Phone won't get signal, but in configuration when manually setting the carrier, the search returns the three major carriers from here, when manually selecting it (Claro in this case) the phone still won't get signal (emergency only)

As there are no replies, can someone at lest quote this in that respective thread?

When did you go from GB to JB? Did you do factory reset then? No one giving you an answer because no one had that problem with just changing kernel. Most problems were when going from GB to JB without doing factory reset.
Послато са GT-I9070 користећи Тапаток 2

Thanks for the reply. The upgrade from GB to JB was the first thing a did when I bought the phone. Opened from it's case and connected it to Kies. Although as you said I did not do a factory reset after the upgrade as I thought it didn't need it as there wasn't any user apps or modification.
Should I backup and do a factory reset (from the stock recovery) and then try to put the Cocore kernel, and see if it gets signal?

Zero.G said:
Thanks for the reply. The upgrade from GB to JB was the first thing a did when I bought the phone. Opened from it's case and connected it to Kies. Although as you said I did not do a factory reset after the upgrade as I thought it didn't need it as there wasn't any user apps or modification.
Should I backup and do a factory reset (from the stock recovery) and then try to put the Cocore kernel, and see if it gets signal?
Click to expand...
Click to collapse
Yeah, you should. Well you can try and see how it goes.

Related

[Q] Possible to have infected kernel in GB?

Hey guys;
Started on Aussie firmware. Flashed to rootable UK GB, but the thing updated to the new ICS, which I know has an unsafe kernel.
I then rooted using dr.ketans method, and I also installed clockworkmod.
Since the kernel was unsafe, I then reflashed the UK rom and tried to skip the ICS update (no luck), but when it installed everything kept FC'ing.
I did NOT perform any recoveries or wipes!
I flashed to a generic, prerooted GB, but everything kept FC'ing. I couldnt access anything. I then flashed back to stock Indian rootable GB, which didnt auto upgrade to ICS. It was fine until I turned the phone off then back on, but now it is doing the same FC thing as the prerooted rom.
So far, I have only used PC Odin (using the single PDA mostly). I also havent performed ANY wipes (I still have all of my contacts and apps from the original Aussie stock). I stuck to Odin because I was told the eMMC bug from my faulty ICS wouldnt be triggered.
I guess the FCing has something to do with not performing a wipe and changing the firmware like 10 times. Unfortunately, I cannot access the *#1234# because the dialler wont work at all.
Bottom line: If I am on stock GB by flashing through Odin, is there still a chance I have an infected kernel? Also, I imagine my best way out of this would be flashing the prerooted ROM and performing a wipe, before moving to something like Paranoid?
Jesus Christ.
Thanks guys,
Vincent.
Edit: Settings is telling me the kernel version is KL3. Guess its safe?
Only official ICS kernels are affected by the emmc bug so unless you are on a LP* rom/kernel you're safe to do a wipe/factory reset. It will most likely solve all your fc problems.
VincentRC said:
Hey guys;
Started on Aussie firmware. Flashed to rootable UK GB, but the thing updated to the new ICS, which I know has an unsafe kernel.
I then rooted using dr.ketans method, and I also installed clockworkmod.
Since the kernel was unsafe, I then reflashed the UK rom and tried to skip the ICS update (no luck), but when it installed everything kept FC'ing.
I did NOT perform any recoveries or wipes!
I flashed to a generic, prerooted GB, but everything kept FC'ing. I couldnt access anything. I then flashed back to stock Indian rootable GB, which didnt auto upgrade to ICS. It was fine until I turned the phone off then back on, but now it is doing the same FC thing as the prerooted rom.
So far, I have only used PC Odin (using the single PDA mostly). I also havent performed ANY wipes (I still have all of my contacts and apps from the original Aussie stock). I stuck to Odin because I was told the eMMC bug from my faulty ICS wouldnt be triggered.
I guess the FCing has something to do with not performing a wipe and changing the firmware like 10 times. Unfortunately, I cannot access the *#1234# because the dialler wont work at all.
Bottom line: If I am on stock GB by flashing through Odin, is there still a chance I have an infected kernel? Also, I imagine my best way out of this would be flashing the prerooted ROM and performing a wipe, before moving to something like Paranoid?
Jesus Christ.
Thanks guys,
Vincent.
Edit: Settings is telling me the kernel version is KL3. Guess its safe?
Click to expand...
Click to collapse
As chasmodo said that wiping in gb again and again even your arse it will not bricked your phone. If you use the latest mobile odin there a data wipe you can check before it install a new rom try it.
Probably. Non wipe gb rom, leaving many ics stuff that messes gb up.
Migrating from ics to gb, go search on that
Sent from my GT-N7000 using Tapatalk 2
I am assuming you did clear cache and dalvik cache before installing a new rom, that's OK, just not to format system or do a factory reset if you are using a kernel that suffers the emmc problem...
If you don't clear cache and dalvik cache then you will have fc's...
Hey guys:
Ended up flashing Abyss, wiping everything, then CWMing paranoid. All good now.
You guys are terrific, I guess this can be locked now? Thanks again!!!
Sent from my GT-N7000 using xda app-developers app

Cant connect to ATT (no calls, no data) and cant save new APNs after upgrading to JB

I upgraded last night to Jelly Bean using these instructions: http://forum.xda-developers.com/showthread.php?t=1775373&page=11 . The last ROM i had flashed was a gingerbread Apex ROM a long time ago, and I think it had i9000 bootloaders (I think this because an i9000 screen pops up first thing when i turn it on, before the devil kernel logo pops up). I ran in to some issues while upgrading so I used Heimdall 1 click without bootloaders to get me back to stock gingerbread and then when I flashed Jelly Bean and the Devil Kernel everything worked (camera, music, etc.) except it doesn't detect any wireless carrier, APNs aren't saved, it doesn't detect when I take my SIM card out, and it also shuts down randomly. I suspect the problem is with the i9000 bootloaders, but what I have read on this forum makes me think installing new bootloaders is somewhat dangerous so I wanted to get advice before I tried anything else. How should I try to fix this? And if I do need new bootloaders, what is the safest way?
Thanks
ahurley said:
I upgraded last night to Jelly Bean using these instructions: http://forum.xda-developers.com/showthread.php?t=1775373&page=11 . The last ROM i had flashed was a gingerbread Apex ROM a long time ago, and I think it had i9000 bootloaders (I think this because an i9000 screen pops up first thing when i turn it on, before the devil kernel logo pops up). I ran in to some issues while upgrading so I used Heimdall 1 click without bootloaders to get me back to stock gingerbread and then when I flashed Jelly Bean and the Devil Kernel everything worked (camera, music, etc.) except it doesn't detect any wireless carrier, APNs aren't saved, it doesn't detect when I take my SIM card out, and it also shuts down randomly. I suspect the problem is with the i9000 bootloaders, but what I have read on this forum makes me think installing new bootloaders is somewhat dangerous so I wanted to get advice before I tried anything else. How should I try to fix this? And if I do need new bootloaders, what is the safest way?
Thanks
Click to expand...
Click to collapse
I don't think it's the bootloaders..I've flashed a jb rom with i9000 boot loaders and I had sim card and data working.. try going back to stock GB, do the whole rooting process, then flash cm9 ics, after that flash JB
Sent from my SGH-I897 using xda premium
zzmomo73 said:
I don't think it's the bootloaders..I've flashed a jb rom with i9000 boot loaders and I had sim card and data working.. try going back to stock GB, do the whole rooting process, then flash cm9 ics, after that flash JB
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Will do as soon as I get home from work. Should I use the same Heimdall method?
While you are in Ginger Bread, you should back up your EFS Folder. I believe that your IMEI was changed in the flash process, and the network could not recognize your phone. In should a case, you could copy the backup of your EFS folder to your JB phone, and restore the IMEI.
kafepuya said:
While you are in Ginger Bread, you should back up your EFS Folder. I believe that your IMEI was changed in the flash process, and the network could not recognize your phone. In should a case, you could copy the backup of your EFS folder to your JB phone, and restore the IMEI.
Click to expand...
Click to collapse
I used titanium backup before I flashed, and also copied all of the contents of my internal and external sd cards to my computer before tinkering with things. So do I already have my EFS Folder? If so, how do I restore it? And if not, how do I back it up when I get back to GB?
For anyone else that might come across this problem, I solved it by flashing this modem, then flashing the kernel again
temporary fix to get data to work: toggle airplane mode off/on
fermata_ said:
temporary fix to get data to work: toggle airplane mode off/on
Click to expand...
Click to collapse
my wifi is not working! ive tried toggling airplane mode on and off but wont work!
Modem reflash worked for me: Thanks!
AHurley: - Thanks for linking to that file, the reflash fixed my issue as well!

Factory reset

I rooted a custom rom to my Note and I am wondering is factory reset still available to me? I want to get back to stock (I know this method will cause a lot work) and this seems the safest method, If I can get back to ginger bread with way.
It seems too easy but I thought, I'd ask.
Thanks for your help.
Simply download and flash GB ROM with Odin
Then wipe cache and data from recovery
Read 1st link on my signature (post 2 and 3 for GB ROM)
Yes, but
dr.ketan said:
Simply download and flash GB ROM with Odin
Then wipe cache and data from recovery
Read 1st link on my signature (post 2 and 3 for GB ROM)
Click to expand...
Click to collapse
Dear Doc,
Thank you for your quick response, Of course, I'll take a look at it. Actually, however, I really wanted to know if factory reset was still an option -- no matter how bad -- for me.
Thanks Again
its an option, but not a good one, youre better off listening to the docter which is why he prescribes this.
That or find out how to flash tar files with ktool, then backup current kernel, flash a safe one like hydra, do your factory resetting, then reflash old kernel with ktool.
all at own risk. Dr Ketans way is best.
Sent with a grin (^.^)
Thanks
baz77 said:
its an option, but not a good one, youre better off listening to the docter which is why he prescribes this.
That or find out how to flash tar files with ktool, then backup current kernel, flash a safe one like hydra, do your factory resetting, then reflash old kernel with ktool.
all at own risk. Dr Ketans way is best.
Sent with a grin (^.^)
Click to expand...
Click to collapse
Thanks for your input. By way of explanation, I bricked my phone thursday night and was lucky enough to get the service people to "fix" it for me while I waited. It scared the bejesus out of me. I use this device hourly - not just daily and the thought of losing it for a week or 10 days caused much anxiety.
So my thought is that doing a factory reset, letting Samsung upgrade the software and then restoring my back up is the 'safest" thing I can do to get my phone back to stock
So if you would take a moment and tell me why a factory reset is not a good alternative, I'd be very interested.
I look forward to your response.
wel if you dont mind emmc bug risk, then its good option. If you do mind, like I do, then its not good option. Personal choice really
Sent with a grin (^.^)
Confused
baz77 said:
wel if you dont mind emmc bug risk, then its good option. If you do mind, like I do, then its not good option. Personal choice really
Sent with a grin (^.^)
Click to expand...
Click to collapse
I thought a factory reset was a good idea because it would give stock GB 2.3.6. I also thought that the bug you are referring to came in ICS 4.0.3.
I think the emmc bug is a major league disaster and if I am exposing myself to it by using a factory reset, I'll dump the idea.
I really appreciate your helping me with this.
no problem.
If your custom rom is gb, then no risk, do your factory reset. If ICS dont cause of bug risk. A safe kernel could help, but its easier dr Ketans way.
Factory resetting on ICS will not give gb by the way.
Sent with a grin (^.^)
Hmmmm
baz77 said:
no problem.
If your custom rom is gb, then no risk, do your factory reset. If ICS dont cause of bug risk. A safe kernel could help, but its easier dr Ketans way.
Factory resetting on ICS will not give gb by the way.
Sent with a grin (^.^)
Click to expand...
Click to collapse
The note N7000 came with GB, I updated to stock 4.0.3 ( got lucky) and then updated to the current custom rom.- Here's where I sit.
Android Version: 4.0.3
Baseband version N7000XXLPT
Kernel version
3.0.15-N70000XXLPY-CL474507
[email protected]#3
SMP Preenpt Fri May 4 04:49:06 KST 2012
BUILD NUMBER
IML74KXXLPY
The phone is NOT rooted
All I want to do is go back to GB stock SAFELY. I thought of using factory reset to do that but wanted to ask about possible problems.
humphster said:
The note N7000 came with GB, I updated to stock 4.0.3 ( got lucky) and then updated to the current custom rom.- Here's where I sit.
Android Version: 4.0.3
Baseband version N7000XXLPT
Kernel version
3.0.15-N70000XXLPY-CL474507
[email protected]#3
SMP Preenpt Fri May 4 04:49:06 KST 2012
BUILD NUMBER
IML74KXXLPY
The phone is NOT rooted
All I want to do is go back to GB stock SAFELY. I thought of using factory reset to do that but wanted to ask about possible problems.
Click to expand...
Click to collapse
Ok, you are not running a custom ROM but a stock one. Factory reset in stock ICS will brick your device. To safely revert to GB, use PC ODIN. Go to Dr. Ketan's thread and find your stock GB firmware, then flash it. Do not wipe anything in stock ICS. This is the thread:
http://forum.xda-developers.com/showthread.php?p=20963707
Sent from my GT-N7000 using xda app-developers app
Duhhhhh
glevitan said:
Ok, you are not running a custom ROM but a stock one. Factory reset in stock ICS will brick your device. To safely revert to GB, use PC ODIN. Go to Dr. Ketan's thread and find your stock GB firmware, then flash it. Do not wipe anything in stock ICS. This is the thread:
http://forum.xda-developers.com/showthread.php?p=20963707
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Just for my info, what tells you it is a stock rom?
Boy, do I feel stupid
So I got everything downloaded and extracted and disconnected the phone and put in download mode (Odin Mode), started Odin, plugged in the extracted file, and then connected the phone to the PC. The PC recognizes the phone but Odin doesn't - no "added" and no port. The firewall and virus checker.
What's next?
Have you installed driver on pc? Even if you have kies installed then also works.
If you dont have it, then find toolbox on my signature, find driver and install to PC, then it will detect device.
Sent from my GT-N7000 using xda premium
yep and switch of usb debugging in settings, development. Just in case thats on. Probably doesnt interfere, but might.
Close Kies when using pc odin.
When in download mode dont forget to confirm with volume up. First time I was like ok nothings happening, Then I saw, damn need to confirm it lol.
Flashing takes a while, so let it complete, even if it looks stuck it might not be. Might take up to an hour to complete. Usually not thought.
Do not check clear efs. Coming from ICS flashing with standard pitfile can be recommended, optional. Anyway after flashing throught Odin, and if rom doesnt boot straight away, do factory reset from recovery mode, then it should boot.
The cleanest factory reset, don't ask me why is from dialer with a code ending in 3855 by the way.
Sent with a grin (^.^)

Putting ICS on My N7000

I just purchased a international Note off EBay. It has GB installed. I am not sure what country this is from but the phone's baseband version is N7000UBKK1 and the kernel version is 2.6.35.7-N7000UBKK2-CL705203. I would like to move to ICS. I need US English as the language. So:
(a) What firmware should I use? I want to use Odin to install.
(b) Is there any possibility of bricking my phone due to the eMMC issue? I have run the eMMC Check app from the Play Store and it says the chip is "insane". But the test of the memory completes without errors. I am not really sure I know what this all means but I want to avoid problems (who doesn't).
(c) I understand the brick problem is with ICS and not GB. Does this continue to be a problem with the various JB roms out there?
Thanks for your time and help.
Flash stock open German XXLRQ then, look for it in dr.ketan's thread for stock roms in note original android dev sticy.
There are no official jb roms for note yet and cm10 or aokp based custom jb roms are totally safe for wipes and all.
Sent from my GT-N7000
For people who just Dont know what version they need to install u can check this from settings -about,or simply just install kies and it will detect ur version,then u can let kies install it for u or u can download it from dr.ketan post then root it then flash any safe kernel as speedmod ir hydracore,one last thing just remember not 2 make any wipes while using stock ICS thats all.
↖(^▽^)↗ Sent from Rego Galaxy Note ↖(^▽^)↗
The brick bug only triggers on unsafe kernels like stock ICS and only if you do wipes like factory resets.
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
So Should I NOT Use a Stock ICS ROM?
Markuzy said:
The brick bug only triggers on unsafe kernels like stock ICS and only if you do wipes like factory resets.
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Hello and thanks to you and the others who have so kindly replied. Does this mean I should find a non-stock ICS ROM to install? I was thinking that going stock would be safer. I was reading this guide <android.gs/update-samsung-galaxy-note-to-official-xxlrq-firmware-update> to updating to the ROM suggested above and near the end it speaks to possibly having to select ‘wipe data/ factory reset’ in recovery mode if, after the Odin install completes, the device fails to boot beyond the logo screen. I would not want to get to that point and not be able to do this if needed.
Also, I would eventually really like to get to JB - especially for the on-device voice command processing. If there is a recommended JB ROM that can do this now and avoid the brick problem, I would appreciate recommendations.
Thanks again for your knowledge and help.
whitedavidp said:
Hello and thanks to you and the others who have so kindly replied. Does this mean I should find a non-stock ICS ROM to install? I was thinking that going stock would be safer. I was reading this guide <android.gs/update-samsung-galaxy-note-to-official-xxlrq-firmware-update> to updating to the ROM suggested above and near the end it speaks to possibly having to select ‘wipe data/ factory reset’ in recovery mode if, after the Odin install completes, the device fails to boot beyond the logo screen. I would not want to get to that point and not be able to do this if needed.
Also, I would eventually really like to get to JB - especially for the on-device voice command processing. If there is a recommended JB ROM that can do this now and avoid the brick problem, I would appreciate recommendations.
Thanks again for your knowledge and help.
Click to expand...
Click to collapse
ofc you can use ICS Stock Rom. But just to be safe you have to flash safe kernel...Speedmod/Notecore/HydraCore are the safer kernels.
For JB there is no official update available from Samsung for our Note. But you can enjoy it with the efforts that developers are doing for us in XDA.
Go to Android Development Section and Have a look on the Topic Titles.Some of them are AOKP/PA/CM10/AOSP... For Me JellyCore is so far gud. You can find the link in my signatures.
I only know u r now in GB.
GB shld be ok to do full wipe. None reporting mmc brick on GB coz of full wipe.
So....
U can do ur full wipe first on stock GB.
Use pc odin to flash ICS 4.04 LRQ.
Voila.... U r on ICS alrd.
Once u r on ics, and on stock ics kernel....
Pls, do not ever do full wipe.
Unless, after that u root and install ics safe custom kernel, then u r safe to full wipe on ics.
Good luck!
Sent from my GT-N7000 at the corner of this rounded earth.
More in Jelly Core?
sahilarora2003 said:
ofc you can use ICS Stock Rom. But just to be safe you have to flash safe kernel...Speedmod/Notecore/HydraCore are the safer kernels.
For JB there is no official update available from Samsung for our Note. But you can enjoy it with the efforts that developers are doing for us in XDA.
Go to Android Development Section and Have a look on the Topic Titles.Some of them are AOKP/PA/CM10/AOSP... For Me JellyCore is so far gud. You can find the link in my signatures.
Click to expand...
Click to collapse
Hello and thanks. I guess it may make sense to bypass the stock ICS which seems to contain issues related to the brick bug and go to something like Jelly Core as you mention. I looked at the page for Jelly Core and see that it says to install using Clock Work Mod and to wipe from a safe kernel first. As a newbie I guess I have some questions:
(a) I am on GB which I understand to be "safe". Is that correct?
(b) Where do I get the CWM for this phone and how do I install it?
(c) To do the "wipe" does that simply mean to use the built-in reset to factory or does this mean something else?
Thanks
Hi there,
a. Yes, Stock GB's are generally safe
b. When your going to flash ROM, each ROM has it's own accompanying CWM.. so when your done choosing which ROM your going to flash your Note to, when your going to bootup in recovery.. and you get the standard CWMR...
c. Yes, Wiping is synonymous to doing the built-in factory reset on your phone (thru Settings), or the alternate way is to go to CWMR and wipe data. Different Methods, same result.
Thanks but...
letters_to_cleo said:
Hi there,
a. Yes, Stock GB's are generally safe
b. When your going to flash ROM, each ROM has it's own accompanying CWM.. so when your done choosing which ROM your going to flash your Note to, when your going to bootup in recovery.. and you get the standard CWMR...
c. Yes, Wiping is synonymous to doing the built-in factory reset on your phone (thru Settings), or the alternate way is to go to CWMR and wipe data. Different Methods, same result.
Click to expand...
Click to collapse
I am sorry but I am still a bit lost here. Before my N7000 I had a Samsung Skyrocket and flashed it using Odin from the GB that was on it to the stock ICS. I found several guides for this online and it worked fine and easily (although I still feared the brickbug). But this is basically all I know about this stuff.
So how do I flash something like Jelly Core? It sounds like I have to install some other was other than I did with Odin/stock ICS on my Skyrocket. Perhaps I need more of a tutorial on how to do this flashing of custom roms. Any suggestions?
I apologize to all for my thick-headedness.
the best and safest way first is to downgrade back to stock GB. Don't do any thing foolish by just flashing a stock ICS (with an unsafe kernel).
Downgrade first to stock GB and work your way up to eventually flash your preferred custom ROM (in cwmr or odin)

[Q] No signal and no APN

I have an AT&T captivate and when I install any rom after stock I have no signal and no apns available (unless I am on stock then I have great signal). It will let me manually enter an apn but it will not stick. I backed up my efs folder from KK4 and replaced it once I went to new rom. I have tried it from stock going to GB, ICS and JB with no luck at all. I can get any rom to load through CWM but no matter what I get no signal and have been reading and searching for 4 days now. Any help would be greatly appreciated! NJD316
NJD316 said:
I have an AT&T captivate and when I install any rom after stock I have no signal and no apns available (unless I am on stock then I have great signal). It will let me manually enter an apn but it will not stick. I backed up my efs folder from KK4 and replaced it once I went to new rom. I have tried it from stock going to GB, ICS and JB with no luck at all. I can get any rom to load through CWM but no matter what I get no signal and have been reading and searching for 4 days now. Any help would be greatly appreciated! NJD316
Click to expand...
Click to collapse
Do you have a modem? What does it say in baseband version (in about phone)? If not, that would be the first thing to look into (flash one).
Is your IMEI fine?
All is back to stock (using Odin) and modem works and imei is good. I can make calls and use Data and WiFi no problem and it picks up my MicroCell. It is when I upgrade to GB, add CWM and try to go to ICS or JB. I have tried CM7, CM9, CM10, and SlimBean 4.2.1 and 4.2.2 and any time I upgrade I lose APNs and it won’t let me add one.
NJD316 said:
All is back to stock (using Odin) and modem works and imei is good. I can make calls and use Data and WiFi no problem and it picks up my MicroCell. It is when I upgrade to GB, add CWM and try to go to ICS or JB. I have tried CM7, CM9, CM10, and SlimBean 4.2.1 and 4.2.2 and any time I upgrade I lose APNs and it won’t let me add one.
Click to expand...
Click to collapse
Because you need to flash a modem after flashing the ROM. Those ROMs don't flash a modem, therefor, after you wipe, you have no modem.
I have tried several modems (6 to be exact) and every time I flash the modem shows in the baseband but stillk no apns or signal, WiFi is fine though.
NJD316 said:
I have tried several modems (6 to be exact) and every time I flash the modem shows in the baseband but stillk no apns or signal, WiFi is fine though.
Click to expand...
Click to collapse
APNs don't just appear, they have to be manually entered and saved.
I know apns don't just appear (on most roms) and they have to be entered manually, in the first post I explained that part . I do appreciate your help on this and your patience and I have had my share of modding my cappy and my sgs2. Basically = I can bring it back to stock (Froyo) and it works fine, if I upgrade to GB or later (to include flashing modems) it shows in the baseband that the modem is there but I have no signal, no apns show and I can manually enter them but they don't stick after saving. I have copied the efs folder that contains the imei and replaced it as many threads have said and it still does not work. I have gone through the process of stock Froyo to JB 4 times with different roms and results are the same.
NJD316 said:
I know apns don't just appear (on most roms) and they have to be entered manually, in the first post I explained that part . I do appreciate your help on this and your patience and I have had my share of modding my cappy and my sgs2. Basically = I can bring it back to stock (Froyo) and it works fine, if I upgrade to GB or later (to include flashing modems) it shows in the baseband that the modem is there but I have no signal, no apns show and I can manually enter them but they don't stick after saving. I have copied the efs folder that contains the imei and replaced it as many threads have said and it still does not work. I have gone through the process of stock Froyo to JB 4 times with different roms and results are the same.
Click to expand...
Click to collapse
Umm, can you try flashing Odin KK4 with bootloaders and see if they stick? That being stock GB 2.3.5
Been through the KK4 process and that didn't work either to get to ICS or JB.
NJD316 said:
Been through the KK4 process and that didn't work either to get to ICS or JB.
Click to expand...
Click to collapse
KK4 is what you should be going back to stock with instead of Froyo, that way you don't flash Bootloaders over and over, pretty much removing the chance to brick your phone.
Once you have the GB bootloaders, to go back to stock, you should use KK4 without bootloaders. (As long as your signal and such is fine on stock GB).
Now, which modem did you try? On JB, you should be flashing the I9000 modems: http://soggycashew.weebly.com/cm7miui--ics-modems.html
I flashed the ugkg3 without any success. I will try the entire process again when I get home. Any particular modem you recommend before I try that one again? I am in Kentucky, USA and there are no points on the website map that is on the link. Thanks Bud.:good:
NJD316 said:
I flashed the ugkg3 without any success. I will try the entire process again when I get home. Any particular modem you recommend before I try that one again? I am in Kentucky, USA and there are no points on the website map that is on the link. Thanks Bud.:good:
Click to expand...
Click to collapse
I can't recommend modem, sadly. They act different on every device and in every area. I have great results with JK4 in the past but it's outdated now.
SO my plan is to start with KK4 (without bootloaders) bringing me to GB, get cwm loaded, flash a i900 modem, make sure signal is good and then I should be able to flash a JB rom from there?
NJD316 said:
SO my plan is to start with KK4 (without bootloaders) bringing me to GB, get cwm loaded, flash a i900 modem, make sure signal is good and then I should be able to flash a JB rom from there?
Click to expand...
Click to collapse
Almost.
If you're on Froyo, flash KK4 with bootloaders. From there, if you need to go back to stock, use KK4 without bootloaders.
Once on GB, make sure you have signal and all his good. Flash Corn kernel and flash the JB ROM you wanna try as per their full instructions.
Finally, try flashing some modems to see which one gives you the best results.
YOU ROCK! It was the corn kernel step. I went from Froyo to Slim Bean 4.2.2 in less than 30 minutes. Thanks Bud!!!!!
Help!
NJD316 said:
YOU ROCK! It was the corn kernel step. I went from Froyo to Slim Bean 4.2.2 in less than 30 minutes. Thanks Bud!!!!!
Click to expand...
Click to collapse
Hi, could you please describe in easier terms how to do it?
Yesterday I was able to upgrade it from 2.3.5 to 4.2.2 and I LOVED IT but got no signal no service at all... i had to take it back to 2.3.5 and today I will try to do it with another stable ROM instead of the nightly that I tried before.
Any tips for me? Thanks a loooot in advanced!
You got no signal and no service simply because you did not follow SlimBean installation instructions.

Categories

Resources