[SOLVED] Stuck on "Your device has been unlocked" - Nextbit Robin

This is my first time attempting to flash a ROM but I haven't even got as far as getting to TWRT. I have followed these instructions...
wiki DOT lineageos DOT org SLASH devices SLASH ether SLASH install
....up to flashing TWRP onto the phone. Attempting to reboot into recovery per the next instruction, the phone's screen hangs on:
Your device has been unlocked and Nextbit OS can't be checked for tampering.
Your device will continue booting in 5 seconds.
Fine, except it does not continue booting. The screen is frozen, and neither pressing nor long holding either the power button or either of the volume buttons does anything. `adb devices` in a terminal does not see the phone, so I can't force a reboot that way. What's my next step?

Solved
The solution was easy, though it took a while to find it. Long pressing vol down + power for several seconds took me to fastboot, and I was able to continue from there.

how did you continue cuz i am not able to restart the device or access it from ADB

truescout said:
how did you continue cuz i am not able to restart the device or access it from ADB
Click to expand...
Click to collapse
the same problem, did you fix it?

Sometimes, you need to press vol down + power for about a minute to reboot.

Related

[Q] I can't access Bootloader or Recovery PLEASE Help!

My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
SF-Echo18 said:
My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
Click to expand...
Click to collapse
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
BerndM14 said:
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
Click to expand...
Click to collapse
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
SF-Echo18 said:
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting on device for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
Click to expand...
Click to collapse
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
BerndM14 said:
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
Click to expand...
Click to collapse
I held Volume Up + Power Button and it showed the white screen with the green HTC logo. I then released all buttons. Once the screen turned off I then held Volume Down + Power Button for two minutes straight and nothing happened.
Even though we haven't found a solution yet, I am appreciative of the help.
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Just remember to change directory in command prompt to the folder where adb.exe is located.
I don't know why the device doesn't reboot into bootloader though when you hold volume down + power button, shouldn't have to hold it for 2minutes. Holding volume up + power button to simulate a "pull" should only take up to 20 seconds or so at most and pressing volume down + power will then immediately take you into bootloader mode, or at least it's supposed to.
Did you release the volume up / power combo when the screen went dead or before? Try holding it until the phone shuts off and then right away press volume down + power.
Sorry if I'm not answering right away though, busy eating, and will be here and away for the next hour or so while I get ready for work =o( once I leave for work I'll only be able to help some more after like 2 hours or so. Hopefully we can do something before then though =o)
wase4711 said:
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Click to expand...
Click to collapse
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
SF-Echo18 said:
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
Click to expand...
Click to collapse
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
BerndM14 said:
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
Click to expand...
Click to collapse
Indeed I appreciate it, but I just finished installing the RUU ha. Hopefully this thread will be of use to someone in a similar circumstance in the future.
Share another method of getting into recovery mode on non-responsive blank screen
Hi,
I just want to share how I accessed recovery mode with the same build.prop issue but with S-ON (might work with S-Off too).
I found the solution from here:
http://forum.xda-developers.com/htc...ter-download-mode-t2853100/page2#post62490577
To get into recovery mode on a non-responsive blank screen, hold the power button and volume up button at the same time and then approximately after 10 seconds, switch from pressing the volume up to volume down button before the HTC logo white screen shows while still holding down the power button. After, a white boot screen will give an option to go into recovery mode.

help Zenfone 2 black screen, no bootloader or TWRP vibrartes twice and nothing

