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.
Related
deleted
AkyrXX said:
So I was attempting to unlock the bootloader using GNex Toolkit, which I now know I never should have done. After supposingly unlocking the bootloader, the Google screen would show up for about 10, then the phone would reboot itself. I decided to let it run its course and see if it would fix itself, but after doing this for about 30 minutes, I figured it wasn't going anywhere. So that's when I (also against my now better judgement) tried to relock/OEM restore using GNex toolkit. Well it wouldn't unlock, and the boot issue still exists. So then I started digging, and found efrant's wonderful guide on restoring my apparently soft-bricked device. However, even this did not fix the issue. I have tried locking the bootloader through fast boot, and while it will say that the bootloader has been locked, upon restart it was still unlocked and still having the boot issues. I even ventured as far as doing a ODIN reboot, but still same issue. I have since tried efrant's again, but still the same issues. I have access to fastboot and ODIN, and recovery, although I have not messed around there too much as I have not been able to find any information about that. At this point, I am all out of ideas on what to do. Just some last bits of info.
I was doing this all on a very freshly installed Jelly Bean update. This particular phone has never been rooted or unlocked. I don't really care about having it rooted or unlocked at this point, I just want a working phone.
Please feel free to make any remarks toward my past actions of using toolkits, as I have now since found the light, and any additional advice would greatly be appreciated.
Click to expand...
Click to collapse
The difficult part now is to understand where did the toolkit fail.
If you ran through the process manually again, and it still bootloops..Have you tried erasing first, then reflashing?
Code:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
also, while it's bootlooping, is logcat already running? That could allow some more insight on what's happening.
deleted
I've got quite a problem.
A few weeks ago, I unlocked the bootloader on my phone and flashed SuperSu to root it.
Today I decided to lock it back for personal reasons, wiping everything.
After it wiped, the phone kinda softbricked. When it turns on the OnePlus logo flashes for a second and turns off.
Won't let me unlock bootloader again, got stock recovery. Tried to use sideload, but ADB can't read the file. My guess it's too large.
What can I do?
I had same problem. Follow the steps. Unlock it again and reboot to the system.
There enable developer option, enable debugging, enable unlock bootloader option.
Rebooted to fastboot mode
Install stock recovery
Adb sideload 3.2 full firmware.
After that reboot your phone to fastboot mode.
Unlock bootloader.
This should do it.
Sent from my ONEPLUS A3003 using Tapatalk
It's like you didn't even read what I wrote...
I said it doesn't boot to system, OnePlus logo appears for a split second and phone turns off.
Bootloader is locked and I cannot flash anything.
ADB Sideload won't read files. Gives the 'cannot read' error.
You know that you can load to bootloader by pressing volume up and power button right?
Sent from my ONEPLUS A3003 using Tapatalk
Monskiller said:
I've got quite a problem.
A few weeks ago, I unlocked the bootloader on my phone and flashed SuperSu to root it.
Today I decided to lock it back for personal reasons, wiping everything.
After it wiped, the phone kinda softbricked. When it turns on the OnePlus logo flashes for a second and turns off.
Won't let me unlock bootloader again, got stock recovery. Tried to use sideload, but ADB can't read the file. My guess it's too large.
What can I do?
Click to expand...
Click to collapse
You should be fine so long as you didn't deactivate the"OEM UNLOCK " option from the developer setting....
do the following
1. press and hold the volume up an power buttons simultaneously to enter the boot loader menu.
2.select start option from the bootloader menu sorry that menu is the boot loader.
3. now connect to pc and use the "fastboot devices" command to see if your pc recognizes you op3 as an android device.
4.type "fastboot oem unlock"
5. flash the custom recovery thru fastboot
5. enter custom recovery and flash your desired rom.
hope this works for you!
ajaysoranam said:
You should be fine so long as you didn't deactivate the"OEM UNLOCK " option from the developer setting....
do the following
1. press and hold the volume up an power buttons simultaneously to enter the boot loader menu.
2.select start option from the bootloader menu sorry that menu is the boot loader.
3. now connect to pc and use the "fastboot devices" command to see if your pc recognizes you op3 as an android device.
4.type "fastboot oem unlock"
5. flash the custom recovery thru fastboot
5. enter custom recovery and flash your desired rom.
hope this works for you!
Click to expand...
Click to collapse
And if by mistake I have deactivate the "OEM UNLOCK " what can I do?
I relocked the bootloader. Which wiped to factory reset.
That wipe deactivated the ability to unlock bootloader until reactivated from the system, which I cannot get to because the phone turns off/bootlops before loading it.
This happened quite a few times on this forum, there is really no reason to relock the bootloader on the op3, it is covered through warranty, but u will have to contact oneplus and they should walk u through and send u files to unbrick it if u r lucky
ovidiu1982 said:
And if by mistake I have deactivate the "OEM UNLOCK " what can I do?
Click to expand...
Click to collapse
then you better get in touch with the op customer service. they will, from what i know, fix it thru a remote connection sitting.
I have no solution for you, but I wonder if you went back to stock recovery first before you relocked the bootloader? I think if you have TWRP and try to relock the bootloader, this happens. NOT that its helpful to you, but if this is the case and you can verify it, might help others avoid making the same mistake.
As far as your problem is concerned, I would look for unbricking guides. I know I saw at least one guide that lets you recreate the entire partition table manually and make it just like new for the OP2 (and has the company's blessings to do so). So it should apply here as well. Sorry, do not remember where I saw this, but must have been either on xda or the oneplus forums.
karthikrr said:
I have no solution for you, but I wonder if you went back to stock recovery first before you relocked the bootloader? I think if you have TWRP and try to relock the bootloader, this happens. NOT that its helpful to you, but if this is the case and you can verify it, might help others avoid making the same mistake.
As far as your problem is concerned, I would look for unbricking guides. I know I saw at least one guide that lets you recreate the entire partition table manually and make it just like new for the OP2 (and has the company's blessings to do so). So it should apply here as well. Sorry, do not remember where I saw this, but must have been either on xda or the oneplus forums.
Click to expand...
Click to collapse
I have stock recovery. I did boot TWRP first and let it change system by mistake, but reflashed stock later. That's what might have caused the bootloop once I relocked.
So I guess if you decide to relock in the future, don't flash TWRP, cause it bootloops, even if stock is reflashed.
Bro don't worry now.
I am gonna guide you out of this.
First install an adb package like this.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Now get a toolkit like this.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Try to connect to fastboot and check for your device in the toolkit.
If failed then kill process adb in your task manager.
Now once connected.
Check OEM status and bootloader status.
Unlock if required.
Now.
Push twrp to your phone .
Then boot into it through the toolkit.
Now load a full ROM.
http://forum.xda-developers.com/oneplus-3/development/rom-op3lite-debloated-tweaked-fast-t3404996
Just copy paste it using your file manager on PC.
Them flash first make it boot and then root.
Hope this helped.
Monskiller said:
I have stock recovery. I did boot TWRP first and let it change system by mistake, but reflashed stock later. That's what might have caused the bootloop once I relocked.
So I guess if you decide to relock in the future, don't flash TWRP, cause it bootloops, even if stock is reflashed.
Click to expand...
Click to collapse
Nah, I think this happens only if you let TWRP modify the system partition. But, I have not and am not willing to test it out
karthikrr said:
Nah, I think this happens only if you let TWRP modify the system partition. But, I have not and am not willing to test it out
Click to expand...
Click to collapse
Don't test it. I've already done it by mistake.
It replaced recovery with TWRP by allowing the modification of system and even after reflashing stock it'll bootloop on relocking recovery.
So I found something useful then.
Hey, i think i found a solution for you. I don't know if i can post here xda thread links, so search "EDL Mode xda" on Google and the first link it is. Hope i helped
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?
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?
Hello,
I usually come here to root my phone and choose the best ROM, but this time I'm here because of a problem with the official ROM. I did a simple OTA android update this weekend, and the phone never restarted. There was enough battery so nothing to report during the install. I'm stuck on an infinite bootloop and the recovery commands take me to a no command.
Beyond having lost all my data, I'm worried because no command is working. I have already followed all the tutorials on youtube (including the most improbable techniques of hitting the back of the smartphone or putting it in the freezer for 10min, I know it's stupid, but when you're desperate you try everything).
So I'm coming here to ask for your help, hoping that someone will give me a solution to at least flash a basic image and start over.
Regards
Thiiibs said:
Hello,
I usually come here to root my phone and choose the best ROM, but this time I'm here because of a problem with the official ROM. I did a simple OTA android update this weekend, and the phone never restarted. There was enough battery so nothing to report during the install. I'm stuck on an infinite bootloop and the recovery commands take me to a no command.
Beyond having lost all my data, I'm worried because no command is working. I have already followed all the tutorials on youtube (including the most improbable techniques of hitting the back of the smartphone or putting it in the freezer for 10min, I know it's stupid, but when you're desperate you try everything).
So I'm coming here to ask for your help, hoping that someone will give me a solution to at least flash a basic image and start over.
Regards
Click to expand...
Click to collapse
Since you can get into bootloader and it's locked, go to platform tools and unlock the bootloader. Then you can flash the factory image and proceed from there. This will wipe data.
The other image is the screen prior to entering recovery via pressing power button and vol up.
I would recommend turning on USB debugging first thing when getting any phone.
Android Flash Tool
flash.android.com
The No Command Screen is normal. You just need to press and hold the Power Button and while doing, so press and release the Volume Up key (after about 5 seconds) and then release the Power key as well. This will take you to stock recovery. From there, you could sideload the OTA package [works on a locked bootloader as well] but as already told in a post just above mine, you need to have enabled USB Debugging beforehand.
The bootloader is locked but you can access it, so go to platform tools and unlock it. After that, you can flash the factory image and carry on. It will erase all data.
To sideload an OTA in stock recovery you shouldn't need to have USB Debugging enabled. Being in sideload mode enables a very limited set of ADB commands on Pixels, including adb sideload <imagename>.zip. I'm not aware that this has changed.
To unlock your bootloader you will need to have OEM Unlocking enabled in Developer Options beforehand.