Database Develop

[Q] Help Unlocked Bootloader Message

Someone have the logo_signed for Retail EU JB? I just want it to quit this message "Warning Unlocked"
Thanks in advance...

AW: [Q] Help Unlocked Bootloader Message
There's no logo.bmp for jb. We have to life with it. Moto isn't stupid > They upgraded the secure Level of the unlocked Logo and doesn't give us the ability to change it anymore.
Sent from my XT890

HSD-Pilot said:
There's no logo.bmp for jb. We have to life with it. Moto isn't stupid > They upgraded the secure Level of the unlocked Logo and doesn't give us the ability to change it anymore.
Sent from my XT890
Click to expand...
Click to collapse
Yup
Only thing I can think of is downgrading the boot loader... But Motorola stated the radio and boot loader cannot be flashed away from the current required signature, this would include secure version checks I'd assume. Which explains why people bricked trying to RSD back to ICS after doing the full ota update.
Sent from my Galaxy Nexus using Tapatalk 2

So.. I have to live with this horrible message? its sad...

AW: [Q] Help Unlocked Bootloader Message
We can downgrade with RSD if the Bootloader is unlocked. But we have to delete the line gpt.bin and motoboot.
I had to do it by myself today, because my i won't boot into the System or recovery anymore. I tried some stuff today. Switching between the full OTA's.
I was able to switch from EU JB OTA to O2 JB with the Homemades. But after i tried to revert back to EU JB with the same method the OTA aborted by setting simlinks and permissions. No Recovery was working (CWM or Stock) and it stucked @ the warning Logo.
RSD saved my ass and i did an Backup of my Retail EU JB before i started to mess around. So i'm back on track :thumbup:
Sent from my XT890

HSD-Pilot said:
We can downgrade with RSD if the Bootloader is unlocked. But we have to delete the line gpt.bin and motoboot.
I had to do it by myself today, because my i won't boot into the System or recovery anymore. I tried some stuff today. Switching between the full OTA's.
I was able to switch from EU JB OTA to O2 JB with the Homemades. But after i tried to revert back to EU JB with the same method the OTA aborted by setting simlinks and permissions. No Recovery was working (CWM or Stock) and it stucked @ the warning Logo.
RSD saved my ass and i did an Backup of my Retail EU JB before i started to mess around. So i'm back on track :thumbup:
Sent from my XT890
Click to expand...
Click to collapse
do i have to downgrade to ICS and quit this message?

Don't know how exactly but i'm bootloader unlocked and currently running the EU jelly bean (installed via the homemade fastboot) and I don't have the warning message.

crunchie-uk said:
Don't know how exactly but i'm bootloader unlocked and currently running the EU jelly bean (installed via the homemade fastboot) and I don't have the warning message.
Click to expand...
Click to collapse
>installed via the homemade fastboot
There ya go.
Sent from my Galaxy Nexus using Tapatalk 2

mattlgroff said:
>installed via the homemade fastboot
There ya go.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So, with JB, who used homemade fastboot AND DON'T USED OTA (capital to alert others), can still change the logo the same way?

diogo.sena said:
So, with JB, who used homemade fastboot AND DON'T USED OTA (capital to alert others), can still change the logo the same way?
Click to expand...
Click to collapse
Homemade doesn't increase the secure version or use partition tables that the ota update does.
Sent from my Galaxy Nexus using Tapatalk 2

M logo on JB
mattlgroff said:
Homemade doesn't increase the secure version or use partition tables that the ota update does.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So Matt there's no way to change the logo on devices unlocked with OTA JB Retail.EU that have the Unlock Warning Message?
It shows that message coming from a particular sector of the kernel? The BMP code is embedded?
Thx in advance

[Q] questions about ...unlock bootloader, root, update rom

hello, I am a software developer but not Android, I'm sorry I can not give no contribution for now. I have a razr_i (Retail GB) with stock ICS 4.0.4 and I'm pretty good especially with the consumption of battery. I could install Jelly Been with OTA. but first I want to be sure I can, however, at a later time to install a cooked rom any optimized. I have read several threads interesting of which I can do after you've installed the root Been jelly with OTA. http://forum.xda-developers.com/showthread.php?t=2123369
what is the procedure? example install jelly stock then root the phone. Then later I want to install a cooked rom. and to do this I have to unlock the bootloader and install a better recovery CWM or TWRP.
I am not clear what are all the steps after installing Jelly Been stock or whether they should take some steps to ICS Stock.

