Bootloop/Black screen of death after flashing boot.img - Android Q&A, Help & Troubleshooting

Well, it's a bit of a long story, so I'll try to be as short as possible.
Last year, and after hours of searching on the internet, I found the solution for "Custom binary blocked by frp lock" on this forum (here and here). Both methods promised to fix the lock without erasing my data, but I decided to try the second one (it consists of reinstalling only the boot image with Odin).
Fortunately it worked for me on the first try, and since this method was not well known on the internet, I decided to make a video tutorial to help those who had the same problem and wanted to keep their data.
The fact is that, unfortunately, this method didn't work for everyone, and in many cases it generated bootloops or black screens of death.
And my question is: does anyone know what could be the cause of this?
I tested it on SM-J710MN and SM-G532M, both running Android Marshmallow, and the bootloops/black screens occurred on devices running Android 6, 7, 8 and (I guess) 9 and 10.

Starting with Android 6 FRP on any such Android device is automatically enabled once a Google account is logged in to a device. The only way to get rid of it is by removing the account from the device into which it has been synced.

jwoegerbauer said:
Starting with Android 6 FRP on any such Android device is automatically enabled once a Google account is logged in to a device. The only way to get rid of it is by removing the account from the device into which it has been synced.
Click to expand...
Click to collapse
Thanks for answering.
Maybe I did not express myself in the correct way, but actually I was referring to the block that does not even allow to boot the device and only shows words in red, as seen in this image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But beyond that my question is about why does the bootloop or black screen happen after flashing the boot.img file? Does it have to do with a different/incompatible version of Android/binary/csc or something like that?

Related

Problems with ICS [encryption, security and recharging]

Hello
I would like my Android device encrypted, as it contains sensitive data. I'm currently on cm-9.0.0-rc1-tinystream-hephappy-p500 (RC1-Rev.B). Now, here is what happened:
- To encrypt internal
I went to Security in System Settings and touched "Encrypt Device". It gave some confirmations and I've accepted them however, now I'm kind of stuck on this screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My first thought was "it is encrypting". But after hours of waiting, I wanted to check if it's done already. So I clicked the power-button once (just to unlock) and it asked for my password. I've entered it and it just went into my normal launcher. I've checked if anything had changed and no, my device has not been encrypted. Any logs somewhere? Any ideas what could have caused the problem?
- To encrypt SDcard
I did some research and didn't find something perfectly for my needs. Anyone has any idea on how to encrypt an SD card to properly work together with Android?
Note: I am using LINK2SD.
Thanks for your help
Another question that actually has nothing to do with my previous post that I post here because it's not worth a new thread: every time I plug in my phone into the charger, it boots automaticly. I don't want that, my previous build of CM9 did just recharge without booting, something I prefer. Any way to configure that?
Another question I want to add to the this thread: is it possible to combine a password lock and a slide lockscreen? Like when I encrypt the phone to enter a password to decrypt it again and then just use the normal slide lockscreen to unlock it each time after the decryption?
One last question: is there any way to encrypt the SQL database in Android? As it contains sensitive data... I've read something about SQLCipher but it doesn't get to work (any help would be appreciated).
Thread can be removed. Problems already solved. Discussion about security here: http://forum.xda-developers.com/showthread.php?t=1790964
And for the charging problem: http://forum.xda-developers.com/showpost.php?p=29217540&postcount=1787

OEM Unlock 7 or 14 days, RMM state...

I read a lot in these forums here about OEM unlock S9+ but until now it did not work for me. Additionally there are lot of confusing information around here...
Can anyone (from OWN experience !) please write how unlock, waiting-time and RMM-states are related?
I bought a new phone from U.K., a variant which actually is only available in the Asian market as far as I know.
Color blue with 256 GByte and dual-SIM.
It has EXYNOS CPU !!! As you can see from my attachments, I have already been waiting 7 days for OEM-unlock with no success. I did not boot into download-mode yet.
I assume Samsung has produced phonse, even with EXYNOS, where the OEM-unlock is impossible...
View attachment SoftwareInfoS9.pdf
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As far as I know, so far, only the snapdragon variants can not be unlocked using the OEM Unlock feature.
I had a custom ROM for about 5 days, and to be honest I sort of wish I hadn't done anything at all. Unlocking the bootloader breaks things like Google Pay and Device Certification on Google Play. This stops things like Netflix and other services (seemingly only ones that rely on Googles Windvine DRM - although the APKs can be installed manually). The second you load TWRP, Knox is gone forever. It is unrecoverable. This I care less about, although Secure Folder had its uses for duplicating apps.
Yes, its possible for Root to fix most of those, but its an endless cat and mouse chase and often breaks when Google update things (I could not get Google Pay to work at all despite Magisk Hide)
During those 5 days, the OEM Unlock option was unavailable to me. When I decided to go back to full stock condition (minus Knox) I loaded all the correct things in via Odin, and the OEM Unlock option was available, with the slider in the off position.
What I want to know at this point, is does turning it on re-lock the bootloader? Because if it does that would likely solve my issues with Google Pay (its incredibly handy).
To answer your question though, the standard waiting time is usually 7 days, after which it will re-appear.
I now rebooted to download mode to see the RMM state. It is Prenormal...

