...as opposed to on the Nook Tablet (efuse, m-shield, etc)?
I understand that CWM on the Fire is an indication of an unlocked bootloader, but I always like reading about the more technical details.
Related
Is the Tab 10.1 SBK locked, or can even the bootloader be patched?
Master Melab said:
Is the Tab 10.1 SBK locked, or can even the bootloader be patched?
Click to expand...
Click to collapse
Depends on how lucky you are. The Limited Edition Tabs given out at Google I/O don't have SBK set and can be nvflashed at will. Some of the retail units seem to be missing an SBK as well, and show a Nexus One like open padlock during boot.
But some of the retail Tabs are SBK locked. These don't show the padlock at all, and fail with the dreaded 0x4 error when you try nvflashing. Presumably the earlier retail manufacturing lots were unlocked as a lot of people are getting locked replacements for defective Tabs. Not a big deal as there's a procedure using Samsung's ODIN tool and the ODIN bootloader mode to flash a 10.1v firmware image that can be rooted. From there, ROM Manager can be installed and CWM installed, and the stock image reinstalled and rooted.
The bootloader doesn't look for signed images and there are no SSKs on the Tegra requiring a signed bootloader. The only signature check is on update zips, which isn't a problem once you set up CWM.
pokey9000 said:
The bootloader doesn't look for signed images and there are no SSKs on the Tegra requiring a signed bootloader. The only signature check is on update zips, which isn't a problem once you set up CWM.
Click to expand...
Click to collapse
So if i get you correctly, even if you have a locked bootloader, you can use ODIN, flash ur tab and at the end you can flash the the stock rom but with a unlocked bootloader?
pokey9000 said:
Depends on how lucky you are. The Limited Edition Tabs given out at Google I/O don't have SBK set and can be nvflashed at will. Some of the retail units seem to be missing an SBK as well, and show a Nexus One like open padlock during boot.
But some of the retail Tabs are SBK locked. These don't show the padlock at all, and fail with the dreaded 0x4 error when you try nvflashing. Presumably the earlier retail manufacturing lots were unlocked as a lot of people are getting locked replacements for defective Tabs. Not a big deal as there's a procedure using Samsung's ODIN tool and the ODIN bootloader mode to flash a 10.1v firmware image that can be rooted. From there, ROM Manager can be installed and CWM installed, and the stock image reinstalled and rooted.
The bootloader doesn't look for signed images and there are no SSKs on the Tegra requiring a signed bootloader. The only signature check is on update zips, which isn't a problem once you set up CWM.
Click to expand...
Click to collapse
Very helpful and concise. What are SSKs? And can nvflash be enabled with a custom bootloader?
Is there any distinguishing feature on the non-SBK locked Tabs, like maybe a specific string their serial number?
I am bumping this thread.
Master Melab said:
Very helpful and concise. What are SSKs? And can nvflash be enabled with a custom bootloader?
Click to expand...
Click to collapse
The SSK is an additional encryption key usually used for encrypting the kernel and other stuff. The Tab doesn't encrypt anything but the bootloader.
The SSK, SBK, and other stuff is stored in the Tegra2 chip itself in efuses. These are one-time programmable, that is, if your Tab has an SBK set then the only (known) way to unlock it is to unsolder the chip and put in a fresh Tegra2.
Is there a way to reset the eFuse on the Tegra or are their spare additional fuses that one can burn and select?
I have to manage a bunch of devices; I want to write my own locked boot loader and distribute signed updates periodically.
Any ideas?
Sent from my Amazon Kindle Fire using xda app-developers app
This tablet was bought from a online warehouse as a returned item. Just for kicks I powered up using the power and - volume. There is Four icons "RCK, Android, USB, and Wipe Data. I have up graded to the JB OTA and I know it had been reset before I got it. Now if I am right has someone tried to root this tablet? I base that on the RCK icon which when selected just shows the android on his face with a red exclamation.
There is no text showing that the boot loader has been unlocked. So where do I go from here to unlock and root ?
That's the normal ASUS JB bootloader, if there isn't any text when turning the tablet on saying: "Device unlocked" it isn't. So if you want to unlock download the unlocking tool apk from ASUS website, install and run on your tablet. After unlocking just check the development section of the forums and get informed on how to install recovery (CWM or TWRP), root and custom ROMs.
Thanks
jgaf said:
That's the normal ASUS JB bootloader, if there isn't any text when turning the tablet on saying: "Device unlocked" it isn't. So if you want to unlock download the unlocking tool apk from ASUS website, install and run on your tablet. After unlocking just check the development section of the forums and get informed on how to install recovery (CWM or TWRP), root and custom ROMs.
Click to expand...
Click to collapse
Thanks for the quick reply. I would of been surprised if it had of been rooted and Amazon.com's techs hadn't of caught it when it was returned.
Going to hold off rooting it until the warrantee is gone. Still having nightmares about my Viewsonic gTablet turning into a cyborg tablet thingy and attacking me. All because I just had to try every ROM I could cram down it.
Although unlikely, it could still be rooted if it was done prior to the jb update, and it could still be locked even if rooted. Download root checker from the market and you can safely test this.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I just picked up the LTE from Best Buy and am clueless on setting it up. I read I should unlock the bootloader, however I read that it may already be done. How can I tell? I also read about rooting, but am unsure if I should wait on this. It is on 4.3 and I am not sure if I should update it now or do it after unlocking (if it isn't unlocked already) or rooting. Any other tips would be appreciated.
You're posting in the wrong forum.
But these are general questions, not device specific.
If you bought it brand new, the bootloader is definitely locked. You can tell because if it is unlocked, there will be an unlocked padlock on the Google boot screen.
To unlock you have to use fastboot. There is no reason to not update either before or after, it doesn't really matter.
My tip would be to READ. And when you have a question, read some more.
Basically to root, you'll run "fastboot oem unlock", flash a new recovery, and flash the SuperSU package. Stay away from "toolkits" and learn how to do it the proper way. This will save you a ton of headaches in the future, especially of you run in to problems because you'll already be familiar with or to use fastboot and stuff.
Look here: http://forum.xda-developers.com/showthread.php?t=2381698
Ultimate [VIDEO Guides] How To Root, Unlock Bootloader and More! New Nexus 7 (2013)
Sent from my Nexus 7 using Tapatalk
Was wondering if unlocking the bootloader and flashing the developer firmware voids the warranty on the shield android tv?
i dont think it does, as on nvidia website themselves state how do it...
I know everything is shown on their website, but nothing is specified in writing about the warranty end of it.
Asked nvidia about it and here is what I got told. http://nvidia.custhelp.com/app/answers/detail/a_id/3245
I'm making a barely educated guess here, but my understanding is that the 905V and 900V (Note 3) are very similar so it occurred to me to try the Note 3 bootloader unlock on the 905V after getting my hopes up regarding [ROM][P905][UNOFFICIAL] LineageOS 14.1 then installing TWRP on my rooted 905V running NK1/4.4.2 only to realize that the bootloader was locked and I couldn't run TWRP.
My CID did change and has stayed modified after using that tool and rebooting, but I still cannot run TWRP. This means that the CID change was good, but the bootloader is still locked right? Is this idea fundamentally flawed, or do we just need a different CID for the 905V and a modified "unlock_n3" could get the job done?
I'm reaching out to ryanbg and beaups to see if they can help or provide feedback.
rainabba said:
I'm making a barely educated guess here, but my understanding is that the 905V and 900V (Note 3) are very similar so it occurred to me to try the Note 3 bootloader unlock on the 905V after getting my hopes up regarding [ROM][P905][UNOFFICIAL] LineageOS 14.1 then installing TWRP on my rooted 905V running NK1/4.4.2 only to realize that the bootloader was locked and I couldn't run TWRP.
My CID did change and has stayed modified after using that tool and rebooting, but I still cannot run TWRP. This means that the CID change was good, but the bootloader is still locked right? Is this idea fundamentally flawed, or do we just need a different CID for the 905V and a modified "unlock_n3" could get the job done?
I'm reaching out to ryanbg and beaups to see if they can help or provide feedback.
Click to expand...
Click to collapse
That is specific for the N900V bootloader. It will not work with this device. You're lucky you didn't brick your tablet. The unlock doesn't work for this device.