Database Info

boot stuck at "fastboot menu" and "This build is for development purposes only."

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.

HELP!!! Recovery and system wont boot

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

is it possible to relock bootloader while using custom rom and recovery?

is it possible to relock bootloader while using custom rom and recovery installed ?
i am asking this because it will make phone more secure while running it on custom recovery as all of us know how to remove screen lock with use of custom recovery
put password on recovery so no one can open it and if we relock bootloader then no one can reflash recovery in it and then there will less chance that our data may get out from phone or can be used if it get stolen or lost.

I am also trying to get rid of the annoying bootloader prompt that says the security of the device might have been compromised....
Please explain how...
Yes i have already flashed the device.

No. Just no.

If you want to brick your phone, just do it.

No, unlocking the bootloader is what allows you to run a custom ROM, that's why the phone is okay with it being custom. You can't just delete a password if you have an encrypted data partition.

Locked bootloaders only accept roms from vendor by certificate.
So If you lock is you will brick your device.
Not sure if hardbrick tools will work...?

This does kind of exist for the OnePlus 5T; see here. It is quite complex, but once you have root under a locked bootloader you can reflash everything (with SIGNED recoveries and boot images). If you fail to sign everything correctly your phone will become more bricked than usual, with no possibility of reflashing except using the MSM Download Tool.
However, before you get any ideas, hold on. The OnePlus 7 is not only an A/B device, but a system-as-root device, neither of which the 5T is. There is no recovery partition that you can easily overwrite. I believe it's still possible to get a twrp-installer zip to do your bidding, if you're able to get Magisk correctly with a locked bootloader. And before you ask, I don't know if it's possible to sign the boot.img with Magisk/TWRP already installed.
This is all pure speculation on my part and I've yet to try any of this with my 7 Pro. I know that no matter what happens, I can always use MSM Download Tool to restore my phone to working software. Then I'll have to start over, installing Magisk and then TWRP to restore my backup. I'm waiting for more input on this from people who know what they are doing, before attempting anything myself.

