Database Develop

[Q] IMEI changed after flash

Installed the CM7 rom as usual but
my imei was changed to 000000000000000 and can not make calls and send sms
(Although not show signal, you can
access the internet). In the system
does not contain the efs folder and
had not backed up. Is there a
solution?
not want to change, I know it's
illegal, I "only" repair the original. Yes,
I googled before posting, but found
nothing satisfactory. thank you and sorry for my bad english.

that was a bug of the rom which was fixed
try flashing the firmware through odin

thanks for the reply. Had already
restored the 2.3.6 rom by odin and
several others with cwm and not
solved.

then its a big problem

dheeraj (dhlalit11) said:
then its a big problem
Click to expand...
Click to collapse
+1
I guess its a hardware problem.. something wrong with the motherboard.. if flashing stock ROM or custom ROM didn't solve it then i guess you have to take it to the SC..

Google gave me this: http://forum.xda-developers.com/showthread.php?t=1264021
- Via xda premium

a.cid said:
Google gave me this: http://forum.xda-developers.com/showthread.php?t=1264021
- Via xda premium
Click to expand...
Click to collapse
had tried this method but the efs
folder (And their archives) do not exist
in the system, unfortunately ...
I've been exploring the system files and view the log Custom recovery found the problem. Recovery was an error during the flash unfortunately could not solve the problem (yet) but anyway it was good to know where the error happened. Any help will be important, since that time my phone is just an MP3 player lol
Once again thank you and sorry for my english

Happened with me once and i think a trip to one of the samsung care center won't hurt much
Just be sure not to tell the people there that you flashed the cm7 custom rom on the device.

thousandecibels said:
Happened with me once and i think a trip to one of the samsung care center won't hurt much
Just be sure not to tell the people there that you flashed the cm7 custom rom on the device.
Click to expand...
Click to collapse
OK, thanks for the reply. I will try
a downgrade to Froyo in any
carrier to recover the efs and if it
fails it'll follow your advice. Thank
you very much

[Q] IMEI unrecoverably lost. EFS wiped. Help needed.

Hi everyone.
I've got to this bad situation where I wiped my IMEI. I was trying to flash CyanogenMod, and it flashed fine except that IMEI was turning into zeroes and radio did not worked. Reverting back to stock ROM helped pretty much, it worked there. So, I decided to back up EFS prior to flashing again. I did it on a rooted stock firmware using online nandroid backup from market. It told me that backup was done fine, and I did not actually check, which was a huge mistake. I reflashed CM, gapps, and then that backup. Obviously, as that backup did not really contain anything, CM did not start. Original firmware flashed by Odin starts up, however, I immediately get "blahblah.gapps failed to start", I cannot connect to wifi because I cannot enter my password for Wifi - kayboard doesn't show up (if I remove the password on router, it connects fine). If I proceed, SetupWizard just crashes.
So, without backup, the only thing I can do is possibly flash EFS from another S Advance i9070P. I know that it would contain others' IMEI, but I can swear I fist change it before flashing. Or, if anybody's willing to help, you can just replace your IMEI with something generic but recognizable, as 123456789012345 for example. I'd try to deal with it.
Or, if there's any other suggestion, I'd gladly listen.

Venseiiz said:
Hi everyone.
I've got to this bad situation where I wiped my IMEI. I was trying to flash CyanogenMod, and it flashed fine except that IMEI was turning into zeroes and radio did not worked. Reverting back to stock ROM helped pretty much, it worked there. So, I decided to back up EFS prior to flashing again. I did it on a rooted stock firmware using online nandroid backup from market. It told me that backup was done fine, and I did not actually check, which was a huge mistake. I reflashed CM, gapps, and then that backup. Obviously, as that backup did not really contain anything, CM did not start. Original firmware flashed by Odin starts up, however, I immediately get "blahblah.gapps failed to start", I cannot connect to wifi because I cannot enter my password for Wifi - kayboard doesn't show up (if I remove the password on router, it connects fine). If I proceed, SetupWizard just crashes.
So, without backup, the only thing I can do is possibly flash EFS from another S Advance i9070P. I know that it would contain others' IMEI, but I can swear I fist change it before flashing. Or, if anybody's willing to help, you can just replace your IMEI with something generic but recognizable, as 123456789012345 for example. I'd try to deal with it.
Or, if there's any other suggestion, I'd gladly listen.
Click to expand...
Click to collapse
Did you do factory reset and wipe cache? Go back to stock with flashing stock firmware. That: "blahblah.gapps failed to start" is because of wrong version of GAPPS installed.

