I have installed CM12 on ONEPLUS. but i need to lock my bootloader so that my office email app wont work otherwise.
Can anyone tel me the process to re-lock bootloader in any custom rom. Or should I go back to Stock only
Yes its the same way you unlocked it. But instead of "fastboot oem unlock" you need to use "fastboot oem lock"
You need to be on stock rom and kernel for this be carefull!!!!
---------- Post added at 10:48 PM ---------- Previous post was at 10:26 PM ----------
If you need a guide to go back to stock use this link http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Thanks to timmaaa for the guide.
nosmas16 said:
I have installed CM12 on ONEPLUS. but i need to lock my bootloader so that my office email app wont work otherwise.
Can anyone tel me the process to re-lock bootloader in any custom rom. Or should I go back to Stock only
Click to expand...
Click to collapse
Be careful relocking your bootloader!
I read someone relocked it and was then unable to unlock it!
Read up on that
royalbluecheese said:
Yes its the same way you unlocked it. But instead of "fastboot oem unlock" you need to use "fastboot oem lock"
You need to be on stock rom and kernel for this be carefull!!!!
---------- Post added at 10:48 PM ---------- Previous post was at 10:26 PM ----------
If you need a guide to go back to stock use this link http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Thanks to timmaaa for the guide.
Click to expand...
Click to collapse
You don't need to be in stock ROM/kernel to lock the bootloader, you can do it at any time with any firmware installed.
Transmitted via Bacon
---------- Post added at 01:54 PM ---------- Previous post was at 01:52 PM ----------
nosmas16 said:
I have installed CM12 on ONEPLUS. but i need to lock my bootloader so that my office email app wont work otherwise.
Can anyone tel me the process to re-lock bootloader in any custom rom. Or should I go back to Stock only
Click to expand...
Click to collapse
Locking your bootloader is similar to unlocking it but the command is a little different.
Code:
fastboot oem lock
But be wary of this because some people have had major issues unlocking it again after locking it. Anyway, how do you know that it's your unlocked bootloader that's causing the problems with your bootloader?
Transmitted via Bacon
Oops didn't knew that, thanks for correcting me.
timmaaa said:
You don't need to be in stock ROM/kernel to lock the bootloader, you can do it at any time with any firmware installed.
Transmitted via Bacon
---------- Post added at 01:54 PM ---------- Previous post was at 01:52 PM ----------
Locking your bootloader is similar to unlocking it but the command is a little different.
Code:
fastboot oem lock
But be wary of this because some people have had major issues unlocking it again after locking it. Anyway, how do you know that it's your unlocked bootloader that's causing the problems with your bootloader?
Transmitted via Bacon
Click to expand...
Click to collapse
My email app gives me a error msg that "Due to security issues it cannot run on a unlocked bootloader".
Thanks for your quick response.
So Should I go ahead and lock my bootloader though I am not in stock rom. Or should I not. Please advice
waterdaan said:
Be careful relocking your bootloader!
I read someone relocked it and was then unable to unlock it!
Read up on that
Click to expand...
Click to collapse
Is there a safe way to relock the bootloader though I am not in the stock rom/kernel.
nosmas16 said:
My email app gives me a error msg that "Due to security issues it cannot run on a unlocked bootloader".
Thanks for your quick response.
So Should I go ahead and lock my bootloader though I am not in stock rom. Or should I not. Please advice
Click to expand...
Click to collapse
As I said earlier, it doesn't matter what ROM you're on, you can lock your bootloader on any ROM.
Transmitted via Bacon
Related
Gone fishing...
Awesome!
Sent from my HTC Sensation 4G using xda premium
Well with the new announcement, I guess I posted these at just the right time...
Do you really have to sign up to download the file???
el7145 said:
Do you really have to sign up to download the file???
Click to expand...
Click to collapse
I see that... I'll re-host on dropbox and update the links tonight.
So...downloading the zip and flashing thru the bootloader should get me back to a stock tmobile gingerbread rom? thanks for the clarification.
I'm on inquisition with 3.32 firmware and really need my wifi calling back.
thanks!
GROGG88 said:
I see that... I'll re-host on dropbox and update the links tonight.
Click to expand...
Click to collapse
Alright bro, thanks, much appreciated
do i need s-off i have it htcdev unlocked
---------- Post added at 05:55 PM ---------- Previous post was at 05:54 PM ----------
but its bricked during juopunut bear process and can only go to recovery and bootloader and when i try to flash stock rom and boot.img (seprately) it doesnt go through
At GROGG88 great idea, with the stupid file sharing situation like it is, it is definitely good to have other places to get files like this. I currently have to go fix my link to the Google Drivers in the HD2 NAND toolkit thread in the HD2 NAND Android forum as I just found out that I get the dreaded FBI Anti-Piracy Warning message when you click on it.
hd2Raz said:
So...downloading the zip and flashing thru the bootloader should get me back to a stock tmobile gingerbread rom? thanks for the clarification.
I'm on inquisition with 3.32 firmware and really need my wifi calling back.
thanks!
Click to expand...
Click to collapse
jett1217 said:
do i need s-off i have it htcdev unlocked
---------- Post added at 05:55 PM ---------- Previous post was at 05:54 PM ----------
but its bricked during juopunut bear process and can only go to recovery and bootloader and when i try to flash stock rom and boot.img (seprately) it doesnt go through
Click to expand...
Click to collapse
GROGG88 said:
I will not provide support for these files since they are stock firmware/software. As with anything on the XDA, these files are for use at your own risk!! I assume no liability from any issues you may cause on your device by the use of these files!
Click to expand...
Click to collapse
Both files have been uploaded to my dropbox. Links in the OP have been updated...
jett1217 said:
do i need s-off i have it htcdev unlocked
---------- Post added at 05:55 PM ---------- Previous post was at 05:54 PM ----------
but its bricked during juopunut bear process and can only go to recovery and bootloader and when i try to flash stock rom and boot.img (seprately) it doesnt go through
Click to expand...
Click to collapse
Just boot into Hboot and then run the RUU as administrator. If you want to flash it via recovery you will have to re flash the stock recovery via ADB fastboot commands. Then you can flash it with recovery.
If you would like your apps to auto Install I would suggest downloading the Google Play Store apk and put it on your SD Card and install after you setup your google account before you agree to the teams of Service in the outdated android market
So this will automatically flash the right firmware and everything and not lose S-Off correct?
djdant said:
So this will automatically flash the right firmware and everything and not lose S-Off correct?
Click to expand...
Click to collapse
Yes. It will return the device to a out of the box state...
GROGG88 said:
Yes. It will return the device to a out of the box state...
Click to expand...
Click to collapse
Ok thanks bro, I just changed my CID back to t-mobile was that needed? Also could I still root or do I need to stay stock in order to get the OTA?
djdant said:
Ok thanks bro, I just changed my CID back to t-mobile was that needed? Also could I still root or do I need to stay stock in order to get the OTA?
Click to expand...
Click to collapse
Keep T-MOB010 cid...
Conflicting reports as to whether or not you can use the OTA with root. If it fails then delete /system/superuser.apk and /system/bin/su
I have not tried running an OTA with root so I cannot say for certain if it will fail.
Either way, you'll need to reinstall a custom recovery and either superuser or supersu after the update.
So exactly how do we do this lol ...Im S-Off with SuperCID and running 3.32 FW and ICS rom I have DL'ed both files and all I want is to be able to OTA when it comes ?
Guides can be found... HERE
GROGG88 said:
I will not provide support for these files since they are stock firmware/software. As with anything on the XDA, these files are for use at your own risk!! I assume no liability from any issues you may cause on your device by the use of these files!
Click to expand...
Click to collapse
Im flashing the RUU now and seems to be fine now the final step is changing the CID back to TMOB US how do you do that from stock
So has anyone managed to use the changed cid after updating to the new 1.85 to re unlock the downloader?
I'm still showing 1111111 cid, but neither the old unlock token, or even new ones will unlock the darn downloader.
I think I saw someone say they managed it, but cant find the post.
Sent from my HTC One X using xda premium
I have root and unlock bl on 1.85.
I finally got it to work! I had to manually RELOCK the 1.85 bootloader (even though it said it was relocked already). Then hit the unlock again. Bam. Thank goodness!
So you re-locked, flashed 1.85, manually re-locked again, and then unlocked?
How did you achieve root? Just by flashing the recovery and SuperSU?
Yes to all. Now im trying to find the right supersu zip to use in rec.
gtkansan said:
Yes to all. Now im trying to find the right supersu zip to use in rec.
Click to expand...
Click to collapse
it's in the thread on the development forum. its the root 1.85 one that only has like 3 posts
http://forum.xda-developers.com/showthread.php?t=1673935
Fantastic. Thank you! Worked and Im finally back up!
After doing the following steps, I had to manually install Busybox from the market.
so if im on rooted 1.73, i can run supercid, run thru htcdev to unlock, manually relock, ruu 1.85, manually relock, unlock thru htcdev, and then can flash CWM & install SuperSU for root?
malox23 said:
so if im on rooted 1.73, i can run supercid, run thru htcdev to unlock, manually relock, ruu 1.85, manually relock, unlock thru htcdev, and then can flash CWM & install SuperSU for root?
Click to expand...
Click to collapse
seems to be correct. Thats exactly what I'm doing/about to do
SkizzMcNizz said:
seems to be correct. Thats exactly what I'm doing/about to do
Click to expand...
Click to collapse
cool, let me know how it goes...i just reg'd at htcdev.
gtkansan said:
Fantastic. Thank you! Worked and Im finally back up!
Click to expand...
Click to collapse
when you say you manually re-locked what do you mean? When I try to re-lock it says already relocked.
---------- Post added at 03:32 AM ---------- Previous post was at 03:28 AM ----------
I can't get it to take. It always still says relocked.
SkizzMcNizz said:
when you say you manually re-locked what do you mean? When I try to re-lock it says already relocked.
---------- Post added at 03:32 AM ---------- Previous post was at 03:28 AM ----------
I can't get it to take. It always still says relocked.
Click to expand...
Click to collapse
Just keep on trying, it took me at least 50 tries to get mine unlocked again.
Sent from my HTC One X using xda premium
i'm on JB (saturn III) hboot 2.0 with superCID/s-off. i can downgrade to hboot 1.0 but i can not change my CID to flash ICS RUU (error 130 with superCID )
first...when i enter code
Code:
adb shell
(device not found)
what shoud i do ?
and there's a issue with my ussd code, it's chinese... i've tried wipe and flash other roms but it's still there
i think if i could flash ICS RUU then the problem will be solved
sorry if my questions are stupid because i'm a newbie
thanks!
rJiLz said:
My cid is supercid!
Click to expand...
Click to collapse
do you already have superCID or not, your post are becoming confusing.
please post your whole CID#
your whole bootloader#
what you're romver#
we need solid information to further help/guide/assist you.
please help me help you
russellvone said:
do you already have superCID or not, your post are becoming confusing.
please post your whole CID#
your whole bootloader#
what you're romver#
we need solid information to further help/guide/assist you.
please help me help you
Click to expand...
Click to collapse
+1
Lol, just now i wanted to post the same.
rJiLz said:
i'm on JB (saturn III) hboot 2.0 with superCID/s-off. i can downgrade to hboot 1.0 but i can not change my CID to flash ICS RUU (error 130 with superCID )
first...when i enter code
Code:
adb shell
(device not found)
what shoud i do ?
and there's a issue with my ussd code, it's chinese... i've tried wipe and flash other roms but it's still there
i think if i could flash ICS RUU then the problem will be solved
sorry if my questions are stupid because i'm a newbie
thanks!
Click to expand...
Click to collapse
#1 did you facepalm s-off or moonshine s-off?
#2 what is your CID?
#3 what ROM are you currently running?
#4 is adb enabled?
#5 do you have YOUR phone's stock boot.img and recovery.img available for flashing when needed?
#6 what/which RUU file are you attempting to use?
#7 is your bootloader still unlocked, or is it relocked?
---------- Post added at 02:25 AM ---------- Previous post was at 02:21 AM ----------
@rJiLz
did you log off?
It's magic, but there are no problems with ussd in CM alfa room.
Flshing stock room will slove the problem too.....
I said :
I'm on JB ( saturn III) , S-OFF, UNLOCKED, MY CID: 11111111,MY HBOOT:1.0... ICS RUU K2_UL
Please help me
russellvone said:
#1 did you facepalm s-off or moonshine s-off?
#2 what is your CID?
#3 what ROM are you currently running?
#4 is adb enabled?
#5 do you have YOUR phone's stock boot.img and recovery.img available for flashing when needed?
#6 what/which RUU file are you attempting to use?
#7 is your bootloader still unlocked, or is it relocked?
---------- Post added at 02:25 AM ---------- Previous post was at 02:21 AM ----------
@rJiLz
did you log off?
Click to expand...
Click to collapse
Sorry for my bad English.
1. FACEPALM S-OFF
2. SUPERCID
3. SATURN III
4. ADB - ENABLED
5. YES, I DO
6. ICS RUU FOR K2_UL
7. UNLOCKED
rJiLz said:
Sorry for my bad English.
1. FACEPALM S-OFF
2. SUPERCID
3. SATURN III
4. ADB - ENABLED
5. YES, I DO
6. ICS RUU FOR K2_UL
7. UNLOCKED
Click to expand...
Click to collapse
You say, adb - enabled.
But the message
adb shell (device not found)
seems to say something else.
Also i said, you should try the ruu with relocked bootloader.
old.splatterhand said:
You say, adb - enabled.
But the message
adb shell (device not found)
seems to say something else.
Also i said, you should try the ruu with relocked bootloader.
Click to expand...
Click to collapse
Relocked bootloader to flash ruu but error 130 with supercid
Adb works well when i relock and unlock but enter "adb shell" - device not found
ok, so you've already accomplished superCID.
and you are wanting to change your CID back to stock CID because the ICS RUU you are trying you use gives error.
but....when bootloader is unlocked you cannot use adb shell?----(no device found)
but when your bootloader is relocked you can use adb?
so just keep your bootloader locked and run the adb shell as root
adb shell
su
? Maybe this will work?
---------- Post added at 01:48 PM ---------- Previous post was at 01:45 PM ----------
rJiLz said:
Relocked bootloader to flash ruu but error 130 with supercid
Adb works well when i relock and unlock but enter "adb shell" - device not found
Click to expand...
Click to collapse
fastboot is used to lock and unlock
?
russellvone said:
ok, so you've already accomplished superCID.
and you are wanting to change your CID back to stock CID because the ICS RUU you are trying you use gives error.
but....when bootloader is unlocked you cannot use adb shell?----(no device found)
but when your bootloader is relocked you can use adb?
so just keep your bootloader locked and run the adb shell as root
adb shell
su
? Maybe this will work?
---------- Post added at 01:48 PM ---------- Previous post was at 01:45 PM ----------
fastboot is used to lock and unlock
?
Click to expand...
Click to collapse
when i relock bootloader and enter "adb shell" - still there (device not found)
now i can not change my cid (from supercid to HTC__032) to flash ICS RUU
I'd like to give you some other things to try but I'm afraid that my actual experience vs what I've read are too far apart from each other.
try googling flash RUU with fastboot.
:thumbup:
russellvone said:
I'd like to give you some other things to try but I'm afraid that my actual experience vs what I've read are too far apart from each other.
try googling flash RUU with fastboot.
:thumbup:
Click to expand...
Click to collapse
now i have a real question:
what is the easiest way to change the cid (to flash ICS RUU without error 130) ?
currently: i've got a k2_ul on JB - Hboot 1.0 - unlocked - superCID - S-off
@rJiLz
superCID should not be an issue. I think it's your Hboot.
you keep posting you have Hboot 1.0
what is the rest of your Hboot#
---------- Post added at 10:09 PM ---------- Previous post was at 10:01 PM ----------
http://forum.xda-developers.com/showthread.php?t=2251800
check this thread out
---------- Post added at 10:35 PM ---------- Previous post was at 10:09 PM ----------
I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE
I am trying to help
so.... that thread summed up
#1 relock your bootloader
Code:
fastboot oem lock
plug phone into computer and run RUU
a do NOT continue with the RUU, but look in your %temp% folder/directory for the rom.zip
#2 place the rom.zip into your fastboot directory
#3 verify connectivity with
Code:
fastboot devices
#4 send cmd
Code:
fastboot oem rebootRUU
#4a pause *** Wait readiness HTC * **
#5 send cmd
Code:
fastboot flash zip rom.zip
#5a If you get the message: FAILED (Remote: 90 hboot pre-update! please flush image again immediately) It's okay. In this situation it is necessary to re-issue the command
Code:
fastboot flash zip rom.zip
#6 send cmd
Code:
fastboot reboot
---------- Post added at 10:45 PM ---------- Previous post was at 10:35 PM ----------
and I think your adb issue with no devices found might have something to do with you trying to run the RUU.
it might have disabled adb. you could try right clicking on the fastboot/adb folding and clicking on "RUN AS ADMINISTRATOR"
maybe that will help with changing CID..... even though superCID is universal.......
just a couple more thoughts
My Hboot info:
TAMPERED
UNLOCKED
K2_UL PUT SHIP S-OFF RL
CID-11111111
HBOOT-1.01.0000
RADIO-0.11.40g.00.15
OPENDSP-v62.0221.1112
eMMC-boot
Dec 7 2012,03:10:20-1
now i'm busy...i will try again later
@rJiLz
any luck?
russellvone said:
@rJiLz
any luck?
Click to expand...
Click to collapse
Thank you very very much but i'm far away from home now. I will report later
to be continued.....
lol
:beer:
russellvone said:
to be continued.....
lol
:beer:
Click to expand...
Click to collapse
Code:
fastboot flash zip rom.zip
so sad, checking model id (failed)
so, what condition is your phone at now?
---------- Post added at 10:05 PM ---------- Previous post was at 09:58 PM ----------
http://forum.xda-developers.com/showthread.php?t=1275632
[TROUBLESHOOTING]/!\ Root | S-OFF | Flashing | RUU | Bootloop | Brick | Resources /!\
this guide says to make a goldcard
I saw a link on motorola site that if you have unlocked your bootloader then click here to return to original state... Does this mean that will I regain my warranty by doing this? Please help me as its my first moto device but I'm pretty familiar with custom roms and unlocking and all the stuff..
Thanx in advance... I'm attaching screenshot of that link from motorola site
That means return to completely stock rom if you have rooted your phone or installed custom roms.
You cannot regain your warranty after you loose it.
And once you unlock your bootloader you don't need to relock it to be able to receive ota update.
All you have to do is flashing a stock firmware then you will be able to receive official update.
I don't think it's possible to re-lock the bootloader on this device.
You can relock but it won't change the status to official.
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
You can relock it but it will not change the status to official.
Just wondering whether the unlocked bootloader warning vanishes after relocking bootloader with code fastboot OEM LOCK
No the message does not go away.
therealduff1 said:
No the message does not go away.
Click to expand...
Click to collapse
Any way to get rid of it while relocked?
Yousvel said:
Any way to get rid of it while relocked?
Click to expand...
Click to collapse
You can flash one of the bootloader unlock fixes that have been posted. You'll have to boot to TWRP to flash them. Your bootloader will always show unlocked AFA Motorola is concerned. All you can do is remove that nag screen.
http://forum.xda-developers.com/showthread.php?t=3294590
Please follow my Thread.. You will be solved.. Just use that logo.bin file for flashing in boatloader via 'fastboot flash logo logo.bin' without quotes.. Done..
Sent from my Moto G(Osprey)
---------- Post added at 09:00 PM ---------- Previous post was at 09:00 PM ----------
File is in the zip..
Sent from my Moto G(Osprey)
Remember that doing this will have no effect on your warranty, Motorola doesn't care what your phone shows, they don't even care if you actually unlock it, once you accept the T&C and get the unlock token, even if you never use it, your warranty is voided.
What I am saying is the screen is purely cosmetic, nothing else.