Hi, i'm new to rooting and flashing. I recently rooted my phone using odin, and flashed a custom rom. I thought I did a backup of my original hardware but can't seem to get back to it. When using the custom rom, everything works except for sound or any apps that require sound, that includes the phone dialer so I can't recieve or make calls. I tried flashing new roms, I even unrooted and installed the stock s4 bell canada rom.
When the phone reboots, it'll say kernel is not seandroid enforcing, and from what I understand, that means that maybe my phone is still rooted??
Currently, i'm back to my stock s4 rom, but sound and phone still doesn't work. Please if anyone has any info on this it would be greatly appreciated.
Thanks
rhabib2008 said:
Hi, i'm new to rooting and flashing. I recently rooted my phone using odin, and flashed a custom rom. I thought I did a backup of my original hardware but can't seem to get back to it. When using the custom rom, everything works except for sound or any apps that require sound, that includes the phone dialer so I can't recieve or make calls. I tried flashing new roms, I even unrooted and installed the stock s4 bell canada rom.
When the phone reboots, it'll say kernel is not seandroid enforcing, and from what I understand, that means that maybe my phone is still rooted??
Currently, i'm back to my stock s4 rom, but sound and phone still doesn't work. Please if anyone has any info on this it would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
Having the same problem. Did you ever get it figured out?
Hey, yup I did. U basically started from scratch. Downloaded proper Rom files and rerooted cleared cache etc, and re flashed. Then for some reason everything worked. There's the link in s4 Canadian forum with title along the lines of 'all in one' follow that. If u have trouble finding it, lemme know, I'll try and get it for u
HI did you have the link of the site? I also have the problem :/
rhabib2008 said:
Hey, yup I did. U basically started from scratch. Downloaded proper Rom files and rerooted cleared cache etc, and re flashed. Then for some reason everything worked. There's the link in s4 Canadian forum with title along the lines of 'all in one' follow that. If u have trouble finding it, lemme know, I'll try and get it for u
Click to expand...
Click to collapse
Link
http://forum.xda-developers.com/showthread.php?t=2314494
Related
Hi!
I have a problem with Galaxy Ace messaging.
First custom ROM on my Galaxy Ace was ICS CM9 beta 8 ROM. Before installing it I did all the things in first sticky thread about how to install custom ROM.
When I installed that CM9 ROM messaging was not working - like, I couldn't normally open that program. It just froze when I tried to do something with messages and showed that Messaging couldn't be launched. That was not the simple program freeze when there is choice to Force quit, but that was different.
I thought that is because of ROM, that was still beta version.
Today I tried different ROM, CM7 Miracle edition. But again the same problem.
I think it is, maybe, because of wrong firmware or something.
Please, needed help.
Thank You in advance,
Daniels
Is it the "real" Galaxy Ace? Without any "i" or "m" etc at the end? Are you able to call?
Try Wipe Data, Dalvik Cache and Cache again + reflashing!
Or do a clean flash with ODIN, but I don't know if that makes sense...
Novastylez said:
Is it the "real" Galaxy Ace? Without any "i" or "m" etc at the end? Are you able to call?
Try Wipe Data, Dalvik Cache and Cache again + reflashing!
Or do a clean flash with ODIN, but I don't know if that makes sense...
Click to expand...
Click to collapse
Real one, just Samsung Galaxy Ace.
After installing the last one, I tried wiping data and re-installing the same ROM.
How can I do a clean flash with ODIN? ODIN was for firmware not ROM, yes?
I meant with "clean flash" original firmware by Samsung. I don't know exactly how important the baseband is, but MAYBE you "destroyed" something and flashing with ODIN can repair it... Read the TUT's about flashing in the first post's of the development section!
Are you able to do calls?
Novastylez said:
I meant with "clean flash" original firmware by Samsung. I don't know exactly how important the baseband is, but MAYBE you "destroyed" something and flashing with ODIN can repair it... Read the TUT's about flashing in the first post's of the development section!
Are you able to do calls?
Click to expand...
Click to collapse
I am able to make calls.
Ok I will try. Thanks
Not working anything.
Tried with ODIN, tried re-installing ROM, tried other firmware...
No success..
Someone could help, please?
What version of CWM did u use?
what.....? I'm just saying ...didnt hurt much
it happened something similar to me, i was messing with sispem apps and deleted some and i destroyed the original firmware you just need to google the original firmware for ur model (L,B,etc...), charge it in odin and u'll get a nice new firmware to mess with ( i recommend u to keep it somewhere, chances are u need it again)
and be shure you're getting the rom for your model because it does metter
this is a tutorial on how to flash stock rom using odin:
http://yagyagaire.blogspot.com/2012/01/how-to-flash-official-stock-firmwares.html
Hope i helped
Thank You all for helping.
Today I tried simple thing - I installed messaging program, that I downloaded from market and everything is working now.
So, I dont know how or why, but these ROMs didn't have messaging program included.
xfr33 said:
Hi!
I have a problem with Galaxy Ace messaging.
First custom ROM on my Galaxy Ace was ICS CM9 beta 8 ROM. Before installing it I did all the things in first sticky thread about how to install custom ROM.
When I installed that CM9 ROM messaging was not working - like, I couldn't normally open that program. It just froze when I tried to do something with messages and showed that Messaging couldn't be launched. That was not the simple program freeze when there is choice to Force quit, but that was different.
I thought that is because of ROM, that was still beta version.
Today I tried different ROM, CM7 Miracle edition. But again the same problem.
I think it is, maybe, because of wrong firmware or something.
Please, needed help.
Thank You in advance,
Daniels
Click to expand...
Click to collapse
Many devs like to keep their ROM lite..so they dont attach many system files which also benefit us as we can customize it as we like...
So u just need to check whether mms.apk file is there in your /system/app folder
if it isnt there then u just have to get it from somewhere and paste it over there using any root file explorer (best one is ES file explorer)
And bingo! Everything will work perfectly
-------------------------------
Hit THANKS if i helped
ok so i wouldnt say im a noob but im not as advanced as some of yous. last night i flashed a leaked ics onto my phone and loved it with one exception. i couldnt figure out how to root it. all my apps are backed up on titanium backup and i didnt want to have to get all of them manually. so i flashed back to stock using odin with a file i used back when that crappy update came out. i rooted it with super one click and and then went to put on a prerooted ics... when in recovery mode now i get this message
cant access to '/system/csc/att/system/'
i try putting on cwm and siyah and i keep getting authentication errors and the installation aborts. also recovery mode wont read my external sd card now. when the phone is booted up it works fine except i tried to do the factory ota update and it keeps failing. i tried reflashing back to stock again and did the update unrooted and it still failed.
i know you guys hate hate when people ask without researching so i did SOME forum browsing and found nothing. sorry i dont really have time to look too extensively. i just want to know how to fix it. i appreciate any help i can get
Joeyjr25 said:
ok so i wouldnt say im a noob but im not as advanced as some of yous. last night i flashed a leaked ics onto my phone and loved it with one exception. i couldnt figure out how to root it. all my apps are backed up on titanium backup and i didnt want to have to get all of them manually. so i flashed back to stock using odin with a file i used back when that crappy update came out. i rooted it with super one click and and then went to put on a prerooted ics... when in recovery mode now i get this message
cant access to '/system/csc/att/system/'
i try putting on cwm and siyah and i keep getting authentication errors and the installation aborts. also recovery mode wont read my external sd card now. when the phone is booted up it works fine except i tried to do the factory ota update and it keeps failing. i tried reflashing back to stock again and did the update unrooted and it still failed.
i know you guys hate hate when people ask without researching so i did SOME forum browsing and found nothing. sorry i dont really have time to look too extensively. i just want to know how to fix it. i appreciate any help i can get
Click to expand...
Click to collapse
Start with getting back to stock using this guide. Check for ICS bootloaders too, you probably flashed them and you have to get stock ones back (careful, flashing bootloaders can cause hardbricking). Once you're back to stock and rooted, you shouldn't need to ever use PC Odin again.
Then use this guide for rooting/flashing.
One other note: when you tried to install CWM, it sounds like you loaded an update.zip onto your phone then tried to install it using stock recovery. Stock recovery won't let you install unsigned update.zips, which is why that method for getting CWM on your phone will never work (hence the authentication error and installation abort). For our phone, CWM is only included in custom kernels, that's the only way to get it on there, and don't even think about updating or changing it via other means. Just flash a custom kernel, it'll include CWM, use it until you want to switch kernels.
Hit my thanks button, I was really nice this time. And post in Q/A next time as well.
EDIT: Skip the second guide if all you want is stock. You should be able to update OTA after following the first guide. Though even if stock is what you want, I highly recommend flashing a custom GB kernel because a) they're more stable and faster and b) you'll have CWM in case you need it.
You started off mentioning about "leak ics" which I have absolutely zero experience.
My suggestion:
1. Try to get it back to stock. Make sure it works correctly.
2. If hasn't rooted yet, do so.
3. Getting CMW into the device by flashing custom kernel.
4. From there, install any ICS ROM you want.
I have a Galaxy S4 from AT&T. I got it a few months ago, rooted it a few weeks after I got it. Randomly about a week ago, when I would make or receive a phone call, I could not hear the phone ringing, couldn't hear the person talking and they couldn't hear me. The only two ways I found it would work is if I booted into safe mode or I was connected to my cars bluetooth. I have no idea what caused it and I haven't messed with anything (like installing apps or changing settings) anywhere around the time it happened. I did many factory resets and hard key resets but nothing fixed it. I saw I had an OTA update so I did that (which I now realize was a big no-no -_-).
Since I did the OTA update while still rooted, that seems to have messed up my root. I seem to be both rooted and not rooted. So in trying to fix my first problem, I created the second problem. To solve both of these, I've been trying to install a fresh stock ROM onto the phone (to nothing but failure). I was trying to remove the root and put it back to stock incase I had to send it in for repairs. I found a few guides/posts from other people who did the OTA update while rooted but I couldn't seem to get it to work. It mostly consisted of re-rooting the phone, then un-rooting it but I could never get the phone to actually show that it was rooted.
(I just tested the phone part of my phone to see if it was working. Called it, and I could hear and be heard fine. Hung up, waited a few minutes and tried again and it didnt work at all. Both times were while it has been turned on for several minutes).
Does anyone know how I can get back to as close to stock as I can get so I can at least get the actual calling part of my phone fixed? Either see if something to do with the rooting is causing the problem or at least let me send it in to get it fixed, then I'll re-root it later.
Phone: AT&T Galaxy S4
Baseband: I337UCUAMF3 <I know the MF3 isn't good for rooting now
Model: Samsung SGH-I337
Android version: 4.2.2
Device Status: Custom
Thanks for any help!
Update: Managed to get rooted again, using this method: http://forum.xda-developers.com/showthread.php?t=2387577. Calling still doesn't work, and (forgot to mention this before) oddly, if I push numbers on the number pad on my phone, you can hear the tones on the phone I'm connected to. Just can't hear me.
steven2k7 said:
I have a Galaxy S4 from AT&T. I got it a few months ago, rooted it a few weeks after I got it. Randomly about a week ago, when I would make or receive a phone call, I could not hear the phone ringing, couldn't hear the person talking and they couldn't hear me. The only two ways I found it would work is if I booted into safe mode or I was connected to my cars bluetooth. I have no idea what caused it and I haven't messed with anything (like installing apps or changing settings) anywhere around the time it happened. I did many factory resets and hard key resets but nothing fixed it. I saw I had an OTA update so I did that (which I now realize was a big no-no -_-).
Since I did the OTA update while still rooted, that seems to have messed up my root. I seem to be both rooted and not rooted. So in trying to fix my first problem, I created the second problem. To solve both of these, I've been trying to install a fresh stock ROM onto the phone (to nothing but failure). I was trying to remove the root and put it back to stock incase I had to send it in for repairs. I found a few guides/posts from other people who did the OTA update while rooted but I couldn't seem to get it to work. It mostly consisted of re-rooting the phone, then un-rooting it but I could never get the phone to actually show that it was rooted.
(I just tested the phone part of my phone to see if it was working. Called it, and I could hear and be heard fine. Hung up, waited a few minutes and tried again and it didnt work at all. Both times were while it has been turned on for several minutes).
Does anyone know how I can get back to as close to stock as I can get so I can at least get the actual calling part of my phone fixed? Either see if something to do with the rooting is causing the problem or at least let me send it in to get it fixed, then I'll re-root it later.
Phone: AT&T Galaxy S4
Baseband: I337UCUAMF3 <I know the MF3 isn't good for rooting now
Model: Samsung SGH-I337
Android version: 4.2.2
Device Status: Custom
Thanks for any help!
Update: Managed to get rooted again, using this method: http://forum.xda-developers.com/showthread.php?t=2387577. Calling still doesn't work, and (forgot to mention this before) oddly, if I push numbers on the number pad on my phone, you can hear the tones on the phone I'm connected to. Just can't hear me.
Click to expand...
Click to collapse
bro best solution for yu is to FLASH THE STOCK FIRMWARE THROUGH ODIN AND DEN ROOT UR DEVICE..
IT WILL SOLVE UR PHONE CALL PROBLEMS TOO
siva aggzz said:
bro best solution for yu is to FLASH THE STOCK FIRMWARE THROUGH ODIN AND DEN ROOT UR DEVICE..
IT WILL SOLVE UR PHONE CALL PROBLEMS TOO
Click to expand...
Click to collapse
I've been trying to flash the stock firmware, or at least I think its the stock firmware I need for it. Odin keeps giving me an "aboot" then "fail" errors as soon as I start the flashing process. Since I upgraded the software, is it even possible to install an older version of it back on?
steven2k7 said:
I've been trying to flash the stock firmware, or at least I think its the stock firmware I need for it. Odin keeps giving me an "aboot" then "fail" errors as soon as I start the flashing process. Since I upgraded the software, is it even possible to install an older version of it back on?
Click to expand...
Click to collapse
yup...if yu have nandroid backup den restore it with cwm/twrp... and if not
den flashing stock firmware is the only solution for yu to solve ur problem
siva aggzz said:
yup...if yu have nandroid backup den restore it with cwm/twrp... and if not
den flashing stock firmware is the only solution for yu to solve ur problem
Click to expand...
Click to collapse
Will I be able to flash the stock firmware after doing the OTA update? My baseband version is I337UCUAMF3 and the only ROM versions I can find are I337UCUAMDL and I337UCUAMDB.
steven2k7 said:
will i be able to flash the stock firmware after doing the ota update? My baseband version is i337ucuamf3 and the only rom versions i can find are i337ucuamdl and i337ucuamdb.
Click to expand...
Click to collapse
yup yu can ...stock rom can b flshed at any tym yu want except wen the mobile has hard bricked
hit thanks rather then typing bro
siva aggzz said:
yup yu can ...stock rom can b flshed at any tym yu want except wen the mobile has hard bricked
hit thanks rather then typing bro
Click to expand...
Click to collapse
Is there a version or a download you recommend I use? I have I337UCUAMDB that is a .tar.md5 file, but when I use Odin to flash it, it gives an Aboot warning then fail about 2 seconds after I start it. How can I fix that? Do I need to be rooted or not before I flash an update, or does it matter?
steven2k7 said:
I have a Galaxy S4 from AT&T. I got it a few months ago, rooted it a few weeks after I got it. Randomly about a week ago, when I would make or receive a phone call, I could not hear the phone ringing, couldn't hear the person talking and they couldn't hear me. The only two ways I found it would work is if I booted into safe mode or I was connected to my cars bluetooth. I have no idea what caused it and I haven't messed with anything (like installing apps or changing settings) anywhere around the time it happened. I did many factory resets and hard key resets but nothing fixed it. I saw I had an OTA update so I did that (which I now realize was a big no-no -_-).
Since I did the OTA update while still rooted, that seems to have messed up my root. I seem to be both rooted and not rooted. So in trying to fix my first problem, I created the second problem. To solve both of these, I've been trying to install a fresh stock ROM onto the phone (to nothing but failure). I was trying to remove the root and put it back to stock incase I had to send it in for repairs. I found a few guides/posts from other people who did the OTA update while rooted but I couldn't seem to get it to work. It mostly consisted of re-rooting the phone, then un-rooting it but I could never get the phone to actually show that it was rooted.
(I just tested the phone part of my phone to see if it was working. Called it, and I could hear and be heard fine. Hung up, waited a few minutes and tried again and it didnt work at all. Both times were while it has been turned on for several minutes).
Does anyone know how I can get back to as close to stock as I can get so I can at least get the actual calling part of my phone fixed? Either see if something to do with the rooting is causing the problem or at least let me send it in to get it fixed, then I'll re-root it later.
Phone: AT&T Galaxy S4
Baseband: I337UCUAMF3 <I know the MF3 isn't good for rooting now
Model: Samsung SGH-I337
Android version: 4.2.2
Device Status: Custom
Thanks for any help!
Update: Managed to get rooted again, using this method: http://forum.xda-developers.com/showthread.php?t=2387577. Calling still doesn't work, and (forgot to mention this before) oddly, if I push numbers on the number pad on my phone, you can hear the tones on the phone I'm connected to. Just can't hear me.
Click to expand...
Click to collapse
No u dnt need to b rooted bro for flashing stock rom...
siva aggzz said:
No u dnt need to b rooted bro for flashing stock rom...
Click to expand...
Click to collapse
I can't get the stock roms to flash. I've tried I337UCUAMDB and I337UCUAMDL, used different USB ports and different computers and they all fail right away. Do you know where I can find a I337UCUAMF3 rom?
steven2k7 said:
I can't get the stock roms to flash. I've tried I337UCUAMDB and I337UCUAMDL, used different USB ports and different computers and they all fail right away. Do you know where I can find a I337UCUAMF3 rom?
Click to expand...
Click to collapse
Did you Tried the official Samsung firmware site?
http://www.sammobile.com/firmwares/
Fantassy123 said:
Did you Tried the official Samsung firmware site?
http://www.sammobile.com/firmwares/
Click to expand...
Click to collapse
Yeah, its not listed there, just two older ones that I can't get to work on my device.
Edit: Just realized my device isn't showing that its custom now. When I boot, I have the normal 'Samsung Galaxy S4' splash screen and in about device, the secure boot status is Samsung. I think I got that somehow with GooManager. Still rooted though as far as I can tell. Tested the phone calling again and seems it only works when my S4 is on speaker phone. I may try and just call samsung tomorrow and see if they will ship me a new one.
Well, I solved the problem. Kinda. I called AT&T warranty support (1-800-801-1101), talked to a guy and ran him through everything I've done. He tried a few things on his end, asked around to see if anyone else had heard of a similar problem (no one had), and they are sending me a replacement and I send the old one back.
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Psychotic-Cerebellum said:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Click to expand...
Click to collapse
OK, from your post it looks like you have done this before. To be sure lets go through the motions one more time.
Your device is updated to 4.4.4 NK4 the latest KitKat version. It's rooted you have supersu icon and run a root checker. First download again ( in case you got a bad download ) a copy of Philz CWM version 6.48.4 here is the link https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte/ use "phil'z_touch_6.48.6-hlte.tar.md5" . I like to use odin version v1.85 it's little older but very stable, here is a link https://mega.co.nz/#!oA5xzTAL!LXoVWB...ZlOMSWdRGVX6Uo now flash the .tar file with odin. Make sure you let device boot up on it's own back to the OS, do not pull the cable and boot the device yourself. Then try and boot into recovery.
If it bootloops again, I would backup all your data to the PC desktop, and then do a factory reset get back to bone stock ( that means when your in download mode it says Samsung Official status not custom ) so many times I have seen folks with an unrooted device where the bootloader still says custom and you end up with a dirty flash or worse. It may take a couple factory resets to get back to stock, it doesn't always take the first time. When I flash a custom rom and then decide to go back to stock, I flash the rom two or three times to make sure I'm bone stock.
If the factory reset doesn't work you may have to flash a new stock NK4 OS. Then root again and install the recovery. Here is my thread with all the info you need http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 , Enjoy !!!
Thanks for taking the time to give me a detailed response. Sounds like I'm gonna have to wait till Wednesday or Thursday when im off work and have some time to do this, but yeah, I was thinking maybe just a factory reset, but I'll use your links and try it one more time first. I'll let ya know. Thanks again
Do you have another link to the older Odin (1.85).the link says the file isn't there... Thanks again
Never got to test it out, but she didn't really want a custom rom anyway, just the WiFi hotspot, and I finally found a method that works, big shout out to idone for his awesome app. If anyone else is looking for WiFi hotspot without root that sees this, check out his tread in the apps and themes, for this phone. Worked like a charm. Thanks again jimzweb1. Much appreciate the reply!
Psychotic-Cerebellum said:
Never got to test it out, but she didn't really want a custom rom anyway, just the WiFi hotspot, and I finally found a method that works, big shout out to idone for his awesome app. If anyone else is looking for WiFi hotspot without root that sees this, check out his tread in the apps and themes, for this phone. Worked like a charm. Thanks again jimzweb1. Much appreciate the reply!
Click to expand...
Click to collapse
Awesome, Ya idone is the man when it comes to enabling the mobile hotspot be careful what you click with app. I will correct that link. Thanks
Psychotic-Cerebellum said:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Click to expand...
Click to collapse
That's the problem Knox security is getting harder flash engineering boot loader again then try rashr in app store to flash philz