Hello
I was updating from a M version to another M verions. But I had to use the temporary recovery method.
This is what I was doing but didn't finish properly
Requirements:
1. Unlocked bootloader
2. TWRP for Z00A (Download | How to Install TWRP)
Unlock Bootloader on Android 6.0 Marshmallow ZenFone 2 ZE551ML/ZE550ML
Download tool (Download Here)
1. Extract it and connect Zenfone 2 with laptop/pc
2. Click unlock.bat will automatically detect whether the adb or fastboot mode, and then reboot into bootloader
3. Will appear on the screen to unlock the success of mobile phones after five seconds will reboot, then hold volume up the phone automatically re-boot back to bootloader.
4. If you missed the previous step, press the power button for 10 seconds off, then press the "Volume Up" and hold the power button to boot into bootloader.
5. After the phone has successfully re-enter the bootloader, click restore.bat on the computer, where the restore refers to the restore Android ifwi 6.0 otherwise Android phone can not enter the system.
6. The phone will reboot and restore white on black ASUS logo screen, and then enter the Android system.
Click to expand...
Click to collapse
I extracted and connect my zen2
Ran the unlock.bat
The phone entered the bootloader, flash his things and boot again but on the white screen
Then I had to hold power button 10s to turn it off and turn it on again
Entered the bootloadr by holding Power+Vol UP then to recovery.
At this time I just used the recovery as I usualy do, Wipe everything, cache, data, etc.
Connect to the PC, put the new UL-Z00A-WW-4.21.40.184-user.zip there and flash.
BUT now that comes the problem. I select the option to boot it after finish flashing.
So obviously I didnt finish the steps mentioned on the quote above.
I didnt ran the restore.bat before reboot into system and now All I see is black screen.
I've tryed some steps of those tutorials for briked phones but My computer can't see the device for long enough
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
I try to do those steps but I'm stuck on this part
now back to the Zenfone 2, hold power for 20 seconds to shutdown, then press simultaneously the key "power" + "volume down", until phone vibrates. Or computer makes detection sound, wait a few seconds it will add an item immediately below intelSoC in device manager “MOOREFIELD” new devices is successful.
Click to expand...
Click to collapse
My phone doesn't boot even on bootloader. It just vibrate twice and then nothing happens.
On my device manager I can see the "Moorefield" but only for a brief moment. when I try to turn on the phone then it immediately disapears and repeat this process (Vibrate twice, long preiod doing nothing and still black screen, then vibrates again twice, repeat)
Any suggestion?
Thanks in advice
Seikushim said:
Hello
I was updating from a M version to another M verions. But I had to use the temporary recovery method.
This is what I was doing but didn't finish properly
I extracted and connect my zen2
Ran the unlock.bat
The phone entered the bootloader, flash his things and boot again but on the white screen
Then I had to hold power button 10s to turn it off and turn it on again
Entered the bootloadr by holding Power+Vol UP then to recovery.
At this time I just used the recovery as I usualy do, Wipe everything, cache, data, etc.
Connect to the PC, put the new UL-Z00A-WW-4.21.40.184-user.zip there and flash.
BUT now that comes the problem. I select the option to boot it after finish flashing.
So obviously I didnt finish the steps mentioned on the quote above.
I didnt ran the restore.bat before reboot into system and now All I see is black screen.
I've tryed some steps of those tutorials for briked phones but My computer can't see the device for long enough
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
I try to do those steps but I'm stuck on this part
My phone doesn't boot even on bootloader. It just vibrate twice and then nothing happens.
On my device manager I can see the "Moorefield" but only for a brief moment. when I try to turn on the phone then it immediately disapears and repeat this process (Vibrate twice, long preiod doing nothing and still black screen, then vibrates again twice, repeat)
Any suggestion?
Thanks in advice
Click to expand...
Click to collapse
you must post question in the thread you are trying instead of making new one. any ways. long press power button to shut down the device completely. then press power button and volume down button. as phone vibrates release power button but keep holding volume down button and wait till moorefield appears in device manager. now release the volume button then click begin download in xfstk.
if u have further question post in in above thread you are following to unbrick
sukhwant717 said:
you must post question in the thread you are trying instead of making new one. any ways. long press power button to shut down the device completely. then press power button and volume down button. as phone vibrates release power button but keep holding volume down button and wait till moorefield appears in device manager. now release the volume button then click begin download in xfstk.
if u have further question post in in above thread you are following to unbrick
Click to expand...
Click to collapse
I did it already and only shows up for a brief moment like I said and then disappears a second before the phone vibrate
help please D:
Seikushim said:
help please D:
Click to expand...
Click to collapse
any luck fixing? i got the same result, no screen or anything, two vibrations since yesterday
Sadly, no.
no fix for me yet...
Let me know if you find something
You have tô unbrick your phone. There are some tutorials in the forum
I am using the Z008D variant of the Zenfone 2.
I had bricked my phone 3 times and the guides that had helped me are:
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
https://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
I too had the same problem the first time I unbricked my phone. The moorefield device would show up briefly in device manager. It is stated in the guide that you had to press power+vol down when connecting the phone to use xFSTK. I googled and found that you had to actually press and hold the vol down button only and then connect the USB cable, then release it when the moorefield device is detected.

