Database Users

Who Has an Unlocked Bootloader?

Hey guys,
With All this Warranty talk, the people who unlocked your bootloader. Do you regret it? Was the warranty worth sacrificing for custom roms? I want to unlock it but at the same time I keep getting these paranoid thoughts that I'm gonna need the warranty later on. WTF. Any help?

You can install custom roms without unlock bootloader. I have evil nxsense rom installed in my N1 without unlock my bootloader.
Sent from my HTC Nexus One using XDA App

HTC honors the warranty even with the bootloader unlocked; I can't say that I've needed to make a claim myself, but that's the consensus from majority of members on this board. So, my advice is just go for it.
I had the same doubts as you, but you won't regret it

habs25 said:
HTC honors the warranty even with the bootloader unlocked; I can't say that I've needed to make a claim myself, but that's the consensus from majority of members on this board. So, my advice is just go for it.
I had the same doubts as you, but you won't regret it
Click to expand...
Click to collapse
Agree with this. Although I've never had to make a claim either.

I unlocked mine as soon as I pulled it from the box back in January 2010. I have had no regrets about it at all. I have never needed warranty service, though I wouldn't hesitate to call HTC for a hardware related issue. If something went horribly wrong with a ROM flash or a radio upgrade, that would be my own fault and I would look into buying a new phone. But I wouldn't try to BS HTC to make them pay for my screw-up.

habs25 said:
HTC honors the warranty even with the bootloader unlocked; I can't say that I've needed to make a claim myself, but that's the consensus from majority of members on this board. So, my advice is just go for it.
I had the same doubts as you, but you won't regret it
Click to expand...
Click to collapse
I have made two claims with my unlocked bootloader. Each has been hassle free and quick. Oh, and cost me nothing.
First, a few months ago for dust under the screen, repaired and sent back in 4 days.
Second, which was last week for power button issues. They received, repaired, and shipped back in one day. I got it back the next.
HTC is quietly brilliant.

thanks guys! i may actually unlock the baseband than.
is unlocking the baseband more beneficial than just doing a root without unlocking?
btw, so you guys think its better to safer to send it in and get it repaired if you have a unlocked baseband than the riskier "swap" (when they send u a new one and you send your old one in) method?

Wisefire said:
I have made two claims with my unlocked bootloader. Each has been hassle free and quick. Oh, and cost me nothing.
First, a few months ago for dust under the screen, repaired and sent back in 4 days.
Second, which was last week for power button issues. They received, repaired, and shipped back in one day. I got it back the next.
HTC is quietly brilliant.
Click to expand...
Click to collapse
hey, did they send it back to you with a locked bootloader?

First time they relocked it.
Second time, they left it unlocked.

ROOT is fine
bambamboom said:
thanks guys! i may actually unlock the baseband than.
is unlocking the baseband more beneficial than just doing a root without unlocking?
btw, so you guys think its better to safer to send it in and get it repaired if you have a unlocked baseband than the riskier "swap" (when they send u a new one and you send your old one in) method?
Click to expand...
Click to collapse
I don't see any point in unlocking boot loader while you can root the phone and do whatever you want. the only thing you can't directly do is to flash a partition usion bootloader commands but you still can do it if you use "flash_img" command in ClockworkMod Recovery (on the adb shell). I install different roms and I am on CM7 now.

I unlocked mine without wanting to. I flashed modaco rom and it just unlocked my boot loader. but there is supposed to be a way of locking it again. it's somewhere on xda...
Sent from my Nexus One using XDA App

Yeah, I like posters that don't know what they post.
1) No ROM can unlock the bootloader. User has to do it and the system has to ask for permission.
2) Once unlocked, it can't be locked, only by HTC.
To the OP: I've unlocked my bootloader long before "non-unlocking" way has been found. Never cared for it since, didn't need the warranty, and it's going to expire soon anyway.

Yes mine unlocked, and I have no reason to regret it, as my phone is a freak that can be locked again.
Worth doing in my opinion, and even if I couldn't lock it again, I still wouldn't regret it.

bohlool said:
I don't see any point in unlocking boot loader while you can root the phone and do whatever you want. the only thing you can't directly do is to flash a partition usion bootloader commands but you still can do it if you use "flash_img" command in ClockworkMod Recovery (on the adb shell).
Click to expand...
Click to collapse
Mine is locked, but there are 2 goods reasons to unlock the bootloader:
1. Once the bootloader is unlocked, you always have a rooted phone. The next ota won't relock it.
2. You have more options to fix a potentially bricked phone.
I'm thinking about doing it for these reasons, plus it seems like HTC still honour the warranty.
Sent from my Nexus One using XDA App

