so i bricked my fire tv 2 and for the life of me can not get windows 10 to detect it. keeping getting message in adbfire no devices detected. is was detecting it yesterday. any ideas peeps?
You're going to have to give us more information. What did you do to it? Is it rooted? Do you have TWRP installed? Is it stuck on the white amazon logo? Does it get to the colorful Fire TV logo? The more information you give, the more likely someone will be able to help.
AFTVnews.com said:
You're going to have to give us more information. What did you do to it? Is it rooted? Do you have TWRP installed? Is it stuck on the white amazon logo? Does it get to the colorful Fire TV logo? The more information you give, the more likely someone will be able to help.
Click to expand...
Click to collapse
sorry, i was trying to install a backup and wiped dalvik cache and cache then got some cache error. will only boot to white logo. no twrp. yes to everything accept getting to the colourful fire tv logo. was on 5.0.5.
thks
mandroid717 said:
sorry, i was trying to install a backup and wiped dalvik cache and cache then got some cache error. will only boot to white logo. no twrp. yes to everything accept getting to the colourful fire tv logo. was on 5.0.5.
thks
Click to expand...
Click to collapse
WIthout access to recovery, your only option is rbox's unbrick image here: http://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349
You'll need an A-to-A USB cable.
AFTVnews.com said:
WIthout access to recovery, your only option is rbox's unbrick image here: http://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349
You'll need an A-to-A USB cable.
Click to expand...
Click to collapse
yes i have tried that but adb does not detect device or should i say windows does not see it. it saw it yesterday. i have tried different ports. the cable is new.
mandroid717 said:
yes i have tried that but adb does not detect device or should i say windows does not see it. it saw it yesterday. i have tried different ports. the cable is new.
Click to expand...
Click to collapse
Sounds like it's an issue with your PC and/or drivers. Try a different PC if you have access to one, or try deleting all the relevant drivers and start from scratch. Sorry I don't have any other suggestions.
AFTVnews.com said:
Sounds like it's an issue with your PC and/or drivers. Try a different PC if you have access to one, or try deleting all the relevant drivers and start from scratch. Sorry I don't have any other suggestions.
Click to expand...
Click to collapse
thx
AFTVnews.com said:
Sounds like it's an issue with your PC and/or drivers. Try a different PC if you have access to one, or try deleting all the relevant drivers and start from scratch. Sorry I don't have any other suggestions.
Click to expand...
Click to collapse
So using different pc worked. Now recovery looks like this when trying to install rom.
{
"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"
}
Delivered by my Silver S7.
mandroid717 said:
yes i have tried that but adb does not detect device or should i say windows does not see it. it saw it yesterday. i have tried different ports. the cable is new.
Click to expand...
Click to collapse
I eventually was able to get backup installed woohoo
AFTVnews.com said:
Sounds like it's an issue with your PC and/or drivers. Try a different PC if you have access to one, or try deleting all the relevant drivers and start from scratch. Sorry I don't have any other suggestions.
Click to expand...
Click to collapse
Delivered by my Silver S7.
mandroid717 said:
I eventually was able to get backup installed woohooView attachment 3961265
Click to expand...
Click to collapse
Awesome, congrats! Remember to thank (and donate to) @rbox. Without him you would have been hosed and out $90.
AFTVnews.com said:
You're going to have to give us more information. What did you do to it? Is it rooted? Do you have TWRP installed? Is it stuck on the white amazon logo? Does it get to the colorful Fire TV logo? The more information you give, the more likely someone will be able to help.
Click to expand...
Click to collapse
I have a FIRE TV STICK stuck on the white amazon logo, no rooted, How can i solve this?
Is new and never worked.
Related
My friend from Korea bought a kfhd 8.9 here in the US and rooted it, but an OTA installed and bricked it. It keeps booting to the stock recovery. I tried getting fastboot to work, but the computer won't detect it, as well as the unbrick utility. Anything I can do?
It keeps booting to 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"
}
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
What attempts did you make to access fastboot?
Powering off, running cmd and typing fastboot -i 0x1949 getvar product, plugging it in. It doesn't detect my device.
I noticed that when I plug it in, Windows makes the beeping sound that tells you something is connected, and something briefly shows up in the hardware and devices section, but then disappears.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Nothing shows up in the device manager when plugged in as well. And I did install the drivers.
You never know with Windows...Have you tried SoupKit?
rha_december said:
Nothing shows up in the device manager when plugged in as well. And I did install the drivers.
Click to expand...
Click to collapse
I would try to remove all the drivers you have now and install the non signed drivers from the first aid perferd drivers and that should go without any problems once that is done you should have a working drivers. Depending if you have windows 7 or 8 on how to disable driver signature.
Alrighty, thanks guys. I give it a shot.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I tried again on a different computer, and followed the instructions for KF First Aide package up until I had to plug it in. A driver installation window popped up and driver not found I can't go beyond that. I pressed 12 to install the Amazon ADB driver.
rha_december said:
I tried again on a different computer, and followed the instructions for KF First Aide package up until I had to plug it in. A driver installation window popped up and driver not found I can't go beyond that. I pressed 12 to install the Amazon ADB driver.
Click to expand...
Click to collapse
I think the step your missing is to disable driver signature enforcement Search in google for disable driver signature enforcement Windows (then whatever version you have) and should find a way to do it, then connect kindle to the computer remove any drivers you see in device manager (and click delete driver if it gives you a check box) Then try the same thing and it should work! (cross all your fingers:fingers-crossed::fingers-crossed
lizzord30 said:
I think the step your missing is to disable driver signature enforcement Search in google for disable driver signature enforcement Windows (then whatever version you have) and should find a way to do it, then connect kindle to the computer remove any drivers you see in device manager (and click delete driver if it gives you a check box) Then try the same thing and it should work! (cross all your fingers:fingers-crossed::fingers-crossed
Click to expand...
Click to collapse
I gave it a shot, but nothing is being picked up. Note that I can't even fully boot up the Kindle. It always goes straight to the stock recovery. Would an OTA disable ADB in the kindle?
UPDATE: Wow... I hit 9 to check fastboot status and it just happened to work, haha. Thanks a lot for your help!
rha_december said:
I gave it a shot, but nothing is being picked up. Note that I can't even fully boot up the Kindle. It always goes straight to the stock recovery. Would an OTA disable ADB in the kindle?
UPDATE: Wow... I hit 9 to check fastboot status and it just happened to work, haha.
Click to expand...
Click to collapse
:good::good: Great now that your in fastboot do you know what to do?
If you like could try my Rom but it will wipe your whole device(nothing on SDcard will be left)
here is the link if you like
It has some glitches still but it is automated from when your in fastboot. And dont forget to letup LMT on first boot.
lizzord30 said:
:good::good: Great now that your in fastboot do you know what to do?
If you like could try my Rom but it will wipe your whole device(nothing on SDcard will be left)
here is the link if you like
It has some glitches still but it is automated from when your in fastboot. And dont forget to letup LMT on first boot.
Click to expand...
Click to collapse
Hm, I actually tried to do a complete restore through fastboot, since it's the only thing working, but when it finishes and the kindle reboots, it still goes back to the stock recovery screen. I can't run the unbrick utility or use anything that requires ADB, since it's not being detected through that ><; damn it. I thought I was on to something.
rha_december said:
Hm, I actually tried to do a complete restore through fastboot, since it's the only thing working, but when it finishes and the kindle reboots, it still goes back to the stock recovery screen. I can't run the unbrick utility or use anything that requires ADB, since it's not being detected through that ><; damn it. I thought I was on to something.
Click to expand...
Click to collapse
I was sending you that link because you don't need ADB to use what I linked, it goes right from fastboot.
lizzord30 said:
I was sending you that link because you don't need ADB to use what I linked, it goes right from fastboot.
Click to expand...
Click to collapse
Gotcha. Do you think I'll be able to boot up normally if I flash this?
rha_december said:
Gotcha. Do you think I'll be able to boot up normally if I flash this?
Click to expand...
Click to collapse
Maybe, hard to tell since like you said you tried to go back to completely stock and it didn't work.
Alrighty, I flashed yours but I ended up with a red screen, but I figured out how to actually fix it. This kindle now run perfectly haha. awesome.
rha_december said:
Alrighty, I flashed yours but I ended up with a red screen, but I figured out how to actually fix it. This kindle now run perfectly haha. awesome.
Click to expand...
Click to collapse
Please post what you did so for the next person that has this problem can get it fixed!
Happy you got it working.
lizzord30 said:
Please post what you did so for the next person that has this problem can get it fixed!
Happy you got it working.
Click to expand...
Click to collapse
I'll do that as soon as I have time to take screenshots and stuff. Just ran through the rain and jumped over a flooded road to get home >< soaking wet.
rha_december said:
I'll do that as soon as I have time to take screenshots and stuff. Just ran through the rain and jumped over a flooded road to get home >< soaking wet.
Click to expand...
Click to collapse
Ok thanks! I want to make a script to fix the red screen problem! I had it once but I forgot how I fixed it lol and I dont want to get it again to try to learn again how to fix
Pretty much all I did was get into fastboot via cmd, and flashed boot, system, and recovery individually; they were for 8.1.4. I was at work when I did it, so I can't remember where I got the files, but you get the idea.
However, I had to type: flashboot -i 0x1949 flash (whatever here) (dragged the file here)
Because putting the file in the same folder as my fastboot didn't work.
After that I just rebooted and it worked.
So, basically I downloaded cm10.1 nightly and it was rebooting every some hour, this morning when i turned it on it immediately started rebooting and it kept rebooting until i pulled the battery.
so i went to the cwm recovery and tried to flash a backup, but whenever i tried to flash the backup it also rebooted..
then i downloaded the google nexus toolkit and thought i could restore my nexus with it, but since i can't boot into android, i can't get adb access...
i'm really lost right now, does anyone know what i can do?
thanks in advance :crying:
error i get in the toolkit
{
"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"
}
Too many links I believe is usually a USB issue, either port on PC, port on phone, USB cable, or even drivers issues on your PC (as in USB driver issues). I could be mistaken on this, but I seem to remember reading that was the solution to this problem a while back.
cupfulloflol said:
Too many links I believe is usually a USB issue, either port on PC, port on phone, USB cable, or even drivers issues on your PC (as in USB driver issues). I could be mistaken on this, but I seem to remember reading that was the solution to this problem a while back.
Click to expand...
Click to collapse
drivers are fine i guess, since i used the toolkit some days ago and everything worked fine..
also i tried to use this guide to start my gnex : http://rootzwiki.com/topic/12069-gu...able-bootloopingpseudo-brickedbricked-phones/
but i get this error again...
Toxina said:
drivers are fine i guess, since i used the toolkit some days ago and everything worked fine..
also i tried to use this guide to start my gnex : http://rootzwiki.com/topic/12069-gu...able-bootloopingpseudo-brickedbricked-phones/
but i get this error again...
Click to expand...
Click to collapse
just change your usb cable or usb port
samersh72 said:
just change your usb cable or usb port
Click to expand...
Click to collapse
doesnt help at all x.x
Do you have kies installed? Just probing an idea.
a manta wrote this.
beekay201 said:
Do you have kies installed? Just probing an idea.
a manta wrote this.
Click to expand...
Click to collapse
i dont, also now i have a weird symbol, its like "phone then two dots then a big yellow exclamation mark followed by two dots and then a computer"
edit : got a picture for the symbol i get upon start.. : http://i.imgur.com/RI9lxWO.jpg
can't boot into fastboot anymore..
edit :
kay tried to do it with odin and odin hangs at system too..
Try my odin package (see my sig) and use odin 1.85
sent from my Galaxy
samersh72 said:
Try my odin package (see my sig) and use odin 1.85
sent from my Galaxy
Click to expand...
Click to collapse
didn't help in any way :/
ugh im getting frustrated :crying:
any ideas are welcome at this point ._.!
Toxina said:
any ideas are welcome at this point ._.!
Click to expand...
Click to collapse
"Odin flashing is like taking a lottery ticket! U never know when u hit the jackpot!"
retry with odin + pit file
samersh72 said:
"Odin flashing is like taking a lottery ticket! U never know when u hit the jackpot!"
retry with odin + pit file
Click to expand...
Click to collapse
tried it but im still stuck at system..
ugh push ;-;
Toxina said:
ugh push ;-;
Click to expand...
Click to collapse
Don't "push" threads, take it easy. It's not going to help if you're stressing about it, believe me. What's your platform-tools version? R16?
http://forum.xda-developers.com/showthread.php?t=1760787
beekay201 said:
Don't "push" threads, take it easy. It's not going to help if you're stressing about it, believe me. What's your platform-tools version? R16?
http://forum.xda-developers.com/showthread.php?t=1760787
Click to expand...
Click to collapse
dont know what version but the date is : 2013 05 22
btw i got my nexus to boot to stock with a sideloaded zip BUT every time i wanna take a photo it freezes and reboots, and when i try to record a video it'll also freeze and reboot, it'll also freeze and reboot if i try to put something into the sd-card through usb, it also makes a loud popping voice everytime it reboots..
edit : it also sometimes freezes on reboot, i think there's something wrong when writing/reading/deleting/saving data with my gnex...
pushing this cause i still need help v.v
still need help.
My wife installed the April update on her phone a few nights ago while I was asleep. After installation, she can't get past the boot lock screen. The screen doesn't recognize any input. I am able to reboot into recovery and would like to try a factory reset, but she has two months of baby photos on there that have not been backed up. I have tried mounting the phone from recovery but none of the computers I have tried will recognize the phone. Any suggestions on how to get the photos off of the device?
Thanks!
boomer13 said:
My wife installed the April update on her phone a few nights ago while I was asleep. After installation, she can't get past the boot lock screen. The screen doesn't recognize any input. I am able to reboot into recovery and would like to try a factory reset, but she has two months of baby photos on there that have not been backed up. I have tried mounting the phone from recovery but none of the computers I have tried will recognize the phone. Any suggestions on how to get the photos off of the device?
Thanks!
Click to expand...
Click to collapse
Perhaps I can use ADB to access the internal storage?
Try all the combinations of usb ports and cables you have. Aren't Microsoft and device drivers magical? There are other things you can try before you factory reset. BTW, was the phone rooted, encrypted or anything else before the update was applied?
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Try all the combinations of usb ports and cables you have. Aren't Microsoft and device drivers magical? There are other things you can try before you factory reset. BTW, was the phone rooted, encrypted or anything else before the update was applied?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
It was stock. She received her replacement today. I never hooked up her bricked phone to my computer pre-brick... Maybe I can hook up the new one, install the drivers on my computer, and then mount the bricked one via Recovery.
boomer13 said:
It was stock. She received her replacement today. I never hooked up her bricked phone to my computer pre-brick... Maybe I can hook up the new one, install the drivers on my computer, and then mount the bricked one via Recovery.
Click to expand...
Click to collapse
That sounds like a plan. You could also try and mount the old phone to the new one with the included c to c cable. You are definitely in an interesting situation.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
That sounds like a plan. You could also try and mount the old phone to the new one with the included c to c cable. You are definitely in an interesting situation.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
That's worth a shot. I've never done that before.
Now I don't know if I'll be able to even get into Recovery. The screen has started doing some weird stuff and I can't get it to shut down.
{
"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 phone comes encrypted. That might make things difficult. You said that the phone won't boot past the boot lock screen, so assume that you mean that the pin is required to fully boot the phone. Is that right? If so, adb pull won't do squat.
Another option is to buy an OTG cable and connect the phone to a mouse and/or keyboard and see if you can poke around and get things transferred.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
The phone comes encrypted. That might make things difficult. You said that the phone won't boot past the boot lock screen, so assume that you mean that the pin is required to fully boot the phone. Is that right? If so, adb pull won't do squat.
Another option is to buy an OTG cable and connect the phone to a mouse and/or keyboard and see if you can poke around and get things transferred.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Correct, it requires a pattern to fully boot. I think it might be completely fubared now anyway.
boomer13 said:
Correct, it requires a pattern to fully boot. I think it might be completely fubared now anyway.
Click to expand...
Click to collapse
It looks like a faulty screen. The data inside may still be there.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
It looks like a faulty screen. The data inside may still be there.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yeah, but it's looking like I'll have no way to access it. Maybe once the battery dies I'll be able to reboot and the screen will work well enough to get into recovery again.
*but is entering fastboot mode*. Title. I've heard that this isn't expected behaviour. All I did was flash a stock firmware belonging to a different country. What's worse is that odin on my pc doesnt even recognise my phone anymore. Please help me (I'm not rooted). And yes, it shows entering fastboot mode.
AllStars101 said:
*but is entering fastboot mode*. Title. I've heard that this isn't expected behaviour. All I did was flash a stock firmware belonging to a different country. What's worse is that odin on my pc doesnt even recognise my phone anymore. Please help me (I'm not rooted). And yes, it shows entering fastboot mode.
Click to expand...
Click to collapse
please post a pic
west2cool said:
please post a pic
Click to expand...
Click to collapse
{
"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"
}
This is how it looks like when trying to go to download mode. I flashed the latest germany firmware and this is what it became. All fastboot commands work but unfortunately not able to get odin back. Please help.
AllStars101 said:
This is how it looks like when trying to go to download mode. I flashed the latest germany firmware and this is what it became. All fastboot commands work but unfortunately not able to get odin back. Please help.
Click to expand...
Click to collapse
Have you tried using SAMtool to boot it into download mode? Are able to use adb commands.
west2cool said:
Have you tried using SAMtool to boot it into download mode? Are able to use adb commands.
Click to expand...
Click to collapse
adb reboot bootloader takes me to fastboot. also SAMtool doesnt support 2020 flagships yet, unfortunately.
AllStars101 said:
adb reboot bootloader takes me to fastboot. also SAMtool doesnt support 2020 flagships yet, unfortunately.
Click to expand...
Click to collapse
I use samtool to boot my s20 plus into Download mode and it does work so try it.
west2cool said:
I use samtool to boot my s20 plus into Download mode and it does work so try it.
Click to expand...
Click to collapse
ok so i did try it. and it still goes to fastboot
you can power the phone off, press and hold both volume up and volume down, then connect your Galaxy to a computer using a USB-C cable. After July Update mine was having the same problem.
Just go to a Samsung repair center.
Take your phone to a Samsung repair center. They usually know how to fix these kind of problems, so this might be your safest bet.
Wreck_8 said:
you can power the phone off, press and hold both volume up and volume down, then connect your Galaxy to a computer using a USB-C cable. After July Update mine was having the same problem.
Click to expand...
Click to collapse
Omg thanks dude! Was thinking of taking it to the service center lol. Works fine now.
AllStars101 said:
Omg thanks dude! Was thinking of taking it to the service center lol. Works fine now.
Click to expand...
Click to collapse
how did you go about solving the problem
YAOHER said:
how did you go about solving the problem
Click to expand...
Click to collapse
Wreck_8 said:
you can power the phone off, press and hold both volume up and volume down, then connect your Galaxy to a computer using a USB-C cable
That's the way to enter download mode
Hey guys, i have a second phone, my Galaxy A50, and i wanna Flash a Custom ROM on it. But the problem is, that fastboot can't detect the phone. I tried everything i could, i installed a whole new Firmware, reinstalled ADB and Fastboot Drivers, restarted my PC like 5 Times. But Still i get the Driver problem. I tried to the method with the Google Bootloader Interface Drivers, but Device-Manager always put something like that. ADB detects my Phone but only fastboot can't detect it.
And Yes tried i OEM Unlocked it, but for some reason i can't unlock it anymore.
{
"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 tried to remove it, but it keeps popping up.
Sorry this is on German, but i hope someone can reconize the structure of the window.
Device Datas:
Samsung Galaxy A50
SM-A505FN/DS
R58M85BL6TT
zunaaaa said:
Hey guys, i have a second phone, my Galaxy A50, and i wanna Flash a Custom ROM on it. But the problem is, that fastboot can't detect the phone. I tried everything i could, i installed a whole new Firmware, reinstalled ADB and Fastboot Drivers, restarted my PC like 5 Times. But Still i get the Driver problem. I tried to the method with the Google Bootloader Interface Drivers, but Device-Manager always put something like that. ADB detects my Phone but only fastboot can't detect it.
And Yes tried i OEM Unlocked it, but for some reason i can't unlock it anymore.
View attachment 5684407
View attachment 5684409
View attachment 5684403
i tried to remove it, but it keeps popping up.
View attachment 5684405
Sorry this is on German, but i hope someone can reconize the structure of the window.
Device Datas:
Samsung Galaxy A50
SM-A505FN/DS
R58M85BL6TT
Click to expand...
Click to collapse
A50 doesn't have fastboot
only adb
JuanTamqd21 said:
A50 doesn't have fastboot
only adb
Click to expand...
Click to collapse
So there is no way to flash it through Fastboot?
zunaaaa said:
So there is no way to flash it through Fastboot?
Click to expand...
Click to collapse
Yep
Just flash twrp via odin
JuanTamqd21 said:
Yep
Just flash twrp via odin
Click to expand...
Click to collapse
Alright but i get the Only official realesed binaries are allowed to be flashed(BOOT) in the Bootloader and stop says fail in ODIN always and yes it was OEM Unlocked.
Now i can't unlock it anymore.
zunaaaa said:
Alright but i get the Only official realesed binaries are allowed to be flashed(BOOT) in the Bootloader and stop says fail in ODIN always and yes it was OEM Unlocked.
Now i can't unlock it anymore.
Click to expand...
Click to collapse
Does the oem unlock is grey?
Also, you need to unlock it also in download mode
JuanTamqd21 said:
Does the oem unlock is grey?
Also, you need to unlock it also in download mode
Click to expand...
Click to collapse
there isn't an Unlock Button anymore
I unlocked it once, then it says to me to lock it again and now i can't see the OEM Unlock Button anymore
zunaaaa said:
there isn't an Unlock Button anymore
I unlocked it once, then it says to me to lock it again and now i can't see the OEM Unlock Button anymore
Click to expand...
Click to collapse
Sign in your google account
JuanTamqd21 said:
Sign in your google account
Click to expand...
Click to collapse
Thanks, i got it and it worked with Odin!