Hey guys, because i still haven't seen a patched stock logo for nougat (and i needed one myself) i fixed the problem like i did some months before.
The logo.bin has the same filesize as the original one but a other md5 due to the modifications with the image linking.
G4liant said:
For everyone who is annoyed with the warning message that the bootloader is unlocked, i modified the logo.bin to show the normal bootlogo.
I edited it with a hex editor, so when the unlocked bootloader picture is triggered it will use the default bootlogo.
It still shows "N/A" which comes from the bootloader... i can't fix that.
If you want to install the logo, just type the following:
fastboot flash logo logo.bin
Click to expand...
Click to collapse
To install the logo just type the command as shown above.
Before you can do that you will have to unzip the files from the attachments.
It's not meant for installation from recovery.
stock nt still N/A present
diegomartinezlovey said:
stock nt still N/A present
Click to expand...
Click to collapse
As i quoted myself in the op:
It still shows "N/A" which comes from the bootloader... i can't fix that.
There are logos which camouflage the N/A with different colors (white) or shrinking/moving the logo so you don't see it.
I personally prefer the most stock Iike experience, even if I can see the N/A, because after the 5 seconds the logo would jump to the original position which annoys me even more.
These logo.bin's merely exist to get rid auf the black screen with the message that your device can't be trusted.
G4liant said:
As i quoted myself in the op:
It still shows "N/A" which comes from the bootloader... i can't fix that.
There are logos which camouflage the N/A with different colors (white) or shrinking/moving the logo so you don't see it.
I personally prefer the most stock Iike experience, even if I can see the N/A, because after the 5 seconds the logo would jump to the original position which annoys me even more.
These logo.bin's merely exist to get rid auf the black screen with the message that your device can't be trusted.
Click to expand...
Click to collapse
..
sidg2 said:
Please do something and remove this annoying error N/A text warning from the stock nougat boot logo. Make the nougat logo fully stock without any text warning.
Click to expand...
Click to collapse
Did you even read what you quoted?
There is a check for the device id implemented into the bootloader. The bootloader is signed and cryptic and can't be altered without causing it to stop working. It is and will stay this way unless Lenovo removes the check.
Because the stock nougat logo is colored and the N/A text is always white, it's impossible to remove while leaving the logo intact.
sidg2 said:
Please do something and remove this annoying error N/A text warning from the stock nougat boot logo. Make the nougat logo fully stock without any text warning.
Click to expand...
Click to collapse
Can we ban people like this? People who make demands from others without even reading the thread?
Is there any chance in future or any way to remove the annoying error Bad key or N/A text warning from the stock nougat boot logo? Is it possible to make the nougat boot logo fully stock without any text warning like Bad key or N/A?
sidg2 said:
Is there any chance in future or any way to remove the annoying error Bad key or N/A text warning from the stock nougat boot logo? Is it possible to make the nougat boot logo fully stock without any text warning like Bad key or N/A?
Click to expand...
Click to collapse
Short and simple: No!
Please can you make this awesome bootlogo to 720p?
Very Elegant! Nice Job!
This solves the problem. I hate that black screen with the warning every time I reboot. This is the absolute best you could get without messing up the bootloader. Thank you so much!
QUOTE=G4liant;71487915]Hey guys, because i still haven't seen a patched stock logo for nougat (and i needed one myself) i fixed the problem like i did some months before.
The logo.bin has the same filesize as the original one but a other md5 due to the modifications with the image linking.
To install the logo just type the command as shown above.
Before you can do that you will have to unzip the files from the attachments.
It's not meant for installation from recovery.[/QUOTE]
Very nice thread folks. Thanks!
Related
I was getting ready to install MIUI v5 when this happened. I was on an older version of Paranoid Android, I'm not too sure which one but it's not the most recent 4.3 one. I tried to boot into clockworkrecovery mod, but now I'm just getting a boot loop. I see the Google symbol with the unlocked lock at the bottom, and then it goes to the Clockwork logo for like 3 seconds. At the bottom it shows the version number, v6.0.4.3, but then it starts to boot again. Right before the logo disappears, the whole screen gets brighter for a split second. How can I fix this?
Any help is much appreciated
Thanks,
jjjnmk
jjjnmk said:
I was getting ready to install MIUI v5 when this happened. I was on an older version of Paranoid Android, I'm not too sure which one but it's not the most recent 4.3 one. I tried to boot into clockworkrecovery mod, but now I'm just getting a boot loop. I see the Google symbol with the unlocked lock at the bottom, and then it goes to the Clockwork logo for like 3 seconds. At the bottom it shows the version number, v6.0.4.3, but then it starts to boot again. Right before the logo disappears, the whole screen gets brighter for a split second. How can I fix this?
Any help is much appreciated
Thanks,
jjjnmk
Click to expand...
Click to collapse
Try flashing recovery again via fastboot
Code:
fastboot flash recovery recovery.img
RajatPatel said:
Try flashing recovery again via fastboot
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I've been looking into that, but I don't have the proper drivers installed on the computer I have with me (which I know is really really dumb). Is there a way to install the drivers even if my phone can only get to fastboot?
jjjnmk said:
I've been looking into that, but I don't have the proper drivers installed on the computer I have with me (which I know is really really dumb). Is there a way to install the drivers even if my phone can only get to fastboot?
Click to expand...
Click to collapse
If you don't know driver stuff, use GNex Root Toolkit. It will guide you to install adb/fastboot drivers.
http://forum.xda-developers.com/showthread.php?t=2208865
http://www.androidrootz.com/2012/08/how-to-get-install-correct-driver-for.html
For basic stuff take a look at this, it's worth to bookmark the following link for future reference:
http://forum.xda-developers.com/showthread.php?t=1828061
while following the xda guide and youtube video listed here:
http://forum.xda-developers.com/showthread.php?t=2733523
and
https://www.youtube.com/watch?v=CCGj0rOuiR4&index=1&list=PL1sUEhaksHWiSi_vtKtb4KPQNHqEEq1L1
I was able to make it to the 9:00 mark on the video or the part in the xda post stating to type the command fastboot reboot-bootloader to boot back to a clean gpe rom to continue the process. What happens now is the google logo shows up without the padlock icon(locked?) and transitions to the boot animation but it never boots to the welcome screen.
I would not mind going to recovery but i can no longer do so. When choosing recovery through the bootloader menu it boots to black then 30 seconds later there is an icon that has a caution sign in the middle. The design style of the icon is HTC based.
I am doing this with a tmobile variant m8 using the super cid
the great heisenberg said:
while following the xda guide and youtube video listed here:
http://forum.xda-developers.com/showthread.php?t=2733523
and
https://www.youtube.com/watch?v=CCGj0rOuiR4&index=1&list=PL1sUEhaksHWiSi_vtKtb4KPQNHqEEq1L1
I was able to make it to the 9:00 mark on the video or the part in the xda post stating to type the command fastboot reboot-bootloader to boot back to a clean gpe rom to continue the process. What happens now is the google logo shows up without the padlock icon(locked?) and transitions to the boot animation but it never boots to the welcome screen.
I would not mind going to recovery but i can no longer do so. When choosing recovery through the bootloader menu it boots to black then 30 seconds later there is an icon that has a caution sign in the middle. The design style of the icon is HTC based.
I am doing this with a tmobile variant m8 using the super cid
Click to expand...
Click to collapse
Somewhere you HAD to have missed something. Many people have gone to and from GPE with these conversions without any problems.
Did you flash the RUU file twice? Maybe retry again from the top.
If you flashed right then I don't think it should show the google logo but instead the stock HTC as you are now on WWE version and not google anymore, so you missed something somewhere.
What does the caution sign in recovery look like? Small phone with red triangle and upside exclamation mark? IF so then that would be the stoc recovery.
But as long as you can get into fastboot still then you can at least retry the guide.
BerndM14 said:
Somewhere you HAD to have missed something. Many people have gone to and from GPE with these conversions without any problems.
Did you flash the RUU file twice? Maybe retry again from the top.
If you flashed right then I don't think it should show the google logo but instead the stock HTC as you are now on WWE version and not google anymore, so you missed something somewhere.
What does the caution sign in recovery look like? Small phone with red triangle and upside exclamation mark? IF so then that would be the stoc recovery.
But as long as you can get into fastboot still then you can at least retry the guide.
Click to expand...
Click to collapse
Thank you for the prompt reply. Thank goodness i kept a backup of my gpe. I used HTC One 2014 (M8) All-In-One Toolkit V2.0 yesterday and i was able to reinstall twrp which the led me to eventually restore my backup. It would not restore initially, but i found that twrp has its own built in file manger.
After navigating to the backup in the external sd i copied it to the root of the phone's internal storage under the TWRP folder. After that the backup was able to restore.
I'm posting this in case anyone else has problems like this in the future.
Hi guys,
I'm worried I really effed up as I've never been stuck in a bootloop before on any of my devices.
I was editing the build.prop to add dual window functionality to all of my apps as per this video https://www.youtube.com/watch?v=Z4X2FF3BwjA&index=35&list=WL
And now my phone is stuck in a bootloop. I keep getting a message saying that Android is updating app X out of 38 and it goes back to the LG splash screen.
Sure enough there's a warning at beginning of that youtube video saying BE SURE THAT BUILD.PROP IS NOT TRUNCATED AND ITS PERMISSIONS ARE RIGHT BEFORE REBOOTING! - I'm assuming this is where I've gone wrong.
I'm using a Canadian version of the phone LG-H812 for Bell. Do I have to return the phone to stock to get out of this? How do I go about doing so?
Help!
I should also note that I don't have a custom recovery installed - I wasn't able to get twrp to work.
I've tried using the dd code to send the stock image to the phone but that hasn't worked since all of my setting/files have been kept in place.
I figure I've just lost root access at this point.
So, still stuck in a bootloop.
Have you tried looking in this thread to see if this helps.
http://forum.xda-developers.com/showthread.php?p=62083159
Beandip-Javier said:
Have you tried looking in this thread to see if this helps.
http://forum.xda-developers.com/showthread.php?p=62083159
Click to expand...
Click to collapse
Thanks!
That might have worked - but my phone is not being detected by adb...? It's says it's offline. Is that a bad sign?
Windows certainly detects it as it makes the usb notification sound.
EDIT - Crap, does this mean my phone is bricked?? I wouldn't think so since it goes into download mode and whatnot.
Did you try to use the LG Flash Tool to flash a "kdz" file?
You have to download the right "kdz" for your phone.
My friend's J2 Prime (SM-G532G/DS) happened to be stucked at Security Error (blue screen), no idea how it get there. Tried to flash stock firmware. But after flashing, the phone booted back into the same blue screen, now with a line of red text at the top saying, "Custom binary blocked by FRP. (recovery. img)". Tried many different stock firmware (with 4 files) but none of them solved the problem. Can't boot into recovery, only download mode. Can someone give me detailed step by step on how to fixed this.
If it help, I'm from Malaysia. So maybe the firmware might need to be from this region. Not sure about the origin of the phone though. Also, what could be the reason for this to happen? I'm assuming root. Could it even happen on its own, I mean without rooting or flashing?
also G532G/DS - ARH1 bootloader
i've been going thru lots of ROMs (including testing Lineages), this have never happened to me before.
Flashing stock firmware thru Odin though, require OEM Unlocking ON in Developer Settings.
^ I mean, did you/your friend turn it on before flashing? if not, it actually succeeded?
Only solution might be possible:
Go to stock recovery (POWER + HOME + VOL-UP), wait for it to load, then factory reset from there.
I suppose some images might help!
I'm pretty sure the OEM if off because he know nothing about this thing. When I got it, it already like this. Can't get into recovery, after the first Samsung logo appear, it went straight into the error screen. Same thing happened after flashing.
I don't know how to post images here...
JEDAlive said:
I'm pretty sure the OEM if off because he know nothing about this thing. When I got it, it already like this. Can't get into recovery, after the first Samsung logo appear, it went straight into the error screen. Same thing happened after flashing.
I don't know how to post images here...
Click to expand...
Click to collapse
+ OEM Unlock: if disabled, Odin should've failed straight away and no reboot stuff going.
+ Can't get into recovery:
Is it true that you cannot get into recovery? If left stock, It should be an Android with spinning stuff, text is "installing update" then no command for a while ~2min, and it will go to normal recovery.
I mean, it is supposed to do "recovery" :v
+ Images: post it on Imgur (or any online image service). Copy link here, add space between "https://" and all the stuff there. Wont be considered URL i guess (havent tried)
hello, i was hoping to get some help with my device not being rootable.
i followed these two guides word for word i cant post links because im new here but i followed the naldotech twrp + root s9 guide and the highonandroid s9 root guide.
tried both reinstalled OS with csc and home-csc twice for each one when my phone was stuck in a loop so i can make sure that its back to factory before i try another method. my phone it either gets stuck at samsung logo or just reboots to recovery never goes to samsung logo my oem unlock button always stays off even though i follow the steps and it says under it that bootloader already unlocked and it never goes blue and oem lock: off in download mode, i did not setup my samsung or google accounts in any of those resets that way no settings get synced.
i really need the help i have been trying this for the past month and a half and i have tried everything i could think off and nothing is working.
current software installed: G960FXXU2CRLI_G960FOXM2CRLI_XSG
Model: SM-G960F/DS
OS: 9.0.0
chriskay525 said:
hello, i was hoping to get some help with my device not being rootable.
i followed these two guides word for word i cant post links because im new here but i followed the naldotech twrp + root s9 guide and the highonandroid s9 root guide.
tried both reinstalled OS with csc and home-csc twice for each one when my phone was stuck in a loop so i can make sure that its back to factory before i try another method. my phone it either gets stuck at samsung logo or just reboots to recovery never goes to samsung logo my oem unlock button always stays off even though i follow the steps and it says under it that bootloader already unlocked and it never goes blue and oem lock: off in download mode, i did not setup my samsung or google accounts in any of those resets that way no settings get synced.
i really need the help i have been trying this for the past month and a half and i have tried everything i could think off and nothing is working.
current software installed: G960FXXU2CRLI_G960FOXM2CRLI_XSG
Model: SM-G960F/DS
OS: 9.0.0
Click to expand...
Click to collapse
Did u fix it ? Cos I have similar issue but on my phone it says the bootloader is locked and the OEM unlock option never turns on , when I turn it on it does factory reset and reboot the device but the option stays off
Akhayev said:
Did u fix it ? Cos I have similar issue but on my phone it says the bootloader is locked and the OEM unlock option never turns on , when I turn it on it does factory reset and reboot the device but the option stays off
Click to expand...
Click to collapse
no fix yet and same thing is happening to me the OEM options always stays off and that's even after a clean firmware install i really hope we can find a way to fix this
chriskay525 said:
no fix yet and same thing is happening to me the OEM options always stays off and that's even after a clean firmware install i really hope we can find a way to fix this
Click to expand...
Click to collapse
Did u wait for 7 days ?