I unlocked my bootloader because the warranty was gone anyway. Put the nexus into the washing mashine . Somehow it survived (Bluetooth, radio and camera gone). It actually was pretty tough. after about 10minutes in the mashine (60°C) the screen was still having fun inside the mashine.

andynx1 said:
Mine is locked, but there are 2 goods reasons to unlock the bootloader:
1. Once the bootloader is unlocked, you always have a rooted phone. The next ota won't relock it.
2. You have more options to fix a potentially bricked phone.
I'm thinking about doing it for these reasons, plus it seems like HTC still honour the warranty.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
1. Well, if you wanna update ota, you don't have reason to root your phone in the first place.
2. what more options exactly you have? simple, do not mess with HBOOT and Recovery partitions, and ur safe.
My opinion, use oneclickroot and don't risk it, cause HTC support behave deferentially now!

bohlool said:
1. Well, if you wanna update ota, you don't have reason to root your phone in the first place.
2. what more options exactly you have? simple, do not mess with HBOOT and Recovery partitions, and ur safe.
My opinion, use oneclickroot and don't risk it, cause HTC support behave deferentially now!
Click to expand...
Click to collapse
Obviously you have no idea what you are talking about.
Read my previous post, HTC has the best customer support & service I have ever received.

Wisefire said:
Obviously you have no idea what you are talking about.
Read my previous post, HTC has the best customer support & service I have ever received.
Click to expand...
Click to collapse
No comment!

Samsung working on eMMC hardbrick fix...or not ?

Does anybody know what Samsung is doing about hardbrick issue ?
Latest news from Daniel Hillenbrand was on Jun 8 (He contacted Samsung and:
Patches will be out in form of new official ROMs and also sourcecode releases after testing, which might take some time
Click to expand...
Click to collapse
source: Daniel Hillenbrand Google +
Yesterday, Entropy512 said:
Even secure erase is not 100% guaranteed to cause damage. It turns out it will only cause damage when the eMMC is in a certain specific state. (I unfortunately can't elaborate on the specifics as that is proprietary information) - However it explains why some people manage to wipe even in CWM without damage.
Click to expand...
Click to collapse
I don’t want any details, but after reading all the threads, information from Ken Sumrall and posts on Samsung official support forums, I think that they don’t want to admit, that there’s a problem with their eMMC chips. I know that it is almost impossible to recreate brickbug situation on stock devices - so there is no problem for Samsung at all (custom rom - not their problem) .
I just don’t know what to think – Samsung is currently Rolling-out the Official ICS 4.0.4 Update for Galaxy S2 and we all know, that each of them contains unsecure kernel (all they need to do is disable emmc_cap_erase, right? )
I may be wrong, maybe fix is a lot more complex than just disabling emmc_cap_erase in kernel, but this is the difference between secure and unsecure kernel…so why they didn’t ? Everyone knows about eMMC bug, but Samsung is rolling out new updates and don’t care…

Its Simple They moved on .......
They dont want to spend their time and energy on this phone instead they are thinking about s4 or galaxy note 2

No, they are not. It's so simple to fix hardbrick bug... But Samsung is not interested at all, and seems that it's a computer working on the builds, not real people, since they still releasing this crap. Samsung super fail.

They just don't care and why should they?
The stock Firmwares are noobproof, but if some geeks from XDA D) flash custom Roms its already not their business because a usual customer never even get accidentally into a recovery where he could wipe the phone.
So, they say users fault. Why invest $$$ for a few people who already figured out themselves how to avoid that bug on an "old" device.
Business.Simple as that.

Testraindrop said:
They just don't care and why should they?
The stock Firmwares are noobproof, but if some geeks from XDA D) flash custom Roms its already not their business because a usual customer never even get accidentally into a recovery where he could wipe the phone.
So, they say users fault. Why invest $$$ for a few people who already figured out themselves how to avoid that bug on an "old" device.
Business.Simple as that.
Click to expand...
Click to collapse
Actually its also their loss as they fix the bricked devices under warranty
No one will tell "I flash a ROM from xda and bricked my phone" to the service center guys
Sent from the beast using CMX

I think there is a fix - I heard a couple XDA members saying that they've got a PIT file to fix the problem. Though all it does is make a new /data partition, and you lose a bit of your space (8GB instead of 11GB)

epic118 said:
I think there is a fix - I heard a couple XDA members saying that they've got a PIT file to fix the problem. Though all it does is make a new /data partition, and you lose a bit of your space (8GB instead of 11GB)
Click to expand...
Click to collapse
That's not a fix. Just a workaround to get the device up and running
Sent from my GT-I9100 using xda app-developers app

