After ROM flash with TWRP imeisv changed from 01 to 88 - Galaxy S 4 Q&A, Help & Troubleshooting

First of all, i want to ask if this is a major problem. My device seems to work with no problems, for now.
Secondly, is there a way to revert back this change?
Thanks.

Flash a stock ROM to see if the imei returns to the original.

I tried many times to restore from backup without success. Then i tried to flash the stock rom (i wipe before and after) without success again. Then i gave up and tried restore my backup again.....and then success!!! I don't understand why...
Thanks for your help.
Also i couldn't find the latest "normal stock" rom LUX, i only find the Le fleur. i think the differences are visual only.

Related

[Q] Wifi broken, can't seem to fix it

Hiya,
Using the international i9505 LTE, I tried flashing faux's kernel today, and everything appeared to be working. I also then flashed the xposed framework/some modules. Afterwards, I realised my wifi wasn't working anymore, and disabling the xposed framework didn't help. I also tried flashing the ausdim kernel which didn't work, as well as flashing my modem file, and the apparent wifi fix files multiple times, none of which solved the problem.
I have a nandroid backup, but would rather not restore it atm as it was made a while ago and I don't want to restore all the apps and stuff, so does anyone have any idea how to go about solving this problem?
nwsk said:
Hiya,
Using the international i9505 LTE, I tried flashing faux's kernel today, and everything appeared to be working. I also then flashed the xposed framework/some modules. Afterwards, I realised my wifi wasn't working anymore, and disabling the xposed framework didn't help. I also tried flashing the ausdim kernel which didn't work, as well as flashing my modem file, and the apparent wifi fix files multiple times, none of which solved the problem.
I have a nandroid backup, but would rather not restore it atm as it was made a while ago and I don't want to restore all the apps and stuff, so does anyone have any idea how to go about solving this problem?
Click to expand...
Click to collapse
Basically yesterday I had the same problem, flash after flash didn't help. Can tell you exactly, what I did:
Found factory version of my firmware in my region (SEB Baltics for me, MGA). Then I reinstalled TWRP recovery through ODIN, wiped everything I could, after that flashed stock firmware 2 times consecutively (no reboot in odin, reboot manually after first flash and flash again).
After that everything went fine, and Wi-Fi started working again. MH1 custom ROM right now, going ok.
Googling seems to suggest having to reflash stuff multiple times (I've seen someone say they flashed their stock rom 11 times wtf), and there doesn't seem to be any set procedure that gets the flash to work... Did you also flash multiple times before this last run worked? Perhaps you just got lucky and it worked the last time? (I assume no one tries to bork their wifi and test if their last routine works again for them).
I'm asking mainly because I don't want to go through the hassle of reflashing the entire rom again; would it be correct to say that wifi is just contained in the modem/radio file, and I should try spam flashing that?
No. WiFi drivers are in the kernel, not the modem. If you were going to flash anything, you'd flash a kernel/rom.
nwsk said:
Hiya,
Using the international i9505 LTE, I tried flashing faux's kernel today, and everything appeared to be working. I also then flashed the xposed framework/some modules. Afterwards, I realised my wifi wasn't working anymore, and disabling the xposed framework didn't help. I also tried flashing the ausdim kernel which didn't work, as well as flashing my modem file, and the apparent wifi fix files multiple times, none of which solved the problem.
I have a nandroid backup, but would rather not restore it atm as it was made a while ago and I don't want to restore all the apps and stuff, so does anyone have any idea how to go about solving this problem?
Click to expand...
Click to collapse
I suggest you use titanium backup to bakup your apps, it's not a tough job as you thought. that might be the easiest way, although some data can't be backup.
nwsk said:
Googling seems to suggest having to reflash stuff multiple times (I've seen someone say they flashed their stock rom 11 times wtf), and there doesn't seem to be any set procedure that gets the flash to work... Did you also flash multiple times before this last run worked? Perhaps you just got lucky and it worked the last time? (I assume no one tries to bork their wifi and test if their last routine works again for them).
I'm asking mainly because I don't want to go through the hassle of reflashing the entire rom again; would it be correct to say that wifi is just contained in the modem/radio file, and I should try spam flashing that?
Click to expand...
Click to collapse
No, I did flash it 2 times straight away. Flashing correct modem didnt help me, dunno why.
Gh0stR1pp3r said:
No, I did flash it 2 times straight away. Flashing correct modem didnt help me, dunno why.
Click to expand...
Click to collapse
read this....
http://forum.xda-developers.com/showthread.php?p=45219995#post45219995
looks bit similar
bofff said:
read this....
http://forum.xda-developers.com/showthread.php?p=45219995#post45219995
looks bit similar
Click to expand...
Click to collapse
Welp, bluetooth had no problems whatsoever. It was only the wifi, which didn't want to turn on. Now everything is ok.
Well, finally got around to reflashing stock as Gh0stR1pp3r suggested, which worked. Thanks
Nandroid, kernel flashing, and modem flashing all didn't work. No clue why. I flashed the ausdim kernel again and it worked this time around, so it's just weird I guess? :S
And unfortunately I seem to have messed up the titanium backup somehow, I can't seem to find any of the stuff I thought I backed up Oh well

[Q] No IMEI/Signal on Custom Rom?

I flashed a custom rom in this case AOSB Rom 1.2.8, when i flash it, my IMEI/Baseband says Unknown and i got no signal, im coming from a stock NEE rom, what do i do..??
bump
failbed said:
bump
Click to expand...
Click to collapse
Try THIS -- It'll fix the corupt EFS partition which has caused no IMEI/Baseband EDIT It might also fix your WIFI issue. However, it is possible it might not work -- 99% of the time it does, but there's always the chance it won't.
Also note = NEE ROM's seem to have some issues flashing, losing sound, phone get's FC's etc. So be careful flashing especially if you upgrade to KK
radicalisto said:
Try THIS -- It'll fix the corupt EFS partition which has caused no IMEI/Baseband EDIT It might also fix your WIFI issue. However, it is possible it might not work -- 99% of the time it does, but there's always the chance it won't.
Also note = NEE ROM's seem to have some issues flashing, losing sound, phone get's FC's etc. So be careful flashing especially if you upgrade to KK
Click to expand...
Click to collapse
I wiped cache/dalvik and flashed the stock rom again and tried it with custom rom aswell, and flashed the file you sent me after, it still dosen't work.
Trying to download a stock 4.4.2 (Not NEE) to see if it works.
Problem Fixed!! : http://forum.xda-developers.com/showthread.php?t=1678429

[Q] No network service GT-S7710 after installing CM10.1, 10.2 or 11

Hi peoples!
I’ve recently installed Cyanogenmod on my Samsung galaxy Xcover 2 (GT-S7710). But when I was done installing my phone couldn’t get any data (H/2G/3G) or call and receive calls. Could someone tell me what I did wrong or forgot whilst or after I installed Cyanogenmod? I would like to know because I’ve read other threads where people with a GT-S7710 do have a working network service on their phone with CM. And I also would like to know the solution to this problem because I can’t take a beating .
I apologize for the length of this first post . I just want to be totally complete about what I’ve done and tried so far to get CM to work with network service. I posted all this information to inform you all and so you could stripe a lot of questions off your list for finding the solution. Also I think this thread may be very useful for other Samsung Android users as well.
Kind regards,
Rick Willems
The problem
So the problem is that when I’ve installed CM10.1 or 10.2 or 11 to my GT-S7710, I don’t have any network service anymore. I tried to install CM using the following method: http://blog.arinium.fi/2014/07/howto-fix-samsung-xcover-2-issues-old-android-low-memory-slow-ui/. I installed CWM 6.0.4.6, wiped cache and installed CM10.2. After this it got stuck in a bootloop. Using the advice of this page: http://forum.xda-developers.com/showthread.php?t=2084905 which was to also wipe data/factory reset and wipe dalvik using CWM it worked!! YES!! But **** no service.
Used Files to install
Links I used to download CWM, CM and Gapps come from these pages:
http://forum.xda-developers.com/showthread.php?t=2384015&highlight=no+network, http://forum.xda-developers.com/showthread.php?p=43294839#post43294839,
CWM: http://www.adriadata.net/xda/skomer/
CM: http://www.adriadata.net/xda/skomer/
Gapps: https://itvends.com/gapps/
What I’ve done and tried
I tried to get network service back when I installed CM10.1 and CM11. In both cases I did a full wipe of data/factory reset, cache and dalvik then installed the latest stock rom/firmware 4.1.2 and do the instructions over again form the chosen method. I did notice that my phone does have network service when I have installed the stock rom/firmware downloaded from this link: http://www.mrcrab.net/down-firmware/14362/Samsung-Galaxy-Xcover-2-GT--S7710.html, My device also has got service when CWM 6.0.4.6. is flashed over the stock rom/firmware. Just not when I installed CM. CM10.1 was running more smoothly than CM10.2 and CM11 was running a little less smooth than CM10.2.
Attempt to solve the problem
I’ve brainstormed the following pages to get to the point of giving up .
http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2
http://forum.xda-developers.com/showthread.php?t=1205439
http://forum.xda-developers.com/showthread.php?t=2448246&page=2
http://forum.xda-developers.com/showthread.php?t=1304258
http://android.stackexchange.com/questions/39076/sim-card-failed
http://forum.cyanogenmod.org/topic/63816-network-problem-with-cyanogenmod-101-1218/
http://forum.cyanogenmod.org/topic/85051-no-service-cant-calltextnetwork-after-flashing-cm11-nightly-on-i9305/
The most pages are threads for other devices, but I thought I just read it anyway, maybe I could get some useful information out of it. Some pages talk about CDMA/RUIM that you can find under network setting in settings, but I’ve not been able to find it on my GT-S7710. Other data found in these pages are also not corresponding with my device.
What I did notice and learned was that information in the EFS folder like Imei, Baseband etc. are used to find and recognize the simcard and thus enable data usage and be able to call and receive calls. So I thought why not backup a copy the EFS folder and place it in CM’s EFS folder after install, so I did. I installed stock firmware where my network service works following the same steps I took that I described earlier, backup the EFS folder to sdcard1, install CWM and CM10.1 and tried to copy the backed-up EFS folder to CM root. But no way would it replace the CM EFS folder, CM simply blocks the copied EFS folder from stock rom/firmware.
I am just out of ideas now and am requesting your aid. Please help me .
Got the same problem here,unfortunately no fix yet
Try this:
kadooosh said:
For those trying to install this or another rom and having the no signal(no smallband) problem. This worked for me on 2 xcovers.
Install cmw: http://theunlockr.com/2014/02/27/install-clockworkmod-recovery-samsung-galaxy-xcover-2-gt-s7710/
Root it: http://theunlockr.com/2014/02/27/root-samsung-galaxy-xcover-2-gt-s7710/
Now normally you can install the custom rom now(vanir). If you do you probably get no signal.
Start odin and flash this file : S7710XXAMB6_S7710OXEAMB3-20130713.tar.md5
I found it on this site: http://www.ulozto.cz/xHADj5PD/samsung-7z
If its dead you can pm me and I can send it.
After I flashed this the phone would just go in a bootloop.
Don't be afraid this is normal.
Now install the vanir rom in the cmw recover mode.
After this it should work fine.
Add a microsd card with 2 partitions and install mount2sd and you have a fully working phone with(almost) unlimited space.
I'm using if for an year now and it works great.
Better then most €500 phones which break after 1 fall .
Click to expand...
Click to collapse
With skomer it is definitely a baseband problem. Changing baseband solves the network signal.
ViktorDelta said:
With skomer it is definitely a baseband problem. Changing baseband solves the network signal.
Click to expand...
Click to collapse
because i have the same problem, i installed cm10.2 and everything were fine for a week and then no signal, i tried to install all the available firmwares out there, the closest i got was to find network and 3g i made a successfull call then i shut it off. At the next boot nothing again. My baseband is xxxx. What do i have to do to change baseband? My IMEI is correct.
does anyone have a /modemfs and /efs folder available to try or/and a modem file to flash?
Odin flash
Go to this page https://boycracked.com/2016/09/11/official-samsung-galaxy-xcover-2-gt-s7710-stock-rom/ and download stock rom labeled "oxeamb3". Put your phone on download mode and connect to odin. Flash this rom with it.
After that, flash your clockworkmod and custom rom. Vanir or CM.
If you still lose signal, try with AND2 stock rom. It's been a while since I did this so I don't remember exactly, but I think AND2 had problems with signal and AMB3 didn't.

SM-G900F restarts constantly but only when left idle

I have an unlocked Galaxy S5 from "Three" Ireland (3IE) that restarts many times during the day but only when I leave it idle. Either on its own or while charging.
When its not charging at home, the restarts drain the battery very quickly.
Unrooted, latest stock ROM for this carrier (Android 6.0.1 G900FXXS1CQD1_G900F3IE1CPJ3_G900FXXS1CQA3)
I searched the forum and tried the following in this order:
1. Replace the battery
2. reset factory settings (and reinstall everything)
3. Flash stock ROM using ODIN v3.12.3 (same ROM version)
Nothing helped. :crying:
I didn't reset factory settings (again) after flashing stock ROM since I don't think that will make a difference. Any ideas?
kdizzy07 said:
I have an unlocked Galaxy S5 from "Three" Ireland (3IE) that restarts many times during the day but only when I leave it idle. Either on its own or while charging.
When its not charging at home, the restarts drain the battery very quickly.
Unrooted, latest stock ROM for this carrier (Android 6.0.1 G900FXXS1CQD1_G900F3IE1CPJ3_G900FXXS1CQA3)
I searched the forum and tried the following in this order:
1. Replace the battery
2. reset factory settings (and reinstall everything)
3. Flash stock ROM using ODIN v3.12.3 (same ROM version)
Nothing helped. :crying:
I didn't reset factory settings (again) after flashing stock ROM since I don't think that will make a difference. Any ideas?
Click to expand...
Click to collapse
Did you have any custom rom installed before? Try flashing latest bootloader for the phone and checking, if all else fails try a custom rom and see if the problem persists.
Mufrad said:
Did you have any custom rom installed before? Try flashing latest bootloader for the phone and checking, if all else fails try a custom rom and see if the problem persists.
Click to expand...
Click to collapse
No custom ROM while the phone was in my possession. It could have been before I got it (I'm not the original owner) but when I did get it I was on stock and unrooted (at least according to "Root Checker").
Didn't I get the latest bootloader when I flashed the latest stock ROM? I remember seeing the files "boot.img" and "modem.bin" in ODIN.
Also if you have any suggestions for a good custom ROM I'm all ears :angel: (I like bug-free*, speed and battery life. In that order of importance)
* - I know there's no such thing as "bug-free" but you get the idea
kdizzy07 said:
No custom ROM while the phone was in my possession. It could have been before I got it (I'm not the original owner) but when I did get it I was on stock and unrooted (at least according to "Root Checker").
Didn't I get the latest bootloader when I flashed the latest stock ROM? I remember seeing the files "boot.img" and "modem.bin" in ODIN.
Also if you have any suggestions for a good custom ROM I'm all ears :angel: (I like bug-free*, speed and battery life. In that order of importance)
* - I know there's no such thing as "bug-free" but you get the idea
Click to expand...
Click to collapse
Sometimes you have to flash bootloader again separately, specially if it was changed to an later version than the one you are flashing through odin, and I would suggest a custom touchwiz rom which is close to stock but with bloat removed and some speed tweaks maybe for the most bug free experience. But also maybe give stock android roms a try, most bugs should be ironed out.
Mufrad said:
if all else fails try a custom rom and see if the problem persists.
Click to expand...
Click to collapse
OK, last night I tried a couple of things:
1. I flashed Slim6 6.0.1.build.2.1 and twrp-3.2.3-0-klte (with wiping) - didn't help.
2. I took the sim card & sd card out - didn't help.
3. I ran logcat from ADB using USB debugging to see if I could get the error before the restart - While the phone was connected and logcat was running, the phone never restarted. Even when the screen timed out and turned off. (I guess the phone doesn't count this as "idle")
oh, and thanks for all the assistance so far
The fact that it happens on custom ROM leads me to think hardware. The fact that it doesn't happen if I keep the phone "busy" leads me to think software. What should I try next?

Screen problem

Hi everyone,
To flash the last rom (nightly ) of LineageOS ( in Oreo,from the 2 february), i had to put the firmware 5.1.7. After flash this firmware i was able to flash the ROM but it makes my phone extremely slow and with screen issues (i can still use the tactile but the screen doesnt follow).
I restored but the problem stills then i put le last stable ROM from Oneplus on android pie (9.0.3). It is a bit better (still really slow) and after a moment i get now like a white noise (same as on TV but with color moreover) by wink ( was more and more often on Google Maps), I had to reboot cause i couldnt use more my phone.
Thanks you in advance !
Ps : I've got TWRP from siankatabg and i'm not rooted , if you want me to send log tell me how pls.
Up :good:
When you were flashing did you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Flash codework's TWRP for Pie. After that reboot into recovery, wipe everything down and use clean flash instructions for your OTA. It should be able to fix any issue you were having. If not let me know.
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Raidenne said:
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Click to expand...
Click to collapse
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Ebeninyo said:
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Click to expand...
Click to collapse
My issues seem gone since few weeks with the last OTA (it very rarely happens now). I don't know what caused that even if i use my backup.
Thanks for your support !

Categories

Resources