boot stuck at "fastboot menu" and "This build is for development purposes only."
After flashing recovery , whatever how many time reboot it ,my phone stuck at "fastboot" menu.
When I click "recovery", Red information "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission." was flashing then back to menu again.
Any advise?
Thanks~~
flyingcowboy said:
After flashing recovery , whatever how many time reboot it ,my phone stuck at "fastboot" menu.
When I click "recovery", Red information "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission." was flashing then back to menu again.
Any advise?
Thanks~~
Click to expand...
Click to collapse
I think you need to unlock bootloader
gss93 said:
I think you need to unlock bootloader
Click to expand...
Click to collapse
Do you mean the pic below?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://drive.google.com/open?id=0B98TI8vzkIzCUkJPNEV1TGlRZ3M
flyingcowboy said:
Do you mean the pic below?
https://drive.google.com/open?id=0B98TI8vzkIzCUkJPNEV1TGlRZ3M
Click to expand...
Click to collapse
Never mind it looks like it is already unlocked based off of the picture. Have you flashed/reflashed TWRP or CWM?
gss93 said:
Never mind it looks like it is already unlocked based off of the picture. Have you flashed/reflashed TWRP or CWM?
Click to expand...
Click to collapse
Yes I tried them both still same
flyingcowboy said:
Yes I tried them both still same
Click to expand...
Click to collapse
Sorry someone more experienced will probably have to help you. I did loose recovery once i had to flash a couple of different times. I tried locking and unlocking boot loader then it eventually worked. What command are you using to flash TWRP/CWM fastboot flash recovery (Name).img?
gss93 said:
Sorry someone more experienced will probably have to help you. I did loose recovery once i had to flash a couple of different times. I tried locking and unlocking boot loader then it eventually worked. What command are you using to flash TWRP/CWM fastboot flash recovery (Name).img?
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
anyway still thanks a lot~~:good:
flyingcowboy said:
fastboot flash recovery recovery.img
anyway still thanks a lot~~:good:
Click to expand...
Click to collapse
No problem. Which one are you flashing twrp or cwm? Maybe changing the recovery/ version of recovery may help. I'm not sure but perhaps certain versions are not compatible with your phone maybe try googling it.
Related
Yo
currently running newest official (12.1-YOG4PAS1N0).
I unlocked the bootloader-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then I put the recovery.img file at the adb path.
then I enter fastboot and typed <fastboot flash recovery recovery.img> and it flashed it.
I disconnected the USB, turned the device off and then immediately booted into recovery (Volume down + Power)... BUT- it takes me to CM stock recovery every time
was wondering if anyone knows what can be done.
CM Recovery update is disabledfrom Dev Options ofcourse.
thanks.
Lidor167 said:
Yo
currently running newest official (12.1-YOG4PAS1N0).
I unlocked the bootloader-
then I put the recovery.img file at the adb path.
then I enter fastboot and typed <fastboot flash recovery recovery.img> and it flashed it.
I disconnected the USB, turned the device off and then immediately booted into recovery (Volume down + Power)... BUT- it takes me to CM stock recovery every time
was wondering if anyone knows what can be done.
CM Recovery update is disabledfrom Dev Options ofcourse.
thanks.
Click to expand...
Click to collapse
Now since this is a straight forward thing you are going to get the basic questions which I suggest you put the exact route you took. was your recovery named recovery.img? Are you sure that its flashing?
Have you tried a toolkit although I agree to try it manually but just as another troubleshooting method.
playya said:
Now since this is a straight forward thing you are going to get the basic questions which I suggest you put the exact route you took. was your recovery named recovery.img? Are you sure that its flashing?
Have you tried a toolkit although I agree to try it manually but just as another troubleshooting method.
Click to expand...
Click to collapse
the recovery is named recovery.img
I tried a toolkit but its too bulky for me
Lidor167 said:
the recovery is named recovery.img
I tried a toolkit but its too bulky for me
Click to expand...
Click to collapse
what do you mean too bulky? did you try the toolkit prior to this or after
Edit: does it show the recovery flash working and being successful?
playya said:
what do you mean too bulky? did you try the toolkit prior to this or after
Edit: does it show the recovery flash working and being successful?
Click to expand...
Click to collapse
prior to this.. says something about not being able to find adb device. but when i open the command prompt and type <fastboot devices> it shows my One. so I gave up on the toolkit
Lidor167 said:
prior to this.. says something about not being able to find adb device. but when i open the command prompt and type <fastboot devices> it shows my One. so I gave up on the toolkit
Click to expand...
Click to collapse
Wugs makes a descent toolkit.. Did you get it fixed
playya said:
Wugs makes a descent toolkit.. Did you get it fixed
Click to expand...
Click to collapse
yeah, appreantly the file name was - recovery.img.img but it didn't show, I had it checked and now it's all good, thanks
Hello guys! I'm on a G 2015 bike to find a way around it. Good tried the procedures without unlocking the bootloader, but without success! Then I went and I was able to unlock Bootloader and repeat the process to install Roo Stock. But to no avail as well. Does anyone have any tips for solving this problem?
I would guess it stops in bootloader because it doesn't like the rom you've flashed.
Did you flash TWRP?
Boot to TWRP and clean flash something else.
Else flash TWRP and then do that.
Hi there! I had the same problem, but the solution was just wait. It took a full 5 minutes to boot since the warning appeared, but it worked fine. Give it a try, wait 5 minutes (literally) and see what happens. If it still stuck, then try the solution above.
KrisM22 said:
I would guess it stops in bootloader because it doesn't like the rom you've flashed.
Did you flash TWRP?
Boot to TWRP and clean flash something else.
Else flash TWRP and then do that.
Click to expand...
Click to collapse
Hi. I tried to do the way you said it, but it did not work. Take a look at the picture
I follow this GUIDE for install
https://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't think your bootloader is unlocked.
Have you unlocked your bootloader using the Motorola site? No other method will work.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
which recovery are you using - copy/paste full module name.
The bootloader has been unlocked by the motorola website! When I insert the cell phone, the message appears that the bootloader is unlocked.
Jdoria said:
The bootloader has been unlocked by the motorola website! When I insert the cell phone, the message appears that the bootloader is unlocked.
Click to expand...
Click to collapse
"when you insert the cell phone" into what?
EDITED POST FOR WINDOWS:
for windows I think type cmd in search bar, right click on cmd.exe and choose administrative (you may have to enter a password) and do everything in that window.
fastboot flash recovery twrp.img
but first tell me exactly which twrp you are using - one is bad.
Better than that just grab the latest from squid and use that. I know it's good.
When it flashes successfully, DO IT AGAIN - don't ask why, just do it - same command.
THEN boot to TWRP and backup your stock if you still have one.
Then and only then, wipe and flash whatever your heart desires.
@Jdoria Please attach the output of "fastboot getvar all"
@KrisM22 "sudo" wont do anything, this is WINDOWS, not Linux.
acejavelin said:
@Jdoria Please attach the output of "fastboot getvar all"
@KrisM22 "sudo" wont do anything, this is WINDOWS, not Linux.
Click to expand...
Click to collapse
Yeah I put a note at the bottom of that post for that. My bad.
Hi I ran cmd.exe in managed mode. Is there any method to format the data of the phone and install everything from scratch?
Jdoria said:
Hi I ran cmd.exe in managed mode. Is there any method to format the data of the phone and install everything from scratch?
Click to expand...
Click to collapse
You need to run it in administrative mode.
I just received my Pixel (not XL and not verizon version) that I bought from the Google Store and I tried loading TWRP on it. Fastboot works and I can fastboot into a TWRP recovery, however, whenever I try to flash another recovery with that recovery, the the message warning me to lock the bootloader pops up, then the phone very briefly goes to white screen with the google logo and instantly shuts off. Then it automatically repeats that process.. Am not sure what I did wrong (for example if I accidentally flashed the wrong variant to begin with?) but I also don't know how to fix it. I have tried all of the TWRP variants and nothing has worked. I also think the I was on 7.1.2.
I spent all night searching through all of the threads and could not find anyone who had a similar situation so any help is greatly appreciated and desperately needed.
Thank you in advance
SponsOne said:
I just received my Pixel (not XL and not verizon version) that I bought from the Google Store and I tried loading TWRP on it. Fastboot works and I can fastboot into a TWRP recovery, however, whenever I try to flash another recovery with that recovery, the the message warning me to lock the bootloader pops up, then the phone very briefly goes to white screen with the google logo and instantly shuts off. Then it automatically repeats that process.. Am not sure what I did wrong (for example if I accidentally flashed the wrong variant to begin with?) but I also don't know how to fix it. I have tried all of the TWRP variants and nothing has worked. I also think the I was on 7.1.2.
I spent all night searching through all of the threads and could not find anyone who had a similar situation so any help is greatly appreciated and desperately needed.
Thank you in advance
Click to expand...
Click to collapse
Try fastboot flashing 7.1.2 boot.img, then fastboot boot into TWRP, flash the attached twrp pixel installer, reboot to recovery from recovery , then flash supersu, then reboot. It will reboot a time or two if that is normal.
Tulsadiver said:
Try fastboot flashing 7.1.2 boot.img, then fastboot boot into TWRP, flash the attached twrp pixel installer, reboot to recovery from recovery , then flash supersu, then reboot. It will reboot a time or two if that is normal.
Click to expand...
Click to collapse
Thank you so much for your quick response.
Is this the version I use? I want to make sure I download the correct one: 7 .1.2 (N2G47O, May 2017)
SponsOne said:
Thank you so much for your quick response.
Is this the version I use? I want to make sure I download the correct one: 7 .1.2 (N2G47O, May 2017)
Click to expand...
Click to collapse
That should work though there should be June update.
p
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
Tulsadiver said:
That should work though there should be June update.
Click to expand...
Click to collapse
Thank you again for your help. I put the June version on instead of the previous and everything seems to be working. My only question is at the end of fastbooting the factory img, it said, "FAILED (remote: Partition table doesn't exist). Is that normal or something to be concerned about?
Here is a photo I took of it:
[/IMG]
SponsOne said:
[/IMG]
Click to expand...
Click to collapse
I don't know why the image doesn't seem to be uploading so here is a link to it:
https://drive.google.com/open?id=0B3fIceeoMIn8NC1XTUVTODNBT1k
Weird problem with my One Plus One. Cannot install ROM and Cannot repair file system via TWRP. I'm at my wits end. Can anyone help me fix this? The attached images should give you an idea of what I am talking about.
The system partition looks like this -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The DATA and CACHE PARTITIONS however,
When trying to wipe/repair this error comes up.
Any help would be appreciated.
rbkoneplusone said:
Weird problem with my One Plus One. Cannot install ROM and Cannot repair file system via TWRP. I'm at my wits end. Can anyone help me fix this? The attached images should give you an idea of what I am talking about.
Click to expand...
Click to collapse
Use fastboot mode to repair the partitions:
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Mr.Ak said:
Use fastboot mode to repair the partitions:
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Click to expand...
Click to collapse
Did that. But Stuck on Cyanogen Logo. I flashed TWRP, and when I do a cache/dalvik wipe I get this error
Is the Bootloader locked ou unlocked?
Malaach2 said:
Is the Bootloader locked ou unlocked?
Click to expand...
Click to collapse
Unlocked
rbkoneplusone said:
Unlocked
Click to expand...
Click to collapse
Seems like partitions are damaged big time.
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
This is your last bet.
Mr.Ak said:
Seems like partitions are damaged big time.
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
This is your last bet.
Click to expand...
Click to collapse
Thanks. I'll try that and report back. I honestly can't see how this could have happened! Could it be that the internal storage is damaged?
rbkoneplusone said:
Thanks. I'll try that and report back. I honestly can't see how this could have happened! Could it be that the internal storage is damaged?
Click to expand...
Click to collapse
Prolly something feked up while flashing or formatting partitions.
Mr.Ak said:
Prolly something feked up while flashing or formatting partitions.
Click to expand...
Click to collapse
I tried the tool from that thread. It flashed everything and turns green. However, the phone is still stuck at Oneplus Logo.
rbkoneplusone said:
I tried the tool from that thread. It flashed everything and turns green. However, the phone is still stuck at Oneplus Logo.
Click to expand...
Click to collapse
Boot into fastboot and flash Cos13.1.x.
Mr.Ak said:
Boot into fastboot and flash Cos13.1.x.
Click to expand...
Click to collapse
Sadly No Change. It was stuck at the red One Plus logo before (of Color OS, I assume), and now it is stuck at white One Plus logo :crying:
Did that. Still stuck at the Oneplus Logo
try the Bacon root toolkit by WugFresh. helped me out where all else failed
VOL"UP"+POWER doesn't work
[email protected] said:
VOL"UP"+POWER doesn't work
Click to expand...
Click to collapse
Adb reboot fastboot
linccracker said:
Adb reboot fastboot
Click to expand...
Click to collapse
When smart in boot loop))
[email protected] said:
When smart in boot loop))
Click to expand...
Click to collapse
Will it not boot into recovery mode? Vol -down and power button
linccracker said:
Will it not boot into recovery mode? Vol -down and power button
Click to expand...
Click to collapse
I tried to uninstall system apps. after an unsuccessful experiment, the phone went into the bootloop. Stock recovery was a possible only with data reset. I wanted to restore system with fastboot but it was not available. Just a hard reset. but is no longer relevant. went to the hardreset. ))
How to unlock bootloader in Oppo a54 cph2339
John. P. John said:
How to unlock bootloader in Oppo a54 cph2339
Click to expand...
Click to collapse
Use mtk client
linccracker said:
Adb reboot fastboot
Click to expand...
Click to collapse
Its shows don't match key or reboot system automatically... Please help me
Deepjatt7 said:
Its shows don't match key or reboot system automatically... Please help me
Click to expand...
Click to collapse
Sorry don't have this phone anymore to try
Deepjatt7 said:
Its shows don't match key or reboot system automatically... Please help me
Click to expand...
Click to collapse
Oppo phones have it's bootloader locked, there used to be method to break it but they fixed it in 2020 security update. So ig there is no way to unlock it.
adb reboot fastboot, in the exact same time that the command ends its process, disconnect USB from device, just 2 seconds, and reconnect again, it will show a fastbootd screen with the exact same menu that recovery.
Pressing and tapping on the recovery version also leads to download mode, specially useful for Qualcomm models.
This works for many Realme devices. Anyway, in a locked device, there’s no much to do through.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
fal3n.4ngel said:
Oppo phones have it's bootloader locked, there used to be method to break it but they fixed it in 2020 security update. So ig there is no way to unloc
SubwayChamp said:
adb reboot fastboot, in the exact same time that the command ends its process, disconnect USB from device, just 2 seconds, and reconnect again, it will show a fastbootd screen with the exact same menu that recovery.
Pressing and tapping on the recovery version also leads to download mode, specially useful for Qualcomm models.
This works for many Realme devices. Anyway, in a locked device, there’s no much to do through.
View attachment 5574189
Click to expand...
Click to collapse
I'm stuck at this same point
Click to expand...
Click to collapse
@armwaypaul What exactly did you want to write?