Hello, i am having some issues with my n910t,
TLDR: Flashed back to stock, lost imei.
i have been playing around with some custom ROM's. when i tried to flash to stock i noticed that my phone did not have an imei, and the phone dies not work on the network
I am not sure on how to approach this.
Any help is appreciated.
moef11223 said:
Hello, i am having some issues with my n910t,
TLDR: Flashed back to stock, lost imei.
i have been playing around with some custom ROM's. when i tried to flash to stock i noticed that my phone did not have an imei, and the phone dies not work on the network
I am not sure on how to approach this.
Any help is appreciated.
Click to expand...
Click to collapse
Have you tried to ODIN back to stock? I would start there.
Or use Kies to do a recovery. Either should fix the issue.
Sent from my SM-N910T using XDA Free mobile app
ShrekOpher said:
Have you tried to ODIN back to stock? I would start there.
Or use Kies to do a recovery. Either should fix the issue.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Ive done both, unfortunately noting.
moef11223 said:
Ive done both, unfortunately noting.
Click to expand...
Click to collapse
Did you happen to do a backup in TWRP before this happened? If so restore it as it defaults to save your EFS folder which hopefully will fix your problem. If not, also try doing an Emergency recovery in KIES, some have said that worked as well. Another way that some have said it worked would be to ODIN back to KK and then upgrade to Lollipop. Just some more things to try.
chipworkz said:
Did you happen to do a backup in TWRP before this happened? If so restore it as it defaults to save your EFS folder which hopefully will fix your problem. If not, also try doing an Emergency recovery in KIES, some have said that worked as well. Another way that some have said it worked would be to ODIN back to KK and then upgrade to Lollipop. Just some more things to try.
Click to expand...
Click to collapse
Will try emergency recovery & kk->lollipop. Thank you will update the post.
chipworkz said:
Did you happen to do a backup in TWRP before this happened? If so restore it as it defaults to save your EFS folder which hopefully will fix your problem. If not, also try doing an Emergency recovery in KIES, some have said that worked as well. Another way that some have said it worked would be to ODIN back to KK and then upgrade to Lollipop. Just some more things to try.
Click to expand...
Click to collapse
Just did both, nothing.. Anyone have any other ideas?
moef11223 said:
Just did both, nothing.. Anyone have any other ideas?
Click to expand...
Click to collapse
Sent you a PM with a link to look at.
Also try searching this site for EFS as that is where the IMEI is stored.
Anybody willing to help me with my imei ? Please. I would be so grateful. Thanks.
Sent from my iPad using Tapatalk
Provided you guys are NOT blacklisted, this procedure I have used in the past and works.....
http://forum.xda-developers.com/galaxy-s2/general/guide-recover-imei-9-steps-t1264021
AxAtAx said:
Provided you guys are NOT blacklisted, this procedure I have used in the past and works.....
http://forum.xda-developers.com/galaxy-s2/general/guide-recover-imei-9-steps-t1264021
Click to expand...
Click to collapse
not working at all
Did you guys try flashing just the modem.bin? Extract modem.bin from stock firmware then flash it via Odin.
Related
Thanks to dhacker29 for the orginal idea and script!
Check out his orginal post for the Droid Bionic here!
Also, thanks to kennethpenn for providing the files you are about to use!
You have to be unlocked to use this!!
I AM NOT RESPONSIBLE FOR ANY THING THAT HAPPENS TO YOU OR YOUR PHONE!
I will try to help as much as possible, but that does not allow you to hold me responsible for anything whatsoever.
Step 1. Download this zip file and extract it, putting all the files in a folder.
Step 2. Download the file "One-Click Fastboot Restore.zip" and extract it, putting all the files in the same folder as the one above.
Step 3. Run the .bat file and follow the instructions.
DO NOT FIX PDS PARTITION UNLESS NECESSARY! IT WILL WIPE YOUR MAC ADDRESS FOR WIFI AND BLUETOOTH!
(Found some typos, not serious. Will fix soon)
No comments yet? I take that as a good sign, I haven't screwed up the script!
What does this do? Restore a backup from fastboot
Sent from my MB860 using XDA App
I'm also curious what exactly it does. At 140k it isn't replacing very much. Does it just fix files related to booting?
Didnt run it because I'm on linux and my phone is fine, but looking at the batch file, it automates flashing the stock gingerbread rom and restores PDS via fastboot.
when I run it, it gives me AdbWinApi.dll error. any suggestions?
I ran this for ****s and giggles and it returns everything back to stock AT&T 2.3 while giving you options along the way of what exactly you wanna restore to stock? webtop, system,pds, wipe data etc. works perfectly! makes life easier really! Phone booted right up after running no problems! Thanks!
beidave said:
when I run it, it gives me AdbWinApi.dll error. any suggestions?
Click to expand...
Click to collapse
Look for that dll file on Google and put it in the folder
Javi97100 said:
What does this do? Restore a backup from fastboot
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
tapeworm_george said:
I'm also curious what exactly it does. At 140k it isn't replacing very much. Does it just fix files related to booting?
Click to expand...
Click to collapse
It restores your phone back to stock AT&T android via fastboot automatically. It also gives you the option to *fix* your pds partition.
It's also an alternative to RSD
Gutterball said:
I ran this for ****s and giggles and it returns everything back to stock AT&T 2.3 while giving you options along the way of what exactly you wanna restore to stock? webtop, system,pds, wipe data etc. works perfectly! makes life easier really! Phone booted right up after running no problems! Thanks!
Click to expand...
Click to collapse
Thanks for your reply, it assures me that the file isn't screwed up!
What happens if i run this on a non-US retail-EU Atrix?
Nevermind.
Sent from my MB860 using XDA App
hkkla said:
What happens if i run this on a non-US retail-EU Atrix?
Click to expand...
Click to collapse
Anyone has a clue? Is this a complete restore to out of the box-state?
sorry if this is a noob question. but dose this revert ext 4 format back to stock? haven't been keeping up lately and this ext 4 ext 3 stuff is new to me.
It restores it back to stock AT&T. EVERYTHING will be restored to stock.
hkkla said:
What happens if i run this on a non-US retail-EU Atrix?
Click to expand...
Click to collapse
It restores it back to stock AT&T. I tried this on an international Atrix.
Pardon my ignorance, i'm trying to restore a bricked Atrix 4G for a friend. It gave error Failed to boot SVF 105:1:2 0x1000 after bad upgrade. Is it possible to use this as a solution? How can i find that out? and in any case, i have downloaded all files, what's the correct procedure to do this?
Thanks in advance.
Anyone?
Sent from my X10i using XDA App
Barzobius said:
Anyone?
Sent from my X10i using XDA App
Click to expand...
Click to collapse
If its already bricked it can't get much worse using this script. Try it.
Sent from my MB860 using Tapatalk
Phalanx7621 said:
If its already bricked it can't get much worse using this script. Try it.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Well, been trying but haven't been able to do anything with it. I mean I never used it before and seems like it needs to boot into fastboot mode which I haven't been able to do.
Is in any way possible to make the phone boot into that via usb cable with this software? I installed all requiered software including drivers but it never detected the phone in that (bricked) state, not even once. The phone turns a green light when u connect the usb without battery in, thats it.
I haven't found any solution yet, only seen ppl saying to buy a new one. Is this brick really that bad that there's absolutely no solution? And it all seems to be caused by lack of SBK as ive read on the net...
Well if there's any good news I would like to hear them
Sent from my X10i using XDA App
It's a hard brick. I'm sorry, but it cannot be fixed. You can always try a factory cable, but so far, nothing can be done. I feel your pain
Hey guys. I messed up my phone. amature mistakes. I learned my lesson. I was trying to flash a jellybean rom plus the Devil R3 kernel over to a rooted Captivate using CWM. It flashed the Devil kernel over smoothly then when I went to intall the Jellybean rom zip it started to go smoothly then it rebooted in about 5 seconds into the installation and all that came up after 20 min of sitting was the Devil kernel screen. I can get to download mode. I could flash different kernels with odin but then I thought to myself my phone is basically bricked, so I tried that one click unbrick and it also messed up my drivers so now I can't use odin. It worked kind of but didn't change anything. Now I am stuck at the AT&T boot screen. I think the OS was deleted. I can't acesses the SD card. I was stupid and didnt create a CWM backup first. Now all I wanna do is simply go back to a basic 2.3.5 gingerbread and I am never gonna try anthing this dumb again. Please help guys this is my last hope.
edit:
I also wanted to clear up I used the corn kernel to install CWM it worked for the installation of the devil kernel but not the installation of Jellybean OS
Heh, deleting the os? I do it all the time, it means nothing. Have you used heimdall at all? That will mess up your drivers, so make sure you don't try to Odin using the same usb port you did with heimdall.
Sent from a jelly bean
korockinout13 said:
Heh, deleting the os? I do it all the time, it means nothing. Have you used heimdall at all? That will mess up your drivers, so make sure you don't try to Odin using the same usb port you did with heimdall.
Sent from a jelly bean
Click to expand...
Click to collapse
Yeah that one click unbrick used heimdall. I tryed a different usb port it worked I can use odin again. What should I do now?
AllieB said:
Yeah that one click unbrick used heimdall. I tryed a different usb port it worked I can use odin again. What should I do now?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1300843
Go to that thread and then to the second post. Download an Odin one-click for gingerbread kk4 probably with bootloaders unless you've been on gingerbread previously in which case you can go without boot loaders. Using that will take you back to stock gingerbread. Then you can use Odin to flash your corn kernel or devil kernel, which ever one you want and continue on with your flashing fun.
Just an FYI based on your OP what happened during the rom flash is normal. A lot of the Jelly Bean roms out there use different partition layouts and different kernels. So when you start the flashing of the rom the first thing is does it install those two things. So a lot of times when it changes one or both of those it will cause a reboot about 5 seconds in and will get you stuck in a boot loop. Next time you end up stuck on a kernel screen just pull the battery and replace it. Then use the three button combo to boot back into recovery. From there you should be able to flash your rom again and it should work without problem.
Its okay to have the OS 'deleted'. First thing you need to do is go into recovery (red devil options screen). Then go to mounts and storage, connect your phone to different computer if possible and mount your internal SD. Open up a browser on your computer and download another ROM (cm10 is stable). Drag and drop that ROM.zip unto your internal SD and flash it from recovery. Peace amigos.
Its a great relief to have such a giving crowd out there
Thank you guys for all your help! I got a rom flashed over "Helly Bean" Now the only issue I am having is the IMEI is messed up. I don't have any clue what to do now. I have tried following other posts even a video and I'm stuck! Please help!
Once again guys thank you so much cause I'm a far stretch from where I was last night where it was a blank Kernel that wouldn't install a rom.
Update:
A few minutes ago I got service w/o changing anything I got a bunch of texts I tried to make a call and lost service. I rebooted and same problem as it has been. No service and it popped up with the IMEI problem.
AllieB said:
Thank you guys for all your help! I got a rom flashed over "Helly Bean" Now the only issue I am having is the IMEI is messed up. I don't have any clue what to do now. I have tried following other posts even a video and I'm stuck! Please help!
Once again guys thank you so much cause I'm a far stretch from where I was last night where it was a blank Kernel that wouldn't install a rom.
Update:
A few minutes ago I got service w/o changing anything I got a bunch of texts I tried to make a call and lost service. I rebooted and same problem as it has been. No service and it popped up with the IMEI problem.
Click to expand...
Click to collapse
Provided the imei issue happened during the helly bean flash you should have a backup on your internal SD card. Look on your internal SD for a folder labeled backup. If you have that look in there and hopefully you'll have a folder within it labeled efs.
If you have that try downloading an app called nitrality from the play store and use it to restore that copy of your efs folder.
Like I said IF it happened because of the helly bean flash that should fix your problem. If not I don't want to tell you what you'll probably have to do....
Sent from my SGH-I897 using XDA
m1batt1 said:
Provided the imei issue happened during the helly bean flash you should have a backup on your internal SD card. Look on your internal SD for a folder labeled backup. If you have that look in there and hopefully you'll have a folder within it labeled efs.
If you have that try downloading an app called nitrality from the play store and use it to restore that copy of your efs folder.
Like I said IF it happened because of the helly bean flash that should fix your problem. If not I don't want to tell you what you'll probably have to do....
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
Ok I went and downloaded that app. I went into tools. Then selected restore efs. It popped up susscessful. Nothing else happened. What should I do next?
AllieB said:
Ok I went and downloaded that app. I went into tools. Then selected restore efs. It popped up susscessful. Nothing else happened. What should I do next?
Click to expand...
Click to collapse
Reboot then check and see if your imei matches and of you get signal again.
Sent from my SGH-I897 using XDA
m1batt1 said:
Reboot then check and see if your imei matches and of you get signal again.
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
I have rebooted. Nothing has changed. Although this freak thing happens ocasionally. I get service for about 2 minutes then it will go away. It has happened 2 times today once before that efs restore and once after. I blew off the sim card ant that was not it. IK it's not AT&T's tower because before this I would get full signall 24/7.
m1batt1 said:
Reboot then check and see if your imei matches and of you get signal again.
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
I have rebooted. Nothing has changed. Although this freak thing happens ocasionally. I get service for about 2 minutes then it will go away. It has happened 2 times today once before that efs restore and once after. I blew off the sim card ant that was not it. IK it's not AT&T's tower because before this I would get full signall 24/7.
AllieB said:
I have rebooted. Nothing has changed. Although this freak thing happens ocasionally. I get service for about 2 minutes then it will go away. It has happened 2 times today once before that efs restore and once after. I blew off the sim card ant that was not it. IK it's not AT&T's tower because before this I would get full signall 24/7.
Click to expand...
Click to collapse
And you did check that you have a backup?
Sent from my SGH-I897 using XDA
Thanks all you guys btw!
m1batt1 said:
And you did check that you have a backup?
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
Yes I have the backup. It is on the SD card Backup/efs
AllieB said:
Yes I have the backup. It is on the SD card Backup/efs
Click to expand...
Click to collapse
Ok I did some playing and actually went in and deleted my efs folder. I did this because I've personally never had the issue so I wanted to see what I could do to understand it better.
So like you Nitrality didn't do me any good so I apologize for pointing you in that direction.
What did work for me is I went in with a file explorer and simply copied all the files in the backup /efs folder directly into the root /efs folder where they should be. I then rebooted into recovery and fixed permissions. Then rebooted normal and all was good.
Now keep in mind that helly bean was the rom that made that backup for you. So if by some chance in your flashing process, a rom that you flashed prior to helly bean caused the issue then the efs backup you have could be corrupt as well. But for now we'll assume it is good and go from there.
Efs problems are best fixed by going back to stock.
m1batt1 said:
Ok I did some playing and actually went in and deleted my efs folder. I did this because I've personally never had the issue so I wanted to see what I could do to understand it better.
So like you Nitrality didn't do me any good so I apologize for pointing you in that direction.
What did work for me is I went in with a file explorer and simply copied all the files in the backup /efs folder directly into the root /efs folder where they should be. I then rebooted into recovery and fixed permissions. Then rebooted normal and all was good.
Now keep in mind that helly bean was the rom that made that backup for you. So if by some chance in your flashing process, a rom that you flashed prior to helly bean caused the issue then the efs backup you have could be corrupt as well. But for now we'll assume it is good and go from there.
Click to expand...
Click to collapse
I did the copy and paste with the recovery file manager. I then backed out and fixed permissions. rebooted. nothing has changed.
korockinout13 said:
Efs problems are best fixed by going back to stock.
Click to expand...
Click to collapse
AllieB said:
I did the copy and paste with the recovery file manager. I then backed out and fixed permissions. rebooted. nothing has changed.
Click to expand...
Click to collapse
Then I'm afraid to tell you that the only other way I know to get your efs and imei corrected is to flash back to stock again as stated before...
m1batt1 said:
Then I'm afraid to tell you that the only other way I know to get your efs and imei corrected is to flash back to stock again as stated before...
Click to expand...
Click to collapse
Dang I have too try that.
hey guys i tried searching for answers. but had no success. i have a note 3 that was rooted with kingo. AT&T automatically installed an OTA update and of course it un rooted my phone. i still get the custom boot screen as well as still have safestrap on my device. my question is how do i reroot my device? ive tried kingo again and it fails after rebootong the phone 5 or 6 times. im still running 4.3 build is JSS15J.N900AUCUBNB4
i know a little on some things but im not as technical as most of you. but any help would be greatly appreciated.
Survivor058 said:
hey guys i tried searching for answers. but had no success. i have a note 3 that was rooted with kingo. AT&T automatically installed an OTA update and of course it un rooted my phone. i still get the custom boot screen as well as still have safestrap on my device. my question is how do i reroot my device? ive tried kingo again and it fails after rebootong the phone 5 or 6 times. im still running 4.3 build is JSS15J.N900AUCUBNB4
i know a little on some things but im not as technical as most of you. but any help would be greatly appreciated.
Click to expand...
Click to collapse
What version of Kingo did you try? Use 1.1.5 or 1.1.8. People have had success with that. 1.1.8 worked for me. Just Google around and you will find the download on the net somewhere.
theorioles33 said:
What version of Kingo did you try? Use 1.1.5 or 1.1.8. People have had success with that. 1.1.8 worked for me. Just Google around and you will find the download on the net somewhere.
Click to expand...
Click to collapse
it was 1.2.0 ill try an older version
In case you have trouble finding a copy
https://mega.co.nz/#!AxdHUCCQ!86DzctSWlXK4VfbInPYBgC_4QYAM2wUR8cewrflAyk0
theorioles33 said:
In case you have trouble finding a copy
unfortunately that did not work. the root failed. that was version 1.1.5, last night i tried 1.1.8 failed and tried the latest 1.2.0 with no success. would you recommend something else? i did try theese root methods with the sd card inserted im not sure if that is a no no or not
Click to expand...
Click to collapse
I'm at a loss. I had my SD card in by the way. Maybe someone else will have some ideas.
Sent from my SAMSUNG-SM-N900A using Tapatalk
theorioles33 said:
I'm at a loss. I had my SD card in by the way. Maybe someone else will have some ideas.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
that sucks. factory reset? ill most likely still have the issue but maybe not. isnt there a way to completely wipe the phone from the boot screen? id rather not if i dont have to.
You can try a factory reset and then root. If not there is a thread in the general section to go back to stock. Works great. I used it.
Sent from my SAMSUNG-SM-N900A using Tapatalk
theorioles33 said:
You can try a factory reset and then root. If not there is a thread in the general section to go back to stock. Works great. I used it.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
but arent i technically back to stock? since i dont have root access? this is very confusing to me. if my carrier didnt push that update i wouldnt be in this boat
You are but we can't figure out why you can't root when others in your situation can. There is Kingo thread you can check out. Maybe you can find some answers there.
Sent from my SAMSUNG-SM-N900A using Tapatalk
anyone have any suggestions?? 139 views in less than an hour someone has got to know something lol
Survivor058 said:
anyone have any suggestions?? 139 views in less than an hour someone has got to know something lol
Click to expand...
Click to collapse
Factory Reset after the update to NB4, also go to recovery wipe cache, then try the 1.18, during the rooting process, look your phone screen, you need to click accept something twice,
I don't know how it all works terribly well but you said you still have Safestrap? Can you still install ROMs and can they have root?
Also, for when you eventually do get it working again. I recommend freezing the ATT updater. It can be awful when it eventually FORCES an update.
I got a free app called App Quarantine and froze "AT&T Software Update".
coolmingli said:
Factory Reset after the update to NB4, also go to recovery wipe cache, then try the 1.18, during the rooting process, look your phone screen, you need to click accept something twice,
Click to expand...
Click to collapse
ok yea this is all french to me. you want me to factory reset? im not sure what the NB4 is?. and i thing i know how to wipe the cache.
Gary3 said:
I don't know how it all works terribly well but you said you still have Safestrap? Can you still install ROMs and can they have root?
Also, for when you eventually do get it working again. I recommend freezing the ATT updater. It can be awful when it eventually FORCES an update.
I got a free app called App Quarantine and froze "AT&T Software Update".
Click to expand...
Click to collapse
safestrap is on my phone but it cant be removed and just says that the phone isnt properly rooted. so no i cannot install roms and i will make sure that once i resolve this ill freezr that app
sorry for the delay guys im back at this again. i do very much appreciate all who are trying to offer assistance
ok guys so ive wiped the cache. and have done the factory reset. kingo 1.1.5 and 1.1.8 both have failed...... what is going on here maybe someone can skype with me the steps to completely flash my phone to the day i got it i see the thread but im scared ****less to try it lol
You will just have to follow the restore to MJ5 thread. The instructions are simple and very easy to follow. Go slow and follow them to the T.
What they do not mention however is do not use a 3.0 USB port. Only 2.0 will work.
Just follow that.
It is literally impossible to brick this phone to the point of it being unrecoverable. There is a tutorial to restore from hard bricks without J-Tag.
Sent from my SM-N9005A using XDA Premium 4 mobile app
graydiggy said:
You will just have to follow the restore to MJ5 thread. The instructions are simple and very easy to follow. Go slow and follow them to the T.
What they do not mention however is do not use a 3.0 USB port. Only 2.0 will work.
Just follow that.
It is literally impossible to brick this phone to the point of it being unrecoverable. There is a tutorial to restore from hard bricks without J-Tag.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey graydiggy, I did the restore back to MJ5, but can't seem to get the last step for rooting to work. I tried every way with putting the rdlv on internal...unzipped and zipped. I even tried doing the same on the external sd as well. When I reboot supersu doesn't do anything. Any suggestion on how to get the last step to work?
Thanks in advance for your help.
chrispyutec said:
Hey graydiggy, I did the restore back to MJ5, but can't seem to get the last step for rooting to work. I tried every way with putting the rdlv on internal...unzipped and zipped. I even tried doing the same on the external sd as well. When I reboot supersu doesn't do anything. Any suggestion on how to get the last step to work?
Thanks in advance for your help.
Click to expand...
Click to collapse
It has to be unzipped and on the internal. You have to reboot a few times for it to activate. After the first reboot, let the phone sit for a few minutes and then reboot again. You should be good to go after that.
Sent from my SM-N9005A using XDA Premium 4 mobile app
graydiggy said:
It has to be unzipped and on the internal. You have to reboot a few times for it to activate. After the first reboot, let the phone sit for a few minutes and then reboot again. You should be good to go after that.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wow that did the trick!!! Thanks for holding my hand lol. I hit your thanks and I appreciate your help.
I've tried everything in my power to fix my phone and nothing is working. I have unrooted and wiped my phone to the best of my ability.
This is my about phone
This is my download mode
Given this, would I be still covered under my warranty
Click to expand...
Click to collapse
EDIT: I think I fixed my problem by restoring a backup I found
Tattered said:
I've tried everything in my power to fix my phone and nothing is working. I have unrooted and wiped my phone to the best of my ability.
This is my about phone
This is my download mode
Given this, would I be still covered under my warranty
Click to expand...
Click to collapse
Not clear what you have done; would help us here to know what steps you've taken then everyone here may have other suggestions. If it's software related and just requires the appropriate flash you might be able to take it to one of the samsung experience centers in Best Buy or you can try their new hangouts support offering and see what they say.
Or just Odin back to NCE. Just leave out the bootloader file or it will fail.
Sent from my SM-G900A using XDA Premium 4 mobile app
thepktrckt said:
Not clear what you have done; would help us here to know what steps you've taken then everyone here may have other suggestions. If it's software related and just requires the appropriate flash you might be able to take it to one of the samsung experience centers in Best Buy or you can try their new hangouts support offering and see what they say.
Click to expand...
Click to collapse
mcnaught82 said:
Or just Odin back to NCE. Just leave out the bootloader file or it will fail.
Sent from my SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have done a factory restore via system recovery
I have attempted a firmware reset via Odin BUT ODIN DOESN'T WORK http://i.imgur.com/T1gE9Rn.png / http://i.imgur.com/zn4S94a.png.
Tattered said:
I have done a factory restore via system recovery
I have attempted a firmware reset via Odin BUT ODIN DOESN'T WORK http://i.imgur.com/T1gE9Rn.png / http://i.imgur.com/zn4S94a.png.
Click to expand...
Click to collapse
Don't put bootloader in BL space. Then try again.
norbarb said:
Don't put bootloader in BL space. Then try again.
Click to expand...
Click to collapse
See the second image of of Oden where it isn't checked
UPDATE: I FIXED IT ! I found a lost SD card with a backup that I restored and It fixed the problems I was having
I'm just curious. You wasn't using a Mac were you?
I am looking to return my tablet back to stock so I can watch Google movies. I have a wifi t710 tab2s. I have rooted it, installed a custom kernel, recovery, and rom. When I try to flash either one of these stock firmware 5.0.2_T710XXU1AOG5_T710XAR1AOG6_XAR.zip or 5.1.1_T710XXU1BOH7_T710XAR1BOH7_XAR.zip in Odin it fails.
Can someone tell me what I am doing wrong. Thanks in advance.
Never mind. I got it.
droid10 said:
I am looking to return my tablet back to stock so I can watch Google movies. I have a wifi t710 tab2s. I have rooted it, installed a custom kernel, recovery, and rom. When I try to flash either one of these stock firmware 5.0.2_T710XXU1AOG5_T710XAR1AOG6_XAR.zip or 5.1.1_T710XXU1BOH7_T710XAR1BOH7_XAR.zip in Odin it fails.
Can someone tell me what I am doing wrong. Thanks in advance.
Never mind. I got it.
Click to expand...
Click to collapse
How did you fix this??? What error were you getting?I'm in same situation. Plz
Sent from my SM-G928T using Tapatalk
neoflasher said:
How did you fix this??? What error were you getting?I'm in same situation. Plz
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
It's a tad annoying when people do that and don't explain how they fixed it so I'll try and elaborate on his behalf. :banghead:
Basically it seems he was attempting to flash the zips in Odin. Odin requires tar or md5 files. I'm guessing he realised he had to extract the tar from the zip file first then flash.
I hope it was something else cause I have extracted the zips
Sent from my SM-G928T using Tapatalk
neoflasher said:
How did you fix this??? What error were you getting?I'm in same situation. Plz
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
I'm not sure if you received my PM. Are you able to boot into download mode?
ashyx said:
It's a tad annoying when people do that and don't explain how they fixed it so I'll try and elaborate on his behalf. :banghead:
Basically it seems he was attempting to flash the zips in Odin. Odin requires tar or md5 files. I'm guessing he realised he had to extract the tar from the zip file first then flash.
Click to expand...
Click to collapse
Yea, I should of explained how I did it. Unfortunately, I don't remember exactly how I did it. I believe I ended up using Samsung Smart Switch or Samsung Kies 3 to return it back to stock. There is an Emergency phone recovery option in both programs that will restore your device back to stock.
When I plug it into smart switch it says not recognized.
Sent from my SM-G928T using Tapatalk
Just got home and flashed no problem. Thanks
Sent from my SM-G928T using Tapatalk