Develop Bugs

[Q] Help with rooting my G2

I've been trying to root my G2 since last night, and before I start, I have to say I do NOT and WILL NOT have access to adb. Some drama with my father caused him to revoke my administrator privilages on all the computers in my house. So I can't install anything or run any unknown .exe's.
The only way I can go about this is using Visionary so far. However, it's been a piece of crap up to this point. I have +r14, USB debugging enabled. Regardless of whether I check "Set system to r/w after root", I always get the same two results when i hit Temproot.
Sometimes it'll go through a couple of triangle screens w/ "rooting device, please wait" and then go back to the main option screen. However, this seemed to do nothing but install Superuser with NO APPS requesting su permissions. After this I'll try to hit "Attempt Permroot now" and it will say "Please Temproot before attempting Permroot". "Unroot now" just says my device isn't rooted. >_> Going into terminal and typing "su" gives me a "su: Permission denied".
Other times when I hit Temproot, it'll go through a few triangle screens, and then just stop on a black screen with only the status bar visible. I can still Home out and use the notification bar and such though, so it's not a total system freeze.
Can someone please help me out here? I ordered my phone on 2/4/11 and got it maybe a week later if that makes any difference, because I've been hearing some things about people not being able to use Visionary on newer phones.

Try using this GUDIE HERE. No ADB needed.

I've tried that guide and one of the two scenarios I provided always happens. :\

I got my phone brand new from the tmo corp store sat night and I had no problem with rooting via visionary and gfree.
Mine did not have that 1.72 update tho. Maybe that's your problem.
From my permarooted overclocked HTC G2 with cyanogen 7 nightly via XDA app

tackleberry said:
I got my phone brand new from the tmo corp store sat night and I had no problem with rooting via visionary and gfree.
Mine did not have that 1.72 update tho. Maybe that's your problem.
From my permarooted overclocked HTC G2 with cyanogen 7 nightly via XDA app
Click to expand...
Click to collapse
Tmobile phones don't get the 1.72 updates, that's only for the desire Z's, Tmobile G2's only have the 1.19 or the 1.22 OTA roms on it.
Sent from my HTC Vision using XDA App

How do I check what update I have? (I heard having Wifi tethering and Wifi calling affects that, I have both)