shut_down said:
Did you do factory reset and wipe cache? Go back to stock with flashing stock firmware. That: "blahblah.gapps failed to start" is because of wrong version of GAPPS installed.
Click to expand...
Click to collapse
Oh but I did, maybe 5 times already... Stock recovery shows: E: failed to mount /efs (Invalid argument)

I had this problem once. Took a downgrade to gingerbread to fix mine. May wwant to try that.
Sent from my S Advance because I can

bobfrantic said:
I had this problem once. Took a downgrade to gingerbread to fix mine. May wwant to try that.
Sent from my S Advance because I can
Click to expand...
Click to collapse
Hm, tried this today. It won't start at all. Showing just its logo all the time.

Venseiiz said:
Hm, tried this today. It won't start at all. Showing just its logo all the time.
Click to expand...
Click to collapse
With a guide to downgrade, not just flash any GB firmware.
http://forum.xda-developers.com/showthread.php?t=2100642

shut_down said:
With a guide to downgrade, not just flash any GB firmware.
http://forum.xda-developers.com/showthread.php?t=2100642
Click to expand...
Click to collapse
I was going to show that guide, thanks for beating me to it LOL

Wow, guys, thank you very much! It worked! Many-many thanks :laugh::good:

Venseiiz said:
Wow, guys, thank you very much! It worked! Many-many thanks :laugh::good:
Click to expand...
Click to collapse
Glad to read that... and this is my 1000th post, LOL.

bobfrantic said:
Glad to read that... and this is my 1000th post, LOL.
Click to expand...
Click to collapse
Hey, time to rise the topic again. After I repaired my phone, after some time I decided to flash a rom for a different region, 2.3.6 also (i did not update it to 4.1.2 anymore). I used ODIN 3.07. But now it does not turn on. At all. It does not react to the power button. No vibration, nothing. No recovery mode, no odin mode. Looks like a complete brick. Why the hell is that?!
Ah, by the way, as I stated in my first post, it's NFC model. The downgrade guide was for non-NFC. So I did not have any NFC functionality after downgrade. Here I wanted to return it as well, so I used a FW for i9070P version. Never had an idea it wouldn't turn on after that.
What can I do?

is it possible???
Hi. I ve experienced the same problem, except tht I ve completely lost IMEI and baseband. Sent it for repair.the person said 1st we ll recover the baseband then IMEI would b recovered. Blv me its been 2 weeks now. I ve read every possible solution I could find but it didnt help. As far as i could understand, IMEI has to b there for baseband to recover. Tried efs pro. Tried 9 steps for IMEI recovery but nothing helped. Tried to downgrade to GB acc to the guide but repartition fails on ODIN 1.85. Used triangle away to reset counter.the counts turn 0 with device status 'samsung official' but as soon as I flash stock JB, the current binary shows custom. IMEI folder in efs is empty. Tried to do the complex methods but got scared coz rest of the fone is f9. Is it possible tht it will be repaired or not. Is there a way out?

[Q] My galaxy S4 active sgh-i537 is soft bricked, need help

My phone was rooted then it updated to the 4.3 and when i reset it because the galaxy play store was not working i tried to re root it and it got stuck on a screen upon boot that says Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. But when i go into Kies it just tries to connect and does't not recognize my phone. I need help on what to do please, I have tried everything.