luisdev said:
hello, I am a software developer but not Android, I'm sorry I can not give no contribution for now. I have a razr_i (Retail GB) with stock ICS 4.0.4 and I'm pretty good especially with the consumption of battery. I could install Jelly Been with OTA. but first I want to be sure I can, however, at a later time to install a cooked rom any optimized. I have read several threads interesting of which I can do after you've installed the root Been jelly with OTA. http://forum.xda-developers.com/showthread.php?t=2123369
what is the procedure? example install jelly stock then root the phone. Then later I want to install a cooked rom. and to do this I have to unlock the bootloader and install a better recovery CWM or TWRP.
I am not clear what are all the steps after installing Jelly Been stock or whether they should take some steps to ICS Stock.
Click to expand...
Click to collapse
If you are still on Ics i reccomend you to first unlock the bootloadet for prevend future bricks
Second, i prefer upgrade to jellybean with the homemade versions, cause are fully stock but are rooted
And after that, instal cwm or twrp
Intel device - Razr i Owner
Hit thanks if i help you or you like my style

sequence:
1) first I have to unblock the bootloader (ICS)
A) then install a new CWM recovery or TWRP (I prefer the latter)
B) then the root
2) Install jelly Been stock initially or later if possible a cooked rom JB
the second (2) step is not clear how I implement it. you can always do the upgrade with OTA after the first step without any problems or special measures are required, and then the fastboot must be compatible with jelly Been stock? there is something not clear to me. thank you for your answer. the devil is in the details

luisdev said:
sequence:
1) first I have to unblock the bootloader (ICS)
A) then install a new CWM recovery or TWRP (I prefer the latter)
B) then the root
2) Install jelly Been stock initially or later if possible a cooked rom JB
the second (2) step is not clear how I implement it. you can always do the upgrade with OTA after the first step without any problems or special measures are required, and then the fastboot must be compatible with jelly Been stock? there is something not clear to me. thank you for your answer. the devil is in the details
Click to expand...
Click to collapse
Well the steps are correct but first install the ota update before root, cause if you root on Ics its gonna lose it when you upgrade so
1- Unlock bootloader
2-Install ota update before cwm (cause the ota update needs the original recovery)
A- You are now on stock jb with unlocked bootloader
3- Install Cwm or twrp
4- Root it whit the root pack for jb on development section
Intel device - Razr i Owner
Hit thanks if i help you or you like my style

[Q] HTC GPE can't update to 4.3. Status 7 error

Guys,
My HTC ONE Google Play Edition received the 4.3 update notification, but when I tried, it gave me a status 7 error and refused to install the update. How can I solve this? I'm using stock kernel, CWM recovery, and it's rooted.
Thanks a lot.

felix1212 said:
Guys,
My HTC ONE Google Play Edition received the 4.3 update notification, but when I tried, it gave me a status 7 error and refused to install the update. How can I solve this? I'm using stock kernel, CWM recovery, and it's rooted.
Thanks a lot.
Click to expand...
Click to collapse
you need stock (gpe) recovery and maybe temp unroot (with supersu)

godutch said:
you need stock (gpe) recovery and maybe temp unroot (with supersu)
Click to expand...
Click to collapse
Thanks for reply!! May I know how I can restore both the recovery and ROM to the default one? Should I follow this?
http://forum.xda-developers.com/showthread.php?t=2358781

You have to flash only the stock recovery and relock the bootloader
And yes, use that guide.
After the update will be installed

Guich said:
You have to flash only the stock recovery and relock the bootloader
And yes, use that guide.
After the update will be installed
Click to expand...
Click to collapse
Thanks guy!! I will check the post thoroughly later. However, just one more quick question. Since my device is an original GPE, it looks like all I have to do will be just a fastboot flash recovery & fastboot oem relock? Seems like from that guide, most steps prior to these commands are needed to turn a normal HTC ONE into a GPE one. Am I understanding correctly here?
Thanks again.

Relocking boot loader not necessary. My boot loader is unlocked.

gunnyman said:
Relocking boot loader not necessary. My boot loader is unlocked.
Click to expand...
Click to collapse
Is better if the relock isn't necessary

