So I've not been a member here for very long but I've been following the nexus one, nexus s, and now the galaxy note forums since their inauguration. Up until now I've not had an issue with rooting, installing and tweaking roms etc. I've not made a post yet because I've felt it unnecessary to add to all the b.s. in these forums and if I have an issue I'll search and find an answer or figure it out myself.
I've run into a problem with Stunner 1.4.26 ..
yes. yes. yes. I have gone through the ringer - full wipe, properly done etc. etc.
On a fresh install I cannot access the internal sdcard. The rom does not see it.. I can't post the bug and whats happening in the dev forum as I haven't made enough posts yet, so now I'm getting started.
Hopefully someone else is experiencing this as I type and I'll be able to sort it out soon.
If I can figure out what is going on rest assured I won't keep it to myself. You'll be the first to know. Oh and I wont just say, 'Hey I fixed it!' I'll actually tell you how I did and what the problem was and why I think my fix is valid..
.damn forums.
Related
Guys, I had someone here talk me through rooting my nexus one with froyo and I'm running into some problems but I didn't know if it had something to do with rooting it or not and the reason is, I got it rooted the same day I received it so I hadn't tried those functions before I got it rooted.
I got it rooted so I could buy this program that makes the fonts larger and it required a rooted phone.
Well, today I was going to try to use it as a hot spot or wifi router and when I tried to enable it, it just says error.
Also, when trying to call and talk to people today, they could barely hear me and I had a hard time hearing them (not sure if this was temporary or not because later, although in a different area, it sounded fine).
When trying to reply to some e mail (online email/godaddy) when I clicked where the text/body goes, I could not type anything 'cause the keyboard wouldn't come up. If I clicked in the email or subject areas, the keyboard came up but not in the body text area.
Any ideas?
I guess I could reset it to default settings to see what happens but it took almost two hours to get it rooted so I really would like to avoid that.
Thanks
George
This should be in Q&A!
Not dev related.
To solve your problem:
looks like a bad boot.img for me.
I always had "Activiating Wifi"... "Error" with bad boot.img.
MOD: move to Q&A
Thanks. I wasn't sure about where to put it and thought there was possibly bigger chance of a reply here. Thanks for moving it.
So, considering I have NO idea what I'm doing and someone else helped me, is the answer to my next question short and simple or not?
What do I do about it?
No, I have no idea what a boot image is.
Should I try to get hold of the guy who helped me root it or see if someone else can talk me though how to fix it?
Thanks
George
guiri_too said:
Thanks. I wasn't sure about where to put it and thought there was possibly bigger chance of a reply here. Thanks for moving it.
So, considering I have NO idea what I'm doing and someone else helped me, is the answer to my next question short and simple or not?
What do I do about it?
No, I have no idea what a boot image is.
Should I try to get hold of the guy who helped me root it or see if someone else can talk me though how to fix it?
Thanks
George
Click to expand...
Click to collapse
Im not a Mod, I did not move your thread.
The boot.img is part of a ROM.
But I don't know what ROM you're using, what build (FRF50/72/85B/91) nor the kernel etc.
I cannot tell you more right now.
Just try a new rooter update.zip because yours might have broke your WiFi.
See Cyanogen's or re-flash a pre-rooted rom.
Actually, I noticed it wasn't moved yet but anyway, I think I have the 72 but still, not sure, I'll have to investigate 'cause I like this phone and I would LIKE it to work for me. Especially since I can apparently use it on tmobile and att.
THanks
The hunt continues
George
no rooting in general does not harm your phone or cause problems in any way. however it is possible to mess something up, maybe install something or screw up settings or similar that could cause problems. you can always flash back to factory ROM, or hard reset, to get your phone working again.
even better, since you are rooted, you should be creating nand backups. and anytime something goes wrong, you restore to a working nand backup to a state that you know your phone was working good.
Yeah, now I have to figure out how to do this but thanks for the replies
George
Hi all.. new to the forum, but not new to rooting, etc.
I've got a Droid 3 and have flashed it with Hash's CM9 nightly 9-20120709.. This is the second flash I've done on this device, and I keep getting this clicking noise on my bluetooth headset. Sometimes it's faint, and other times, it overwhelms my conversations.. People on the other end complain of it constantly. Sometimes, if I disconnect / reconnect my headset, it clears up for a while, but I keep hoping for a more permanent fix. Has anyone come across this? I've searched the Dev forum, but can't post this there, because I'm new, and am not readily finding anything relevant... Help??
I love the custom ROM's so far, and don't want to have switch back to stock because of this.
Also, dumb question - What's liberty? I've seen a couple of people mention it, but not sure what they're referring to.
-Roger
To the admins I apologize if this is in the wrong section if it is please move it accordingly.
Hello everyone, I have an issue, hopefully someone can hel me and it starts like this. I and everyone else have been waiting for months for a safe root method and a recovery system such as TWRP OR CWM just incase I fudge something up flashing custom roms so I can always go back to stock. I came across a safestrap article and decided it was something similar to what I was looking for. So I decided to root using the big K. I know not the best choice, you can boo me now.
After a successful root, I installed safestrap. Unfortunately safestrap kept crashing upon starting the app, I couldnt even get it to set up. thats fine, I was just going to unroot and keep on living life, but then I stumbled upon Xposed installer, that modified and tweaked like a custom rom but without all the risk according to a website. I said hey thats worth a try and I did. After the Xposed installer setup and a reboot, I wad looking for mods on the web and all of a sudden my apps and system files started crashing to the point that I could not use my phone. I immedeately uninstalled Xposed installer ss soon ad my phone stabalized and unrooted.
I thought everything was good, 4 hours later the apps and system files started crashing again, so I did a reboot and I noticed that custom with the lock came up on intial startup. though I was told I was unrooted by the K program and even double checked using a rootchecker app, which stated I had indeed an unrooted phone. I did another reboot and no custom or logo came out. At this point I just wanted a working phone and As much as I hated doing so I did a factory reset. This seemed to have fixed the problem, but 4 days later my phone randomly went into a bootloop. I couldnt get it to stop so I took out the battery and that did not fix it.It was strange becuase I thought it might have been unrelated since it wasnt doing this when I had the issue with Xposed installer.
After yet another factory reset my phone seems to be fine, its still too early to tell though since its only been about a day. I had the normal google playstore and gvoice app crashing...Sigh..the only thing different was that sometime yesterday after the second factory reset a notification popup of unfortunately a sytem file stopped working came up. I acknowledged it, but thankfully I havent gotten any problems. I forgot what the notification read. hopefully its not related to what happened the other day.I dont know if this is related to one another, but I did notice that before I rooted my android system had automatically upgraded. I looked for issues like this on the net and saw people where having random bootloops after system upgrades and that unchecking scanning for wifi fixed the problem. though I did this and it did not work, thats why I did the second factory reset.
Now Im asking for help if any further issues arise. I love my Note3 and at this point I just want a reliable working device. Im keeping my fingers crossed and hopefully that will be the end of it, but in case it started to act up again, what can I do? any information and help is greatly appreciated. thanks.
Never uninstall any Xposed app that changes system files without first reverting any changes you made with it. Some of them are permanent until they are turned off in the App. Then you can disable the module.
You may want to look into this http://forum.xda-developers.com/showthread.php?t=2559715
I cannot stress this enough.
READ READ READ.
Too many times have I seen someone read a line or 2 then rush right in ultimately turning their very nice phone into the most expensive paperweight one could own.
On that link I posted, read it until your eyes are bleeding if you truly need to start from scratch.
I am not joking here.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Thanks man. it makes sense. I will look into it. you mentioned read. I have read what I thought was plenty, but always ideas and opinions differ, sometimes knowing too much and causing what they say decision paralysis. Because I still read about the Xposed experiences and different people go about it in a different way. but what you mentioned about reverting back makes alot of sense.
I read throughout this forum daily and see people post problems they are having after taking an update. Word to the wise. Whenever you do an update no matter how big it is. Do an FDR. If you dont know what an FDR is google it. People are complaining about battery life, issues with stuff not working and sit here and ask question but do not try to figure it out on their own. The number one reason there are issues after an update is because the previous build is partially on the phone still and will cause bugs with the new build. Do a FDR and start fresh then, if the problem continues post. I have answer so many peoples PM's asking about how to fix an issue, and the first thing I ask is Did you do an FDR? You sit there and complain about issues but also complain about doing an FDR. I can guarantee you (unless u have a defect) any issues if not all issues will be resolved doing an FDR.
That's very true an fdr is needed for the best possible result but then again people are so impatient they don't wait for the yet new break-in period from the update
I agree with you 100% about doing an FDR. With few exceptions, I will do an FDR after an update but I didn't on this last update because I wasn't having any issues before the update nor have I come across any after it. I am holding off on the FDR until we get the Lollipop update. Unless weird stuff starts happening, then I will go ahead and do it.
the_rooter said:
If you dont know what an FDR is google it.
Click to expand...
Click to collapse
But this sentence doesn't make any sense, wouldn't it have been less typing to just say that "FDR = Factory Data Reset". Most people that come here for issues are not techies and more than likely, they used Google to do a search for their issue and Google gave them this website as the place to go for answers. Telling them to go back to Google to do another search is counter productive.
But I also understand your frustration, I used to own an LG Ally. That phone was so bad that you had to do an FDR before an update because it didn't have enough memory and if you had installed any apps it wouldn't update. Once, they released a pre-update which removed all the bloatware just so they could do the regular update. No body seemed to understand that and then they would complain about their phones not working correctly.
FDR = Franklin D. Roosevelt
I am not an expert, but have been installing updates on my phones for nearly a decade and never had an update mess up a phone. My routine is always have a fully charged phone, charger connected, at home near my router for full wifi reception, download and install at home make sure no running apps, no active wallpaper. Perhaps is simply a matter of being lucky but over the years I have read hundreds of threads that started with: I did a factory reset and it did not help, I consider it a last resort possible solution that maybe has a 50% chance at best to solve your problem and them you lost all your settings you worked so hard to get just right. Just an opinion, not telling anyone what they should do.
So i posted this in the Unoffical Xposed Lollipop thread but i figured i'd make a new post since it isn't really related. Looking around i also can't really find similar issues to try to diagnose and solve myself unfortunately. Today after testing out GB on my S5Active and then removing it, since i found no real use other than slowing my system down i found myself with an interesting new Xposed log after, my phone ended up bugging out asking me to "Sign into a network" that i already had internet access through and been set up. It then restarted itself and sat in boot. Wouldn't finish so i pulled the battery and it started back up, checked the log and this issue started arising. I'm not even certain GravityBox is the culprit, but i got a damn good feeling considering how it's supposedly not TW compatible even though a bunch of TW users are posting about their successful experiences with it.
So, Since i lack an Nandroid backup because i had already lost everything previously including Nandroid in previous issues, would my best fix be reset and start from scratch for the third time? Or is there anything from the tombstone & log that would help figure out a solution rather than a fresh start.
Tombstone & Log attached
Edit: also it's on boot when this appears, doesn't really seem to effect anything. And only other thing I could see it maybe coming from is me editing my .xml for sd permissions, but I don't quite understand the code.
Xposed Framework crashing. You should contact the devs of framework for Samsung devices, or visit respective thread, to provide details.