Related
Guys,
I just updated with the CM10 nightly and I am getting a prompt on bootup that my IMEI is not valid. The IMEI is not blank, and isnt something like 0123456789. Is this a big issue? My calling and texting are working fine, as is my mobile data.
Thanks
The same happens to me. I did an efs backup with root manager but is there any risk? Could someone explain please?
I backed up with cwm before loading cm10 0823. And did an imei restore from Nitrality and it says successful. However I still get an invalid imei on bootup
Sent from my GT-I9000 using xda premium
Updated to cm10 0824. Same issue. Should I do a full cwm restore?
Sent from my GT-I9000 using xda premium
Hey guys common issue if you want it back follow my guide http://forum.xda-developers.com/showthread.php?t=1845104 you might want to titanium backup your apps first then backup your sd
Sent from my GT-I9000 using xda premium
Restored cwm backup from before the issue started. No long have invalid imei. Update to latest cm 10 and invalid imei prompt on startup. However the imei screen under About has an imei number in it still.
Sent from my GT-I9000 using xda premium
Correct imei though as in the same as the one under the battery?
Sent from my GT-I9000 using xda premium
Nope. Its a different one.
Sent from my GT-I9000 using xda premium
webchaos said:
Nope. Its a different one.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
OK so its invalid try the link I previously posted if it works or not get back to me
Sent from my GT-I9000 using xda premium
After going back to stock GB, darky resurrection ROM, cm9 and finally cm10. IMEI is back and looking OK. Thanks.
Sent from my GT-I9000 using xda premium
That's good
Sent from my GT-I9000 using xda premium
Felt a bit of nostalgia going back through the last 2 years of ROMs lol. Thanks again.
Sent from my GT-I9000 using xda premium
webchaos said:
Felt a bit of nostalgia going back through the last 2 years of ROMs lol. Thanks again.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Well, in my case, my father's phone lost all efs backups, and nv_data.bin is corrupted (regenerated new one with default generic IMEI).
So, there is nothing to restore from. Reflashing to stock 2.3.6 JW5 firmware didn't help. So you think that I will have to reflash to 2.2.1? How so? I don't understand how older firmware may help restoring correct IMEI...and I don't own JTAG, z3w or SPT boxes...
And for morrons - no, there is no .nv_data.bin, no nv_data.bin.bak, or similiar...only new nv_data.bin(md5) with default, generic IMEI.
Is there any way to restore it? if somebody start to complain that I am thief, I can prove by photos of original phone box, and buying papers I have (my father gave them to me for this purpose).
And no, I don't have to steal anything, I own SGS3, SGS2, SGS, SGT10.1....so stealing another SGS is not an option for me
I just want to restore that phone to it's stock state (and then reflash again with CM10).
Anyone?
Virnik0 said:
I just want to restore that phone to it's stock state (and then reflash again with CM10). Anyone?
Click to expand...
Click to collapse
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
just flash a JVU and a PIT , should get you back your IMEI or look at My android solutions for details
xsenman said:
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
just flash a JVU and a PIT , should get you back your IMEI or look at My android solutions for details
Click to expand...
Click to collapse
Why are you so confident, that JVU will regenerate /efs?
as said before, my father was so genius, that he has wiped /efs partition out. I have restored some data, but without proper IMEI, so now I have generic one. I still do have old JVU package somewhere on my NAS, but I do not understand, how old firmware may help, because I am without any /efs backup anywhere... is that firmware customized so it checks and regenerates /efs if its damaged? If so, why is this feature missing from latest full JW5 firmare? Please understand that I know what I am doing, but right now, I have empty hands...without JTAG, z3w or similiar low-level gadget, it is really hard to restore proper /efs on my own...
But thank you for links, I will take a look on them...
More Clues On Fixing IMEI Issue (solved for me)
In my case I upgraded directly from Froyo to CM10.1 and got then same dreaded 'default' invalid/corrupt IMEI=004999010640000
On inspection of the /efs files present it was clear they had been created by the system in response to not being present.
Following advice in this thread and elsewhere I downgraded back to Froyo (XXJPU) and like magic my correct IMEI re-appeared but as soon as I upgraded up to CM9 it changed back to the invalid default of 004999010640000 again.
To cut a long story short I downgraded back to Froyo (XXJPU) again, flashed a recent CWM recovery and booted into the recovery. I then used ADB to get a (root) shell prompt and discovered that the correct /efs data was being mounted from the device /dev/stl3 and at this point I was able to tar up the contents of /efs and safely make a backup. I then upgraded to CM10.1, restored the correct /efs backup and rebooted.
Happy with correct IMEI now
I am not sure what is going on but I am speculating that the big jump from Froyo to CM10.1 bypasses come critical intermediate ROM build where the correct IMEI data is copied from /dev/stl3. CM10.1 assumes this step has taken place and makes no attempt to get the original IMEI data.
... Robert
robertrath said:
In my case I upgraded directly from Froyo to CM10.1 and got then same dreaded 'default' invalid/corrupt IMEI=004999010640000
On inspection of the /efs files present it was clear they had been created by the system in response to not being present.
Following advice in this thread and elsewhere I downgraded back to Froyo (XXJPU) and like magic my correct IMEI re-appeared but as soon as I upgraded up to CM9 it changed back to the invalid default of 004999010640000 again.
To cut a long story short I downgraded back to Froyo (XXJPU) again, flashed a recent CWM recovery and booted into the recovery. I then used ADB to get a (root) shell prompt and discovered that the correct /efs data was being mounted from the device /dev/stl3 and at this point I was able to tar up the contents of /efs and safely make a backup. I then upgraded to CM10.1, restored the correct /efs backup and rebooted.
Happy with correct IMEI now
I am not sure what is going on but I am speculating that the big jump from Froyo to CM10.1 bypasses come critical intermediate ROM build where the correct IMEI data is copied from /dev/stl3. CM10.1 assumes this step has taken place and makes no attempt to get the original IMEI data.
... Robert
Click to expand...
Click to collapse
Exactly that. Same goes with going from Gingerbread to Jelly Bean.
That critical intermediate rom... Is CM9
In other words, to safely preserve your IMEI,
Froyo/GB ---> CM9 ----> CM10/10.1/JB
Sent from my GT-P7510 using Tapatalk HD
Hey there I was searching/googleing the instructions for unrooting the T-Mobile Galaxy Note (t879) but could only find the international versions.
Does anyone know the process or can point me to a video/tutorial to go back to a fully unrooted Note?
Also, how do I go about going back to the tmo recovery, removing the CWM recovery? Where can I find that? Do I do that before I unroot it or after?
Once I flash the unrooted stock rom (if there is any for Tmo) do i need to reset the flash counter and how would I do that if it is unrooted?
Sorry for all the questions, I hope someone can help me...
Thanks in advance!
Background: my mic started to produce garbled noise, it works fine on handsfree mode but not on the regular mode. if I can fix it I don't need to go back to stock or unroot it.
I tried a different ROM but that didn't work (CM10), i cleared the tmo talkvoice app cache and data but still the same result.
So i assume that the mic is broken and that I will have to send it in/RMA it...
Try this post here,
http://forum.xda-developers.com/showthread.php?p=32691120
Sent from my SGH-T879 using xda premium
joemm said:
Try this post here,
http://forum.xda-developers.com/showthread.php?p=32691120
Sent from my SGH-T879 using xda premium
Click to expand...
Click to collapse
Thank you joemm, that did it.
If the mic problem ever happens to anyone else then flashing to another ROM, such as ICS/JB wont fix it. You need to return to stock, preferably to a nandroid back up (from when it worked)
Then I rooted the stock phone again, put CWM recovery on it and went straight from there to JB (AoCP) and have not had any problems with the mic so far. its been running great so far!
Can I install stock recovery and then try to take a ota to update. Will I loose root and will I loose my rom? Will I be able to reinstall a rom or will I need to reroot?
you can try, you shouldn't loose root or anything but once you have unlocked and flashed stuff I doubt stock recovery will like your system enough to take the update. try this http://forum.xda-developers.com/showthread.php?p=53518227
HOW Change ...... ???
Sent from my SM-T217S using XDA Free mobile app
From my understanding, as long as /system is stock, you can install the stock recovery and then take the OTA. Afterwards, you'll need to re-root your phone. Make a backup of your current setup before you get started. Once you've taken the update and get rooted again, you can always restore your backup.
Sent from my HTC device
Magnum enforcer is correct.
Sent from my 831C using XDA Premium 4 mobile app
I will give it a try this weekend and let you know how it goes.
Edit does not work but thanks for helping me.
Must be the fact that I am s on. We need that s off before we can do anything as far as updating
This one is tricky. I flashed the stock rooted rom from mikmik, I then unrooted and flashed the stock recovery via fast boot. When applying the Ota, it fails because the build.prop is not stock. Comes back with an error like /system/build.prop unexpected.
dilaynie said:
This one is tricky. I flashed the stock rooted rom from mikmik, I then unrooted and flashed the stock recovery via fast boot. When applying the Ota, it fails because the build.prop is not stock. Comes back with an error like /system/build.prop unexpected.
Click to expand...
Click to collapse
I just tried it to and did the same exact thing except I had boot loops as we'll.
when I flashed back to the stock recovery to take the recent OTA, I had a reboot bootloop like every 2-3 minutes, I was ready to throw the phone against a wall, then it hit that I read recently someone else had the same issue, and mentioned a factory reset fixing the issue, yup after a factory reset, the reboot bootloop was gone, I just now rerooted and flashed a backup
sent from HTC M8 using tapatalk
scott_0 said:
when I flashed back to the stock recovery to take the recent OTA, I had a reboot bootloop like every 2-3 minutes, I was ready to throw the phone against a wall, then it hit that I read recently someone else had the same issue, and mentioned a factory reset fixing the issue, yup after a factory reset, the reboot bootloop was gone, I just now rerooted and flashed a backup
sent from HTC M8 using tapatalk
Click to expand...
Click to collapse
But after all that we're you able to update the radio and second did it fix the signal issues?
jdmohn12 said:
But after all that we're you able to update the radio and second did it fix the signal issues?
Click to expand...
Click to collapse
yes, I was able to take the latest OTA, and no, it did not help with my signal at all, my device didn't drop calls or anything, but it has a hard time latching onto lte at times before and after the OTA.......
sent from HTC M8 using tapatalk
Do we know how to get passed the build.prop error?
Sent from my 831C using XDA Free mobile app
this might be a really stupid question (and my first post no less), but does performing a factory reset take me back to stock, unrooted form?
currently i am rooted with S-on, TWRP and Chainfire SU.
i followed a youtube video to root and im basically clueless with regards to doing anything more.
thanks in advance.
Tbaggington said:
this might be a really stupid question (and my first post no less), but does performing a factory reset take me back to stock, unrooted form?
currently i am rooted with S-on, TWRP and Chainfire SU.
i followed a youtube video to root and im basically clueless with regards to doing anything more.
thanks in advance.
Click to expand...
Click to collapse
no, a factory reset will not unroot you, you need to restore a stock backup, then flash stock recovery in fastboot to unroot while s-on
sent from HTC M8 using tapatalk
scott_0 said:
no, a factory reset will not unroot you, you need to restore a stock backup, then flash stock recovery in fastboot to unroot while s-on
sent from HTC M8 using tapatalk
Click to expand...
Click to collapse
Thank you. I saved a stock backup (i think) while rooting so ill see what i can do tonight. fastboot is the white background screen that uses volume buttons to select, right?
Tbaggington said:
Thank you. I saved a stock backup (i think) while rooting so ill see what i can do tonight. fastboot is the white background screen that uses volume buttons to select, right?
Click to expand...
Click to collapse
yes sir, power off the phone completely, hold down power and volume down, select fastboot
sent from HTC M8 using tapatalk
Hey everyone.
I've spent the better of the last three hour scouring the inter webs, Google, and these forums trying to find the answers to my questions - but to no avail (I've found partial answers, but I am afraid a partial answer could lead to a total brick).
Here we go:
I bought one of the first Sprint HTC One M8's through Amazon. Here are the details:
Model: 831C
Android Version 4.4.2
Software Version 1.12.651.17
Unlocked but S-On (Using TWRP)
Naturally, right out of the box I rooted it. However, I did not save the original ROM.
* I want to restore the phone to its original state so I can accept the OTA update and hopefully address the god-awful cell signal.
I've found a lot of stock recoveries online, but none that match 1.12.651.17.
Do I need to find that specific recovery to flash to my phone? Will another one work (e.g. 1.54.654.13)?
I've never worried about saving my stock recovery in the past (been rooting since the HTC Evo days) but it looks like not doing so finally caught up with me.
Thanks in advance.
PS I did find something 1.12.651.17 related here, but how to flash this to my phone (or whether or not it will brick) is beyond me. I've downloaded all 6 files and am waiting to figure out how the heck to get them to my phone.
http://forum.xda-developers.com/showthread.php?t=2736048
So I have an LG G2 that I used AutoRec on and it flashed a different kernel not compatible with the display type. I flashed the stock ROM back thinking it would fix the problem but it did not. Does anyone know how to flash the right kernel for the display? I've been looking but it seems I'm going to have no luck since I just flashed back to stock and I need root and a custom recovery to do so. Any help would be appreciated, thanks.
Pictures of my problem below.
Sent from my SM-N900V using XDA Free mobile app
mexicanhobo said:
So I have an LG G2 that I used AutoRec on and it flashed a different kernel not compatible with the display type. I flashed the stock ROM back thinking it would fix the problem but it did not. Does anyone know how to flash the right kernel for the display? I've been looking but it seems I'm going to have no luck since I just flashed back to stock and I need root and a custom recovery to do so. Any help would be appreciated, thanks.
Pictures of my problem below.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
The OP has a link under the warning to get the JDI version. http://forum.xda-developers.com/showthread.php?t=2715496 Read ,read, read. There's also a tool in G2 Android Development that will detect if your pannel is LGD or JDI.
Sent from my XDABBEB VS98025A v2.0.0 using XDA free mobile app
I have looked through that whole thread and it seems you need to be able to use recovery and have root permission. Most of them claim to have only a few lines but they are still able to see their screen. Mine stays how it looks in the picture 100% of the time. I used the TOT method before to flash it back to stock but it seems that didn't do anything to fix it, that's why I'm asking on this forum. Since it's complete stock and I have no way of seeing what's going on on the display. For some reason it seems to boot up into download mode also without me doing anything but turning it on. If you have any experience with this issue could you inform me about it? Thanks, man.
Sent from my SM-N900V using XDA Free mobile app
mexicanhobo said:
I have looked through that whole thread and it seems you need to be able to use recovery and have root permission. Most of them claim to have only a few lines but they are still able to see their screen. Mine stays how it looks in the picture 100% of the time. I used the TOT method before to flash it back to stock but it seems that didn't do anything to fix it, that's why I'm asking on this forum. Since it's complete stock and I have no way of seeing what's going on on the display. For some reason it seems to boot up into download mode also without me doing anything but turning it on. If you have any experience with this issue could you inform me about it? Thanks, man.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
Can you get into recovery? Try grabbing the kernel here and flashing it.
http://forum.xda-developers.com/showpost.php?p=51974589&postcount=281
Otherwise if the screen is like this 100% of the time, I'd say it's farked, use the return to stock guide and take it back for a replacement.
Thank for replying, unfortunately that is the answer to my question. It is like that 100% of the time and I flashed stock back on to it thinking it would fix the problem. This leaves me with a messed up screen and a phone without any root or custom recovery. I will ask, is it possible to flash a kernel in stock somehow with adb or anything of the sort? I have already sent it in for a replacement so I don't think I will be able to send it in again.
Sent from my SM-N900V using XDA Free mobile app
I recently purchased a Samsung Note 4 (SM N910T) for from a guy on craigslist after saving up money to buy it, but it keeps turning off out of no where . the phone was having problems before I rooted it, after I rooted it, and after I odin'd the earliest version of kit kat of the phone.. The turning off occurs at any time, during boot, during flashing TWRP, during normal usage of phone, anytime. I recently purchased a brand new OEM Samsung Note 4 Battery and but still has problems. I'm currently on stock DOK2 and still having trouble. Does anybody know what I can do to fix this? I can't contact the original seller anymore
Is it rebooting on its own or shutting off completely?
Sent from my SM-N910T using Tapatalk
Starts rebooting on its own
qbanlinxx said:
Is it rebooting on its own or shutting off completely?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Reboots on its own
You have messed with kernel now flash stock kk and keep trouble away from you
junejo46726 said:
You have messed with kernel now flash stock kk and keep trouble away from you
Click to expand...
Click to collapse
If he's on dok2, likely stuck there and cannot go back to kk. For the op, I think you found why they were selling it..... I would recommend somewhere like swappa.Com over Craigslist.
Sent from my SM-N910T using XDA Free mobile app
Go into TWRP and wipe everything including internal sd. Then boot into download mode and flash the DOK2 firmware in ODIN. it could be the software related. If that doesn't fix it, then it might be hardware. You may have to take the phone apart and see if it's got a lose wire or a fried MB. Water damage can also cause this behavior.
So I have kept my device stock except for SuperSU and Busybox, no kernel flash, or rom flash yet, my question is, has Samsung fixed the issue with deleting NV data when flashing between roms? What I want to do, is flash TWRP and backup my current setup, then I want to unroot it, and back it up so that I can switch back and forth between rooted and stock, because I found out that screen mirroring breaks sometimes when you run the stock rom rooted and I want to know before hand if I need to backup my NV data with QPST before flashing back and forth between these two modes. I know I can do it in the terminal, but i've seen issues on my SGS3 with this being restored in a ROM that was not the one you backed up from, I.e. it seemed almost like the backup in the terminal assigned a unique identifier to the backup so when you flashed a ROM and needed to restore it would say the backup was corrupted, of course while I don't see any reason why the NV data would get destroyed during the process of what I'm trying to do, I just want to be fully prepared, because I'm pretty sure the .QCN generator I have for the SGS3 isn't going to write a new .QCN (NV data file) that is going to work on the note 4 seeing as how there were two or three updates to the .QCN version number for the SGS3.
Sent from my SM-N910T using XDA Free mobile app