Never flash roms that's not made for your model
Flashing them may work but it's highly you end up with a brick if the phone started and boots you end up
Mostly loosing original imei forever even if you fixed it with boxes you get different imei
Wifi problems or other apps crashing because of the wrong drivers that's inside that ROM
if flashing those roms works there will be no different models in first place
Related
I recently bought a for parts Captivate off of Ebay, Description saying the unit would only power on and that the touchscreen wasn't working.
I looked at the photos and determined that it must be a hardware malfunction, I have some spare parts to try and see what I could do.
(since my previous cappy fried after a botched job re-applying the unbrickable mod that had worked once before)
I receive the phone, in near new condition, no battery and dented back cover, and I thought "okay, no problem" and got to work trying see what was wrong exactly
I was unable to determine what android revision since I would reboot after lockscreen, so I flashed it with various roms, including AOCP 2.2, Slim Bean and at&t GB's that had been rooted with odin and cwm for slim bean and aocp and cm10
So the following symptoms happen based on which android revision I use
2.1 stock
- phone reboots seconds after the phone has booted to the touchwiz lockscreen, touch screen has no response, I can't say it's 2.1 definitely but could be since every other rom works fine except any signal or data other than wifi
2.2, 2.3.X and all the way to 4.1.1
- SIM card detection - does not warn of missing sim or bothers to detect once inserted
- IMEI is unknown other than the one on the sticker, which is in one piece
- Baseband is unknown even if I flash a modem
I've replaced the sd card/sim card daughter board that also connects the loud speaker to the mainboard. Still nothing. at least the sd card and speaker work.
So... any ideas or should I use this phone like a Galaxy player minus the front camera?
Gizoid1337 said:
I recently bought a for parts Captivate off of Ebay, Description saying the unit would only power on and that the touchscreen wasn't working.
I looked at the photos and determined that it must be a hardware malfunction, I have some spare parts to try and see what I could do.
(since my previous cappy fried after a botched job re-applying the unbrickable mod that had worked once before)
I receive the phone, in near new condition, no battery and dented back cover, and I thought "okay, no problem" and got to work trying see what was wrong exactly
I was unable to determine what android revision since I would reboot after lockscreen, so I flashed it with various roms, including AOCP 2.2, Slim Bean and at&t GB's that had been rooted with odin and cwm for slim bean and aocp and cm10
So the following symptoms happen based on which android revision I use
2.1 stock
- phone reboots seconds after the phone has booted to the touchwiz lockscreen, touch screen has no response, I can't say it's 2.1 definitely but could be since every other rom works fine except any signal or data other than wifi
2.2, 2.3.X and all the way to 4.1.1
- SIM card detection - does not warn of missing sim or bothers to detect once inserted
- IMEI is unknown other than the one on the sticker, which is in one piece
- Baseband is unknown even if I flash a modem
I've replaced the sd card/sim card daughter board that also connects the loud speaker to the mainboard. Still nothing. at least the sd card and speaker work.
So... any ideas or should I use this phone like a Galaxy player minus the front camera?
Click to expand...
Click to collapse
There could be a lot of things wrong with it since you are at least the second owner and don't know the full extent of possible damage.
But lets assume all things are functional but calls and data. I do want to clarify though, other than the 2.1(?) flash your screen responds as normal? If so try getting a one-click version of 2.2 and flashing it back to stock. Then just for good measure download Kies, which is Samsungs official firmware update client. It should take you to 2.3(Gingerbread). Now is the time to go into your phone settings and check your IMEI. Make sure it matches what's under the battery. Hopefully reverting back to stock with official software will restore your IMEI.
I've personally never had my IMEI get screwed up during a flash but after reading countless posts, and responses regarding the issue it seems that a lot of time if you are missing your IMEI the baseband version will show unknown as well. As for not showing a missing SIM warning I am at a loss but those are the best steps I can tell you to take in an effort to recover your IMEI.
Also if the above steps get you back in business make sure you do a backup of your /efs folder before moving ahead with any other flashing of ROMs to avoid a possible repeat of the same issues.
I'll give kies a try after downgrading, thanks
Kies says connecting... and then after maybe 5 - 10 minutes later says could not gather info on GT-i9000.
Gizoid1337 said:
Kies says connecting... and then after maybe 5 - 10 minutes later says could not gather info on GT-i9000.
Click to expand...
Click to collapse
Hmm well I'm going to say you have i9000 bootloaders installed on your cappy. So Kies is getting confused and can't find the right software for your phone...
You could try doing a Gingerbread one-click with bootloaders for the cappy but you run a serious risk of permanently bricking your phone when you start messing with bootloaders. Of course as it stands you don't have more than an mp3/video player.
My suggestion would be to go ahead and grab one of the stock one-clicks with I897 bootloaders. As long as you don't pull the plug during the 1-2 seconds it's flashing those, you'll be fine. Once you've flashed, if you still can't get it, you can try the /efs repair that's in the development section.
It sounds to me like the SIM card slot could be borked, though. If that's the case, I believe connexion2005 (Josh at mobiletechvideos) offers a service to repair that for a nominal fee. If getting it working as a phone isn't a big deal, then you can just ignore the SIM slot repair and get one of the Captivate Touch roms and make it a media player.
Hello, back and so far flashing with uckk4 with bootloaders, and uckf1 also with bootloaders, so far same issue, no signal,imei, or baseband
Gizoid1337 said:
Hello, back and so far flashing with uckk4 with bootloaders, and uckf1 also with bootloaders, so far same issue, no signal,imei, or baseband
Click to expand...
Click to collapse
I'm gonna say you're definitely having some hardware issues at this point. Sounds like you have a media player.
Sent from my SGH-I897 using xda app-developers app
I also found that I have no gps when running on UCKB2.
Anybody know where a custom 2.1 rom could be found? having a bit of trouble finding 2.1 custom rom that's odin flashable
Because now /efs is now NOT mountable and empty, good thing I made a efs pro backup, But nv_data.bin is mostly blank in hex workshop. Is that how it supposed to be?
EDIT - nvm about 2.1 roms, anything to fix umountable /efs would be nice, also nice would be if I stopped messing with my phones
Gizoid1337 said:
Hello, back and so far flashing with uckk4 with bootloaders, and uckf1 also with bootloaders, so far same issue, no signal,imei, or baseband
Click to expand...
Click to collapse
i had the same problem the other day what worked for me was leaving the sim card out while flashing the modem, reboot, then shut down and insert sim card.
Hey everyone i have had massive problems with the IMEI on my i9000 finally managed to flash back to stock ROM but im still getting no signal. The IMEI is fine and i have a backup of the efs folder saved. What files do i need in this folder as i will delete all of the contents then start again.
Thanks
If your still getting no signal but are not getting "No Service" then either the modem you flashed in the stock ROM is utter pants for specific handset so trying flashing a different modem or a different ROM altogether :/
But if a different modem or ROM doesn't fix it then you have a antenna problem... sorry bud
Hey mate,
Cheers for the reply. I will try a new ROM can you recommend any small ROM's that will work on my device? I don't know a great deal abour ROM's and flashing in general tbh.
I need to finish my guides badly! Then I'd just be able to point you towards them :/
But since their not... cause I've been lazy, please head over to SamMobile/ and create an account if you haven't already done and download the correct firmware for you i9000.
Getting the right firmware is difficult, it's even more difficult since I'm guessing you don't know the PDA build from what the phone was running originally... for example by phone when I got it was running I9000BVJV7 which is actually Android 2.3.3 for the UK and sim locked to Orange.
When you take into account that the Android version, the country and the carrier have an effect on the specific firmwares for two (on the face) identical phones you can begin to see how many millions of different firmwares there are out there just for one phone...
So just try your best and read all the helpful info on SamMobile. If you get really really stuck or if something nasty happens to the phone while flashing either come back to this thread or PM me and I will talk you through a recovery kit that will hopefully restore the phone to a stock ROM (but not official stock ROM).
Since you're new to flashing please be reminded flashing can completely kill a phone to the point of no return, having said that I must have flashed a million times in both ClockworkMod and Odin but that doesn't mean death can't happen at any time.
Thanks mate i really am grateful for the help. I will give that a go and see what i can find.
Downloaded all of the vodaphone rom's and all of the orange roms. The device was used on vodaphone and im still getting the same error :/ any more ideas?
I have a factory unlocked P1000 that recently started having some issues. When I first got it two years ago, I had flashed it with the following:
PDA1000DXJK2
PHONE1000DXJJ2
CSC1000OLBJJ2
During all that time, everything was working fine everywhere I had been (Asia and North America), with at least three different SIM cards and carriers.
About three weeks back, I suddenly lost voice/data. At first, I thought it was a SIM/carrier issue, but some swapping with a friend revealed that it was my tab that was the problem. Searching here and elsewhere, all I could come up with was that my IMEI was showing as the generic 0049990106400 and not the one listed on the back of my tab. I had been aware of them not matching, but it had never caused problems in the past. I was able to confirm, however, that the radio/modem was still working. I could place emergency calls, I could see that the networks were there, I just could not connect to any of them.
In my attempts to restore the original IMEI, following a guide here, I managed to lose my broadband entirely. I have been researching and trying to get it back ever since, so far to no avail. Unfortunately, I haven't been able to find a copy of the P1000DXJK2/DXJJ2 firmware I used the first time. However, I have tried multiple stock ROMS, different tutorials, and most recently, flashing with Overcome 4.1. The result is always the same: everything works except for the phone. Phone, broadband, and IMEI list as unknown.
Currently:
PDA: P1000XXJQ1
PHONE: Unknown
CSC: P1000OXAJQ1
Model number: GT-P1000
Firmware version: 2.3.3
Baseband version: Unknown
Kernal version: 2.6.35.7 [email protected] #2
So, here I am desperately appealing for any help anyone might be able to provide. My tab has been my only phone for years and often my only internet access, so I am feeling pretty lost without it. I am fairly tech savvy and I follow instructions very well, but I have never really messed around much with Android, so I am hoping the experts here are going to be able to come up with something.
So, you said you most recently use overcome 4.1.
When you first use Odin to flash GB-stock-safe-v5, before you put overcome kernel, what is the IMEI?
No point to proceed to Overcome ROM if GB-stock-safe-v5 didn't bring back the IMEI.
Yes, that is what I assumed, but I gave it a try anyway. If nothing else, it gave me better recovery mode tools.
As I said above, nothing has worked so far. My IMEI was unknown before flashing with GB Stock, as it is now. However, at this point, I would be happy just to get a working modem again, even if the IMEI remains messed up... One thing at a time.
the fact that the IMEI suddenly is gone, and on further tweaking the radio/baseband is gone, I think your internal storage is failing.
first it hits the EFS area, then the baseband area.
That is my suspicion.
You could probably proceed to flash latest CM/AOKP or whatever, which repartition your internal storage.
You should get your baseband, because the /radio/modem.bin in those MTD partitioned ROM sits on a different part of the storage.
But since you never have a backup of your EFS, those ROM will not give you your IMEI either.
Only flashing a stock ROM will give you the right EFS (assuming the area it writes into is writable)
I also wonder if there a person expert enough to rewrite the pit file, so that your EFS and baseband is shifted from its original position, and use that with the GB stock safe v5
This is an interesting idea. To clarify, though, my IMEI did not suddenly go, to my knowledge. For at least the last year and a half, the IMEI listed did not match the one printed on the back. Everything worked fine, so I never gave it much thought. What I do not know is if it changed again, or if it has been the generic one I listed above all along.
Could it be that something is simply wrong with the EFS, preventing the modem.bin from flashing correctly? One of the IMEI restoration tutorials I attempted early on involved messing with the EFS. I believe this was the same night the modem stopped working, though I did not notice a direct cause-effect relationship. There were other (failed) attempts between that and broadband coming up "unknown." I will admit I was a little hasty in those first few days. I was traveling, crunched for time, and panicked that I would have no phone.
Earlier this week I had an unsuccessful install of the alpha CyanogenMod 13.0 rom - didn't want to be encrypted so I substituted the latest HC M kernel. wasn't the first time I couldn't get a new rom to boot so didn't initially think much about it but following that flash I couldn't get any new rom to install and successfully complete setup. Each try would get stuck at step right after wifi was set up. I eventually determined there was an issue trying to connect with Google servers. Tried a multitude of fixes but nothing worked. Ultimately I found that my IMEI and IMEI ID had been hosed and both were now 0's rather than the original IMEI number. I unfortunately did not have the efs partition backed up (at least that I could find). I have tried every method, tool, etc. I have been able to locate to repair or to re-write the IMEI to the phone but so far to no avail.
I restored the original stock software (going back to the original lmy47e on the phone when I purchased it) as well as subsequent releases with a hopeit could somehow restore the IMEI but nothing has worked. I have managed to getto where I can make and receive calls and SMS/MMS but once I'm out of wifi range, no internet access. I even have trid a new SIM from Verizon but tha made no difference. Still a bit confused as to where the IMEI value is stored (and how it could be corrupted) but at this point it looks like new phone time (already ordered a new N6 from Amazon).
Hoping maybe someone might have some suggestion that might help me out. Seems like the N6 is new enough and different enough that the usual fixes don't seem to work. I know discussions around flashing IMEI's isn't really legit on xda but I'm just trying to get back my original IMEI rather than trying to mask a problem phone.
The only accepted way to get it back is to restore a back up. Having the IMEI corrupted happens when roms flash the wrong partitions. Samsung is known for storing the IMEI in a partition that is easily corrupted or erased when flashed. Not normally a nexus issue and I'm not sure which partition the IMEI is stored under.
It is not unheard of that cm roms have some issues like this. It wasn't to long ago that they bricked some nexus.
I got a Note 9 from an Ebay seller yesterday. It was rooted when I got it and I installed TWRP and flashed a new ROM after (didnt test out the carrier initially). After the flash, I put in multiple sims but service does not work (the cell radio is working, even connects to the towers). I decided to flash stock firmware through ODIN but it does not work, I get some secure boot error. Also, the fast-boot mode is in Korean so I believe this is a model from Korea. What could be the issue here and is there anyway to fix it?
Note: The seller claims that he tests all phones before shipping, and said that the cell service was fine for him (in the same country as me). I didnt test my sim prior to flashing the ROM so I cant prove it.
Sounds like your EFS partition is corrupted.
There are a few ways to fix it but I cannot remember them all.
I know that I fixed by downloading multiple versions of the stock rom and flashed them multiple times till it fixed it self.
But do some research on how to fix efs and imei.
Dr.katen or whatever his name is has made some software to back it up for future corruption so once you get it working again I suggest you back it up.