ANYONE KNOW HOW TO DO A SOFTWARE REPAIR ON THE NOKIA 1

Morning,so i am going to try yet again for some help here with regards my mom's Nokia 1 device running on Android 10 Go. Since she updated her phone to Android 10,she has had cmstant issues with the phone. Since updating it,her messages app will not switch to dark mode at all,i have tried uninstalling it and replacing it with other versions etc but it never has a dark mode option available in the app at all.
Then her Google Chrome would not update at all. I got that sorted after a lot of trial and error,resetting the phone and so on. Now the phone has issues with her wallpapers resetting to the default wallpaper the whole time at random. She also suddenly has an issue with her camera after the recent camera related update. She can take a photo,but is unable to view it from her camera app after taking the photo. She also is unable to delete the photo after taking it.
So,i am wanting to know if anyone has any idea of how to perform a software repair or maybe a way to re-install Android 10 on her phone other than just doing a factory reset which does'nt fix any of her issues anyway. Please,we just want to get the phone working properly,so if anyone knows how we can do that,it would be appreciated.
Thank you
Just like any MTK phone use spflashtool then flash it
U should check Wich model first
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@Hucin44 thank you. Have you tried this with a Nokia 1 or do you know someone that has? I do not want to try this if nobody else has and were successful. Last thing i want is to brick my mom's phone.
U can follow this
Downgrade Nokia 1 TA-1066 from Android 10 Go to Android 8.1 Go
The Nokia 1 recently got the Android 10 update. The update got lot of bugs like SD card losing write permissions, launcher3 not having widgets and shortcuts on top of other bugs in Pie. This has compelled me to look for going back to Android 8.1...
forum.xda-developers.com
It's work for more secure if afraid to brick the phone uncheck preloader in spflashtool
Thank you

Help me, I HARD Bricked my phone (Xiaomi Redmi 10X 5G) Erased all partitions!

So I have this phone Xiaomi Redmi 10X, and I wanted to put Pixel Experience 11.0 in it, after seeing this thread on GitHub.
To my surprise, following steps on that link was not that easy!
I flashed MIUI 22.1.19 manually (not in the correct way), and I ended up with a hard bricked phone.
Yesterday, while Googling about that, I managed to run into a tool called MTKClient v2.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and it solved my problem, by flashing original firmware and got it correctly working with the default MIUI 13 system.
BUT, that wasnt enough for me, because I still wanted to put Pixel Experience in it since I like it so much and think it is so sexy!!! So I, without knowing what I was doing, erased all the partitions in my phone with that tool.
Now, I cant get it to connect to that tool to work or connect with my device. On the cmd behind though, I do get some hope after seeing that device is still recognized in some way, but that's all there is to it, it doesnt go further, only "Phone detected: Reading model info".
I've tried to wait and keep both volume buttons pressed at the same time, but to no avail.
Since this, I've tried several tools but none is working to reset my partition table to original state, since I think that's my problem.
Any idea how to fix it?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
No. What is that?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
Even if it connects, it shows no partitions to write over.
What it needs, is to first restore the erased partitions, I think, and then writing (flashing) the firmware into it.

Huawei P20 Lite "Your Device Has Failed Verification and may not work properly." Maybe has no OS I dont know. Please Help!!

Ok, so i got this random Huawei P20Lite right?
Back isnt pealed off, works fine, no damages.
BUT WAIT... About Works Fine... It Wont really boot up into The OS!!!
Somethimes shows this really weired Image when pluged in and charging the phone, or randomly:
A green Screen with a Red Square on Top and a Blue one Down.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not My Picture
It will then boot up and greed you with A:
Again, not my Picture.
Acording to Huawei, You have to Use HiSuite to recover it.
1. Put the Phone into Fast Boot. AND conect to PC
2. Open HiSuite on Your PC and click on Recovery mode or whatever its called.
3. i donk know i forgot.
anyways, i get this nice little message
(In translated, this means That: Your Device doesnt support System Recovery.
Bro wth
Anyways, our phone story doesnt end there...
I tried doing it without the Computer.
using eRecovery!!! not surprising i know...
Still, it was stuck on booting animation trying to enter eRecovery.
According to Huawei, "this message is displayed when a system file is replaced or modified, or the system is manually updated to an unofficial version". They were responding to another user with the same issue as mine.
I think that this is the Issue. Still, the instructions to fix it, dont work. (as tested above.)
Tutorials show the eRecovery method without the PC.
Here are some info i found:
Another Guy having the same issue:
i forgot the link but someone else on XDA Had the same issue.
please help!!!
hello sir did you have any luck resolving this issue (I've purity much looked every were but I had no chance)

Categories

Resources