Related
Hey guys I have been reading through this forum and I think I get most stuff now. There is only one thing confusing me, when talking about bootloaders and unlocking them, everyone says its irreversible and you loose warranty and drm keys.
My question is, why? Can't we just backup it with CWM or similar? Can't we just make a backup when we receive the device from factory and then if we need warranty for something can't we just flash back and put everything original, including bootloader and stuff?
Thank you
shamelessly dumping to first page
Your warranty is never truly lost. Just remember, if they can't turn it on, they don't know it was rooted.
lowandbehold said:
Your warranty is never truly lost. Just remember, if they can't turn it on, they don't know it was rooted.
Click to expand...
Click to collapse
thank you, but my curiosity extends to the technical level, not just in the practical sense
gtype said:
thank you, but my curiosity extends to the technical level, not just in the practical sense
Click to expand...
Click to collapse
Ok, well the technical answer is once you unlock it, it can't be locked. Recovery does not back up your bootloader. A better alternative is flashing a different bootloader. There are some phones where the engineering bootloader used by OEM devs is available, so you can always go back to the stock bootloader.
EDIT: Actually now that I think about it, you can make a backup. I honestly have not dealt much with Samsung phones, so I am not sure if it is the same. But when you first root an HTC you take an initial image, which you store on your SD card or computer and you use it to unroot. When you unroot using that method it sets your bootloader back to factory. Also when you use a factory image, such as a PDxx.img and flash that through hboot, it gives you a stock bootloader as well.
lowandbehold said:
Ok, well the technical answer is once you unlock it, it can't be locked. Recovery does not back up your bootloader. A better alternative is flashing a different bootloader. There are some phones where the engineering bootloader used by OEM devs is available, so you can always go back to the stock bootloader.
Click to expand...
Click to collapse
isnt the bootloader in the boot partition?
gtype said:
isnt the bootloader in the boot partition?
Click to expand...
Click to collapse
Yes, the bootloader and the kernel are in the boot partition.
lowandbehold said:
Yes, the bootloader and the kernel are in the boot partition.
Click to expand...
Click to collapse
sorry if I'm being thick, but since the bootloader is part of the partition, what stops me from backuping all the partitions, unlock the bootloader, and then after some time flash the original dumped stuff?
gtype said:
sorry if I'm being thick, but since the bootloader is part of the partition, what stops me from backuping all the partitions, unlock the bootloader, and then after some time flash the original dumped stuff?
Click to expand...
Click to collapse
Hey, you can try it. That is a very sensitive partition to mess with. The main issue is, how many times have you flashed a ROM and for some reason it just doesnt flash right and you get a boot loop? Easy fix, wipe everything, reflash, good to go. If you flash the bootloader and reboot your phone and something went wrong with the flash...you have a hard brick. No coming back, period. So, experiment wisely. It is the same thing with flashing through terminal. If you get 1 space, 1 character wrong in the command line...hard brick.
actually I don't own a smartphone yet, but I'm going to soon. Since I'm well versed in Linux I was checking out the Android OS in general and that question popped up in my mind and I just couldn't find any info about it. Does that make kernel flashing dangerous too, since it's in the same partition as the bootloader?
gtype said:
actually I don't own a smartphone yet, but I'm going to soon. Since I'm well versed in Linux I was checking out the Android OS in general and that question popped up in my mind and I just couldn't find any info about it. Does that make kernel flashing dangerous too, since it's in the same partition as the bootloader?
Click to expand...
Click to collapse
No, kernel flashing is fine. A bad flash just ends in a bootloop, no big deal. Bootloaders and radios..those are the ones you have to be careful with.
lowandbehold said:
No, kernel flashing is fine. A bad flash just ends in a bootloop, no big deal. Bootloaders and radios..those are the ones you have to be careful with.
Click to expand...
Click to collapse
Alright, thank you very much.
Actually, it just struck me, why is it dangerous if it doesn't flash properly, the recovery partition is separate and you can make the device boot from it right?
gtype said:
Alright, thank you very much.
Actually, it just struck me, why is it dangerous if it doesn't flash properly, the recovery partition is separate and you can make the device boot from it right?
Click to expand...
Click to collapse
I am assuming you could if you have one backed up. But when a bootloader doesn't flash right and you get a brick, you can't even get into recovery. Most of the time the phone won't even power on. Because booting into recovery requires the bootloader.
lowandbehold said:
I am assuming you could if you have one backed up. But when a bootloader doesn't flash right and you get a brick, you can't even get into recovery. Most of the time the phone won't even power on. Because booting into recovery requires the bootloader.
Click to expand...
Click to collapse
I see. Thanks a lot for your time
gtype said:
I see. Thanks a lot for your time
Click to expand...
Click to collapse
Hey, no problem. Just sitting here on the front end of my 12 hour shift..nothing better to do!
lowandbehold said:
Hey, no problem. Just sitting here on the front end of my 12 hour shift..nothing better to do!
Click to expand...
Click to collapse
New question, if you are still around. What exactly is a locked bootloader? Is it just a bool in the bootloader code? Where are the DRM keys and why are they lost?
gtype said:
New question, if you are still around. What exactly is a locked bootloader? Is it just a bool in the bootloader code? Where are the DRM keys and why are they lost?
Click to expand...
Click to collapse
It depends on the device. A bootloader is usually unlocked by an unlock.bin for that device. I'm not an expert on bootloaders though...
dmeadows013 said:
It depends on the device. A bootloader is usually unlocked by an unlock.bin for that device. I'm not an expert on bootloaders though...
Click to expand...
Click to collapse
I was talking physically, like are the keys in the bootloader, is S_OFF etc bool variables etc. I guess I'll try to dig it up somewhere. thanks
gtype said:
New question, if you are still around. What exactly is a locked bootloader? Is it just a bool in the bootloader code? Where are the DRM keys and why are they lost?
Click to expand...
Click to collapse
A locked bootloader doesn't allow you to change key parts of the system such as a kernel. So you can still root your phone, but all of the custom ROM's have to use the stock kernel. So if you are on a gingerbread stock ROM, you can't run Ice cream sandwich because you can't change kernels. The DRM keys are what is used to encrypt the bootloader, so if you unlock the bootloader the keys are lost.
I have Asus Eee Pad TransformerTF101 with an unlockbootloader is there any way to get the device back with locked bootloader ?
and how i can lock the bootloader again ?
The bootloader does not 'lock and unlock'. What are you trying to do? Unroot the device? Reinstall android OEM recovery and return to stock?
The 'locked' or 'unlocked' bootloader simply refers to the fact that the bootloader is encrypted, and for some versions we have the encryption key and can manually unlock via NVFlash to restore a bricked device, yet on other versions the bootloader key is unknown thus it is considered 'locked'.
I suggest reading up a bit more. If you don't know what you are trying to do and able to explain your problem then we can't possibly help you.
There is no concept of locked or unlocked in the tf101 bootloader, in the most general sense it is unlocked as it allows booting of unsigned kernels, and flashing of unsigned blobs.
the leaked key allows lower level communication (bootrom) with the device and can recover from bootloader errors.
hi Brothers
I applied these steps
http://www.youtube.com/watch?feature=player_embedded&v=VMHXeYMgPy4
Now i would like to return bootloader lock
thanx
You are not "back with a locked bootloaded" please use the right terminology..
luna_c666 said:
You are not "back with a locked bootloaded" please use the right terminology..
Click to expand...
Click to collapse
Haha I knew this one would be good!!!!!!!
I love how every once in awhile little stevie comes from nowhere and hands someone's ass back to them on a silver platter (done it to me a few times to lol)
One day i will be like himand you luna one day
Sent from my Transformer TF101 using xda premium
hi Brothers
Im sorry guyz i did n't explain to you what i wanted exactly ,
I applied these steps
http://www.youtube.com/watch?feature=player_embedded&v=VMHXeYMgPy4
Now i would like to return bootloader lock
thanx
lo3ti said:
hi Brothers
Im sorry guyz i did n't explain to you what i wanted exactly ,
I applied these steps
Now i would like to return bootloader lock
thanx
Click to expand...
Click to collapse
Maybe you're trying to say you want to unroot and return to stock?
Because the bootloader questions have been answered for you
by luna_c666 and lilstevie above.
baseballfanz said:
Maybe you're trying to say you want to unroot and return to stock?
Because the bootloader questions have been answered for you
by luna_c666 and lilstevie above.
Click to expand...
Click to collapse
I'm curious if the fellow is confusing the 'bootloader' with the recovery mode? From the sounds of it...he either has little understanding of english and can't/hasn't read my guide or is just dense, I'm leaning towards the first scenario
I dropped my phone last night and broke the screen and can no longer see anything. I know I can restore with Odin but how can I re-lock the bootloader without being able to see the screen?
mbmlsx said:
I dropped my phone last night and broke the screen and can no longer see anything. I know I can restore with Odin but how can I re-lock the bootloader without being able to see the screen?
Click to expand...
Click to collapse
restoring the completely stock odin file should relock the bootloader as well.
Thanks!
no it dont lock the bootloader you have to push the stock aboot.img via adb since you cant see your screen, then power off and odin back to stock. on a side note i doubt they will even check to see if your bootloader is unlocked.
Neverendingxsin said:
restoring the completely stock odin file should relock the bootloader as well.
Click to expand...
Click to collapse
That does not re-lock yor bootloader. You have to use ez-unlock to relock it then flash stock image
Tap'n
droidstyle said:
no it dont lock the bootloader you have to push the stock aboot.img via adb since you cant see your screen, then power off and odin back to stock. on a side note i doubt they will even check to see if your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks but where can i find the stock aboot.img? I looked through your all in one guide but couldnt find anything about adb the stock boot or the file.
mbmlsx said:
Thanks but where can i find the stock aboot.img? I looked through your all in one guide but couldnt find anything about adb the stock boot or the file.
Click to expand...
Click to collapse
pull the stock aboot.img from the ez-unlock app with file manager or something equivalent and put it on the root of your sd card. i forget the command to push with adb, but there is some info around here on it. ill check around and see if i can find it.
when you open link click on old info!
http://forum.xda-developers.com/showpost.php?p=30274259&postcount=1
Why even restore to stock. Insurance does not care if its rooted and unlocked nor will Samsung if your sending it in for repairs.
Sent from my SCH-I535 using Tapatalk 2
johnnilsson said:
Why even restore to stock. Insurance does not care if its rooted and unlocked nor will Samsung if your sending it in for repairs.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
True. Just trying to cover my ass just in case.
Run it over with your car.
Sent from my SCH-I535 using Tapatalk 2
Actually I'm pretty sure you will be in "locked" status just from doing Odin with a full factory image. Its exactly how I relock. It flashes the new boot.img and if you use the ez-unlock app afterwards, it shows as locked. Imagine it as still having unlock capabilities with aboot, but still being in locked status. For all intensive purposes, you're locked.
Don't worry about it, your not claiming warranty. In this instance it does not matter at all. Your having the hardware itself being repaired at a cost to you, or your making an insurance claim on a physically damaged device. Either way there is no software related issues that your claiming therefore root is completely irrelevant.
And remember, rooting is not illegal, it just voids your warranty if you screw something up software related.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
TechSavvy2 said:
Actually I'm pretty sure you will be in "locked" status just from doing Odin with a full factory image. Its exactly how I relock. It flashes the new boot.img and if you use the ez-unlock app afterwards, it shows as locked. Imagine it as still having unlock capabilities with aboot, but still being in locked status. For all intensive purposes, you're locked.
Click to expand...
Click to collapse
i thought this at one time but its not true...going back to stock does replace boot.img(kernel), but not the aboot.img(bootloader). you have to lock with the ez-unlock app or push the secure aboot.img via terminal or adb.
droidstyle said:
i thought this at one time but its not true...going back to stock does replace boot.img(kernel), but not the aboot.img(bootloader). you have to lock with the ez-unlock app or push the secure aboot.img via terminal or adb.
Click to expand...
Click to collapse
drioidstyle is 100% correct guys and gals.... I have performed tests on 3 different S3's to confirm.... Follow his instructions in that thread.... Edit: It is Brian Gove's thread in this same forum...
Next time just say you dropped it in a lake or the ocean. That way you have nothing to return and you have a extra battery
Hi, I'm just about to root root my N5. I had already 2 htc phones and i rooted them without problems. But now I'd like to know whether there is something I have to pay attention about more than on other phone or is the Nexus 5 in general a "easy to root" phone which doesn't brick often? And I'd also like to know whether the warranty restores when gettin the phone back to stock?
Nothing is harder to brick than a Nexus.
There is a flash counter that can be reset if you need to warranty the device.
Sent from my Nexus 5 using Tapatalk
Nexus is easy-street to root compared so other devices. Very hard to brick it unless you load a rom that is not compatible, obviously.
When you go back to stock you can re-lock the bootloader and as the above guy said reset the flash counter.
Hope this helps.
estallings15 said:
Nothing is harder to brick than a Nexus.
There is a flash counter that can be reset if you need to warranty the device.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
mistahseller said:
Nexus is easy-street to root compared so other devices. Very hard to brick it unless you load a rom that is not compatible, obviously.
When you go back to stock you can re-lock the bootloader and as the above guy said reset the flash counter.
Hope this helps.
Click to expand...
Click to collapse
Thanks Guys for the quick replies! Helps me a lot! Do you know whether the bootloader status shows "locked" or "relocked" then ?
sGollSv said:
Thanks Guys for the quick replies! Helps me a lot! Do you know whether the bootloader status shows "locked" or "relocked" then ?
Click to expand...
Click to collapse
There is an image of a padlock on the splash screen and also the lock status is listed in the bootloader. They change when you lock or unlock it. It's a simple fastboot command. This isn't an HTC. This is a Nexus. Whole different ball of wax.
Sent from my Nexus 5 using Tapatalk
estallings15 said:
There is an image of a padlock on the splash screen and also the lock status is listed in the bootloader. They change when you lock or unlock it. It's a simple fastboot command. This isn't an HTC. This is a Nexus. Whole different ball of wax.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
So they won't recognize if I did already unlocked it ?
sGollSv said:
So they won't recognize if I did already unlocked it ?
Click to expand...
Click to collapse
Reset the tamper flag and relock and no one will know the difference. http://forum.xda-developers.com/showthread.php?p=47156064
jd1639 said:
Reset the tamper flag and relock and no one will know the difference. http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
Ok thank you, I'm gonna root it now
jd1639 said:
Reset the tamper flag and relock and no one will know the difference. http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
What he said.
Sent from my Nexus 5 using Tapatalk
after unlocking make sure to boot the phone fully once before attempting to install a custom recovery or whatever.
meangreenie said:
after unlocking make sure to boot the phone fully once before attempting to install a custom recovery or whatever.
Click to expand...
Click to collapse
and also to restart the bootloader, I remember I had something go awry when I loaded twrp but it was being goofy before I could go into it and that is the solution
How to root Nexus 5 without unlocking bootloader?
mini_wan said:
How to root Nexus 5 without unlocking bootloader?
Click to expand...
Click to collapse
theres no way yet, it cant be done as of now. you can unlock it, get root, then relock it easy enough.
simms22 said:
theres no way yet, it cant be done as of now. you can unlock it, get root, then relock it easy enough.
Click to expand...
Click to collapse
Unlock bootloader will earse my all data
simms22 said:
theres no way yet, it cant be done as of now. you can unlock it, get root, then relock it easy enough.
Click to expand...
Click to collapse
I not want lost my data:crying:
mini_wan said:
Unlock bootloader will earse my all data
Click to expand...
Click to collapse
mini_wan said:
I not want lost my data:crying:
Click to expand...
Click to collapse
thats understandable. thats why i do it right away. backup and save whatever you can onto your computer.
Haha the first thing I did when I got my nexus 5 was unlock bootloader and root to avoid this!
Sorry to gloat
Sent from my Nexus 5 using xda app-developers app
TechMennis said:
Haha the first thing I did when I got my nexus 5 was unlock bootloader and root to avoid this!
Sorry to gloat
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
i got mine and never did power it on into the os once while unrooted. booted to bootloader very first thing, unlocked, flashed, then powered it in to the os the first time with custom rom/kernel
adb backup was implemented for this exact purpose, though it seems to have mixed results for people. you could try it
As others say learn about your phone. ADB commands save it.
The number of stupid tool kits on the nexus 5 is out of hand. No wonder pple can't do anything. They buy a phone unlock it and flash the wrong thing and cry. Tough learn!
Sent by mobile telephone.