Database Develop

[Q] s-off from recovery (TWRP, CWM)

My phone is stuck in RUU mode (HTC logo and 4 warning triangles).
I can get it to boot CWM or TWRP via fastboot boot. Problem is I'm S-ON with HTCDev unlock, and there's no RUU available for Bell Mobility.
Is there any way at all to get S-OFF directly from recovery? Like, run revone from adb in CWM recovery or something? Alternatively, is there any way to boot a full ROM using fastboot boot?

ergosteur said:
My phone is stuck in RUU mode (HTC logo and 4 warning triangles).
I can get it to boot CWM or TWRP via fastboot boot. Problem is I'm S-ON with HTCDev unlock, and there's no RUU available for Bell Mobility.
Is there any way at all to get S-OFF directly from recovery? Like, run revone from adb in CWM recovery or something? Alternatively, is there any way to boot a full ROM using fastboot boot?
Click to expand...
Click to collapse
Why your phone is stuck in ruu mode if there is no ruu for your phone?

alray said:
Why your phone is stuck in ruu mode if there is no ruu for your phone?
Click to expand...
Click to collapse
I restored it back to stock (or so I thought), but when I tried installing the 4.3 OTA the phone got stuck in bootloop and eventually just stuck in ruu.

ergosteur said:
My phone is stuck in RUU mode (HTC logo and 4 warning triangles).
I can get it to boot CWM or TWRP via fastboot boot. Problem is I'm S-ON with HTCDev unlock, and there's no RUU available for Bell Mobility.
Is there any way at all to get S-OFF directly from recovery? Like, run revone from adb in CWM recovery or something? Alternatively, is there any way to boot a full ROM using fastboot boot?
Click to expand...
Click to collapse
I come from China, I can solve your problem, you can contact QQ990128461, or email [email protected]

wudan120 said:
I come from China, I can solve your problem, you can contact QQ990128461, or email [email protected]
Click to expand...
Click to collapse
What's your problem? Just trolling around, or do you actually have something to contribute??
http://forum.xda-developers.com/showpost.php?p=51284986&postcount=3
http://forum.xda-developers.com/showpost.php?p=51285277&postcount=2
http://forum.xda-developers.com/showpost.php?p=51466900&postcount=7