legendaryxm90 said:
How do I check what update I have? (I heard having Wifi tethering and Wifi calling affects that, I have both)
Click to expand...
Click to collapse
If you have wifi calling and tethering built-in, then you have the 1.22 OTA update already (I think all of the newer G2's come with it). I'm not sure if it shows up anywhere you can check easily, but I do know the OTA came with a newer radio so you could check in your Settings->About phone. The baseband version should end in something like 26.03.02.08.
The version number is also stored on partition 17, but I don't think you can check that without at least temp root. Not positive though.

I have no idea why Visionary is having problems even temp rooting your phone. One problem may be that you tried the permroot function within it (I don't know what it does, but many users have reported strange behavior when it doesn't work right).
Maybe you can try doing a factory reset and then starting again. Also, you might want to try disabling all of the added functionality in Visionary (such as temp rooting or setting system as R/W on boot), restarting the phone, and then trying the temp root again. Or uninstalling Visionary and then reinstalling it.
If you can just get su to work in terminal, then you should be okay.

joemm said:
Tmobile phones don't get the 1.72 updates, that's only for the desire Z's, Tmobile G2's only have the 1.19 or the 1.22 OTA roms on it.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
me=de de dee! lol. thanks for that info. i didnt know that specific detail.

Ok, so I just factory reset my phone, and I'm going to try this with a fresh downloaded r14. Gonna try with no options checked. Also, is it better to do this with the phone connected to the computer or not?
EDIT: OK here's what I was talking about. -_- Just tried it TWICE. First time it went back to the option screen, Terminal gives me su: permission denied again. Did it a second time. Currently stuck on a black screen w/ only status bar visible. WTF IS GOING ON MAN.

legendaryxm90 said:
Ok, so I just factory reset my phone, and I'm going to try this with a fresh downloaded r14. Gonna try with no options checked. Also, is it better to do this with the phone connected to the computer or not?
EDIT: OK here's what I was talking about. -_- Just tried it TWICE. First time it went back to the option screen, Terminal gives me su: permission denied again. Did it a second time. Currently stuck on a black screen w/ only status bar visible. WTF IS GOING ON MAN.
Click to expand...
Click to collapse
Not sure what's happening. How long are you waiting on the blank screen? I've seen some people say the temp root took a while on their phones. I saw in one of the forums (maybe dev), someone posted another app that can achieve temp root as well. Might be worth taking a look...

I waited 15-20 minutes and nothing. >_> I'll look for that other app because I just read somewhere that VISIONary doesn't work on the latest OTA phones. Is that true?
EDIT: Haven't found anything. Is there ANY hope for me without adb? :<

Here's the other temp root program someone mentioned: http://forum.xda-developers.com/showthread.php?t=951208
Never tried it myself but maybe it'll work for you.
Also, I think the thing about Visionary not being compatible for OTA phones was only for the permroot option. Like I said, people have reported really strange behavior when it doesn't work.
Just thought of another thing to try. Maybe clear the data for the superuser app. Hopefully when you try su in terminal then, it'll pop up with the dialog box asking for permissions again.

ianmcquinn said:
Just thought of another thing to try. Maybe clear the data for the superuser app. Hopefully when you try su in terminal then, it'll pop up with the dialog box asking for permissions again.
Click to expand...
Click to collapse
D'OH. THAT DID IT. Got the superuser popup!
THANK YOU SO MUCH!! +REP

WiFi - bcm4329.ko file?

Hey I have a desire Z and my logcat says that the Wifi driver isnt loading. I want to replace it with one that works so my wifi actually turns on.
If you have a bcm4329.ko for the desire z could you please let me know?
Thanks

Isn't that file subject to the kernel you're running? Or are you stock and just looking for the stock bcm file also?

KCRic said:
Isn't that file subject to the kernel you're running? Or are you stock and just looking for the stock bcm file also?
Click to expand...
Click to collapse
Yeah I think it is normally part of a kernel but I cant seem to get this damn wifi to work no matter what I do, so I was thinking if anyone had one of the files kicking around I would just ADB overwrite the old one and see if it works.

Try flashing one of the kernels in my signature -- they both include a corresponding WiFi driver.

theSpam said:
Try flashing one of the kernels in my signature -- they both include a corresponding WiFi driver.
Click to expand...
Click to collapse
Still doesn't work
Really have no more ideas to fix my wifi.

you can always jus download a rom and go to the folder where its located and take it out and push it in your phone instead of waiting for some one

ilostchild said:
you can always jus download a rom and go to the folder where its located and take it out and push it in your phone instead of waiting for some one
Click to expand...
Click to collapse
I tried that too and it didn't do anything. Im really pulling at straws. Is there a program to test to make sure the hardware is actually good?

Im sure you done this already but some one is bound to ask, so ask now.
have you tried to wipe
and reflash the rom your using and try it again,

ilostchild said:
Im sure you done this already but some one is bound to ask, so ask now.
have you tried to wipe
and reflash the rom your using and try it again,
Click to expand...
Click to collapse
Yep, tried that twice. I even went back to stock between the reload.
One time I flashed it using the PC10IMG method and the other I used Clockwork (rom manager).
I really have no idea where to go at this point. I think I've exhausted all my ideas. Ive tried reflashing roms, kernels, and radios.
Was hoping someone had some diagnostic software that would test the hardware of the phone or something so at least then I would know if my actual hardware for the WiFi and Bluetooth was shot or not.
Thanks anyways.

Wow, I forgot about this thread over the weekend
Anyway, have you tried changing the permissions for the file? You can use 'fix permissions' in ROM Manager or clockwork or use Root Explorer to change the permissions. Of course if you're a terminal kind of guy you can chmod it.
Sometimes the permissions don't set correctly or, on some systems running linux, the permissions get changed for some reason. Maybe that's what's going no here, sounds like it anyway. Btw, make sure to reboot after changing the permissions because it won't work until you do.

has anyone fixed this issue where wifi stops working?

wifi not turning ON
Hello Everyone,
During the process of getting IP address from WiFi network, I received a "Error Massage" on my Alcatel OT-990. After this massage, WiFi started behaving abnormally. Sometimes it turned ON another time it did not. Now after a few weeks later, WiFi is not turning ON at all.
I have Tried following Solutions but nothing worked:
1. Did factory reset, erased system, cache etc and Flashed different ROMs (JB ot 990, ICS QME, QLTsar, 2.3.4, Telenor One touch 4.0.04) using Recovery many a times(From different Sources).>>Problem not solved
2. Updated my phone using alcatel update manager to 2.3.4>>> Problem not solved
3. Tried by changing permissions of BCM4329.KO, wpa_supplicant.confg etc every file related to wifi/wlan>>Problem not solved
4. Used WiFix Manager>>>Problem not solved.
Bluetooth and FM radio working all right.
If anybody knows about its solution ..please help me out.

Hands free activation with everey reboot

Can someone help me with this? I found that if you remove sprintandroidextension.apk it goes away but it didnt. I also found that by removing SprintOMADMConnMOPlugin.apk it goes away, but i cant find it on my Galaxy note 2. Any ideas? Thanks in advance.

If you let it go all the way through HFA once it won't return. Since you removed sprintandroidextension.apk I'm not sure it will succeed now. Try re-adding that first.

Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak

digitallogik said:
If you let it go all the way through HFA once it won't return. Since you removed sprintandroidextension.apk I'm not sure it will succeed now. Try re-adding that first.
Click to expand...
Click to collapse
I tried doing that many times but it never worked, it just gave me an error.
trim81 said:
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
Click to expand...
Click to collapse
Thank you! it worked

interesting. found this thread buried, and there still seem to be many people with this issue... seemingly related to the chameleon FCs some are getting, somehow possibly related to the LK8 update and/or a return to an earlier stock version...
digitallogik said:
If you let it go all the way through HFA once it won't return.
Click to expand...
Click to collapse
I've let it complete (personally) aprox 20+ times, so no go.
trim81 said:
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
Click to expand...
Click to collapse
could the "fix" really be this simple? (at work, can't test this right now.)

kingdazy said:
could the "fix" really be this simple? (at work, can't test this right now.)
Click to expand...
Click to collapse
yes, and you can delete the activation.apk as well to stop it

trim81 said:
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
Click to expand...
Click to collapse
thanks, stopped the HFA, still have the chameleon errors to deal with...
t3project said:
yes, and you can delete the activation.apk as well to stop it
Click to expand...
Click to collapse
and I suppose I could do that too.
but both of these workarounds are "dirty fixes", and not fixing the fundamental issue.

kingdazy said:
thanks, stopped the HFA, still have the chameleon errors to deal with...
and I suppose I could do that too.
but both of these workarounds are "dirty fixes", and not fixing the fundamental issue.
Click to expand...
Click to collapse
your solution is to thoroughly wipe and reflash whatever rom you are running.

t3project said:
your solution is to thoroughly wipe and reflash whatever rom you are running.
Click to expand...
Click to collapse
I would have thought so too. As I've been advised by other as well. But...
I have, at least five times, run a return to stock, both through ODIN and OneClicks.
I still have the issue. Baffles the mind. Makes little sense. But there it is. And I'm not the only one.
(Just so it's noted, and before you accuse me otherwise, I am not new at this, and I follow directions fastidiously. I've never once had a problem that I didn't cause myself, and I've always been able to fix them by further reading/researching.)
Just for SnG's I'll quote myself and others from a few other posts in other threads:
kingdazy said:
well, this is annoying. I seem to be stuck with the "hands free activation" and chameleon fc.
i'm assuming a nice total stock one click should fix it?
Click to expand...
Click to collapse
garwynn said:
Sure should! Please try the stock restore or rooted restore.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
kingdazy said:
interestingly, it didn't fix it... "preparing network", "hands free" and chameleon FC on every reboot. this is after the rooted full restore OC. what am I missing? weird.
(history: I was rooted stock w/ twrp from the mskip toolkit method of rooting, got rid of twrp using the mrRobinson stock w/ root, and flashed the sxtp update to lk8, got a wifi failbug and tried to get back to stock rooted using mrRobinson and started getting this issue. lol. ok. so... one-clicked your rooted full restore, still there. is that even possible?)
well, my phone seems to work, as long as I don't reboot.
but I find it worrisome.
have to sleep for work now, but if you had any advice for things to try when I wake up, let me know? thanks dood.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
kingdazy said:
Just my 2 cents, my experience with this error.
I'm getting the Chameleon FC, and the persistent HandsFree Activation on every reboot. All started when I lost wifi on the LK8 update zip (I was rooted, thanks to Voodoo OTA rootkeep), and tried to get back to LJC...
And this morning, I tried the following:
Installed TWRP with GooManage, restored a nandroid from my orig rooting using the toolkit, no luck, same two errors.
So then I OneClicked the Full Restore (SPH-L900_LJC_Stock_Restore.exe), and wtf, still there.
As I mentioned in my quote, it (the Note2) works, not broken, but I find the persistent error worrisome.
I am open to criticism, suggestions, whatever. What am I missing?
Click to expand...
Click to collapse
Itchiee said:
I'm having similar issues, I was on the release before LK8, then updated to LK8 but wanted to start over again.
Once i downgraded to LJ1? the hands free bug kept popping up every reboot, until I moved onto to LJC then LK8 update file which is fine.
I'm trying to figure out myself how to go back to the original firmware (pre any updates) without the issues... /subscribed.
Wonder if this is tied into it somehow...
I dunno, my head is exploding reading all these posts, replies.... 5 different versions of restore.
Click to expand...
Click to collapse
evilgenyus said:
I have tried the one click restores back to ljc and the original tar, and I still have the hands free activation issue and the chameleon error. And when I update to lk8 I get no wifi. I have tried returning to stock about 4 times and then updated to lk8 with the same results. I always go back to ljc bc I need wifi.
Click to expand...
Click to collapse
kingdazy said:
interestingly, even using a stock oneclick full restore (and even using a TAR in Odin), still have the handsfree repetition and chameleon FCs. (lol, I'm not complaining really, it's early in the dev life for this device I suppose. )
Also, I've been reading that re-flashing the LK8 update.zip (via sxtp?) while it seems to fix the HFA and ChameleonFC, it kills the wifi? (it killed my wifi after aprox 2 days use, when I orig updated...)
Click to expand...
Click to collapse
garwynn said:
I'm starting to wonder if the move to 4.1.2 changed something that isn't handled properly by older versions. Without a gn2 will be hard to confirm... but I may be resolving that soon as well!
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Click to expand...
Click to collapse
It would apear that something in the LK8 changes ... something. Permanently?
So, any new advice would be welcome...?

Would renaming the chameleon apk have the same result as hfa
Sent from my Nexus 7 using xda app-developers app

smooth703 said:
Would renaming the chameleon apk have the same result as hfa
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
fine question, but without knowing what the chameleon apk does, i'm reluctant to f**k with it.
anyone know? (a goog search gave me nothing...except this XDA rom w/ a fix...? I'm going to try n PM him...)
and again, my concern is the issue seems to be more significant, seeing as a Full Wipe to Stock doesn't fix it.

has anyone with our issue attempted to get their MSL, do a NVflash reset? (##786#)
I am (for some reason) unable to get my MSL, so can;t test this.
sxtp site said:
If you need to clear NVRAM/Sprint data login info, perform a ##72786# reset from the Dialer and enter MSL.
Type getprop ril.MSL in adb shell or terminal to retrieve your MSL.
Click to expand...
Click to collapse

kingdazy said:
has anyone with our issue attempted to get their MSL, do a NVflash reset? (##786#)
I am (for some reason) unable to get my MSL, so can;t test this.
Click to expand...
Click to collapse
I tried it, it doesnt work. You have to go to settings and activate device to get your info back, and it still does handsfree on every boot and no way to update profile

shiftr182 said:
I tried it, it doesnt work. You have to go to settings and activate device to get your info back, and it still does handsfree on every boot and no way to update profile
Click to expand...
Click to collapse
Same here I tried it no luck.
Charles
Sent from my SPH-L900 using xda premium

So I ended up returning my phone to Sprint, the swapped it out pretty easy, let them see the issue and error, they said "yeah, that ain't normal", got me a new one.
kingdazy said:
it would seem that the factors that all of us with this issue have in common are: a) rooting w/ ToolKit ver2 b) flashing LK8 update zip c) trying to return to stock LJC/LJ1 because of a wifi problem... please chime in if you have the issue, but not one of those factors?
After everything, I just returned to stock LJC w/ Flash Counter @ 0 (no) w/ the errors still present, took it into Sprint store said, 'hey guys, this is weird, i've got a persistent error, won't go away after resetting my phone." (IE, acted dumb enough to not have rooted/flashed unofficial shtuff/etc, but smart enough to know that it's a real issue), they looked at it, asked a few obvious questions, replaced it, because obviously something was wrong in a permanent way. I want to a corp store, not a "repair center". I think it was a good thing that these guys were not super techie.
I told them as little as possible, that I had a "wifi issue after an update, tried full reset (through the android settings menu, of course), and the problem didn't go away, no matter what". Once they heard that I had done a full factory reset, and saw the problem/error happen, it was a no-brainer to swap out.
I'll be avoiding the LK8 leak for now, and frankly gun-shy about the toolkit.
Click to expand...
Click to collapse
I had someone ask how I got it back to stock unrooted w/ no flash count, and while that might be abvois to some, just in case someone doesn;t want to hunt around, or ask this is what I did, with links:
kingdazy said:
ok, to get back to stock, first use this OneClick to get to Stock+Root, it will wipe ALL internal memory except SD card:
http://rwilco12.androidfilehost.com...sung Galaxy Note II (SPH-L900)/LJC/ROM/Rooted
Instructions are here:
http://www.sxtpdevelopers.com/showt...-TAR-SPH-L900-LJC-(LJC-Modem-Kernel-ROM-Stock)
then use TriangleAway, this will set your counter at 0 (reads as "no" in download mode). it should also say "Official" And "Samsung Official"
Then, if you want to get Total Stock unrooted, for returns to Sprint, or any other reason, use Odin (not mobile) to flash this:
http://www.androidfilehost.com/?fid=9390214368362234120
Instructions for flashing that are here:
http://www.sxtpdevelopers.com/showthread.php?76-TAR-STOCK-Full-L900VPALJC-quot-Back-to-Stock-quot
After I did those things, I was stock unrooted, no flash count.
Click to expand...
Click to collapse
Good luck to the people with this error, I feel for you, very frustrating. I am hoping that Samsung releases an official OTA soon similar to LK8, that you will be able to flash that will fix the error and the wifi.
And I hope the devs are reading these posts (even if they are not responding), are at least looking into it.
I know we have the attentions of garwynn, he's made the SxTp team at least aware that there might be an issue.
You'll be seeing me.

Yeah, I have to give it up to garwynn, he hooked me up with the pit file for our phone. Good people.

ProjectROM 2.1
Did a clean install and I get this as well =/

RussellAlan said:
Did a clean install and I get this as well =/
Click to expand...
Click to collapse
a clean install, coming from what? And what did you use to get back to stock? (Just asking so people will have a clear history of what is causing this. In case a dev wants to look closer at the problem, have clear ideas where to start)
Sent from my SPH-L900 using xda premium

ceabbott2 said:
Same here I tried it no luck.
Charles
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
+1
Sent from my galaxy note 2....

kingdazy said:
So I ended up returning my phone to Sprint, the swapped it out pretty easy, let them see the issue and error, they said "yeah, that ain't normal", got me a new one.
I had someone ask how I got it back to stock unrooted w/ no flash count, and while that might be abvois to some, just in case someone doesn;t want to hunt around, or ask this is what I did, with links:
Good luck to the people with this error, I feel for you, very frustrating. I am hoping that Samsung releases an official OTA soon similar to LK8, that you will be able to flash that will fix the error and the wifi.
And I hope the devs are reading these posts (even if they are not responding), are at least looking into it.
I know we have the attentions of garwynn, he's made the SxTp team at least aware that there might be an issue.
You'll be seeing me.
Click to expand...
Click to collapse
I try that method but mine still show 1 on the counter. Is there a way to get rid of that?

Wifi Error

I have the EVO 4g and I was able to put it into S-off....Once i did that i was getting wifi error when i tried to use the wifi. I'm stumped and have looked everywhere and have not gotten any clear answers. I have tried to install a rom (using digital karma now) but to no avail. Please help me out :laugh:

Try upgrading radios

death-by-soap said:
Try upgrading radios
Click to expand...
Click to collapse
that did not work =\

Could try reflashing the kernel and wiping cache and dalvik cache in recovery.
You tried switching your router off and on again?

note that some kernels need to have data and/or system mounted first in recovery before flashing the kernel otherwise wifi breaks. Just a thought.
also, you did sanity check your network by conforming that other devices still connect fine?
Sent from my PC36100 using xda app-developers app

Robobob1221 said:
Could try reflashing the kernel and wiping cache and dalvik cache in recovery.
You tried switching your router off and on again?
Click to expand...
Click to collapse
well i didn't do the router because its not even scanning for a router at all. This is a fairly new phone so it was never dropped (just some info).

NxNW said:
note that some kernels need to have data and/or system mounted first in recovery before flashing the kernel otherwise wifi breaks. Just a thought.
also, you did sanity check your network by conforming that other devices still connect fine?
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
yeah the network is fine. I have another EVO that i use for wifi purposes, but the usb port broken. I have been charging my battery on one phone and using wifi on the other. It was fine while it lasted but now its a bit old. I want to flash one of these phones to pageplus and i prefer the one that the wifi works on.

Ok...let me search my memory banks to see if I can help. I have had this problem about 2 or 3 times, and I searched DILIGENTLY for an answer. After countless, and I mean countless pages, I found a solution. (Not saying you didn't search right...but it took me a while, and I had to change the words of my search about 20 times.)
You need a file explorer with root access. There are many good ones, and I use ES File Explorer. Not saying it's the best, not saying it's the worst, not saying anything except that it's the one I use. Period.
Anyway, you must access the root of your phone, and go to these folders.
System-->Etc-->Wifi.
In the Wifi folder, either rename the supplicant file to be safe, or delete it. I renamed mine the first time around to be safe, but I can confirm that deleting doesn't hurt anything. Restart your phone, and it will rebuild the file when the phone reboots. No need to wipe cached or anything. And fixing permissions doesn't work for this.
Try it, and let me know.
P.S.: I would give credit to the person who originally posted this solution, but I don't remember, since the answer was not on XDA, and I found it in a forum for a random Samsung phone.
______________________________
HTC Evo 4g

aarsyl said:
Ok...let me search my memory banks to see if I can help. I have had this problem about 2 or 3 times, and I searched DILIGENTLY for an answer. After countless, and I mean countless pages, I found a solution. (Not saying you didn't search right...but it took me a while, and I had to change the words of my search about 20 times.)
You need a file explorer with root access. There are many good ones, and I use ES File Explorer. Not saying it's the best, not saying it's the worst, not saying anything except that it's the one I use. Period.
Anyway, you must access the root of your phone, and go to these folders.
System-->Etc-->Wifi.
In the Wifi folder, either rename the supplicant file to be safe, or delete it. I renamed mine the first time around to be safe, but I can confirm that deleting doesn't hurt anything. Restart your phone, and it will rebuild the file when the phone reboots. No need to wipe cached or anything. And fixing permissions doesn't work for this.
Try it, and let me know.
P.S.: I would give credit to the person who originally posted this solution, but I don't remember, since the answer was not on XDA, and I found it in a forum for a random Samsung phone.
______________________________
HTC Evo 4g
Click to expand...
Click to collapse
nope did not work...I eeven tried taken wifi files out of my working evo to this one and still did not work

Do a Full Wipe of everything. Then Flash a Stock Rooted Rom. See if that corrects the issue. You may also want to check out THIS thread. Also the one HERE.

Hmmmm...I tried my best. I hope you find a solution soon.
But the way, does it simply say error, or does it behave strange, like turn off and on for a while, then give you the error message?
______________________________
HTC Evo 4g

aarsyl said:
Hmmmm...I tried my best. I hope you find a solution soon.
But the way, does it simply say error, or does it behave strange, like turn off and on for a while, then give you the error message?
______________________________
HTC Evo 4g
Click to expand...
Click to collapse
it say error

Since nothing else has seemed to work you could try this..http://forum.xda-developers.com/showthread.php?t=1982149 ..you have to be running an ics or jb rom for the app to work though. Just throwing it out there.

If You Used The TMobile Root Method...

2 things... Would anyone mind verifying that once you use the tmobile root, you can no longer boot into recovery?
I tried to factory reset and the recovery will not boot.. Just flashes the android icon every few seconds.
The only way to boot back into the phone is to put it into download mode and re run the tmobile root. It will restart and all will be good.
Now, if it is not just my phone that no longer has a working stock recovery, does anyone know a way to factory reset without a working recovery? I'm guessing it's not possible. Kies does not work with the Sprint Note 4 yet. They updated it today and you can backup the n4 but not factory reset.
Finally, can anyone that used the Galaxy Tools app to get WiFi tethering to work, check to see if your private mode will turn on? I do not have xposed installed and the wifi tether fix in the galaxy tools app seems to be the only thing I can think of that would have broke Private Mode.
Thanks!

Same thing happened to me. I had to get another note 4. There is no way until samsung releases the firmware dump. Sprint even called best buy samsungs care center to see if they have the reflash files and they don't even have it. Odin wipe the data and bring it into sprint so they can give you another one.

Mine boots just fine to the recovery and tecovery works just fine.
I know when i first downloaded thw CF auto for n910t and used the oding in that package my process failed and phone showed to monitors on screen
So i took battery off and download mode again and used a different odin i allready had same version and did the process again and worked and everything is fine.

Androidwarrior said:
Same thing happened to me. I had to get another note 4. There is no way until samsung releases the firmware dump. Sprint even called best buy samsungs care center to see if they have the reflash files and they don't even have it. Odin wipe the data and bring it into sprint so they can give you another one.
Click to expand...
Click to collapse
It is not that big a deal. I can wait for a custom recovery and then go from there. I wanted to factory reset so that I could get private mode back, but I will just use it as is until there is another alternative.
Others are saying that their recoveries are working fine. I guess you and I are the lucky ones
Thanks Androidwarrior.

CJPRICO said:
Mine boots just fine to the recovery and tecovery works just fine.
I know when i first downloaded thw CF auto for n910t and used the oding in that package my process failed and phone showed to monitors on screen
So i took battery off and download mode again and used a different odin i allready had same version and did the process again and worked and everything is fine.
Click to expand...
Click to collapse
What version of Odin did you use? Thanks

I just auto-rooted with N910T, and tried to install Wifi Tether (and TrevE variant) and neither worked. I don't think it started the tether correctly, it was unable to open the log for write, so I don't have a log. I am pretty sure the root was successful (at least partially). I used the root checker app and it said I was good and within the terminal emulator I was able to switch users to root.
I also unsuccessfully tried X Tether. It started up, and showed up on my computer, but I wasn't able to connect to it, and after a while it invariably told me that I needed to upgrade my service.

loonytunes said:
What version of Odin did you use? Thanks
Click to expand...
Click to collapse
3.07 but a normal odin (with all options available) not modified (that it wont let you chose anything but pda) like the one it came with the cf auto
---------- Post added at 10:42 PM ---------- Previous post was at 10:41 PM ----------
hpmaxim said:
I just auto-rooted with N910T, and tried to install Wifi Tether (and TrevE variant) and neither worked. I don't think it started the tether correctly, it was unable to open the log for write, so I don't have a log. I am pretty sure the root was successful (at least partially). I used the root checker app and it said I was good and within the terminal emulator I was able to switch users to root.
I also unsuccessfully tried X Tether. It started up, and showed up on my computer, but I wasn't able to connect to it, and after a while it invariably told me that I needed to upgrade my service.
Click to expand...
Click to collapse
Have you tried Galaxytools from playstore it worked just fine on mine for hotspot

Just loaded it... It seems like I am getting a "System Updating" every time I reboot now, not sure if it was doing it before that though. After some playing with it, I think it is now working. I hit the "Enable Native Hotspot" and it rebooted and then it worked for a while, I tried it again, and it seems more reliable now. I'm still not convinced its completely reliable. I tried a speedtest on my laptop while tethering and I got about 8Mbps down, but only about 300kbps up. The upload seemed very goofy, like it was sending a lot of data and then pausing, and then sending a lot of data. Interestingly it was on 3G initially and getting about 1.5Mbps and the same thing up (and then when I rebooted it, I got LTE and the higher download speeds).

hpmaxim said:
Just loaded it... It seems like I am getting a "System Updating" every time I reboot now, not sure if it was doing it before that though. After some playing with it, I think it is now working. I hit the "Enable Native Hotspot" and it rebooted and then it worked for a while, I tried it again, and it seems more reliable now. I'm still not convinced its completely reliable. I tried a speedtest on my laptop while tethering and I got about 8Mbps down, but only about 300kbps up. The upload seemed very goofy, like it was sending a lot of data and then pausing, and then sending a lot of data. Interestingly it was on 3G initially and getting about 1.5Mbps and the same thing up (and then when I rebooted it, I got LTE and the higher download speeds).
Click to expand...
Click to collapse
Even before root. They were doing that system update everytime y restart. But u can freeze samsung DM service if it bother you

hpmaxim said:
Just loaded it... It seems like I am getting a "System Updating" every time I reboot now, not sure if it was doing it before that though. After some playing with it, I think it is now working. I hit the "Enable Native Hotspot" and it rebooted and then it worked for a while, I tried it again, and it seems more reliable now. I'm still not convinced its completely reliable. I tried a speedtest on my laptop while tethering and I got about 8Mbps down, but only about 300kbps up. The upload seemed very goofy, like it was sending a lot of data and then pausing, and then sending a lot of data. Interestingly it was on 3G initially and getting about 1.5Mbps and the same thing up (and then when I rebooted it, I got LTE and the higher download speeds).
Click to expand...
Click to collapse
Can you check to see if using galaxy tools to enable tether kills your private mode? Since using the galaxy tools app, whenever I click on private mode it fails saying "Private mode failed to start, try again."

loonytunes said:
Can you check to see if using galaxy tools to enable tether kills your private mode? Since using the galaxy tools app, whenever I click on private mode it fails saying "Private mode failed to start, try again."
Click to expand...
Click to collapse
My private mode is gone but id assume its because of xposed but can't be for sure.

sml2004 said:
My private mode is gone but id assume its because of xposed but can't be for sure.
Click to expand...
Click to collapse
I'm not sure how to use it since this is the first time I've heard of it, but it appears to be there. S Health seems to have been killed somewhere along he way there. No more pedometer, UV sensor, SPO2, or heart rate....

Did some googling and found this. http://www.andromods.com/fix-troubleshoot/fix-xposed-framework-shealth-problem-galaxy-s5.html
I'm going to try it and see if it works on ours.
Update: Uninstalled Xposed and S Health started working again. Going to back up and try the buildprop edit in a bit.

Shadeoblac said:
Did some googling and found this. http://www.andromods.com/fix-troubleshoot/fix-xposed-framework-shealth-problem-galaxy-s5.html
I'm going to try it and see if it works on ours.
Update: Uninstalled Xposed and S Health started working again. Going to back up and try the buildprop edit in a bit.
Click to expand...
Click to collapse
In Xposed install "Wanam Xposed", open Wanam, go to Security Hacks, and click "Disable Secure Storage" and S Health will work fine.
Sent from my SM-N910P using Tapatalk

hpmaxim said:
I'm not sure how to use it since this is the first time I've heard of it, but it appears to be there. S Health seems to have been killed somewhere along he way there. No more pedometer, UV sensor, SPO2, or heart rate....
Click to expand...
Click to collapse
pdaddy said:
In Xposed install "Wanam Xposed", open Wanam, go to Security Hacks, and click "Disable Secure Storage" and S Health will work fine.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
That sounds way simpler.
Thanks!......
So I tried that and it didn't work.....hmmmm

Shadeoblac said:
That sounds way simpler.
Thanks!......
So I tried that and it didn't work.....hmmmm
Click to expand...
Click to collapse
Yep, me too... Didn't make a difference.

hpmaxim said:
Yep, me too... Didn't make a difference.
Click to expand...
Click to collapse
Going to try that buildprop edit. I'll report back as soon as I'm done.
Update: The buildprop edit from http://www.andromods.com/fix-troubleshoot/fix-xposed-framework-shealth-problem-galaxy-s5.html
worked. Xposed and S Health working now.

Shadeoblac said:
Going to try that buildprop edit. I'll report back as soon as I'm done.
Update: The buildprop edit from http://www.andromods.com/fix-troubleshoot/fix-xposed-framework-shealth-problem-galaxy-s5.html
worked. Xposed and S Health working now.
Click to expand...
Click to collapse
I had the same problem with S Health, but there is an xposed module that will fix the issue for you. Just search in the download section of xposed.

hpmaxim said:
Yep, me too... Didn't make a difference.
Click to expand...
Click to collapse
allaidback said:
I had the same problem with S Health, but there is an xposed module that will fix the issue for you. Just search in the download section of xposed.
Click to expand...
Click to collapse
I'll check it out, but it's working fine now. Now if I could only remember how to get the SD back to normal again.

TWRP should be out today so we can root via an actual Sprint method if you guys wanted to wait a little longer. I believe you can even root via CF now.
Sent from my SM-N910P using Tapatalk