Related
I tried to flash a kernel to my samsung showcase, but it didn't work. it wouldn't even go to boot logo. i have gotten it to boot now but everything keeps crashing every few seconds and it says verizon, but i have ntelos. I cant get any 3g or data. I have ClockWorkMod installed on it. PLEASE HELP.
jdp123321 said:
I tried to flash a kernel to my samsung showcase, but it didn't work. it wouldn't even go to boot logo. i have gotten it to boot now but everything keeps crashing every few seconds and it says verizon, but i have ntelos. I cant get any 3g or data. I have ClockWorkMod installed on it. PLEASE HELP.
Click to expand...
Click to collapse
If you have clockworkmod installed on it, boot into cwm and wipe data/cache/dalvik and flash a different showcase kernel that you know works. Do you have a functioning showcase kernel already on your sd card?
You flashed a Verizon Fascinate kernel onto a Telus Showcase. Good job.
Dude I did the same thing my advice and what worked for me is flash the cell south showcase rom. Root your phone get rid of all cell south Apps make it look stock take it back get a new one that's if your in your 60 or 90 days i forget what it is as far as I know there's no roms For are showcase yet. If they give u **** just say u talked to customer service and samsung and u told them your phone seemed really slow and u noticed a few apps always running that shouldn't be even after you killed them like screen capture service and a few others and they told u it's probably a phone defect and should take it back and pick the rep that's looks like they want to go home they only want sells and will get you out as quick as possible. I hope all works out well for you I know how it is I'm on frog and payed 450..... but it should
Got my cell south Rom from some dudes in a irc chat room #samsung-mesmerize they helped me out a lot and if your willing to dump your Rom when u get a new phone they will make you a Rom for your phone
Electrodeath0 said:
You flashed a Verizon Fascinate kernel onto a Telus Showcase. Good job.
Click to expand...
Click to collapse
Telus doesn't use the Showcase. They use a GSM version of the Fascinate. The Showcase is a CDMA phone that is like a twin to the Verizon Fascinate and the US Cellular Mesmerize.
Another Fascinating post by my XDA app...
big_c said:
Dude I did the same thing my advice and what worked for me is flash the cell south showcase rom. Root your phone get rid of all cell south Apps make it look stock take it back get a new one that's if your in your 60 or 90 days i forget what it is as far as I know there's no roms For are showcase yet. If they give u **** just say u talked to customer service and samsung and u told them your phone seemed really slow and u noticed a few apps always running that shouldn't be even after you killed them like screen capture service and a few others and they told u it's probably a phone defect and should take it back and pick the rep that's looks like they want to go home they only want sells and will get you out as quick as possible. I hope all works out well for you I know how it is I'm on frog and payed 450..... but it should
Got my cell south Rom from some dudes in a irc chat room #samsung-mesmerize they helped me out a lot and if your willing to dump your Rom when u get a new phone they will make you a Rom for your phone
Click to expand...
Click to collapse
how do i flash cell south rom? I cant even boot into my phone now and if i mount my sd card from cwm it doesnt show up on pc. The only things i can go into are cwm, download mode, and recovery mode.
Use Odin in download mode go to the irc chat I told u adout and ask for the rom that's were I got mine the helped every step of the way ask for bakedtator I told him about you these are good guys they saved my ass http://webchat.freenode.net/ just make a nickname by putting it in the box like u already have one the channel is #samsung-mesmerize just like that put the #
jmcintire said:
Telus doesn't use the Showcase. They use a GSM version of the Fascinate. The Showcase is a CDMA phone that is like a twin to the Verizon Fascinate and the US Cellular Mesmerize.
Another Fascinating post by my XDA app...
Click to expand...
Click to collapse
Slow down there buddy I'm on a showcase sch i500 cdma right now n-telos does have it they started selling it around may 1st its not gsm n-telos is cdma a little different then the cell south found out the hard way
Same problem here. Found directions to install Cyanogen 7.1 on a Samsung Showcase as it listed it to be compatible. Downloaded ClockworkMod Recovery and installed it using Heimdall Suite 1.1.1. Used CWM to then install the Cyanogen 7.1 rom and Google apps rom as well. All seemed good except for when it booted it listed my carrier as Cellular South. My carrier is actually Ntelos.
Needless to say the only thing that initially worked were voice calls and the web for some reason. Text messaging was broken(a big one with me).
I tried to *228 to see if that would maybe program the phone for the proper settings but it did not work.
So I thought that because I had backed up my phone with CWM I could just revert back to my old image and all would be well. The restore function did not work. Rebooting into CWM from the ROM manager I was able to initiate the restore. All seemed well and it notified me it had restored. When I rebooted my phone however it was frozen at the Samsung logo. I rebooted into CWM and cleared my cache and did the factory reset only to find that after a reboot it just loads straight to CWM.
Now I basically have a useless phone. I can reinstall Cyanogen but I no longer have signal for service. It also seems hit or miss as to if it installs with no problems. Sometimes it will install and the default widgets will show errors loading. The google apps will not install sometimes even though they show confirmed through CWM. I can reboot the phone from ROM manager into CWM and it will perform the restore just the same as the first time without any problems but the phone will not boot back up to the stock ROM. If I try to boot straight to CWM using Volume+Home+Power it will not perform the restore. It goes through small part
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system
That's as far as I get.
I'm basically stuck in this vicious cycle with no end in site. I've tried researching til my eyes hurt to find a solution to my problem. I can't find a stock ROM anywhere. Obviously the combination of a small carrier and a small audience for this model phone yields little along the lines of widespread support. So I've came here to the XDA Developers board in hopes that someone will be able to help me.
I must humbly ask for everyone's help. I bought a Galaxy S3 (Sprint) today and rooted no problem. I downloaded font changer and Rom Toolkit. I changed a font and clicked "reboot" and the phone hung on the reboot screen--after the sprint logo and says "Samsung" with the blue light going up and down in intensity.
I tried a cache clear and data wipe, neither of those worked. I also tied reflashing the root ROM. That didn't work.
My most recent steps were to flash the stock recovery and stock ROM. It still hangs. I can get to recovery and am able to flash with ODIN. What should I do next?!
If nothing else, is there a way to reset the flash counter so I can maybe get Sprint to fix it? The only way I saw is to download an app, which won't work.
Any help is appreciated, I've tried all that I could think of.
UPDATE: Maybe there is no ROM installed anymore? I'm downloading the full Omega ROM. Anyone have a link to the sprint stock rom?
brickeds3 said:
I must humbly ask for everyone's help. I bought a Galaxy S3 (Sprint) today and rooted no problem. I downloaded font changer and Rom Toolkit. I changed a font and clicked "reboot" and the phone hung on the reboot screen--after the sprint logo and says "Samsung" with the blue light going up and down in intensity.
I tried a cache clear and data wipe, neither of those worked. I also tied reflashing the root ROM. That didn't work.
My most recent steps were to flash the stock recovery and stock ROM. It still hangs. I can get to recovery and am able to flash with ODIN. What should I do next?!
If nothing else, is there a way to reset the flash counter so I can maybe get Sprint to fix it? The only way I saw is to download an app, which won't work.
Any help is appreciated, I've tried all that I could think of.
UPDATE: Maybe there is no ROM installed anymore? I'm downloading the full Omega ROM. Anyone have a link to the sprint stock rom?
Click to expand...
Click to collapse
My only suggestion is to do a full wipe again (not just cache mind you) and then install the latest ROM for a Sprint phone one more time. Did you not do a nandroid backup that you could restore? Always do a nandroid backup before messing with any part of the phone for this very reason. I'm not harping. I'm just saying in the future it will save you from this issue.
P.S. This is the International thread. You better not be flashing your Sprint S3 with an International S3's ROM. That's a big no-no...
UPDATE:
*sigh*
Sprint Samsung Galaxy S3 Android Development Thread
Omega doesn't have a ROM for the Sprint version. You need to pay more attention before flashing your ROM's. Get a ROM from the above link, and never do anything without doing a nandroid backup first. Seriously.
I think I'm screwed
I reinstalled the Sprint software twice before I tried the other rom. Nothing worked. The Omega rom has me completely bricked.
I ordered a jig to see if that helps and will take it to a cell phone store in town (not factory) to see if they can get it into download mode. I have the sprint .tar bootloader thanks to this forum.
This was my first root and I never heard of the nandroid backup. I hope I can fix this for a $100 bucks and it isn't a $1000 mistake.
brickeds3 said:
I reinstalled the Sprint software twice before I tried the other rom. Nothing worked. The Omega rom has me completely bricked.
I ordered a jig to see if that helps and will take it to a cell phone store in town (not factory) to see if they can get it into download mode. I have the sprint .tar bootloader thanks to this forum.
This was my first root and I never heard of the nandroid backup. I hope I can fix this for a $100 bucks and it isn't a $1000 mistake.
Click to expand...
Click to collapse
1. Do you currently have the stock recovery or a custom recovery (e.g. CWM)? If you have stock recovery go to question 2, otherwise go to question 4.
2. Are you able to flash custom recovery via appropriate steps? If yes go to question 3, otherwise I think you're screwed.
3. Flash custom recovery.
4. In custom recovery do a full wipe.
5. Download THIS ROM to your SD Card and then flash in recovery.
6. See if the issue is resolved. If the issue is resolved that's fantastic. If the issue is not resolved then I'm pretty sure you're screwed.
Thanks
Thanks for that! Tomorrow I'm taking it to a custom cell phone repair/unlock store to see if they have a jig. If they do I'll try these steps, if not we'll see if my carrier is understanding...
I think moderator in development section should make compulsory to any developers make very big warning to anyone who read development thread. Many case carrier based phone come here to ask and flash ROM.
Sent from my GT-I9300 using Tapatalk 2
apisfires said:
I think moderator in development section should make compulsory to any developers make very big warning to anyone who read development thread. Many case carrier based phone come here to ask and flash ROM.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
The developers can't make it any more clear. The user is already clicking on Samsung Galaxy S III I9300. That isn't the phone they have. The developers can't be held responsible for users that refuse to read.
ive done the same exact thing and need to figure out how to fix it!!! did you find a cure for it yet?
brickeds3 said:
I reinstalled the Sprint software twice before I tried the other rom. Nothing worked. The Omega rom has me completely bricked.
I ordered a jig to see if that helps and will take it to a cell phone store in town (not factory) to see if they can get it into download mode. I have the sprint .tar bootloader thanks to this forum.
This was my first root and I never heard of the nandroid backup. I hope I can fix this for a $100 bucks and it isn't a $1000 mistake.
Click to expand...
Click to collapse
Remove your battery ..wait for 5 min...insert it and try to go into download mode. if you can get the correct rom and flash it.
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
pstrulm said:
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
Click to expand...
Click to collapse
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory reset in between.
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
androidmechanic said:
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
AT&T Phones have a [logo}AT&T] on the top-center!!
But if you are in doubt, use kies to do a full recovery-restore [WILL ERASE EVERYTHING ON YOUR DEVICE].
See post #4 on this thread.
fbauto1 said:
androidmechanic said:
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
androidmechanic said:
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
you are both actually correct, however, I am looking at PSTRULM's stats. if he is anything like me when I started, the more simple and less complication involved in the process, the more he may understand.
ANDROIDMECHANIC is stating the most basic and beginner way to do this and understand simply. after doing this a few times as I did, the basic mechanics of the process will become more fluent.
then he can make his own decisions as to methods which might be easier for him, without confusing.
I am sure you both are a huge help to everyone and I thank members such as yourself for your efforts. ME, I prefer baby steps, cause I know I can really EFF things up if I get confused
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Just a reminder.. when flashing through Odin, make sure it's an ODIN-flashable tarball, i.e., you can't flash a recovery-type zip through Odin and vice versa.
So to start off I've got an s3 through the dreaded ALLTEL... I know there's hardly anything for it so ya.. I flashed cwm through Odin and installed supersu and quickly found out I had to go through Knox.. I went and ran the de-samsungnizer script to remove Knox so no more Samsung firewall crap.. Got it rooted and everything's good til I realize the main reason I rooted (WiFi hotspot) doesn't even work so I go back to Google and find a WiFi hack mod .zip and flash it now I'm stuck at booting.. Come to find out that somehow I've switched my phone to d2spr.... Or at least thats what cwm says when I tried to flash a d2usc cm11 nightly.. Dumb me i know i will be harshly scolded.. I didnt make a backup!!!! Now trying to get back to stock now... Thinking.. My wife has the same phone bone stock could I just make a nandroid of hers and flash over mine or have I turned my phone into a really nice paper weight???
Flash stock rom via odin, to recover the you'll have to start again, btw your in the wrong forum this is for int'l s3.
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