|
||||
Re: Root 3D with new bootloader 1.5?
They may be able to, but is there any reason when a working solution already exists? I wonder how much time they would devote to something that is already 'solved' by HTC. You may not be able to flash things like people always have and have assumed it the 'only/correct' way, but you can end up with the same result of a custom ROM/kernel. About the only thing I haven't seen done is downgrading HBOOT (which doesn't really do much other than a few extra adb commands using the engineering HBOOT).
__________________
|
|
||||
Re: Root 3D with new bootloader 1.5?
What is the important reason to have s-off?
__________________
HTC Evo LTE > (Dell x51v → Motorola Q (Verizon) → Mogul → 800w → Treo Pro → Touch Pro 2 → EVO 3D (SERO) ) > iPhone 5
|
|
||||
Re: Root 3D with new bootloader 1.5?
From what I understand s-off (standing for security-off from what Karl told me) allows people to flash custom kernals.
Correct me if Im wrong, Im still trying to figure this all out. |
|
||||
Re: Root 3D with new bootloader 1.5?
Oh I see. Is kernal the same as ROM?
I remember kernal is something inside the corn from some computer science class. |
|
||||
Re: Root 3D with new bootloader 1.5?
Quote:
The kernal on the other hand, from what I can understand, is a linux based script that act like a decision maker between the user and the hardwear The kernal tells the ROM what componants are available for use and tells the ROM how fast to run, what to prioritize and what to exclude ect. Pretty much, (from my understanding) when you tell the phone to do something, the ROM submits a request to the kernal, and then the kernal replies by telling the hardwear how to go about your request Some kernals make the phone faster and more powerful. Thats why having s-off is somewhat of a big deal cause the kernal can drasticly improove the performance of the ROM Last edited by aedon; 10-30-2011 at 11:24 PM. |
|
||||
Quote:
Evo 3D on Tapatalk |
|
||||
Re: Root 3D with new bootloader 1.5?
C:\rootevo3dnew>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.152s] writing 'unlocktoken'... (bootloader) unlock token check successfully OKAY [ 0.006s] finished. total time: 0.158s This is what I am getting when I get to loading the Unlock bin. I have everything needed to be installed. This is not my phone, its a friends and it had been updated so IDK if the new OTA had blocked this method right now. Im at a loss for whats going on. Im in Fastboot USB and get to push this but thats it, no unlock screen like in the video. Checking the file its 256 bytes so IDK why its showing (0 kb) pushed. HBoot is still 1.50.000 and LOCKED. Any suggestions?? |
|
|
|