I'll get straight to the point, yesterday I went and re-rooted my phone with Kingroot (I had already rooted it once with Kingroot) to try something called Magisk, and basically what happened is that I installed Magisk manager and selected the 3rd option to install it (can't remember the details), I am new at this sort of stuff but I knew it would be risky without some sort of recovery mode installed.
Next thing I know the phone shows the LG logo like normal but with an error message on the up left corner of the phone saying:
"ERROR: boot certification verify
[880]--------------------------------------------
[880]
[880] Secure booting error!
[880] Cause: Boot certification verify
[880]
[880]--------------------------------------------"
And then the screen goes black it doesn't really shut down because it takes me about 10 seconds of holding the power key which is force reboot instead of the 2-3 second hold.
I've been trying to get solutions for this around the forums but nothing works as I don't know my exact model number.
I would appreciate some help and thanks in advance!
Related
Hi guys,
little bit of background on the phone, had it since new close to 2 years away (2 year contract and im 7weeks from an upgrade) the phone is on orange (well EE now)
Basically when I turn my phone on it is stuck in a force close loop, with loads of different messages appearing, such as;
(process com.sec.android.provider.logsprovider)
calenders, messaging etc etc
So I have tried going into the boot mode, by pressing volume up, home screen and the power button.
Then when I try to reboot it comes up with the error messages;
e:error in /data/log/recovery_log.txt (read-only file system)
(read-only file system)
e:copy_kernel_file :: Can't Open /data/log/recovery_kernel_log.txt
Rebooting...
It then just continues onto the normal home screen, then when I enter my swipe code it comes up with the force close loop again.
Any solutions to this problem, Or will I have to factory restore, or is completly broken? Im not due an upgrade for about 7weeks either
Would rather not have to factory restore if possible as I have some files on there I dont want to loose, but if its unhelpable so be it
Thanks in advance guys!
Cheeky little bump, Anyone know a fix to this?
Have similar problem...
I believe a factory reset will fix it...sorry to hear you losing files though..
I have a similar problem. I should probably make a new thread for this though...
Background: Samsung Galaxy SII 1900 bought October 2011. Yesterday flashed a stock ROM for the phone and everything was working perfectly. This is probably not related but have been trying to install a working version of Android Keyboard which has gesture typing working for other languages than English, German, Spanish and French and so some hours before this happened I tried to flash a zip with that but it turned up "e: signature verification failed" so I pretty much gave it up and the phone was still working. Then I decided to install another recovery mode on the phone cause that should allow me to install without verification. So I downloaded the one for SGS2 at clockworkmod com rommanager and put it in on the SD card. Then I shut down the phone and this is the weird part: First I accidentally pressed the power button first so I realised the phone was gonna boot normall so I pressed the power button again to force shut it down. I pressed for quite a long time and then it just restarted and I'm at a boot loop where it says Samsung Galaxy S II with white text on black background.... Then suddenly after removing the battery and trying start several times it booted normally. So I just continued where I left off going to make a backup in Titanium Backup before flashing CWM and suddenly the phone just restarted and I got into the boot loop again. I am able to enter Download mode and Recovery mode but the phone no longer starts. Been trying like 30 times to restart it... Now when I entered Recovery mode just now I got the error message
"E:Error in /data/recovery_kernel_log.txt(Read-only file system)" in red letters... and that's where I'm at now.
Here's a sitty picture of it from my HP Chromebook webcam ******* (Google Drive) Edit: Not allowed to post links in first 10 posts
Hey guys hope you're fine ^^
A friend of mine is having an issue with his phone so he asked me for help, and now i'm asking you lol
well the problem is that :
1- having a weird colored screen on startup (1st attached image)
2- after few second the phone just get stuck on boot animation (2nd attached image)
3- sometimes the phone goes into and update screen and then get stuck on 5% and after a while reboots (3rd attached image)
4- the phone just wont shut down it when i hold the power button the screen goes black, then instantly i feel a vibration and the multicolored screen comes back, then the same story "boot loop"
Well now let me tell you how this problem occurred, well my friend bought this phone from someone, so he doesn't know if there was custom recovery ever installed on this phone or if it's on stuck recovery
the phone was working fine, then one day an update notification pops up, he does the update, the first time it showed him an error message, but he tried one more time and it got throw the update process, unfortunately the phone got rebooted but never made it past the boot screen
now because the phone won't shut down, i can't get into fast boot or recovery mode (i don't know how to do that unless the phone is shut down, and doing the volume/power button combination)
i'm really stuck here and don't know what to do, i'd really appreciate your help guy
PS: sorry for the English, that was the best i could do
EDIT : i managed to get into fastboot mode,yeeeey! (see the 4th attachement)
how did you get into fastboot mode
i am not able to do it
I have a Umidigi Crystal (2/16) and it´s not booting anymore.
How that came is a long story.:crying:
I got the phone, wanted to root it and while I was enabling usb debugging in developer options, I noticed you can root it from there as well.
I have no idea whether thats a Umidigi special or if that was seen on other phones too, basically I had a slider option to enable root access.
After a reboot, SuperSU was installed automatically, root checker, file explorer and rom toolbox worked fine with it but I actually rooted to get Xposed Installer.
That worked very well too, only did I want to have a custom recovery to prepare my phone in case of a bootloop.
So I followed these instructions.
I hadn´t unlocked the bootloader by the time and since the instructions said I would have to unlock it I did that first using these instructions.
Everything worked as expected but from this point on, on the pre-bootanimation picture my screen would say
Code:
Orange State
Your device has been unlocked and can't be trusted
Booting in 5 sec...
As everything else was the same as before, I just ignored it.
Then I moved on to installing TWRP by, again, these instructions.
The process seemed to work but after finishing, I was unable to boot into recovery mode, my phone would just boot into the normal OS(which still worked by the time).
I wanted to get around that by using this app but because of the unlocked bootloader my phone was factory reset
and I had to root again.
I was going for the same way I already did it beforehands and I was asked to reboot again.
After that point, my phone was stuck in the pre-bootanimation screen saying it´s orange state thingy again and would just stay there forever.
I tried installing the stock rom from here ((2/16 - V1.0_20171026)) to get rid of the root setting I enabled.
Now I get the pre-bootanimation screen with the orange state text again and after 5 seconds it keeps the background image but the text disappears.
Thats where it´s stuck for like 3 hours now.
When I press the power key a couple of seconds, that loop starts again, I can´t turn the phone off.
Things I can still do:
•Reboot (holding the power button, still get stuck the same way though)
•Access a PC, the internet, an SD Card and electricity
•Charge the phone
•I still have all the drivers on my PC properly installed
Things I can´t do
•Keep the phone turned completely off
•Boot into fastboot, recovery or normal OS
•Get the PC to recognize my phone (not even the adb)
What I want (if possible in that order):
•Boot into literally any OS
•Use the current OS or any custom rom
•Have root access without the developer option method
•Have TWRP
•Unlocked Bootloader
I know, I ask for a lot but this is the only phone I have right now and I badly need it.
Getting it to boot again is really the primary goal here.
Thanks so much to everyone who tries to help me, it really means a lot
Good day all,
I've had my LG for a year almost working perfectly on stock OS.these days it looks like hanging and always say google services stopped ... i have tried a full hard reset(vol- power lg logo vol- power) it goes and starts with the android robot and loading then just goes off
i have also tried getting it into download mode to flash with original rom and it gives me same error,
ERROR : boot certification verify
[1230] ---------------------------------------
[1230]
[1240] secure booting Error!
[1240] cause : boot certification verify
[1240]
[1240]----------------------------------------
then it turns off alone...
.
However i download the LG drivers and after i try turning on the phone normally it goes off all i did was keep holding the volume up button then plugged into PC(win7) i get a removable disk of 63.9mb with two folders init(image and verinfo), in device manager it is COM15 LGE AndroidNet USB Serial Port. please keep in mind the screen is blank off when all this shows on PC.
I'm basically out of options idk what to do, please help me i have searched all over the web and cant find anything valid .
Any help would be appreciated.
Hello. H830 owner, unlocked, rooted with Magisk, TWRP installed with 30C stock ROM. Today I got a notification to upgrade the Magisk Manager app, which I did. After installing and starting MM, it showed a Magisk update available - I clicked install and specified direct install (like I have many times before). The phone rebooted and I believe got to the T-Mobile splash screen then went into a loop with the apostophe triangle page "Your device software cannot be checked for corruption. Lock the bootloader"...
The only two things I can do are: 1) Pull the battery to power it off, and 2) hold down vol up +vol dn+power to get the IMEI barcode screen. Normal methods of booting into recovery do nothing. Attached it to PC and ran ADB devices and nothing shows up, so trying to run ADB reboot or ADB reboot bootloader yields "error: device '(null)' not found".
This seems bad. I have multipled devices rooted and with custom ROMs and recoveries and I've never seen anything like this. Since this phone is running stock Oreo, I never really need to do much other than perhaps an occasional TWRP backup. The phone has been pretty much flawless, until this Magisk upgrade attempt.
Anyone have any insights or solutions? I don't know what to try next.
did you solved the problem?