Hi, I had a rooted firmware on my firetv and work with it fine for almost a year. a week ago i changed some system files and now my firetv wont boot up and its stock in White amazon logo nothing further and im unable to see even the coloured logo!
My FTV didnt have unlocked bootloader or CWM.
I have a Male A to Male A USB cable. I saw a post here regarding the use of a cable, and that it gained the user Fastboot. So, in trying I disconnected the Fire TV power, connected the Fire TV to my laptop via the male to male usb cable, and plugged the power back on.
My laptop reported in the device manager (Windows 7), "FireTV" with no drivers loaded. I manually used the Android ADB drivers from Google, but was unable to connect to the Fire TV via Fastboot or ADB while in this mode. It seems that at least, the Fire TV is not in USB host mode while at the white Amazon Logo.
I then tried the Alt+PrtScn+i command while the Amazon Fire TV but it never goes to any recovery mode. i have tried it even 10times no luck!
I have spent hours to know how to fix this problem still no solution. please someone help me :crying::crying:
Im waiting for your generous advise.
Also is there anyway that i can reflash stock firmware through fastboot recovery?
shamid202 said:
Also is there anyway that i can reflash stock firmware through fastboot recovery?
Click to expand...
Click to collapse
You need an unlocked bootloader to use A to A usb. If you can't access recovery I'm sorry to say I don't think you can flash anything with your current setup.
Hopefully I'm missing something...
Out of curiosity, what were you trying to accomplish by moving system files? Good luck.
like there is no way at all?!
shamid202 said:
like there is no way at all?!
Click to expand...
Click to collapse
Depending on what version of the bootloader you have, in theory fastboot oem emmc-info should get your the numbers you need to use the Fire HDX unlock. Once unlocked, you should be able to flash CWM and then flash one of the prerooted roms.
rbox said:
Depending on what version of the bootloader you have, in theory fastboot oem emmc-info should get your the numbers you need to use the Fire HDX unlock. Once unlocked, you should be able to flash CWM and then flash one of the prerooted roms.
Click to expand...
Click to collapse
What do you exactly mean? its not a fire HDX its Fire TV. still what is OEM fastboot ?
shamid202 said:
What do you exactly mean? its not a fire HDX its Fire TV. still what is OEM fastboot ?
Click to expand...
Click to collapse
If you were on 51.1.0.2 software, and you can get fastboot working running the command 'fastboot oem emmc-info' will get you the information you need to use the HDX unlock on the fire tv. But if you weren't on 51.1.0.2, its not gonna work.
rbox said:
If you were on 51.1.0.2 software, and you can get fastboot working running the command 'fastboot oem emmc-info' will get you the information you need to use the HDX unlock on the fire tv. But if you weren't on 51.1.0.2, its not gonna work.
Click to expand...
Click to collapse
Hi
I believe im on that bootloader! my firetv infos are
(bootloader) 0x152b23645d
7090020141740FVD fastboot
I dont have Linux if any of you guys could generate the unlock.img file for me i would really appreciate it
shamid202 said:
Hi
I believe im on that bootloader! my firetv infos are
(bootloader) 0x152b23645d
7090020141740FVD fastboot
I dont have Linux if any of you guys could generate the unlock.img file for me i would really appreciate it
Click to expand...
Click to collapse
http://www.mediafire.com/download/j7vogdcdir8tk1x/shamid202-unlock.signed
thank you so much for that. but it says
C:\FTV>fastboot -t 0x1949 flash unlock unlock.signed
sending 'unlock' (0 KB)...
OKAY [ 0.005s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.022s
if im able to get this 0x152b23645d from my bootloader it means im able to unlock it ?
shamid202 said:
thank you so much for that. but it says
C:\FTV>fastboot -t 0x1949 flash unlock unlock.signed
sending 'unlock' (0 KB)...
OKAY [ 0.005s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.022s
if im able to get this 0x152b23645d from my bootloader it means im able to unlock it ?
Click to expand...
Click to collapse
No. If it fails you aren't on 51.1.0.2.
any other options at all??
anyone please ?
shamid202 said:
anyone please ?
Click to expand...
Click to collapse
can you try:
http://forum.xda-developers.com/fire-tv/general/hardware-root-via-emmc-chip-t2885344
any solution yet guys?
how do i creat unlock.signed file?
70900201411707U7 fastboot
(bootloader) 0x4501486126
Related
Hi guys I got 3HT7G model and I am trying to root it so I can install CM. I am having problem with getting device in to fastboot mode. I have several HTC phone and new Nexus 7 and my fastboot works perfectly, SDK is installed and all tools under C:\sdk\platform-tools
Now this is my first Kindle but from what I understand from before I had to always get in to bootloader/fastboot mode manually and only then ADB start to work. In here I see if "waiting for device" is active unit will automatically will get in to fastboot, well it does not for me. Any adias on wtf is going on here this is driving me mad. I have this Kindle drivers installed and adb is checked on in security. I am starting to think my 8.4.6 version is somehow diffirent from other. Anyone please help.
Thank you, once again other devices like Nexus 7 works and getvar command gives me needed answer ......
More details on what you have done would be nice, but basically you turn your kindle off, leave it u plugged, and on the PC run "fastboot -i 0x1949 getvar product", once it says waiting for device you plug your kindle in and it should go into fastboot. If you hear windows make a noise like something connected and disconnected very fast but it doesn't enter fastboot then you need to try to install the driver in my signature for the device as it appears on windows so you can successfully run the fastboot command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
More details on what you have done would be nice, but basically you turn your kindle off, leave it u plugged, and on the PC run "fastboot -i 0x1949 getvar product", once it says waiting for device you plug your kindle in and it should go into fastboot. If you hear windows make a noise like something connected and disconnected very fast but it doesn't enter fastboot then you need to try to install the driver in my signature for the device as it appears on windows so you can successfully run the fastboot command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yeah sorry should of known.
1. I tried adb devices
List of devices attached
B0C9100424551JHB device
2. I tried bin4ry tool v31 and instead of usual download/sending I got an path error ....
I was about to copy from prompt ...and it looks like for some reason this time it worked, I do see superuser app now but I did got an error there in the middle , don't know if it matters. I'll report if anything is messed up later on with ROM installation. Anyway to check ROOT status from stock system ? So I know this app is not just pretty face ?
managed to get everything installed here are last few output code:
C:\Users\Konstantin\Downloads\KindleFireHD89Root\stuff>fastboot -i 0x1949 flash
bootloader kfhd8-u-boot-prod-8.1.4.bin
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.019s]
writing 'bootloader'...
OKAY [ 0.035s]
finished. total time: 0.055s
C:\Users\Konstantin\Downloads\KindleFireHD89Root\stuff>fastboot -i 0x1949 flash
boot kfhd8-freedom-boot-8.4.3.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.445s]
writing 'boot'...
OKAY [ 0.562s]
finished. total time: 1.009s
C:\Users\Konstantin\Downloads\KindleFireHD89Root\stuff>fastboot -i 0x1949 flash
recovery kfhd8-twrp-2.6.0.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.445s]
writing 'recovery'...
OKAY [ 0.567s]
finished. total time: 1.014s
C:\Users\Konstantin\Downloads\KindleFireHD89Root\stuff>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.000s
C:\Users\Konstantin\Downloads\KindleFireHD89Root\stuff>[/CODE]
After reboot for about 30 mins now I see kindlefire logo (fire is blue in logo) It does not reboot or anything it just sits there. Oh man I hope I haven't screw something up. I tried to boot in to recovery, I could. I restarted again, and again I am on blue kindlefire logo. What's going on ? Anything I should try ? I don't have any roms inside device memory yet. In device manager I see Kindle with yellow mork on it (odd)
You have to put the ROM on the sdcard so you can flash it when it does this, use my tutorial to get a ROM on it, also try updating the drivers again for the device with an exclamation using the ones in my signature. http://forum.xda-developers.com/showthread.php?t=2459498
Technically you can also boot the device into stock rooted os, but you need to flash an older version from before they started making sure the boot loader was the same version as the os, otherwise when they don't match the end result is well, what you have before you right now.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I always do this to myself, ALWAYS. I panic and think this is the problem I and only I could possibly have and about 3 posts later I found like 10 more people with exact same problem that think this is first in the world just like me, anyhow I did sideload feature and loaded cm .zip and installed sideload.zip from install. I am looking at CM logo booting, so far so good.
P.S.
I was looking at that logo for sometime now, I had to do wipe data and restart once again. All good now.
Thank you !
HI!
Can anyone help with this? ADB works, i can boot into bootloader, "fastboot oem unlock" says it's already unlocked. If i use fastboot boot recovery.img:
downloading 'boot.img'...
OKAY [ 0.494s]
booting...
And nothing happens.
if I use "fastboot devices"
Android Fastboot fastboot
This tab running 5.1.1 and my OS is win10.
Thanks.
flekkelek said:
HI!
Can anyone help with this? ADB works, i can boot into bootloader, "fastboot oem unlock" says it's already unlocked. If i use fastboot boot recovery.img:
downloading 'boot.img'...
OKAY [ 0.494s]
booting...
And nothing happens.
if I use "fastboot devices"
Android Fastboot fastboot
This tab running 5.1.1 and my OS is win10.
Thanks.
Click to expand...
Click to collapse
Hello!
Did you successfuly root the device?
t0nck said:
Hello!
Did you successfuly root the device?
Click to expand...
Click to collapse
Yes, almost every oneclick root program can root it. But be cautios, if you root your device, you won't be able to unroot it completely, and your device won't get OTA updates anymore. I bricked my device when I wanted to properly unroot it.
I'm really hoping that someone here can help me. I'm using a Mac. I'm using a fastboot cable. I have a Kindle Fire HD 8.9" (2nd Gen) (Model #: 3HT7G). One day I left it charging. I came home and found the screen was completely red. I restarted it by holding down the power button for 40 seconds. That brought it back to normal. I used it for a couple of weeks and now I can't get it out of the red screen.
I called Amazon and they won’t help me because it’s out of warranty. They want to sell me a new one at a discounted price. I can’t get a new one because it can’t be shipped outside of the US. I’m in Vietnam.
I want to unbrick it by installing CyanogenMod 12.1. I am following the steps on the CyanogenMod wiki for “jem”.
I'm done with -
Step 1: Test your...
Step 2: Download the files...
When I get to Step 3 (Use fastboot to apply...), the first step is ok:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin (see below for my Terminal window)
The screen on my Kindle changed. It says in yellow text "fastboot mode" with a blue arrow pointing down. In the upper left in white text it says "writing bootloader...done".
The next step (step 2) is NOT ok:
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
It just says:
sending 'recovery' (8173 KB)...
I waited for about 40 minutes and then it came back with:
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
I'm a newbie and I have no idea what I'm doing. I'm just following the steps on the CyanogenMod wiki and praying that it will unbrick my Kindle Fire.
Here's my Terminal window:
Last login: Sat Sep 17 06:12:59 on console
Seans-MacBook-Pro:~ sean$ cd Desktop/android
Seans-MacBook-Pro:android sean$ ls
adb kfhd8-freedom-boot-8.4.6.img
cm-12 kfhd8-twrp-2.8.7.0-recovery.img
fastboot kfhd8-u-boot-prod-8.1.4.bin
Seans-MacBook-Pro:android sean$ fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
-bash: fastboot: command not found
Seans-MacBook-Pro:android sean$ ./fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
< waiting for device >
sending 'bootloader' (243 KB)...
OKAY [ 0.975s]
writing 'bootloader'...
OKAY [ 0.156s]
finished. total time: 1.131s
Seans-MacBook-Pro:android sean$ ./fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
sending 'recovery' (8173 KB)...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
You don't want to use the Jem instructions. You have an hdx. Try http://forum.xda-developers.com/kindle-fire-hdx and good luck!
Sent from my SGH-T999 using XDA-Developers mobile app
Shack70 said:
You don't want to use the Jem instructions. You have an hdx. Try http://forum.xda-developers.com/kindle-fire-hdx and good luck!
Sent from my SGH-T999 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm pretty sure it's a Kindle Fire HD. Not an HDX. On the back it just says "kindle". My KF doesn't have the shape of an HDX. It looks like the KF on love my fire dot com; "2012 Kindle Fire HD 8.9" (2nd Generation)". I posted already in the HDX forum (by mistake) before I posted here. Davey126 said I have a HD (not an HDX).
onwithsean said:
I'm pretty sure it's a Kindle Fire HD. Not an HDX. On the back it just says "kindle". My KF doesn't have the shape of an HDX. It looks like the KF on love my fire dot com; "2012 Kindle Fire HD 8.9" (2nd Generation)". I posted already in the HDX forum (by mistake) before I posted here. Davey126 said I have a HD (not an HDX).
Click to expand...
Click to collapse
If you have a Jem then you don't need a fastboot cable. I would get a different cable and use http://forum.xda-developers.com/showthread.php?t=2128175 as a guide to install custom firmware, not the wiki you are using.
Sent from my SGH-T999 using XDA-Developers mobile app
Shack70 said:
If you have a Jem then you don't need a fastboot cable. I would get a different cable and use http://forum.xda-developers.com/showthread.php?t=2128175 as a guide to install custom firmware, not the wiki you are using.
Sent from my SGH-T999 using XDA-Developers mobile app
Click to expand...
Click to collapse
When I had my KF connected to my Mac with the fastboot cable I typed in this:
./fastboot -i 0x1949 getvar product
It returned with this:
product: Jem-PVT-Prod-04
That means I have a Jem, right? Is a Jem a Kindle Fire HD?
onwithsean said:
When I had my KF connected to my Mac with the fastboot cable I typed in this:
./fastboot -i 0x1949 getvar product
It returned with this:
product: Jem-PVT-Prod-04
That means I have a Jem, right? Is a Jem a Kindle Fire HD?
Click to expand...
Click to collapse
Yes! OK, try doing what's in this video: https://m.youtube.com/watch?v=eSpTxlpumMY
I have a Mac.
onwithsean said:
I have a Mac.
Click to expand...
Click to collapse
Sorry no Mac experience. Can't you emulate or dual boot windows?
Shack70 said:
Sorry no Mac experience. Can't you emulate or dual boot windows?
Click to expand...
Click to collapse
I'll try it with a friend who has a Windows computer. I'll post back with the results.
onwithsean said:
I'll try it with a friend who has a Windows computer. I'll post back with the results.
Click to expand...
Click to collapse
Good luck
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Just a shot in the dark but have you enabled oem unlocking in developer options?
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
no unfortunately not , thats the problem
amans90 said:
no unfortunately not , thats the problem
Click to expand...
Click to collapse
Okay well I hope you can get your phone sorted now , if I've helped then please leave a thumbs up on my post I really appreciate it...
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Hi i have the same problem like you did you solve it ?
Dsn Fouad said:
Hi i have the same problem like you did you solve it ?
Click to expand...
Click to collapse
see below.
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Sent from my ONEPLUS A3003 using Tapatalk
n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
I dont know i flashed the lastest os and the old with sideload but it stuck on 45%
n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
Here
Dsn Fouad said:
Here
Click to expand...
Click to collapse
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Hmm, I thought he said he can enter bootloader and recovery. If so, reboot the phone in stock recovery and flash full Rom from local update.
Sent from my ONEPLUS A3003 using Tapatalk
tnsmani said:
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Click to expand...
Click to collapse
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Dsn Fouad said:
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Click to expand...
Click to collapse
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb and boot.
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
Oh i see now where can i find the lastest recovery and by how i need to flash it, in adb sideload (recovery.img) or fastboot flash recovery (oneplus recovery.img)?
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
I tried again but failed with official oneplus 3 recovery
Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here
Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
...
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
jeffrey268 said:
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Nah it will still fail, all because of that oem and device state locked, lol i buy a new phone used it 1 month i was having a update available i updated it and then boom 370€ gone just like that, it took me 4 month to got it, i just want to kill people now im very depressed right now god bless people like you thanks for your help.
Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
Click to expand...
Click to collapse
fastboot boot twrp.img
creating boot image...
creating boot image - 13133824 bytes
downloading 'boot.img'...
OKAY [ 0.442s]
booting...
FAILED (remote: image verification failed)
Click to expand...
Click to collapse
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?
Bolemichel said:
Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
fastboot boot twrp.img
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?
Click to expand...
Click to collapse
Have you tried flashing stock?
Bolemichel said:
Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
fastboot boot twrp.img
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?
Click to expand...
Click to collapse
Were you able to solve that?
FWIW, the state you're describing is not unheard of and requires to use the fwtool (reference, for example, here). But that, in turn, requires you can have TWRP installed... because with the bootloader in this limbo state, it also refuses to load TWRP on the fly using "fastboot boot ..."
xrad said:
Were you able to solve that?
FWIW, the state you're describing is not unheard of and requires to use the fwtool (reference, for example, here). But that, in turn, requires you can have TWRP installed... because with the bootloader in this limbo state, it also refuses to load TWRP on the fly using "fastboot boot ..."
Click to expand...
Click to collapse
No, meanwhile I returned it to google and got a new one. But thank you for help!