op3 keeps rebooting

hi all
i need a little help here
i have a op3 it wont turn of
wen i hit power buttom for 12 sec it just start again an load start screen
then after 2-3 sec it reboots again
if i hold power an volume + it goes to fastboot screen stay there for 3-4 sec an then reboots again
an i cant use volume buttoms to select
they work because i can hit volume + an it enter fastboot
deleted
nobody ???
Same here
This same issue is happening with me. Were you able to fix it?
anand.deshpande84 said:
This same issue is happening with me. Were you able to fix it?
Click to expand...
Click to collapse
yes it was the power buttom
u have ro push it hard to get it to stop rebooting
Alternate method to get the phone back
Well, out of desperation, I did the following:
1. Keep fastboot and twrp recovery ready
2. Type in the fastboot recovery command in prompt
3. Press volume up and power button.
4. As soon as I get the fastboot screen, quickly connect your phone to the PC
5 As soon as you hear the new device connection music press enter on the command prompt
steps 4 and 5 should be completed within 5 seconds ?
Repeat steps 1 to 5 couple of times until you get the timing right.
Finally it worked for me on third attempt and I got my phone back ?
Once it booted normally I went back to the recovery, wiped the caches, ran diagnostic and repair disk tools nothing came out of the ordinary.
Hope it helps anyone with same problem..

No access to bootloader or recovery after a custom ROM install attempt

