I just set up my V20 and I set up finger and knock batter but didn't say I needed it to boot, I didn't set up a secure boot but when I reflashed the Sprint Firmware I was asked for it. Help?
Related
this evening i updated audax rom for g928f from 3.1 to 6.2, everything looked fine since i opened people edge and it freeze while opening it.
So i rebooted my phone and now when i try to turn it on, appears a red text :
KERNEL IS NOT SEANDROID ENFORCING
Custom binary locked by FRP Lock
the only thing i can do is putting the device in download mode
What can i do ? Can i save data from my internal sd? :crying:
I've purchased 12 of these Tablets for my company. Out of the box they were android 6.0, as soon as we connected them to WiFi the 7.0 Update option came up so we updated all 12. We then loaded our Comodo MDM enrollment on them. Well Next time they rebooted 9 of them would not come up, they just sit at the samsung screen fading in and out. I went into recovery mode to try factory reset & wipe, I get the message that "mdm does not allow factory reset". So I tried resetting the cache which did nothing as well. So I loaded Odin and booted into odin mode tried to load a stock rom and I get the message that the device is in FRP mode and cannot load a custom image...
I have ALWAYS had droids and I favor Samsungs normally.... I have always rooted and unrooted every device I've ever had, but these have me stumped... I cannot get into USB debugging mode, I cannot get the things to boot at all. Every tutorial requires debugging mode. Samsung Business support is NO help at all. So I turn to the dark side... HELP!!!
cpubugs said:
I've purchased 12 of these Tablets for my company. Out of the box they were android 6.0, as soon as we connected them to WiFi the 7.0 Update option came up so we updated all 12. We then loaded our Comodo MDM enrollment on them. Well Next time they rebooted 9 of them would not come up, they just sit at the samsung screen fading in and out. I went into recovery mode to try factory reset & wipe, I get the message that "mdm does not allow factory reset". So I tried resetting the cache which did nothing as well. So I loaded Odin and booted into odin mode tried to load a stock rom and I get the message that the device is in FRP mode and cannot load a custom image...
I have ALWAYS had droids and I favor Samsungs normally.... I have always rooted and unrooted every device I've ever had, but these have me stumped... I cannot get into USB debugging mode, I cannot get the things to boot at all. Every tutorial requires debugging mode. Samsung Business support is NO help at all. So I turn to the dark side... HELP!!!
Click to expand...
Click to collapse
Sounds to me like the problem isn't with Google's FRP lock but with the Comodo MDM enrollment. First thing I'd do is contact their tech support. The FRP lock doesn't prevent you from flashing a ROM with Odin. The FRP lock would just ask for the Google login and password on the first reboot. And I have seen other security apps blame the FRP lock for not allowing a ROM to flash via Odin.
So today i bought my LG G6.
There was a software update (i thing Oreo update) i installed it and when i got to the secure screen on the boot.
I type my PIN ,which was valid and my phone now is stuck on the secure loading screen.
At first i thought it was just going to take some time but after 25 minutes of waiting this started to worry me.
The phone is still on loop and when i use the Power Button and the Vol down the phone restarts but the same thing happens.
I tried everything from restarting it , to hard resetting (which doesn't want to work, the bootloader menu doesn't even show up with all the steps completed correctly) to throwing it on the ground.
(PHONE IS NOT ROOTED)
EDIT:I MANAGED TO SOLVE THE ISSUE BUT NOW IM STUCK AT THE PROVIDERS SCREEN WHICH IS (TIM) AND I CANNOT DO ANYTHING OTHER THAN SOFT RESTART
Regards,
Try put the phone into download mode and use LG bridge to reflash stock [Use the "Update error recovery" to reflash]
Hello guys this is my first post.
I have a SM-G930V Verizon S7 that previously was in bootloop with OREO, but constantly rebooted at the beginning of the setup I mean when it says hello and so on.
I flashed Nougat without problems and booted normaly but then the FRP was doing his work, I could not boot since I didnt know the email or password.
I then flashed a file that I found to bypass FRP and succeded. I finally got it working very well.
After a while when I tried to clean bloatware suddenly frozen and then never booted again, I wanted to root but couldn´t.
NOW when I flash any ROM from Marshmellow , Nougat and Oreo, it says PASS in ODIN but I cannot enter the recovery.
Vol+, Home and Power gives me a blue line top left saying RECOVERY BOOTING..... then a blue screen saying ERASING... and the reboots again and again. The menu that I can get is the Maintenance Boot Mode (Vol- Power). This menu has 4 items:
1.Normanl Boot, 2.Factory Reset, 3.Safe Mode, 4.Power Down, and the only who works is power down.
I don´t know how much batery is left because I don´t know if in this menu or in download mode the battery charges.
I flashed the last OREO from SAMMOBILE, I also flashed the ROM wich I grabbed when using VZW Software Upgrade Assistant which supposed to be repairing the device but nothing whatsoever.
I don´t have any new ideas my head is full and hot now. PLEASE HELP will be appreciated.
OK, I have an LG Stylo 2 MS550 originally flashed for the Metro PCS carrier with a stock Android 7 ROM.
I've re-flashed the phone with a lineage custom OS ROM to Android 7.1.2.
I've also flashed the recovery partition with TWRP and used it to root the phone.
Also, the bootloader is unlocked.
What I'd like to do is change the splash screen that initially pops up when the phone is initially powered on.
To be clear, I'm NOT talking about the boot animation.
I've easily changed that simply by re-writing the .zip in the appropriate system folder.
What I want to do is get rid of the "LG Powered by Android" logo that the bootloader puts up right after power on.
How do I accomplish this?
Is the bootloader code stored somewhere in the system directory?
Or is it some super low level code burned in a ROM register on the processor itself so no one can get to it?
Thanks.
Any help, guys?