Why one should never unlock the Motorola Razr HD bootloader (xt925) !

The pro & cons of unlocking the bootloader:
Pro: Install customs ROMS with custom kernels (basically that's it)
Cons: - Loosing warranty from Motorola & your carrier
- No more firmware upgrades (your IMEI is dropped out of Motorola databank)
- Little verity of quality custom ROMs or development (close to none) exist for the Razr HD
- Future upgrade to JB & KLP will never happened (this phone is listed as a potential candidate for KLP update)
- Keeping your xt925 beyond your 1 year warranty will still guaranty, a steady upgrades of firmware
- Can root a phone with bootloader locked (without loosing warranty - root is reversible)
- Legally (Motorola binding Bootloader unlock contract), you can't sell a BL unlock Motorola Razr HD phone !
If someone can add some Pro's to an unlock bootloader please do it..

Are you sure about the firmware upgrades? I read somewhere that's not the case.

I wish I had known all this before I unlocked my phone.

Are you sure about the firmware upgrades? I read somewhere that's not the case.
Click to expand...
Click to collapse
I spoke to Motorola & my carrier services, also read the warning details before the unlock process begins.
I wish I had known all this before I unlocked my phone
Click to expand...
Click to collapse
Same here..(I learned all that after the fact)

I'd add this to Pro:
If you're stuck on Rogers 49003 ICS because you flashed the ROM trying to get root, your best option to get anything above 4.0.4 is to unlock bootloader?

Perhaps a CWM install will be possible for those with unlocked bootloaders when updates come.
It seems that in one form or another an unlocked bootloader means being able to push all the new files in doesn't it? Is there any limitation on this phone, for example flashing a new modem or kernel?

Cons one by one:
itzik_man said:
- Loosing warranty from Motorola & your carrier
Click to expand...
Click to collapse
True, but obvious.
itzik_man said:
- No more firmware upgrades (your IMEI is dropped out of Motorola databank)
Click to expand...
Click to collapse
Nope. Even if you were not to receive OTA, which by the way is not true as I've observed on my Photon Q, you can still freely flash the new firmwares yourself ^^
itzik_man said:
- Little verity of quality custom ROMs or development (close to none) exist for the Razr HD
Click to expand...
Click to collapse
Depends on ones point of view. Usually a CM port means you get newer Android sooner.
itzik_man said:
- Future upgrade to JB & KLP will never happened (this phone is listed as a potential candidate for KLP update)
Click to expand...
Click to collapse
Why it wouldn't? Unlocking BLs has no impact on upgrade schedule.
itzik_man said:
- Keeping your xt925 beyond your 1 year warranty will still guaranty, a steady upgrades of firmware
Click to expand...
Click to collapse
No. That's solely on Moto / Google decision. They don't have to update it at all. (See Droid 3, Milestone 3, Motorola XT720 etc.)
itzik_man said:
- Can root a phone with bootloader locked (without loosing warranty - root is reversible)
Click to expand...
Click to collapse
Yes, although you have to be careful, because there are scirpts checking if you're rooted.
itzik_man said:
- Legally (Motorola binding Bootloader unlock contract), you can't sell a BL unlock Motorola Razr HD phone !
Click to expand...
Click to collapse
You can sue Moto for breaking laws. They can't forbid you doing that (don't know honestly how is that in US / Canada, but I doubt that seeing how it works with computer games).
So please, while for normal user not willing to flash custom ROMs it's true that they should not unlock the bootloader, don't spill nonsenses around that. It's just that when you unlock your bootloader, you're on your own when playing with the firmware. But when you have stock firmware back on it, nothing prevents you from getting the OTA.

don't spill nonsenses around that. It's just that when you unlock your bootloader, you're on your own when playing with the firmware. But when you have stock firmware back on it, nothing prevents you from getting the OTA.
Click to expand...
Click to collapse
Possible 90% of your response represent just false theories..
OTA is goneforever once you unlock your bootloader ! If & when you be able manually to install JB, still your IMEI (not registered with Motorola) wont OTA.
You can sue nobody ! it's a contractual agreement you "sign" when you agree to unlock BL !
And if you can't OTA, No future auto upgrades.
So, before you use a statement "don't spill nonsense" make sure you are talking sense...

At least on my O2 Germany xt925 I got the update OTA from ICS to JB after unlocking. Had to return to the stock bootloader because the OTA relies on it after rebooting though.

