I really wanted to work this out myself but my time is very limited, I do not have access to a PC so don't want to risk bricking, and I've already spent many hours searching answers and downloading files. I need a working phone ASAP and it's not easy finding a spare in my current situation.
My phone died (battery) while active as hotspot. I replaced battery and now it won't detect ANY sim card (sim cards verified to work). Upon attempting to access mobile network settings: "Insert sim card to access network services".
Also, I'm not sure if it's related or not, but IMEI number is "unknown".
I'm really hoping it's a software/firmware corruption issue that I can fix.
I have tried the following:
Replacing sim
Fight mode
Restarting
Combinations of the above 3
Wiping SD card
Factory reset
Reflashing CF-root kernel via CWM (I think it worked but reboots before I can read log).
Now I want to try flashing a custom ROM. I have CWM installed and I was going to install CyanogenMod. I am aware of how to do this, but...
- I read that attempting to flash a JB ROM over a gingerbread kernel can cause an issue and that I may need to flash a JB kernel before installing cyanogenmod. Is this true? And if so, where can I find out what kernel to flash. I've seen lists, but I see all these numbers and names which don't really mean anything to me. Is there a stock JB kernel that would be suitable, or is any KB kernel fine?
- Does installing a custom ROM like CM not flash it's own custom kernel? Because I don't understand why having a gingerbread kernel should potentially cause issues.
- Is there anything that installing a custom ROM like CM doesn't flash (apart from bootloader)?
- Should I just flash a stable gingerbread CM ROM instead?
I appreciate any info
Cheers
[edit]
I also flashed modem. Problem persists.
Ok mate u said u want flash cm10.2 looks u got cwm ok then do this download ur cm10.2 rom copy to sd card then download latest kernel 9.39 from this link
http://dorimanx.shine.sk/
Copy tu ur sd
After that boot into cwm find kernrl u downloaded dorimanx9.39 and flash , when u do that reboot cwm and start flashing ur cm10.2 and dnt forget about gapps
Now u can enjoy ur cm10.2 .
Omt if u wanna stay with stock cm kernel just reboot but if u wanna have most adwenced kernel for sgs2 after flashing cm flash again dorimanx 9.39 a to solve ur missing imei chose one of this modems from this link http://forum.xda-developers.com/showthread.php?p=31416701 and flash exacly the same like rom,kernel a if u got crap reception flash another modem.
Hit thx button if i helped u
Sent from my GT-I9100 using xda premium
At op do you have a efs bk up?
I9100/I9300
Flashing anything without a PC nearby is lunacy/asking for trouble. If something goes even slightly wrong, you won't be fixing it without one.
DSMB said:
I really wanted to work this out myself but my time is very limited, I do not have access to a PC so don't want to risk bricking, and I've already spent many hours searching answers and downloading files. I need a working phone ASAP and it's not easy finding a spare in my current situation.
My phone died (battery) while active as hotspot. I replaced battery and now it won't detect ANY sim card (sim cards verified to work). Upon attempting to access mobile network settings: "Insert sim card to access network services".
Also, I'm not sure if it's related or not, but IMEI number is "unknown".
I'm really hoping it's a software/firmware corruption issue that I can fix.
I have tried the following:
Replacing sim
Fight mode
Restarting
Combinations of the above 3
Wiping SD card
Factory reset
Reflashing CF-root kernel via CWM (I think it worked but reboots before I can read log).
Now I want to try flashing a custom ROM. I have CWM installed and I was going to install CyanogenMod. I am aware of how to do this, but...
- I read that attempting to flash a JB ROM over a gingerbread kernel can cause an issue and that I may need to flash a JB kernel before installing cyanogenmod. Is this true? And if so, where can I find out what kernel to flash. I've seen lists, but I see all these numbers and names which don't really mean anything to me. Is there a stock JB kernel that would be suitable, or is any KB kernel fine?
- Does installing a custom ROM like CM not flash it's own custom kernel? Because I don't understand why having a gingerbread kernel should potentially cause issues.
- Is there anything that installing a custom ROM like CM doesn't flash (apart from bootloader)?
- Should I just flash a stable gingerbread CM ROM instead?
I appreciate any info
Cheers
[edit]
I also flashed modem. Problem persists.
Click to expand...
Click to collapse
The problem is the unknown IMEI because the phone gets identified my this unique number. If its lost, SIM-Cards won't work. If you made an EFS Backup, it should be easy to recover the IMEI. But if you didn't...it will be nearly impossible.
stopro said:
Ok mate u said u want flash cm10.2 looks u got cwm ok then do this download ur cm10.2 rom copy to sd card then download latest kernel 9.39 from this link
http://dorimanx.shine.sk/
Copy tu ur sd
After that boot into cwm find kernrl u downloaded dorimanx9.39 and flash , when u do that reboot cwm and start flashing ur cm10.2 and dnt forget about gapps
Now u can enjoy ur cm10.2 .
Omt if u wanna stay with stock cm kernel just reboot but if u wanna have most adwenced kernel for sgs2 after flashing cm flash again dorimanx 9.39 a to solve ur missing imei chose one of this modems from this link http://forum.xda-developers.com/showthread.php?p=31416701 and flash exacly the same like rom,kernel a if u got crap reception flash another modem.
Hit thx button if i helped u
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks for the info. However I have flashed multiple modems and phone is still nit detecting sim. IMEI still missing.
H3llwar said:
The problem is the unknown IMEI because the phone gets identified my this unique number. If its lost, SIM-Cards won't work. If you made an EFS Backup, it should be easy to recover the IMEI. But if you didn't...it will be nearly impossible.
Click to expand...
Click to collapse
I'd never heard of backing up the EFS before yesterday, so unfortunately I don't have one with IMEI. I think I have a nandroid backup at home somewhere, would this have a backup of the EFS/IMEI?
If I had it written down, would that allow recovery of EMEI?
Some roms bk up to efs folder so looking in to your sd card you may have one. Flash the nand if not it may restore it. May not though. Worth trying. Have you tried to flash gb firmware with odin as this has for some got it bk.
I9100/I9300
andrewwright said:
Some roms bk up to efs folder so looking in to your sd card you may have one. Flash the nand if not it may restore it. May not though. Worth trying. Have you tried to flash gb firmware with odin as this has for some got it bk.
I9100/I9300
Click to expand...
Click to collapse
If I have a backup it will be on my PC or a HDD on the other side of the planet. But I will indeed look for it when I can. I'm fairly confident I would've done a full backup before I flashed a CF root kernel via Odin when I originally rooted the phone.
And no I haven't tried to flash gingerbread firmware via Odin. I don't have access to a PC. But I did flash the CF root kernel via CWM.
Your gonna need to look and hope your have mate or service center job. Local phone shop could prob do it to.
I9100/I9300
Fixed. Thanks stopro.
The phone was deteriorating. Apart from not detecting sim cards, it somehow lost su access. Even though I would allow access it would fail (issue with system/xbin/su). I couldn't even connect to WiFi anymore.
Flashed Dorimanx kernel 9.39
Flashed latest CM 10.2 nightly
Flashed GApps
Flashed modem
Wiped cache and Dalvik cache 2x each
Did a data wipe/factory reset
Booted
All working fine. IMEI number is displayed correctly. WiFi connected immediately (could not successfully obtain IP address before). I had to re unlock my phone to use a different carrier sim (I unlocked it before leaving Australia, but that flashing must've relocked it). Now it is connected to 3G with which I am posting this reply.
Not really digging this JB style, but hopefully I'll get used to it. Happy I've got phone all working properly though.
Related
Hi All,
Just got my S2 last week. Planning to move to CM7 this weekend. I have rooted the device and am on the Codeworkx kernel. I had a few questions:
1. Is there a problem while flashing via Odin if Debugging is not enabled (I think it is more of a OS feature which we haven't entered when in download mode, so shouldn't matter according to me.) ? I tried to disable debugging, and then went to download mode and Odin did detect the phone, but I did not try to flash anything so if anyone has tried that, your input is more than welcome.
2. The reason for above question is: What if I completely brick my phone (with debugging disabled) and no ROM .zip in the sd storage, how do I get the phone up and running ? I understand that I can flash kernels via Odin, but is it true for ROMs as well ?
3. What's the issue with ROM manager ? Is it recommended to stay away from it for S2 ? I have tried to do a Nandroid backup and it always takes me to the Android robot with a exclamation mark screen. Then I have to reboot and the backup magically restarts and completes successfully. Most people have suggested to use CWM recovery directly, so not sure if I should get rid of the ROM manager altogether.
That should be all for now. I have a jig ready by the way, so am not that worried about the process and plan to do a fair bit of reading before proceeding, however, the answers to above queries would be really great !
Thanks in advance,
Ish
I can answer some of your doubts.
I don't know if you can flash via odin in case you don't have the usb debuggin enabled so I'm not going to say anything about it.
Anyway if something happens to your phone and you dont have any ROM on your sd card but you have CWM recovery installed (which is almost everytime the case) then in CWM there is a mount usb stoage option. With it you can easily transfer .zip ROM files to flash, or even a nandroid backup you saved in your PC.
ABout ROM manager, this is what I suggest you. The first time you flash CM7 don't use ROM Manager (I even tried using it with the codeworkx kernel with no luck). Now, once you are in CM7 it works perfectly and it's really helpful to flash nightlies withouth wiping data (I flash half the nightlies as they are realeased). So the first time you flash CM7 wipe everything (do a nandroid backup first), even wipe /system, /data, cache partition, dalvik cache, so you don't have any problems. THen install zip from sd card and when it finish install the zip file again (just two installs in a row no wiping in beween, trust me, the first time I tried I didn't do that and couldn't boot the phone).
Hope it helps.
EDIT: You can flash stock ROM via odin, there is a thread by infratech were this is explained and you have a list of downloable stock ROMS you can flash with Odin, these are region and carrier specific and you probably will get the one for your carrier. I found the stock ROM for my carrier and I'm from chile, you shouldn't have any problems with that. Well, good luck, CM7 is by far the best ROM I've flashed.
Oh another thing, go for the latest nightly since the battery life is incredibly improved over the RC (or was it stable?) version.
Thanks !
tomascunill said:
Anyway if something happens to your phone and you dont have any ROM on your sd card but you have CWM recovery installed (which is almost everytime the case) then in CWM there is a mount usb stoage option. With it you can easily transfer .zip ROM files to flash, or even a nandroid backup you saved in your PC.
Click to expand...
Click to collapse
Awesome ! This is exactly what I was looking for. I haven't dived into all the options of the CWM, so didn't know that this feature existed.
Also, many thanks for explaining most of the things in a single concise post, it was very helpful. I'll have to check the ROM flash with Odin, so I will search for that thread and have a go through it later today.
Once I get a hang of CM7, I'll go in for the nightlies as well. And yes, I did read about the CM7 guys revert the status to an RC because of the bugs reported, so will give it a try once I definitely know what I'm getting into .
Thanks again,
Ish.
cheemais said:
Awesome ! This is exactly what I was looking for. I haven't dived into all the options of the CWM, so didn't know that this feature existed.
Also, many thanks for explaining most of the things in a single concise post, it was very helpful. I'll have to check the ROM flash with Odin, so I will search for that thread and have a go through it later today.
Once I get a hang of CM7, I'll go in for the nightlies as well. And yes, I did read about the CM7 guys revert the status to an RC because of the bugs reported, so will give it a try once I definitely know what I'm getting into .
Thanks again,
Ish.
Click to expand...
Click to collapse
Well good luck! Tell me if you get any problem.
Hello.
My brother just bought his new razr hd and gave me his galaxy s2. At least its much better than blackberry.
Im having some problems with it and I have some doubts.
thanks for your time
-I didnt ask my brother because he is travelling for his work.
1- Once rooted, always rooted? I saw somewhere that if I reflash the baseband I could lose the root. Is that true?
My brother rooted it with 4.0.3 with a bug that you dont even needed to plug the phone to the pc to root it. It had a brazilian firmware, then he flashed a trinidad tobago firmware and did the root. I want to reflash the modem and try new modems. Thats why im concerned about. Can I do it without any concerns?
My root does not have the yellow triangle on boot.
2- Then he installed CM9. Can I factory wipe it via CWM? Im afraid of that superbrick bug, but it now has CM9 kernel. Im safe, right?
It has the crazy chip. Checked with an app.
3- Are you guys also having problem with the new ROM manager version? 5.9.3.0? None functions that need root permissions work. If I uninstall to previous version, it works.
4- Why ROM manager it asks me to install a "new" 6.0.1.0 version when I have a 6.0.1.2 CWMR?
5- I did a factory reset via menu. It is the same as doing factory wipe on CWMR?
6- When he flashed CM9, the wifi roaming bug was fixed. But after I factory reset, it seems to stopped working. When I move between access points, the signal increases then it disconnects and reconnects...
Thanks.
Questions belong in Q&A
facsi2 said:
Hello.
My brother just bought his new razr hd and gave me his galaxy s2. At least its much better than blackberry.
Im having some problems with it and I have some doubts.
thanks for your time
-I didnt ask my brother because he is travelling for his work.
1- Once rooted, always rooted? I saw somewhere that if I reflash the baseband I could lose the root. Is that true?
My brother rooted it with 4.0.3 with a bug that you dont even needed to plug the phone to the pc to root it. It had a brazilian firmware, then he flashed a trinidad tobago firmware and did the root. I want to reflash the modem and try new modems. Thats why im concerned about. Can I do it without any concerns?
My root does not have the yellow triangle on boot.
2- Then he installed CM9. Can I factory wipe it via CWM? Im afraid of that superbrick bug, but it now has CM9 kernel. Im safe, right?
It has the crazy chip. Checked with an app.
3- Are you guys also having problem with the new ROM manager version? 5.9.3.0? None functions that need root permissions work. If I uninstall to previous version, it works.
4- Why ROM manager it asks me to install a "new" 6.0.1.0 version when I have a 6.0.1.2 CWMR?
5- I did a factory reset via menu. It is the same as doing factory wipe on CWMR?
6- When he flashed CM9, the wifi roaming bug was fixed. But after I factory reset, it seems to stopped working. When I move between access points, the signal increases then it disconnects and reconnects...
Thanks.
Click to expand...
Click to collapse
Before I answer anything, please check this out:
http://forum.xda-developers.com/showthread.php?t=1763193
Now then,
1. Root remains until u manually unroot it (by removing su binary and Superuser app), unroot using SuperSU app, or flash a stock firmware. Flashing a baseband (or modem) doesn't unroot your phone. But flashing an entire firmware does. Still, you can always root if you get unrooted!
2. Brickbug only affects stock 4.0.4 firmwares with stock kernel. CM9 should be safe to do a full wipe, since you're on a custom kernel. :good:
3 & 4. I suggest you stay away from ROM Manager as many members have reported problems while using it. Since u already have CWM, you don't need ROM Manager.
5. Factory reset via Settings and via Recovery ought to be the same. I prefer to do via CWM though.
6. I don't know about this as I haven't tried CM9 for a long time! Maybe you should check out the CM9 discussion thread to see if someone else has ur issue, and look for a possible fix for it.
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
muffintastic said:
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
Click to expand...
Click to collapse
To avoid brickbug is by flashing JB 4.1.2. (good alternative!)
But if you really like ICS then i suggest you move back to 4.0.3. There is no avoiding brickbug on 4.0.4.
If you have rooted it, you can check with 'Brickbug check' app on google play, to see if you have sane (or insane) chip (brickbug or not), cause most custom kernels and roms have found a solution to this bug, and use it on their roms/kernels. Which means on those you can safely wipe and restore etc.. (but check brickbug app first on google play)
Yep. Don't wipe a rooted phone running 4.0.4. And if you're really paranoid, don't even wipe a non-rooted phone running 4.0.4 (Entropy mentioned at least one case he knew of where someone borked their phone doing a wipe on a phone running 4.0.4 via stock Android recovery, tho it seems to be very rare).
The TL;DR is don't run rooted stock 4.0.4 if you mess with your phone in any way.
I know that's not a fix, but that's because there isn't one. Some chips aren't susceptible to the bug; there's an app floating around here somewhere/Google Play where you can check which chip you have (seems to be more that are susceptible).
Your 1st paragraph is a load of crap.Bootloop has nothing to do with "brickbug".More like by you not running kernel cleaning script,or not factory resetting before/after flashing a new rom.
As mentioned by others,just dont have 4.0.4 running on your phone.So you are still left with over 100 custom/stock roms to choose from........lol
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Hopper8 said:
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Im not sure Hopper.I am leaning towards the restore would be "cancelled" due to not being complete,rather than it succeeding leading to bootloop.
But hes not said.
And he cant get "factory" rom with a restore as it didnt come with cwm lol.
Sorry to clear things up.. I updated it to 4.1.2 via Kies many months ago. I used PhilZ method to root, no problem. Few months down the line since then I put LiquidSmooth 2.4 (few days ago) then restored a backup from PhilZ recovery and put 4.1.2 and everything back on no problem. Then restarted the phone and it when into a boot loop of the Orange and Samsung logo.
I'm not stupid as I've rooted my own SGS3 and Samsung Galaxy ACEs etc, Just forgotten to put that info in lol and yes I always use the Factory Reset to install a new rom.
And yes when I managed to get it restored from this so called boot loop (by putting 4.1.2 Orange UK firmeware back on via Odin) the EMMC brick bug is present as i've checked via an app via Google Play. My overall goal is to eliminate this problem or temp fix so I can put different roms on and if I don't like them recovery back to the latest restore without issues.
Are we on the same line now ?
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
help me out here please
MistahBungle said:
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
Click to expand...
Click to collapse
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
andreshbozo said:
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
Click to expand...
Click to collapse
Here is my situation.
I had 4.1.2 JB. Installed CM11 M8 and CWM_6.0.4.7(coming previously from Siyah) at the end of July. In the beginning of October my phone just shut down. That happened before on the same and previous rom so I wasn't worried. I turned it on and phone was in bootloop. That was strange because the last time that happened I installed Chainfire. So bootloop without any cause..that was strange. I tried making a backup before flashing the ROM. But I got an error. I can't remember but I can dig it somewhere if you want it. I tried then flashing recovery(bad idea) and Odin again reported an error. When I restarted phone I noticed that my Recovery mode was gone. Just gone and with no solution on how to restore it. I tried numerous methods OMAP drivers, heimdall, .pit file method but nothing. So I brought my sgs2 to the store where I bought it and they concluded that it was bad eMMC chip.
Now, your problem reminds me of mine because Odin wouldn't want to flash anything without an error(well, not exactly anything, I managed to flash some partition using Heimdall but it was not sufficient) but it doesn't have to be.
What version of cwm were you using?
Hi
I am New To XDA
I have a Galaxy S3 i9300 International. I rooted it succesfully and Installed CWM recovery on it. And i tried to install custom ROMS but After installing Custom RoMs I couldnt get Network Signal. Coverage quickly comes and disappears. Sim also not showing. Tried Almost 5 ROMS ( Kitkat, Lollipop , S5 Ported etc....)
But nothing helped. But when i go to stock rom everything works like charm no any problems.
Why cant i get network in any of CuStom ROMs
NOTE: Tried Registering Manually too
@shamuzny: which stock ROM does work for you (build and baseband)?
If your stock rom is 4.1.2 then it is efs v1. You need efs v2 to get signal on kitkat or lolipop roms. First install an official 4.3 rom for your country and upgrade your efs. Then install custom roms that you said.
But IMPORTANT!!! get a clean efs backup of your old v1 incase you want to go back. And after you install 4.3 get an clean efs of your v2 efs too...
If you dont know what i am talking about, make a good search, understand everything and then do it. If you do something wrong there may be no going back....
thewalekk said:
If your stock rom is 4.1.2 then it is efs v1. You need efs v2 to get signal on kitkat or lolipop roms. First install an official 4.3 rom for your country and upgrade your efs. Then install custom roms that you said.
But IMPORTANT!!! get a clean efs backup of your old v1 incase you want to go back. And after you install 4.3 get an clean efs of your v2 efs too...
If you dont know what i am talking about, make a good search, understand everything and then do it. If you do something wrong there may be no going back....
Click to expand...
Click to collapse
I was on 4.1.2 then Flashed to 4.3 then also i had an update of 11.94MB i did that also
And rooted and installed but sadly i couldnt get the network
@rp158
rp158 said:
@shamuzny: which stock ROM does work for you (build and baseband)?
Click to expand...
Click to collapse
I9300Ddugmk1
This is my baseband
@shamuzny: then you should have efs v2 -data. As advised yet, download the actual firmware from sammobile.com, flash it with Odin and make a factory reset in recovery. Then root again and make an efs-backup. Network access at the end of procedure?
rp158 said:
@shamuzny: then you should have efs v2 -data. As advised yet, download the actual firmware from sammobile.com, flash it with Odin and make a factory reset in recovery. Then root again and make an efs-backup. Network access at the end of procedure?
Click to expand...
Click to collapse
Actually I bought the phone from Dubai and i dont know its original country of manufacture
So i flashed it by Sri Lanka"s Firmware which i had earlier. How to find the country of manufacture? Please help me
@boomboomer, will you help a bit?
https://www.dropbox.com/s/f1zbm0tvsvh5ww5/MegaWipe_-_GS3.zip?dl=0
https://www.dropbox.com/s/qzgn1abhr4qcmls/Ultimate_Kernel_Cleaning_Script_v1.0_en_SGS3.zip?dl=0
Download this two zip files first. They will wipe your entire phone including system and kernel as their names.
First flash the kernel clean then flash megawipe via a custom recovery.
Then without rebooting (wont boot because there is no system) hold power home and vol down and get to odin mode. Flash your 4.3 to the phone and see if that worked... if not, dial *#06# and check your imei number.
Hello.
I've got really strange issue, so i'm currently using s5 port rom.
It's is really sluggish so i wanted to move to some aosp based rom. The problem is whenever i flash a new rom my modem/ baseband become unknown and i can't see my efs partition. Restoring proper backups from many tools don't help. I also tried to flash modems but no succed (normal modems and zuluman modded on by twrp and touch cwm (not philz one)). It stills stays as unknown. Once when i formatted whole efs partition it gave me normal modem version but as soon i restored efs, modem became unknown. When i go back to s5 port rom everything is working as should (is it because aroma installer?).
Is it some kind of bug or i bricked my phone in weird way?
Thanks in advance
When flashing roms you must flash back to stock each time to make sure the device is working as it should. It ensures that any problems are related to whatever you're doing.
I have had circumstances where I have flashed a stock firmware, let the phone boot, switched off, flashed a custom rom, booted the phone, run maps and location was miles away with no way to change it.
Flashed back to stock twice with a factory reset in between and let the phone boot, location worked fine again.
The point I'm trying to make is that bugs can be inherent. Just because you flash another rom it doesn't mean everything is fixed that was previously broken. Only stock roms can do that. Something I've noticed with flashing stock firmware is that on the first flash it seems to only replace what is different from stock. On the second flash it replaces EVERYTHING. I don't know if this is actual or just my imagination but it seems the case for my I9300.
Once you have a stock working device make a backup of your modem and efs. Flash whatever you need and if you have issues then try restoration of the backup you made..
You can never make enough backups!.
Beamed in by telepathy.