Hi,
I had a S3 and used Kies to do backups and restores.
Really had no problems with it, it actually worked!!!
Ok, now I have a S4 and after setting everything up
just the way I want it i tried to do a backup. For some
reason it always hangs up on one of the backup
categories. I tried unchecking a few and it still hangs
on one. I finally only did about 5 or 6 things and it went through.
Got me baffled on this, any ideas??????
Thanks, Ken
kenfb1 said:
Hi,
I had a S3 and used Kies to do backups and restores.
Really had no problems with it, it actually worked!!!
Ok, now I have a S4 and after setting everything up
just the way I want it i tried to do a backup. For some
reason it always hangs up on one of the backup
categories. I tried unchecking a few and it still hangs
on one. I finally only did about 5 or 6 things and it went through.
Got me baffled on this, any ideas??????
Thanks, Ken
Click to expand...
Click to collapse
Have you read the "pinned" threads in the General section yet?
You never said what your firmware was or what your carrier is, but if it is AT&T and has MF3 firmware, KIES will not work for you at this time. You should do a lot of researching , reading, and learning, before you end up with a hard brick. Good luck.
Hi
scott14719 said:
Have you read the "pinned" threads in the General section yet?
You never said what your firmware was or what your carrier is, but if it is AT&T and has MF3 firmware, KIES will not work for you at this time. You should do a lot of researching , reading, and learning, before you end up with a hard brick. Good luck.
Click to expand...
Click to collapse
Hi,
And thanks. I searched for Kies and problems and not much related.
Just got the phone, 4.2.2 out of box. I will read the thread,
Thanks Again,
Ken
Related
After installing CWM recovery, kernel, root, and CM7 on a Vzw Tab, is it possible to fully restore it back to stock so that Samsung will honor the warranty?
Friend of mine's Tab is having some screen issues and the warranty expires in about two weeks.
Is it possible or is he SOL?
Thanks
Ahhk said:
After installing CWM recovery, kernel, root, and CM7 on a Vzw Tab, is it possible to fully restore it back to stock so that Samsung will honor the warranty?
Friend of mine's Tab is having some screen issues and the warranty expires in about two weeks.
Is it possible or is he SOL?
Thanks
Click to expand...
Click to collapse
Yes he can. There is a stock ROM EC02 that is flashable using a program called Heimdall. It takes you back so Verizon would never know.
Go here:
http://forum.xda-developers.com/showthread.php?p=11601647
leapinlar said:
Yes he can. There is a stock ROM EC02 that is flashable using a program called Heimdall. It takes you back so Verizon would never know.
Go here:
http://forum.xda-developers.com/showthread.php?p=11601647
Click to expand...
Click to collapse
Sweet! Thank you much.
I saw some posts about stock ROMs floating around, but wasn't sure that the kernel, recovery, and EXT4 could all be restored back to stock.
leapinlar said:
Yes he can. There is a stock ROM EC02 that is flashable using a program called Heimdall. It takes you back so Verizon would never know.
Go here:
http://forum.xda-developers.com/showthread.php?p=11601647
Click to expand...
Click to collapse
I have an AT&T Galaxy Tab and that link doesn't work for me. I've tried everything I possibly could to try to get this thing back to something I can use that doesn't reboot when I try to use the keyboard. I've done search after search and it never provides me with any information that's helpful to getting it back to a workable condition. I've come across the link above numerous times and I've tried to use those instructions over and over with no success.
I really think it's worth pointing out that constantly pointing people to these directions isn't helpful to those trying to restore a non-Verizon Tab. It's done zero good to me with my AT&T Tab.
GreNME said:
I have an AT&T Galaxy Tab and that link doesn't work for me. I've tried everything I possibly could to try to get this thing back to something I can use that doesn't reboot when I try to use the keyboard. I've done search after search and it never provides me with any information that's helpful to getting it back to a workable condition. I've come across the link above numerous times and I've tried to use those instructions over and over with no success.
I really think it's worth pointing out that constantly pointing people to these directions isn't helpful to those trying to restore a non-Verizon Tab. It's done zero good to me with my AT&T Tab.
Click to expand...
Click to collapse
But I clearly asked about a Verizon Tab and he replied with Verizon Tab-related info. That's a helpful thing.
On the other issue, the last thing you want to do with an AT&T Tab is try and use CDMA (Verizon/Sprint) ROMs. This is probably why your Tab is screwed.
Stick to GSM/ATT ROMs and you'll probably have better luck.
I've tried to find AT&T ROMs and none have worked so far.
Every time I search on this subject here I get sent to the Verizon fix.
I had the same problem, for some reason the older versions of Android that was posted on here haven't worked for me. Pretty much all the links provided in the instruction posts on turning the tab into a phone had Froyo 2.2 links. However I downloaded the Gingerbread rom 2.3.3 and flashed it and it works now:
thegalaxytabforum.com/index.php?/topic/112-samsung-galaxy-tab-firmware-list
Don't forget to reflash the radio you want.
Hello everyone!
Is it possible to use the Market, after making the ROOT?
thank you
P.S i want to by the Samsung Galaxy Tab 10.1 can i recover the Original Rom with HEIMDALL suit?
Yea you can still use market after you root.
Sent from my PC36100 using XDA App
Thanks Dmaxx67
So... I did the stupid thing. I attempted to go back to my old MF9 backup through TWRP after upgrading to MJA, and now my wifi won't even turn on. I've been trying to figure this out for a few hours now, trying various fixes. I've tried to use ODIN to flash back to complete stock, but that just destroys my phone until I flash a recovery through ODIN. Everything I've seen on the forums so far has made it seem as though there is no hope since Samsung added in Knox.
I'm sorry if this has been resolved elsewhere, but I've literally been searching the General. Q&A, Android Development, Original Android Development, and Developer forums for several hours today with no luck. Can someone please help me with this? I just want my phone to be fully functional again...
EDIT:
Here's the deal; my main problem was with Wifi not working. The Stock MF9 Kernel was not working, but the 4.2.2 TW Kernel found here finally did.
did you try this?
leaderbuilder said:
did you try this?
Click to expand...
Click to collapse
Yes. Nothing changed when I did that. I suppose that I should call out that I am currently on MF9.
dante042 said:
So... I did the stupid thing. I attempted to go back to my old MF9 backup through TWRP after upgrading to MJA, and now my wifi won't even turn on. I've been trying to figure this out for a few hours now, trying various fixes. I've tried to use ODIN to flash back to complete stock, but that just destroys my phone until I flash a recovery through ODIN. Everything I've seen on the forums so far has made it seem as though there is no hope since Samsung added in Knox.
I'm sorry if this has been resolved elsewhere, but I've literally been searching the General. Q&A, Android Development, Original Android Development, and Developer forums for several hours today with no luck. Can someone please help me with this? I just want my phone to be fully functional again...
Click to expand...
Click to collapse
i just gave up on trying to do a restore. I actually used Titanium to get as much information from my old backup as possible then just rolled with it. I know that probably isn't what you wanted to hear but that what worked for me.. hope that helps
I have read that the WiFi issue may be a Kernel issue.. Did you try a different TouchWiz kernel and see if it worked out?
Sent from my SPH-L720 using XDA Premium 4 mobile app
lmayes69 said:
i just gave up on trying to do a restore. I actually used Titanium to get as much information from my old backup as possible then just rolled with it. I know that probably isn't what you wanted to hear but that what worked for me.. hope that helps
Click to expand...
Click to collapse
This is actually what I was trying to do, sadly. Titanium was backing up my info to the phone storage rather than the SD card, and I had to do a data wipe to get to MJA, so I lost them. I figured I could restore to my MF9 backup to redo them, and that's when the trouble started.
I finally got it working. I had to try several different kernels until one finally worked. Now about flashing a new ROM...
rosa styhome
dante042 said:
I finally got it working. I had to try several different kernels until one finally worked. Now about flashing a new ROM...
Click to expand...
Click to collapse
What kernel did you use and how did you install it? I'm having a similar issue and can't find a fix.
Scott02 said:
What kernel did you use and how did you install it? I'm having a similar issue and can't find a fix.
Click to expand...
Click to collapse
Scott, check my first post. I edited it with a link to the page with the kernel I used. Make sure that you choose the correct kernel for your Android version. The MF9 and MJA designators have nothing to do with which kernel you need, so make sure to check in your "aboout phone" section to find out what android version you're running. Using the 4.3 kernel on 4.2.2 will cause a bootloop, which is easily fixed by flashing the correct kernel.
Hey guys, I don't post here often, but I'm not new to this. It was through this forum that I first started rooting with mfy s3.
I just got a note 3 through Sprint. I've gotten used to getting off the grid, so I immediately jumped to root it. I decided on Jellybomb after reading some reviews. Then I downloaded everything necessary to make the jump: Odin, 1.85 and 3.09, jellybomb, cwm 6.0, twrp 7, auto-root, and the original roms in case I had to hop back.
First I went with Chainfires auto-root. I didn't seem to have any problem flashing that. The problem came with flashing twrp and the new rom. I can't remember which one was giving me trouble (I've been fighting it almost a week now). Somehow some way the phone has been stuck in an autoboot that says "seandroid not enforcing" and either "warranty bit: recovery" or "warranty bit: kernel". I tried new kernels. I tried things in different order. I can get into recovery but only after going immediately after autoroot. Even there you have a broken android.
Please help. I've been without a phone for a week.
KoolCharisma said:
Hey guys, I don't post here often, but I'm not new to this. It was through this forum that I first started rooting with mfy s3.
I just got a note 3 through Sprint. I've gotten used to getting off the grid, so I immediately jumped to root it. I decided on Jellybomb after reading some reviews. Then I downloaded everything necessary to make the jump: Odin, 1.85 and 3.09, jellybomb, cwm 6.0, twrp 7, auto-root, and the original roms in case I had to hop back.
First I went with Chainfires auto-root. I didn't seem to have any problem flashing that. The problem came with flashing twrp and the new rom. I can't remember which one was giving me trouble (I've been fighting it almost a week now). Somehow some way the phone has been stuck in an autoboot that says "seandroid not enforcing" and either "warranty bit: recovery" or "warranty bit: kernel". I tried new kernels. I tried things in different order. I can get into recovery but only after going immediately after autoroot. Even there you have a broken android.
Please help. I've been without a phone for a week.
Click to expand...
Click to collapse
This one is the International Note 3 forum.
You should ask for actual details in the specific Sprint Note 3 forum:
http://forum.xda-developers.com/note-3-sprint
You should also pay more attention to the fact that the questions should be posted in the Q&A subforum.
Thanks
xclub_101 said:
This one is the International Note 3 forum.
You should ask for actual details in the specific Sprint Note 3 forum:
http://forum.xda-developers.com/note-3-sprint
You should also pay more attention to the fact that the questions should be posted in the Q&A subforum.
Click to expand...
Click to collapse
Cheers! It looks from your sig though that you have found a work around on your international version. Are they really that different, that need entirely separate instructions. Obviously I downloaded all of the suggested software for Sprint and followed Sprint suggested, but I'm frustrated because I simply don't understand how I could do something the same way everyone else did and yet have it fail on me like this.
I am having the exact same problem...at first i was able to flash 'openrecovery-twrp-2.6.3.0-hltetmo.img.tar and it would boot my phone back to normal. I have now run into this problem again and my first original fix isn't working anymore. If I can figure out a way I will definitely let you know!
Getting Answers
Anonymous777 said:
I am having the exact same problem...at first i was able to flash 'openrecovery-twrp-2.6.3.0-hltetmo.img.tar and it would boot my phone back to normal. I have now run into this problem again and my first original fix isn't working anymore. If I can figure out a way I will definitely let you know!
Click to expand...
Click to collapse
Hey man, thanks for reaching out. I realized I should probably have been in the Sprint form so I created a new thread there and I've been getting some help!
If you want: shoot over there and see if the tips can help you: http://forum.xda-developers.com/showthread.php?p=51096673
Anonymous777 said:
I am having the exact same problem...at first i was able to flash 'openrecovery-twrp-2.6.3.0-hltetmo.img.tar and it would boot my phone back to normal. I have now run into this problem again and my first original fix isn't working anymore. If I can figure out a way I will definitely let you know!
Click to expand...
Click to collapse
Hey man we've made a lot of headway at the above thread Thanks to Macmars. You should check it out and see if we can help each other.
Sent from my SM-N900P using xda app-developers app
KoolCharisma said:
Hey man we've made a lot of headway at the above thread Thanks to Macmars. You should check it out and see if we can help each other.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
I figured out what to do, use odin 3.9 and flash this, it took about 15 minutes to go through the whole process. Once my phone boot up it froze at the T-Moble logo or whatever, so I waited like 20 minutes and then powered it off, went into recovery and did a factory reset which then solved all my problems. I lost root, but no big deal to me. Better than buying a new phone!!! Btw the only place I could find this file is off sammobile.com. You have to sign up for a free membership thing but at least they give you the stock firmware.
TMB-N900TUVUCNB4-20140305155920/N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5
KoolCharisma said:
Hey man we've made a lot of headway at the above thread Thanks to Macmars. You should check it out and see if we can help each other.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Right on man!
Sent from my SM-N900P using xda app-developers app
So I had a stock 4.2.2 rom on my phone, I eventually rooted it with QBking's method and also used his wifi. Recently I was having issues so decided to unroot my phone. If I need the links I'll pull them up but the rom used was L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5.
I checked the md5 and everything was fine. So I booted up odin everything was smooth then I noticed the bar wasn't moving so I left it for awhile came back about 20 minutes later it still was in the same spot so left it again and still same thing. So in the end now it just fails everytime I try to odin the tar. Not sure what to do from here but can't do anything. Yes I know search is my friend but I've looked through about 50+ threads and I'm still clueless usually I have no issues following this stuff. Any help is appreciated.
So...
you didn't read, search or look through the forums as much or well though.
If you had 4.4 on you're phone you'd have found out that you CANNOT go 'back' to a version before your current firmware version you show you used MDC - that is WAY before kitkat/NAE. There are dozens of posts about this. I know I've personally responded to many of them.
Do some more reading and searching look for the NAE .tar and PC Oding that. You will get back to 'zero' - stock unrooted. Then read a whole lot more and you'll find this is a great device.
leaderbuilder said:
So...
you didn't read, search or look through the forums as much or well though.
If you had 4.4 on you're phone you'd have found out that you CANNOT go 'back' to a version before your current firmware version you show you used MDC - that is WAY before kitkat/NAE. There are dozens of posts about this. I know I've personally responded to many of them.
Do some more reading and searching look for the NAE .tar and PC Oding that. You will get back to 'zero' - stock unrooted. Then read a whole lot more and you'll find this is a great device.
Click to expand...
Click to collapse
If you READ the above I didn't have 4.4 I had 4.2.2, I haven't updated my phone in quite sometime because what I had was functioning well for me until recently , I had some issues and need the phone replaced. Anyways since I apparently didn't read at all /sarcasm I tried on a different pc and got it to actually odin back to stock 4.2.2 no root. I appreciate your comment though uncalled for, anyways thanks for your time.
Applogize for the mis-read of 4.2 vs 4.4. My bad.
But my sarcasm does stand.
The 'different PC/different port fix/suggestion has been suggested many, many, many times.
My ire is not directed at you personaly, but the throngs of folks who dont look and won't respond back to the forums on how/if they fix their problem so that other can learn.
Fantastic that you got it working and thank you for posting back! Most don't seem to when they get it working, thus not contributing to the groupp knowledge.
Good luck on new phone.
You should always post the links if you're looking for help so we can help better.
I updated 4.4.4 NI2 on my Galaxy S5 and gained root access. Everything seem to be ok, but there is lag when I am typing a email, listening to music or watch a video. Battery life is definitely worst than before, for the first night it can't be fully charge after 5 hours plugged in with the phone ON. It seems like there is something running in the background to cause this.
Please help. I am not very technical, so if there is any further information you need to help with this, please let me know where to get and I'll update the post.
flyaway718 said:
help please!!!!!!!!!!!
Click to expand...
Click to collapse
Try backup and reset in the settings menu and then flash the NI2 full tar and do the reroot process again. I had the same problem on the NHA update but it went away after I did that.
Please read forum rules before posting
Questions, Help and Troubleshooting belong in the Q&A, Help and Troubleshooting sections
You may ask your question once after searching and then only bump your question once after 24 hours has passed with no reply
Thread moved to Q&A
Thanks
FNSM
Misterxtc said:
Try backup and reset in the settings menu and then flash the NI2 full tar and do the reroot process again. I had the same problem on the NHA update but it went away after I did that.
Click to expand...
Click to collapse
I tried that, but the problem still exist. It look like the phone is constantly trying to communicate with the cell network. It's extremely worst when reception is not great.
flyaway718 said:
I tried that, but the problem still exist. It look like the phone is constantly trying to communicate with the cell network. It's extremely worst when reception is not great.
Click to expand...
Click to collapse
You could try flashing one of the older modems from here in download mode and Odin to see if that helps. Personaly the signal strength has been good if not better for me. I was getting alot of laggy behavior. A weak signal will definetly drain your battery because the phone works alot harder trying to find it.
Flashing an old firmware worked for me..
Appreciated..