Related
Well my work just got a bunch of iPhones and the CEO got one of the. He had the Samsung before so I got it as an upgrade over my crackberry.
Now I really want to install a custom rom/kernel on the phone but I am hesitating because its really not my phone and my work owns it.
What do you guys think should I stick with stock or should I root the phone and install a rom?
Stock. There's nothing like explaining to the boss how you f'd up company equipment.
I dont know if one should/should not install custom roms on a work phone, as I don't have one. But I can tell you that if you do decide to root and install one of the custom roms, it's not that hard to unroot and go back to stock later on when you need to return the phone. There are several threads here that will guide you through the process too.
jenisiz said:
Stock. There's nothing like explaining to the boss how you f'd up company equipment.
Click to expand...
Click to collapse
I guess your right I just hate being stuck on 2.1 when I know I can have a nice Froyo install. It's just so hard not to do because I have done it with all my other devices.
dsf767 said:
I guess your right I just hate being stuck on 2.1 when I know I can have a nice Froyo install. It's just so hard not to do because I have done it with all my other devices.
Click to expand...
Click to collapse
I hear you...but who's to say he won't ask for it out the blue someday?
Idk, at this point, the fascinate is practically impossible to brick. You also say you have experience rooting and customizing other phones, correct? I say go for it. The only reason I could see not to is due to security issues. Work passwords and etc.. I really don't know too much about all of that tho.
Sent from my SCH-I500 using XDA Premium App
I have a rooted android work phone. All you have to do is read what ppl are saying about the roms and FOLLOW DIRECTIONS and youll be fine.
dsf767 said:
Well my work just got a bunch of iPhones and the CEO got one of the. He had the Samsung before so I got it as an upgrade over my crackberry.
Now I really want to install a custom rom/kernel on the phone but I am hesitating because its really not my phone and my work owns it.
What do you guys think should I stick with stock or should I root the phone and install a rom?
Click to expand...
Click to collapse
Used my fascinating voodoo powers
I seriously discourage doing anything to it. It's not yours for one, and (no disrespect to the devs ofcourse, their work is amazing) there really isnt anything spectacular for this phone at the moment due to samsung's failure to provide any source code. To be more specific... our kernels suck.
And oh yea this shouldve been in the Q&A section so be ready for ashasaur to move this thread. (hes really good at doing that )
Depends on your comfort level, and of course, your corporate policies.
Sent from my SCH-I500 using XDA Premium App
I would say root your phone at the most. It's fairly easy to recover from just rooting, but flashing roms/kernels/modems is much more risky. At least with rooting, you could fairly easily freeze the bloat with TiBu and have a more functional phone. Thawing everything and un-rooting would have you a stock phone back fairly quickly, and you could also still receive OTA updates as well.
I say go for it if anything goes wrong all you have to do is odin back to stock it removes everything its as simple as plugging the phone in load the stock file and click start I've done this countless times
We pick our work cell phones specifically because of the potential customization we can do. I hate being stuck with some company's version of what they think will be useful to me in my job. I can Odin this phone back to stock/factory defaults in less than 5 minutes if need be, so customizing this phone and expanding its abilities, and recovering from those customizations quickly, were what attracted me to it.
Android is Android, whether it's Samsung's stock version or one of the dev's version of it. Your phone is still going to perform the same tasks you need it to for your job. As long as you are both competent with the technologies involved and confident in your ability to restore to stock, I don't see why you should hesitate from exploring the options that are out there, especially when Froyo source drops and we see an explosion of dev-created customizations/enhancements.
Really? If your asking for advice on whether to mess with a business owned phone, it makes me wonder are you the ceo's mail clerk?
SuperClean2.9.1vNitroDark
Personally for a work phone, I'd update it for better usage in my work.
Increasing battery life usage duration.
Less irritating buggy glitches.
Removing the idiotic TW/BING/VZW craps. (too many add-on hacks from google default causing reliability and dependability problems)
Adding Backup and Restore nandroid for possible failures and migrations.
I suggest DJ05 + SuperClean + Blaze v2.3.1R2.
I've not seen a specfic thread dedicated to ROMS that people are using that appear to be flawless. I did do a search on here, but honestly, I'm new to Android and don't know exactly what to search for other than maybe CM7.1, UnNamed, and ROMs. of which you get way too many threads to sort through. figured I'd start this and people can add things. I'll keep it updated on this first post with updates as people post them. This may help others who are new find what they need to. If you know of a safe rom, post up. If you also know of a walkthrough of how to install it, post that up as well since other newbs may want help walking through their first flash. Thanks!
considering tomween1 already spent the time to create a thread with all the info you need (here) i think this thread is redundant. just my opinion, though.
nothing is "safe" if you dont know what you're doing or dont do homework, first. On the flip side, most roms are relatively safe if you know what to do. All the info you need to flash, root, whatever ... is usually stickied to the top of the section.
If it isn't from netchip, and you take care to READ all directions and instructions and warnings before flashing - everything here is safe.
(Only thing "unsafe" really is bootloaders - which is why I make sure any bootloader thread has plenty of warnings.)
I think he meant "safe" is the ROM has no error which all the cook ROMs have. Even the Stock ROm sometimes has a bug.
re: Errors
sweetboy02125 said:
I think he meant "safe" is the ROM has no error which all the cook ROMs have. Even the Stock ROm sometimes has a bug.
Click to expand...
Click to collapse
NOTICE:
If anyone wants a custom rom without any bugs or errors please look elsewhere!
(xda is not the right place for you.)
if anyone is looking for:
1) something safe to flash
and
2) doesnt want to read and gain the proper knowledge prior to touching their phone
then they should leave their phone as it is right out of the box. There are a lot of people on this forum that are more than willing to help someone out but dont expect them to do all the work. You need to meet them half way and have some prior knowledge of what you are doing.
I respect this post and would love to see it turn into a rom known bugs thread. For ex unnamed is a battery hog. P8 has Bluetooth issues and cm7 has sub par cam.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
zgr8jakez said:
I respect this post and would love to see it turn into a rom known bugs thread. For ex unnamed is a battery hog. P8 has Bluetooth issues and cm7 has sub par cam.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
The problem is, if everyone posted bugs in this thread, you'd have to sift through pages and pages of posts to see if you have a similar problem. Even then, the problem may not be the rom but a bad flash or incompatibility with a app. This would be so cluttered, you wouldn't be able to get anything out of it. What if there was a bug and the dev fixed it in a update? A newb would read the thread and think there's a issue that hasn't been resolved. Bugs are best left to their dev thread where they can be announced and addressed. If you want to see what rom A has to offer, take the time to READ.
zgr8jakez said:
I respect this post and would love to see it turn into a rom known bugs thread. For ex unnamed is a battery hog. P8 has Bluetooth issues and cm7 has sub par cam.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
Hmmm.... these "bugs" look more like opinions or might possibly be user error. For me UnNamed is a battery genius and I probably got over 2 days of use on one charge. I'm using Bluetooth just fine on Serendipity right now. And cam on cm7 works better for some then it might work for you bro.
im on uname rom myself but look to make the change to {ROM} MIUI 1.10.21 {Updated on 10-25-11} cuz i love miui so, unmae is a very good fast rom i just miss miui.
task650 said:
Hmmm.... these "bugs" look more like opinions or might possibly be user error. For me UnNamed is a battery genius and I probably got over 2 days of use on one charge. I'm using Bluetooth just fine on Serendipity right now. And cam on cm7 works better for some then it might work for you bro.
Click to expand...
Click to collapse
My thoughts exactly. (Except I never tried CM7)
Sent from my Galaxy S II (i777)
Yup. I've never had battery problems with gtg's ROM. Yes, S8 is slightly better on battery due to being more aggressively debloated, but it's not THAT much better.
Usually, anyone who encounters severe drain has encountered an app bug.
Slight exception: Any ROM that doesn't include my 10/20 kernel is susceptible to the fuel_alerted wakelock bug. Easy enough to flash my kernel over any ROM that hasn't been updated with the 10/20 kernel.
At this point, any user who claims a ROM is a battery drainer is usually at fault themselves. Especially if they haven't posted debugging info collected as documented in my Known Battery Drainers thread.
Most of the issues people have with roms are user errors.
Sent from my SAMSUNG-SGH-I777 using XDA App
One thing I forgot: The UCKJ2 leak that is distributed as a .exe file is an "Odin One-Click" flash package which will flash crippled bootloaders. I would suggest avoiding it.
re: One-Click
Entropy512 said:
One thing I forgot: The UCKJ2 leak that is distributed as a .exe file is an "Odin One-Click" flash package which will flash crippled bootloaders. I would suggest avoiding it.
Click to expand...
Click to collapse
What I am looking for is a complete stock 4 part odin flash rom like
this below but one which is for the SGS2 i777 phone and not the i9100.
OR an Odin One-Click flash for i777.
PIT select u1_02_20110310_emmc_EXT4.pit
PDA select CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.md5
PHONE select MODEM_I9100XXKI3_REV_02_CL1062028.tar.md5
CSC select GT-I9100-CSC-MULTI-OXAKI3.tar.md5
So far I could not find a 100% stock package for the i777 here in XDA.
Designgears had a very good odin one-click for the old captivate I used to have.
Either one would be good, one-click or just the complete 4 part odin flash.
Glad I could get the convo going! I'm very conservative when it comes to testing rom's and am a battery nazi as far as processes go. Cm7 is fine with still shots but unless they fixed it lately the fps on it was not perfect. I know I'm alone on the Bluetooth issue with s8 but had just gone from a fresh wipe to clean install
.. there have been allot of mms issues with that rom though..
UnNamed has more bloat so of course it will use more power after I froze the bloat it was where s8 was. The devs are amazing not knocking any at all just putting my 2 cents in. Btw the way I found the easiest way to play around with rom's was to back up in both cwm and titanium, flash one for a week and repeat indefinitely that way you can get the best of all worlds.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
CSC and cache get integrated into the system image on first boot - so you will never see a return-to-stock that includes csc and cache for UCKH7, since the return-to-stock was generated from a dumped phone, and since it's the initial stock firmware, H7 doesn't exist as Odin upgrade leaks anywhere.
Same exact deal as gtg's Ultimate Unbricks for the Infuse - the D5 unbrick (and I think the E3 unbrick too, will check tonight) were created from system dumps, so do not include a separate CSC or Cache file, as those get integrated into the system image on first boot.
RE: [RoM]UCLD3 Official ATT "Leak" !CLOSED!
I just wanted to say TY to the developers of this ROM, especially task. I got burned, but I knew what I was getting into. I'm within 30 days, plus have 1 yr warranty, plus insurance. I got my new phone and I'm happy.
Thanks again guys for trying to bring us something new and exciting.
Just a question: were all of the AT&T leaks affected by this, or just UCLD3?
The general consensus is that LD3 was the culprit, however it is possible that all leaks are affected.
The culprit was the CWM injected kernel in the version task posted. All other leaks and the one-click version of LD3 were unaffected.
nbell13 said:
The culprit was the CWM injected kernel in the version task posted. All other leaks and the one-click version of LD3 was unaffected.
Click to expand...
Click to collapse
And you know this how? Without facts, this statement is useless bro. One thing I do know is the bricking only happened to a few people. Far less then people who didn't have issues. Just like entropy said, without reproducing it would be hard to figure out. But either way. Leaks are just that. Leaks. They are pretty much worthless considering everything else we already have. So really, to figure out exactly the cause we would have to go through the process of brick, then replace/fix the device and so on.
task650 said:
And you know this how? Without facts, this statement is useless bro. One thing I do know is the bricking only happened to a few people. Far less then people who didn't have issues. Just like entropy said, without reproducing it would be hard to figure out. But either way. Leaks are just that. Leaks. They are pretty much worthless considering everything else we already have. So really, to figure out exactly the cause we would have to go through the process of brick, then replace/fix the device and so on.
Click to expand...
Click to collapse
I thought that's what you had said yourself in your thread (haven't read it in a while)
Task
I have flashed this rom many times and no issues with my phone. Although I have been lurking in these threads as a NOOB, it is apparent to me that you have to:
follow instructions in OP before flashing
Read all the of the thread before flashing
Make sure that you have the entire zip file downloaded before flashing...
Not sure what is the problem, but it is not anything with zip I down loaded.. I did both.The other files such as Shomans or AOKP as they are better than any stock rom...
Thank you for all that you do...
nbell13 said:
I thought that's what you had said yourself in your thread (haven't read it in a while)
Click to expand...
Click to collapse
i think i may have said something about it, but just wasn't sure what was happening. there were too many "it could be this" and "it could be that" stuff being mentioned. but i did however make an attempt for 2 days trying to replicate the brick. i have no qualms about buying a new phone so i wasn't worried at all about bricking. i tried every way that anyone mentioned plus more but i still couldn't get it to brick. so i'm still iffy about the whole thing. i just said screw and took down the thread. considering A TON of people don't like to read OP's and follow directions i thought it would be the best thing to do.
task650 said:
i think i may have said something about it, but just wasn't sure what was happening. there were too many "it could be this" and "it could be that" stuff being mentioned. but i did however make an attempt for 2 days trying to replicate the brick. i have no qualms about buying a new phone so i wasn't worried at all about bricking. i tried every way that anyone mentioned plus more but i still couldn't get it to brick. so i'm still iffy about the whole thing. i just said screw and took down the thread. considering A TON of people don't like to read OP's and follow directions i thought it would be the best thing to do.
Click to expand...
Click to collapse
Thanks for the hard work on it anyway Task. I read the OP. I read every post in the thread and then I read the OP again. I have flashed and reflashed it several times. Flashed several kernels and still running great.
The original OEM battery and earpiece failed within a day of each other so I am back to using my Atrix until I can get a warranty replacement on the i777.
Thanks again Task...it was fun while it lasted.
task650 said:
i think i may have said something about it, but just wasn't sure what was happening. there were too many "it could be this" and "it could be that" stuff being mentioned. but i did however make an attempt for 2 days trying to replicate the brick. i have no qualms about buying a new phone so i wasn't worried at all about bricking. i tried every way that anyone mentioned plus more but i still couldn't get it to brick. so i'm still iffy about the whole thing. i just said screw and took down the thread. considering A TON of people don't like to read OP's and follow directions i thought it would be the best thing to do.
Click to expand...
Click to collapse
Lol, I just bought the GNex from Google Play myself... Gonna need to switch back to T-Mobile in the fall when I move back to my hometown... AT&T has **** for signal there That, and I'm finally sick of touchwiz.
nbell13 said:
I'm finally sick of touchwiz.
Click to expand...
Click to collapse
Yeah that's why I use AOKP I can't stand touchwiz ics
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Lol. I installed nova to take care of that. Do want some of the other stuff so have to leave tw in some way but at least I don't have to look at it.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
nbell13 said:
The culprit was the CWM injected kernel in the version task posted. All other leaks and the one-click version of LD3 were unaffected.
Click to expand...
Click to collapse
No - even after the re-repack I believe a few more bricks happened.
Looks like the UCLD3 leak (and maybe all leaks) have the same bug that is in all of the Epic 4G Touch leaks and all Chinese Galaxy Note ICS leaks, along with the SHW-M250S/K/L official ICS releases and source code - it's a nasty one that can cause severe hardbricks if you wipe in recovery.
When I say "severe hardbrick" - I mean that the eMMC chip actually gets damaged to the point where not even JTAG recovery services like mobiletechvideos.com are able to recover the device.
It's looking like UCLD3 has the same issues that SiyahKernel 3.1rc6 had (which was rebased on SHW-M250L sources).
This is probably like some of the xbox360 and ps3 bricking updates -- an update changes something in the way the device operates. In those update -- spinning the media faster or turning on gpu acceleration of the UI, etc.. some devices can't take the change in the baseline for which they were certified and die.
Perhaps they changed voltages, media parameters, etc -- without source, we won't know for sure.
othermark said:
This is probably like some of the xbox360 and ps3 bricking updates -- an update changes something in the way the device operates. In those update -- spinning the media faster or turning on gpu acceleration of the UI, etc.. some devices can't take the change in the baseline for which they were certified and die.
Perhaps they changed voltages, media parameters, etc -- without source, we won't know for sure.
Click to expand...
Click to collapse
Sweet.... I want one of them Xbox with ICS
Yea this is one of those oddities. On mine I did do a wipe using the ld3 leaked kernel (trying to get ld3 installed) and although it wouldn't boot it also didn't hard brick. I ended up wiping using Odin and starting over.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Entropy512 said:
No - even after the re-repack I believe a few more bricks happened.
Looks like the UCLD3 leak (and maybe all leaks) have the same bug that is in all of the Epic 4G Touch leaks and all Chinese Galaxy Note ICS leaks, along with the SHW-M250S/K/L official ICS releases and source code - it's a nasty one that can cause severe hardbricks if you wipe in recovery.
When I say "severe hardbrick" - I mean that the eMMC chip actually gets damaged to the point where not even JTAG recovery services like mobiletechvideos.com are able to recover the device.
It's looking like UCLD3 has the same issues that SiyahKernel 3.1rc6 had (which was rebased on SHW-M250L sources).
Click to expand...
Click to collapse
Thank you for your insights, while I understand very little in the way of repacks and source code, I can grasp (beginning to) smart, safe flashing practices. When you share your thoughts on these subjects, the non-dev community is so much the better for it (though there will never be a silver bullet to the spreading of BS through the grapevine).
And it looks like I'm still the only one who wants Samsung stock roms.
raduque said:
And it looks like I'm still the only one who wants Samsung stock roms.
Click to expand...
Click to collapse
There are still plenty of great TW GB ROMs around. Unfortunately, people who want a stable, safe stock ICS ROM will have to wait until Samsung gives you one. Without the developers we wouldn't have ICS on our phone AT ALL, so complaining is without merit (unless you are complaining to Samsung).
raduque said:
And it looks like I'm still the only one who wants Samsung stock roms.
Click to expand...
Click to collapse
Naw I want a Samsung stock rom built for the ATT version also
Sent from my SGH-I777 using XDA Premium App
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
Hi all,
So, I took the leap of rooting my HOX+ (international) about 2 months ago, and the ROM of choice was CM.
I loved it! Love everything about it. At the time, the "stable" channel hadn't been opened, so I was using the version in nightly - it's been moved to stable now - 10.1.
Since I was attached to the stable repo, Goo Manager notified me when 10.2 moved into nightly. After a couple of days of having it stick in my status bar, nagging for an update, I just clicked and let it do its thing.
Unfortunately, this broke my phone . I got an error something along the lines of "the process com.android.phone has stopped". When I tapped "okay" the notification would re-appear after <1 second. I've since found out via Google this is something to do with my kernel (why the auto-update didn't update the kernel too is beyond me =s ) - but at the time, I just wanted a functioning phone with minimal fuss, and thought it'd be best moving myself to stable anyway. This is what I did.
That was Tuesday of this week. Between then and now, the "signal"/reception on the phone (I use Vodafone, so coverage isn't spectacular anyway) has been awful - calls randomly dropping, and it just being unreliable and generally a pain. This is despite it being the supposedly "stable" channel, and the version being the same as the one I installed from nightly (previously). Maturing seemed to make the ROM more buggy, not less!
In the interests of having a working phone, I decided to leave CM. Atm, I'm going to try out an AOKP build - though officially unofficial, I'm hoping that minimalistic => less things to break. We'll see how it goes.
I've run various Google searches and the HOX+ finally seems to be getting (after nearly a year) a good developer community - with Lloir at the forefront of it, and Maxwen's blade kernel. Could anyone recommend a flexible, good looking, regularly updated ROM? I'm not a Sense fan (not long before rooting, Sense 5 came out, and it was "the straw that broke the camel's back" so to speak), but otherwise...I'm not really sure what I'm looking for. GPL would be good, and I'm a fan of minimalism (having as little clutter in the way of unused apps as possible). An active and engaged developer/dev community is a must - I don't want to install software that will become obsolete within a week, and have no prospect of a new release. Other than that, I'm more or less happy to try everything/anything!
Cheers,
AA.
PS - I should probably mention, although I'm in no way a dev, I am quite comfortable with tech, and don't mind spending a bit of time researching things to get stuff working. I'm a dedicated GNU/Linux user, and after a fair bit of distro-hopping I've come full circle to landing on Xubuntu. My view of my phone is basically a more awkward, more delicate version of my PC - the concept of "bricking" a computer is a joke, and I think until this possibility is 100% eliminated on phones, the developer community is always going to be slightly held back. I think the models used for developing Linux OSes could/should be applied to the ROM development process, too - as brilliant as the community is atm, it does have the "exclusive hacker culture" feel to it still.
The kernel didn't update because the device is s-on, also the call dropping bug, is you're problem no one else mentioned it. Just do research on the small amount of ROMs we got.
Sent from my Nexus 5 using Tapatalk
Lloir said:
The kernel didn't update because the device is s-on, also the call dropping bug, is you're problem no one else mentioned it. Just do research on the small amount of ROMs we got.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hi,
How come you can be so sure of the cause? The 'symptom' must be relatively common, I suppose a bit like the technological equivalent of a headache and nausea.
The device is S-ON, you're right. I've read a little but I've not found anything specific to the UK about potential risks. You've got the same phone as me, and you're in the UK too, would you recommend going S-OFF? Does it cause problems with your carrier (I read somewhere that the manufacturer wasn't so bothered, but the carrier was - as it allowed the user to change certain things to do with the way the phone received carrier signal)?
Last bit on ROMs - I've read/seen quite a lot, but the information just isn't out there (unless you personally badger the devs, perhaps). The most official most ROMs get is a thread here. Compare that to (for instance) a Linux distro - you can more or less guarantee that if a distro is linked to on Distrowatch, it'll have it's own site, you can read up about source, included packages, what distinguishing features that OS has, what DE/package manager, etc. There's virtually no equivalent for phones - the best I've seen is xda's ROM listings under the device...if you're lucky one or two of the bigger ones (e.g. CM) will have it's own site. So, in lieu of that, I'm wanting to get a feel of what other users are doing, and what they'd recommend
ArminasAnarchy said:
Hi,
How come you can be so sure of the cause? The 'symptom' must be relatively common, I suppose a bit like the technological equivalent of a headache and nausea.
The device is S-ON, you're right. I've read a little but I've not found anything specific to the UK about potential risks. You've got the same phone as me, and you're in the UK too, would you recommend going S-OFF? Does it cause problems with your carrier (I read somewhere that the manufacturer wasn't so bothered, but the carrier was - as it allowed the user to change certain things to do with the way the phone received carrier signal)?
Last bit on ROMs - I've read/seen quite a lot, but the information just isn't out there (unless you personally badger the devs, perhaps). The most official most ROMs get is a thread here. Compare that to (for instance) a Linux distro - you can more or less guarantee that if a distro is linked to on Distrowatch, it'll have it's own site, you can read up about source, included packages, what distinguishing features that OS has, what DE/package manager, etc. There's virtually no equivalent for phones - the best I've seen is xda's ROM listings under the device...if you're lucky one or two of the bigger ones (e.g. CM) will have it's own site. So, in lieu of that, I'm wanting to get a feel of what other users are doing, and what they'd recommend
Click to expand...
Click to collapse
you cannot S-OFF the X+ currently, so i'm not going into that. Also you stated you flashed from CM10.1 > 10.2, which i assume was a dirty flash (no full wipe etc)
it's like installing the Arch + xubuntu on the same hard drive, which is bound to cause issues. So a full wipe was needed, as you should know "nightlies" are well nightlies, UNSTABLE
the closest we have to distrowatch are the rom reviews and so on. there's my PureAosp, AOSP+ both based on 4.3
CM as well you know what that is.
AOKP no longer supported but stable.
as "best rom" and so on are fround upon, due to the flame and chest beating and so on. which mean's you won't get a good answer tbh, and i'am quite impartial when it comes to rom's as i won't recommend anyone's rom's nor my own.
Lloir said:
you cannot S-OFF the X+ currently, so i'm not going into that. Also you stated you flashed from CM10.1 > 10.2, which i assume was a dirty flash (no full wipe etc)
it's like installing the Arch + xubuntu on the same hard drive, which is bound to cause issues. So a full wipe was needed, as you should know "nightlies" are well nightlies, UNSTABLE
the closest we have to distrowatch are the rom reviews and so on. there's my PureAosp, AOSP+ both based on 4.3
CM as well you know what that is.
AOKP no longer supported but stable.
as "best rom" and so on are fround upon, due to the flame and chest beating and so on. which mean's you won't get a good answer tbh, and i'am quite impartial when it comes to rom's as i won't recommend anyone's rom's nor my own.
Click to expand...
Click to collapse
First thing first, cheers for this man! It's good to be able to have a "conversation" with a dev - although Linux distros have got more infrastructure in place, there is a lack of 1:1 as a result (of having so many devs, etc).
It wasn't a dirty flash at all - every time I've written a new ROM I've wiped everything (or at least, ticked all the boxes in TWRP), then after reformatted - you can see the output of the 'make ext4fs' in front of your eyes. So unless it's that there's some partition which is write-protected (I assume the kernel is - since every time I've had to flash a new kernel - regardless of the wiping in TWRP, the phone just boot-loops without the kernel being flashed)...it's been clean.
I flashed 10.1 BEFORE it was in stable - so my phone was still pointing at the nightly repo (I guess?). GooManager pestered me into updating, and when I did, I ran into issues (presumably, the auto-update isn't intelligent enough to write a new kernel, and/or its in this write-protected partition which can't be accessed from the OS?)
It'd been a while since I'd put 10.1 on, and thought it'd be worth checking to see if it was in stable yet (it was). Did full wipe - as above - and then hit that annoying bug with call dropping. So I'd gone from being working on nightly to broken on stable. Time for a new ROM, methinks...looked around, and decide to post here.
As things stand I'm using AOKP (just because it was another popular ROM I knew, not really for any other reason). It's doing my head in though - either I'm being thick, or there's no option to edit settings in ANY app. I'm missing some of the gloss CM has too, things like it coming with a File Manager installed (why the hell would you not have one?!). From what you say, flashing 10.1 might be worth trying again...I'll go through from ground 0 and hopefully it won't break this time.
I get the thing with not wanting to advertise...so instead can I ask what you yourself use on your HOX+? Do you use it as a main phone, or is it just something you use for developing?
ArminasAnarchy said:
(presumably, the auto-update isn't intelligent enough to write a new kernel, and/or its in this write-protected partition which can't be accessed from the OS?)
I get the thing with not wanting to advertise...so instead can I ask what you yourself use on your HOX+? Do you use it as a main phone, or is it just something you use for developing?
Click to expand...
Click to collapse
you are right on point 1, it's in the write protected partition, and 2nd point, i tend to use my own rom's....i'am in the mindset, if i don't use my own rom's why should other people?
Lloir said:
you are right on point 1, it's in the write protected partition, and 2nd point, i tend to use my own rom's....i'am in the mindset, if i don't use my own rom's why should other people?
Click to expand...
Click to collapse
Haha, I see the logic!
Okay: so we've narrowed it down to a kernel issue. With my AOKP flash, what I did (blade wasn't for the right Android version I think) was extracted the .img file from the ROM.zip and flashed that.
With CM 10,1 (i.e. stable channel) - in your opinion would it be better to do the same, or use the blade kernel?
ArminasAnarchy said:
Haha, I see the logic!
Okay: so we've narrowed it down to a kernel issue. With my AOKP flash, what I did (blade wasn't for the right Android version I think) was extracted the .img file from the ROM.zip and flashed that.
With CM 10,1 (i.e. stable channel) - in your opinion would it be better to do the same, or use the blade kernel?
Click to expand...
Click to collapse
ALL my rom's are extract kernel from zip, i'am not sure what max did with his AOKP.....but 100% all mine you pull from zip and flash that
you can try the CM10.2 btw M1 not long ago released....just an idea..
Lloir said:
ALL my rom's are extract kernel from zip, i'am not sure what max did with his AOKP.....but 100% all mine you pull from zip and flash that
you can try the CM10.2 btw M1 not long ago released....just an idea..
Click to expand...
Click to collapse
Re-installed 10.1 (stable) again. Same issue, even though I've only had it running for 24 hours, it's dropped the call and didn't seem able to get 3G data (it was stuck at "E" for some reason, which makes doing anything impossible) despite being in the middle of the city and not near anything obvious that should block it like a huge block of flats etc.
I installed 10.2, we'll see how it goes.