Hey peeps, trying to fix this phone for my brother. Is this phone bricked? Or is there anyway to flash it? I can't seem to get into download mode but the phone shows up in Odin I just don't wanna further damage it if there is a better way. Thank you for your time!
{
"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"
}
Click to expand...
Click to collapse
just go ahead and flash latest stock firmware or id recommend doing the lowest binary level of firmware your phone has been updated to. looks like you have flashed combination firmware witch is why it looks like that.. that is just download mode
exnfox said:
just go ahead and flash latest stock firmware or id recommend doing the lowest binary level of firmware your phone has been updated to. looks like you have flashed combination firmware witch is why it looks like that.. that is just download mode
Click to expand...
Click to collapse
I tried to use odin but it won't do anything after it starts it wont connect.
It won't flash unless you get it to downloading mode. Download mode for is volume down + home on boot. If it doesn't enter download mode and you have a better recovery installed like TWRP or other with option to boot to Download mode then use that instead. It may be that home or volume key on the phone doesn't work or other hardware problem.
Jerahya said:
It won't flash unless you get it to downloading mode. Download mode for is volume down + home on boot. If it doesn't enter download mode and you have a better recovery installed like TWRP or other with option to boot to Download mode then use that instead. It may be that home or volume key on the phone doesn't work or other hardware problem.
Click to expand...
Click to collapse
Tried all methods to get into download mode usb jig just makes the phone not boot at all, download mode flash's for a second before going to stock recovery is there anything I can flash in stock recovery to get into download mode or install twrp?
korupt data said:
Tried all methods to get into download mode usb jig just makes the phone not boot at all, download mode flash's for a second before going to stock recovery is there anything I can flash in stock recovery to get into download mode or install twrp?
Click to expand...
Click to collapse
not sure if you really did some digging but try this.
https://www.reddit.com/r/AndroidQue...ed_upload_by_key_pressing_phone_unresponsive/
if not try adb reboot download.
if none of it works then bring it to a shop for jtag.
Related
How can I get into recovery mode on a device that doesn't boot AND has broken volume buttons?
I have a Galaxy Nexus that isn't booting (boot loop) and I can't manually start recovery mode, because my volume buttons are broken.
Is there anything I can do?
get it repaired first
SuperStalin said:
How can I get into recovery mode on a device that doesn't boot AND has broken volume buttons?
I have a Galaxy Nexus that isn't booting (boot loop) and I can't manually start recovery mode, because my volume buttons are broken.
Is there anything I can do?
Click to expand...
Click to collapse
You need to get ADB working. You should be able to restore the device that way without having to touch the buttons.
Visit this link for tutorial recovery using ADB.
Thoughts: Volume- Not Working, Can't Boot Into Recovery
{
"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"
}
cacing32 said:
You need to get ADB working. You should be able to restore the device that way without having to touch the buttons.
Visit this link for tutorial recovery using ADB.
Thoughts: Volume- Not Working, Can't Boot Into Recovery
Click to expand...
Click to collapse
Unfortunately, adb recognizes my device as "unauthenticated" and I can't send any commands to it.
SuperStalin said:
How can I get into recovery mode on a device that doesn't boot AND has broken volume buttons?
I have a Galaxy Nexus that isn't booting (boot loop) and I can't manually start recovery mode, because my volume buttons are broken.
Is there anything I can do?
Click to expand...
Click to collapse
Hello bro
If you have rooted device.. You can find this app "Android Tuner"
Install this and grant root permissions... And in this tool go to menu and select reboot with full choices
And select recovery
Killwish said:
Hello bro
If you have rooted device.. You can find this app "Android Tuner"
Install this and grant root permissions... And in this tool go to menu and select reboot with full choices
And select recovery
Click to expand...
Click to collapse
My phone is stuck on boot loop, can't get into the OS.
SuperStalin said:
My phone is stuck on boot loop, can't get into the OS.
Click to expand...
Click to collapse
Oh sorry bro... I didn't read your post carefully...
Do you have both volume keys broken?
Killwish said:
Oh sorry bro... I didn't read your post carefully...
Do you have both volume keys broken?
Click to expand...
Click to collapse
Yep. The only way is to get it repair. Sigh.
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
after update
{
"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"
}
what is your question you need to be more specific than this
just hold power button for more than 10 seconds
or go into recovery mode by pressing power button, and from there shutdown or restart it
ineedroot69 said:
what is your question you need to be more specific than this
Click to expand...
Click to collapse
How to fix it I try for press and log to fastboot but recovery mode can't log
indestructible master said:
just hold power button for more than 10 seconds
or go into recovery mode by pressing power button, and from there shutdown or restart it
Click to expand...
Click to collapse
Not working friend I try to fastboot for get recovery mode but still like the over picture
My phone show that error too but it can still boot does your phone still boot?
ineedroot69 said:
My phone show that error too but it can still boot does your phone still boot?
Click to expand...
Click to collapse
Yes it still booting logo google
MBenzKH said:
Yes it still booting logo google
Click to expand...
Click to collapse
so basically your device won't start? what are you doing before this error show up?
did you try pressing the power button to continue?
mine has this just ignore it and press VOL+ it will continue to boot
@ineedroot69 i try follow you said
It can't log to recovery mode also and only fastboot mode can
MBenzKH said:
@ineedroot69 i try follow you said
It can't log to recovery mode also and only fastboot mode can
Click to expand...
Click to collapse
flash full stock rom or flash the partition that is corrupted via fastboot
@ineedroot69 need unlock fastboot
MBenzKH said:
@ineedroot69 need unlock fastboot View attachment 5242237
Click to expand...
Click to collapse
you fvck up real bad lmao
what are you doing before that error shows up?
Just security update in setting
MBenzKH said:
Just security update in setting
Click to expand...
Click to collapse
you are rooted via Magisk before?
Normal use never root
MBenzKH said:
Normal use never root
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Not working need to unlock bootloader
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?
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.