lavorno said:
My phone was rooted then it updated to the 4.3 and when i reset it because the galaxy play store was not working i tried to re root it and it got stuck on a screen upon boot that says Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. But when i go into Kies it just tries to connect and does't not recognize my phone. I need help on what to do please, I have tried everything.
Click to expand...
Click to collapse
Do you have CWM installed?

tiskael said:
Do you have CWM installed?
Click to expand...
Click to collapse
no

lavorno said:
no
Click to expand...
Click to collapse
Sorry, should have read a bit closer. I was going to recommend that you use CWM to flash ROMs back but you don't have the i9295. Where did you purchase it from? I'm from Australia, so I'm not sure about the US, but I think I've read in other threads that some Best Buys(?) have Samsung stores in them that have reflashed the stock firmware free of charge without actually checking your warranty. Maybe you want to look into this?

tiskael said:
Sorry, should have read a bit closer. I was going to recommend that you use CWM to flash ROMs back but you don't have the i9295. Where did you purchase it from? I'm from Australia, so I'm not sure about the US, but I think I've read in other threads that some Best Buys(?) have Samsung stores in them that have reflashed the stock firmware free of charge without actually checking your warranty. Maybe you want to look into this?
The problem with your S4A is that it has a locked bootloader, so you can't flash firmware yourself, sorry!
Click to expand...
Click to collapse
I bought it in the US at a best buy so i will take it there and see what they can do, thanks for the help.

lavorno said:
I bought it in the US at a best buy so i will take it there and see what they can do, thanks for the help.
Click to expand...
Click to collapse
If you don't want to go to Best Buy right away you can try flashing the firmware yourself.
http://forum.xda-developers.com/showthread.php?t=2629093

If you took the official OTA for 4.3, ML2, there is no known root exploit available. Odin is easy to flash with - there are 1 clicks that do all the hard work for you, all you have to do is put your phone into download mode and the app does the rest on your PC. Make sure you have the proper drivers installed. Best way I found was to download the software suite from Samsung for the phone. Without the proper drivers Odin won't see the phone (I found this out the hard way.)

lavorno said:
I bought it in the US at a best buy so i will take it there and see what they can do, thanks for the help.
Click to expand...
Click to collapse
I just took it to best buy and they restored it and now it is as good as new, thanks for the advice.

lavorno said:
I just took it to best buy and they restored it and now it is as good as new, thanks for the advice.
Click to expand...
Click to collapse
No worries, I heard they were pretty good in the US. Remember though, you can't root it on 4.3 (yet). If they've set it back to 4.2.2 then you can root again and not update to 4.3. If they've set it to 4.3 then either you will have to follow @Devo7v's instruction to flash back or wait it out as a root method is currently being worked on.

Bricked SGH i537
my sghi537 has bricked. i can only enter into download mode..
As i downloaded stock firmware of 4.3 ML2 and i tried to flash it by Odin...
Unfortunately at first odin said that i have no pit partition...
then i downloaded Pit and tried to flash but ^^^ write failed ^^^ was the thing i saw every time...
I looked up my phn download mode screen and i found that ^^^ Write protection Enable ^^^
So i couldnt flash stock ML2 firmware and my phn is bricked ....
Someone pls help me...........

Shabnur said:
my sghi537 has bricked. i can only enter into download mode..
As i downloaded stock firmware of 4.3 ML2 and i tried to flash it by Odin...
Unfortunately at first odin said that i have no pit partition...
then i downloaded Pit and tried to flash but ^^^ write failed ^^^ was the thing i saw every time...
I looked up my phn download mode screen and i found that ^^^ Write protection Enable ^^^
So i couldnt flash stock ML2 firmware and my phn is bricked ....
Someone pls help me...........
Click to expand...
Click to collapse
What firmware were you originally on.

Devo7v said:
What firmware were you originally on.
Click to expand...
Click to collapse
I was in 4.3 Ml2
it will b a lot if u help me......
my phn is dead now..
Its saying try kies to recover firmware......

