Related
Okay, so I was unrooting my droid incredible and it brought it to stock 2.1 i was trying to install the update.zip to update it to 2.2, but it wasnt working...so i tried installing the 2.2 RUU onto it...and now when i try to turn on my phone it always boots into the Bootloader...what should i do?
Note: LED charging light still comes on, and i can still go into recovery(stock recovery though since my phone is no longer rooted)
If theres no way to fix it, can i just play dumb and tell verizon its not starting up, because doesnt HTC have to reflash everything anyway for security purposes....the only downside though is they would probably send me an SLCD Incredible
First and foremost, your phone is not bricked... not even close.
Simply try reinstalling the 2.1 RUU. Being that it's signed by HTC, you should be able to do what you need to in the stock recoveryThat being said, your update.zip probably failed because your phone was restored to a state prior to the May OTA. Without being at the correct software version, you cannot use the update.zip to install Froyo.
If you get the bootloader, you should be ok. I think the zip has to be on the root of the SD and named update.zip for the stock recovery.
Sent from my DInc
Look in the android development forum for "the ultimate back to stock thread". download the "PB31IMGxxxxx" file there, rename it to just PB31IMG.zip and put it on the root of your sd card. Go into the bootloader and let it run the update. This will bring you back to a 2.2 stock. From there you can re-root and do whatever else you like.
Sent from my ADR6300 using XDA App
Okay, well it was the get back to stock thread that i followed...and i know that i was trying to do the update.zip from a version of android that was too old, because i was the one who posted a thread a few months back with the update.zip in it. However, i was obviously stupid enough to not save teh "May" OTA and now the link is dead. Some people were reporting however that it still worked without it, so i wanted to see for myself.
In any case, it seems that a 5 hour battery pull seemed to do the trick, go figure. Can someone explain to me what a battery pull on this kind of stuff makes a difference and why the length of time sometimes makes a difference as well?
So... I seen baconbits shortly after rooting and flashing, I installed baconbits, phone booted, than right from start up I get forceclose on every app and process... than I tried to do a backup, I got an error on cwm so than I wiped data and tried to reflash fresh and start over, that would not work. So I recovered the stock froyo and fixed cwm than I flashed fire and ice cm7 rom.. everything has been fine since I fixed it.. it was still frustrating tho..
But when ever I go to my boot loader before recovery, I get this green font that says blah blah blah not found (its trying to locate files to install that stock froyo, but after it doesn't locate the file I'm free to access recovery or do whatever.. is there a way to delete that "cannot find" ****, it takes about 20 seconds from holding power and volume down to give me control.. that's why I want it gone its annoying.. even if I can't fix it, I guess its not a major setback..
melodicjunkie said:
So... I seen baconbits shortly after rooting and flashing, I installed baconbits, phone booted, than right from start up I get forceclose on every app and process... than I tried to do a backup, I got an error on cwm so than I wiped data and tried to reflash fresh and start over, that would not work. So I recovered the stock froyo and fixed cwm than I flashed fire and ice cm7 rom.. everything has been fine since I fixed it.. it was still frustrating tho..
But when ever I go to my boot loader before recovery, I get this green font that says blah blah blah not found (its trying to locate files to install that stock froyo, but after it doesn't locate the file I'm free to access recovery or do whatever.. is there a way to delete that "cannot find" ****, it takes about 20 seconds from holding power and volume down to give me control.. that's why I want it gone its annoying.. even if I can't fix it, I guess its not a major setback..
Click to expand...
Click to collapse
thats internal feature of Hboot... it looks for pc10img.zip on sd card.... not at all an error....
and it can be useful in a situation where you mess up your recovery and rom ... you would be able to save your phone via that ....
also its used to go back to stock rom and unroot when needed
+1 for hispeedword. Best possible answer right there - that's exactly what's going on. Use ROM Manager to reboot straight to recovery from now on and it will skip HBOOT so you don't have to wait through all of that. CM and most other roms also allow that option when you hold down the power button.
Now, you said "shortly after rooting and flashing" - what exactly did you flash? You do know baconbits is ONLY meant to be used with the stock rom right? The exact one that you rooted and that came on your phone. If you flash ANY other rom - even a 'stock rooted rom' then you run into tons of errors when flashing baconbits.
Dont flash baconbits, its not needed
Sent from my HTC Vision using XDA App
TheMod'sPolice said:
Dont flash baconbits, its not needed
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yeah I was being stupid, I didn't even know at the time when my phone messed up that it was from me flashing baconbits...until I did a back up, than flashed a different rom and reflashed baconbits, lmao..
so your saying to use baconbits if you rooted but didn't flash custom roms, than it works fine?
I'm thinking of switching to a sense rom, I don't even know why.. what are the pros/cons of sense? Thanks.
Assuming you've already answered your question up there, sense roms usually consume more battery life because of the plethora of constantly active widgets. However, if you're VERY social or buisiness, Id recommend it. The battery drain only cuts down on a few hours, depending on your usage, cpu governers and radio, and for that, you get a lot of functionality from the rom. Plus the new elegant blues ported theme for sense roms is just gorgeous. I also like the whole manual link to facebook in the contacts. Still hoping for a port for that xP try it out.
Sent from my HTC Vision using XDA Premium App
This afternoon I received my replacement phone from Asurion and like and good Android user, I attempted to root it with the Universal root method that had worked really well on my old phone. For some reason, the root did not work and I attempted to restore the phone to stock using the PC36IMG for 3.70 to go along with the 2.10 hboot. Everything seemed to have gone fine until the phone booted up. After a few minutes, it froze and rebooted itself. On top of that, when it does boot it recognizes neither the sdcard nor usb.
I can get into the bootloader and seem to have access to the sdcard from there but any attempts I've made to adb into it have come up with a "no device found" error.
If I attempt to go into recovery, it reboots then goes to the screen with the evo with the red exclamation point on it.
I have no idea what could be the problem or even where to go to try to fix it. I've tried searching the forums but anything I can find about reboots usually has to do with custom roms and any solutions to the other problems seem to revolve around being to adb into the phone while its booted up which does not work due to the lack of usb.
Check k2buckleys post out HERE n report back.
hgelpke said:
This afternoon I received my replacement phone from Asurion and like and good Android user, I attempted to root it with the Universal root method that had worked really well on my old phone. For some reason, the root did not work and I attempted to restore the phone to stock using the PC36IMG for 3.70 to go along with the 2.10 hboot. Everything seemed to have gone fine until the phone booted up. After a few minutes, it froze and rebooted itself. On top of that, when it does boot it recognizes neither the sdcard nor usb.
I can get into the bootloader and seem to have access to the sdcard from there but any attempts I've made to adb into it have come up with a "no device found" error.
If I attempt to go into recovery, it reboots then goes to the screen with the evo with the red exclamation point on it.
I have no idea what could be the problem or even where to go to try to fix it. I've tried searching the forums but anything I can find about reboots usually has to do with custom roms and any solutions to the other problems seem to revolve around being to adb into the phone while its booted up which does not work due to the lack of usb.
Click to expand...
Click to collapse
When you enter recovery, and get the red triangle screen, adb should recognize the phone from there. Also, if you set the phone into 'fastboot' mode, from the bootloader, does fastboot see the device?(fastboot devices) As blake directed you to another post of mine, you see one of the questions is if you are S on or S off. Whats the result there?
also, not sure if some of this may help or not, because you're phone is freezing up, but see this thread in regards to SD card and USB not being recognized.
Whatever the issue is, Z4root also causes the phone to freeze/reboot almost immediately as I run it. I think the problem is that some files got flashed during the attempted root that are still lingering a causing the issues. By all accounts the phone is restored to stock in that it reads the PC36IMG file just fine and restores everything that needs to be restored. It even says that recovery is restored. The problem is that recovery is not restored at all.
I'm quite baffled by it. If I can't fix it, I was hoping to bring it into Sprint for an exchange since it does show s-on and appears to be completely stock. My concern is that it is in asurion replacement and if they send it off, are they going to discover something when it gets back to them, I don't want to get hit with a large sum of $$$.
hgelpke said:
Whatever the issue is, Z4root also causes the phone to freeze/reboot almost immediately as I run it. I think the problem is that some files got flashed during the attempted root that are still lingering a causing the issues. By all accounts the phone is restored to stock in that it reads the PC36IMG file just fine and restores everything that needs to be restored. It even says that recovery is restored. The problem is that recovery is not restored at all.
I'm quite baffled by it. If I can't fix it, I was hoping to bring it into Sprint for an exchange since it does show s-on and appears to be completely stock. My concern is that it is in asurion replacement and if they send it off, are they going to discover something when it gets back to them, I don't want to get hit with a large sum of $$$.
Click to expand...
Click to collapse
If your phone is S on, you have nothing to worry about. Just don't send it in with a bunch of "root related" stuff on your SD card, and you'll be fine. How did you get s on?
Sent from my PC36100 using XDA App
I reflashed the RUU to get the phone back to stock. And by all accounts, it worked. Except that it didnt.
hgelpke said:
I reflashed the RUU to get the phone back to stock. And by all accounts, it worked. Except that it didnt.
Click to expand...
Click to collapse
So running the RUU seemed successful, but it still didn't work? But it did turn you back to S on? Had you used Unrevoked before?
Sent from my PC36100 using XDA App
I did the autoroot found here:
http://forum.xda-developers.com/showthread.php?t=838448
If I'm not mistaken, it uses some of or all of unrevoked, but I'm not sure.
I have not used the files from the unrevoked website though.
Can you attach the autorootlog.txt file to a post for me to take a look at? If you got a refurb phone it may have had something still messed up by the previous owner.
Sent from my PC36100 using XDA Premium App
I'll get the log file when I get home from work. Hopefully there is something telling in there. It didn't really dawn on me that the phone could have been rooted by a previous owner, thereby doing something to my attempt.
It's pretty rare anymore but definitely not unheard of. When the new hardware came out there were a ton of people bricking them by forcing their hboot to downgrade or trying to root with the old unrevoked. And, you could definitely tell with some of the refurbs.
From my personal experiences with asurion, along with those of quite a few people I've talked to, they don't really fix the refurbs as much as just get them back to a useable state so they can be pawned off on someone. The minute you try to root or flash an upgrade/ota it is going to start acting up again.
Sent from my PC36100 using XDA Premium App
Since I'm getting another Asurion phone, what can I do to avoid it in the future?
Depends on what is wrong with it. Although, if it boots to the bootloader then odds are it is fixable.
Sent from my PC36100 using XDA Premium App
Xhausx, I want you on whatever subforum is my hone forum. when this man speaks, . ... listen.
Sent from my PC36100 using XDA App
Hey everyone.
I know there's a couple other threads with this problem, but none of them included their last_kmsg files. It took a bunch of tries before I could stay booted up long enough to grab it, but I have one.
I'm getting a significant number of reboots on my EVO. Like almost unusable at times. It seems fairly random, although there's a slight suspicion is has something to do with the GPS. Maps has been a crash-cause before and the most recent bout last night was brought on by foursquare. (the annoying part is I had just used 4sq fine 30 minutes prior with no issues. Then, booted it up, refreshed locations and my phone was unusable for hours.)
I've done all the standard things. Fix permissions, wipe cache, wipe dalvik, wipe data/system, reinstall the latest CM7 build (update-cm-7.0.2.1-Supersonic-signed.zip), wipe cache, wipe dalvik. I entered my google account info but told it not to sync anything. It is now rebooting less than a minute after it starts up. I haven't installed any apps at all since this most recent wipe/reload of CM7. It reboots with and without the sd card installed.
I'm at a loss here and getting incredibly frustrated. Many replies say it's as easy to fix as wipe everything and re-do it. Obviously something abnormal is screwed up on my phone and I can't figure it out.
Here's the pastebin from this morning: pastebin.com/Ki7H8bH3 (Crap, I don't post here enough to be allowed to post links. Just add the http part to that.)
And then when I got awake enough, I did another complete wipe/reload. The rebooting is even worse now, it's taken me almost an hour to get to a point I can install es explorer to try and pull another file. And when I did, it was blank.
Any ideas?
Thanks!
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
grifta67 said:
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
Click to expand...
Click to collapse
You're very welcome. Sorry for the delayed response. I was having a late lunch and then drove home. Anyway, keep us informed of your progress and enjoy the rest of your day.
posting & replying via the XDA Premium app.
No worried on any delay, just glad to have someone that took a read and time to reply!
Ugh, it's the randomness of this that has me so frustrated. I thought I had a good install again, I left it sit on the "touch the android" screen for a few minutes and it stayed on. Made it through the setup process ok. I allowed the setup to "auto-download" a handful of the google apps it asks if you want. Once they got to about 38%... boom, restart.
So I did another toooootal wipe and I'll manually install those apps one by one. We'll see...
dougjamal said:
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Seems like this gets posted quite often, huh??? lol
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
Indeed, my friend...lol...but it works.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
It does and it wish it was that easy. It's frustrating to read that others seem to have no issues at all yet when I follow those directions, which are everywhere, nothing seems to work.
dougjamal said:
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I re-downloaded CM7 this morning thinking that might be the issue, but it hasn't seemed to help. I'll give a different rom a try probably, maybe there's something other than CM7 I'd be content with.
Whelp, I downloaded SalvageMod and their gapps. Wiped everything, installed salvage, installed gapps, rebooted.
I got through set-up, was ok for a couple minutes, then as I was going into my contacts to see if they had sync'd yet... reboot.
This makes me think this can't be a ROM issue.
Any other ideas?
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
jesuspgt said:
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
Click to expand...
Click to collapse
Hey jesuspgt,
I haven't tried that yet. I'll look around for a rooted stock ROM later and give that a shot.
My current status is back to uncertainty. At the moment, my evo has been sitting here fine, not rebooting, for the past hour or two. It's still the Salvage ROM I first installed (i.e. I haven't reinstalled it since it rebooted). Now I haven't really used it any, so it might go to hell as soon as I do that, but for now, it's on and only had that one (maybe two, I can't keep track...) initial reboot.
That's what makes it tricky to diagnose. I know using any custom ROM runs the risk of loosing stability and all ROMs probably produce a reboot here and there. Tough to tell if it's just a "comes with the territory" type of reboot or an actual problem.
Even though I'm sure there's some CM features I'll miss, maybe Salvage is my answer.
Thanks!
*sigh* Well I decided to try using some apps and guess what... reboot.
All I was doing was trying to play a game of Androminion, which is about as basic and not-tasking as possible, so I can't imagine that's what crashed things.
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
dougjamal said:
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Excellent, I'm going to try that. My hboot is still 0.93!
Hey dougjamal,
Just wanted to drop an update. I know how annoying it is to help someone out and never hear how things ended up!
Who knows what combo helped, but I'm fairly stable now. After updating my hboot, I flashed to Sprint Lovers, did the ##GPSCLRX# trick and then flashed to the latest nightly of CM7 (63 I believe). Only one or two crashes and one bootloop since then.
Of course, as luck would have it, a new problem showed up in the form of a dead spot on my touch screen. Right about where the "Clear" button is for notifications, that entire strip across the phone won't respond to touch. I was hoping it was a nightly issue, but I switched to a different rom and the issue was still there. Looks like it's going in for a warranty claim after-all!
Thanks for all your help
-grifta67
I searched and couldn't find an answer to my specific situation but apoligize in advance if this is addressed. I really am new to this so don't want to screw something up.
Basically, if I am rooted with the current stock 4.3, can I take an OTA update? I don't mind losing root.
Background info:
I rooted a while ago, can't specifically but I recall it being a "one-click" method. I checked with root checker from the play store and it says I have root access. If I open SuperSU it tells me KNOX is detected and I know I never removed them so I think it's right. I am running L900VPUBMK4.
I hope 4.4 is released soon, so I'm really just preparing for that day. I need to do a factory reset in the next day or two anyways because my phone is acting up and I have a ton of junk on it anyways so I want a fresh start. I originally rooted to get wifi tethering working but that never worked out for me and I really don't need root at all.
Thanks in advance.
This should be asked under q&a but to answer your question yes you can but you will need the stock recovery installed and not CWM/Philz/TWRP
Sent from my SPH-L900 using Tapatalk
Elw00d said:
This should be asked under q&a but to answer your question yes you can but you will need the stock recovery installed and not CWM/Philz/TWRP
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Can this be moved to QA then?
So did I install a custom recovery to root? Is there a way to check? I've tried several varieties of volume +/- and power to try to boot into recovery but nothing happens.
I'm in the same boat as you, but I'm still running 4.1.2. I installed "CF Auto Root" so I could run "WiFi Tether - TrevE Mod". From what I remember it installed a different recovery as well. I'm trying to avoid completely erasing everything on my phone, I just wanna remove the root and nothing else, goto Setting, System Update, Update Firmware to whatever is the recent one available, then run CF Auto Root again. Is that not possible?
I've got MobileODIN installed on my phone, but I swear that over the years that the "standard" skill level has jumped 10 fold since my days of rooting Palm Treo's, my Samsung Epic, etc...there are so many [xxxx][xxxx][xx] box things that I'm COMPLETELY at a loss here.
m5james said:
I'm in the same boat as you, but I'm still running 4.1.2. I installed "CF Auto Root" so I could run "WiFi Tether - TrevE Mod". From what I remember it installed a different recovery as well. I'm trying to avoid completely erasing everything on my phone, I just wanna remove the root and nothing else, goto Setting, System Update, Update Firmware to whatever is the recent one available, then run CF Auto Root again. Is that not possible?
I've got MobileODIN installed on my phone, but I swear that over the years that the "standard" skill level has jumped 10 fold since my days of rooting Palm Treo's, my Samsung Epic, etc...there are so many [xxxx][xxxx][xx] box things that I'm COMPLETELY at a loss here.
Click to expand...
Click to collapse
I looked on my laptop and remember what I used. I used Kingo Android Root to do it. It didn't appear to work because I never got a "success" popup. But when I did a root check it says I have it.
How do I check if I have a custom recovery?
I'm with you M5James - very confusing. Even the "one-click" idiot proof method I used confused me. Different boxes to check that I have no idea as to what they mean.
I've rooted, installed ROM's and kernals, OC'd, custom baked my own ROM's using 7Zip, I tweaked my GF's phone so that she could use it here in the States and then while we were in Dubai as well, etc. Nowadays, when it comes to things like pushing through ADB (I have no clue what that even means, I've just heard it enough that it sticks lol), all the [xxx] before the title of the ROM, kernal, etc and I just become a dear in headlights. Lastnight I tried Googling random things on how to remove root easily and one mentioned using Superuser and just clicking the Unroot Complete icon, which I did. Running random apps says I've removed root, Market doesn't work anymore (I'd upgraded to the Lucky Patcher Market is where I'm guessing the problem is), yet even though I don't have root, I still can't get the OTA to push 4.3 to my phone. I don't even really care about having 4.3 because I'm fine w/ using 4.1.2 at the moment, I'm just sick of the random pushes to my phone asking me to update.
In regards to my Note II with just installing things like custom ROM's, I haven't wanted to do anything wild to it for fear of being like the days of when I had a custom Samsung Epic...worked great OC'd, but could never get battery stats to work right, then the phone would freak out and become laggy, I'd reboot and then suddenly the battery was dead. I just want a simple root, add root-only apps as needed like WiFi Tether, then continue on being a texting whore lol.
If you have rooted your epic and installed custom recovery all this should be pretty simple. All the info is here. Its to the point where rooting and unroofing can be down in probably under 10 mins. You have to read.
Sent from my SPH-L900 using XDA Free mobile app
I read it all, but it's gotten to the point where it's overly technical sometimes. I get lost in jargon, acronyms, I liked it better when there were 5 REALLY good guys making ROM's that worked, not 30 people making their own variations in their basement, then it turns into a pissing match of who's got the latest, fastest, most battery efficient, you've gotta do this to do that, but don't do this if you want that (assuming I know WTF "that" is in the first place) otherwise you'll brick your phone (but you can maybe unbrick it this way), if you swallow this pill you'll get rid of one symptom but you'll get 15 other problems in it's place, etc...then I just say F'it and leave my phone the way it is lol
My wife has the note2, I have the s3 (both rooted, I'm running a custom rom). I think I'm gonna take her back to stock so so she can get the update, then I'll just flash a custom recovery and su zip. It'll give me a chance to clean up her phone.
Edit: thinking of using this
http://forum.xda-developers.com/showthread.php?t=2086769
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2