Related
I bought a Rezound on ebay, pre-rooted/unlocked with the leaked ICS / Sense 3.6 ROM (besides that, pretty much bone-stock)
I decided I wanted to try out a different ROM and make sure I am familiar with the process before I try to do the S-OFF process....
Well, I found that the first thing I needed to do to upgrade to (insert ICS/Sense 4 Rom here) was to upgrade to the newest Firmware (3.11.605.22), and I am currently on 3.11.605.01 ... I followed their instructions closely to update the firmware ( re-lock , load new FW as PH98IMG.zip , flash it , unlock, etc)
Well, that didn't work for me, when I got to loading up hboot and it automatically updating the FW, it didn't do what the instructions said it would, it showed a dark blue bar near the top/right, waited for that to complete, then same thing but yellow, that completed and asked to reboot, but would only reboot to fastboot...
eventually I unlocked it again and it allowed me to return to my ROM (normal ICS/sense 3.6)
Sorry about this short story... lol ^
Basically I cannot for the life of me install any rom with success... I can't even restore the nandroid I made last night (before any of this) with success..
the CLOSEST thing to success I got was installing newts One XxX sense 4 rom, it booted, and will sit on the lock screen just fine, but when I try to unlock and go to settings to turn off animations (like instructed) it will freeze and reboot....
DO I need to install the newest FW???
OR what do I need to dooo?
Pls help! I am fairly familiar with android, as I had a D Inc before this, evervolv ICS etc etc....
Thanks alot anyone !
x70xchallengerx said:
I bought a Rezound on ebay, pre-rooted/unlocked with the leaked ICS / Sense 3.6 ROM (besides that, pretty much bone-stock)
I decided I wanted to try out a different ROM and make sure I am familiar with the process before I try to do the S-OFF process....
Well, I found that the first thing I needed to do to upgrade to (insert ICS/Sense 4 Rom here) was to upgrade to the newest Firmware (3.11.605.22), and I am currently on 3.11.605.01 ... I followed their instructions closely to update the firmware ( re-lock , load new FW as PH98IMG.zip , flash it , unlock, etc)
Well, that didn't work for me, when I got to loading up hboot and it automatically updating the FW, it didn't do what the instructions said it would, it showed a dark blue bar near the top/right, waited for that to complete, then same thing but yellow, that completed and asked to reboot, but would only reboot to fastboot...
eventually I unlocked it again and it allowed me to return to my ROM (normal ICS/sense 3.6)
Sorry about this short story... lol ^
Basically I cannot for the life of me install any rom with success... I can't even restore the nandroid I made last night (before any of this) with success..
the CLOSEST thing to success I got was installing newts One XxX sense 4 rom, it booted, and will sit on the lock screen just fine, but when I try to unlock and go to settings to turn off animations (like instructed) it will freeze and reboot....
DO I need to install the newest FW???
OR what do I need to dooo?
Pls help! I am fairly familiar with android, as I had a D Inc before this, evervolv ICS etc etc....
Thanks alot anyone !
Click to expand...
Click to collapse
If you want to go back to a GB rom you need to reflash the boot image that came with it. If you want a sense 4.0 to work you need to flash the old firmware patch. For the patch I have attached it. Flash it via recovery and your rebooting on a sense 4.0 rom/ new firmware rom should be gone. (don't forget to follow the OP for Newts rom about disabling animations btw) for the boot images look to the op of the rom you are running.
cstrife999 said:
If you want to go back to a GB rom you need to reflash the boot image that came with it. If you want a sense 4.0 to work you need to flash the old firmware patch. For the patch I have attached it. Flash it via recovery and your rebooting on a sense 4.0 rom/ new firmware rom should be gone. (don't forget to follow the OP for Newts rom about disabling animations btw) for the boot images look to the op of the rom you are running.
Click to expand...
Click to collapse
Ok thanks for the reply, I did install the "old firmware patch" included with Newts XxX Sense 4 ROM, and I can successfully get the ROM to boot, it doesn't operate very well, and only for a few minutes because it will freeze and reboot. It doesn't allow me to get to the settings, no matter how fast I try to get there, it ALWAYS freezes before I can access the setting :/ ...
x70xchallengerx said:
Ok thanks for the reply, I did install the "old firmware patch" included with Newts XxX Sense 4 ROM, and I can successfully get the ROM to boot, it doesn't operate very well, and only for a few minutes because it will freeze and reboot. It doesn't allow me to get to the settings, no matter how fast I try to get there, it ALWAYS freezes before I can access the setting :/ ...
Click to expand...
Click to collapse
Hmm.. wow I'm lost. I had the same issues before I installed the patch, but after I didn't and it went fine. I'm going to have to think about this one for awhile.
cstrife999 said:
Hmm.. wow I'm lost. I had the same issues before I installed the patch, but after I didn't and it went fine. I'm going to have to think about this one for awhile.
Click to expand...
Click to collapse
Okay after flashing the ^above^ patch, the rom seems to work now, it didn't freeze so I was able to turn off animations and now it works might fine
Do you know by chance any good kernels for an ICS/Sense 4 ROM?
the stock one was draining faster than it was charging (while plugged in lol)
So I tried out the 1.836 OC kernel and it seems to be working fine, but I am interested more in battery life than performance right now, coming from the DInc, this phone is buttery smooth and doesn't REALLY need OC just yet (for me anyway)
Thanks for the help by the way!
I just flashed [ROM] (5/25) Nils' Business ICS 4.0.3 Sense 3.6 last night for my S-OFF ReZound. Everything went beautifully and the ROM looks great. The problem I think I have is whenever an app throws up a notification my phone reboots. I first noticed it whenever I sync'd my Google account and it threw up a notification about new gmail messages. So I stopped syncing Gmail. Then it happened whenever I tried to open Twitter/Facebook or when I adjusted the ringtone volume or my alarm went off.
Does anyone have an idea why these things would cause the phone to reboot? Are there any commonalities between these functions?
Weird. Not sure about that. The only rebooting I get on the ROM is when I use my Lock Screen App instead of using the power button. From what I understand though, that is a problem with ALL the ICS versions for Rezound. I can't wait until that is fixed...I hate trying to press that little power button through the small hole in the case I use.
Did you do a full wipe and then flash? Sounds like something residual from a previous ROM. If you did wipe and flash, did you restore anything in Titanium? It clearly states in the OP for that ROM not to do that.
yea i did a full wipe and flash twice. i havent installed or used Titanium to this point.
it first started happening when i attempted to sync my google account, which was about the 3rd thing i did after installing the ROM.
Someone for mad at me for telling them search the old firmware patch
Is suggest you do the same
If you can't find your sdcard or if your phone reboots when it makes a sound.... You need to flash the old firmware patch
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Someone for mad at me for telling them search the old firmware patch
Is suggest you do the same
If you can't find your sdcard or if your phone reboots when it makes a sound.... You need to flash the old firmware patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
if you're referring to the GB firmware patch, then I did do that during the ROM install process per the instructions. i can try doing that again though.
You are on gingerbread firmware correct?
I have read about the patch not working the first time so that could be the issue
Sent from my ADR6425LVW using Tapatalk 2
i did come from GB firmware, but flashed the RUU 3.14.605.5 and then flashed the GB firmware patch. after doing this and booting into the RUU, i then flashed Nil's ROM.
nalees said:
i did come from GB firmware, but flashed the RUU 3.14.605.5 and then flashed the GB firmware patch. after doing this and booting into the RUU, i then flashed Nil's ROM.
Click to expand...
Click to collapse
if you flashed the 3.14RUU, you shouldn't need the GB firmware patch since you are now on ICS.
I would reinstall the ROM and skip the patch.
oh ok! i will do that now.
*update 2*
rats, 5 minutes later, as i'm refreshing my twitter app, it reboots. going to see if it continues to replicate. so far it has. uninstalling and reinstalling it. /// still rebooting when i refresh twitter. weird.
nalees said:
oh ok! i will do that now.
*update 2*
rats, 5 minutes later, as i'm refreshing my twitter app, it reboots. going to see if it continues to replicate. so far it has. uninstalling and reinstalling it. /// still rebooting when i refresh twitter. weird.
Click to expand...
Click to collapse
When you went from gb and ran the ics ruu, did you run the ruu twice.? It only updates a few things the first time through. The second time it does all items on the list.
Sent from my Rezound
oh my, just read through Nil's instructions again and you're right, it does say to run it twice...
i only did the RUU once.
ok, so from here, I need to reflash the RUU one more time? and then reload Nil's ROM?
hmm, also noticed on step #10 i need to unlock the bootloader again? is this true even if i'm s-off?
I went from completely stock to S-OFF and running Nils' latest Business Sense 2 days ago. I have not had any of the problems you mentioned.
His instructions do no say to install the RUU twice. They say that it's a 2 pass affair to install it. If you went through the whole process to install it once, you don't need to do it again.
However, I agree with an earlier post. Installing a GB firmware patch after installing an ICS RUU is probably your problem. Re-doing the whole thing from Nils' instructions for "Latest Leak and Installation Instructions", and then just installing his v4.1 ROM is probably all you need to do to get straightened out.
You absolutely need to flash the RUU twice. The 2nd time it will appear to be stuck on one of the times and flash it like 10 times but that is normal.
nalees said:
hmm, also noticed on step #11 i need to unlock the bootloader again? is this true even if i'm s-off?
Click to expand...
Click to collapse
It says that in Step #10, I believe. And yes, you have to do that in order to install (or re-install, as the case may be) AR Recovery (Step #11).
---------- Post added at 02:10 PM ---------- Previous post was at 02:03 PM ----------
con247 said:
You absolutely need to flash the RUU twice. The 2nd time it will appear to be stuck on one of the times and flash it like 10 times but that is normal.
Click to expand...
Click to collapse
I started on Monday with a bone stock Rezound. I unlocked, rooted, and did the wire trick for S-OFF.
Then I flashed the 3.14 RUU once, unlocked again, installed AR Recovery again, and then flashed Nils' v4.1 ROM (for S-OFF).
My phone seems to be working fine. Exchange mail (I don't use Gmail), contacts, calendar and tasks. Visual Voice Mail. Notifications. Text messaging. Facebook. WiFi Tether. Google Maps. Camera. Bluetooth handsfree. Everything seems to work fine. The only thing I haven't tested yet, that I mean to, is to force it to 3G only for data and test that I can talk and surf the Web at the same time.
Since I did not flash the RUU twice, what should I be looking for to not work right?
Do not HTC unlock after s-off.
Edit: saw you did.... Basically you will have unlocked or re locked. If you wanted the bootloader to appear stock you have to s-on and do the s-off process again. Then it would say locked. Not a big deal.... Unless you are paranoid and have to do a warranty swap.
Sent from my Rezound
ericsignals said:
Do not HTC unlock after s-off.
Sent from my Rezound
Click to expand...
Click to collapse
yea, i was reading this thread and that's why i thought that...
http://forum.xda-developers.com/showthread.php?t=1620211&page=6
i'll do some more reading before i proceed.
Just tested the SVDO.
Went into Phone Info and set my phone to CDMA Auto (PRL).
Turned off WiFi.
Confirmed status bar displayed 3G.
Called up my bank and let the automated menu thing talk over speakerphone.
Ran Speedtest on phone and it worked.
Went into Phone browser, did a Google search and got results.
Turned on WiFi Tether on my phone.
Connected my TouchPad (running ICS) to phone hotspot.
Ran Speedtest on TP. Got 1934kbps down and 1945kbps up.
I'd say simultaneous voice and 3G data work just fine with Nils' ROM, too...
so i redid everything tonight the proper way and its up and running perfectly! loving it
nalees said:
so i redid everything tonight the proper way and its up and running perfectly! loving it
Click to expand...
Click to collapse
And that releives me. Have fun
Hi, it has been awhile since I have posted but I have been reading the forums and trying to keep up with things on my 3D. I have since un-rooted my 3D and have returned it to latest stock OTA updates. I did this because I was planning on maybe going to the next greatest phone
My question is pretty simple and involves the process of updating to the ICS when it becomes available...hopefully soon from what I am hearing. Anyways, Would it be best if I deleted any programs I have installed from the play store now? I mean just in case there are conflicts? Or should the update delete them and not reinstall them?
Please be kind...LOL!!!
If you want to update to ICS right now, by using the unofficial leaks, you'll have to re-root and install it that way. This would wipe all data on the phone when installing the new rom. No need to remove apps or data now or anything, but it's always a good idea to back up things you want to keep, just for safe keeping.
If you want to wait for the official ICS, I'm fairly certain that it will also wipe all data and apps on your phone, as it'll need to install a new firmware, which wipes all data on the phone.
No need to remove any apps and such before updating, as they'll automatically get removed anyways.
When you update, you can just install the apps again.
- Moon
Thanks Moon for the reply to this weak at best question...LOL!!! I can just remember at one time when I was flashing and stuff, that the user installed stuff just re-downloaded and installed on its own. I can;t remember if there was an opt out for that or not. I was just curious and like I said a pretty weak question but a great response. Thanks
Also note, if you use the unofficial ICS that everyone is basing their ROM's off of, you won't be able to go back to GB. you are stuck on ICS, but you can flash other ICS roms, just can't go back to Gingerbread.
felacio said:
Also note, if you use the unofficial ICS that everyone is basing their ROM's off of, you won't be able to go back to GB. you are stuck on ICS, but you can flash other ICS roms, just can't go back to Gingerbread.
Click to expand...
Click to collapse
Odd, because if you have the GSM 3D model then you can go back to gingerbread no problems. Even with the firmware update.
scariola said:
Odd, because if you have the GSM 3D model then you can go back to gingerbread no problems. Even with the firmware update.
Click to expand...
Click to collapse
+ 1 i nand back to 3.0 from time to time, no issue
felacio said:
Also note, if you use the unofficial ICS that everyone is basing their ROM's off of, you won't be able to go back to GB. you are stuck on ICS, but you can flash other ICS roms, just can't go back to Gingerbread.
Click to expand...
Click to collapse
Never heard of this on CDMA either. Maybe if you updated your firmware to the new Virgin Mobile one, but even then,I think you can downgrade to GB.
Sent from my ICS 3VO with Tapatalk 2
If you want to wait for the official ICS, I'm fairly certain that it will also wipe all data and apps on your phone, as it'll need to install a new firmware, which wipes all data on the phone.
Click to expand...
Click to collapse
I've never seen an OTA update wipe everything on the phone.
sitlet said:
I've never seen an OTA update wipe everything on the phone.
Click to expand...
Click to collapse
This has been my experience with OTA's as well. It seems that the user installed programs would automatically re-install and like I said there was an opt out at one time but I was not sure that it still existed.
I have a few odd ball programs mostly to do with fishing and stuff, like fishing status etc. and If I see or read that ICS is in fact ready to drop, I will probably go ahead and delete all user installed programs and return to full stock just in case. I have not heard of any problems with older programs on ICS but then again we don;t have the official so who knows.
Anyways thanks for not bashing me on this...:silly:
evomike77 said:
+ 1 i nand back to 3.0 from time to time, no issue
Click to expand...
Click to collapse
I've relocked my phone and used the RUU to go back GB twice now pretty easily. I think the issue was if you updated your firmware with the ICS leak, not the ROMs based on the leak.
baj24 said:
I've relocked my phone and used the RUU to go back GB twice now pretty easily. I think the issue was if you updated your firmware with the ICS leak, not the ROMs based on the leak.
Click to expand...
Click to collapse
Really?
I haven't actually tried it, but I read a few places that once you go to ICS via a ROM based on the leak, you are stuck on ICS ROM's.
Just to note, I've read this on the CDMA development area. Hmm, I'll have to try going back just to see myself, I like ICS, personally, but having options to go back is never a bad thing.
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
When I last rooted and ROM'd my GN2 it was shortly after the first OTA. I haven't touched it since then since it's been a great phone for me. I have been unhappy now for about a month with the performance and other issues. I have an issue that's requiring me to factory reset and since I will be basically losing everything anyway I want to update to the newest ROM.
Here's where I am now:
Android Version 4.1.1
Baseband Version I605VRALL4
Kernel Version 3.0.31-414933 [email protected] #1
Build Number JRO03C.I605VRALJB
Hardware Version I605.06
This is where I want to be: http://forum.xda-developers.com/showthread.php?t=2765021
I have the files downloaded and on my SDcard. I have the 4.3 MJ9 firmware ready to be flashed in Odin. But the post says I would only need that if I am coming from 4.1.2 (which I am not) so would that even be needed?
I can't seem to recall how can I tell if my bootloader is unlocked? I used the CASUAL root method originally. I have never had an issue with Root function so I know I am rooted still.
I have the PhilZ/CWM installed as my recovery.
I have a current backup to my sdcard.
Should I just flash as the thread says?
Thanks in advance and I've been at this for 5 hours now and in searching the forums for information about updating from 4.1.1 and there has been none. I've seen the "no posts found" page so many times I could throw my computer! haha!
Hey there,
Yeah you should have an unlocked bootloader since I used casual as well. Flash with Odin the firmware, they mention 4.1.2 because they assume everyone is already on that. You basically need the 4.3 firmware for all the new roms to ensure WiFi works specifically I believe while radios will still work.
So once you Odin you can flash the tw 4.4.2 ROM and expect it all to work. If you have been wanting to try stock aosp 4.4.4 now is a good time, they have gotten very stable since our phone has official cyanogen support.
Good luck
Yeah I followed a post from the thread that was a long process. I flashed 4.1.2 stock. Re-casual rooted. Then flashed 4.3 and the firmware. Then did the 4.4.2 radio and such. It was like a 4 hour process.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Well I had good luck yesterday but now seem to be having issues. And I can't screen shot so I don't know what to do.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Can you describe your issues the best you can?
Sent from my SCH-I605
When I plug in a headset or take out the S pen I get a consistent message about Pagebuddy closing. It won't stop popping up until I put the pen back or unplug the headset. I disabled pagebuddy in the settings hoping that would stop it. I cleared the cache and data from the app and also went into recovery and wiped cache. It was working fine for the first day. Then just started erroring.
Sounds like you have an app installed that's not playing nice. I would use Titanium Backup and freeze all user apps, then unfreeze one at a time to find the culprit
Sent from my SCH-I605
Today it stopped doing it. No messages for a headset plugged in or S-pen removed. I don't know what happened.
Verizon Note 2
Nebula 4.4.2