hey guys!
i will realy appriciate any help on this one:
i am in a light panic attack as i might bricked my first phone..
today i have updated my t989 to ics 4.0.4 via kies, and then rooted it.
of course the root was so i can flash a rom. i chose to try cm9.
any ways, in order not to get the phone stuck in boot loop, i have tried to install the touch version of the cwm recovery.
i did it through the zip on sd option.
the version i used was: CWM6013-TOUCH-CM9-recovery (file size 4.201)
it seemed ok at first.
but then when i retsrted the phone, i noticed that every app i am trying to launch takes forever to respond (about a minute)...
i have tried to do factory reset and it did not help - the phone was sluggish even on the first setup screens..
now i am in the process of downloading the stock version again, to unroot. is this the way to go? did i miss something?
please let me know what info i can provide so you will be able to help me.
again, and i can't say it enough: every help will be very much appreciated. so, did i brick my phone?
thanks!
cvbn
Dude wrong section.
cvbn52 said:
hey guys!
i will realy appriciate any help on this one:
i am in a light panic attack as i might bricked my first phone..
today i have updated my t989 to ics 4.0.4 via kies, and then rooted it.
of course the root was so i can flash a rom. i chose to try cm9.
any ways, in order not to get the phone stuck in boot loop, i have tried to install the touch version of the cwm recovery.
i did it through the zip on sd option.
the version i used was: CWM6013-TOUCH-CM9-recovery (file size 4.201)
it seemed ok at first.
but then when i retsrted the phone, i noticed that every app i am trying to launch takes forever to respond (about a minute)...
i have tried to do factory reset and it did not help - the phone was sluggish even on the first setup screens..
now i am in the process of downloading the stock version again, to unroot. is this the way to go? did i miss something?
please let me know what info i can provide so you will be able to help me.
again, and i can't say it enough: every help will be very much appreciated.
thanks!
cvbn
Click to expand...
Click to collapse
What all did you do to install the ROM?
Something like this happened to me on my original Galaxy S when I updated it via Kies to the new stock version. Everything was running extremely sluggish. I don't remember what I ended up doing to fix it but I most certainly did not keep the stock update on there. I rebooted it and let it sit for about 30mins and then rebooted it again and tried using it. It was a bit better but still not good so I just flashed another Rom and then it was lightning quick.
The good news is you didn't brick it if you can still boot up and run stuff. I'd suggest updating your recovery to TWRP as that seems to be the preferred one now a days, it's the one I've been using to flash countless Roms without any problems, and most Devs recommend it. Apart from that, follow the install instructions precisely and you shouldn't have a problem. To be sure, after upgrading your recovery to TWRP, you could do the wipes (cache/dalvik/factory reset/system) 2-3 times before installing your new Rom, that seems to help some people coming from previous troublesome Roms.
I've noticed a few problems people seem to have around here come from the recovery, mainly those not using TWRP and/or using some form of outdated or beta CWM. Hopefully you can fix your problem, I know first hand how awful that sluggish feeling is. Good luck!
Please forgive me if this is in the wrong spot or if I broke some forum rule, I have never posted here but I have read a ton, thanks for all the help you guys have posted by the way.
First off I am not by any means an expert on computers and rooting but I have a decent understanding of the basics and can easily follow online instructions to root. I obviously have a d2att, I recently rooted it. I was happy with it unrooted for nearly a year but when samsung released the 4.3 update my phone really started sucking. Eventually I decided to root just to get a rom that functions better. I have been running gummy rom kit kat, I think its the nightly from march 10th, I have had no real issues other than some random reboots here and there. My mom begged me to root her d2att because she also was tired of the buggy samsung 4.3 update. I eventually rooted hers, even though I really didn't want to, knowing that I would get calls about every little issue and I would have to run and fix it... anyway
She has had issues that I have not had, she says that her phone randomly turns to silent periodically and causes her to miss calls, and she also says her bluetooth is intermittent. I don't use blue tooth at all so I wouldn't know but I have not had an issue with randomly going to silent. I have tried a lot of custom roms over the past 2 months since I rooted, including CM11, CM10 (all of them), AOKP, slimroms, of course Gummy, and a variety of others. All of them have had some major bug that is unbearable, from not connecting to wifi or not sending and receiving MMS, except for gummy which I have only had the random reboots.
Okay, so when I rooted mine originally I made a nandroid copy of the original rom after I rooted it, I didn't realize but somehow this nandroid file created to my internal memory instead of my sd card, so when I loaded a custom rom it was deleted. Like I said I'm far from an expert and that was a huge mistake. So anyway when I rooted my moms (same phone) I made a nandroid of her stock rom after the root and saved it to my computer, tablet, flash drive, external hd... etc.
Now that she is having problems with the absolute best ROM that I have found functionality wise, I thought I would restore her stock rom and debloat it, try my best to get it running better. I used her nandroid back up and restored my phone to it, only to get a ton of errors, everything was force closing. I kept getting the popups that "unfortunately ... has stopped" they were nonstop. Literally all I could do was hit ok and try to do the same with the next window, finally I get rid of those and the phone wouldn't run any apps or make any calls etc. So I rebooted to recovery and went restored my nandroid that I made earlier that day and all is fine with my phone again.
So here is my questions. First off when I made the nandroid of her stock rom I renamed the file STOCKROM, that way I would def know what it is and to not delete it. Will renaming a nandroid file make it not work correctly?
Also would a nandroid back up of her phone simply not work correctly on mine? I thought it would but it def does not. Maybe there is saved data that doesn't match my sim card.. I have no clue.
If I used this nandroid on her phone do you think it will work corretly?
If I messed up the file be renaming it, does anyone have a backup for stock that I can possibly use?
Last but not least, any recommendations for custom roms for d2att? I really just want speed, and no bugs
I am really sorry about the excessively long post, but I wanted to fill in the background info before I asked my questions, in case it was needed. Any help at all will be greatly appreciated.
Again please forgive me if I broke a forum rule or posted in the wrong spot, I don't typically post on any forums ever, I just tend to read the posts of others. THANKS IN ADVANCE FOR ANY AND ALL HELP, GREATLY APPRECIATED.
sdevans80 said:
So here is my questions. First off when I made the nandroid of her stock rom I renamed the file STOCKROM, that way I would def know what it is and to not delete it. Will renaming a nandroid file make it not work correctly?
Also would a nandroid back up of her phone simply not work correctly on mine? I thought it would but it def does not. Maybe there is saved data that doesn't match my sim card.. I have no clue.
If I used this nandroid on her phone do you think it will work corretly?
If I messed up the file be renaming it, does anyone have a backup for stock that I can possibly use?
Last but not least, any recommendations for custom roms for d2att? I really just want speed, and no bugs
Click to expand...
Click to collapse
If you decide to go back to stock 4.3, this thread should help. AT&T I747 UCUEMJB Stock Restore
I've never had to use a nandroid and definitely have not tried one on a phone different from where it was made, but from reading in the past I don't believe that renaming it is causing the problem. I believe it is probably due to either trying it on a different phone or the file structure may have been changed when you moved it to the pc. Hopefully someone more experienced will chime in regarding the nandroid on your phone. If it is still on her phone I think it may work.
thanks
Zdq4DDunit to the pc. Hopefully someone more experienced will chime in regarding the nandroid on your phone. If it is still on her phone I think it may work.[/QUOTE]
Thanks for the tips. I know its still on her phone and the name hasnt been altered. I wanted ti try a debloated touch wiz for her. I havr liked Gummy but loaded a carbon jelly beam tonight. So far so good. Any suggestions for custom ROMs for attd2? I have had a time finding one bthats useful. I'm glad I have my gummy on nandroid. When I finish screwing around for her that's where I'll head back to I'm sure. Unless I find a sweet bug free ROM through a reccomendation. I'll check the link in the AM thanks for the reply.
sdevans80 said:
I wanted ti try a debloated touch wiz for her. I havr liked Gummy but loaded a carbon jelly beam tonight. So far so good. Any suggestions for custom ROMs for attd2?
Click to expand...
Click to collapse
I have been considering Intergalactic, but I haven't tried it yet.
Any link for that?
sdevans80 said:
Any link for that?
Click to expand...
Click to collapse
[ROM] Intergalactic v4.1 [AllianceRom][UCUEMJB][4.3][1/8/2014]
question
You MUST have the UCUEMJB or UCUEMJ2 bootloader and the UCUEMJB modem installed before proceeding or this ROM will not work properly. Your data and wifi may be broken if you do not do this first. These are available here: Bootloader and Modem Options
sdevans80 said:
Any link for that?
Click to expand...
Click to collapse
Quick question. I have only rooted and flashed cm toms and aokp. I haven't done anything specifically to change my boatloadsoor kernel. I really don't have the knowledge absolute that. The first step says what's listed above. What does this mean? Can you help? Thanks for the time and tips.
Hello everyone,
I really need your help with my wife's Metro PCS Samsung GS4 M919N.
The thing is, we are now living outside the US so I had to unlock her phone. After ordering the unlock codes, I decided to root the phone and use a custom ROM while waiting for the codes.
That is why I found this guide here: androidforums.com/metropcs-galaxy-s4-all-things-root/790899-metropcs-galaxy-s4-all-things-root-guide.html
So while reading the guide, I aimed to have the following accomplished at the end:
Recovery: TWRP
Custom ROM: CyanogenMod 10.2.1
I then started doing the guide for the TWRP recovery by using Odin. I got the message saying that the flashing passed and went ahead to restart to recovery to install CM 10.2.1 as a custom ROM. The thing is that I keep on restarting to the stock recovery not TWRP. So I went to YouTube and found a video showing how to flash TWRP using GooManager. After following that guide, I went to restart to recovery and I successfully got into TWRP.
Now, to achieve my goal, all that's left to do is to flash CyanogenMod 10.2.1 (jfltetmo).
Before doing that, I decided to make a backup. After using TWRP to do a backup, I proceeded to installing the custom ROM + gapps (wiped with the default settings). Everything was working I think (I handed the phone to my wife so she was he one testing it). After some time, she decided she wants the stock ROM instead so I decided to download the androidforums.com/metropcs-galaxy-s4-all-things-root/783769-rom-recovery-flash-able-stock-m919nuvuamf2-rooted-deodexed-rom.html ROM.
I flashed the newly downloaded ROM + gapps (same file). This time, I couldn't get the gapps to work probably because it was meant for another version. So I decided to just restore from the backup I created earlier.
So, the usual stuff. Wipe. Restore. Restart.
Seems to be going smoothly because my wife was happy to see the old ROM she was used to.
Until the phone started to restart on it's own. (It's pretty much downhill from here on out).
At first I thought it was just a random thing that probably would never happen again. I was wrong as it became more frequent as days went by.
Recently I can't just restart the phone, I would have to remove the battery and then restart it. Now, it's getting really hard to restart the phone. Please help me fix this. I prefer to leave the phone rooted, but if the fix unroots the phone then so be it, anyway my wife prefers the stock ROM so only the unlocking was necessary.
Metro PCS Samsung Galaxy S4 M919N
Recovery:
TWRP 2.6.3.1
ROMs:
Stock Metro PCS
CyanogenMod 10.2.1
Let me know if you need more information from me. Hopefully I can restart the phone so I can give you some version numbers.
Thanks everyone!
I didn't read everything but just wanted to say
VERY GOOD THREAD!
this is how threads should be done. Very descriptive, organized, told us everything you did and asked for help! Good job man! Only negative is it prolly should have gone in Q&A section but irregardless very good thread!
About your issue, I recommend flashing stock Odin tar file to everything back to stock and reroot and start over. Flashing stock will not lock it again it will remain unlocked. But should get you back up and fresh. Just be aware it will erase all your data and all of the internal SD card.
Sent from my SGH-M919 using Tapatalk
dokgu said:
Hello everyone,
I really need your help with my wife's Metro PCS Samsung GS4 M919N.
The thing is, we are now living outside the US so I had to unlock her phone. After ordering the unlock codes, I decided to root the phone and use a custom ROM while waiting for the codes.
That is why I found this guide here: androidforums.com/metropcs-galaxy-s4-all-things-root/790899-metropcs-galaxy-s4-all-things-root-guide.html
So while reading the guide, I aimed to have the following accomplished at the end:
Recovery: TWRP
Custom ROM: CyanogenMod 10.2.1
I then started doing the guide for the TWRP recovery by using Odin. I got the message saying that the flashing passed and went ahead to restart to recovery to install CM 10.2.1 as a custom ROM. The thing is that I keep on restarting to the stock recovery not TWRP. So I went to YouTube and found a video showing how to flash TWRP using GooManager. After following that guide, I went to restart to recovery and I successfully got into TWRP.
Now, to achieve my goal, all that's left to do is to flash CyanogenMod 10.2.1 (jfltetmo).
Before doing that, I decided to make a backup. After using TWRP to do a backup, I proceeded to installing the custom ROM + gapps (wiped with the default settings). Everything was working I think (I handed the phone to my wife so she was he one testing it). After some time, she decided she wants the stock ROM instead so I decided to download the androidforums.com/metropcs-galaxy-s4-all-things-root/783769-rom-recovery-flash-able-stock-m919nuvuamf2-rooted-deodexed-rom.html ROM.
I flashed the newly downloaded ROM + gapps (same file). This time, I couldn't get the gapps to work probably because it was meant for another version. So I decided to just restore from the backup I created earlier.
So, the usual stuff. Wipe. Restore. Restart.
Seems to be going smoothly because my wife was happy to see the old ROM she was used to.
Until the phone started to restart on it's own. (It's pretty much downhill from here on out).
At first I thought it was just a random thing that probably would never happen again. I was wrong as it became more frequent as days went by.
Recently I can't just restart the phone, I would have to remove the battery and then restart it. Now, it's getting really hard to restart the phone. Please help me fix this. I prefer to leave the phone rooted, but if the fix unroots the phone then so be it, anyway my wife prefers the stock ROM so only the unlocking was necessary.
Metro PCS Samsung Galaxy S4 M919N
Recovery:
TWRP 2.6.3.1
ROMs:
Stock Metro PCS
CyanogenMod 10.2.1
Let me know if you need more information from me. Hopefully I can restart the phone so I can give you some version numbers.
Thanks everyone!
Click to expand...
Click to collapse
I agree with Elesbb. If the goal is jus tto get back to stock, just do an odin flash of the stock ROM. Be advised if you flash the latest Kit Kay update you will nto be able to go back to Jelly Bean. From your post it seems like you are partial to Jelly Bean. So if that's what you want, but sure you use the stock 4.3 ROM. You can find it around here on XDA somewhere with a quick search to make sure you have the right one.
As Elesbb said, you won't loose the 'sim unlock'. But you will lose root. However you can root the stock ROM just fine.
You might also consider one of the myriad of TouchWiz based custom ROMs. They are look just like TouchWiz that your wife wants, but have a lot of optimizations and options in them. Those should flash just like any ROM. If you still get the reboot issue then do the Odin back to stock, reroot, then flash the custom TW roms.
---------- Post added at 12:46 PM ---------- Previous post was at 12:45 PM ----------
Thread cleaned.
Rather than bashing a ROM or user let's keep on topic and help the OP resolved the problems he's having. Arguing over the virtues of a ROM doesn't help anyone.
Thank you,
Rwilco12
Before posting this thread I sent the aforementioned guide's poster (arocker). He sent me a reply saying not to use gapps as the stock ROM for Metro PCS already comes with Google apps. I'll try his suggestion first and see if the phone still reboots a lot.
If the problem persists, I will try the solutions mentioned here. Thanks a lot!
elesbb said:
I didn't read everything but just wanted to say
VERY GOOD THREAD!
this is how threads should be done. Very descriptive, organized, told us everything you did and asked for help! Good job man! Only negative is it prolly should have gone in Q&A section but irregardless very good thread!
About your issue, I recommend flashing stock Odin tar file to everything back to stock and reroot and start over. Flashing stock will not lock it again it will remain unlocked. But should get you back up and fresh. Just be aware it will erase all your data and all of the internal SD card.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
After trying arocker's suggestion to not flash gapps, the phone still reboots. So now, I am going to try your solution guys.
But before I do, I want to make sure that I am on the correct paths/links.
Here's what I found for the following:
ODIN
forum.xda-developers.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539
I've had a couple of chances to use ODIN but only using specific functions like flashing a recovery file while the phone is in download mode. I don't however have any experience using ODIN to put the phone back to stock where the phone gets unrooted. Having the phone unrooted is fine by me as I only needed to have the phone unlocked.
Any step-by-step guides for using ODIN for this specific purpose guys? I don't want to mess this up again.
Thanks and sorry for the trouble.
dokgu said:
After trying arocker's suggestion to not flash gapps, the phone still reboots. So now, I am going to try your solution guys.
But before I do, I want to make sure that I am on the correct paths/links.
Here's what I found for the following:
ODIN
forum.xda-developers.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539
I've had a couple of chances to use ODIN but only using specific functions like flashing a recovery file while the phone is in download mode. I don't however have any experience using ODIN to put the phone back to stock where the phone gets unrooted. Having the phone unrooted is fine by me as I only needed to have the phone unlocked.
Any step-by-step guides for using ODIN for this specific purpose guys? I don't want to mess this up again.
Thanks and sorry for the trouble.
Click to expand...
Click to collapse
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
PanchoPlanet said:
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
Click to expand...
Click to collapse
Hello PanchoPlanet,
Thanks for the link. I went ahead and tried to unroot without Windows (Mobile Odin) as per the instructions on the link. I downloaded everything and went ahead to install the Mobile Odin APK. When I ran it to install the Flash Kernel, the app told me that the device is not supported.
To my understanding the guide is for M919 devices but should work for my wife's device as well (M919N - Metro PCS). I would like to try the guide for using Windows but I'm not really expecting for it to work or I might mess it up more. I'll try to search some more and provide the links where this forum will lead me to. But if you have any ideas, please let me know asap. Thanks!
PanchoPlanet said:
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
Click to expand...
Click to collapse
Ok, here's what I found:
forum.xda-developers.com/showthread.php?t=2446497
It seems like the perfect thread for what I am trying to achieve. Will let you guys know if it is successful. But it will have to wait for tomorrow. Gonna catch some sleep.
Okay, I'm running out of options. I was able to flash the stock ROM using Odin 3.07. The recovery looks like it came back to the stock recovery as I no longer have TWRP installed. When I install Root Checker, I see that I am no longer rooted. That's good.
But my original problem is still here. The phone reboots a lot. The phone is so unstable that it is barely usable.
I am now going to try one more thing.
I have a Galaxy S4 (I337M) from Rogers Canada (my wife has Metro PCS M919N). Mine got rooted and has CyanogenMod 10.2.1 as a custom ROM. My phone is working perfectly while hers reboots a lot. I was thinking it was because of a faulty battery. So I am doing an experiment by swapping the batteries. So far no reboots have occurred, but I will continue to monitor this.
Any ideas why the battery is kinda messed up?
This thread talks about battery stuff and reboots:
http://au.ibtimes.com/articles/530338/20131216/samsung-galaxy-s4-problems.htm
Batteries can go bad a lot of ways. Extreme temperature, factory defect, phone drops, moisture, etc.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
This thread talks about battery stuff and reboots:
http://au.ibtimes.com/articles/530338/20131216/samsung-galaxy-s4-problems.htm
Batteries can go bad a lot of ways. Extreme temperature, factory defect, phone drops, moisture, etc.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And 100% of the time, they eventually just get old.
dokgu said:
Okay, I'm running out of options. I was able to flash the stock ROM using Odin 3.07. The recovery looks like it came back to the stock recovery as I no longer have TWRP installed. When I install Root Checker, I see that I am no longer rooted. That's good.
But my original problem is still here. The phone reboots a lot. The phone is so unstable that it is barely usable.
I am now going to try one more thing.
I have a Galaxy S4 (I337M) from Rogers Canada (my wife has Metro PCS M919N). Mine got rooted and has CyanogenMod 10.2.1 as a custom ROM. My phone is working perfectly while hers reboots a lot. I was thinking it was because of a faulty battery. So I am doing an experiment by swapping the batteries. So far no reboots have occurred, but I will continue to monitor this.
Any ideas why the battery is kinda messed up?
Click to expand...
Click to collapse
That's a wierd situation, by swapping batteries you basically performed a battery pull, which acts as a reset, that in it self may have cleared your issue.
Now if battery is bad that could be an unusual problem. Maybe just replacing the battery will be the end of your mystery.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
The battery should be brand new as the phone was just recently purchased this April.
Anyways, so far no reboots have happened and any instability has not been shown at all. Everything looks ok, yet.
Anyone know if it is safe to swap batteries? Our phones have different S4 models. I'm not sure what the implications would be. Also what is this battery pull which acts as a reset? We've been pulling the battery a lot of times but the reboot still happens but not when we swapped batteries.
The batteries are all the same. Don't worry about that.
Even if its a new battery if could have just been bad. A manufacturing defect perhaps.
Sent from your phone. You should be more careful where you leave that thing.
dokgu said:
The battery should be brand new as the phone was just recently purchased this April.
Anyways, so far no reboots have happened and any instability has not been shown at all. Everything looks ok, yet.
Anyone know if it is safe to swap batteries? Our phones have different S4 models. I'm not sure what the implications would be. Also what is this battery pull which acts as a reset? We've been pulling the battery a lot of times but the reboot still happens but not when we swapped batteries.
Click to expand...
Click to collapse
This battery thing is wacky, anyway swapping batteries should not be a problem, it's just an energy storage container. Pulling the battery isn't like powering down the phone or resetting/rebooting ,sometimes devs request a battery pull to get the proper wipe effect that reboots can't provide.
You inadvertently solved your problem by accident. That's a good thing.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
PanchoPlanet said:
You inadvertently solved your problem by accident. That's a good thing.
Click to expand...
Click to collapse
I have quite literally solved the vast majority of my problems this way.
Its a preferred method.
Sent from your phone. You should be more careful where you leave that thing.
Sometimes it's that "total disconnect "of power that kind of gets all the ducks lined up in a row and everything flows in the dynaflow.
Good.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
its very important topics and it might seen for every galaxy s4 users.just wonderful topics.
This exact same thing happened on my mother's 6-month old S3. If you're still wondering, you could try putting the old battery and running a CPU stress test app. It should increase the current draw and trigger a shutdown.
EDIT: whoops, sorry to kind of zombie. Didn't check the date.
Sent from my Galaxy S4
Hey everyone, I'm Having trouble with tons of issues with my Sprint note 2 that came with version 4.4.2.
I've been struggling for weeks trying to fix this on my own so any help will be EXTREMELY appreciated.
Here's the problem:
-EVERY TIME i make a backup of ANYTHING it does not restore. I sit there waiting on the load up screen for over an hour about 6 times now. I have TWRP version 2.7.0.0 because the 2.7.1.0 does not work and will not work for me for some reason. To fix it i have to flash the complete stock rom on it like it comes from the factory with odin. Then i have to root the phone again and try it all over again. Please if anyone has any idea whats going on here please help!.. i tried recovering with almost every option and i cant find help anywhere! :crying:
-Now this is a big problem. Since i cant recover from my backup when i flash a new rom it is taking a lot of my time. i flash a rom to my device and every time i have no signal. Like i flashed Omni and Liquidsmooth for example and they work perfectly! except i have no signal!.. I've read some forums and they said to type in some numbers to call and reset your phone for latest Profile and crap but it says no signal obviously so i cant call anything. What I'm wondering here is if there is a fix to my problem. I flash my phone to stock every single night after i try and work on it for hours and hours so i can have service the next day at least. I've been doing this for 2 weeks straight and i'm kinda getting sick of it. And if i call sprint support to help get signal back to my device would i get in trouble or something because i'm using a custom rom? so they would most likely not help me?
-I also have an issue with my Sprint Airwave as when i root my phone or flash a rom it immediately stops working! I'm not to worried about that as much as the other issues i have . But i thought i would just throw that out there!
I hope someone knows some of these problems. Like i said ANY help will be greatly appreciated.
Please look into this issue for me as i have spent way to much time on this and i just want a rom on my dang phone ... Thanks for your time!
Have you tried using Philz Recovery instead of TWRP?
ANDROID...A New Digital Revolution Of Incredible Developers
askills said:
Hey everyone, I'm Having trouble with tons of issues with my Sprint note 2 that came with version 4.4.2.
I've been struggling for weeks trying to fix this on my own so any help will be EXTREMELY appreciated.
Here's the problem:
-EVERY TIME i make a backup of ANYTHING it does not restore. I sit there waiting on the load up screen for over an hour about 6 times now. I have TWRP version 2.7.0.0 because the 2.7.1.0 does not work and will not work for me for some reason. To fix it i have to flash the complete stock rom on it like it comes from the factory with odin. Then i have to root the phone again and try it all over again. Please if anyone has any idea whats going on here please help!.. i tried recovering with almost every option and i cant find help anywhere! :crying:
-Now this is a big problem. Since i cant recover from my backup when i flash a new rom it is taking a lot of my time. i flash a rom to my device and every time i have no signal. Like i flashed Omni and Liquidsmooth for example and they work perfectly! except i have no signal!.. I've read some forums and they said to type in some numbers to call and reset your phone for latest Profile and crap but it says no signal obviously so i cant call anything. What I'm wondering here is if there is a fix to my problem. I flash my phone to stock every single night after i try and work on it for hours and hours so i can have service the next day at least. I've been doing this for 2 weeks straight and i'm kinda getting sick of it. And if i call sprint support to help get signal back to my device would i get in trouble or something because i'm using a custom rom? so they would most likely not help me?
-I also have an issue with my Sprint Airwave as when i root my phone or flash a rom it immediately stops working! I'm not to worried about that as much as the other issues i have . But i thought i would just throw that out there!
I hope someone knows some of these problems. Like i said ANY help will be greatly appreciated.
Please look into this issue for me as i have spent way to much time on this and i just want a rom on my dang phone ... Thanks for your time!
Click to expand...
Click to collapse
I've had this same problem, I know a bit about flashing custom roms, but only cause i've learned through trial and error. I also have a note 2 on sprint, the L-9000. What I done was found a stock, or close to stock (something was changed cause it shows as custom in my phone instead of stock). that got my signal working again. But what I have read (and anyone that knows more than I do, which is going to be alot of people here, feel free to correct me) is, it has to do with your APN settings which seems to be telling the phone how to interact with the towers. so here is how I would handled it (if there are any devs that disagree by all means enlighten the both of us on this issue)
1. if you haven't already, get a custom boot loader like Clock Work Mod
2. flash stock rom
3. re-boot to boot loader
4. make back up of phone in functioning state and then copy over to your computer
5. download custom roms and tinker away. if you ever brick the phone or mess up and have no service, load the backup from step 4.