OK, total stupid moment.
All I had to do was restore a stock nandroid for my CID (found on http://www.htc1guru.com/) using recovery booted via fastboot boot [cwm filename].img.
Then, run fastboot oem boot.
Found last command on: http://forum.xda-developers.com/showthread.php?t=1612969
Guess i got scared by the warning triangles. :victory:
Looks like the "modem" partition is still corrupted, so I have to run fastboot oem boot every time I boot the phone. But, now I should be able to boot a rom, get root, and s-off the regular way.
Also I actually was S-ON with a locked bootloader - managed to do the HTCdev unlock "blind" while in the ruu mode.

[Q] Q softbricked help please

hi i have done sum thing terrible to my phone and now i can only asses the boot loader cant get in to OS or recovery,
unable to flash new recovery and after trying to flash stock RUU i am stuck with boot loader relocked have tried to re unlock it but no luck.
s-on with os 7.19.401.2 any ideas on what to do?

Necrolog_92 said:
hi i have done sum thing terrible to my phone and now i can only asses the boot loader cant get in to OS or recovery,
unable to flash new recovery and after trying to flash stock RUU i am stuck with boot loader relocked have tried to re unlock it but no luck.
s-on with os 7.19.401.2 any ideas on what to do?
Click to expand...
Click to collapse
What steps did you take that led you to this point? Are you stock recovery at minute or are you custom recovery? Is your phone detected by fastboot (type fastboot devices)
Also I assume to tried HTC.com/dev to unlock using a different unlock token?

stovie_steve said:
What steps did you take that led you to this point? Are you stock recovery at minute or are you custom recovery? Is your phone detected by fastboot (type fastboot devices)
Also I assume to tried HTC.com/dev to unlock using a different unlock token?
Click to expand...
Click to collapse
just for future reference, he needs to flash the stock firmware, same one he already has, my suspicions say he has re-locked his bootloader with a custom recovery on there, thats why he cant unlock his bootloader, it requires stock recovery, the only way to get stock recovery on an s-on and re-locked device is to flash stock firmware. :good:

Seanie280672 said:
just for future reference, he needs to flash the stock firmware, same one he already has, my suspicions say he has re-locked his bootloader with a custom recovery on there, thats why he cant unlock his bootloader, it requires stock recovery, the only way to get stock recovery on an s-on and re-locked device is to flash stock firmware. :good:
Click to expand...
Click to collapse
Yeah I figured he'd done that, which is why I wondered was he custom recovery

thanks for the reply’s, i have now tried to use a new unlock token but i get the same problem as before, before i relocked the boot loader i flashed what i think was the stock recovery but now i can’t get in to recovery i can use fastboot and it does show up under fastboot devices and when i try to put the unlock token on i get the screen to confirm but when i confirm it boot into recovery and just stays there till the battery drains on i reboot it any more idea’s or advice ?

Help To Relock Moto X XT1052 Bootloader

Hey guys
I have a Moto X XT1052- The Indian Version.
I rooted my phone a few weeks back and I've decided that I don't want root access anymore.
I have unrooted my phone from the SuperSU app by clicking the clean up button.
Now I can't find anything as to how to relock the bootloader. I don't really need the warranty to be active again but if there is a way to do that it would be appreciated.
Also I need help to remove the bootloader unlocked warning message to be removed as well.
Please be clear in your explanations as I'm new to all this.
I have attached details about my phone to this post.
Thanks in advance

If you are already unrooted than there is no need to go further. The bootloader can be relocked with fastboot like you unlocked the bootloader but its getting back to the state relocked and not locked. That means your warranty's is still voided and the warning message keeps there. To remove the warning there was a tutorial here in the forum. Basically it's just changing the bootlogo.

bronko15344 said:
If you are already unrooted than there is no need to go further. The bootloader can be relocked with fastboot like you unlocked the bootloader but its getting back to the state relocked and not locked. That means your warranty's is still voided and the warning message keeps there. To remove the warning there was a tutorial here in the forum. Basically it's just changing the bootlogo.
Click to expand...
Click to collapse
It is possible to unroot from the SuperSU app isn't it? That's what I did.
But I want to relock the bootloader.
Does it erase data on the phone?
Will it lead to bricking or any other problems?
And could you explain the procedure in detail please?
And could you give me a link to the guide you mentioned?
Thanks

RohanAditya said:
It is possible to unroot from the SuperSU app isn't it? That's what I did.
But I want to relock the bootloader.
Does it erase data on the phone?
Will it lead to bricking or any other problems?
And could you explain the procedure in detail please?
And could you give me a link to the guide you mentioned?
Thanks
Click to expand...
Click to collapse
Relocking the bootloader will erase your data. There are serveral threads on XDA about it... here is one -> http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786 while it says VZW (Verizon Wireless) in the subject, the same steps and info apply to all 2013 Moto X's.
No it will not lead to bricking, as long as you are re-flashing the EXACT same rom that is on your phone, and your battery is 100% charged before starting. In other words,as always, if the battery goes dead during the process, there is a potential to brick, and DOWNGRADING your ROM is not good.
As for changing the logo.bin to remove the unlock warning... see -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961/post53098892 or see the LOGO.BIN info at -> http://mark.cdmaforums.com/MotoX-Bootlogo.htm
As @bronko15344 has already said, your bootloader status will change to "Relocked."
There are 3 states to the bootloader.
1. Locked Status Code 0 (as it ships from the factory)
2. Unlocked Status Code 3 (when the bootloader is unlocked)
3. Locked Status Code 2 (aka RELOCKED, after you use fastboot oem lock command)
If the status is Unlocked or Relocked (code 3 or 2), you'll get the unlocked bootloader warning at boot up. While you can replace the Logo.bin to hide or remove the message, any subsequent flash or ota that replaces logo.bin will cause the warning to return.
We do not have a way to toggle back to LOCKED Status Code: 0 as it came out of the box.
In other words, even relocking doesn't take you back to 100% completely stock.
Keep in mind, I have NOT tried flashing a custom logo.bin to remove the unlocked warning on a phone set as "Locked Status Code 2" (aka relocked). I don't know if you need to be Unlocked Status Code 3 to flash it.

KidJoe said:
Relocking the bootloader will erase your data. There are serveral threads on XDA about it... here is one -> http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786 while it says VZW (Verizon Wireless) in the subject, the same steps and info apply to all 2013 Moto X's.
No it will not lead to bricking, as long as your battery is 100% charged before starting. (in other words,as always, if the battery goes dead during the process, there is a potential to brick)
As for changing the logo.bin to remove the unlock warning... see -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961/post53098892 or see the LOGO.BIN info at -> http://mark.cdmaforums.com/MotoX-Bootlogo.htm
As @bronko15344 has already said, your bootloader status will change to "Relocked."
There are 3 states to the bootloader.
1. Locked Status Code 0 (as it ships from the factory)
2. Unlocked Status Code 3 (when the bootloader is unlocked)
3. Locked Status Code 2 (aka RELOCKED, after you use fastboot oem lock command)
If the status is Unlocked or Relocked (code 3 or 2), you'll get the unlocked bootloader warning at boot up. While you can replace the Logo.bin to hide or remove the message, any subsequent flash or ota that replaces logo.bin will cause the warning to return.
We do not have a way to toggle back to LOCKED Status Code: 0 as it came out of the box.
In other words, even relocking doesn't take you back to 100% completely stock.
Keep in mind, I have NOT tried flashing a custom logo.bin to remove the unlocked warning on a phone set as "Locked Status Code 2" (aka relocked). I don't know if you need to be Unlocked Status Code 3 to flash it.
Click to expand...
Click to collapse
Thank you so much

RohanAditya said:
It is possible to unroot from the SuperSU app isn't it? That's what I did.
But I want to relock the bootloader.
Does it erase data on the phone?
Will it lead to bricking or any other problems?
And could you explain the procedure in detail please?
And could you give me a link to the guide you mentioned?
Thanks
Click to expand...
Click to collapse
If you used the "Full Unroot" option in the app it should revert all changes which are made during the root process. To be sure that your system partition is completely stock you can flash it with fast boot (this won't delete your installed apps and data)
To do this look into this guide
guide-moto-x-return-to-100-stock
Short version:
1.
Download and extract the sbf flies matching your phone and carrier from here:
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
To decide which file you need to download:
info-tip-web-sites-official-leaked-roms
2. (this step is necessary to remove your warning message)
ghost-original-bootanimations-unlocked
download the standard boot animation and extract the logo.bin and overwrite the logo.bin from the sfb files.
3.
now flash the system partition, kernel, recovery and the new logo (without the warning) with the following commands: (Note: For flashing system.img you MUST use mfastboot instead of fastboot. It's to big for the normal fast boot. So no typo here)
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
Don't execute the following command as this will delete all your data/installed apps etc.
Code:
fastboot erase userdata
That should be sufficient to revert everything what was changed during the root process. Check if everything looks like it was was on stock rom (including the recovery and the bootlogo)
Now you can relock your boot loader using one of the these commands (I'm not sure which one it was but it should be the first one. If that is giving you a error than try the second one)
Code:
fastboot oem lock
fastboot oem relock
But actually I would not relock your boot loader since you gain nothing and if you want to unlock it again all your data will be erased during the unlock process. and since you are not rooted you can't backup everything before...
Edit: Like @KidJoe said. If you accepting an OTA than the warning comes back. so if you relock your bootloader you can't hide that message without unlocking (and loosing all your data) again. Just stay on the unlocked bootloader

bronko15344 said:
Now you can relock your boot loader using one of the these commands (I'm not sure which one it was but it should be the first one. If that is giving you a error than try the second one)
Code:
fastboot oem lock
fastboot oem relock
.
Click to expand...
Click to collapse
On the 2013 X, if you just do Fastboot OEM LOCK, it will prompt you with "ready to flash signed images."
The info in the thread I posted a link to are accurate. You must fastboot oem lock begin, flash full stock rom (using mfastboot), erase cache and user data, then fastboot oem lock.

KidJoe said:
On the 2013 X, if you just do Fastboot OEM LOCK, it will prompt you with "ready to flash signed images."
The info in the thread I posted a link to are accurate. You must fastboot oem lock begin, flash full stock rom (using mfastboot), erase cache and user data, then fastboot oem lock.
Click to expand...
Click to collapse
Oh wasn't aware that you directly have to flash a firmware to relock the bootloader. Thank you

hey how u do u unlock ur moto x t1052 .

Bootloader causing brick only when rebooting from b to a.

Can go to BL and "fastboot set_active a" then reboot to go from b to a. No problems switching a to b in TWRP or BL by set_active command. The real problem is that if I try to update and forget to go to BL I get bricked and have to run blankflash.bat.
Which takes me to a locked BL where I can't boot TWRP via fastboot...
I thought I got out the first time but I have not been able to recover without flashing stock which wipes or makes data partition unrecoverable.
Anyway... WTF did I do to BL to make it detect that it is locked when I have unlocked, and never relocked BL.
Any insight would be greatly appreciated, thanks.

What are you updating to? There was a run of 15.1 ROMs that would result in bricks. It's fixed now- so if you are trying to flash a really old rom, try flashing the latest.

Moto G6 Bricked NEED HELP!!!

ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
ibb.co/QmnK1cB)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks

pyschodelicbros said:
ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks
Click to expand...
Click to collapse
You should download the stock firmware from here and following this guide to restore to stock firmware. Even if the rest of the commands don't work, the first two should reset the bootloader and partition tables and make it bootable or maybe unlockable again. You can also maybe try to boot TWRP but I don't know if that'll work because the boorloader is acting odd

pyschodelicbros said:
ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks
Click to expand...
Click to collapse
You should be able to flash official firmware even if the bootloader is locked. Do you still have the original unlock key you received from Motorola to unlock the bootloader? You'll have to use that to re-unlock your bootloader.
Code:
fastboot oem unlock UNIQUE_KEY
Replace UNIQUE_KEY with the unlock key you received.
EDIT: It just occurred to me that "OEM unlocking" is probably toggled off since you re-locked the bootloader. That's why it says "feature disabled".
You could also try to restore stock firmware using Lenovo Moto Smart Assistant. It has a Rescue option that does that.
https://support.lenovo.com/us/en/downloads/ds101291

AgentICS said:
You should download the stock firmware from here and following this guide to restore to stock firmware. Even if the rest of the commands don't work, the first two should reset the bootloader and partition tables and make it bootable or maybe unlockable again. You can also maybe try to boot TWRP but I don't know if that'll work because the boorloader is acting odd
Click to expand...
Click to collapse
I heard that once u relock bootloader, your unlock feature gets disabled for a few days. Anyone know if that is true?

pyschodelicbros said:
I heard that once u relock bootloader, your unlock feature gets disabled for a few days. Anyone know if that is true?
Click to expand...
Click to collapse
I'm pretty sure it's because the bootloader can't contact the OS correctly and therefore can't validate the request

AgentICS said:
I'm pretty sure it's because the bootloader can't contact the OS correctly and therefore can't validate the request
Click to expand...
Click to collapse
mfastboot oem lock
mfastboot oem lock
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash boot boot.img
mfastboot oem lock
I did this to lock the bootloader, not knowing my OS wasnt installed properly so theres no OS and my bootloader is locked.
"fastboot oem unlock"
says bootloader feature disabled
Picture of my bootloader log
[Copy link and past without the )]
ibb.co/QmnK1cB)

Ragarianok said:
You should be able to flash official firmware even if the bootloader is locked. Do you still have the original unlock key you received from Motorola to unlock the bootloader? You'll have to use that to re-unlock your bootloader.
Code:
fastboot oem unlock UNIQUE_KEY
Replace UNIQUE_KEY with the unlock key you received.
EDIT: It just occurred to me that "OEM unlocking" is probably toggled off since you re-locked the bootloader. That's why it says "feature disabled".
You could also try to restore stock firmware using Lenovo Moto Smart Assistant. It has a Rescue option that does that.
https://support.lenovo.com/us/en/downloads/ds101291
Click to expand...
Click to collapse
Lenovo Moto Smart assistant says device isnt recognize, it might be USB debugging due to not being able to get into the OS.
I tried getting the unique key using "fastboot oem get_unlock_data" but i get this in my CMD
[Copy link and past without the )]
ibb.co/QHD0ZcS)
I do have my orginal unique key saved in a file from when i first unlocked my bootloader and when I tried to flash it I get bootloader feature disabled.
[Copy link and past without the )]
ibb.co/0MPsZrp)
I heard that the oem unlock gets disabled for 7 days after relocking wondering if that is true???