Guys, thanks for you guys help. I've stocked it back to stock recovery, and have the bootloader locked back. Now when I start the phone, the little lock isn't shown anymore. However, I'm still having 2 issues here.
1) The 4.3 update isn't there anymore!! It doesn't come back even I did a clear cache/force close on the Google Services Framework.
2) It's still showing my phone is still tampered. I booted into the recovery, and it's now the stock one. Is that normal?
Thanks.

Normal because you're rooted

Thanks guy!! I could upgrade successfully.

[Q] Re-installing jelly bean 4.3 xperia sp

Need help!!!
1st i rooted my phone and installed cm 11. After a few days of use i decided to reinstall my stock rom. I downloaded the rom i.e. 'C5302_12.1.A.1.201' and it installed without any issues. But after that whenever i'm trying to update the FW to 12.1.A.1.205, i'm getting error message. I tried both from mobile client update service and pc client update service (error message showing me can't install update as i'm using modified software).
What do i do?

joe_xperia_sp said:
Need help!!!
1st i rooted my phone and installed cm 11. After a few days of use i decided to reinstall my stock rom. I downloaded the rom i.e. 'C5302_12.1.A.1.201' and it installed without any issues. But after that whenever i'm trying to update the FW to 12.1.A.1.205, i'm getting error message. I tried both from mobile client update service and pc client update service (error message showing me can't install update as i'm using modified software).
What do i do?
Click to expand...
Click to collapse
Did you unlock your bootloader? If so then re-lock it.

Oblox said:
Did you unlock your bootloader? If so then re-lock it.
Click to expand...
Click to collapse
yes, i unlocked my bootloader. Though i installed the new fw with flash tool but would love to know how to relock bootloder again, so will you please elaborate how to do so.
Thanks in advance.

joe_xperia_sp said:
yes, i unlocked my bootloader. Though i installed the new fw with flash tool but would love to know how to relock bootloder again, so will you please elaborate how to do so.
Thanks in advance.
Click to expand...
Click to collapse
If you followed the guides on xda then youll have all the relevant backups you need. If you dont have the TA partition backup then you might be a bit buggered.
Search here for relocking bootloader threads and see what they say.

[Q] Unlocked Bootloader running 5.01 - is it safe to upgrade OTA to 5.1?

Hi Noob question here, I don't want to root or flash my Nexus 6, I bought it from a guy 2nd hand and he had flashed various roms. He restored it to stock android before selling it to me - It has the unlocked padlock on boot - Unlocked Bootloader running 5.01 - is it safe to upgrade OTA to 5.1? Will there be any danger of bootloop?
What should I do?

@Darius,
Unlocked bootloader has no effect on installing OTA.
Yes, there's always a risk of bricking if you don't follow the directions precisely. There are several "how to" threads. Read, understand, and ask questions.

Whatever you do, relocking the bootloader is probably not the answer ?
Sent from my Google N6 on VZ

Darius said:
Hi Noob question here, I don't want to root or flash my Nexus 6, I bought it from a guy 2nd hand and he had flashed various roms. He restored it to stock android before selling it to me - It has the unlocked padlock on boot - Unlocked Bootloader running 5.01 - is it safe to upgrade OTA to 5.1? Will there be any danger of bootloop?
What should I do?
Click to expand...
Click to collapse
If the device is completely stock (including recovery), you should be able to take the OTA. Unless there is something wrong with your device hardware, I don't see any risk. It is just a regular OTA you get from google, direct to device, and you just apply it. Just make sure your phone has a full charge, and don't interrupt the update process.
As a precaution, you should back everything up - never say never
Oh, and to second what DebianDog wrote, don't lock your bootloader

Thanks for all the tips guys, applying update right now...

I have been trying to upgrade my Sprint Nexus6 for the last 3 days. the download goes well the install gets halfway through the blue line under the Android and then he lays down with an "Red Error"
boot loader unlocked and rooted running Stock 5.01. suggestions of the log files i should pull to help narrow this down?

myopic said:
I have been trying to upgrade my Sprint Nexus6 for the last 3 days. the download goes well the install gets halfway through the blue line under the Android and then he lays down with an "Red Error"
boot loader unlocked and rooted running Stock 5.01. suggestions of the log files i should pull to help narrow this down?
Click to expand...
Click to collapse
Nothing needed to narrow it down - you cant take the OTA if you rooted -> because rooting installs SU -> which changed your /system partition -> it no longer matches what the OTA looks at -> and it will fail, sorry.
Unroot it and you might try it again, or you would have to re-flash a stock image to be clean and then take it. The bootloader being unlocked is not the cause.