Shabnur said:
I was in 4.3 Ml2
it will b a lot if u help me......
my phn is dead now..
Its saying try kies to recover firmware......
Click to expand...
Click to collapse
Download the full ML2 Odin, check the MD5 to make sure you didn't get a corrupted download. MAKE SURE all the files are in the right place in Odin and flash away. It should put the stock firmware back on the phone. Then you can proceed from there.

Devo7v said:
Download the full ML2 Odin, check the MD5 to make sure you didn't get a corrupted download. MAKE SURE all the files are in the right place in Odin and flash away. It should put the stock firmware back on the phone. Then you can proceed from there.
Click to expand...
Click to collapse
Sorry to disturb u again..
i m new in advance user mode..
will u tell me how i can compare the md5 num..
i dont even no where it is..
pls help me a little bit more....

Shabnur said:
Sorry to disturb u again..
i m new in advance user mode..
will u tell me how i can compare the md5 num..
i dont even no where it is..
pls help me a little bit more....
Click to expand...
Click to collapse
The MD5 is sort of like the fingerprint for the file, so you need the MD5 of the file you downloaded to match the MD5 that was posted in the thread. Download WinMD5Sum from the website here. Under File Name load the ML2 Odin zip package that you downloaded. WinMD5Sum will generate the MD5 of the file you downloaded and you can compare that to the MD5 the uploader posted in the thread. If the MD5's match then that means you downloaded exactly what was posted. If the MD5's don't match exactly, then you have a corrupted download and need to download it again.

[SOLVED] Bricked i9305? - No Recovery - "Get PIT for mapping" stuck - sboot.bin FAIL

