Is the bootloader unlocked on 7 Pro, non T Mobile out of the box, and is it easy to root?
It is unlockable with a simple fastboot command. Root is a mess as there are multiple versions of the phone and it is easy to flash the wrong boot image.
Sent from my GM1917 using Tapatalk
Related
Hello guys, I'm not a super noob but I can certainly use some advise and suggestions. I was trying to be all smart and try to put CM7 on my phone by rooting the nexus S without having to unlock the bootloader. I've read around and realized that I could do so if my phone is on 2.3.2 or 2.3.1.
So I search around and the following thread:
http://forum.xda-developers.com/showthread.php?t=947950
suggested using Odin to downgrade from 2.3.4 to 2.3.1. After doing the steps I realized that it also unlocked my bootloader. Now does anyone know if there is a way to relock my bootloader if I used the Odin?
I've done some reading and as far as I can tell you can relock your phone using the "fastboot oem relock". but this method only works if you originally used the "fastboot oem unlock" in the first place.
Any suggests?
hamidsani said:
Hello guys, I'm not a super noob but I can certainly use some advise and suggestions. I was trying to be all smart and try to put CM7 on my phone by rooting the nexus S without having to unlock the bootloader. I've read around and realized that I could do so if my phone is on 2.3.2 or 2.3.1.
So I search around and the following thread:
http://forum.xda-developers.com/showthread.php?t=947950
suggested using Odin to downgrade from 2.3.4 to 2.3.1. After doing the steps I realized that it also unlocked my bootloader. Now does anyone know if there is a way to relock my bootloader if I used the Odin?
I've done some reading and as far as I can tell you can relock your phone using the "fastboot oem relock". but this method only works if you originally used the "fastboot oem unlock" in the first place.
Any suggests?
Click to expand...
Click to collapse
The command is actually "fastbook oem lock" and I would think it would work now matter how the bootloader was unlocked. You should at least try it. You just have to make sure you have Android SDK installed and your device drivers installed.
fastboot oem unlock to unlock and wipe your phone, flash cwm recovery, flash cm7.
turn off phone, turn it back on to bootloader and do fastboot oem lock.
Done.
Other than removing the unlock icon from showing what is/are the added benefit(s) of relocking the phone? I am just curious as I unlocked my Nexus S by ADB using the fastboot oem unlock command. Thanks.
Sent from my Nexus S using Tapatalk
Hi there,
just got a One X and wanted to install a custom Rom. Did bootloader unlock and installed TWRP with Toolkit. As I'm on Windows 8 I couldn't do the root part, if I'm not mistaken this is not needed and the custom ROM will be rooted anyway..? So TWRP installed successfully and I cleaned Cache but it doesn't start when i select recovery in HBOOT it stucks at the green HTC logo.. Is there any advice? Thanks in advance..
Edit: also just noticed that you did not root. You really need to do that before trying to install a ROM. I know you unlocked the boot loader but rooting is still needed to access system files. With out that, it is pointless. Find a Linux or windows 7 mention.
Better yet just run a live USB within Linux. That should work. Ooh, I wonder can you boot using your phone since it can be considered a mass storage device....probably not. Sorry off topic.
My guess is that windows 8 probably isn't reading your phone correctly. But you said you unlocked the boot loader. Try to manually install twrp
Sent from my Carbon-ize Evita using xda-developers app
TacoLoco said:
Hi there,
just got a One X and wanted to install a custom Rom. Did bootloader unlock and installed TWRP with Toolkit. As I'm on Windows 8 I couldn't do the root part, if I'm not mistaken this is not needed and the custom ROM will be rooted anyway..? So TWRP installed successfully and I cleaned Cache but it doesn't start when i select recovery in HBOOT it stucks at the green HTC logo.. Is there any advice? Thanks in advance..
Click to expand...
Click to collapse
Just download the latest HTC sync from HTC website and it Will install drivers you need, you can then leave sync or uninstall it and drivers will remain.
Sent from my HTC One X using xda premium
How are you going to access twrp if you do not have root and super user?
Good luck with that.
Sent from my HTC One X using xda premium
If the bootloader is unlocked, there's no need to root. They are independent of each other.
Check md5 on your recovery file and reflash. Then do fastboot erase cache and try going to recovery.
Sent from my One X using xda app-developers app
I thought unlocking the BL and root was co-dependant. You can root but can't install ROMs until the BL is unlocked. Or you could unlock boot loader but can't touch system files until you gain root access.
Or did I miss understand? Which is why rooting alone nor unlocking the BL alone is not the only step in installing a ROM.
Sent from my Carbon-ize Evita using xda-developers app
Herc08 said:
I thought unlocking the BL and root was co-dependant. You can root but can't install ROMs until the BL is unlocked. Or you could unlock boot loader but can't touch system files until you gain root access.
Or did I miss understand? Which is why rooting alone nor unlocking the BL alone is not the only step in installing a ROM.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
I will explain further.
For ATT One XL root was needed prior to unlocking the bootloader to allow you to write to system files(which is no longer possible as of 3.18), and be able to change the CID in order to allow HTCDEV to provide the Unlock_code.bin to unlock your bootloader. This is probably where your confusion stems.
IF, like every other carrier, ATT allowed you to unlock the bootloader, you would not need to have rooted to be able to unlock your bootloader, you could have just unlocked it and then flashed TWRP. At that point you could flash a rooted rom or allow TWRP to root your rom for you. (For some rom versions, I believe anything under 3.18)
Hope this cleared some stuff up for you! :good:
Ah makes perfect since now. Darn AT&T and their lock downs.
So basically Rogers and Telstra can root just by unlocking and that's it. No exploit needed. And of course flashing twrp and a rom
Sent from my Carbon-ize Evita using xda-developers app
Herc08 said:
Ah makes perfect since now. Darn AT&T and their lock downs.
So basically Rogers and Telstra can root just by unlocking and that's it. No exploit needed.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
Correct!
Just bought a used One x At&t..I want to Root it but i dont know if its bootloader is locked or unlocked.It has got the Stock Rom & Stock recovery.
It says S-off in the bootloader menu..I want to Root it..Should i just go & Flash Custom recovery then go for the Rooting?
Well if you flash recovery and the bootloader is locked it will fail so there's not really any harm in trying.
Though it says In the bootloader if it's locked unlocked or relocked
Sent from my HTC One X using xda app-developers app
Bootloader is locked..Guess i have to unlock it first :crying:
Plug it in, fire up cmd prompt and type adb getvar cid
If it comes back as 11111111 simply unlock with htc dev, its super simple.
Then fastboot recovery.
You can always try the fastboot cmd
Fastboot oem unlock
Can't remember if that works or not lol. Probably not though just a thought since its already s-off
Since it is s-off you will ALWAYS be able to root very easily. :thumbup:
Sent from my HTC One X using Tapatalk 2
Sak3ater said:
Bootloader is locked..Guess i have to unlock it first :crying:
Click to expand...
Click to collapse
What's it matter if your phone has a tampered and unlocked tag?
Sent from my HTC One XL using xda app-developers app
I've just received an update to android 4.2.2 with Sense 5 on my rooted HTC One SV (Vodafone Spain), and I'm not able to perform. After rebooting appears fastboot :
****TAMPERED***
***RELOCKED***
*** Security Warning ***
K2_U PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40a.00.04
OpenDSP-v9.2.0268.1214
eMMV-boot
Mar 29 2013.20:55:40:20204
and the menu for bootloader.
What's wrong? Is there any way to solve?
Security warning? Were you by any chance S-Off with any custom kernel, boot.img, custom hboot.img, etc???
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 12:52 AM ---------- Previous post was at 12:49 AM ----------
You said CWM in your thread? Do you by any chance still have a custom recovery on your device?
I will have to look into this personally as I have never seen this 'security warning' before. I find it very interesting
Sent from my C525c using XDA Premium 4 mobile app
re
Sorry, previously i've tried to perform upgrade, but CWM gives me an error reffered to access file and can't mount device, so i tried to install a boot.img from a backup. Then, the problem I exposed.
Thanks for your attention.
You can't upgrade with cwm from an over the air update. You must have your stock recovery for it to work. You can't install a boot.img with S-On unless you flash it through fastboot command, and not with a custom recovery. You have to unlock your bootloader before you can do any of this. Then relock your bootloader after you flash your boot.img and stock recovery.img.
Sent from my C525c using XDA Premium 4 mobile app
re
Modding.MyMind said:
You can't upgrade with cwm from an over the air update. You must have your stock recovery for it to work. You can't install a boot.img with S-On unless you flash it through fastboot command, and not with a custom recovery. You have to unlock your bootloader before you can do any of this. Then relock your bootloader after you flash your boot.img and stock recovery.img.
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's the question, I flashed boot.img and recovery img (from a backup) using fastboot command.
And there's more: I see the red text in bootloader after apply the OTA, so applied the info on "[MOD][4.1.2] Remove Red Text in HBoot/Bootloader (for k2u & k2ul) - S-Off only!" http://forum.xda-developers.com/showthread.php?t=2289357 with the same result as taking an aspirine. Then the same with
TUTORIAL: Remove *TAMPERED* & *RELOCKED* flag / HBoot w/o unlock_code.bin http://forum.xda-developers.com/showthread.php?t=2541843 . Guess the result??
yes, the same: none. I'm getting amused trying to get my phone having 4.2.2 and sense 5 from 4.1.2 and 4+, but I will not having a brick (nice brick anyway, but useless).
Ahhh, I forget to tell you, after applying remove tampered, and rebooting to fastboot, the warning has dissapeared, but tampered and relocked remains. Is not funny ?
As you can guess, I'm not a guru in this matter. I wish it were MS-DOS , then there will be a chance.
You CANNOT FLASH A CUSTOM HBOOT while you are S-On and with a locked bootloader. My tutorial which you posted requires that you are S-OFF which you are not. You are currently S-On. Had you read my instructions in that tutorial you would had seen that.
In addition, you currently have a CUSTOM recovery on your device with a LOCKED bootloader which was a huge mistake.
You HAVE to unlock your bootloader to fix your problems. Once you unlock your bootloader you will be fine. YOU CANNOT FLASH ANYTHING IF YOUR BOOTLOADER IS LOCKED.
1.) Unlock your bootloader with your unlock_code.bin file, then restore your phone with your backup. If you do not have your PERSONAL unlock_code.bin file then you need to head over to HTCDEV.com and follow their guide to receiving one which will be sent via email to you.
2.) Insure you do not have a custom hboot, custom boot, custom kernel, custom recovery installed on your device - if you do then RESTORE them with your stock IMG's.
3.) After you have unlocked your bootloader, restored your device with your backup, and insured you have no custom .imgs on your device...... THEN, AND ONLY THEN, will you relock your bootloader. After which you will be able to upgrade your phone.
Sent from my C525c using XDA Premium 4 mobile app
Modding.MyMind said:
You CANNOT FLASH A CUSTOM HBOOT while you are S-On and with a locked bootloader. My tutorial which you posted requires that you are S-OFF which you are not. You are currently S-On. Had you read my instructions in that tutorial you would had seen that.
In addition, you currently have a CUSTOM recovery on your device with a LOCKED bootloader which was a huge mistake.
You HAVE to unlock your bootloader to fix your problems. Once you unlock your bootloader you will be fine. YOU CANNOT FLASH ANYTHING IF YOUR BOOTLOADER IS LOCKED.
1.) Unlock your bootloader with your unlock_code.bin file, then restore your phone with your backup. If you do not have your PERSONAL unlock_code.bin file then you need to head over to HTCDEV.com and follow their guide to receiving one which will be sent via email to you.
2.) Insure you do not have a custom hboot, custom boot, custom kernel, custom recovery installed on your device - if you do then RESTORE them with your stock IMG's.
3.) After you have unlocked your bootloader, restored your device with your backup, and insured you have no custom .imgs on your device...... THEN, AND ONLY THEN, will you relock your bootloader. After which you will be able to upgrade your phone.
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's a help
. No problem with 1 and 3, but 2... I think it will be a little difficult. I've just no idea how to do this, specially how and where to get stock images.
You don't have any idea about how much patient and helpfull you are. Thanks very very much
Pull the boot.img from your backup and copy it to your computer. Insure you name it boot.img.
Now go I into CWM and restore your device with your backup.
Now go into fastboot so you can flash your boot.img
fastboot flash boot boot.img
Now go into your recovery to confirm if it is stocked or custom. If shown a black screen with triangle then you are back to stock recovery. Otherwise it will still be CWM. If still CWM you will need to go to the link I will be providing in the below post and find a recovery.img suited for your device and flash it just like I told you to do with your boot.img
fastboot flash recovery recovery.img
At this point, I can only HOPE you do not have a CUSTOM HBOOT on your device but from the sounds of it you do not since you attempted that with a LOCKED bootloader which ultimately failed during its process.
So with that said, go ahead and relock your bootloader.
fastboot oem lock
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 10:39 AM ---------- Previous post was at 10:34 AM ----------
http://forum.xda-developers.com/showthread.php?t=2317379
Sent from my C525c using XDA Premium 4 mobile app
Let's have some fun:
I did everything as you told me, everything. So assume there's a stock boot and a stock recovery. Also CWM dissapeared from recovery.
entering in fastboot after reboot I get the same message except ****security warning*****.
including S-ON !!!
Well, at this point, using again fastboot oem lock, the future brick says "device was already locked".
Is it not fun?.
Awesome, I'm really having fun while learning. I hope not to annoy you, in that case I promise to be more serious an read much much posts here and other forums before have any question.
I know it would be silly, but will try to install by itself the OTA. I find it could be interesting to see what will happend
I'll tell you
Ohhhh! , at this moment it seems to work, thanks .
If is there any thing I could do for you, tell me please, need some file from the ota or backup??
just tell me.
Is it possible to relock the bootloader on this device?
The usual "fastboot oem lock" command does not work. I want relock for recevice OTA message update of kitkat.
Thanks
You can't relock the BL once its been unlocked. Having an unlocked boot loader won't prevent you from taking OTAs as long as you are running 100% unrooted stock with stock recovery
Sent from my XT925 using XDA Premium 4 mobile app
saloums7 said:
You can't relock the BL once its been unlocked. Having an unlocked boot loader won't prevent you from taking OTAs as long as you are running 100% unrooted stock with stock recovery
Sent from my XT925 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The motorola site says otherwise: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/91987/p/1449,8620 only that i don't find anything about my phone.
mitsus said:
The motorola site says otherwise: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/91987/p/1449,8620 only that i don't find anything about my phone.
Click to expand...
Click to collapse
The only devices for which you can relock the bootloader are the ones on this page : https://motorola-global-portal.custhelp.com/app/standalone/rom-images
As far as OTAs are concerned it has already been discussed back when JB 4.1.2 was getting released with the whole Rogers fastboot image vs official OTA. You will get OTA even if bootloader is unlocked.