Related
I loved the 1.8 ghz overclock with the temp root, but now I am S-OFF/perm rooted...how do I get this to be permanent as well? When I run the perma-temp root with overclock and hulu fix, none of that stuff seems to stay after reboot. Any ideas? Thanks in advance.
I'm Having the same issue, but i believe that the program has to be run around differently. I've only messed with one other android device and OC has always been through the kernel. So im guessing that was a S-ON workaround to a S-OFF solution. Kinda like bringing a gun to a bomb fight if that makes any sense. Now we will have UV/OC Kernels soon, and its not like this phone is slow without the OC. Just sit back and let the amazing devs take care of you man.
Yeah I wish I knew how to code and could help! I am tech savvy enough that I can usually figure out some fixes/workarounds on my own without having to pester the devs, and I'm sure it'll be here soon (wouldn't put it past one of them getting it out tomorrow, but not holding my breath) as we finally just got root today.
I thought it was in the kernel, and figure I could just flash a new one in recovery, but all I've seen use adb right now and I'm not to great with that unless it is spelled out for me.
Thanks again for all the amazing work to everyone that has helped these past weeks!
The process pushed a .ko (linux kernel) file to the kernal that regulated the clock speed and voltage. Just wait for a custom kernel, it will be faster and more stable.
To go 2+ days without freezing and/or randomly rebooting?
Lol huh? I don't have this problem ever...
So far:
Deck ROM: yes, could go weeks without rebooting.
CleanROM: yes, only had it about 2 days but no problems
Synergy: no, tried every kernel and it wouldnt go more than about 12 hours without a hard crash.
About all I've tried at length
Sent from my PG86100 using xda premium
Nope. And it always screws up when I need it the most.
Sent from my PG86100 using Tapatalk
My personal ROM has actually never needed a reboot or crashed.
Via My HTC Evo 3D On The Now Network From Sprint.
Every ROM I've ran except some of myn's nightlies were completely stable.
Synergy - very stable
Cyanogenmod - seems to be the stablest
InfectedROM - Kind of stable
Myn's 2.3 - Not really stable, but these are experimental nightly builds we have
If it reboots randomly and freezes a lot, there is most likely too many apps running or similar stuff that is causing that. I use my phone heavily and have never experienced reboots/freezes/shutoffs.
Steelh never had an issue works for days before reboot just to clean up
Gotcha, nice replies guys.
I refuse to run ROMs with several broken things, aside from AOSP, which is understandable.
Cm7 on airplane mode. No service so im good with wifi. 3D movies. ONLY reboot I ever had was adding 2000 songs to my sdcard. Phone couldnt handle it for 10 minutes. Then it scanned properly and good to go again.
Whooo! (Cole Voice...)
Basically, the reason I'm asking is because virtually every single frequently updated Sense ROM in the development section is full of issues people are having. I'm trying to understand why they are so popular if they are riddled with issues every other update. Do people not enjoy stable phones? I've been running the same ROM since July and to this day there isn't a single 'new' feature that has been implemented in ROMs these days that I don't want. If there happens to be one, it doesn't need a full flash.
My question is: Why are so many people using Sense ROMs that have nothing but issues and stuff that doesn't work properly? Since HTC has already provided a fairly solid foundation with the Stock ROM, how are so many Sense ROMs broken?
If the answer is aesthetics and looks, why not take a stable ROM, and work from there to get the look you want?
I'm also trying to understand the mind of a "Flashaholic" and besides AOSP or MIUI, there doesn't seem to be enough differences between these Sense ROMs other than kernels and random fiddling with the framework that really differentiate them. For a person that understands how ROMs work and can easily determine the core differences between them, I can tell you exactly what differences that ROM A has from ROM B, and yet, the user opinion is much wider.
Take for instance ROM A, which has a cute tagline in its title and is made by a 'veteran' so to speak. The changelog and file-by-file difference between that and ROM B, made by a seemingly unknown person are pretty small, but the audience seems to think ROM A is much more 'stable' and 'fast' than ROM B.
Aside from messing with the framework, I have done side-by-side comparisons of where most of the ROMs features claim to shine--its tweaks to memory, ram usage, cpu, kernel, etc; which reside mostly in the /system/etc folder and under build.prop and the differences are so small and most of the tweaks are identical. With that said, framework 'tweaks' make a minimal difference in every day situations and most phones will perform almost identical to the Stock ROM. The real differences lie in random build.prop tweaks and init.d scripts which mostly come from poorly documented sites and sources that were meant for Desktop computers and/or older phones like the G1 and can actually have a negative effect on our current phone's performance. I'm sure HTC has done enough research that their method of ROM delivery is probably optimal for most people.
At any rate, I'm interested in more discussion from the people in this thread.
Id like to try your dualcore mod with 1st core at 700mhz and 2nd core at 500mhz. Can you make the file for me? But is it possible to get a screen off profile with it?
Whooo! (Cole Voice...)
I have flashed before due to aesthetics but now I'm on a hunt for a smoother (stutter free) rom. I also like having extra settings that some offer like synergys, and Eternity, and having beats is a plus although not necessary. The closest I've gotten is Eternity 1.3.1 w/stock look along with Tiamat sense 1.0.3 kernel and flashable script by Smokin. Smokins script made a difference in smoothness for me specially in the app drawer. The only issue that plagues my phone is intermittent black screen during calls.
Other reason I flash is sometimes I get tired of things and want something new to play with. Makes me feel I have a new device.
knowledge561 said:
Id like to try your dualcore mod with 1st core at 700mhz and 2nd core at 500mhz. Can you make the file for me? But is it possible to get a screen off profile with it?
Whooo! (Cole Voice...)
Click to expand...
Click to collapse
I can pretty much build a script that can accomplish this
aznmode said:
I have flashed before due to aesthetics but now I'm on a hunt for a smoother (stutter free) rom. I also like having extra settings that some offer like synergys, and Eternity, and having beats is a plus although not necessary. The closest I've gotten is Eternity 1.3.1 w/stock look along with Tiamat sense 1.0.3 kernel and flashable script by Smokin. Smokins script made a difference in smoothness for me specially in the app drawer. The only issue that plagues my phone is intermittent black screen during calls.
Other reason I flash is sometimes I get tired of things and want something new to play with. Makes me feel I have a new device.
Click to expand...
Click to collapse
That I can understand, but with the differences between Sense ROMs being so small, why? I suppose looks is a good enough reason as any, especially if you don't know how or feel like trying to extract the apks or images needed to make your current ROM look like the ROM you're installing.
freeza said:
I can pretty much build a script that can accomplish this
Click to expand...
Click to collapse
Thanks. Im on cm7. Do I send you this build.prop or init.d or something? Also I use setcpu, im guessing I wont be able to use it anymore? Screen off profile would be 192-384mhz
Whooo! (Cole Voice...)
Senseless I get way better 4g coverage than any other ROM I've tried. With others my 4g would go on and off every 3-4 minutes. It really bugged me out.
Sent from my 62 inch 3d tv.
I flash roms to have wireless tether mainly. Recently i like using sprint hotspot and it ia easier to flash a modified stock rom instead of tracking down the flashable hack. Other than staying up to date with software without breaking root, i dont see a reason not to be stock rooted. I buy htc for sense so aosp roms just arent for me. Im running infected eternity 1.4.1 and love the themed look just because it seperatea me from the rest if the world, if i wanted to fit a mold i would be rocking that girly iphone.
Sent from my PG86100 using XDA Premium App
Freeza,
What ROM are you using?
Sent from my PG86100 using XDA App
yousefak said:
Synergy - very stable
Click to expand...
Click to collapse
First time I've heard anyone claim synergy is stable. Even the synergy devs have given up trying to get non stock kernels to run reliably with it and have recommended limping along by flashing the stock kernel over the included one until the ROM can be fixed.
As to why so many problems: I think half of it is kernel compatibility and half is in the baking. Some bake in the latest version of this or that apk that hasn't been thoroughly tested. Market 3.2 is a good example. Doesn't work: can't buy paid apps. Same problems occur with other apps like all the borked superuser updates between 3.0.2 and 3.0.6. So with all the pushing to include the latest versions of every low level app baked into the ROM, of course there will be some mismatches.
Not a fan of AOSP ROMs. Most of those don't have 20% of the stuff working like 4g, 3d camera, and other stuff. Most say right at the top, "dont expect this to work... Or that to work". No thanks.
Sent from my PG86100 using xda premium
Could dual cores always being on cause damage to the phone?
Via My HTC Evo 3D On The Now Network From Sprint.
http://forum.xda-developers.com/showthread.php?t=1158951
That can probably be done with this phone since it uses the same chipset as the E3D and Sensation. Once I get mine next tuesday/wednesday ill see what I can do about getting this module to work.
If anyone takes a look at it, post anything you have tried. This could in theory at the very least allow an undervolt which would help offset the LTE power sucking.
Yeah see I wwas talking about this earlier. I think this will work. I PMed viperboy who actually wrote one of the bloatware scripts when we had temproot. Just waiting for a response AMD hope to get a jump start on this. Good idea starting this thread tho
Sent from my ADR6425LVW using Tapatalk
reverepats said:
Yeah see I wwas talking about this earlier. I think this will work. I PMed viperboy who actually wrote one of the bloatware scripts when we had temproot. Just waiting for a response AMD hope to get a jump start on this. Good idea starting this thread tho
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Coming from the bravoc which has almost zero development aside from 2fast at his site I am used to just thinking of things to try. I was able to port a couple dinc roms to it even though I was told it couldn't be done. I hope to be much more involved with development here since there are already more posts in this section than there were in a year at the site dedicated to the bravoc
con247 said:
Coming from the bravoc which has almost zero development aside from 2fast at his site I am used to just thinking of things to try. I was able to port a couple dinc roms to it even though I was told it couldn't be done. I hope to be much more involved with development here since there are already more posts in this section than there were in a year at the site dedicated to the bravoc
Click to expand...
Click to collapse
Yeah I.hear ya. I.haven't gotten much Involved myself buy then again I'm no dev LOL. But I k.ow my way around a bit. But I think the dev section is gonna he hoppin as well.
Sent from my ADR6425LVW using Tapatalk
It took a few days to get that inc port almost bugfree (usb pc transfer wouldn't work) but it was otherwise fine iirc. I hope that with support and other work to use as examples i can make some stuff for this device that isn't either a variation of AOSP or a sense port that has some serious drawbacks.
I am personally more interested in the possibility of underclocking and undervolting than OCing. Or maybe OCing and undervolting like I did with my droid x - can really help save some battery and allow the phone to sip less juice. This phone is so new I am getting ahead of myself, but hopefully in time we can get root/roms/OCing and undervolting apps to work on the Rezound.
I normally run my battery on performance mode on all my phones. I set it to normal, and with the equivalent usage I get 1/3 better battery life. I even leave all my antenna's on(except WiFi when I am away).
Just to let everyone know what I tried. I took the file for "unsupported phones" from the link's thread and changed the version number to match the rezound, which is -- 2.6.35.13-g20c5d1d -- . As you can see it was not just the ending part starting with the 'g' that needed to be changed as ours is 2.6.35.13 and the file was made for 2.6.35.10. But since a reboot resets everything I tried it by changing only the part starting with 'g' and it failed saying "Exec format error". So I then changed the entire version string to match ours and adb actually completed the task but the phone rebooted immediately and everything was wiped out again.
I did this before the kernel source was put up on the forums but since I dont have ANY knowledge of messing with kernels I am no help there, but hopefully this can help someone get this mod going for the Rezound.
we don't have perma root like the 3vo did so I don't think this will work until then. But this was a band aid until the kernel source was released so this won't even be necessary anymore.
con247 said:
we don't have perma root like the 3vo did so I don't think this will work until then. But this was a band aid until the kernel source was released so this won't even be necessary anymore.
Click to expand...
Click to collapse
The guy who made Setcpu made a script that allowed oc on the stock kernel on the 3D. It was before perm root. It was right after agrabren found the first exploit and a reboot would return the phone to stock. You temp rooted ran the script from adb and used Setcpu to oc.. Some of the smoothest kernel action the 3D had.. I'm sure same thing is potentially there, just need someone smart enough to do..
Sent from my PG86100 using xda premium
send me a link. Ill take a look at the script.
pstevep said:
The guy who made Setcpu made a script that allowed oc on the stock kernel on the 3D. It was before perm root. It was right after agrabren found the first exploit and a reboot would return the phone to stock. You temp rooted ran the script from adb and used Setcpu to oc.. Some of the smoothest kernel action the 3D had.. I'm sure same thing is potentially there, just need someone smart enough to do..
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Yeah I rememba that man. I was just talking about that the other day. I also mentioned that maybe we can use that somehow but I wouldn't know where TP start. But we need a stable Temp Root first I think. Not degrading anyone's work either.
Sent from my ADR6425LVW using Tapatalk
con247 said:
send me a link. Ill take a look at the script.
Click to expand...
Click to collapse
It will take me a little time to find. I don't think I have the script on sd anymore and the thread is buried deep. I shall go look.
Edit: ironically easier than I thought to find. Here is the thread from the 3D forum.
http://forum.xda-developers.com/showthread.php?t=1158951
And I know for a fact this worked and worked well. I used for a while, well up until we were s-off..
Sent from my PG86100 using xda premium
sooooooo set cpu works with root....i made a profile for screen off. seems to be working.....
combatmedic870 said:
sooooooo set cpu works with root....i made a profile for screen off. seems to be working.....
Click to expand...
Click to collapse
Cool. I did find a tidbit that might (don't get your hopes up and basically pretend I didn't even say this) make root last longer. Obviously until I have my rezound for the next few days I can't even think about testing anything.
Then put it out there for us to test! Don't be selfish! lol
AtLemacks said:
Then put it out there for us to test! Don't be selfish! lol
Click to expand...
Click to collapse
I will once I get around to writing it. I am in class right now then I am driving 5 hours home. So maybe tomorrow afternoon Ill get a script working. Also, I may have figured out a way to disable elements of sense in an automated script(for those that don't like sense).
con247 said:
It took a few days to get that inc port almost bugfree (usb pc transfer wouldn't work) but it was otherwise fine iirc. I hope that with support and other work to use as examples i can make some stuff for this device that isn't either a variation of AOSP or a sense port that has some serious drawbacks.
Click to expand...
Click to collapse
Since I happened to venture to theses parts since our buddy plat ventured to this. I am a bit surprised to see you switched. How ever the module you are talking about in the op I am pretty sure you can't just hex edit the kernel version. As the kernel will be different for the device compared to that of the evo 3d. If it is anything like doing the g2 version for the htc merge that is. Where it had to be recompiled to work correctly.
I am sure one of the dev's familiar in here with building source code could get it done up. If it works after that I am unsure. Though con you ported the sense hd rom from the inc to the desire. That was the only one that you had ported. Followed by you followed samuel2706's guide and other info he gave you. Then you came to me to ask how I fixed the mms and verizon branding in the rom. In which I told you how to fix it but you put it off as you fixed it. As you are putting off in here.
any thoughts? just rooted it yesterday, was trying to figure out what the best kernel is
Stock, lol. Whatever comes on the ROM is going to be your best bet right now.
I am using stock rooted with ziggy kernel due to his having call recording enabled. Works well for me.
Sent from my ADR6425LVW using Tapatalk
I used Ziggy's for a few weeks but like most other users I found that it rebooted itself at least once a day no matter what the clock settings where (innefabilis ROM).
I switched to the OC dsb kernel & it has run absolutely perfectly ever since, but I don't see any huge advantage over just running the stock kernel at this point.
~John
rcrott1 said:
any thoughts? just rooted it yesterday, was trying to figure out what the best kernel is
Click to expand...
Click to collapse
It depends on what ROM you're running to some extent. Also, people are having different experiences running the same ROM/kernel combo so ymmv.
I would decide on a ROM you want to try then read through that ROM's thread and look for issues people are having and what kernels they're using. Then read through the kernel threads and check for issues for it being used with the ROM you like.
It will depend on how you use your phone too. I've read where people running Ineffabilis ROM with ziggy's kernel are fine except if they let the phone charge to 100% while it's on it starts bootlooping. So I could never use that since I usually charge overnight and need to use the phone as my alarm clock. I went with dsb but haven't done any oc/uv tweaking yet.
You can always try one out and then change it if it's not working out for you.
I've personally used ziggy and dsb, I didn't notice much of a difference between either, but dsb was/is SUPER easy to flash, puts boot.img INS ph91img.zip on your sd and reboots to villager for easy install (ziggy might have done this to, I don't remember)
I also used both with inefabliss and didn't notice any issue with ziggy, but results may very!
nerd in training
Have been an Android user since November 2009 when I got my OG Droid, was rooted and ROMed in January after the 2.0.1 update came out and dev's cracked it. I really want a Note 2 but want to be sure we will see ROMs, Kernels and recoveries. From reading the Dev section it seems SBOOT is locked and we can't even get kexec at this point. It sounds like the VZW version may just be locked down too tight to get anything other than just Root. So, given all this, what do you guys think is the liklihood of use seeing custom ROMs, kernels and recoveries on the VZW Note 2?
bose301s said:
Have been an Android user since November 2009 when I got my OG Droid, was rooted and ROMed in January after the 2.0.1 update came out and dev's cracked it. I really want a Note 2 but want to be sure we will see ROMs, Kernels and recoveries. From reading the Dev section it seems SBOOT is locked and we can't even get kexec at this point. It sounds like the VZW version may just be locked down too tight to get anything other than just Root. So, given all this, what do you guys think is the liklihood of use seeing custom ROMs, kernels and recoveries on the VZW Note 2?
Click to expand...
Click to collapse
Custom ROMs is fairly easy. The way the phone was rooted is how one would also do a custom ROM at this point. If we are to get more than that, we're going to need to find a way to unlock the bootloader, which so far, has been futile, but it was also people that have never really done it before trying. Hopefully, an unlock method is found, and we can then go with custom recoveries and kernels, along with easier to flash custom ROMs.
imnuts said:
Custom ROMs is fairly easy. The way the phone was rooted is how one would also do a custom ROM at this point. If we are to get more than that, we're going to need to find a way to unlock the bootloader, which so far, has been futile, but it was also people that have never really done it before trying. Hopefully, an unlock method is found, and we can then go with custom recoveries and kernels, along with easier to flash custom ROMs.
Click to expand...
Click to collapse
So they would have to be just custom versions of the stock ROM correct, since you would have to continue using the stock kernel. Is AOSP basically impossible without unlocking the boot loader and getting custom kernels? I don't want to have to rely on VZW and Samsung for updates, at their pace 4.3 will be out and this will still be on it's current 4.1.1.
just gotta wait for a leak from someone important....hopefully it doesn't take as long as it did for the s3!
bose301s said:
So they would have to be just custom versions of the stock ROM correct, since you would have to continue using the stock kernel. Is AOSP basically impossible without unlocking the boot loader and getting custom kernels? I don't want to have to rely on VZW and Samsung for updates, at their pace 4.3 will be out and this will still be on it's current 4.1.1.
Click to expand...
Click to collapse
You could do something that looks like AOSP, but no, I don't think you could get true AOSP until we get custom kernels.
I've been in Android for a few years now, and I've always defaulted towards AOSP since I hate the heavy overlays that these OEM's place on our devices, but this is the FIRST time in a long time that I will be saying this: why would you even want custom ROM's for this device?
I mean that, honestly. It's perfect. Sure it's nice to get root and modify certain things, but for the most part I don't see any 3rd party ROM trumping stock for this phone. Just the S Pen alone is reason enough to never want to leave stock.
I wasn't really lurking the Note 1 ROM scenes so I don't know how well developers were able to port S Pen functionality over to ROM's like CM10 etc, but I don't imagine they'd ever be able to fully integrate it to the level it is on stock.
And given the immense battery life, top notch performance on stock, I don't see a need to "trim the proverbial fat" of the actual firmware anyway. It's just, perfect.
You can have custom ROMs without getting rid of spen features. I agree with you that I wouldn't want an AOSP ROM but shaving a little weight off this thing wouldn't hurt
Sent from my SCH-I605 using xda app-developers app
Honestly, I'm just waiting for a rom that's debloated, deodexed, has unlimited multiview, wifi toggle, adjustable homescreen, etc. etc. Nothing major, unless some one comes up with some neat ideas on how to integrate the S Pen into the ROM for a better user experience. We've got a good dev community, so I remain optimistic that something cool will come our way.
i agree...i see no need for aosp on this device at this time. just need root and hopefully cwm recovery. samsung has touchwiz dialed in pretty well. however aosp will have its place when this device quits getting updates.
I'd just like it open and custom kernels I don't mind touchwiz on this type of device
Sent from my SCH-I605 using xda app-developers app
Honestly the S Pen is NOT at all what is drawing me to this phone, really couldn't care less about it to be honest. What IS drawing me to this phone is the bigger screen from my G-Nex, the faster processor, the bigger battery and the improved screen. Also the improved radios and data conenction from the notoriously bad G-Nex radios is a huge draw, but none of this is about the S Pen. I know I may be in the minority with my opinion here, but that's at least what I want, and to be honest, when is having more ROMs for a device worse than having less That's why I want AOSP ROMs and custom kernels etc.
bose301s said:
Honestly the S Pen is NOT at all what is drawing me to this phone, really couldn't care less about it to be honest. What IS drawing me to this phone is the bigger screen from my G-Nex, the faster processor, the bigger battery and the improved screen. Also the improved radios and data conenction from the notoriously bad G-Nex radios is a huge draw, but none of this is about the S Pen. I know I may be in the minority with my opinion here, but that's at least what I want, and to be honest, when is having more ROMs for a device worse than having less That's why I want AOSP ROMs and custom kernels etc.
Click to expand...
Click to collapse
+1
But I will admit that I am PLEASANTLY suprised at how nice TW is. With an AOSP JellyBean launcher and lock screen I am really enjoying this thing. I am not sure what could really improve this bad boy other than some cleaned up stock ROM and OC kernel.
Sent from my Super Famicom
xxxxmarkxxx said:
I'd just like it open and custom kernels I don't mind touchwiz on this type of device
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
What I'd a custom kernel going to give you over stock performance? A few added features maybe, but it didn't seem like this phone needs undervolting or overclocking.
bose301s said:
Honestly the S Pen is NOT at all what is drawing me to this phone, really couldn't care less about it to be honest. What IS drawing me to this phone is the bigger screen from my G-Nex, the faster processor, the bigger battery and the improved screen. Also the improved radios and data conenction from the notoriously bad G-Nex radios is a huge draw, but none of this is about the S Pen. I know I may be in the minority with my opinion here, but that's at least what I want, and to be honest, when is having more ROMs for a device worse than having less That's why I want AOSP ROMs and custom kernels etc.
Click to expand...
Click to collapse
Aosp roms are the hardest to get on cdma devices, plus isn't this chip a new one as well? Many hurdles to jump over before that happens.
Sent from my ADR6425LVW using Tapatalk 2
If we could have per app DPI on TW, that would be really cool. I'm confident we'll get this thing unlocked soon enough tho.
Sent from my SCH-I605 using xda premium
im with the others...im very impressed at this UI of this phone. i would like a recovery and perhaps and overclock but the overclock isnt even needed IMO. other than that (thought id never say this) the stock rom nailed it. its apparent the people at samsung not only know what they are doing but listen to the consumer. i dont know how many of you are boaters but phones are like boats. you will never find the perfect one. however judging from the reviews so far this is about as close as it comes...from my point of view anyway..
and to think i was hesitant about getting it. i stood in the store for 30 minutes contemplating it. the rep was about to give up when i said "okay im pulling the trigger". first time i have ever bought a phone and not been 100% sure when i walked through the door.
I guess I have also been spoiled by the phones I have had, the OG Droid and the Galaxy Nexus, honestly I don't think any one phone has had a bigger and more vibrant community than the OG Droid, not even the Galaxy Nexus. I would like to be able to stay on the cutting edge of Android though, knowing that if a new version is released I should have it within 24-48 hours if not less. I am using 4.2.1 on my Nexus and quite like it, seems even smoother than 4.1.2 and also like the few new features, mainly the quick settings panel and PhotoSphere. I know the Galaxy series was one of the originators of the quick setting panel but I like Google's implementation quite a bit. Would just be weird to give up using CM after doing so for almost 3 years now. All decisions to consider. May pick up the phone at Best Buy and see if I like it an return it if I still prefer the Nexus.
There is a thread about them trying to get CM10 on the Note 2, but the VZW version might be the hardest.
http://forum.xda-developers.com/showthread.php?t=2019535
Would it be useful to start a bounty for a bootloader unlock and custom recovery or for CM and AOSP on it? If so I would donate, just wondering what you all think.
I have said in a lot of devices forums in the past that the amount people will be able to do is proportional to the amount of effort and the support the communities give. In this case you guys have already bought adamOutler a phone, and he has torn it down, we have started to analyze the bare bones, and I'm sure hes looking for an unbreakable mod. With this being said lets address a couple of the questions at hand:
First off it does not look like their will be an easy fix to the fact that the bootloader is locked. The way that it looks in the white paper are their are efuses that are used as both a hardware key and possibly a configuration bit. Once this is set it cannot be unset. All hope is not lost though. With adam's UART he has found a couple loading points that might be inject a new bootloader and kernels and such there. However this is a shot in the dark, as it utilizes the fact that there is some security code loopholes in the boot chain to allow for injections.
Secondly there is always the possibility of custom roms. Using subsystems such as 2ndboot and such you can always make it so that you load a new system image onto the existing one, though this means longer boot up times. Also there is another cool thing out there called kexec (this may or may not be enabled in the default kernel). If enabled in the kernel, the kernel can shut down proc1 and then re initiate with a new kernel ontop of it. If properly coded all phones with the root ability have the ability to do this if they can issue a kexec. Kexec has been ported over to many phones, and some of which dont have kexec enabled in the existing kernel. This makes it so EVERY DEVICES THAT HAS ROOT HAS THE POSSIBILITY TO HAVE CUSTOM ROMS. However with kexec not being enabled on ever phone, it makes it hard to program ever phone to have the right kernel injection points.
The last thing is that to the best of my knowledge the bootloader code is not public, which makes it very hard to find vulnerabilities, however it does not mean that they never get found. Time. Time is all we ask for, as this is not our only job and it takes alot of hard work from devs free time to work and develop. With all that being said im sure in time someone some where will find a link.
Wondering if there is any way I can help. I am not new to Android, however I have never gone past using already fully known and documented things, standard rooting etc. I am interested in getting to know things better so if I can be of any help let me know.
Man I think this will be the last time I buy a Samsung phone from Verizon. The way they force samsung to lock down the bootloader is crazy.
Sent from my SCH-I605 using Tapatalk 2