itzik_man said:
Possible 90% of your response represent just false theories..
OTA is goneforever once you unlock your bootloader ! If & when you be able manually to install JB, still your IMEI (not registered with Motorola) wont OTA.
You can sue nobody ! it's a contractual agreement you "sign" when you agree to unlock BL !
And if you can't OTA, No future auto upgrades.
So, before you use a statement "don't spill nonsense" make sure you are talking sense...
Click to expand...
Click to collapse
Once again.
A) The reason why the page says "no updates" is beacuse OTA updates only work when you're on stock firmware, which is unlikely when you have the bootloader unlocked. That's all.
B) There are things that such "agreement" cannot contain. Being unable to sell the phone is one of them in most countries.

I disagree from the op.
Every change to device firmware compromises the warranty, not just bootloader, read the agreements ... If you exploit a bug to have root access, you will have to fool everyone who will have contact with your phone so they don't see what you have done. Even if you try to "reverse" the root, you(or the program you use) will always leave a trace.

We should be promoting "unlock the world"
This is not to imply everything should be free, however if I own something it should be mine in every regard, that includes breaking it.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 03:13 PM ---------- Previous post was at 03:12 PM ----------
@skrilax thanks for you work on the a500.
Sent from my Galaxy Nexus using Tapatalk 2

I have xt925, first thing I did was unlock boot loader. Then I updated ota to Telstra JB. OP is misleading people.

Once again.
A) The reason why the page says "no updates" is beacuse OTA updates only work when you're on stock firmware, which is unlikely when you have the bootloader unlocked. That's all.
B) There are things that such "agreement" cannot contain. Being unable to sell the phone is one of them in most countries.
Click to expand...
Click to collapse
To end my part in this discussion: The limitations, restrictions & disadvantages of unlocking the bootloader are much greater then any benefit or gain under the current availability of development !

Darbness said:
I have xt925, first thing I did was unlock boot loader. Then I updated ota to Telstra JB. OP is misleading people.
Click to expand...
Click to collapse
Have you tried out lte tethering? It doesn't work on Rogers.

To epinter -
I disagree from the op.
Every change to device firmware compromises the warranty, not just bootloader, read the agreements ... If you exploit a bug to have root access, you will have to fool everyone who will have contact with your phone so they don't see what you have done. Even if you try to "reverse" the root, you(or the program you use) will always leave a trace.http://www.linuxmobile
Click to expand...
Click to collapse
I did not notice your response at first, now to the point -
Without any disrespect to the work, time & effort invested, the main point is being ignored by the developers: All comments I got on this OP didn't touched the number one reason of my suggestion to not unlock the bootloader: There in not really enough of a variety of development options today to justification the bootloader unlocked of the xt925.