[SOLVED] Bricked i9305? - No Recovery - "Get PIT for mapping" stuck - sboot.bin FAIL
Yo.
Basically been using this phone for ages, having random freezing issues for a while, so I decided to /****it and re-stock everything because it is likely that I have been an idiot with kernels/messing around with stuff once.
This freezing has persisted through stable, unstable, nightly CM 10.2/10.3/11 ROM's as well as pure stock and unrooted, so I figured it was something deeper down - the kernel, and I got a stock kernel for i9305 (attached). Everything basically went to ****, the phone got stuck bootlooping on the initial Samsung logo, doing the button-combo to get into recovery just stucks it on that logo. I can enter Download mode.
No biggie, I'll just ODIN it up (3.0.7) and flash the stock firmware, except now (this did not happen before the kernel flash) it simply fails with "sboot.bin FAIL", which people claim to be a PIT error (Kies not open btw, no KiesTrayAgent either, it's on the PC though), so I grab a i9305 stock PIT that I try and flash with the stock firmware, except now it gets stuck at "Get PIT for mapping" and never moves onwards from there.
So I'm essentially stuck with a problem that can probably be fixed by a stock firmware ODIN flash, and a problem that prevents me from fixing the PIT stuff to get the stock firmware through.
I have tried ODIN-flashing CWM recovery as well as stock recovery (also attached), but I'm still stuck on the logo regardless.
Any help here? Kinda lost ATM.
EDIT: Can't link/attach the .rar with the files. :S

Just re-install your back up

Raistlin1158 said:
Just re-install your back up
Click to expand...
Click to collapse
Retarded answer.
@OP
We need more data... first, which kernel did you flash ? If you can't attach it, link to it.
Second, what stock rom did you try to flash ?
Third, are you knoxed?

Hey guys.
Cheers for the answers, I just figured it out though actually. The sboot.bin error was caused by some bootloader-stuff-thingy I could hardly explain if I got a book on it. I got ahold of another stock ROM which flashed fine, I cleaned up and all that (NAND erase all did the job), back to CM11 as TouchWiz didn't fix my problems.
To answer your questions (others might have the problem and find this thread):
http://forum.xda-developers.com/galaxy-s3/development-i9305/recovery-odin-flashable-tar-t1971265 <- kernel
I tried to flash an "XXBMD1" stock ROM from SamMobile, it had worked previously.
I am Knoxed and have "tripeed the fuse" (trying to fix the crashing issues I went back to stock ROM, then it prompted for the 4.3 TouchWiz update which brings KNOX), so I'm without warranty (ODIN returns "KNOX Warranty Void: 1), but I guess I can consider this a learning experience as everything turned out good enough in the end.

There you go:
Based on JellyBean 4.1.2_XXBMD1 <--- You can't flash 4.1.2 because of the knox bootloader.
Had you tried a stick 4.3 you might have been sucessfull

daedric said:
Retarded answer.
Click to expand...
Click to collapse
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr

Raistlin1158 said:
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Click to expand...
Click to collapse
soft bricks aren't fixed by restoring nandroids.

Update odin and change usb cable and port.

Raistlin1158 said:
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Click to expand...
Click to collapse
Apologies for not detecting the irony on your post.
Yet, what you wrote means you didn't even bother to read the OP. What good would a nandbackup do, if he cannot even get to recovery?
I take back the retarded and replace it with lazy.
chongc1996 said:
soft bricks aren't fixed by restoring nandroids.
Click to expand...
Click to collapse
A nandroid wouldn't do any harm as soon as he got a recovery working
Raistlin1158 said:
Update odin and change usb cable and port.
Click to expand...
Click to collapse
Again, OP second post not read. His issue was probably originating in a attempt to flash a stock 4.1 (with 4.1 bootloader) over a 4.3 bootloader. Knox won't allow it.
Add stubbornness to laziness.
@ OP: please change the [Q] in the op to [SOLVED]

daedric said:
Apologies for not detecting the irony on your post.
Yet, what you wrote means you didn't even bother to read the OP. What good would a nandbackup do, if he cannot even get to recovery?
I take back the retarded and replace it with lazy.
A nandroid wouldn't do any harm as soon as he got a recovery working
Again, OP second post not read. His issue was probably originating in a attempt to flash a stock 4.1 (with 4.1 bootloader) over a 4.3 bootloader. Knox won't allow it.
Add stubbornness to laziness.
@ OP: please change the [Q] in the op to [SOLVED]
Click to expand...
Click to collapse
heh, last time i soft bricked, i could access recovery like op, but nandroid didn't help. some other problem that flashing stock rom solved

.... the phone got stuck bootlooping on the initial Samsung logo, doing the button-combo to get into recovery just stucks it on that logo. I can enter Download mode.
Click to expand...
Click to collapse
chongc1996 said:
heh, last time i soft bricked, i could access recovery like op, but nandroid didn't help. some other problem that flashing stock rom solved
Click to expand...
Click to collapse
As you can see, OP could NOT get to recovery, only download. His fault was attempting to flash 4.1 with OLD BOOTLOADER on top of a 4.3 NEW BOOTLOADER.

daedric said:
As you can see, OP could NOT get to recovery, only download. His fault was attempting to flash 4.1 with OLD BOOTLOADER on top of a 4.3 NEW BOOTLOADER.
Click to expand...
Click to collapse
ok sir, you are right, calm down, I'm out of here.

Cheers for the helpful as well as not-so-helpful responses, all back up and running now.

[Resolved] Stuck in Download Mode after failed flash attempt.

Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.

timmytron said:
Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.
Click to expand...
Click to collapse
Oh god are you on the US version (SGH-I537)? If you're on the international version (I9295) ignore this post but otherwise, you need to read and take in my short rant. Trust me I wish this weren't the case, but it is, and it's important:
The Galaxy S4 Active i537 has a locked bootloader. There is no way around this, no ifs ands or buts. You simply cannot flash custom ROMs or recoveries. That's it, end of story as far as CM, CWM, AOSP and such things are concerned. That being said there is a sort of recovery called SafeStrap which you can use to make nandroid backups, flash mods and STOCK-BASED roms, but it's not a true custom recovery in the sense that we had been used to, because of this locked bootloader nightmare.
OK so I think you're gonna want to check out this thread. It's all about how to install any firmware from download mode, I think you're gonna have to go with NE3 or NH3.
Let me reiterate. NO CUSTOM ROMS. NO CWM. No Paranoid, no cyanogenmod, no AOSP, no crossing go before going directly to jail. Sorry for the stupid joke but seriously, you have got to keep your phone on stock-based roms (of which there are unfortunately few).
Firmware download links

timmytron said:
Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.
Click to expand...
Click to collapse
What phone do you have (i537 or i9295) and what version of firmware were you on?

Devo7v said:
What phone do you have (i537 or i9295) and what version of firmware were you on?
Click to expand...
Click to collapse
i537 and second to last, I537UCUCNE3

Okay, :laugh: I'm back. FINALLY found some MD5 files that loaded. In the process of updating and putting things back they way they were. Thank you to all who viewed/helped!
Is there a way to mark this as "Resolved"?

Web browser login, edit, advanced.
Add "solved" to title?

same problem with my i537, need help
timmytron said:
Okay, :laugh: I'm back. FINALLY found some MD5 files that loaded. In the process of updating and putting things back they way they were. Thank you to all who viewed/helped!
Is there a way to mark this as "Resolved"?
Click to expand...
Click to collapse
Need help, having the same problem

baddhabbitz88 said:
Need help, having the same problem
Click to expand...
Click to collapse
Have you used ODIN before?

i537 Stuck in download mode
timmytron said:
Have you used ODIN before?
Click to expand...
Click to collapse
yes I have use odin but I think I have the same issue you did, need to know where to get the files .

baddhabbitz88 said:
yes I have use odin but I think I have the same issue you did, need to know where to get the files .
Click to expand...
Click to collapse
Okay. Well I'm not sure where I got the files either. What I'm going to do is upload them (please do keep in mind that it's a huge file) to my Drive account and I will link it here when complete. You are on the AT&T i537 version?

baddhabbitz88 said:
yes I have use odin but I think I have the same issue you did, need to know where to get the files .
Click to expand...
Click to collapse
Did you get my PM?

timmytron said:
Okay. Well I'm not sure where I got the files either. What I'm going to do is upload them (please do keep in mind that it's a huge file) to my Drive account and I will link it here when complete. You are on the AT&T i537 version?
Click to expand...
Click to collapse
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.

baddhabbitz88 said:
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.
Click to expand...
Click to collapse
Well AT&T decided to completely lock us out on this particular version on this particular phone. At least we have *ROOT*.

baddhabbitz88 said:
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.
Click to expand...
Click to collapse
You need to make sure you are flashing a version that is the same or more recent than the version you are currently on. You cannot downgrade your firmware or else you'll end up with a bootloop.

Devo7v said:
You need to make sure you are flashing a version that is the same or more recent than the version you are currently on. You cannot downgrade your firmware or else you'll end up with a bootloop.
Click to expand...
Click to collapse
k will try to find a more updated version but that is part of the problem is locating the firmware I need + this started doing it on its own and really never dug into it to no which firmware was on it other than rooted months ago with towelroot
---------- Post added at 09:36 PM ---------- Previous post was at 09:04 PM ----------
timmytron said:
Did you get my PM?
Click to expand...
Click to collapse
yeah I got it thanks but it didn't work still digging

baddhabbitz88 said:
k will try to find a more updated version but that is part of the problem is locating the firmware I need + this started doing it on its own and really never dug into it to no which firmware was on it other than rooted months ago with towelroot
---------- Post added at 09:36 PM ---------- Previous post was at 09:04 PM ----------
yeah I got it thanks but it didn't work still digging
Click to expand...
Click to collapse
Always check the stickies.
http://forum.xda-developers.com/showthread.php?t=2892445