Related
If you root your nexus via the "official" way, you're screwed if you have a hardware failure, because the warranty is null and void. We need to figure out a way to root that is similar to how we rooted the MyTouch and G1.
My suspicion is that the "official" unlock isn't in the spl. I think it is more like a sim unlock.
I think we should just leave it alone and learn how to root the G1 way. That way, if we have a hardware problem, we can revert the dang phone to factory specs.
Any ideas? I think a gold card may be a could place to start.
This message was deleted by its author
Given that Swetland has said the HTC should honour the hardware warranty if the flaw isn't causable by rooting, and even suggested that you message him if you get such things refused I think that most of us are pretty happy with that, certainly many of the main devs are.
Not that I'm suggesting you shouldn't do what you want to, just pointing out that you're unlikely to get the support that the G1 root had
This message was deleted by its author
t4tav said:
Plus, I would like to see a "non" official way. That way we are still not giving up our warranty.
Click to expand...
Click to collapse
It's been stated the HTC should honor the Hardware warranty.
If you are rooting, for any reason whatsoever, you are voiding your software warranty. And that's correct - you are well off the reservation and you should only root if you are aware of the risks and know what you are doing.
There is absolutely no reason you should expect to have your software warranty honored after you root.
While I can understand the desire for a sneaky backdoor root, it's really not to our advantage for such a thing to exist. Google managed to shipped this phone roootable out of the box. That is simply wonderful for the various people producing ROMs, it makes the phone a blast for hackers, it will spurn some serious innovation (and has done so already.) All good.
If people start backdoor rooting and making warranty claims, all of that may be spoiled and we may end up with a Nexus Two that is simply completely locked down.
Not good.
This message was deleted by its author
DebauchedSloth said:
It's been stated the HTC should honor the Hardware warranty.
If you are rooting, for any reason whatsoever, you are voiding your software warranty. And that's correct - you are well off the reservation and you should only root if you are aware of the risks and know what you are doing.
There is absolutely no reason you should expect to have your software warranty honored after you root.
While I can understand the desire for a sneaky backdoor root, it's really not to our advantage for such a thing to exist. Google managed to shipped this phone roootable out of the box. That is simply wonderful for the various people producing ROMs, it makes the phone a blast for hackers, it will spurn some serious innovation (and has done so already.) All good.
If people start backdoor rooting and making warranty claims, all of that may be spoiled and we may end up with a Nexus Two that is simply completely locked down.
Not good.
Click to expand...
Click to collapse
I completely agree with you. Look at the Droid Eris, for as long as it has been out, they are just starting to get an exploit that is working. They do not even have root yet.
I personally think that the people that most want to root without an unlocked bootloader are the people that will mess their phone by not understanding what they are doing to it fully. As stated above, you should be able to get your phone fixed if you have obvious defects that are not related to software.
While I think it would be interesting to have an alternative method to rooting, at the same time, I would view it as detrimental to what is trying to be done with this phone.
Just my small $0.01 (its not a full rant, trust me)
This message was deleted by its author
at first i thought it just a software, in any platform if you do anything to the software it will be ok, and the warranty still available like iphone or WM devices.
we need do small hacking to make this work, i don't know why xda-developer doesn't have any hacker, it should be easy.
This message was deleted by its author
t4tav said:
I think I got that :/
(Removed my idea - We need a passimg.nbh)
However, I am really holding out on someone from HTC or Google saying that all hardware faults will be covered even if the bootloader is unlocked.
As soon as that happens I will root my nexus
Edit - The other reason for (personally) look for another root method is that if you unlock the bootloader now, It wipes the system, all the apps and all the settings. I to be honest, I can't really be bothered to reinstall all of them, considering that the Market doesn't seem to track what I install/un-install.
Click to expand...
Click to collapse
This.
Like one of the above posters said everybody saying theres no need because they SHOULD replace hardware defects...I called HTC (haven't rooted) and asked them if I can repair hardware defects on a unlocked bootloader. The response "There is no warrenty if you have unlocked the bootloader."
This message was deleted by its author
t4tav said:
I think I got that :/
(Removed my idea - We need a passimg.nbh)
However, I am really holding out on someone from HTC or Google saying that all hardware faults will be covered even if the bootloader is unlocked.
As soon as that happens I will root my nexus
Edit - The other reason for (personally) look for another root method is that if you unlock the bootloader now, It wipes the system, all the apps and all the settings. I to be honest, I can't really be bothered to reinstall all of them, considering that the Market doesn't seem to track what I install/un-install.
Click to expand...
Click to collapse
if you are afraid to wipe then you shouldnt root your phone. i garranty that you WILL be wiping your phone many times in the future. i must have wiped my g1 more than 30 times and the nexus one 6 or 7 times already. but dont worry, there are always free backup apps like titanium backup
The Nexus is not like the G1 or mytouch in any way to root the Nexus is Different than any Htc Phone. The Porcessor is not the mt3g or g1. so to try to root it like the mytouch or g1 may bring more problems. Note No mather how you root it the warranty is still void unless you unroot it to send it back in.
This message was deleted by its author
t4tav said:
I must of wiped my G1 atleast 20+ times. I've also flashed around 20 Custom roms too (Since JF Rom's were all the rage).
I've found that mybackup works well. So I may purchase that. My Nexus is now happily rooted and running extremely fast
I'm not scared of wiping, it's just sometimes it can get sore
Click to expand...
Click to collapse
ive used backup for root users for ages(it seems like it). i seriously recommend you try titanium backup, it backs private apps up also.
simms22 said:
ive used backup for root users for ages(it seems like it). i seriously recommend you try titanium backup, it backs private apps up also.
Click to expand...
Click to collapse
Titanium seems to work well
Anyways, Let's move this topic back on track
That's my motivation
kingskidd268 said:
The Nexus is not like the G1 or mytouch in any way to root the Nexus is Different than any Htc Phone. The Porcessor is not the mt3g or g1. so to try to root it like the mytouch or g1 may bring more problems. Note No mather how you root it the warranty is still void unless you unroot it to send it back in.
Click to expand...
Click to collapse
We should have a way to "unroot."
I can see the other side to this too. If some yahoo roots their phone, then overclocks it to 2ghz or something and fries it... that SHOULDN'T be covered by warranty.
On the other hand, if I'm running one of cyanogen's roms and the speaker goes out, it should be covered.
Personally, if I fried a ROM because I overclocked it or something like that, I would NEVER send it in for warranty work. I would only send it in if the problem was clearly the manufacturer's.
Just my 2 cents
t4tav said:
Edit - The other reason for (personally) look for another root method is that if you unlock the bootloader now, It wipes the system, all the apps and all the settings. I to be honest, I can't really be bothered to reinstall all of them, considering that the Market doesn't seem to track what I install/un-install.
Click to expand...
Click to collapse
To be very clear, this behavior (data wipe on unlock) is intentional. Otherwise if your phone is lost or stolen, it would be trivial for somebody to unlock it, boot a custom kernel, and copy your contacts, email, etc from internal flash.
The Market should restore your installed apps automatically, and Settings Backup should be able to restore the bulk of your settings.
This message was deleted by its author
I am beginning to think it isn't actually possible. I've tried everything, but I can't seem to brick my Vibrant to a point that I can't recover and Odin back to life. I read that flashing ROMs over bootloaders that aren't compatible can do it, but I was still able to force DL mode (never used a jig--haven't had a need yet) and Odin to stock even after doing that.
I say "with experience" because it is obvious that there are probably thousands of Vibrants that either hit the trash or are sitting in desk drawers somewhere..."bricked." I consider myself experienced with this phone. Been flashing on it for a year, tweaking signal settings, build.prop settings, and scheduler settings. The guys on here that have abused and really pushed their devices to discover the limitations are the ones who I want to hear from if possible. I don't particularly know if, short of dunking it in my coffee, I can be more abusive to this thing. This is one limitation I haven't yet discovered. Is it TRULY unbrickable?
It is possible. I have bricked 2 - most of the older devs have bricked at least one. This sucks for the guys that did the bricking but is good for the guys just starting out because they come into it knowing what not to do.
True bricks generally come about by way of flashing an incorrect sbl or have even happened by interrupting the flashing of a proper sbl.
Most non sbl "bricks", however, are nothing more than soft bricks that patience and perseverance will remedy.
I bricked my phone twice since I started rooting my vibrant. The first one when the usb disconnected from the laptop while it was half way odin. The second time was a hardware brick. The phone just simply has no light lolz. What happened was that I selected all the checkboxes when I odin the GB loader. However, I was able to bring her back to life after trying every possible combination while my heart was pumping 3,000 gallons of my blood in every minutes and my forehead was soaking with smelling sweat. lolz
Oh it can be done, install gb bootloaders from the old days, through light roms, flash the original axura rom, try to flash to stock. spend a week with a black screen, get warranty. Bootloaders are the kiss of death. Odin really only works if you can boot, and p.c. recognizes, through yellow com. If you dont have that your attitude will change dramatically. Youve only had soft bricks, not "The BlackScreen Of Death"
okies try harder, yada yada, yada
yea just try to update your phone using kies
Sent from my T959 using XDA App
S#*T, how could anyone forget, my bad....
jellette said:
It is possible. I have bricked 2 - most of the older devs have bricked at least one. This sucks for the guys that did the bricking but is good for the guys just starting out because they come into it knowing what not to do.
True bricks generally come about by way of flashing an incorrect sbl or have even happened by interrupting the flashing of a proper sbl.
Most non sbl "bricks", however, are nothing more than soft bricks that patience and perseverance will remedy.
Click to expand...
Click to collapse
And I definitely do appreciate the work that you guys do--I was sitting nearly in tears (ok, maybe a little buzz brought the tears) about a month after I bought my vibrant in October 2010. The kid in the T-Mobile store actually rooted it for me when I went back for some help with my bill, so I had access to files that I didn't know what to do with. I tried to apply some crap theme that, at the time, I thought destroyed my phone and turned it into a piece of $400 coffee table art. My wife would have probably beaten me if I hadn't discovered XDA and the brilliant work you guys do. After that little ordeal, I got heavy into reading the threads here and slowly but surely, got pretty fearless thanks to the research you guys had already done for me.
One other question for you: If you had those bricked phones today, would you be able to revive them after an sbl brick?
I believe even the worst brick can be fixed via JTAG Service.
from my understanding and from my noob experiences this phone is unbrickable
Don't forget about the hardware mod that let's you flash boot loaders
Sent from my SGH-T959 using XDA Premium App
It's NOT unbrickable. It's just hard to, unless if your just a total absolute idiot or a accident happens. I know my dogs pulled my usb cord while i was odining once, it caused a brick.
As the vibrant and the sgs are nearly the same, I've never bricked it at all... I just lost my IMEI that's all but that doesn't seem to make any problems at all. That's the only bad thing that happened to me : )
xriderx66 said:
It's NOT unbrickable. It's just hard to, unless if your just a total absolute idiot or a accident happens. I know my dogs pulled my usb cord while i was odining once, it caused a brick.
Click to expand...
Click to collapse
It is unbrickable you can fix it even if bootloader get deleted the only way you can brick it is if USB port is broken
Sent from my GT-I9000 using XDA App
Hi,
I've soft bricked my phone several times and restored it with no problems till last night. I had GB bootloader on my vibrant flashed back stock rom using odin and then upgraded to stock 2.2 rom using KIES. Now phone is not responding to anything. I've spend hours on forums and chats i've tried almost every thing and nothing could bring back my phone I even let it chard over night like some people say did not help.
Please let me know if there any way to restore it? Again it has GB bootloader with stock 2.1 and than upgraded to stock 2.2 via KIES.
Thanks in advance!
Did u get a USB jig yet that should work
Sent from my SGH-T959 using XDA App
manus ferrera said:
Did u get a USB jig yet that should work
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
No not yet...I still want to find a way to restore it without JIG. It should be a way!
I think problem is that most of solutions where posted for Vibrant stock Bootloader not a GB Bootloader. May be there are different steps are required for GB Bootloaders. I don't want to give up
With GB BL you have to use vol+ and power to get into download mode. Just an fyi in case you didnt know.
What he said!
bfranklin1986 said:
yea just try to update your phone using kies
Sent from my T959 using XDA App
Click to expand...
Click to collapse
Thats exactly how I bricked mine, and found out a day after by stumbling across a thread on the dangers of using KIES, when I was newbee dumb!
Also, if you can power the phone on in any way shape or form, meaning if you see anything on the screen, or the LED's illuminate, then you are NOT HARDBRICKED, that is still a softbrick senario!!
And BTW the primary Btloader is what powers the phone one, and the 2ndary Btloader is what loads the OS or ROM!
And when the primary is corrupted, that's a TRUE HARDBRICK scenario, because if you cant power the phone on, then nothing short of JTAGing it , will resurrect it!!
Although Adam Outler, supposedly has a Resurrection program, to JTAG the solder-less way, using pin point test probes and his Resurrection program, to inject and re-flash the Btloaders and thus, bring a dead non powered phone to life!
Link to Adam's Work: http://forum.xda-developers.com/showthread.php?t=1397393
---------- Post added at 11:09 AM ---------- Previous post was at 10:58 AM ----------
anatoliyus said:
No not yet...I still want to find a way to restore it without JIG. It should be a way!
I think problem is that most of solutions where posted for Vibrant stock Bootloader not a GB Bootloader. May be there are different steps are required for GB Bootloaders. I don't want to give up
Click to expand...
Click to collapse
A JIG will not work, if the primary Bootloader is corrupted it wont power on , JIG's only work with phones that will power on, and in his case he corrupted the primary, and only JTAGing it will resurrect it, unless he has the intelligence to try this alternative below, otherwise send it to Adam or TechMobile, the only two guys I know who are true Ninja's with this type of micro surgery!
http://forum.xda-developers.com/showthread.php?t=1397393
It sucks...Just 2 weeks ago I've installed FFC, ordered 1800 Battery...invested money.
Don't want to spend any more money on this old cell phone I may just go and buy new phone then.
---------- Post added at 05:19 AM ---------- Previous post was at 04:48 AM ----------
dseldown said:
Thats exactly how I bricked mine, and found out a day after by stumbling across a thread on the dangers of using KIES, when I was newbee dumb!
Also, if you can power the phone on in any way shape or form, meaning if you see anything on the screen, or the LED's illuminate, then you are NOT HARDBRICKED, that is still a softbrick senario!!
And BTW the primary Btloader is what powers the phone one, and the 2ndary Btloader is what loads the OS or ROM!
And when the primary is corrupted, that's a TRUE HARDBRICK scenario, because if you cant power the phone on, then nothing short of JTAGing it , will resurrect it!!
Although Adam Outler, supposedly has a Resurrection program, to JTAG the solder-less way, using pin point test probes and his Resurrection program, to inject and re-flash the Btloaders and thus, bring a dead non powered phone to life!
Link to Adam's Work: http://forum.xda-developers.com/showthread.php?t=1397393
---------- Post added at 11:09 AM ---------- Previous post was at 10:58 AM ----------
A JIG will not work, if the primary Bootloader is corrupted it wont power on , JIG's only work with phones that will power on, and in his case he corrupted the primary, and only JTAGing it will resurrect it, unless he has the intelligence to try this alternative below, otherwise send it to Adam or TechMobile, the only two guys I know who are true Ninja's with this type of micro surgery!
http://forum.xda-developers.com/showthread.php?t=1397393
Click to expand...
Click to collapse
Thanks...will try this solution. Downloading Ubuntu...
heysoos said:
I am beginning to think it isn't actually possible. I've tried everything, but I can't seem to brick my Vibrant to a point that I can't recover and Odin back to life. I read that flashing ROMs over bootloaders that aren't compatible can do it, but I was still able to force DL mode (never used a jig--haven't had a need yet) and Odin to stock even after doing that.
I say "with experience" because it is obvious that there are probably thousands of Vibrants that either hit the trash or are sitting in desk drawers somewhere..."bricked." I consider myself experienced with this phone. Been flashing on it for a year, tweaking signal settings, build.prop settings, and scheduler settings. The guys on here that have abused and really pushed their devices to discover the limitations are the ones who I want to hear from if possible. I don't particularly know if, short of dunking it in my coffee, I can be more abusive to this thing. This is one limitation I haven't yet discovered. Is it TRULY unbrickable?
Click to expand...
Click to collapse
There are several of us that have including myself, heathen and Eugene just to name a few. We've actually taken the bullet previously so you don't have to. We pretty much know now what will cause a hard brick and that's why you rarely here of one now.
Sent from my SGH-T959 using xda premium
I thought that i was going to stay with my GS4 for awhile, since I decided that i didn't want to spend money every time a new phone came out. But out of curiousity, i chatted with Sprint to see how much credit they were giving for a GS4. They stated that they were only giving $135.00 credit trade in value on the GS4, but i was browsing Best Buy Mobile, and they gave me $310.00 for my GS4! So, out of pocket expense with upgrade was $40.00 + tax (roughly $25.00), came out to be $65.00 out of pocket expense...i couldn't say no and took the deal since i didn't want my trade in value to decrease later on.
But here I am, new phone (which i love - but if you have a Note 2, i am not sure the upgrade to the Note 3 is worth it) and i want to root & flash badly. Knox, however, is making me think twice about doing so. How many of you are rooting it anyways? I saw a root method that won't trigger the Knox flash counter, but flashing a rom would, which is the main reason i would want to root anyways.
I was running Beanstalk 4.3 on my GS4, and it was faster than my Note 3 (completely stock at the moment), and the battery life was pretty good, i could go a full day, with about 4 hours on screen time. I can only imagine the results would be better if i do the same for my Note 3.
So how many of you have taken the plunge and rooted + rom'd? Aside from void of the warranty, are their any other drawbacks from tampering with Knox?
I want to badly, but just wanted to see if it has adversely affected anyone who already has.
Thanks,
JD
Honestly I am not rooted (although every day it gets harder and harder not to) but not because of warentee but rather because of all the problems people are having. . From force closing to root disappearing for no reason. I don't feel we know enough about the ramifications to the inner workings of what Knox is doing.
http://swappa.com/listing/ZZV485/view
note 2 for sale
jdizzle316 said:
I thought that i was going to stay with my GS4 for awhile, since I decided that i didn't want to spend money every time a new phone came out. But out of curiousity, i chatted with Sprint to see how much credit they were giving for a GS4. They stated that they were only giving $135.00 credit trade in value on the GS4, but i was browsing Best Buy Mobile, and they gave me $310.00 for my GS4! So, out of pocket expense with upgrade was $40.00 + tax (roughly $25.00), came out to be $65.00 out of pocket expense...i couldn't say no and took the deal since i didn't want my trade in value to decrease later on.
But here I am, new phone (which i love - but if you have a Note 2, i am not sure the upgrade to the Note 3 is worth it) and i want to root & flash badly. Knox, however, is making me think twice about doing so. How many of you are rooting it anyways? I saw a root method that won't trigger the Knox flash counter, but flashing a rom would, which is the main reason i would want to root anyways.
I was running Beanstalk 4.3 on my GS4, and it was faster than my Note 3 (completely stock at the moment), and the battery life was pretty good, i could go a full day, with about 4 hours on screen time. I can only imagine the results would be better if i do the same for my Note 3.
So how many of you have taken the plunge and rooted + rom'd? Aside from void of the warranty, are their any other drawbacks from tampering with Knox?
I want to badly, but just wanted to see if it has adversely affected anyone who already has.
Thanks,
JD
Click to expand...
Click to collapse
There is a method now to root without tripping KNOX, it involves flashing back to Stock MI3 firmware and something something KNOX binary counter gets reset to 0x0. Custom ROM will still trip the counter. Essentially you could run Stock with root access on MI3 and even flash the hotspot fix mod.
Don't root or modify your device if you even think twice about the warranty, you're taking a risk by flashing via ODIN and Recovery and you will be responsible for any potential damage to your phone, if you're within your 14 return period chances are they'll take it back no questions asked.
Root access, custom ROMs, themes, mods/fixes/improvements, battery and performance optimizations, debloated apps, free tethering... There are just so many reasons to root and not a lot of reasons not to.
I've removed all the KNOX files from my system, device still runs fine. The Knox counter was tripped as shows 0x1 but I don't care, what does that even do? KNOX is just a security system implemented for whatever reason, a minor annoyance that will soon have complete workarounds.
Just a warning though, some people do experience issues, from "force closing apps" to "soft-bricking" ... Just follow the directions listed on the OP of the developer thread exactly as they're listed and you should be okay.
Thanks for the info!!!
I've always rooted all my other phones, and i guess you're right!
Knox, being new is just a little intimidating. May I ask if you rooted via the method without tripping the counter? Also, did you flash a rom or did you debloat yourself?
Thanks for your time and advice
Kompster said:
There is a method now to root without tripping KNOX, it involves flashing back to Stock MI3 firmware and something something KNOX binary counter gets reset to 0x0. Custom ROM will still trip the counter. Essentially you could run Stock with root access on MI3 and even flash the hotspot fix mod.
Don't root or modify your device if you even think twice about the warranty, you're taking a risk by flashing via ODIN and Recovery and you will be responsible for any potential damage to your phone, if you're within your 14 return period chances are they'll take it back no questions asked.
Root access, custom ROMs, themes, mods/fixes/improvements, battery and performance optimizations, debloated apps, free tethering... There are just so many reasons to root and not a lot of reasons not to.
I've removed all the KNOX files from my system, device still runs fine. The Knox counter was tripped as shows 0x1 but I don't care, what does that even do? KNOX is just a security system implemented for whatever reason, a minor annoyance that will soon have complete workarounds.
Just a warning though, some people do experience issues, from "force closing apps" to "soft-bricking" ... Just follow the directions listed on the OP of the developer thread exactly as they're listed and you should be okay.
Click to expand...
Click to collapse
jdizzle316 said:
Thanks for the info!!!
I've always rooted all my other phones, and i guess you're right!
Knox, being new is just a little intimidating. May I ask if you rooted via the method without tripping the counter? Also, did you flash a rom or did you debloat yourself?
Thanks for your time and advice
Click to expand...
Click to collapse
I rooted and installed JellyBomb right away because performance>warranty to me. I have been having some of The connectivity issues others have mentioned, they are the same worth our without root. All in all, I, m glad I rooted.
Good info on the knox free root here.
http://forum.xda-developers.com/showthread.php?t=2484095
From my Note 3
We now have MI5!!!
jdizzle316 said:
Thanks for the info!!!
I've always rooted all my other phones, and i guess you're right!
Knox, being new is just a little intimidating. May I ask if you rooted via the method without tripping the counter? Also, did you flash a rom or did you debloat yourself?
Thanks for your time and advice
Click to expand...
Click to collapse
You're welcome.
I rooted with the CF-AutoRoot method that tripped the KNOX binary counter.
Initially I flashed freeza's Deodexed Stock ROM and debloated it myself.
I posted a thread in the "General" category called "Potentially" Safe to Freeze/Remove Apps (SM-N900P)
I was not quite satisfied with stock and wanted a bit more, backed up everything and flashed JellyBomb ROM. No regrets. This ROM is awesome and just keeps getting better.
Sent from my Rooted, TWRP'd & JellyBombed SM-N900P using XDA...
I waited all of a day to root and have had no issues other than a bluetooth problem which turned out to be a problem with my Alpine. Haven't looked back and am looking forward to some new ROMs.(at the very least a Sprint 1X 3G mod) I have a warranty through squaretrade so the factory one doesn't bother me.
did you go the route of not tripping the Knox counter, or the other method (CF)?
Thanks, I'm just trying to gather as much info as i can before i take the dive myself....not having root/custom rom is killin me!
appreciate the input, thank you
piaa_nissan said:
I waited all of a day to root and have had no issues other than a bluetooth problem which turned out to be a problem with my Alpine. Haven't looked back and am looking forward to some new ROMs.(at the very least a Sprint 1X 3G mod) I have a warranty through squaretrade so the factory one doesn't bother me.
Click to expand...
Click to collapse
The only thing available when I did mine was CF. My counter is tripped. My theory is the Knox counter is more of a thing for a corporate IT department to verify security. I've only seen one foreign post where the person was supposedly told it would void the phone warranty. My Motorola X explicitly stated it will void the warranty when I unlocked the boot loader and I would think Samsung would do the same when put intov download mode. That's just my opinion though
Sent from my SM-N900P using Tapatalk
piaa_nissan said:
The only thing available when I did mine was CF. My counter is tripped. My theory is the Knox counter is more of a thing for a corporate IT department to verify security. I've only seen one foreign post where the person was supposedly told it would void the phone warranty. My Motorola X explicitly stated it will void the warranty when I unlocked the boot loader and I would think Samsung would do the same when put intov download mode. That's just my opinion though
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Have you had any issues. . I am not concerned about the warrantee but I am worried about all the issues people have had. . Losing root, selinux issues etc. . What has your experience been?
http://swappa.com/listing/ZZV485/view
note 2 for sale
As I said in my original post, no issues. YMMV
I'm rooted, running stock, loving the phone. My only issue was that I couldn't get 5 rows of icons on my home screens to maximize real estate... so I ventured for the first time into launchers, and I'm very happy with Nova right now.
caffeiNater said:
I'm rooted, running stock, loving the phone. My only issue was that I couldn't get 5 rows of icons on my home screens to maximize real estate... so I ventured for the first time into launchers, and I'm very happy with Nova right now.
Click to expand...
Click to collapse
Nova and Apex are considered the best.
Is there anyway to flash a 4.4 Rom on the Verizon gs4 with 4.3 on it?
If you have mdk firmware...
Sent from my SCH-I545 using XDA Premium 4 mobile app
I have a screenshot in the attachments:
Nickco43 said:
Is there anyway to flash a 4.4 Rom on the Verizon gs4 with 4.3 on it?
Click to expand...
Click to collapse
Keep an eye on this thread
http://forum.xda-developers.com/showthread.php?t=2720163
They're working on getting it for non MDK phones. Guess a lot of people have been quite busy lately on here.. I wouldn't attempt what there doing in that thread just yet unless your ready to use Odin.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
How hard is odin?
Nickco43 said:
How hard is odin?
Click to expand...
Click to collapse
Well Odin isn't rally that hard but since you're fairly new to this I'm going to suggest you read up a lot more before attempting anything along those lines.
You could end up with a $600 paper weight if things go badly and trust me they do. The guy who made that post I sent you is waiting for his new S4 as we speak because he hard bricked it trying to do things like that. Odin can save you from a " soft brick" not a hard one.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
---------- Post added at 10:15 PM ---------- Previous post was at 10:14 PM ----------
http://forum.xda-developers.com/showthread.php?t=2606501
Check this out
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
Also here are some great videos on things for our phones
http://forum.xda-developers.com/showthread.php?t=2337590
I think Odin is one of them along with many others
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Mistertac said:
Well Odin isn't rally that hard but since you're fairly new to this I'm going to suggest you read up a lot more before attempting anything along those lines.
You could end up with a $600 paper weight if things go badly and trust me they do. The guy who made that post I sent you is waiting for his new S4 as we speak because he hard bricked it trying to do things like that. Odin can save you from a " soft brick" not a hard one.
hes right (Mistertac is right, I mean kinda) but it was bricked because i forgot to add a file crucial to having the download mode capability to the script before flashing it; but i was toying with bringing over the at&t 4.42 not the vzw leak which i actually did at first via mk2 stock at&T rom and odin but then reverted back to mk2 then tried to go back but by innovating a new way to flash via safestrap and not forcing the users to use odin but i was super baked and a little drunk and up a lot longer than i should have been so I'd blame that. actually most of the methods we're using will not hard brick unless your one that doesnt follow directions well or use common sense. but just wait a day i'll have the process cemented and new ROM's-a-plenty
funny thing is that I called vzw enough times trying to get them to force an at&t s3 onto my line (so i didnt have to replace the imei num with my old phones but they "couldnt" even though I said its unlocked on your APNs and I'll run an any frequencies they needed and said I could just clone my old lg revo to the s3 to trick their system into activation on 4g if their "techs" couldnt handle a simple activation... its funny when honesty is rewarded because after i bull****ted with the guy for long enough on various subjects like how stupid and invasive knox is and how he thought in the end they'd lose a percentage of their customer base by forcing updates containing it and requiring future phones to have it and then I told him I was so pissed that verizon was absolute last on the 4.42 bandwagon and that I was trying to get those of us on the already knoxed pos bl that was shipped with my 1st replacement phone updated to 4.42 as most really didnt care to have the super locked up nsa ready 4.42 verizon bull**** update and then told the tech I enjoyed cooking and porting roms to the system he responded with whats your nick was on xda?... 20 minutes later I'm midway through a free extended warranty on the s4 with free overnight shipping ?! so I guess some techs are ok most of them know much much less than the common user on xda but hey every now and again... he also told me we could expect the OTA to start showing up May 6th-8th and that our leaked version is probably the same version as the official so we'll see how accurate this guy is but i couldnt believe after telling him how i bricked and why he was so nice. he also explained that when i send the old phone back to the warranty department if there not able to prove without a doubt that software manipulation is the cause of the brick they can't charge for it and that if download mode fails to come up the phones usually sent off to be "refurbished" by samsung or a company in relation too which probably has the ability to write from emmc any bl or version of the i9505 because they've got the keys to the city.... and if i'm questioned about how I got the phone in that state at all to say I avoided taking an ota because I was against the use of knox and locked bootloaders and when i accidently started upgrading i got scared and popped the battery. 1000s of s4s have softbricked or hardbricked because of these locked bootloaders and so its an excellent excuse for anyone needing to warranty or use insurance to get a new phone. oh he laughed at me when i asked if it was "possible he could send me an MDK model phone cause originally thats what I had and I'd like another"... but I still wouldnt recommend flashing other carriers bootloaders which is what I did to brick it initally. flashing verizon's shouldnt hurt anything and should be repairable at software level with odin easily enough however if your waiting to have your bl unlocked upgrading it further might stunt this possibility. all in all if your new to all of this then yeah wait for someone to hold your hand.
but there technically shouldn't be a "hard" bricked phone anyway as theres definately a way to flash the bl over emmc or use an sdcard debrick img to get odin capabilities back I failed tho in achieving this type of restore but theres been some success. eventually this ability will come to light here in the vzw threads and then we'll b unbrickable finally maybe even unlocked if someones able to piece together an mdk flash over formated mk2 emmc forced usb qbdload mode but I've had my fun with it glad to b done (wouldnt be so bad if i wasnt poor and had multiple s4s to test and f with) and hopefully on 4g in a few hours I think I'll stick to playing with ROMs after this 4.42 SS update is finalized tho it is much more my forte
thats my weekly rant maybe my difficulties will help someone else or maybe im just proving how mmj and beer and scripting at 5am isnt wise lol
Click to expand...
Click to collapse
@gigilie
Good update man thanks. Course I didn't really know exactly how you bricked that phone. I just wanted to illustrate how careful people need to be if their just getting into this kind of thing.
Anyways I'm always following what you're up to on here and wish ya the best of luck!
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
My Tmobile Samsung S5 had tripped Knox after rooted. I read that Triangle Away can set back the Knox counter. Before purchasing this app, I want to ask have anyone able to use Triangle Away on the S5? Thank!
caodangra said:
My Tmobile Samsung S5 had tripped Knox after rooted. I read that Triangle Away can set back the Knox counter. Before purchasing this app, I want to ask have anyone able to use Triangle Away on the S5? Thank!
Click to expand...
Click to collapse
It will not work. If you try it, it may brick your phone.
MattMJB0188 said:
It will not work. If you try it, it may brick your phone.
Click to expand...
Click to collapse
thank for the information.:good:
caodangra said:
thank for the information.:good:
Click to expand...
Click to collapse
No problem.
There is a new ROM that takes care of this problem. But you have to install that ROM. Just go under development there are only a few there.
Sent from my SM-G900T using xda app-developers app
dpshptl said:
There is a new ROM that takes care of this problem. But you have to install that ROM. Just go under development there are only a few there.
Sent from my SM-G900T using xda app-developers app
Click to expand...
Click to collapse
I think you are misinformed. KNOX cannot currently be subverted.
BLuFeNiX said:
I think you are misinformed. KNOX cannot currently be subverted.
Click to expand...
Click to collapse
That is correct - some have said (those that know more than I) that tripping knox blows a Q FUSE which as I understand it is a phyisical attribute on the phone not a software attribute - - to UNDO that would be impossible without a soldering iron of somekind -)(joking) but there are tons of QFUSES avaialble from what I have read - and it seems that Samsung and maybe even the carrier tech staff have a way of "Reassigning" the QFUSE or someting - as many phones taken back for repairs are returned with Knox reset to 0.
I may be completely wrong in the way I am describing this - as I am not developer and have only read a bunch about it - much of which was way over my head - but that is my interpreation of how it works (on a very simple level)
For the record, I ran Triangle Away on my TMO S5 without any issue. I'm not sure if it worked as I have not checked.. but it did not brick my phone.
Also, this is the first I've heard of this KNOX chip and hardware tampering system. It is very possible to construct a loop that is designed to blow a fuse; thus triggering a desired software effect. HOWEVER, its still software which means that (in theory) its still possible to work around. If all of this is true, it will only be a matter of time before we have a work around.
luckyduck69 said:
For the record, I ran Triangle Away on my TMO S5 without any issue. I'm not sure if it worked as I have not checked.. but it did not brick my phone.
Also, this is the first I've heard of this KNOX chip and hardware tampering system. It is very possible to construct a loop that is designed to blow a fuse; thus triggering a desired software effect. HOWEVER, its still software which means that (in theory) its still possible to work around. If all of this is true, it will only be a matter of time before we have a work around.
Click to expand...
Click to collapse
wondering any update did it work or not ....i need to send my phone in and wanted to know
There is currently no way to reset the Knox Warranty flag on a G900T (and most other models) once it has been set to 0x1. Triangle away does not work. Tons of threads on XDA about this, and much more discussion can be found with a simple Google search.
hondasforlife said:
wondering any update did it work or not ....i need to send my phone in and wanted to know
Click to expand...
Click to collapse
Don't send it in. Go to a retail store. Less chance of them checking.
hondasforlife said:
wondering any update did it work or not ....i need to send my phone in and wanted to know
Click to expand...
Click to collapse
Triangle away will not reset your Knox flag.
The flag can be reset in theory and has actually has been reset under controlled conditions in Development threads. But don't expect an end user solution to materialize anytime soon. For all practical purposes, a Knox flag is irreversible.
Sending a 0x1 phone to Samsung for warranty service will inevitably get it returned as unrepairable i.e. a refused warranty claim. If you live in the EU you can argue with them as their are stronger consumer protection laws ostensibly preventing them from refusing a claim unless they can demonstrate that your root damaged the phone.
For anyone elsewhere, it's more effective to claim warranty through your carrier. Many carriers don't care about Knox.
.
caodangra said:
thank for the information.:good:
Click to expand...
Click to collapse
my friend just took a GS5 back to tmobile because he basiclly bicked it and was to impatient to drop iot off at my house to fix it. They gave him a new one no questions asked and knox was tripped ..Its like they dont even care .. If you have premium handset protection it dont even matter if you trip knox . I think they would rather get a knox tripped phone rather than one that has a cracked screen ..The sales people up there only know how to do one thngand that is a factory reset to solve any and all problems .LOL.The last thing tmobile wants to do is keep you from having a phone.
T-Mobile does not check if Knox was tripped. They don't know how to check it anyways. Just make sure that if they ask, do not give an impression that the phone is rooted.
I bricked my phone & brought back to Sprint & got a new one without a problem... Thank God!
fffft said:
Triangle away will not reset your Knox flag.
The flag can be reset in theory and has actually has been reset under controlled conditions in Development threads. But don't expect an end user solution to materialize anytime soon. For all practical purposes, a Knox flag is irreversible.
Sending a 0x1 phone to Samsung for warranty service will inevitably get it returned as unrepairable i.e. a refused warranty claim. If you live in the EU you can argue with them as their are stronger consumer protection laws ostensibly preventing them from refusing a claim unless they can demonstrate that your root damaged the phone.
For anyone elsewhere, it's more effective to claim warranty through your carrier. Many carriers don't care about Knox.
.
Click to expand...
Click to collapse
Some info in this thread is false, but this user explains it correctly. Triangle away is not about the Knox counter but about the Flash counter, which counts if your phone has been flashed. And on some devices it counts how many times you've flashed. I've attached a screenshot to clarify
The OP question, if triangle away works wasn't answered that i saw. I boldly tried it, with TriangeAway version 3.26 on an international SM-G900F with Polish Lollipop rom ...BNL9 version. The phone was Odin flashed with official Polish firmware to upgrade to 5.0 lollipop and then rooted with CF autoroot. And on this device TriangleAway worked! Flash counters were reset to official. Knox still tripped of course.
Nice Thread. I have some more questions about this topic. I have a S5 with Phoenix ROM.
I don't care about knox or warranty, but for cosmetic issues I would like to have this SEAndroid Enforcing Thingy go away. So may I ask what part of the system reports This message. And what does SEAndroid mean? If this is some kind of certificate or other property? How will the phone know if, for example, Android 5.3 comes out? Or will that use an old kernel the phone already knows?
What are the chances someone makes a custom kernel that is SEAndroid Enforcing?
PenzRules said:
Nice Thread. I have some more questions about this topic. I have a S5 with Phoenix ROM.
I don't care about knox or warranty, but for cosmetic issues I would like to have this SEAndroid Enforcing Thingy go away. So may I ask what part of the system reports This message. And what does SEAndroid mean? If this is some kind of certificate or other property? How will the phone know if, for example, Android 5.3 comes out? Or will that use an old kernel the phone already knows?
What are the chances someone makes a custom kernel that is SEAndroid Enforcing?
Click to expand...
Click to collapse
Triangle away will not remove it. Only way to remove it is to run 100% stock kernel
Could not someone edit the text to Kernel ready for CPUSPEEDENFORCING? Or Kernel Is too smart for the phone? P.S. Your answer was already given. I asked something else.
In an effort to reclaim the thread and keep it going (as for a question that I have as well), what is the hardware effect that the QFUSE breaking causes? My Knox was tripped before I received the phone, and the only noticeable flaw I have (not sure if it is Knox related because I received the phone by a trade) is that within my back camera pictures, I have three black spots that look like burns (snapshot attached). Could someone help me out?