Skrilax_CZ said:
Cons one by one:
Yes, although you have to be careful, because there are scirpts checking if you're rooted.
Click to expand...
Click to collapse
Can someone elaborate on this point; I read in another thread that when you remove all rooted apps and data, clear out the files left in /system, that there is still info stored stated if the device has ever been rooted, and that this can be cleared using an app on a PC (don't remember which) however when I looked at the app it was specific to the XT926 and thus I wouldn't be able to use it.
After a thorough clean of every rooted app and everything left behind by rooted apps, is there a known way (or assumed to be working way) on XT925 to erase the record of the root.
Also, assuming I was to get my phone back to that state and remove proof of root, what specifically do I need to do in order to be careful as stated... or is epinter correct in saying that there is always a trace left behind, and if so, is this a blatant trace or something that hasn't been of much concern for Motorola in the past when servicing phones?
Tombs1234 said:
At least on my O2 Germany xt925 I got the update OTA from ICS to JB after unlocking. Had to return to the stock bootloader because the OTA relies on it after rebooting though.
Click to expand...
Click to collapse
How would I return to a stock bootloader if I were to unlock mine and an OTA didn't work? How did you do it?

itzik_man said:
The limitations, restrictions & disadvantages of unlocking the bootloader are much greater then any benefit or gain under the current availability of development !
Click to expand...
Click to collapse
It's your decision whether to unlock the bootloader or not. I'm just saying (for other users) that many of the cons you wrote were absolutely incorrect.
PantsDownJedi said:
Can someone elaborate on this point; I read in another thread that when you remove all rooted apps and data, clear out the files left in /system, that there is still info stored stated if the device has ever been rooted, and that this can be cleared using an app on a PC (don't remember which) however when I looked at the app it was specific to the XT926 and thus I wouldn't be able to use it.
After a thorough clean of every rooted app and everything left behind by rooted apps, is there a known way (or assumed to be working way) on XT925 to erase the record of the root.
Also, assuming I was to get my phone back to that state and remove proof of root, what specifically do I need to do in order to be careful as stated... or is epinter correct in saying that there is always a trace left behind, and if so, is this a blatant trace or something that hasn't been of much concern for Motorola in the past when servicing phones?
Click to expand...
Click to collapse
I believe there is something stored in the pds partition. Or at least it is that way on Droid RAZR XT912 and you had to fix it to remove the remaining traces. Flashing FXZ is also a way how to get a clean stock firmware, but pds partition is not affected that way.
PantsDownJedi said:
How would I return to a stock bootloader if I were to unlock mine and an OTA didn't work? How did you do it?
Click to expand...
Click to collapse
I think he meant "stock firmware" instead of "stock bootloader"

So if that were the case on this phone, I wonder if doing a dd backup of the pds partition before rooting at ICS, for restoring after downgrade, would be the way to go. Assuming it restores properly, it would be a good thing to add to the sticky thread about rooting. I did a dd of all my partitions except for /data last night, but I'm already rooted.
hmm... I'm wondering if there's something inaccessable in /system or even the sdcard since they get mounted with fuse. My only other Android phone was the Galaxy S II which was pretty straightforward and dead simple to root and unroot. I was surprised to see the fuse module being used to mount anything when I got this one.

The original topic is here: http://forum.xda-developers.com/showthread.php?t=1857558
I don't know if there was a proper fix developed (haven't checked) on the RAZR.

Is there any reason why I SHOULDN'T update to OTA 4.3?

As the title states, is there any reason why I shouldn't update to OTA 4.3?
I'm currently running a stock, non-rooted SGH-I337M on Bell. I'm just wondering about KNOX...if I start messing with my phone, should I do it from 4.2?

I updated to 4.3 and I'm seeing a little jank, and it feels less robust than 4.2.2 was. Also, if you intend to root or do a custom recovery/ROM, you will have to wait a few weeks until the bootloader is unlocked and some more cutting gets done on 4.3 before you can do anything like that.

aycockonxion said:
I updated to 4.3 and I'm seeing a little jank, and it feels less robust than 4.2.2 was. Also, if you intend to root or do a custom recovery/ROM, you will have to wait a few weeks until the bootloader is unlocked and some more cutting gets done on 4.3 before you can do anything like that.
Click to expand...
Click to collapse
Hmm...I don't think that the Canadian bootloaders are locked.

Snizzoop said:
Hmm...I don't think that the Canadian bootloaders are locked.
Click to expand...
Click to collapse
Ahh yes, I understand that you are correct.

aycockonxion said:
Ahh yes, I understand that you are correct.
Click to expand...
Click to collapse
So, as I understand it then...
...if I update to MK6, I will have KNOX.
The only reason I should be concerned about tripping KNOX is if I need to send the phone in for warranty, OR if I want to put the phone on some sort of enterprise server? If I don't care about either of these things, I should flash the OTA...and then root/ROM without worry?

Snizzoop said:
So, as I understand it then...
...if I update to MK6, I will have KNOX.
The only reason I should be concerned about tripping KNOX is if I need to send the phone in for warranty, OR if I want to put the phone on some sort of enterprise server? If I don't care about either of these things, I should flash the OTA...and then root/ROM without worry?
Click to expand...
Click to collapse
Virtually no carriers actually check to see if you're rooted.. Once it's accepted for warranty by the carrier it's sent to Samsung and disassembled. It carries some risk, but realistically it's not something to lose sleep over.

I'm in the same boat. I do want to root my phone soon then flash it when the 1 year warranty runs out. Should I root now or after my update? (It's asking to update now)
Would I lose root after my update anyway?

Snizzoop said:
So, as I understand it then...
...if I update to MK6, I will have KNOX.
The only reason I should be concerned about tripping KNOX is if I need to send the phone in for warranty, OR if I want to put the phone on some sort of enterprise server? If I don't care about either of these things, I should flash the OTA...and then root/ROM without worry?
Click to expand...
Click to collapse
If you don't care about either then updating to MK6 isn't going to hurt. The only other concern may be that as far as I know there is no way to revert back to 4.2.2/MG1. I have heard some people were having weird issues around OTAs though like incomplete or frozen downloads and having to start it over again. You can also flash through Kies on your computer now. I assume most of the OTA issues have been resolved now, but imho using a usb cable is always the better practice.
Maleki said:
I'm in the same boat. I do want to root my phone soon then flash it when the 1 year warranty runs out. Should I root now or after my update? (It's asking to update now)
Would I lose root after my update anyway?
Click to expand...
Click to collapse
Yes. I had to unroot to get OTA though, then re-root afterwards.
You guys might want to review this thread as well: http://forum.xda-developers.com/showthread.php?t=2535801. There are other options to OTA and Kies.

