Related
I flashed to Froyo 2.2 leaked the day I got my phone and never even knew about device ID. What does this mean for my future
avs420 said:
I flashed to Froyo 2.2 leaked the day I got my phone and never even knew about device ID. What does this mean for my future
Click to expand...
Click to collapse
You can always flash back to stock using the following method (see link):
http://forum.xda-developers.com/showthread.php?t=731989
Once you flash back to stock, write down the ID and then do as you wish. This is the only way I can think of right now in order to get your ID. However, I thought the Froyo 2.2 leaks only changed the Android ID and not the device ID. But in any case, you can always go back to stock and write whatever information you need down.
Yeah, the problem is with the Android ID. After flashing 20+ times now, I decided only 2 days ago to save my Android ID when I flashed back to JF6. Before then, I was running with the incorrect Android ID or randomly generated ID without a problem.
And the way I ended up getting my Android ID was flashing to JF6, and downloading the app "Android ID Changer" (no root required just to view your ID)
I still have a backup copy of my JF6 settings.db file on my computer from when I first enabled sideloading. Just so happens, it's also my backup of my Android ID.
So just a thought for everyone else who comes around this thread for whatever reason, if you have a nandroid backup of your 2.1 rom, just dump the data.img file and grab your settings.db, open it with your favorite SQLite editor, and nab your Android ID out of it.
Ok, let me make sure I know what we're talking about. I flashed my Captivate to the leaked 2.2. It's rooted and lagfixed.
So, in doing so I've lost my device ID? How does this affect the phone? I haven't noticed any differences.
Mike
MicroBeta said:
Ok, let me make sure I know what we're talking about. I flashed my Captivate to the leaked 2.2. It's rooted and lagfixed.
So, in doing so I've lost my device ID? How does this affect the phone? I haven't noticed any differences.
Mike
Click to expand...
Click to collapse
You may have periodic market problems. There are some games that may not work.
If it is working ok for you then go with it for now. When you are bored with what you are on and want to change roms you should and probably have to flag back to stock. St that time you can readily retrieve your id using app android id changer
Sent from my SAMSUNG-SGH-I897 using XDA App
i had an issue where even flashing back to stock one click wasn't rest IMEI or ID (also had changed my product code to tmobile.
Regardless your originial id can be found in multiple places
1. i believe its on the label under your battery
2. if the label is unreadable if you registered your phone with samsung website log in you can see your IMEI.
bames said:
i had an issue where even flashing back to stock one click wasn't rest IMEI or ID (also had changed my product code to tmobile.
Regardless your originial id can be found in multiple places
1. i believe its on the label under your battery
2. if the label is unreadable if you registered your phone with samsung website log in you can see your IMEI.
Click to expand...
Click to collapse
The IMEI and Android ID are NOT the same thing. They are not related in any way at all.
If you mess up your IMEI there is no way to recover it or change it without a hardware device. The IMEI ties your phone to the carrier network and is used in conjunction with your SIM card.
This discussion is about the Android ID - it has nothing to do with cell phone networks or carriers, but it is used by games and the Market to identify your device. It can be changed very easily.
alphadog00 said:
The IMEI and Android ID are NOT the same thing. They are not related in any way at all.
If you mess up your IMEI there is no way to recover it or change it without a hardware device. The IMEI ties your phone to the carrier network and is used in conjunction with your SIM card.
This discussion is about the Android ID - it has nothing to do with cell phone networks or carriers, but it is used by games and the Market to identify your device. It can be changed very easily.
Click to expand...
Click to collapse
not sure what your referring to as hardware device. Mine was messed up after flashing one of the i9000 roms as was my product code. Many of the custom roms assign a generic imei when installed but is usually restore to original when one click odin back to stock. In one instance doing such wouldn't restore it.
Both were able to be restored using root manager and a hex editor to correct the nv_data.bin file.
Where do you find the device id anyway?
qwertyaas said:
Where do you find the device id anyway?
Click to expand...
Click to collapse
I downloaded an app called "ID" made by "Sora Takayama" from the market. That lists your SIM Serial, Device ID, Android ID and Subscriber ID.
The IMEI and Android ID are NOT the same thing. They are not related in any way at all.
If you mess up your IMEI there is no way to recover it or change it without a hardware device. The IMEI ties your phone to the carrier network and is used in conjunction with your SIM card.
This discussion is about the Android ID - it has nothing to do with cell phone networks or carriers, but it is used by games and the Market to identify your device. It can be changed very easily.
Click to expand...
Click to collapse
Actually if you look at the first post the user asked specifically about their DEVICE ID (+ the thread title is regarding DEVICE ID) which is the IMEI as i understand. The Android ID is in fact different than the IMEI (DEVICE ID) and its possible he meant to reference android id but i was simply responding to the question as it was stated rather than reading anything into it.
So to be clear my understanding is
IMEI = DEVICE ID
IMEI does not = ANDROID ID
DEVICE ID does not = ANDROID ID
-------------
and +1 on the ID app...i am going to snap a screen shot of it to keep saved on external and hard drive so i have the info accessible if something gets messed up.
Sorry I meant Android ID
What happens if you ddn't write down your device ID when you got your phone?
A little Korean dude shows up at your house, rings the bell and then laughs in your face.
JK
cappysw10 said:
What happens if you ddn't write down your device ID when you got your phone?
A little Korean dude shows up at your house, rings the bell and then laughs in your face.
JK
Click to expand...
Click to collapse
he already did that after the most recent "gps optimization" app released in the market
Hi there,
I am having difficulty unlocking my new (UK) galaxy S2 and I figured this is the best place to ask for help. I have searched the threads on this forum and have not been able to find the answers I need. So I'm starting a new thread.
I have rooted the phone successfully and followed the instructions with the chainfire app and when it finished it said it couldn't find the unlock code. The phone came from Virgin as part of a contract, however the contract has been cancelled and I don’t have a virgin sim any more so I haven’t actually tried it with the virgin network. It might be worth mentioning here that when I put a different sim card in it the screen that pops up asking for the unlock code isn't there. I have also completed the procedure with the “galaxy S Unlock” app created by Helroz and that was also unsuccessful. Because the three steps in "galaxy S unlock" were unsuccessful I have restored the efs folder back to its original state. I have not bothered to try the manual method of recovering the unlock code using the hex editor because after reading this forum it seemed unlikely to work and it looked like a bit of a hassle.
I have tried several sim cards in the phone that work with my friend’s phone. And my phone was unable to connect to any networks. Except, when I tried my friends T-Mobile contract sim card I connected to the T-mobile network but my phone wouldn't allow out going or incoming calls however the data network worked fine! Yes the internet was working through the t-mobile network (wifi was turned off)
Isn't that weird!!!! So it kind of looks like the phone might be being blocked by the service provider but I find that very unlikely because up until a couple of days ago the phone was sealed in its box.
I have read through most of the "[HOWTO] GT-I9100 Free SIM Unlock via nv_data.bin by Odia" thread and there is some mention of a new locking technique employed by the various phone network companies. Does my problem sound like it could fall in to that category??
It might also be worth mentioning that I took the phone to a phone shop to see if they could unlock it. They couldn't, but the guy did check the IMEI number on a website called checkmend.com and that site reported: "checkmend has a record of this item having been blocked by a cell phone network" and "checkmend has a record that this item is currently blocked by one or more cell phone networks". Does anyone know anything about this website and weather it is reliable or not. Like I say I find it extremely unlikely that it has been blocked because I have only just got it out of the sealed box.
I am very frustrated as you can all imagine and I would really appreciate some help. Feel free to ask any questions, I am a bit of a noob but I'm not completely incompitent so don't be afraid to get technical.
Thank you for listening,
Yours,
Dardarland.
Bump...
I'm having kind of the same trouble here...
I tried the Chainfire's app and it couldn't find my code, so i went and tried the Helroz App
after following the instructiones in the app and checking with *#7465625# it changed network block to OFF... but when i inserted a diff carrier sim it said: network block... and now my other carrier sim got blocked and won't get recognized by the phone it used to be in... LOL
pls help us both!!
Unlocking
Hi
I did have the same problems with the chainfire app
what i did is use Galaxy_S Unlock (google it as I can not post links at the moment)
Also you will need to install busybox for this to work.
just search for busybox in market and install the first app that comes up
Hope it works
ragsbava said:
Hi
I did have the same problems with the chainfire app
what i did is use Galaxy_S Unlock (google it as I can not post links at the moment)
Also you will need to install busybox for this to work.
just search for busybox in market and install the first app that comes up
Hope it works
Click to expand...
Click to collapse
Thanks fella, worked like a charm
Re: fjaraiza
fjaraiza said:
Bump...
I'm having kind of the same trouble here...
I tried the Chainfire's app and it couldn't find my code, so i went and tried the Helroz App
after following the instructiones in the app and checking with *#7465625# it changed network block to OFF... but when i inserted a diff carrier sim it said: network block... and now my other carrier sim got blocked and won't get recognized by the phone it used to be in... LOL
pls help us both!!
Click to expand...
Click to collapse
Hi fjaraiza,
I saw somewhere in the forum guys that were having similar problems due to the carrier branded rom they had on the phone and due to helroz method which is far more intrusive than odia's. Helroz is flipping bits within nv_data.bin which might lead to corruption. The success of Helroz's method also depends on the phone protection method, some newer versions check the correspondent md5 and ignore the file if it's not the right one.
Your best bet would be to restore an /efs backup if you have one or backup the current state of /efs and try another rom.
Good luck,
Stefan.
P.S.: use thanks when the supplied information is useful
can unlock the messed up ones for a lil fee, pm
Helroz unlocks but then locks again...
Hi all, I've got a weird problem. I used Helroz SIM unlocker on my SGS2 (Im running the latest CM9 build 28/8) and it works. Helroz unlocks the phone but only for about 1-2h?! After about 1-2h the phone has lost NW connection and ask for the SIM unlock code. If I press 'dismiss' then I can run Helroz unlocker again and it will be ok for 1-2h and then loose the unlock again... Has anyone had this problem? Before I used a stock Samsung ROM and then Helroz unlocker worked perfectly, its since I've moved to CM9 ROM that I'm having this issue. Can anyone help?
Thanks in advance
I did have the same problems with the chainfire app
what i did is use Galaxy_S Unlock (google it as I can not post links at the moment)
Also you will need to install busybox for this to work.
just search for busybox in market and install the first app that comes up
Click to expand...
Click to collapse
This worked like magic, but i can i now uninstall the busybox as i dont need it or do i have to keep it on my phone to have it unlocked?
same pronblem
i unlocked my phone using "samsung galaxy unlock" when it was on gingerbread. then i updated it to jelly bean using cm10.2 & after that when i switched it on it says "Enter sim unlock code". i used the same app again but did't get any benefit. also tried few other apps but failed. now when i put the 3 network (the original carrier) it do same with that as well. somebody tell me what to do?
Relocated from email discussion:
Hey, great tool[editorial: I think in reference to: http://code.google.com/p/cdmaworkshoptool/ ]. Would it be possible for me to get a copy of the most recent build? I'm looking into some things on the galaxy s3 because we lose the min and phone number on non-stock roms. -C
to C:
Most recent build is .2 which is public.. What exactly do you mean by lose? As in they must be reprogrammed after.a rom is flashed? Does the, normal version of dev term you have downloaded fail to write the number back?
3:39 PM (2 hours ago)
to me
It's a temporary problem with cm10. Development has been slow. It's lost on the first reboot and then mms doesn't work. In android, under status about it lists "My Phone Number" as unknown and Min as unknown. Just trying to see if I can write them while the OS is booted.
to C:
To write a mdn and min typically you would connect to the phone in diagnostic mode.. Send mode offline. Send spc. Then simply write mdn and min from the nam part of the interface.. There are typically three nv items which dev term writes for mdn, and min. Then, mode reset will reset and you can confirm if this wrote the nv item..
Did that answer any questions?
to C:
Having never tested a galaxy s iii I'm not sure if devterm should work... There is alot of chatter online about a program called ets, you might look.for that if devterm doesn't work. Please let me know if you are able to successfully write on the galaxy siii.
to me
We are able to write to it with qpst. I actually got the numbers back, but I'm not sure how. Now Im in the process of seeing if I can figure out how to replicate it. What is supposed to happen when you put it into reset mode? It doesn't work for me after that.
to C:
After mode reset the radio of the phone will literally reset.. Some phones this will actually turn off and on the whole phone.. Some will just show no.service temporarily... After mode reset.cdmadevterm will disconnect.from phone.. There are alot of variables, but typically if.qpst could write the phone devterm should also be able.. The mdn and min are really quite simply three nv items, I suspect the subsystem that normally stores this information is being overwritten or formatted by cyanogen...
if you have ever used cdma worksop or qxdm the mode offline and mode reset is functionally the.same..
to me
Thank you so much for going back and forth with me on this. I really appreciate it. The only major difference I noticed between an nv dump on stock and cm is that cm has a lock code for some reason. What is this ETS software you're referring to? CDMA workshop is a bit too expensive unfortunately.
Although I am not totally familiar with the tool it is linked on XDA in another section:
http://forum.xda-developers.com/showthread.php?t=1696621
I wonder if this might have something to do with the chipset not being qualcomm? On the other hand if you said it worked with qpst maybe they are somehow compatible?
The VIA tool probably won't work since we do have a qualcomm chipset. I still have not figured out how i managed to get it to work once but it came up with the unlock sim message I put in the code for my phone that I Found in nvram and then I tried the spc and a few other things and eventually hit dismiss. It said that it could not connect or something to that effect. Then I checked and it had my phone number as 000-000-xxxx which xxx was that unlock code. Then I restarted and I had the number again. I'm wondering if I somehow got the phone to let go of how its storing the phone number.
Hm. If it is qualcomm I would think that cdmaDevTerm should work... this is how one would normally write the mdn and min with devterm:
http://www.chromableedstudios.com/techninjutsu/howtowritemdnminwithcdmadevterm
Perhaps if this doesn't work you could include the response to the NV write from the LogQ tab to help understand the behavior? Maybe the rom is activating a different Nam profile or something?(I'm not sure if I even have a spot on the UI for that in devterm but a log might help understand)
(for logging purposes you may want to trying writing a fake phone number for privacy)
I guess my question also is: are you trying to figure out why the rom does this? or just a good way to fix it when it does?
Hi to all, I'm writing here because I had my first problems with my v970 (with etotalk rom). This evening I checked my mobile and I found that none of the sim was active (I was not in airplane mode) and I could not activate them, as if they were not in their slots. Meanwhile the upper part of the device began to heat up, so I tought it could be an antenna/receiver problem. I almost forgot to say that I installed Truecaller (deleting Contapps) and updated facebook and few others apps less than one hour before the event, but I already uninstalled them to exclude some of the possible causes. I'll gladly listen to any advice. Thank's in advance. GL
Restart, and see if it continues.
Already tried a lot of times, with or without sim cards. I also noticed an abnormal use of battery.
When did the problem start? What did you do before it started? Does your cellphone always have no signal, or does it come & go (sometimes SIM works, sometimes it doesn't)? Have you checked your APN settings?
post-mortem said:
When did the problem start? What did you do before it started? Does your cellphone always have no signal, or does it come & go (sometimes SIM works, sometimes it doesn't)? Have you checked your APN settings?
Click to expand...
Click to collapse
The problem started yesterday and I never experimented It till now. As I Said, before I encountered It, I updated some apps from the market and I changed the default caller manager (should I call It in this way?) with Truecaller. I also deleted my sim contacts
. I can't check apn because there are no apns to check (Android shows me the voice "mobile networks" but I can't select it
Update: I tried to restore the original rom, but the problem persists. I also made a check with the recovery, and it shows me that the device cannot detect sim cards. I begin to think that it's an hardware problem (ouch). Am I right?
What did you do in recovery that checks SIM cards? Are you talking about CWM recovery?
post-mortem said:
What did you do in recovery that checks SIM cards? Are you talking about CWM recovery?
Click to expand...
Click to collapse
Nope, it's the faulty recovery that etotalk sent me with the phone. I would like to install the cwm and flash another rom, but I'll leave that as the last option
If the recovery they sent you is faulty, then what good is it? If there's a custom recovery available for your phone, you might as well go with it, not that it'll solve anything by itself.
You might try inserting some kind of shim along with the SIM card to see if the extra pressure help make contact with the leads. Careful, of course, that whatever you stick in there doesn't stay behind.
post-mortem said:
If the recovery they sent you is faulty, then what good is it? If there's a custom recovery available for your phone, you might as well go with it, not that it'll solve anything by itself.
You might try inserting some kind of shim along with the SIM card to see if the extra pressure help make contact with the leads. Careful, of course, that whatever you stick in there doesn't stay behind.
Click to expand...
Click to collapse
I know about the recovery, but I was trying to don't invalidate the warranty (as if I'll ever use it...). Now I'm charging the phone, it's already the third time today...
Aw, heck. If you've got warranty, just send it in.
post-mortem said:
Aw, heck. If you've got warranty, just send it in.
Click to expand...
Click to collapse
Yep, I've got warranty, but sending it in China will cost me almost as much as buying a new one
Ok, I flashed a recovery and a custom rom, but nothing happened.The signal is still absent and the antenna heats up the same way as before. I tried to enter engineer mode and it shows me messages as "com.android.internal.telephony.CommandExcepti on: RADIO_NOT_AVAILABLE", "3G off. Cannot set", ecc... It also shows me "invalid IMEI" if I try to look at it and I cannot change it back with the AT +EGMR command (it says "Radio on" and "SIM State: ABSENT", altough the SIM card is in its slot).
I think you have to crack the case.
ArcheoGian said:
Ok, I flashed a recovery and a custom rom, but nothing happened.The signal is still absent and the antenna heats up the same way as before. I tried to enter engineer mode and it shows me messages as "com.android.internal.telephony.CommandExcepti on: RADIO_NOT_AVAILABLE", "3G off. Cannot set", ecc... It also shows me "invalid IMEI" if I try to look at it and I cannot change it back with the AT +EGMR command (it says "Radio on" and "SIM State: ABSENT", altough the SIM card is in its slot).
Click to expand...
Click to collapse
Hmmm... if your phone is reporting invalid IMEI numbers then I would try first to get that working as it should. Read this tutorial and re-write your IMEI numbers.
Then I would try the latest stock ROM, which is available on ZTE support website. Here is the direct link to the ROM.
If your phone still doesn't work after that, then I'm afraid you have a hardware problem.
I have had the telephone for more than one month with no problem. Trying every ROM made by Bruno with no problem at all with signal, but...
About 4 days ago, I started suffering exactly the same problems stated by ArcheoGian. I have tried everything (installing older Roms, rebooting, changing SIMs from 1 to 2, etc.) but unfortunately with no success. I just have to try to install the original ROM, but I supose it will be the same.
Afer a few reboots, I can make the telephone to search for a network, it founds it, it connects, it transfers data, I can make calls, but ramdomly (can be after 30 seconds, 30 minutes or maximum one hour) it disconnects and the red X of death (Xbox 360 times ) appears on top of the screen.
I can try to go and return from airplane mode, or search for networks that it won't re-connect.
I fear it can become a typical problem for this phone.
I am "delighted" to send it back to China and wait for two months to get it back (after explaining it to the seller and so on). Fingers crossed
@prinxo: did you buy it from eto...k? (I don't know if I can write the entire name of the seller)
Update: I tried everything it was told me (except to crack the case, at least not yet...), my last hope is to manually insert the IMEIs inside the data folder. There's just one problem: none of the methods suggested in the link posted by bcgngm works on my phone, so I need to generate the IMEIs whit my pc (I couldn't open the exe with windows 7, I'll try with win xp in a while, otherwise I have to ask someone to create it for me).
ArcheoGian said:
@prinxo: did you buy it from eto...k? (I don't know if I can write the entire name of the seller)
Click to expand...
Click to collapse
No, I bought it from another seller at Aliexpress.
As I thought: I tried to re-install an original ROM, and everything remains the same. I thought I was successfull but after one hour the phone disconnected itself from the network. After that moment, I need about 3 re-boots to get signal again and it lasts for just a few minutes.
At this point, I would disregard a software problem.
Happy happy to have to send it back to China.
ArcheoGian said:
Update: I tried everything it was told me (except to crack the case, at least not yet...), my last hope is to manually insert the IMEIs inside the data folder. There's just one problem: none of the methods suggested in the link posted by bcgngm works on my phone, so I need to generate the IMEIs whit my pc (I couldn't open the exe with windows 7, I'll try with win xp in a while, otherwise I have to ask someone to create it for me).
Click to expand...
Click to collapse
Why do you say it is not working? My preferred method is to use the adb commands (and for that you have to install Android SDK). Don't forget that when you type the commands there is no output message on the screen. The phone has to be restarted so that changes take effect.
bgcngm said:
Why do you say it is not working? My preferred method is to use the adb commands (and for that you have to install Android SDK). Don't forget that when you type the commands there is no output message on the screen. The phone has to be restarted so that changes take effect.
Click to expand...
Click to collapse
The third and the fourth ones are the only methods to restore IMEI I didn't try, just because I never used sdk and adb (and I'm not sure to be able to use them). I followed the others options (I also created the IMEI file with the russian program), but it continues to show me the "invalid IMEI" message. Can you help me, maybe showing me a good walkthrough?
This ADB Tutorial looks easy to follow. Check it out!
Hey everyone here at XDA, just wanted to share my recent experience with loosing my phone service after flashing MIUI from the clockwork rom manager app. Basically, i flashed the rom from within the rom manager app and really liked the rom until I noticed that I had lost data and phone service. Apparently I was stuck in roaming, with a little triangle replacing the 4g icon in the notification bar at the top of the screen. I did a bunch of searching through forums and everyone who was having this issue was having it due to the loss of there IMEI. The people afflicted by loss of service did not have the correct IMEI or any at all on their phone.
But my IMEI was there and it was correct. So I restored the nandroid backup I made at the time of flashing MIUI but that didn't solve the issue so I restored the backup I made when I originally rooted my phone and installed CWM. That still didn't fix it. Some forum posts were saying the SIM card might have been fried, some were saying that they had totally lost the ERI folder, or something... I was getting worried. The last thing I tried was flashing a stock 4.1.1 rom via Odin and still I had no service. Well I needed a phone for work so I went on the VZW site Monday morning and switched my service to an old blackberry storm (I know, right?) that I had laying around and went to work. When I got home I looked on the web some more and found info about accessing the hidden menu with a code that wipes all data and settings. Is this different than the factory wipe from the settings menu? Anyway I wiped via the hidden menu and after that the little roaming triangle was gone. I switched my service back to the Gs3, which involved taking out the SIM card and registering it again, and after that my service, data, and 4g icon was back. Problem solved. I am wondering though if I could have used the hidden menu/wipe feature from MIUI, and for that matter what caused my phone to get stuck in roaming?
I would like to root, and explore other roms but now I'm worried about this happening again. It doesn't help that someone told me service providers can deny service for rooting your phone. I don't know if that's true or not. I know now that I should make a IMEI backup, even though I don't think that was my problem. I recently took the ota and am back on stock 4.1.2. Just wanted to share this with everyone, and bounce it around to see if anyone has any ideas, and maybe this could help someone who is having the same issue. As far as the hidden menu and wipe code, I don't remember what it was but you could look it up if you need to try it.
Thanks everyone
mattunden said:
Hey everyone here at XDA, just wanted to share my recent experience with loosing my phone service after flashing MIUI from the clockwork rom manager app. Basically, i flashed the rom from within the rom manager app and really liked the rom until I noticed that I had lost data and phone service. Apparently I was stuck in roaming, with a little triangle replacing the 4g icon in the notification bar at the top of the screen. I did a bunch of searching through forums and everyone who was having this issue was having it due to the loss of there IMEI. The people afflicted by loss of service did not have the correct IMEI or any at all on their phone.
But my IMEI was there and it was correct. So I restored the nandroid backup I made at the time of flashing MIUI but that didn't solve the issue so I restored the backup I made when I originally rooted my phone and installed CWM. That still didn't fix it. Some forum posts were saying the SIM card might have been fried, some were saying that they had totally lost the ERI folder, or something... I was getting worried. The last thing I tried was flashing a stock 4.1.1 rom via Odin and still I had no service. Well I needed a phone for work so I went on the VZW site Monday morning and switched my service to an old blackberry storm (I know, right?) that I had laying around and went to work. When I got home I looked on the web some more and found info about accessing the hidden menu with a code that wipes all data and settings. Is this different than the factory wipe from the settings menu? Anyway I wiped via the hidden menu and after that the little roaming triangle was gone. I switched my service back to the Gs3, which involved taking out the SIM card and registering it again, and after that my service, data, and 4g icon was back. Problem solved. I am wondering though if I could have used the hidden menu/wipe feature from MIUI, and for that matter what caused my phone to get stuck in roaming?
I would like to root, and explore other roms but now I'm worried about this happening again. It doesn't help that someone told me service providers can deny service for rooting your phone. I don't know if that's true or not. I know now that I should make a IMEI backup, even though I don't think that was my problem. I recently took the ota and am back on stock 4.1.2. Just wanted to share this with everyone, and bounce it around to see if anyone has any ideas, and maybe this could help someone who is having the same issue. As far as the hidden menu and wipe code, I don't remember what it was but you could look it up if you need to try it.
Thanks everyone
Click to expand...
Click to collapse
My suggestion, never use Rom Manager to flash!! Stick to TWRP(I prefer twrp), CWM or Odin.