I was wondering if anyone knows whether or not rooting/unlocking bootloader trips a rumored "fuse" that is permanent? Can this be fixed by reverting back to stock and relocking the bootloader. Never heard of anything like this with nexus devices.
This is the wrong forum, but no, rooting and unlocking bootloader has no effect on fuse
Sent from my Nexus 6P using Tapatalk
heleos said:
This is the wrong forum, but no, rooting and unlocking bootloader has no effect on fuse
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I don't think anyone has found anything that does trip it yet.
Related
On the atrix I don't want it unlocked anymore the bootloader so how can it be locked again?
It can't, once unlocked always unlocked. Only thing you can do is flash an sbf to "hide" the unlock text but that is not recommended.
sillyshyme said:
On the atrix I don't want it unlocked anymore the bootloader so how can it be locked again?
Click to expand...
Click to collapse
Did you ask in the pudding thread? I'm pretty sure all this is covered there.
Sent from my MB860 using xda premium
I believe a fuse is burned once you unlock the bootloader and the process is irreversible. Sorry
Running MIUI Alpha
WuchuHurD said:
I believe a fuse is burned once you unlock the bootloader and the process is irreversible. Sorry
Running MIUI Alpha
Click to expand...
Click to collapse
YEP YOU ARE 1000000000010001000%
correct witch also kinda looks like the numbers in that particular fuse witch
is burnt
and Dont try to flash back to 1.8.3
eather or you will something like this
failed to boot
0001
witch translates to a hard brick
Sent from my MB860 using Tapatalk
I had to return my atrix to warenty due to the digitizer. I just pluged my atrix up an ran the software updter from motos website. It remov3d the unlock from my device. It is actually simple to do
Sent from my Transformer TF101 using Tapatalk
I did the same thing this week and sent my phone back to att for a warranty replacement.
That doesn't actually "relock" the device. It just removes the unlocked sign at boot.
Sent from my MB860 using XDA App
Has there been a method created yet to root the Nexus 7 without unlocking the bootloader?
I'd like to load up some of my old settings from my last tablet but don't want to unlock the bootloader just yet...
Should probably be in Q&A section.
No.
Also... what this guy said
jklitten said:
Should probably be in Q&A section.
Click to expand...
Click to collapse
Helpful hint, if you're making a new thread and it has or should have a question mark it goes in Q & A section
Sent from my Nexus 7 using xda app-developers app
danifunker said:
Has there been a method created yet to root the Nexus 7 without unlocking the bootloader?
I'd like to load up some of my old settings from my last tablet but don't want to unlock the bootloader just yet...
Click to expand...
Click to collapse
Just re lock it after you root.
Sent from my Nexus 7 using Tapatalk 2
colonel187 said:
Just re lock it after you root.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I flashed the original boot.king the relocked it. Hopefully the boot.img is okay...
Sent from my Nexus 7 using Tapatalk 2
None that I've found but you can just lock it again after (if for some reason you want to).
Sent from my Nexus 7 using XDA Premium HD app
I'm also kind of interested in this; my Moto Atrix 2 has a locked bootloader (curse you Motorola) but we were able to root it and get CWM on it pretty easily I think. I'm not at all sure how that worked, and I don't know if the root I gained was "optimal" (is there even a difference?). I'm interested also in seeing if there is a way to get root without unlocking for the Nexus 7 because I don't want to factory reset just yet.
Are you guys sure there is no way? Is it just a fundamental difference between the two devices that prohibits it on the Nexus?
If you unlock, root, install custom rom & kernel and then follow this tutorial to reset it to factory, can you send your device to asus without being discovered?
Hi!
I want to root my Nexus 7 with unlockroot but I know that then warranty won't work anymore. But if I unroot then my warranty will work again. So my question is.. When I root my Nexus and when somethong happens (like not turning on anymore or etc.) then I can't unroot it? It means that warranty won't work and I have to fix it by myself or take it to some business who does things like this.
Just use one of the nexus toolkits and you can unroot or relock bootloader, whatever you want.
What toolkit do you suggest using? Because I just ordered a new 16 gb Wi-Fi version
Sent from my SGH-T959V using xda app-developers app
As far as I know they are both as good as each other. It seems to be down to your UI preference. I use mskip's toolkit, but other's prefer Wug's.
So if my Nexus 7 is not turning on I can easily relock bootloader and unroot?
Sent from my Nexus 7 using xda app-developers app
AW: Rooting Nexus 7 16GB
jeremin said:
So if my Nexus 7 is not turning on I can easily relock bootloader and unroot?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Exactly
Sent from my Nexus 7 using xda app-developers app
Wat from do you guys suggest starting out with
Sent from my SGH-T959V using xda app-developers app
jeremin said:
So if my Nexus 7 is not turning on I can easily relock bootloader and unroot?
Click to expand...
Click to collapse
How would anybody do anything to a device that can not be turned on?
Perhaps you meant "won't boot", but who knows really.
If you experience a hardware failure or do something dumb like flash junk to the bootloader (or erase it without flashing a valid one before exiting the currently-running bootloader), then nobody here can guarantee you anything at all.
There have been a couple of reports on here of devices which developed apparent hardware troubles which did not totally brick the device (that is, the unlocked bootloader state could still be observed), but apparently wrecked things to the point that no currently known techniques could rescue the device or relock the bootloader.
Having said that, there have been even more reports of newbs doing stupid stuff and bricking their devices. Interpret that any way you like; I interpret it to mean the owner bricking the device is more likely than it being caused by hardware failure.
Until there is something like "nvflash" for the N7 (might never happen), the N7 should not be considered to be unbrickable (say compared to Samsung devices that work with Kies/heimdal).
good luck
Hey guys,
I just bought the nexus 4 from a guy and its working awesome. The only "problem" I have is that the guy before me was playing around with the nexus. And now I have a locked bootloader, no SU binaries/root but CWM?? Is it possible to have CWM with a locked bootloader?
Anyways, i dont want to play around with it because the original store that sold this nexus will blame me for playing around with it if something actually happens.
So can i update it to key lime pie when it comes out without any problems?? Or can i remove CWM without unlocking the bootloader(i have alot of apps)?
Thanks
Sent from my Nexus 4 using xda app-developers app
You can flash a ROM and then relock the bootloader. Just unlock it and start again
Nevermind
EddyOS said:
You can flash a ROM and then relock the bootloader. Just unlock it and start again
Click to expand...
Click to collapse
Can i update it without removing the nonfunctional recovery?
Sent from my Nexus 4 using xda app-developers app
It's better to go back to 100% stock so you know exactly what's been done
You can always use this if you're rooted. https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Sent from my Nexus 4 using Tapatalk 4 Beta
Hello guys
THIS IS A QUESTION TO ALL THOSE WHO DONT CARE ABOUT SAMSUNG WARRANTY/ AT&T WARRANTY.
I am aware that attempting to downgrade from kit kat to jellybean will trip Knox counter however I don't care for it. What will be the worst consequence of me doing so. Soft brick? Or hard brick. And if I do succeed will the triped counter prevent me from having a custom recovery.
Tripping the Knox bootloader counter to 0x1 isn't a worry of mine . But a hard brick is so if I can and be able to load custom recovery NOT SAGES TRAP. That be great. I've been rooting/flashing for years now and I never seen such measures of slavery from a company. I never bought a phone with warranty anyways.
Ps: there's no straight answer in searches. All I've gotten is mixed answer I need a straight YES or NO. If yes how.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
androidfine16 said:
Hello guys
THIS IS A QUESTION TO ALL THOSE WHO DONT CARE ABOUT SAMSUNG WARRANTY/ AT&T WARRANTY.
I am aware that attempting to downgrade from kit kat to jellybean will trip Knox counter however I don't care for it. What will be the worst consequence of me doing so. Soft brick? Or hard brick. And if I do succeed will the triped counter prevent me from having a custom recovery.
Tripping the Knox bootloader counter to 0x1 isn't a worry of mine . But a hard brick is so if I can and be able to load custom recovery NOT SAFE STRAP. That be great. I've been rooting/flashing for years now and I never seen such measures of slavery from a company. I never bought a phone with warranty anyways.
Ps: there's no straight answer in searches. All I've gotten is mixed answer I need a straight YES or NO. If yes how.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
androidfine16 said:
Hello guys
THIS IS A QUESTION TO ALL THOSE WHO DONT CARE ABOUT SAMSUNG WARRANTY/ AT&T WARRANTY.
I am aware that attempting to downgrade from kit kat to jellybean will trip Knox counter however I don't care for it. What will be the worst consequence of me doing so. Soft brick? Or hard brick. And if I do succeed will the triped counter prevent me from having a custom recovery.
Tripping the Knox bootloader counter to 0x1 isn't a worry of mine . But a hard brick is so if I can and be able to load custom recovery NOT SAGES TRAP. That be great. I've been rooting/flashing for years now and I never seen such measures of slavery from a company. I never bought a phone with warranty anyways.
Ps: there's no straight answer in searches. All I've gotten is mixed answer I need a straight YES or NO. If yes how.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, you can't downgrade an ATT I337 from 4.4.2 back to Jelly bean. They locked the boot loader and it is not possible to flash a downgraded kernel. It's not a warranty issue, it's a "there's no way to do it that is known" issue.
Some folks with Canadian phones have reported success (at expense of tripping Knox) but I'm not aware of any way to do it on U.S. ATT phones. And I agree with you, it's ridiculous what ATT/Verizon are doing with these locked boot loaders. Next time, I will buy an unlocked phone...
Marc
Frankenscript said:
No, you can't downgrade an ATT I337 from 4.4.2 back to Jelly bean. They locked the boot loader and it is not possible to flash a downgraded kernel. It's not a warranty issue, it's a "there's no way to do it that is known" issue.
Some folks with Canadian phones have reported success (at expense of tripping Knox) but I'm not aware of any way to do it on U.S. ATT phones. And I agree with you, it's ridiculous what ATT/Verizon are doing with these locked boot loaders. Next time, I will buy an unlocked phone...
Marc
Click to expand...
Click to collapse
Is there at least some sight of relief to report in the attempts at unlocking so far. Beside Safe strap.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
androidfine16 said:
Is there at least some sight of relief to report in the attempts at unlocking so far. Beside Safe strap.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Everything I have read suggests no known avenue of exploit. I think this is a permanent and irrevocable thing that our wonderful devs have been unable to crack. Sigh.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Of I'm not mistaking the s5 also had a locked bootloader. So will an exploit in that aid here.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
androidfine16 said:
Hello guys
THIS IS A QUESTION TO ALL THOSE WHO DONT CARE ABOUT SAMSUNG WARRANTY/ AT&T WARRANTY.
I am aware that attempting to downgrade from kit kat to jellybean will trip Knox counter however I don't care for it. What will be the worst consequence of me doing so. Soft brick? Or hard brick. And if I do succeed will the triped counter prevent me from having a custom recovery.
Tripping the Knox bootloader counter to 0x1 isn't a worry of mine . But a hard brick is so if I can and be able to load custom recovery NOT SAGES TRAP. That be great. I've been rooting/flashing for years now and I never seen such measures of slavery from a company. I never bought a phone with warranty anyways.
Ps: there's no straight answer in searches. All I've gotten is mixed answer I need a straight YES or NO. If yes how.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Except for the boot loader, the rest of the system can be downgraded to MK2. Read this thread for more info http://forum.xda-developers.com/showthread.php?t=2663545
jmjoyas said:
Except for the boot loader, the rest of the system can be downgraded to MK2. Read this thread for more info http://forum.xda-developers.com/showthread.php?t=2663545
Click to expand...
Click to collapse
Yeah but there's no point in doing that if I can't load a custom recovery afterwards. Man f**Ck Samsung and att
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app