aycockonxion said:
Virtually no carriers actually check to see if you're rooted.. Once it's accepted for warranty by the carrier it's sent to Samsung and disassembled. It carries some risk, but realistically it's not something to lose sleep over.
Click to expand...
Click to collapse
The repair process works a little different in my area. If I have an issue, I take my phone to the store...I use a loaner phone while they send mine to a repair facility. If the repair facility finds a reason not to perform repairs under warranty, they don't.
crazy_dr0id said:
If you don't care about either then updating to MK6 isn't going to hurt. The only other concern may be that as far as I know there is no way to revert back to 4.2.2/MG1. I have heard some people were having weird issues around OTAs though like incomplete or frozen downloads and having to start it over again. You can also flash through Kies on your computer now. I assume most of the OTA issues have been resolved now, but imho using a usb cable is always the better practice.
Click to expand...
Click to collapse
10-4.
Last question...rooting doesn't give that "custom" warning at boot, does it? I think that's only once you install a custom recovery?

If you are not planning on rooting or anything I say go for it. It seems a lot smoother for me, battery life seems far better, im getting slightly better service, and lastly we have built in emojis now (granted you can only send them as an mms through text but you are able to see them system wide now on apps such as ig or twitter etc) I personally say go for it.

Snizzoop said:
Last question...rooting doesn't give that "custom" warning at boot, does it? I think that's only once you install a custom recovery?
Click to expand...
Click to collapse
I think it does, but honestly can't remember... did mine on Nov 23rd and flashed a custom rom within an hr of rooting.

crazy_dr0id said:
If you don't care about either then updating to MK6 isn't going to hurt. The only other concern may be that as far as I know there is no way to revert back to 4.2.2/MG1. I have heard some people were having weird issues around OTAs though like incomplete or frozen downloads and having to start it over again. You can also flash through Kies on your computer now. I assume most of the OTA issues have been resolved now, but imho using a usb cable is always the better practice.
Yes. I had to unroot to get OTA though, then re-root afterwards.
You guys might want to review this thread as well: http://forum.xda-developers.com/showthread.php?t=2535801. There are other options to OTA and Kies.
Click to expand...
Click to collapse
My plan was to go stock for a year then when the initial warranty runs out (I have sweet extended one through the re-seller) I was going to go with a custom rom. That's what I did with my S1. It doesn't look like I'll have the luxury. I already updated once and got a secure boot. Lesson learned I guess.

Slow Charging
The new update really takes a long time to charge if you are using a 3rd party charger. Idk if its true for everyone, or if this was done on purpose but I notice my gs4 charging wayyyyy slower than on 4.2.2.

downgrade confirmation

hello guys
I have a sm-n900.....it came upgraded to kitkat in the box
although the performance of the phone is mind blowing but I feel it is a battery draimer......and also I read reviews on net that people with jellybean used to have their battery last more than one day with usual udage but in my case it is only upto 16-17 hrs
I thought of downgrading to jellybean and went to service cemtre where they told me that downgrading in not possible in note 3
I then searched at home and found it is bit complicated and if we do we may loose update to kitkat if we want afterwards
like in my earlier s2 (i9100) and note (n7000) I could flash any firmware anytime
but wat to do downgrade this to jellybean without loosing the possibilities of update to kitkat

plz someone
I know people are here having far big issues compared to mine
but I would be really happy is someone would guide me through this

anikanu said:
hello guys
I have a sm-n900.....it came upgraded to kitkat in the box
although the performance of the phone is mind blowing but I feel it is a battery draimer......and also I read reviews on net that people with jellybean used to have their battery last more than one day with usual udage but in my case it is only upto 16-17 hrs
I thought of downgrading to jellybean and went to service cemtre where they told me that downgrading in not possible in note 3
I then searched at home and found it is bit complicated and if we do we may loose update to kitkat if we want afterwards
like in my earlier s2 (i9100) and note (n7000) I could flash any firmware anytime
but wat to do downgrade this to jellybean without loosing the possibilities of update to kitkat
Click to expand...
Click to collapse
you cant downgrade at all
just not going to happen sorry bud

