So I cant boot my phone and am COMPLETELY stuck and freaking out so hard.
I did a clean install of the validus rom and bean gapps. During set up, I made a pattern lock and made it required for boot up.
First time after restarting, i go into twrp and see the pattern prompt. I enter the correct pattern, and it says its wrong. I am able to get into twrp by entering anything other than the right pattern. I CANNOT boot into and rom even after flashing a new EDL image. I need my phone for work in a few hours my boss would kill me if he didnt live on the other side of the country I am extremely desperate for help.
Whenever i try to look up how to bypass the pattern, it only shows ways for patterns that are not required during boot up.
How do I get rid of secure startup on A2017U B25 unlocked bootloader?
UPDATE: After flashing EDL I was able to remove Patter Secure Startup using the STOCK recovery, lol wish I tried that hours ago
Related
Whenever I try to unlock the bootloader of my Nexus 7. I will get to the screen that asks do I really want to unlock, I select yes. At the top of the bootloader screen it just sits and says "Unlocking now...." from there It will not reboot into the bootloader and whenever I do get it powered down and back into the bootloader it is still locked. I have also tried fastboot and various toolkits to automatically unlock and flash back to factory.
In the end I am trying to get in back to original state. I have fastboot.exe and the image file. At the moment trying to boot the device it will not get past the first "Google" startup screen. Any help would be appreciated. I am fairly new at this and have been spending hours of time trying to get my Nexus 7 to work again.
I recently successfully restored my Axon 7 (A2017U) to B20 and tried to OEM lock it again. After running "fastboot oem lock", the phone rebooted, but came up with something that said "To start Android, enter your password." I didn't have a password before, so I tried something I found online called default_password to see if it would unlock (which it didn't) & then other passwords to get the phone to wipe itself and essentially perform a factory reset. However, now it is stuck in Safe Mode and says "Decryption unsuccessful: The password you entered is correct but unfortunately your data is corrupt." When I try to wipe the phone, it says it is factory resetting, but then it restarts and goes to a blank screen. (Which I suspect is because TWRP is still installed as a recovery, not stock). In addition, power+volume up no longer works since the phone is oem locked, but power+volume down takes the phone into Factory Test Mode. My computer still recognizes the phone when it shows up in Safe Mode, but I cannot see it in ADB.
Where can I go from here to factory reset the phone? Is it possible to send this to ZTE to fix since it is OEM locked at the moment?
I followed razorblader's advice and successfully got the phone into EDL mode and ran tenfar's tool. However, that made it worse and now the phone just shows ZTE for the second & the screen goes blank.
EDIT: Nevermind, I was running that program without recovery.img/boot.img in the same directory, D'OH! Luckily, I still had comms with the phone after that mistake & I re-ran the program successfully. I can now get into TWRP recovery. However, booting into system still shows the corrupt data message. I'm going to try a factory reset from TWRP and see if that fixes the issue.
OK good news, got my Axon 7 working again, stock + locked & am currently posting this from it. One reason I wanted to relock it however was to get OTAs and right now B27 is showing up. Now before I almost brick my axon again, do I need to flash stock B20 recovery before I'm able to install this update? Also, I'd like to get to B29 eventually, but I'm guessing I need to update to B27 first. (correct me if I'm wrong though)
Hello, my english is unfortunately not very good, so I translated with Google Translate.
I wanted to root my phone (Huawei Nova Can-L11) and used this guide.
https://forum.xda-developers.com/nova-plus/development/recovery-unofficial-twrp-huawei-nova-t3523473 .However, I have installed a wrong image or something go wrong .
Now the mobile always starts again, about 3 seconds. I briefly see the Huawei logo, and then the orange font that is not trusted.
The problem I had yesterday, but it somehow managed to close the OEM again, and the mobile ran normally.
It was with the power button and soft key, but this is probably no more.
Now I wanted to install the correct image, unlock oem and the error is back. But I can not come back. Adb and Fastboot find no device, and the PC is not synonymous displayed.
Maybe I'm too nervous for the key combination because it worked yesterday. But I'm just scared.
If my PC would display the mobile, I could possibly with fastboot go back to lock oem. But it does not indicate anything ..
Ask for help, I hope I have not completely destroyed it.
hi! i have bricked Nova Plus, after factory reset in TWRP. i use all method flash fiirmware - tel is bricked. i bay credit in DC Phoenix (15 evro) and download fullflash firmware. after flashing and factory reset,phone is boot sussec. after full boot i flash firmware from hwmt. after flashing run factory reset- boot- tel is fully working!
always wait for 10-15 minutes after a flash/reboot...it takes some time...IF after 15 minutes its still on phone booting well...youre in bootloop
So, put my son's SM-T580 on the charger last night, it was fine (he's been using it for months), woke up this morning to it boot looping. It will not get past the initial boot screen and has that annoying red text 'Custom Binary Blocked by FRP Lock' in the upper left corner. It will not boot recovery. I can only boot to the bootloader. Of course, I can't flash anything using ODIN because of the FRP lock. I'm thinking the only options I have is to try flash a stock ROM / Recovery back onto it and start over but I was wondering if anyone else has ever seen or heard of anything like this before I do that. Thanks.
UnZoner said:
So, put my son's SM-T580 on the charger last night, it was fine (he's been using it for months), woke up this morning to it boot looping. It will not get past the initial boot screen and has that annoying red text 'Custom Binary Blocked by FRP Lock' in the upper left corner. It will not boot recovery. I can only boot to the bootloader. Of course, I can't flash anything using ODIN because of the FRP lock. I'm thinking the only options I have is to try flash a stock ROM / Recovery back onto it and start over but I was wondering if anyone else has ever seen or heard of anything like this before I do that. Thanks.
Click to expand...
Click to collapse
The only thing that I can think of is that someone, somehow disabled the OEM Enable setting in /Developer options. This is what trigger the FRP lock.
You will need to hold Vol-, Home and Power buttons to boot to download mode and use Odin to flash a stock ROM. Then you will need your the Google Login and Password that is registered to the tablet. If you don't know those, you're in a heap of trouble.
As soon as you get stock up and running, the first thing to do is enable the developer options and make sure that OEM is enabled. After that you can flash TWRP and custom ROMS.
If you don't know the Google info, the tablet CAN be salvaged, but it is a complicated process.
lewmur said:
The only thing that I can think of is that someone, somehow disabled the OEM Enable setting in /Developer options. This is what trigger the FRP lock.
You will need to hold Vol-, Home and Power buttons to boot to download mode and use Odin to flash a stock ROM. Then you will need your the Google Login and Password that is registered to the tablet. If you don't know those, you're in a heap of trouble.
As soon as you get stock up and running, the first thing to do is enable the developer options and make sure that OEM is enabled. After that you can flash TWRP and custom ROMS.
If you don't know the Google info, the tablet CAN be salvaged, but it is a complicated process.
Click to expand...
Click to collapse
This is what I was afraid of. It is my sons tablet so I have all his Google info. I would not be surprised if he somehow reset the developer options. He'll lose some of his game progress but that's nothing compared to losing the whole tablet. Thanks for the reply. Off to download a stock rom and start over.
So, pretty much what the title says...I got the prompt to update to Oreo. Clicked install and left it. It does whatever it needs to do and after 2 hours of leaving it there it was just stuck on the boot screen. Tried to boot into recovery and no luck, it just remains on boot screen. I can access fastboot mode though.
Because the boot loader is locked, I can't install a custom recovery or anything. I tried everything I could in my own power before resorting to here. Any suggestions?
Did you hold the power button down until your phone completely powered off? I'm assuming you did. What you described isn't supposed to happen on a dual partition phone. If an update goes bad the phone is supposed to recover by booting from the other partition. If powering the phone down completely and then turning it back on doesn't allow you to boot I would honestly go straight to Essential Support since you didn't mod your phone or unlock the bootloader. I dealt with support via email and if nothing else they are definitely very responsive. They answer emails so promptly it was almost like being in a chat.
devon4786 said:
So, pretty much what the title says...I got the prompt to update to Oreo. Clicked install and left it. It does whatever it needs to do and after 2 hours of leaving it there it was just stuck on the boot screen. Tried to boot into recovery and no luck, it just remains on boot screen. I can access fastboot mode though.
Because the boot loader is locked, I can't install a custom recovery or anything. I tried everything I could in my own power before resorting to here. Any suggestions?
Click to expand...
Click to collapse
Hello
Tell us the status of your phone Did you solve the problem? Tell us the way I'm stuck in the same problem