Related
So my touchscreen didnt want to work anymore yesterday.
I restarted my phone several times and it didnt work.
I then went into xrecovery and clicked 'fix permissions'
Then more stuff didnt want to work anymore
I reinstalled the update.zip file, did a factory reset etc
And now my phone is stuck at the boot with 'Sony Ericsson'
I had minicm6 v6 on my phone (u20i)
I tried reinstalling a backed up zip, but still nothing.
What now?
If you made a backup you should try to restore that.
Sent from my Xploded Dinc2
Edit: Got my phone working, but now when I download something from the market, the phone restarts when it installs ?
Have you figured out the reason why it keeps restarting? If not I would try to reflash the rom.
Keep us updated.
Sent from my Xploded Dinc2
Ok I did another factory reset and cleared dalvik cache.
Everything is working good now
Thanks
No problem that's is what this community is here for
Sent from my Xploded Dinc2
Sweet
Soooo now that everything is working fine again, would anyone like to recommend me a new ROM to install? Some CM7 mod/rom maybe?
Which ones are the best?
(I know there is a list with all of the roms available for my phone, just thought I'd ask)
Im not sure which roms are available for your phone but cm7 is always a good choice.
Sent from my Xploded Dinc2 using xda premium
I ended up in installing CyanoCream Sandwich v2.0
Looking good so far
demozzracy said:
Sweet
Soooo now that everything is working fine again, would anyone like to recommend me a new ROM to install? Some CM7 mod/rom maybe?
Which ones are the best?
(I know there is a list with all of the roms available for my phone, just thought I'd ask)
Click to expand...
Click to collapse
Check this one Its the best one and quite fast then other ROMS
http://forum.xda-developers.com/showthread.php?t=1415026
I had Stornmix V2 installed for a couple of weeks and it's fast and stable...I really like it.
The only problem I noticed is that when I'm using the video camera, the phone just freezes and I need to remove the battery to make it work again.
The problem with that one is the requirements:
Unlocked bootloader
Latest version of the nAa kernel
I dont know if I have those things on my phone.
And Im not too sure on how to put it on, if i have too
Update:
CyanoCream Sandwich is a bit slow to be honest. I think I will be looking for a new one to install
You will learn little by little by searching through the forums. Unlocking takes some time and some patience.
If you only follow the instructions step by step then you will get an unlocked bootloader and you can install any kernel. dont worry, you will get it soon.
my regards and good luck for that.
Hello everyone. It's been a year since I last came to this site. This is where I got all my info on rooting. I'm somewhat embarrassed to say I'm still running my Gnote on 2.3.6 GB, baseband I717UCLA1, Saurom.
Recently my Gnote has become incredibly slow. More force closed now than ever before. Battery life is next to nothing. A full charge will last me 4hrs...yes 4 hours with fulltime use (txting, calling, browsing, watching videos and playing games). It will last me about 10hrs if I don't do a damn thing on it except maybe check an email, a txt or the time.
I've come back to get info on upgrading to ICS or Jellybean. My question is, have I basically done the hard part already (rooting) and just need to download a correct ROM and flash away, is that correct? Or do I need to take additional steps?
My other question is, in your opinion what's the most popular ROM for the Gnote 1 out right now. I'm way out of of the loop and I'm catching up on my reading.
Thanks and it's good to be back to this site. Hopefully I'll stick around more often this time around.
wow a year?
surprised nobody else chimed in, but I think I can get you in the right direction. with a few questions for ya, I think you will be on your way. I am reasonably new to the Note, but not to rooting or flashing. yes, I have rooted Note and flashed rom's.
1.did you root a year ago or just now? not sure if it will work rooted, but Samsung should be able to get you upgraded STOCK ICS very easily. the only reason I say that is I have not seen that modem before.
2. are you wanting to stay stock or flash custom? the Samsung upgrade is going to only take you to ICS. if you want JB, you need custom rom. pretty sure you know some of this. either way I believe, even if you want JB, you need ICS first. again, I think modem is going to be issue.
3. (not a question) in any of these issues, I, myself always believe that returning to stock is the safe bet. then start from there. there are people here with more experience that may tell you you don't need to. I need that confidence and fresh start to know nothing is tainting my process, then I have to start over anyway, but that's just me.
I will, as others will, always direct someone to the "Super Everything Thread". ALL questions can be answered there. no matter which you wish to do, its all there. from how to's to every flavor of rom.
I am sure no matter what you want to do it could involve using "Odin". which you may have done already. just check that everything is up to date.
same thing goes for a custom rom if you wish. its not that older roms aren't solid, but you may not have the support you may want or need.
and every phone is different I am sure you know. so what is great on one, is not on all. also some of newer roms (and not all are available here) work better with alternative kernals.
alternative kernals now CAN allow things such as overclocking or undervolting. these can be a fine line providing better or worse speeds and battery life. often sacrificing one for the other. don't play with it myself or need to right now.
*******again, "Super Everything Thread" and READ, READ, READ ******
hope I helped at least a little bit
BLASTphemus said:
Hello everyone. It's been a year since I last came to this site. This is where I got all my info on rooting. I'm somewhat embarrassed to say I'm still running my Gnote on 2.3.6 GB, baseband I717UCLA1, Saurom.
Recently my Gnote has become incredibly slow. More force closed now than ever before. Battery life is next to nothing. A full charge will last me 4hrs...yes 4 hours with fulltime use (txting, calling, browsing, watching videos and playing games). It will last me about 10hrs if I don't do a damn thing on it except maybe check an email, a txt or the time.
I've come back to get info on upgrading to ICS or Jellybean. My question is, have I basically done the hard part already (rooting) and just need to download a correct ROM and flash away, is that correct? Or do I need to take additional steps?
My other question is, in your opinion what's the most popular ROM for the Gnote 1 out right now. I'm way out of of the loop and I'm catching up on my reading.
Thanks and it's good to be back to this site. Hopefully I'll stick around more often this time around.
Click to expand...
Click to collapse
Personally I would suggest updating to the stock ICS and the re-root from scratch and flash one of the more stable ICS Roms such as Padawan v8, it's really stable, fast and has some note 2 features, really nice rom, stable fast and smooth. If you're wanting a JellyBean rom, I suggest one of 2 roms out there. The UnOfficial RootBox which is what I am running now, really smooth fast, no FC's so far all going good on it for the past couple of days or the Sons OF Android rom build 4. All are really great. Padawan is the most stable and still keeps you Spen sensitivity and features. Flashing one of the JB Roms, you will lose Spen apps. Hope that helped
Demmonnixx said:
Personally I would suggest updating to the stock ICS and the re-root from scratch and flash one of the more stable ICS Roms such as Padawan v8, it's really stable, fast and has some note 2 features, really nice rom, stable fast and smooth. If you're wanting a JellyBean rom, I suggest one of 2 roms out there. The UnOfficial RootBox which is what I am running now, really smooth fast, no FC's so far all going good on it for the past couple of days or the Sons OF Android rom build 4. All are really great. Padawan is the most stable and still keeps you Spen sensitivity and features. Flashing one of the JB Roms, you will lose Spen apps. Hope that helped
Click to expand...
Click to collapse
Ok, even though I'm already rooted. I can just update to ICS using Kies or do I use Odin? Or does it matter? Also, if I'm updating to stock ICS with whatever method I won't be able to backup any of my apps and contacts correct? Since I'll be starting from scratch again?
You may want to update your recovery to avoid errors with newer builds before you flash another rom. I suggest latest twrp. As for contacts. Just sync them with gmail and they'll be restored once you sign in. As for the rom of choice. Read through the development threads, watch YouTube reviews and find one that fits your preference.
Sent from my SGH-I717 using Tapatalk 2
Well the problem I've now been having is I cannot connect to kies to upgrade to stock ICS. I've tried 2 computers. The problem in my PC is I'm unable to install Samsun USB drivers. I've uninstalled/reinstalled. I even plugged in the USB adapters on MOBO to different ports. I still get "?" for USB under device manager. WIth my laptop I'm able to install the usb drivers but kies never detects my phone. I get the error "this device is not supported by kies 2.0" I have USB debugging turned on. I though it might be the cable so I went and got a couple of $2 cables and still nothing.
It seems I'm stuck on GB or is there an other way to upgrade to ICS with kies??
BLASTphemus said:
Well the problem I've now been having is I cannot connect to kies to upgrade to stock ICS. I've tried 2 computers. The problem in my PC is I'm unable to install Samsun USB drivers. I've uninstalled/reinstalled. I even plugged in the USB adapters on MOBO to different ports. I still get "?" for USB under device manager. WIth my laptop I'm able to install the usb drivers but kies never detects my phone. I get the error "this device is not supported by kies 2.0" I have USB debugging turned on. I though it might be the cable so I went and got a couple of $2 cables and still nothing.
It seems I'm stuck on GB or is there an other way to upgrade to ICS with kies??
Click to expand...
Click to collapse
You have to unroot to get stock update and use kies
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
No need to flash a stock ROM. Just full wipe and install the ROM of your choosing. More than likely you will want to update the baseband/modem/radio or whatever you want to call it. Easy to find and install. You can update recovery if you want or need as darkchyldx101 suggested.
Agoattamer said:
No need to flash a stock ROM. Just full wipe and install the ROM of your choosing. More than likely you will want to update the baseband/modem/radio or whatever you want to call it. Easy to find and install. You can update recovery if you want or need as darkchyldx101 suggested.
Click to expand...
Click to collapse
it was suggested he flash to stock and re-root, which isnt a bad thing it cleans up the phone pretty good
BLASTphemus said:
Well the problem I've now been having is I cannot connect to kies to upgrade to stock ICS. I've tried 2 computers. The problem in my PC is I'm unable to install Samsun USB drivers. I've uninstalled/reinstalled. I even plugged in the USB adapters on MOBO to different ports. I still get "?" for USB under device manager. WIth my laptop I'm able to install the usb drivers but kies never detects my phone. I get the error "this device is not supported by kies 2.0" I have USB debugging turned on. I though it might be the cable so I went and got a couple of $2 cables and still nothing.
It seems I'm stuck on GB or is there an other way to upgrade to ICS with kies??
Click to expand...
Click to collapse
As JamieD81 mentioned that would be your best bet is to unroot and re-root, install the new baseband: here's a link to it
http://forum.xda-developers.com/showthread.php?p=39606775
Scroll down to phlunkie's post
Will probably speed you up a little too.
hmmmm
JamieD81 said:
it was suggested he flash to stock and re-root, which isnt a bad thing it cleans up the phone pretty good
Click to expand...
Click to collapse
seems ive heard this somewhere before???? hmmmmm , maybe I am not such a dullard after all
Ok, after a little more reading I'm glad so say I'm now rooted on ICS with Padawan V5 rom. My Gnote is once again snappy fast and smooth.
This is what I did.
1. Unrooted
2. upgraded to ICS with kies
3. rooted (made backup of stock ICS, used twrp)
4. flashed padawan V5
Thank you all for your suggestions and recommendations. :good:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
Hello first of all I would like to thank all the great developers for the great ROMs out there.
Second I would like to warn everyone that this is a "first world problem rant" that I'm about to write up with a legit frustration I have.
I have a rooted Samsung Galaxy S4 from ATT and the only reason I got this phone over any other Android phone is the great camera and the screen.
I absolutely hate TouchWiz. It's bloated, slow and painfully ugly (to me). For this reason I decided to try out Flashing roms.
For the last couple of weeks (months maybe?) I have been using Cyanogenmod 10.1 stable with not many problems. Mostly camera issues but no biggie.
My frustration is the following: CyanogenMod has had two stable updates for my phone to go from 10.1 to 10.2 and, though it flashes perfectly, every time I reboot the phone the phone gets stuck on the "Samsung Custom (lock)" screen and I am forced to go into TWRP and reflash 10.1+Gapp from my SD carfd.. This happens EVERY TIME. With CM10.1 I can restart the phone just fine by the way. It's 10.2 and other Roms that make get stuck on the Samsung Custom (lock) screen.
So i decided to try out Gummy ROM because Kit Kat
I put the ROM in my SD card, Formated, Wiped and Installed. Worked like a charm until the camera wasnt working that well. I read the forums and said to restart to fix the camera.. Guess what?...AGAIN....Stuck on Samsung Custom (lock) screen.
My frustrations is that pretty much EVERY Rom that I have tried minus CM10.1 has done this to me and I have no idea what I'm doing wrong.
I have tried battery pulls, waiting 30 seconds, wiped dalvik, cache, etc. Fixed Permissions....everything and I have to reflash the ROMs almost 99% of the time unless I use CM10.1. I am tired of reading forums to fix this so here I am asking for your help.
/endrant
I have no idea what else to do so any help would be great.
INFO:
Current ROM: Gummy 1.1-11-21-13-UNOFFICIAL
Android 4.4
Baseband version
I3377UCUAMDL
Kernel Version
3.4 g0-Elite-Kernel-ga719cb
Build Number:
KRT16S
Google Apps:
Gapps-Kk-20131113.Zip
TWRP Version
I have no idea and I'm not about to restart phone and go through the pain of reflashing the ROM again as I just did. I will punch so many babies if I have to do this again!'
Thanks for listening.
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
9859834534
prsterero said:
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
Click to expand...
Click to collapse
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Speedsterspeed277 said:
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Click to expand...
Click to collapse
It could be. There have been people that get weird issues with twrp so you may want to test out a different recovery to see if the issue persists.
prshosting.org
Edit: They do keep coming!
I looked into doing it, and there is no way in hell that I should be a) doing it, and b) unleashing it onto the world. It would be bad.
I only have the one phone to test it on and can't risk messing it up and I don't have the experience to work on it if it didn't come out perfectly.
I expect that it will be the last Sprint ROM released for this phone, We're nearing the end of support, so it would be good to have these final versions "fixed" and available
...on the off chance a few developers will jump right in and cook up a few mega ROMs for us.
DQG1 Root and Xposed (rewritten)
On a related note, I installed stock DQA1 DQG1, using the usual CF Autoroot, battery pull thingy process Odin for the ROM and TWRP, then booting once, booting into recovery, and then installing SuperSU and it rooted fine. No loss of settings or anything else as far as I can tell.
I did have to install the latest versions of the Xposed files. After rooting and custom recovery (TWRP works fine), install XposedInstaller_3.1.4.apk first like any other apk, then go to recovery and install Wanam v87.1-alt-sdk23-arm-custom-build, but everything (Xprivacy, etc.) worked fine. Keep in mind, you HAVE to use the "alt" (see the "alt" in the file name above?) version or else it won't work. Samsung made some changes, blah, blah, blah. Much thanks to Wanam!
New side note: I did do a factory wipe, and even after reinstalling everything, and using a ROM that contains bloatware, I still have like 40% more space on the phone. I truly don't know what happened there.
Anyone have any thoughts as to kernel? I downloaded Emotion r26 RC1, and BeastModeKernel 1.0BETA, but I haven't tried them yet.
EDIT: Emotion r26 RC1 works fine, but it doesn't seem like CPU freqs are ever going to stick.
No surprise that neither Emotion nor BeastModeKernel worked; I haven't seen anything else that may.
Thoughts anyone?
Both kernels are good, emotion has a few more options to tweak but I took an update a month or two ago and run NotEdge ROM fine , I just use SO launcher with it because I like TW, also latest xposed is 86.1 and I wish I could do what your asking but it probably would be just as bad you'll be fine with that ROM I just suggested it has everything u just requested just make a nandroid and do it at home in case you do something wrong you can always ODIN back your firmware
Sent from my HTC One M9 using XDA-Developers mobile app
D'oh!!
Eating a little crow here. So far, there have been two three 742 updates, maybe there will be more. Who knows?
But I edited the title of the first post. Again. Again. 741 times.
Do you guys have a link to the stock unrooted rom? My phone is royally screwed right now and still stock. I want to do a clean flash and see if that fixes it.
Over a year later, and the still keep coming.
Hmmmm.
I did take another gander around, but it seems that I would need Linux to do it correctly, so I am still opting out of doing it myself.
mictek said:
Do you guys have a link to the stock unrooted rom? My phone is royally screwed right now and still stock. I want to do a clean flash and see if that fixes it.
Click to expand...
Click to collapse
They all arrive here: https://www.sammobile.com/firmwares/galaxy-note-edge/SM-N915P/ eventually.
Hello i got a note 4 Sprint MM 6.0.1 N910PVPU5DQI5 . i am from Argentina, and i bought the phone used from a guy from USA. (i don`t know how but it`s working with the bands here but i dont know if 4g is working, the guy says it works, maybe i don`t have 4g singal in my zone) .
the phone works fine, but has some srpint stuff and ads that bother me. so i flashed TWRP , and now i am looking for any roms and kernels to flash.
for example, is safe to flash this: https://forum.xda-developers.com/note-4-sprint/development/rom-updated-1-14-2017-t3538051
or should i change something first ???.