This was possible on the Redmi Note 3 pro. Someone created a mod where you could flash recovery directly using the MiFlash tool (Xiaomi's equivalent of MSTOOL). This was great because I had a locked bootloader and used orange fox recovery to lock the recovery... A theoretically fully secure rooted device

The anwser is no. You can try it like I did but it will tell you you have to format the device. I just learned the button combo. Thats what my problem was. Everytime I wanted to restart my phone I would always forget to shutdown completly because you have to do the button combo to enter rooted state. I just got used to it.
Edit: but I did manage to stop upgrade to the ugly Andriod 11 and managed to get my gear sport to work on my rooted rom. Thats all I wanted was Call recorder and for my watch to work.

So far no,I have been working on it and rebuilt a ops file with patched boot.and get this new error lol. If any one knows what I should try let me know. I am able to fully unpack and repack the ops files and flash.have been able to disable quite a few checks in the flashing with MSM tool.
{
"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"
}

QUALCOMM Crashdump Mode on boot even after using MSM tool

So long story short: I was on Flamingo OS A13, got a crashdump mode all of the sudden, I tried flashing again without success. Then I used MSM tool to go back to OOS 11 and after completing, the device just shows the OnePlus logo, screen gets distorted (see image below) and goes off. I try turning it off and on using all the buttons, and I can access Fastboot mode and Recovery only without any problem. But when I try to boot normally, it crashes on the OP logo again and goes into crashdump mode. I tried every latest MSM tool (OOS9, OOS10, OOS11).
Not sure what else to do.
{
"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"
}

for some reason I always get the same error after using msm tool.
try to boot to twrp recovery using all in one tool or any other way. then flash OOS 11 on both slots (don't forget to format data).
you should be fine. tell us if you managed to fix it by any way

Dark Fear said:
for some reason I always get the same error after using msm tool.
try to boot to twrp recovery using all in one tool or any other way. then flash OOS 11 on both slots (don't forget to format data).
you should be fine. tell us if you managed to fix it by any way
Click to expand...
Click to collapse
Thanks for your reply. Unfortunately I can't boot to twrp since MSM locks the bootloader and I can't unlock it unless I boot the device first, which is the problem.

Nimrodz91 said:
Thanks for your reply. Unfortunately I can't boot to twrp since MSM locks the bootloader and I can't unlock it unless I boot the device first, which is the problem.
Click to expand...
Click to collapse
can you use fastboot roms?

Dark Fear said:
can you use fastboot roms?
Click to expand...
Click to collapse
No, because bootloader is locked and I can't boot up first.

Nimrodz91 said:
No, because bootloader is locked and I can't boot up first.
Click to expand...
Click to collapse
Did find the solution. I have the same problem even the photo that you shared of the phone its the same with lines coming. The MSM tool does it all but again the phone goes black and i can just access Fastboot

abbasi89 said:
Did find the solution. I have the same problem even the photo that you shared of the phone its the same with lines coming. The MSM tool does it all but again the phone goes black and i can just access Fastboot
Click to expand...
Click to collapse
Unfortunately, no. After researching about the issue, I found that it's a hardware problem where the RAM or motherboard needs to be replaced. I ended up buying another OP7Pro and decided to get my hardbricked one fixed sometime later.

Question I cannot install twrp on to my galaxy a12

i tried to install twrp , root and degoogle my galaxy a12, i have no experience at all and nearly bricked my phone
i unlocked my bootloader, go into download mode, i tried flashing twrp 3.7.0 image i downloaded on the official website, it didn't work and everytime i reboot it got into download mode again
i flashed the stock rom again, go to the support thread of twrp on the galaxy 12 here, i did like the tutorial but i cannot flash the rom with the re partition and nand erase because odin will just froze and the progress bar wont appear
after that i tried flashing it like the post said. put the twrp image in the AP box, and the vbmeta.img.md5(i extracted the vbmeta.zip file since i cannot put the zip file into the box) into userdata box, then start, restarted the phone and after that it got the "An ERROR Has Occured While Updating Device Software" with the teal background, i freaked out but luckily i fixed it with the frp hijack software.
after that i'm just too scared to continue, does anyone know what i did wrong? my guess is that it's at the vbmeta file but the support post give that file only and i just extracted it and put the md5 file in the userdata box.

I assume that you flashed twrp recovery with vbmeta and you had One Ui 4.0 (Android 12) on stock. It's just that I had a similar thing when I flashed it on TWRP.
Note: WHEN YOU HAVE INSTALLED THE VBMETA AND TWRP FILE AND YOU ARE USING THE STOCK FIRMWARE THEN DO NOT LOGIN TO YOUR SAMSUNG ACCOUNT. YOUR PHONE WILL BE BLOCKED. AND WHEN TURNED ON, IT WILL PROVIDE THE FOLLOWING.
{
"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"
}

lil_kyrick said:
I assume that you flashed twrp recovery with vbmeta and you had One Ui 4.0 (Android 12) on stock. It's just that I had a similar thing when I flashed it on TWRP.
Note: WHEN YOU HAVE INSTALLED THE VBMETA AND TWRP FILE AND YOU ARE USING THE STOCK FIRMWARE THEN DO NOT LOGIN TO YOUR SAMSUNG ACCOUNT. YOUR PHONE WILL BE BLOCKED. AND WHEN TURNED ON, IT WILL PROVIDE THE FOLLOWING.
View attachment 5789287
Click to expand...
Click to collapse
no, it is the android 11 version with the A127FXXU5AVC4 stock firmware (vietnam region) and no i didn't login to anything after unlocking bootloader, and the warning shows something like this image here
but without the 2 last line, instead it has a korean and japanese translation below that first 2 english lines
i think i messed up at the vbmeta part, i though my phone was hard bricked but i managed to fix it and flashed a the stock firmware again

Oh ****. So connect your phone to your computer and use the "Emegency Software Recovery" function in the Smart Switch program.
What was your mistake? Yes, the fact is that you have SM-A127F, and you set it for SM-125F. And you need to repair the device now, otherwise, contact the nearest service center. Here is a link to the guide you need for your device.

lil_kyrick said:
Oh ****. So connect your phone to your computer and use the "Emegency Software Recovery" function in the Smart Switch program.
What was your mistake? Yes, the fact is that you have SM-A127F, and you set it for SM-125F. And you need to repair the device now, otherwise, contact the nearest service center. Here is a link to the guide you need for your device.
Click to expand...
Click to collapse
ah i already fixed it myself with frp hijacker, thank you for your consideration

az_r08 said:
ah i already fixed it myself with frp hijacker, thank you for your consideration
Click to expand...
Click to collapse
Can you send a ss of the odin you are using and the settings?

What I assume is you need to use patched odin or you device is encrypted.