anikanu said:
plz someone
I know people are here having far big issues compared to mine
but I would be really happy is someone would guide me through this
Click to expand...
Click to collapse
The reason you are not getting any response is because this question has been asked 59 billion times a day since KK rolled out, and the other million plus members who are aware of it are restraining themselves through giant facepalms.
In short, no, there is no way to downgrade.

donalgodon said:
The reason you are not getting any response is because this question has been asked 59 billion times a day since KK rolled out, and the other million plus members who are aware of it are restraining themselves through giant facepalms.
In short, no, there is no way to downgrade.
Click to expand...
Click to collapse
mate do you math its 58 billion times a day lol :silly:

jaythenut said:
you cant downgrade at all
just not going to happen sorry bud
Click to expand...
Click to collapse
donalgodon said:
The reason you are not getting any response is because this question has been asked 59 billion times a day since KK rolled out, and the other million plus members who are aware of it are restraining themselves through giant facepalms.
In short, no, there is no way to downgrade.
Click to expand...
Click to collapse
jaythenut said:
mate do you math its 58 billion times a day lol :silly:
Click to expand...
Click to collapse
so can I root the phone and move to some other custom kernel based rom and then flash jellybean via odin
wat wud happen if I do it using odin.....will it hardbrick or some apps wont work.....plz tell...I know its annoying but plz

anikanu said:
so can I root the phone and move to some other custom kernel based rom and then flash jellybean via odin
wat wud happen if I do it using odin.....will it hardbrick or some apps wont work.....plz tell...I know its annoying but plz
Click to expand...
Click to collapse
Forget jelly beans you can never go back all it will do is Bootloop

donalgodon said:
The reason you are not getting any response is because this question has been asked 59 billion times a day since KK rolled out, and the other million plus members who are aware of it are restraining themselves through giant facepalms.
In short, no, there is no way to downgrade.
Click to expand...
Click to collapse
and I see that u r using same ohone rooted
whuch method did y follow and also is der any prob in handling og the phone after rooting
and can u go back to stock unrooted again to restorr warranty and reset binary counter

jaythenut said:
Forget jelly beans you can never go back all it will do is Bootloop
Click to expand...
Click to collapse
u mean I cant even go to cm10.2 too

anikanu said:
u mean I cant even go to cm10.2 too
Click to expand...
Click to collapse
No, you can't

anikanu said:
and I see that u r using same ohone rooted
whuch method did y follow and also is der any prob in handling og the phone after rooting
and can u go back to stock unrooted again to restorr warranty and reset binary counter
Click to expand...
Click to collapse
I rooted via CF-AutoRoot (as my signature indicates below) and there were no problems. For me, KitKat is working perfectly in every respect.
No, you cannot reset the Knox binary trigger. I could not possibly care any less about it at this point in time.
I plan to use the device until something better comes along, then sell it, so why worry about it?

donalgodon said:
I rooted via CF-AutoRoot (as my signature indicates below) and there were no problems. For me, KitKat is working perfectly in every respect.
No, you cannot reset the Knox binary trigger. I could not possibly care any less about it at this point in time.
I plan to use the device until something better comes along, then sell it, so why worry about it?
Click to expand...
Click to collapse
so now if u visit samsung
what page the officials would open in order to see ur knox counter

Pierre118 said:
No, you can't
Click to expand...
Click to collapse
how r u having knox still 0 even after rooting

