I'm sure this is a noob question, but can you update a rom (unnamed) using the update zip if you skip an update. I'm at 1.0.4 and I want to update, but it looks like the update says v1.1.0-v1.2.0, so does this mean I can't use it to go from 1.0.4 directly to 1.2
I've got a ton of apps on, so I'd rather not factory wipe if I can help it.
Gtg uses non-wipe installs for this reason (I think). You can't use the 1.1.0 to 1.2 update, but you can use the full 1.2 package, and you shouldn't lose your apps.
But, you may want to back up beforehand to be safe.
Sent from my Galaxy S II (i777)
I'm at UnNamed v1.1.0 currently and want to update to 1.2.
What I'm unclear on is the Wipe data step. Do I need to do that if I'm using the appropriate update zip or is that just in the instructions for clean/new installs of the full zip?
Better yet, what exactly does that step even do? Does that clear personal/saved data or program data like settings?
Knips178 said:
I'm at UnNamed v1.1.0 currently and want to update to 1.2.
What I'm unclear on is the Wipe data step. Do I need to do that if I'm using the appropriate update zip or is that just in the instructions for clean/new installs of the full zip?
Better yet, what exactly does that step even do? Does that clear personal/saved data or program data like settings?
Click to expand...
Click to collapse
That step clears your rom wipes anything on that rom, if you are running 1.10 all you have to do is flash the update zip 1.10-1.20 (not the full zip) and reboot its easy, i did it last night
the full version is if you are coming from a different rom or want to do a fresh install
Worked like a charm. Thanks
anyone try the NFC option?
i went straight from 1.0.4 to 1.2 without any issues.
Dave7 said:
i went straight from 1.0.4 to 1.2 without any issues.
Click to expand...
Click to collapse
No apparent issues. gtg456x said you should install 1.2.0 full without a wipe rather than skip over an update.
creepyncrawly said:
No apparent issues. gtg456x said you should install 1.2.0 full without a wipe rather than skip over an update.
Click to expand...
Click to collapse
+1
You may be missing features or some stuff that you just don't know of yet. Just flash the full rom without a wipe. It is just as easy as doing the update. It only takes a little while longer to download.
Fair enough...
I guess that is one problem with a thread that has 1400+ replies. If critical info is not in the first post it is easily skipped. I even tried searching the thread to see if there was a mention of the "proper" procedure.
Dave7 said:
Fair enough...
I guess that is one problem with a thread that has 1400+ replies. If critical info is not in the first post it is easily skipped. I even tried searching the thread to see if there was a mention of the "proper" procedure.
Click to expand...
Click to collapse
Just read the last few pages. Its mentioned several times.
Sent from my HTC PH39100
well, since i have time to waste I looked at the thread from the time the latest update was made until the time I did my update. No mention (in that time period) that you should do a full install and not the update.
"the last few pages" is full of posts made after I downloaded flashed the update. I still stand by what I said, 1400+ posts, when most are semi off topic or stupid questions, is A LOT to fish through for a basic install question.
No worries, just did the full install and all went well.
Yes, adding this little detail to the first post would be the best. I have this same problem and had to search the forums for a while before finding this thread. Should save time for a lot of people who don't follow the thread daily for updates.
Just my two cents - I was on this rom and noticed that after receiving a txt message, all notifications would play out of the front ear speaker, and not the rear speaker. I searched the unnamed dev forum high and low for a post on this and did not find an answer, but did see a post from a user with the same issue. Just curious if anyone else ran into this. Since switched to MIUI but loved unnamed and would really like to switch back, but I found the notifications issue a deal breaker...
Related
Ok, this is a very noob question, yeah yeah.
I rooted my tab last night (first root) did the backups and everything is all good. I must really commend the developers and forum members as this was incredibly easy. You guys do great work.
This evening I flashed the bonsai mod. I followed the thread step by step. After the install I flashed the kernel update as well.
The thing is, I just don't see a difference. I don't see any release notes on bonsaigeek so I'm not sure what to expect. I was expecting, however, to reboot the tab to a blank homepage, no apps installed or anything. But everything is the same. My home pages are set up identically, I still have all my apps installed.
I wiped cache/dalvik. my kernel version says 2.6.36.4-bonsai and my build number is Bonsai_v0.1.5 P7510UEKF3
So...what should I be looking for here?
pandamaja said:
Ok, this is a very noob question, yeah yeah.
I rooted my tab last night (first root) did the backups and everything is all good. I must really commend the developers and forum members as this was incredibly easy. You guys do great work.
This evening I flashed the bonsai mod. I followed the thread step by step. After the install I flashed the kernel update as well.
The thing is, I just don't see a difference. I don't see any release notes on bonsaigeek so I'm not sure what to expect. I was expecting, however, to reboot the tab to a blank homepage, no apps installed or anything. But everything is the same. My home pages are set up identically, I still have all my apps installed.
I wiped cache/dalvik. my kernel version says 2.6.36.4-bonsai and my build number is Bonsai_v0.1.5 P7510UEKF3
So...what should I be looking for here?
Click to expand...
Click to collapse
Bonsai rom is in early development and there are no visible changes to the user at the moment. All changes are backend or kernel related. You should notice a smoother snappier system but at this point in development its still basically a "stock" rom. Over time as the rom continues to develop im sure you will see more changes. Everything remained setup as wiping cache/dalvik does not erase any apps or settings.
Well thank you very much sir
Sent from my GT-P7510 using XDA Premium App
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Are you a Tmobile user?
Double0EK said:
Are you a Tmobile user?
Click to expand...
Click to collapse
Yeah. Even tried a new simcard even though I didnt think it would do any good.
toyoter91 said:
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Click to expand...
Click to collapse
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
mrmako777 said:
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
Click to expand...
Click to collapse
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
toyoter91 said:
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
Click to expand...
Click to collapse
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
mrmako777 said:
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
Click to expand...
Click to collapse
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Having a similar problem
toyoter91 said:
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Click to expand...
Click to collapse
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
BillyD325 said:
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
Click to expand...
Click to collapse
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
antiquezip said:
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
Click to expand...
Click to collapse
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
BillyD325 said:
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
Click to expand...
Click to collapse
I had this error factory reset stop the error.
This belongs in Q&A.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
Hi,
Not sure where to report this kind of thing but I seem to be getting frequent lockups on my S2 with the Resurrection Remix 3.1.3 that I wasn't getting with the previous 3.1.2.
abc.mikey said:
Hi,
Not sure where to report this kind of thing but I seem to be getting frequent lockups on my S2 with the Resurrection Remix 3.1.3 that I wasn't getting with the previous 3.1.2.
Click to expand...
Click to collapse
You mean freezes and/or fc's? You actually have to ask in the RR-thread, but I understand you only have posted 8 posts for now.
Remember RR 3.1.3 is still very new and under development, and isn't as stable as 3.1.2 is. If you want more stability, flash the 3.1.2-version.
And did you flash it with a full wipe? It's a must.
Sent from the Matrix
abc.mikey said:
Hi,
Not sure where to report this kind of thing but I seem to be getting frequent lockups on my S2 with the Resurrection Remix 3.1.3 that I wasn't getting with the previous 3.1.2.
Click to expand...
Click to collapse
The normal procedure would be to first read through the posts on the roms dev thread and see if others have had same issue and what (if any) solution is. if you dont see any comments then make one of your own explaining issue (You wont be able to do this until you have 10 posts).
Before leaving any replies on topic you should try doing a wipe/factory reset in recovery then boot to system see if you have same issues. Its advised to wipe recovery before each rom flash (Unless you have stock kernel, If you have stock rom/kernel you need to flash custom kernel before wiping. You can mostly ignore wiping if you are updating to new version of same rom however its still advised as somtimes can lead to issues.
You dont need to worry about apps/appdata and sms etc as you can easily backup them with Titanimum Backup Pro and SMS Backup etc. Get pro version of TB as you can batch backup/restore app/appdata in one go.
Donnie Sins said:
You mean freezes and/or fc's? You actually have to ask in the RR-thread, but I understand you only have posted 8 posts for now.
Remember RR 3.1.3 is still very new and under development, and isn't as stable as 3.1.2 is. If you want more stability, flash the 3.1.2-version.
And did you flash it with a full wipe? It's a must.
Sent from the Matrix
Click to expand...
Click to collapse
Thanks for the replies!
It freezes as in apps start becoming more and more unresponsive, sound if playing starts to stutter more and more until it ceases playing at all and phone us completely unresponsive except to a long hold if the power button. Sorry but I don't know what FC is.
I upgraded because the notifier informed me that there was a new ROM; I see now that it's a good idea to wait a bit now. I've downgraded to 3.1.2 which I've been very impressed with the responsiveness and stability of.
My first attempt at installing 3.1.3 was an attempt at an upgrade but didn't work very well as I think I followed the wrong procedure. But the issues I was having were with a wipe and reinstall following all the steps in the manual plus an undocumented one to install the keyboard patch for the S2 to make the keyboard work at all.
TheATHEiST ok will try reporting there next time, hopefully my post count will allow it by that time
TheATHEiST said:
The normal procedure would be to first read through the posts on the roms dev thread and see if others have had same issue and what (if any) solution is. if you dont see any comments then make one of your own explaining issue (You wont be able to do this until you have 10 posts).
Before leaving any replies on topic you should try doing a wipe/factory reset in recovery then boot to system see if you have same issues. Its advised to wipe recovery before each rom flash (Unless you have stock kernel, If you have stock rom/kernel you need to flash custom kernel before wiping. You can mostly ignore wiping if you are updating to new version of same rom however its still advised as somtimes can lead to issues.
You dont need to worry about apps/appdata and sms etc as you can easily backup them with Titanimum Backup Pro and SMS Backup etc. Get pro version of TB as you can batch backup/restore app/appdata in one go.
Click to expand...
Click to collapse
I can confirm that I have followed all the procedures (flashed at least 20 differet roms by now) and can also confirm that I have been facing a laggard and slow responsiveness throught out the rom, with couple of FCs and lockups as well. At least thrice I had to force reboot. Also I have done an extensive search and the only thread I could see on the similar issue was this.
I am posting here because of same reason as OP as I have a low post count but I have been following xda for over 2 years now.
I know the obvious answer is to downgrade to 3.1.2 or not install RR at all. This is "just reporting", you know!
Thanks!
Hey, I am also experiencing the same thing as the OP and 7mojo. My S2 would randomly freeze and the only way to get it working is a hard reboot. It happens randomly but quite often, I would say atleast 3 times a day. I have done a full wipe and re-install but no luck. Like 7mojo said, I too have searched the web and the only thing relating to this issue is this thread. Anyone else having this problem? any solutions? I hope there is an update soon.
Nevethen5 said:
Hey, I am also experiencing the same thing as the OP and 7mojo. My S2 would randomly freeze and the only way to get it working is a hard reboot. It happens randomly but quite often, I would say atleast 3 times a day. I have done a full wipe and re-install but no luck. Like 7mojo said, I too have searched the web and the only thing relating to this issue is this thread. Anyone else having this problem? any solutions? I hope there is an update soon.
Click to expand...
Click to collapse
I've had similar problems.. am guessing its due to bugs in the unstable rom. Will have to wait for the dev to release an update. For the time being, better stick with 3.1.2.
As for me, I switched to JellyBAM. And then to CM10.1. And then to Omega.
"To err is human, to forgive is divine"
Sent from my SGS II
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
The phone has been working great on Android 4.1.2 as I describe in the thread ( Optimizing [Rom][I605VRAMC3][4.1.2])
Found Here: http://forum.xda-developers.com/note-2-verizon/help/rom-optimizing-t2817294
EXCEPT NOW, every time I boot the phone, I get a message that says All the APPS are upgrading automatically . I think the problem is related to me Using Titanium Backup to Freeze SDM 1.0 . The reason I froze SDM 1.0 was to stop the Nag from Verizon for a firmware update .
Anyone know what I need to freeze to stop the auto upgrading on every boot? It really slows down the boot time.
Thanks in advance
You probably did this already, but double check to make sure Play Store is not set to Auto Update apps. Can. be found in Play Store. settings. I don't believe that freezing SDM would play a role here, but I've been wrong before.
Sent from my SCH-I605 using XDA Premium 4 mobile app
mattnmag said:
You probably did this already, but double check to make sure Play Store is not set to Auto Update apps. Can. be found in Play Store. settings. I don't believe that freezing SDM would play a role here, but I've been wrong before.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks , Play Store was set to auto update so I changed it , I just tried your suggestion and I rebooted . I'm still getting the same message while booting: Android is updating.............................................................................
doctor-cool said:
Thanks , Play Store was set to auto update so I changed it , I just tried your suggestion and I rebooted . I'm still getting the same message while booting: Android is updating.............................................................................
Click to expand...
Click to collapse
Hmmmm.... It's probably still working on updating apps that it started working on previous to disabling the auto update.
This might work..... Toggle off your wifi and data, then try going to phone Settings, Application manager, All Apps... then force close the Play Store and wipe the app data. Then open the Play Store again and it should go straight to settings area. Set it to " Do not Auto Update apps " and then back out of Play Store, turn wifi/data back on, and go back into Play Store and sign into the app again/change any other settings back to how you like them . I hope that will stop the auto update.
Sent from my SCH-I605 using XDA Premium 4 mobile app
mattnmag said:
Hmmmm.... It's probably still working on updating apps that it started working on previous to disabling the auto update.
This might work..... Toggle off your wifi and data, then try going to phone Settings, Application manager, All Apps... then force close the Play Store and wipe the app data. Then open the Play Store again and it should go straight to settings area. Set it to " Do not Auto Update apps " and then back out of Play Store, turn wifi/data back on, and go back into Play Store and sign into the app again/change any other settings back to how you like them . I hope that will stop the auto update.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Everything worked just like you predicted except when I reboot the phone it says "Android is updating 1,2,3..........................................88 ...................................
doctor-cool said:
Everything worked just like you predicted except when I reboot the phone it says "Android is updating 1,2,3..........................................88 ...................................
Click to expand...
Click to collapse
For a test,
I cleared data and disabled the Play Store, Turned off data and wifi . REBOOTED I'm still getting the same message while booting: Android is updating.......................................... ...................................
Now I'm thinking the problem is due to me flashing Gapps.
I flashed (HDPI / MDPI / TINY: gapps-jb-20121011-signed.zip) for Android 4.1.1 – 4.1.2 – Jelly Bean, from http://www.teamandroid.COM/gapps/
I probably shouldn't have flashed it on top of the official stock 4.1.2 Verizon ROM. I probably have two version of Gapps on my phone competing with each other. The quickest thing would probable be to re-flash to the OEM [Rom][I605VRAMC3][4.1.2]
doctor-cool said:
Everything worked just like you predicted except when I reboot the phone it says "Android is updating 1,2,3..........................................88 ...................................
Click to expand...
Click to collapse
Ok.... I just realized that this has nothing to do with the Play Store App or updating your apps.... Your actual phone system is optimizing at boot screen.... like this pic, right?
Sent from my SCH-I605 using XDA Premium 4 mobile app
I'm not in any way a developer or expert.... this stuff is just a hobby for me...so please understand these are just my thoughts to hopefully help and not make things worse for you. With that said, I suspect you have an app or script (or something) that is doing something like wiping the Dalvik cache with each reboot, which is triggering your phone to run through the optimization process each time you boot. I am pretty confident this has nothing to do with SDM being frozen. I'm not sure about gapps with stock. Why do you need that if your running stock?
Sent from my SCH-I605 using XDA Premium 4 mobile app
Anyhow, What ROM do you recommend ? I'm using my phone to do Wave Accounting and Pay Pal transactions so I cant have down time.
doctor-cool said:
Anyhow, What ROM do you recommend ? I'm using my phone to do Wave Accounting and Pay Pal transactions so I cant have down time.
Click to expand...
Click to collapse
Sorry for being off base with my initial thought on your above post... It's been a long week at work and I'm tired.... so that's my excuse...
I hope you get it sorted out with what's causing your phone to upgrade/optimize apps at each reboot. I did a Google search just now and apparently, this is common issue asked on XDA. I found several comments from people saying they think something causes the Dalvik/Cache to get wiped on reboot. I also read where someone reported that flashing Gapps did the same thing to them. If you're going to flash a new ROM, that should take care of the problem when you wipe things for the new flash.
On the XDA forums, it's generally frowned upon to ask for ROM recommendations. But for me personally, I have decided to settle (for now) on Beanstown106's JellyBeans ROM Build 22 which is based off of 4.1.2. I think this was the last 4.1.2 based Rom (for our SCH-I605's) that he did for his JellyBeans ROM before he moved on to developing for 4.3 MJ9, so I think a lot of the bugs were worked out of it.
I love the ROM and I've tried out several others. I always end up coming back to it because it's really stable and (pretty much) everything works. And with Xposed Modules and his built in options, I can tweak everything to how I like it.
You can still grab his older JellyBeans ROM build 22 by going to the current Alliance Rom Thread here: ( http://forum.xda-developers.com/showthread.php?t=2032447 ), and then going to the "Downloads" area right above the thread title. The ROM Filename is: note2_JellyBeans_B22.zip.
There's tons of great ROM's for our phone and there's so many talented developers..... so I truly think you have to read through the threads on each of the ROM's to make a decision for your personal needs... but I know that JellyBeans Build 22 is very stable if that's what you're wanting. If you decide to try out JellyBeans Build 22, let me know if you need help with instructions for flashing it. I saved the install instructions for future reference when I flashed it the first time last year, but I don't see those old install instructions any place now that he's moved on to developing for the updated 4.3 build.
mattnmag said:
Sorry for being off base with my initial thought on your above post... It's been a long week at work and I'm tired.... so that's my excuse...
I hope you get it sorted out with what's causing your phone to upgrade/optimize apps at each reboot. I did a Google search just now and apparently, this is common issue asked on XDA. I found several comments from people saying they think something causes the Dalvik/Cache to get wiped on reboot. I also read where someone reported that flashing Gapps did the same thing to them. If you're going to flash a new ROM, that should take care of the problem when you wipe things for the new flash.
On the XDA forums, it's generally frowned upon to ask for ROM recommendations. But for me personally, I have decided to settle (for now) on Beanstown106's JellyBeans ROM Build 22 which is based off of 4.1.2. I think this was the last 4.1.2 based Rom (for our SCH-I605's) that he did for his JellyBeans ROM before he moved on to developing for 4.3 MJ9, so I think a lot of the bugs were worked out of it.
I love the ROM and I've tried out several others. I always end up coming back to it because it's really stable and (pretty much) everything works. And with Xposed Modules and his built in options, I can tweak everything to how I like it.
You can still grab his older JellyBeans ROM build 22 by going to the current Alliance Rom Thread here: ( http://forum.xda-developers.com/showthread.php?t=2032447 ), and then going to the "Downloads" area right above the thread title. The ROM Filename is: note2_JellyBeans_B22.zip.
There's tons of great ROM's for our phone and there's so many talented developers..... so I truly think you have to read through the threads on each of the ROM's to make a decision for your personal needs... but I know that JellyBeans Build 22 is very stable if that's what your wanting. If you decide to try out JellyBeans Build 22, let me know if you need instructions for flashing it. I saved the install instructions for future reference when I flashed the first time last year, but I don't see those old install instructions any place now that he's moved on to developing for the updated 4.3 build.
Click to expand...
Click to collapse
Thanks and right on time, After I did my return to stock I thought I needed to wipe both caches' and the system to be able to do a Titanium backup.
I lost my operating system and Odin didn't recognize my phone, I was looking for a 4.1.2 zip file at the time I found your post. THANKS!
I'm downloading now
doctor-cool said:
Thanks and right on time, After I did my return to stock I thought I needed to wipe both caches' and the system to be able to do a Titanium backup.
I lost my operating system and Odin didn't recognize my phone, I was looking for a 4.1.2 zip file at the time I found your post. THANKS!
I'm downloading now
Click to expand...
Click to collapse
When you say you returned to stock, I'm hoping you didn't ODIN flash a full stock version of 4.1.2, because that would have relocked your bootloader and removed the custom recovery and root. If you were able to use Advance wiping features, you must still have some sort of custom recovery on your phone.
Hopefully, you do so you can flash a zipped ROM back onto it. If you've still got an unlocked bootloader and have a custom recovery, you may want to try to flash this root/modified version of "stock" 4.1.2:
( http://forum.xda-developers.com/showthread.php?t=2261478 ). It was also made by Beanstown106 and the thread still has instructions.
Also, you may do some Google searching to find tips on how to get your computer/ODIN to recognize your phone in download mode again... the most common tips I've seen are to try to uninstall and reinstall the Samsung drivers on your computer...and to try different USB cables and different USB ports on the computer.
I'm exhausted and I'm going to bed, but here are the original install instructions posted by Beanstown106 for JellyBeans ROM Build 22 if needed.
------------------------
"(INSTRUCTIONS) YOU MUST BE UNLOCKED
Step 1-
Make sure u are unlocked
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom (flash it in your custom recovery)
Step 4-
Reboot and Enjoy!"
-------------------------------------
Hope that helps. (Also, if Beanstown's stuff helps you... I'd encourage you hitting the thanks button for all his hard work )
mattnmag said:
When you say you returned to stock, I'm hoping you didn't ODIN flash a full stock version of 4.1.2, because that would have relocked your bootloader and removed the custom recovery and root. If you were able to use Advance wiping features, you must still have some sort of custom recovery on your phone.
Hopefully, you do so you can flash a zipped ROM back onto it. If you've still got an unlocked bootloader and have a custom recovery, you may want to try to flash this root/modified version of "stock" 4.1.2:
( http://forum.xda-developers.com/showthread.php?t=2261478 ). It was also made by Beanstown106 and the thread still has instructions.
Also, you may do some Google searching to find tips on how to get your computer/ODIN to recognize your phone in download mode again... the most common tips I've seen are to try to uninstall and reinstall the Samsung drivers on your computer...and to try different USB cables and different USB ports on the computer.
I'm exhausted and I'm going to bed, but here are the original install instructions posted by Beanstown106 for JellyBeans ROM Build 22 if needed.
------------------------
"(INSTRUCTIONS) YOU MUST BE UNLOCKED
Step 1-
Make sure u are unlocked
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom (flash it in your custom recovery)
Step 4-
Reboot and Enjoy!"
-------------------------------------
Hope that helps. (Also, if Beanstown's stuff helps you... I'd encourage you hitting the thanks button for all his hard work )
Click to expand...
Click to collapse
Thanks I used JellyBeans ROM build 22 just to have a system so that I could get to Odin. Then I did flash the full stock version of 4.1.2 then I used the Casual method to unlocked the boot-loader and reinstall WIN recovery and root. As explained here http://forum.xda-developers.com/note-2-verizon/help/rom-optimizing-t2817294. ( I ran into some driver issues between Casual and Odin but they were resolved)
Actually I have three Samsung i605's.
I have one that has got all the Verizon OTA updates, never tampered with it's on 4,4,2.
I have the one we have been talking about I have restored it to the fully stock version of 4.1.2 with Root.
And the last one I am experimenting with DN3 (Ditto Note 3) for fun and knowledge.
doctor-cool,
That's great. Glad you got it fixed.
And that's pretty cool to have extra devices to work with. Must be nice.
Sent from my SCH-I605 using XDA Premium 4 mobile app