Hi everyone,
So yeah, I probably shouldn't have played around with recovery, bootloaders and custom OS, but my XZ2 Compact was rendered nearly useless by the last Android update, so I tried to install the new official Lineage OS on it. But I failed. Hard.
Symptoms
The phone now only reacts to the power button. When I press it, it displays a battery charge icon for a minute or two, then the screen turns off.
None of the other physical buttons do anything, and the button combinations don't work. As a result, I can't boot to recovery, or even access to fastboot.
The light indicator is on and red.
I let the phone drain its battery, see what happens, and well, nothing. Eventually the screen stops turning on. When I replug the phone, even if I don't touch anything, it will end up showing me the battery icon again, and is stuck in the same loop.
'adb devices' still sees my phone, but with no permissions. 'fastboot devices' doesn't see anything.
On Windows, Emma (Sony's flashing tool) doesn't see the device.
Causes
I was following this tutorial. I went up to "temporarily booting a custom recovery using fastboot". I used the latest LineageOS recovery for my phone, and the flashing worked fine according to the output of the fastboot command. But that's all. Impossible to do anything after that.
Do I now own a glorified paper weight? Or can I save this?
Thanks!
SOLVED! I managed to stop the charging loop with a key combination I discovered: volume up + volume down + power for about 10s. Then was able to load the bootloader and re-flash a recovery, custom ROM etc. Thank you all for your help.
Have you tried to hold vol+, vol- and power button all together for (at minimum) a minute?
I would then try to restore stock firmware with newflasher (you'll find it using Google search or here on xda).
Great, thanks a lot I didn't know this key combination and it allowed me to get out of that charging loop and start the bootloader. Problem solved!
Nice, glad to hear!

How to reliably start TWRP

I have TWRP installed, and have managed to run it a few times. Now I cannot start TWRP at all.
From off, if I switch on, the following happens:
1) Screen with Samsung Galaxy A70 - Secured by Knox
2) 0.5 seconds later another screen, "this phone's bootloader is unlocked and it software integrity. .." and "press power key to continue..."
3) 5 seconds later, same screen as (1)
4) 3 seconds later, red letters "this phone is not running Samsung's official software"
5) 3 seconds later blank screen with "samsung" and then booting to android.
In my experience I have to flash twrp every time I want to use it( I don't know the reason but I couldn't fix it ) , for booting twrp on the other hand I turn off the phone first, then I press power button+volume down until the "this phones bootloader..." screen appears, here is the tricky part, you have to quickly let go of these two buttons, press power button, let go of the power button (after the warning disappeared) and then press volume down button (and hold it) until twrp logo appears, this happens really fast so you may need to do it a few times to get used to it.
mobin22 said:
In my experience I have to flash twrp every time I want to use it( I don't know the reason but I couldn't fix it )
Click to expand...
Click to collapse
Yes, same here, the only time I have managed to run TWRP on this phone, is right after a flash.
mobin22 said:
and then press power down button
Click to expand...
Click to collapse
Do you mean volume down?
Zilliman said:
Yes, same here, the only time I have managed to run TWRP on this phone, is right after a flash.
Do you mean volume down?
Click to expand...
Click to collapse
Power off the device, plug into a pc, wait for it to start charge, hold vol up and power till it turns on. Wala boots to twrp. If you have magisk installed,you can use the reboot option within magisk.
mobin22 said:
In my experience I have to flash twrp every time I want to use it( I don't know the reason but I couldn't fix it ) , for booting twrp on the other hand I turn off the phone first, then I press power button+volume down until the "this phones bootloader..." screen appears, here is the tricky part, you have to quickly let go of these two buttons, press power button, let go of the power button (after the warning disappeared) and then press volume down button (and hold it) until twrp logo appears, this happens really fast so you may need to do it a few times to get used to it.
Click to expand...
Click to collapse
Samsung changed how to enter recovery on Android 11. Power off device, plug into pc, wait for it to charge, then hold vol up and power till it turns on. Alternatively, if you have magisk installed, use the reboot options within magisk.
I did that. Thanks!
But it has gone to:
Android Recovery
Samsung /a70qxx/a70q
11/RP1A.200720.012./A705FNXXUB5DVB3
user/release-keys
Use volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe date/factory reset
...
...
...
Where is TWRP? It seems it's gone.
Zilliman said:
I did that. Thanks!
But it has gone to:
Android Recovery
Samsung /a70qxx/a70q
11/RP1A.200720.012./A705FNXXUB5DVB3
user/release-keys
Use volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe date/factory reset
...
...
...
Where is TWRP? It seems it's gone.
Click to expand...
Click to collapse
That's because you're not installing it properly go back to my guide and follow it exactly and stop listening to these other people. I've been modding this device since it first came out with Android 9, I know every inch of this device. You're getting confused by what other people are telling you
MarvinMod said:
5- Press and hold vol down and power till the screen turns blank then immediately press and hold vol up. The device will reboot then land you in the twrp splash screen
Click to expand...
Click to collapse
It fails here, on this step. After successful flash of recovery.tar, power + vol down to reboot, cable still connected, nothing you can do now can bring TWRP up. The phone boots into Android.
EDIT: I think I have now got it. I will update in a few mins.
Zilliman said:
It fails here, on this step. After successful flash of recovery.tar, power + vol down to reboot, cable still connected, nothing you can do now can bring TWRP up. The phone boots into Android.
EDIT: I think I have now got it. I will update in a few mins.
Click to expand...
Click to collapse
After successful flash of recovery.tar, power and vol down to reboot, as soon as the phone screen goes blank, immediately release all keys and press and hold vol up. Must be as soon as screen goes blank. The device will then reboot twice and land you in twrp splash screen. You must hit vol down and power after successful flash then when screen blanks, vol up. If you miss this step, twrp will not hold and revert back to stock recovery.
Here is the notes I made today:
****************************************************************
INSTALL + START TWRP
phone is off
press up + dn
insert cable
go into download (press up)
ODIN 3.14 + AP:tar(vbmeta.img+twrp.img), auto reboot off, press upload
when it succeeds, press dn + pwr until it reboots
then quickly up + pwr until it starts (no need to hold down)
this starts in TWRP
from powered off
press pwr button
goes into twrp or android(system) -- depending on what was used last time
if we used reboot->system last time it will now **Always** go into system!
to go back into twrp:
switch off
power cable until charge
pwr + up until it starts
****************************************************************
The above means that you CANNOT go back to TWRP unless you have a cable and a PC near by.

Categories

Resources