anikanu said:
how r u having knox still 0 even after rooting
Click to expand...
Click to collapse
You need to do some searching on the site. All these questions have answers that have been gone over and over.
Early 4.3 users could root their phone but Knox gets tripped. RDLV method worked then without tripping Knox up till MJ3 of 4.3. Anything above that as stock and Knox gets tripped. KitKat goes one step further in that you cannot revert to 4.3 at all, even if you are willing to trip Knox.
You can root the phone but AFAIK (I haven't bothered with KK - my phone runs brilliantly on v6 (4.3) Omega) you trip Knox anyway you do it.
Knox 0x1 may or may not doom your warranty - somecountries have laws that say Samsung cannot quirm out of hardware problems by claiming software changes. You may or may not care about Knox. Mine is a grey import from HK that I had all kinds of fun getting over to a non-freaky ROM, so when it eventually triggered Knox I didn't give a toss. I did root the phone with RDLV and changed ROMs several times before something that shouldn't have, tripped the Knox bit.
Now there is about as brief a history as you will get. Use what is in it to go search and find any more complete answers.
Always search before asking basic questions - at the least it means you will be able to ask intelligent questions, not ones you can find by looking at the titles of recent posts in Q&A forums.

anikanu said:
so now if u visit samsung
what page the officials would open in order to see ur knox counter
Click to expand...
Click to collapse
They'd just boot to Download mode and see the Knox flag.
I don't care about it, honestly. If I ever need warranty assistance, I'd just hope for the best, but since it's Samsung, I'd expect the worst.

Journyman16 said:
You need to do some searching on the site. All these questions have answers that have been gone over and over.
Early 4.3 users could root their phone but Knox gets tripped. RDLV method worked then without tripping Knox up till MJ3 of 4.3. Anything above that as stock and Knox gets tripped. KitKat goes one step further in that you cannot revert to 4.3 at all, even if you are willing to trip Knox.
You can root the phone but AFAIK (I haven't bothered with KK - my phone runs brilliantly on v6 (4.3) Omega) you trip Knox anyway you do it.
Knox 0x1 may or may not doom your warranty - somecountries have laws that say Samsung cannot quirm out of hardware problems by claiming software changes. You may or may not care about Knox. Mine is a grey import from HK that I had all kinds of fun getting over to a non-freaky ROM, so when it eventually triggered Knox I didn't give a toss. I did root the phone with RDLV and changed ROMs several times before something that shouldn't have, tripped the Knox bit.
Now there is about as brief a history as you will get. Use what is in it to go search and find any more complete answers.
Always search before asking basic questions - at the least it means you will be able to ask intelligent questions, not ones you can find by looking at the titles of recent posts in Q&A forums.
Click to expand...
Click to collapse
donalgodon said:
They'd just boot to Download mode and see the Knox flag.
I don't care about it, honestly. If I ever need warranty assistance, I'd just hope for the best, but since it's Samsung, I'd expect the worst.
Click to expand...
Click to collapse
I may be annoying u guys
but what I understand from till now is dat I wont get the privileges of the phone as I used to get in xperia live and sgs2 and maybe what I will use be the stock rom
btw I have still not downloaded the app data of knox which is of 170mb.....wat do u guys suggest should I do it or let it be
and 1 last question that is der any way to have mass storage mode.....as in mtp we dont see the files and folders starting with (.) and I have many imp stuffs on my sd which have their starting with a . and u all know that in mtp we dont see such files and folders.....so is der any way to have the mass storage mode back
plz answer......I know I annoyed a lot.....but plz

You should be able to use another mode. When you connect via USB, swipe down the Notification bar and there should be a Notify there you can tap to choose other modes.
You might need to go into Build Number (Settings/About Phone) and tap 7 times to turn on Developer mode and then turn on USB Debug. (not sure as that's always one of the first things I do)
Unless you are the only person on the planet who sees a need for Knox, you don't need to DL anything to do with Knox. Check in Application Manager and see if you can turn all of it off.

Journyman16 said:
You should be able to use another mode. When you connect via USB, swipe down the Notification bar and there should be a Notify there you can tap to choose other modes.
You might need to go into Build Number (Settings/About Phone) and tap 7 times to turn on Developer mode and then turn on USB Debug. (not sure as that's always one of the first things I do)
Unless you are the only person on the planet who sees a need for Knox, you don't need to DL anything to do with Knox. Check in Application Manager and see if you can turn all of it off.
Click to expand...
Click to collapse
I also have enabled developer options due to my habit of doing in cm roms in previous phones
but on usb connection there are only 2 modes
media transfer protocol
camera protocol
mass storage is missing

donalgodon said:
I plan to use the device until something better comes along, then sell it, so why worry about it?
Click to expand...
Click to collapse
Interesting question. Do you find you can easily sell your rooted/modified phones?
I'm always concerned that people won't want to buy a rooted phone that's potentially been flashed 100+ times with possible excessive CPU over-clocking etc. I always try to put the phone back to stock (or as close as possible) before I sell it on.
Is it just me who feels those concerns?

Medical HRH said:
Interesting question. Do you find you can easily sell your rooted/modified phones?
I'm always concerned that people won't want to buy a rooted phone that's potentially been flashed 100+ times with possible excessive CPU over-clocking etc. I always try to put the phone back to stock (or as close as possible) before I sell it on.
Is it just me who feels those concerns?
Click to expand...
Click to collapse
Well, in my region, the vast majority of buyers don't even know what root is, so it's never been an issue for me. I don't expect that to change anytime soon. The Note 3 doesn't show any issues at all when reflashed unless Knox flag is tripped. Even then, the only "issue" is the warranty bit flag shown in Download mode and the loss of Knox container, which almost nobody uses. Out of a 100 buyers, you might find one that knows what root is and less than that who know how to get to Download mode, and even fewer who'd potentially use Knox, so no, not a problem.