Related
I have installed several of the 2.1 roms out there. Each one that i install causes my phone to randomly restart. Is this a common issue with anyone else? As soon as I go back to 1.5, the restarting stops.
I am having the same issue on the stock 2.1. The only answer I have gotten from HTC is hard reset. But I have already done this twice. So I am going to root my phone and hopefully get rid of this problem. It only started after I updated to 2.1.
BigDiz007 said:
I have installed several of the 2.1 roms out there. Each one that i install causes my phone to randomly restart. Is this a common issue with anyone else? As soon as I go back to 1.5, the restarting stops.
Click to expand...
Click to collapse
Silly question perhaps, but are you completely wiping data and dalvik cache before flashing any of these 2.1 ROMs? Sometimes this happens if you don't do a full wipe before installing new ROMs.
I'm having the same issue, and I did a full wipe, installed several different roms and finally settled on aloysius
i've had the same problems with every 2.1 rom with the exception of darchdroid.
for me it usually happened after i placed a phone call and tried to hang up
and yes everything was wiped before flashing....
im having the same issue i knew i wasnt the only one, has anyone figured out why this is???
I am getting that error trying to install ZenEXP.
Same issue here, only mine's been doing it out of the box, as I got mine the day the EVO was released. I've rooted it and attempted to install several ROMs hoping to get rid of the issue, but had no luck so far. Never had the luxury of having 1.5, as mine came with 2.1, so I just thought it was the phone, honestly. Interesting to know the issue doesn't occur with 1.5...
Anybody got a copy of the stock 1.5 from original release? I'd like to give it a shot.
I do not have any issues that have been listed here. I am running fresh rom and everything is working great.Just wanted to make sure all views arebeing represented in this thread
hmmm....had a thought, did the phone get really hot when it happened....cause that is what happened when i was on fresh....
NomadHellfire said:
Same issue here, only mine's been doing it out of the box, as I got mine the day the EVO was released. I've rooted it and attempted to install several ROMs hoping to get rid of the issue, but had no luck so far. Never had the luxury of having 1.5, as mine came with 2.1, so I just thought it was the phone, honestly. Interesting to know the issue doesn't occur with 1.5...
Anybody got a copy of the stock 1.5 from original release? I'd like to give it a shot.
Click to expand...
Click to collapse
You won't be able to go back to the stock 1.5 original. That has been tried already by a bunch of developers here and it didn't work. You would probably be able to flash a 1.5 ROM (browse way back into the Development pages forum here), but since you had stock 2.1, there's no way for you to go back to stock 1.5.
For all the rest of you, not sure why you are getting random reboots, but as mentioned in the previous post, sometimes the Heros do that when they get overheated or overworked. It would be best to root and start with a very stable, non-overclocked ROM. A couple of the most stable and reliable stock-based ROMs here in this section are DamageControl 2.09.1 and nfinitefx45's Stock 2.27.651.6. I recommend you try either of those out if you haven't already -- hopefully that will fix/solve some of your troubles.
Please report back if any if you have success or more problems with these...we want to make sure you get the help you need
overheating is defiantly not whats causing my restarting. im not trying to thread hijack so ill provide a link to the thread i started about this same issue. in my thread i have attached bug reports (i think thats what they are) and now i have stopped receiving help just when i provided the info needed to see whats casuing this
http://forum.xda-developers.com/showthread.php?t=684727
Im not any good at code so i cant read the big reports well. but i believe its a hardware issue because there is a small presentage of people having these errors and i cant seam to get anyone to be able to reproduce this if it doesnt happen to them.
shawnwojcik said:
overheating is defiantly not whats causing my restarting. im not trying to thread hijack so ill provide a link to the thread i started about this same issue. in my thread i have attached bug reports (i think thats what they are) and now i have stopped receiving help just when i provided the info needed to see whats casuing this
http://forum.xda-developers.com/showthread.php?t=684727
Im not any good at code so i cant read the big reports well. but i believe its a hardware issue because there is a small presentage of people having these errors and i cant seam to get anyone to be able to reproduce this if it doesnt happen to them.
Click to expand...
Click to collapse
Sorry, I don't understand much of the code myself. And I think a handful of our devs here who understand all that coding have already moved on to the EVO. I read your other thread too but don't know what else to suggest. Wish I could help more. You could just be one of the unlucky few who got a bad, buggy phone right out of the box.
Have you thought about just calling Sprint customer service and asking for a replacement phone? Certainly with all the trouble you're having it may be worth it. I think even if you don't have the insurance plan, a replacement phone is only around $35.
@chromiumleaf, yeah sadly i think its time for a different phone.
Ok, so I've been trying this for the last two hours, and here is what I get:
gyazo.com/5c509d2ca71adcc9d011c2583dbf7f0d
Device not found, I've went through updating driver processes, I can't possibly think of what I'm doing wrong?
Help much appreciated,
Thanks,
Alex
Has anyone been keeping track of how many threads are started every day with this exact same issue, I am sure the last one is still on the main page if anyone even wants to bother looking
asb2164 said:
Has anyone been keeping track of how many threads are started every day with this exact same issue, I am sure the last one is still on the main page if anyone even wants to bother looking
Click to expand...
Click to collapse
Boy you can't even count those now
to write this takes longer than a search !!!
Hi buddies
As Grarak chose to close the thread of his rom and that maybe some of you want to have some more return and exchanges about the way the rom works, discuss about bugs etc, i open this thread, so that we will be able to do what a forum is done for : talk and exchange together.
New version is 12082014, any return?
Testing soon..
Is calling with sim 2 in 2g working Now?
If not how to use it Any tetsters!
Edit :still No sound from sim2
and there is No way to chose network type
and No 3g from sim 2 too
Im on 9-12-14 build....2g sim not working same as official cm11....3g sim is working......
i 've had terrible battery life, and searching on google lead me to a battery misc processus eating battery, problem solved with 5.0.1 by google
do you guys have the same experience, and have heard about a fix incorporation in the new builds? :good:
I had to go all the way back to the 11-20-14 build. I tried updating to the new builds 12-8, 12-9 and 12-10. No data at all on any of these builds.
Flashed the newest build! We're on Lollipop 5.0.1 now This update is supposed to help battery life. We'll see.
The new music app automaticaly force closes, and the DSPmanager was replaced with AudioFX.
thank you guys for these feedbacks.
Foxy, when you say the new music app, you mean the cyanogenmod one? strange, what could have change ?
Audio playback is fixed now ?
fabulous69 said:
thank you guys for these feedbacks.
Foxy, when you say the new music app, you mean the cyanogenmod one? strange, what could have change ?
Audio playback is fixed now ?
Click to expand...
Click to collapse
I don't know? It's just called "Music" but the icon is like a poorly designed not lollipop looking purple circle. But Apollo is gone so I suppose that's it. And audio playback works, just the app crashes right when I open it.
FoxyDrew said:
I don't know? It's just called "Music" but the icon is like a poorly designed not lollipop looking purple circle. But Apollo is gone so I suppose that's it. And audio playback works, just the app crashes right when I open it.
Click to expand...
Click to collapse
mhm then i think a change that has broke the app. I m sure Grarak will correct it in the next release
Ok, the ROM was going great for me, then yesterday at work my phone turned off when it was in my pocket. I tried turning it on, it booted, started doing the boot animation and then did that for five minutes before it shut off again. This time it wouldn't turn back on no matter how many times i tried power cycling or booting into bootloader. When I got home I tried charging it and the light wouldn't even come on. So I plugged it into my PC and the phone showed up as qhsusb_bulk. After researching that i found it means the bootloader got wiped somehow. My question is, how could my bootloader be gone, because as far as I know, no one has gotten their device S-OFF.
your device is bricked
seems there is a solution on the web but not working for everybody and for specific devices
i dont know what to advice you...
i dont know if it is rom related, but if it is, i wont flash this !
Yes that's what i figured. Luckily Amazon was nice enough to give me a new phone once I send that one in. I was just trying to figure out how it would even be possible that my bootloader got fried, considering my device was still S-ON.
any one who tried this rom found any bugs ???????? i want to know the bugs and want to know in htc 816 daul the second sim worked or not
DRAGONMM2010 said:
any one who tried this rom found any bugs ???????? i want to know the bugs and want to know in htc 816 daul the second sim worked or not
Click to expand...
Click to collapse
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
kr338r said:
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
Click to expand...
Click to collapse
Completely agreed.
kr338r said:
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
Click to expand...
Click to collapse
yes, no doubts on his knowledge there!
@FoxyDrew
do you experience better battery life now that we have 5.0.1 ? thx
fabulous69 said:
yes, no doubts on his knowledge there!
@FoxyDrew
do you experience better battery life now that we have 5.0.1 ? thx
Click to expand...
Click to collapse
Didn't test it. Haven't spent enough time on Lollipop because of the no data issue.
I've been playing around with the lastest builds, and I'm actually getting LTE to work without modifying anything, I just have to let it sit for a WHILE and it connects and works quite well.
HOWEVER, I have been getting a corrupt data partition issue with some non-google play apks. I assume that since the build are already not stable, adding homemade, root apks that modify data might cause some corruption. I'll keep playing with it and report back any further updates on how this may be happening.
thirteen_percent said:
I've been playing around with the lastest builds, and I'm actually getting LTE to work without modifying anything, I just have to let it sit for a WHILE and it connects and works quite well.
HOWEVER, I have been getting a corrupt data partition issue with some non-google play apks. I assume that since the build are already not stable, adding homemade, root apks that modify data might cause some corruption. I'll keep playing with it and report back any further updates on how this may be happening.
Click to expand...
Click to collapse
Yah data works...just not good. It has to do with not being able to access APN's.
No one want's to sit "for a WHILE" to open a webpage or read an email.
On the latest build, System UI crashes.
i have a machine with linux on it and a remote desktop client called teamviewer for those who would want to help get one of these roms ported so to speak. further more anyone have ideas or know how to fix other issues as well as kernels. then post here let us know although my post its not just for me. i will also keep posting my progress here from now on. if anyone wants to learn what i learned i have a discord server where we can voice at. its hard to actually type and explain and the other machine can show as i talk about what ever. so feel free to post what ever as well if u just want me to call it quits let me know down bellow. i figure we get enough people who know stuff bout each of the process we might get farther then just me. then im gonna try to develop my own rom that will be awhile xd. i learned what i know in like a month so im no expert but i love learning new stuff as well as knowing i accomplished something good.heres what i got so far auto brightness doesnt work double tap does not work although its in the settings. wifi is still broke im getting closer to get wifi but maybe some new eyes can help with the kernel configs or symlink or well you get the picture.https://www.androidfilehost.com/?fid=457095661767145938heres how to flash goto twrp goto wipe do the delete data option that has you type yes. then just restore backup normal way in twrp. sorry first one was a old broke version posted new link. also install install one of these when ur finish restore http://opengapps.org/if this was helpful please hit the ty button. if u feel the need to donate thats there as well enjoy and maybe we can get rr marsh mellow to at least be our temp os. after you load it up at least once i recommend going back to twrp and doing the factory restore option
before u proceed to other stuff
discord code to join my server Hf9x6a5. make sure u install 64bit gapps
bump
about to test
madvane20 said:
https://www.androidfilehost.com/?fid=457095661767145938heres how to flash goto twrp goto wipe do the delete data option that has you type yes. then just restore backup normal way in twrp. sorry first one was a old broke version posted new link. also install install one of these when ur finish restore http://opengapps.org/if this was helpful please hit the ty button. if u feel the need to donate thats there as well enjoy and maybe we can get rr marsh mellow to at least be our temp os. after you load it up at least once i recommend going back to twrp and doing the factory restore option
before u proceed to other stuff
discord code to join my server Hf9x6a5. make sure u install 64bit gapps
Click to expand...
Click to collapse
I am going to give this a spin and see how it does to give you feedback and to "field test it". i know i said that i was going to try to port a rom myself but im willing to admit that i got in over my head and just simply dont have the time to learn how to do so. im really excited to try what you have accomplished so far however. will let you know how it goes!. thanks again.
jarrettsuydam said:
I am going to give this a spin and see how it does to give you feedback and to "field test it". i know i said that i was going to try to port a rom myself but im willing to admit that i got in over my head and just simply dont have the time to learn how to do so. im really excited to try what you have accomplished so far however. will let you know how it goes!. thanks again.
Click to expand...
Click to collapse
k i just bout got crdroid done after i fix this error it should finish compiling
someone else i know said it runs good they might post i think it runs nice and fast just the wifi is killing me on that one but if i get crdroid working then thats a step to get the rest
jarrettsuydam said:
I am going to give this a spin and see how it does to give you feedback and to "field test it". i know i said that i was going to try to port a rom myself but im willing to admit that i got in over my head and just simply dont have the time to learn how to do so. im really excited to try what you have accomplished so far however. will let you know how it goes!. thanks again.
Click to expand...
Click to collapse
Yeah the Rom was pretty good, very fast, compared to the stock rom.
stuck with this error on crdroid
hardware/qcom/audio-caf/msm8916/hal/audio_hw.c:438:14: error: use of undeclared identifier 'SND_AUDIOCODEC_ALAC'
id = SND_AUDIOCODEC_ALAC;
^
hardware/qcom/audio-caf/msm8916/hal/audio_hw.c:441:14: error: use of undeclared identifier 'SND_AUDIOCODEC_APE'
id = SND_AUDIOCODEC_APE;
its like 70 or so % done
madvane20 said:
k i just bout got crdroid done after i fix this error it should finish compiling
someone else i know said it runs good they might post i think it runs nice and fast just the wifi is killing me on that one but if i get crdroid working then thats a step to get the rest
Click to expand...
Click to collapse
yeah it wont be a DD without wifi but im light on using data anyhow for the time being. what version of crdroid are you making? im not personally interested in any particular version of android i just cant wait any longer to rid myself of EMUI as a whole beyond what im already able to. i dont know if either of you had any issues or maybe it was just me, but copying RR to my ext-sd twrp folder it would just stop copying and i tried it both from within twrp and android. i had to copy it directly to the root of the ext-sd. anyway im installing now just wanted to let you know what was up so far over here.
Edit: I'm sure this wont apply to those who cant figure it out as you shouldnt mess with it anyway if you couldnt but, you have to remove the "_image" from the end of the system backup file in order for twrp to see that partition and be able to restore it.
jarrettsuydam said:
yeah it wont be a DD without wifi but im light on using data anyhow for the time being. what version of crdroid are you making? im not personally interested in any particular version of android i just cant wait any longer to rid myself of EMUI as a whole beyond what im already able to. i dont know if either of you had any issues or maybe it was just me, but copying RR to my ext-sd twrp folder it would just stop copying and i tried it both from within twrp and android. i had to copy it directly to the root of the ext-sd. anyway im installing now just wanted to let you know what was up so far over here.
Edit: I'm sure this wont apply to those who cant figure it out as you shouldnt mess with it anyway if you couldnt but, you have to remove the "_image" from the end of the system backup file in order for twrp to see that partition and be able to restore it.
Click to expand...
Click to collapse
is android n im stuck atm on compiling but i might be fixing wifi on the rom ur using hope it works. also i this all was way over my head didnt think id make it this farxd
Hey its Jarrett didn't wanna login. RR works amazing and is exactly what I'm looking for from a ROM. Auto brightness works just fine for me, I came directly from b130 BTW. WiFi just sits there trying to turn on but it never does so I can confirm that. Also double tap to lock works for me. Is there anything that doesn't work for you that you'd like me to try and confirm coming from b130 seems to fix the issues you were having other than WiFi not working.
jarrettsuydam said:
Hey its Jarrett didn't wanna login. RR works amazing and is exactly what I'm looking for from a ROM. Auto brightness works just fine for me, I came directly from b130 BTW. WiFi just sits there trying to turn on but it never does so I can confirm that. Also double tap to lock works for me. Is there anything that doesn't work for you that you'd like me to try and confirm coming from b130 seems to fix the issues you were having other than WiFi not working.
Click to expand...
Click to collapse
see if nfc is there and works if so then yea only thing left is wifi and what ever minor bugs after that. so does it run much better than stock? also anyone have any luck or have ideas to fix the wifi?
madvane20 said:
see if nfc is there and works if so then yea only thing left is wifi and what ever minor bugs after that. so does it run much better than stock? also anyone have any luck or have ideas to fix the wifi?
Click to expand...
Click to collapse
I do not have a way yo test NFC but yes this ROM is butter smooth and leaves much more room available while also allowing you to use an SD card as expanded system storage. I have yet to find any bugs or settings that do not work as intended other than WiFi and double tap to wake but only WiFi is important to me.
jarrettsuydam said:
I do not have a way yo test NFC but yes this ROM is butter smooth and leaves much more room available while also allowing you to use an SD card as expanded system storage. I have yet to find any bugs or settings that do not work as intended other than WiFi and double tap to wake but only WiFi is important to me.
Click to expand...
Click to collapse
ok well since i been hitting alot of wall trying to get n up and running gonna see if i cant get a working kernel compiled for rr mm til then wish i had some help xd but i will do what i can cant expect to much only a month or so in on learning etc. later once i learn how im gonna go for a stab at enabling otg if its even possible on this phone
madvane20 said:
ok well since i been hitting alot of wall trying to get n up and running gonna see if i cant get a working kernel compiled for rr mm til then wish i had some help xd but i will do what i can cant expect to much only a month or so in on learning etc. later once i learn how im gonna go for a stab at enabling otg if its even possible on this phone
Click to expand...
Click to collapse
Im near certain that this phone hardware wise does not support otg. But if we get WiFi I'll be sure to hit that donate button. Thank you for what we have so far. Its running great and everything I wanted is available. Even audio over USB works just fine.
jarrettsuydam said:
Im near certain that this phone hardware wise does not support otg. But if we get WiFi I'll be sure to hit that donate button. Thank you for what we have so far. Its running great and everything I wanted is available. Even audio over USB works just fine.
Click to expand...
Click to collapse
i was gonna about the audio over usb looks like u done posted that is the speaker loud enough for speaker phone if not i will tweak that. also i might of not been a developer when i started but by the time im done i guess i can consider myself a developer xd
madvane20 said:
i was gonna about the audio over usb looks like u done posted that is the speaker loud enough for speaker phone if not i will tweak that. also i might of not been a developer when i started but by the time im done i guess i can consider myself a developer xd
Click to expand...
Click to collapse
Speakerphone is a little quite but tolerable when playing a YouTube video. I suppose it could go up a little bit. Until I run into other situations that's all I have for you right now.
jarrettsuydam said:
Speakerphone is a little quite but tolerable when playing a YouTube video. I suppose it could go up a little bit. Until I run into other situations that's all I have for you right now.
Click to expand...
Click to collapse
yea i think i can fix speaker easy the wifi i have to compile a complete kernel with drivers etc designed for it
I found another bug, it may be kernal related. When watching videos via the YouTube app that video may freeze while Tue audio continues playing. This has been occurring since installed.
jarrettsuydam said:
I found another bug, it may be kernal related. When watching videos via the YouTube app that video may freeze while Tue audio continues playing. This has been occurring since installed.
Click to expand...
Click to collapse
ok well im working on rebuilding the kernel with new compiled drivers i will send u it to test when im done if u want hopefully i fix wifi as well. im surprised noone has offered any help or got everything working. guess i will keep trying. i have noticed in stock that there is a process running called usb otg so makes me wonder why otg doesnt work
madvane20 said:
ok well im working on rebuilding the kernel with new compiled drivers i will send u it to test when im done if u want hopefully i fix wifi as well. im surprised noone has offered any help or got everything working. guess i will keep trying. i have noticed in stock that there is a process running called usb otg so makes me wonder why otg doesnt work
Click to expand...
Click to collapse
I've been intending to work on it, but I'm on vacation with the family this week so my time has been short.
I wanted to start a thread in the AT&T forum for everyone to share there successes and workarounds after rooting with Samfail. I know there is a thread for the root process here https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340 But i wanted this to be a place where we can share also what works for the AT&T phones.
I just rooted tonight, so far all i have done is disable the AT&T bootup sound but going to /system/omc/ATT/res/media/audio/ui and renaming PowerOn.ogg to read PowerOn.ogg.bak
As i figure out more things I'll keep updating the op.
Please feel free to share any tweaks you may know.
dirtydodge said:
I wanted to start a thread in the AT&T forum for everyone to share there successes and workarounds after rooting with Samfail. I know there is a thread for the root process here https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340 But i wanted this to be a place where we can share also what works for the AT&T phones.
I just rooted tonight, so far all i have done is disable the AT&T bootup sound but going to /system/omc/ATT/res/media/audio/ui and renaming PowerOn.ogg to read PowerOn.ogg.bak
As i figure out more things I'll keep updating the op.
Please feel free to share any tweaks you may know.
Click to expand...
Click to collapse
As I sure you've seen my complaining in the root thread -- My main issue is the inability to get full calling features
It is very weird from my perspective in that everything seems to provision properly. I can make WiFi Calls but if I turn Wifi off then try ot make a call the call Ends suddenly unless I turn Enhanced LTE services off. But the really weird thing is that I can make calls in the area near my work (it is a bit more remote than where live) and it does appear that the calls are being made VoLTE. So why would the network in one place allow the calls to go through but in another the calls suddenly end ??? I think the answer to this might be the clue to getting this issue fixed for AT&T users.
I know many of you don't need the full calling features but for me it is essential and I would go without root if I can't find a solution :crying::crying:
jcrompton said:
As I sure you've seen my complaining in the root thread -- My main issue is the inability to get full calling features
It is very weird from my perspective in that everything seems to provision properly. I can make WiFi Calls but if I turn Wifi off then try ot make a call the call Ends suddenly unless I turn Enhanced LTE services off. But the really weird thing is that I can make calls in the area near my work (it is a bit more remote than where live) and it does appear that the calls are being made VoLTE. So why would the network in one place allow the calls to go through but in another the calls suddenly end ??? I think the answer to this might be the clue to getting this issue fixed for AT&T users.
I know many of you don't need the full calling features but for me it is essential and I would go without root if I can't find a solution :crying::crying:
Click to expand...
Click to collapse
Yea i never video or WiFi call (ok maybe have yo WiFi call about 2 or 3 times a year) so losing those two things don't bother me. I've always turned off enhanced lte services since they introduced it simply because it drains more battery plus from what I've googled about it, it don't really pertain to anything i need. I am hopeful though that once people start to use this root method, we'll start to figuring out how to fix everything like normal.
I'm not really sure the purpose to use this root method, its not even really root to begin with. What are your plans with using this method? I mean there are a few fun things to do but not worth a unstable system and 80% battery.
timmy10shoes said:
I'm not really sure the purpose to use this root method, its not even really root to begin with. What are your plans with using this method?
Click to expand...
Click to collapse
Why do you say "it's not really root to begin with"? By doing this method you gain access to root files and to the heart of your phone. SuperSU installs and works, you are able to deodex, theme, modify all as you want if you know what your doing. Sure there are a few issues with it (battery limited to 80%, WiFi calling, and camera) but none of this will get fixed we work on finding out the issue, but root has always brought about some type of issue one way or another in locked bootloader devices. My plan with rooting my phone is to build my rom with the tweaks and mods that i like, run the ad blockers that i like, possibly install xposed (haven't used it in a while). One of the main purposes of root in my opinion is to make your phone the way you like it. I mean you can sit around and wait for someone to make the phone how they like it and then possibly share it with others or you can take the initiative to learn yourself. Not really root to begin with? It's root, just not how it used to be. I hope someone does figure out a different root method that don't render the battery to 80%, i wish i knew how to look for exploits (I'm currently trying to learn) but until then, this is what we have. What are your reasons for believing this is not a real root method?
timmy10shoes said:
I mean its not really root because they are using a modified system file, not finding a real working exploit. It is a leaked factory image and a leaked factory kernel that needs to go with it. The 80% isn't going away. Its built into the kernel with can't be touched or motified. But we can always dream
Click to expand...
Click to collapse
Well that's why I'm still hoping for a different root method they don't have to use leaked files. But i can say that this root method runs a lot smoother than the method we had to use in the S7. This method hasn't been out very long, but is say within the next few months we'll start seeing more development happening . Or at least i hope. I've just recently started making my own roms (i don't release them to anyone being as I'm still learning and can't give a lot of trouble shooting assistance) but it's fun for me to pass the time at work. (I have a real laid back job with nothing to do a lot of times lol)
I mean its not really root because they are using a modified system file, not finding a real working exploit. It is a leaked factory image and a leaked factory kernel that needs to go with it. The 80% isn't going away. Its built into the kernel with can't be touched or motified. But we can always dream
---------- Post added at 04:48 PM ---------- Previous post was at 04:44 PM ----------
I get the fun part of it, thats why I use unlocked devices to flash the good stuff.
timmy10shoes said:
I mean its not really root because they are using a modified system file, not finding a real working exploit. It is a leaked factory image and a leaked factory kernel that needs to go with it. The 80% isn't going away. Its built into the kernel with can't be touched or motified. But we can always dream
---------- Post added at 04:48 PM ---------- Previous post was at 04:44 PM ----------
I get the fun part of it, thats why I use unlocked devices to flash the good stuff.
Click to expand...
Click to collapse
I've thought about buying am unlocked device but have read conflicting posts about service and radio bands messing that are used here in the US so I've always shyed away from them.
I have developed a few roms myself for the Bionic and Razr. Its highly entertaining and I want it myself but there hasn't been true root since the note 3 I believe.
---------- Post added at 04:54 PM ---------- Previous post was at 04:53 PM ----------
dirtydodge said:
I've thought about buying am unlocked device but have read conflicting posts about service and radio bands messing that are used here in the US so I've always shyed away from them.
Click to expand...
Click to collapse
I use unactivated devices. There is a ton on trial and error so I don't use my daily driver for that.
Are there any ROM anywhere for the snapdragon? Also anyone know where the stock firmware is located or can be found? When you go back,is it like it never happened ?
Don_Pachuco said:
Are there any ROM anywhere for the snapdragon? Also anyone know where the stock firmware is located or can be found? When you go back,is it like it never happened ?
Click to expand...
Click to collapse
No roms yet (on AT&T at least that i know of). Not trying to be rude but do you even search, see attached picture. Literally 4 post down from this thread.
I did search, and the one thread that I found, says "link removed". Then further down, it has files for the S8+.
Don_Pachuco said:
I did search, and the one thread that I found, says "link removed". Then further down, it has files for the S8+.
Click to expand...
Click to collapse
https://forum.xda-developers.com/att-galaxy-note-8/how-to/n950u-odin-5-files-stock-firmware-t3715770
Help!!! Please help!!!!
This is my first time with odin or basically anything computer related i am stuck at 2nd step of samfail. can some one please tell me what to do. it says fail (auth) thank you in advance. I have already done step 1 and it failed just like the instructions say but now in step 2 it fails every time. I'm stuck please help!
truly in over my head hear
jforest3026 said:
This is my first time with odin or basically anything computer related i am stuck at 2nd step of samfail. can some one please tell me what to do. it says fail (auth) thank you in advance. I have already done step 1 and it failed just like the instructions say but now in step 2 it fails every time. I'm stuck please help!
truly in over my head hear
Click to expand...
Click to collapse
This is a thread for mods done after rooting, post questions about getting rooted in your root thread please.
https://forum.xda-developers.com/ga...nt/root-samfail-galaxy-note8-t3685340/page323
the %80 max battery issue
I've enjoyed a rooted Note 8(sm-n950u) Nougat7.1.1 for over a week via samFAIL method and am quite thankful to the samfail/pwned team for providing it.
The max battery issue is the only drawback as far as I've noticed so far. I have a nice and speedy phone that is devoid of bloating apps, and vendor/carrier garbage.
As far as the max battery issue, I've done some digging and haven't found a cure yet.
I've noticed a couple things.
in /efs/Battery and in /sys/class/power_supply/battery there is a file named batt_capacity_max that has something to do with the max battery limit which is obvious by name of course.
Notes:
1. You can not change the value in /sys/class/power_supply/battery/. You can edit and write the file without any error or sign of failure; But checking the file immediately afterwards, you'll find that the contents did not change.
2. You can change the file in /efs/Battery/, but the contents are reset upon reboot.
3. The file contains only a number.
In my case, batt_capacity_max contains the number 1000 regardless of the charged state. i.e. It is 1000 when the phone if charged to max, and it is 1000 when the phone is nearly drained.
I change the value to see if it has any effect, and it does.
I interpreted the 1000 as binary 8, and changed to number to 1010 (binary 10). Then I charged the phone only to find that I could not charge the phone past 17% eep! This wasn't a problem though as rebooting the phone or returning the file to its original value restored the function to normal(rooted normal, that is..max 80%).
I've also deleted the file, then charged the phone to find that there was no effect.
I then came across a slightly older xda thread charge to 100 snapdragon root(s8 sampwn)
The thread had a great number of contributors and provided a great deal of background info, but the method described therein has become obsolete or does not apply to the Note 8 i believe.
If anyone has discovered anything effective regarding the battery max limit, I hope they will contribute that info here, or at least link to an existing thread that I may have missed.
One thing I would like to understand is what processe(s) are being employed in this battery limit system. Is it merely a sub-function of the SafetyNet, or something else? I've filtered what I believe are the pertinent logs(dmesg and logcat) trying to find reference to batt_capacity_max but have come up empty.
I have't tinkered with this in a couple days, but I plan to get back to it tomorrow. Anyone has ideas or suggestions, please contribute. personally I don't really care wether I "fix" this issue as much as I am using this pursuit to glean a better understanding of the android/samsung subsystems relative to it. .. to fix it, of course, is ideal.
delete