So I appear to have a soft bricked phone. It is on stock firmware, although it has been unlocked previously in order to flash that over the Three custom firmware.
It randomly rebooted itself into a boot loop where it would get as far as the Razer logo and restart itself. I got into recovery and tried to factory reset it, at which point it claimed to have formatted /data but then complained it failed to mount /mnt/vendor/persist (no permission).
I can't see it in adb devices unless I put it in sideload mode - I presume I can't sideload anything anyway unless it is unlocked for flashing.
I can reboot to the bootloader and then see it in fastboot but I can't do very much there because the bootloader is not unlocked (so I can use Netflix, my banking app, etc), but I can't boot to the OS in order to unlock it or make sure adb debugging is on. The general instructions on Razer's website to do fastboot flashing unlock or unlock_critical don't seem to work as I think this needs the phone to be in 'download mode' which doesn't seem to be a thing since the Pie update. So if I try to reflash stock firmware it just complains that everything is locked.
Is there any way to get it into a flashable state without booting into the OS, or am I just screwed?
Related
Nexus 5x h790 - Android 6.0.1
Some day he restarted and frozen in Google Logo. I just access the Bootloader Mode, recovery and Download mode don't run.
The problem is I can't into in Android settings, so I can't enter in developer options, OEM unlock is not allowed and USB debugging to. Because this I can't unlock my bootloader in Fastboot mode. I try use NRT but for solving my problem I need unlock my bootloader and my OEM is not activated.
Yesterday I read some topic that talking about let the device restart several times, for my surprise this worked and enter in the initiation process of Android, but is not everytime that works and is too longer to wait this miracle happens.
Please help me with this problem I don't know what I do now.
Sorry for my English I am from Brazil
Most likely you have a hardware problem.
You can try sideloading the FULL OTA using adb sideload and recovery, but you said you can't get into recovery. I am not sure if you can't get into recovery, ever, or just can't get in most of the time, but sometimes you can. If latter, try adb sideload of FULL OTA.
Bootloader is useless if you can't unlock it.
The last option is to use LGUP and the TOT file, but I think you mentioned not being able to get into download mode.
Keep in mind if you flash the TOT file, it doesn't come with a vendor partition, so it is likely you'll get some error during startup. What I would do is immediately go to developer options and enable OEM unlocking, then go to bootloader and unlock, then flash a full factory image that includes the vendor you need.
That's pretty much your options.
Regarding to title, I was trying to flash a custom rom on my Honor 7X but apparently with the crazy amount of idk twrp recoveries and failed flashes, the phone (totally empty with both system and data) decides to factory reset lowlevel after i try to fastboot oem relock bootloader and it stays stuck at 99%. Any troubleshooting tips would be great.
Well, am experiencing similar problems.
I was on rooted Stock, when I got a System update available prompt.
I uninstalled Magisk, Flashed stock recovery and did a Factory reset from the Stock recovery.
It booted up, but there was no Keyboard installed. I think, I had uninstalled the pre-installed one when I was rooted.
I couldn't get past the Setup Wizard, as the FRP was Locked and there was no way of typing the password.
I tried to flash the system.img from fastboot but it gave me 'Remote: command not allowed' error. (Even for flashing recovery)
I google'd a bit and ended up on a solution as to relock the bootloader, Turn on OEM Unlocking and lock the bootloader again.
I relocked the bootloader, it did a 'Low-level factory reset' and now the phone is even bootloop. (it boots into eRecovery from the Honor/Huawei logo)
I tried the 'Download latest version and recovery' from eRecovery. It's giving me 'Package verification failed' error.
'dload' method never worked for me, and it is still the same.
Any solution/suggestion?
Bootloader relock with empty system is a definite hard brick.
I think you may need to ues dload method and flash a service rom to get back up and running.
dload says software install failed, any ideas? @mrmazak
apparently now its back to usual after leaving it stuck at 99% overnight until the battery dies out, could go back to fastboot and stuff
How far did it get? Stop and fail at 5% happens when update not found or not correct update.app.
Of it loads higher that 5% then fails , that's probably not gonna be able to fix it.
We have only found 2 service roms. Both are bnd-l21c432 one is Nougat one is Oreo. Both have been used on other versions of honor 7x. But after it runs you need to run hurupdater or hwota with correct model / region fullOTA.
My girlfriend has a OnePlus 3T and is stuck on Oxygen OS 5.0.4, and it doesn't matter if I download the update via the update settings or install it locally or via adb, or use twrp to flash it, I tried all those ways.
Regardless, the update fails every time. I also tried deleting the ota folder, and rebooting her phone to recovery and deleting cache... that doesn't work either. I also tried using adb and typing in - adb reboot "dm-verity enforcing" - still nothing.
I also used the toolkit from here:
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
and I tried to lock the bootloader. It took me hours to figure out how to get the bootloader unlocked again, cause I had to enter a password to get in, and at the time my girlfriend had no password on her phone at all.
After I figured out about unlocking the bootloader again, I made a password in the security setting, re locked bootloader, still nothing. The password works while phone's bootloader is unlocked, but not while it's locked.
I made a video to further explain and show the situation.
https://www.youtube.com/watch?v=YBtQW00JsNU
Still nothing?
DranzerX13 said:
My girlfriend has a OnePlus 3T and is stuck on Oxygen OS 5.0.4, and it doesn't matter if I download the update via the update settings or install it locally or via adb, or use twrp to flash it, I tried all those ways.
Regardless, the update fails every time. I also tried deleting the ota folder, and rebooting her phone to recovery and deleting cache... that doesn't work either. I also tried using adb and typing in - adb reboot "dm-verity enforcing" - still nothing.
I also used the toolkit from here:
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
and I tried to lock the bootloader. It took me hours to figure out how to get the bootloader unlocked again, cause I had to enter a password to get in, and at the time my girlfriend had no password on her phone at all.
After I figured out about unlocking the bootloader again, I made a password in the security setting, re locked bootloader, still nothing. The password works while phone's bootloader is unlocked, but not while it's locked.
I made a video to further explain and show the situation.
https://www.youtube.com/watch?v=YBtQW00JsNU
Click to expand...
Click to collapse
I watched your video,
Before you relock the bootloader you must install the stock recovery for your device, you can't relock while TWRP is installed, use this guide, (read the guide once completely before you start).
https://forums.oneplus.com/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Also make shure you use the latest ADB drivers Inside (SDK Platform-Tools) from google:
https://developer.android.com/studio/releases/platform-tools
Good Luck!
It worked like a charm. Thank you!
Long story short, I ended up with a classic bootloop (shows boot animation continuously) from messing around with Magisk modules, so I did a wipe from recovery, still bootloop, so I tried reverting completely to stock with the OEM downloads. I tried flash_all_except_storage.bat, and flash_all.bat, but this time it was a different bootloop. The phone shows the Android One logo, the screen flickers like it's going to the boot animation, but then it just goes back to the Unlocked Bootloader Warning Screen, then the Android One logo, and loops like that. I dumbly thought locking the bootloader, reflashing everything, and starting over like it were a new phone would fix the issue, so I did flash_all_lock.bat, but now I'm just stuck with this weird bootloop and a locked bootloader. Trying to unlock the bootloader with fastboot just gives me "oem unlock is not allowed", so I'm at a loss here.
Does anyone know of anything else I could do, or is this a hard brick?
With a locked bootloader EDL flash probably is your last chance.
Maybe this thread helps:
https://forum.xda-developers.com/mi-a2-lite/help/hard-bricked-mi-a2-lite-help-to-enter-t3862648
thorin0815 said:
With a locked bootloader EDL flash probably is your last chance.
Maybe this thread helps:
https://forum.xda-developers.com/mi-a2-lite/help/hard-bricked-mi-a2-lite-help-to-enter-t3862648
Click to expand...
Click to collapse
I got stuck with a similar problem and that was the only option, to boot into EDL mode you will need to partially dissasemble your device and flash the image via fastboot or via MiFlash (download the latest version as I had problems with an older one). Since that incident I kept the bootloader unlocked just in case something happens.
I had the phone booted into EDL mode and attempted to flash the stock ROM (10.0.3.0) with MiFlash, but it errored out with an ERROR_UNSUPPORTED_TYPE. I tried with the previous version, 10.0.2.0 and it worked for some reason. That fixed it though, so thanks! I've been lightly tinkering with rooting android phones a few years now, but until encountering this issue, I'd never heard of EDL mode. You learn something new every day? ?
I have the same issue with my nephew 's mi a2 lite which has the bootloader locked.
It only shows the android one logo.
I cannot go to recovery mode, but I can go in fastboot.
Changing from "a" to "b" doesn't solve anything and being the bootloader locked is not possible to flash anything from fastboot.
So I've opened the device and I've short circuited the edl pinpoint to be able to flash with MiTool (I've used an old version since more recent ones gave errors when flashing).
I was able to flash both the latest official ROM and the oldest one which I've found ( daisy_global_images_V11.0.14.0.QDLMIXM_10.0 and daisy_global_images_V9.6.4.0.ODLMIFF_8.1 respectively).
In both cases the device still is "frozen" with the android one logo when I've tried to turn it on after the flashing procedures gave me a successful status.
What else can I do?
Must be rusty in my old age, but I dont remember having any of these issues back with my previous android phones... the 11 is my first new one since the 6T though.
Whats my situation:
Phone boots into fastboot, attempts to boot to recovery, or continue, or restart all end back at fastboot. Can issue fastboot commands, but all roads seem to lead back to fastboot.
How I got here:
When I first got my phone, I unlocked the bootloader via fastboot command, but for some reason my phone wouldn't let me set a pin. Be it numeric, alphanumeric, or pattern, it would never let me confirm after putting it in the second time, and consequently I couldn't register a fingerprint or face scan. Reddit suggested that this sometimes happens after bootloader unlock but can be resolved by re locking and unlocking again... ok fair enough, haven't done much yet, whats another factory wipe.
fastboot flashing lock command - finished, boots straight back to bootloader
fastboot flashing unlock command - finished, ok time to try booting through to see if it fixed the problem... stuck in fastboot.
I'm rusty enough to want to stop here and seek guidance before I further brick my phone. I have fastboot access so in theory I should be able to flash an image from here? Any guidance would be appreciated. I'll admit I've fallen off the scene hard (new baby, job etc) and perhaps I should have just left my phone locked... but habits die hard eh?
You can only flash the full rom /images with unlocked bootloader
With locked bl you becomes the messages
Flashing on locked states not allowed
did you flash a patched init_boot.img after your first unlock?
benhc911 said:
Must be rusty in my old age, but I dont remember having any of these issues back with my previous android phones... the 11 is my first new one since the 6T though.
Whats my situation:
Phone boots into fastboot, attempts to boot to recovery, or continue, or restart all end back at fastboot. Can issue fastboot commands, but all roads seem to lead back to fastboot.
How I got here:
When I first got my phone, I unlocked the bootloader via fastboot command, but for some reason my phone wouldn't let me set a pin. Be it numeric, alphanumeric, or pattern, it would never let me confirm after putting it in the second time, and consequently I couldn't register a fingerprint or face scan. Reddit suggested that this sometimes happens after bootloader unlock but can be resolved by re locking and unlocking again... ok fair enough, haven't done much yet, whats another factory wipe.
fastboot flashing lock command - finished, boots straight back to bootloader
fastboot flashing unlock command - finished, ok time to try booting through to see if it fixed the problem... stuck in fastboot.
I'm rusty enough to want to stop here and seek guidance before I further brick my phone. I have fastboot access so in theory I should be able to flash an image from here? Any guidance would be appreciated. I'll admit I've fallen off the scene hard (new baby, job etc) and perhaps I should have just left my phone locked... but habits die hard eh?
Click to expand...
Click to collapse
You need to re-unlock the bootloader in the original china ROM!
I can help you if you get stuck on this issue ! pm me! !
I did indeed reunlock the bootloader. I imagine the issue possibly when I was attempting to root by patching a boot img with magisk and flashing that... Although after doing that my phone seemed to operate fine.
Regardless I reflashed the original, and it seemed to still bootloop into fast boot.
I tried relocking the bootloader, going to recovery, etc. After some degree of insanity doing seemingly the same thing I got to stock recovery, and then back to bootloader then back to recovery, then it flashed me writing in Chinese and it booted normally.
Since then I've rebooted my phone with no issue.
Not sure what exactly happened to make it conditionally work/not work... But given the time I wasted on it and the infant I'm having strong second thoughts about bothering with an unlocked bootloader. I'm clearly not in my element anymore as my confidence of which files to flash and commands to do so was very low (hence the post). My initial suspicion was "I have fast boot I can just flash original rom and I'm back to square one at least" but was too "afraid" to proceed and brick my new phone.
To expand on the "why bother with unlocked bootloader", I feel like it's been 3 phones since I truly took advantage of unlocking my bootloader. Perhaps I need to read more about the current state to see if there is a value proposition for me, or if I'm just creating more work (to then root, magisk, TWRP, safetynet, windvine etc)
Same happened to me,
Possible solution:
I used fastboot enhance to flash the payload.bin all over again, after it finished it rebooted into fastbootd automatically, then I falshed the same payload.bin into fastbootd as well then it rebooted into system smoothly.