Database Develop

[Q] Help unbricking

Hi,
I have a Sprint htc one that I had previously unlocked, rooted and installed twrp and cm10.1 on. I was trying to restore the factory rom and now I can't boot up. seams like i have deleted all OS'. I can open the bootloader and twrp. I can not find any zip in twrp to reinstall cm10 just to get the phone working again. I have tried the adb function in twrp but it keeps failing. i have also tried to install the RUU file but can not get it to work. it states that my device has 1.31.651.2 and the RUU I'm trying to use is 1.29.651.7. Is there somewhere I can download the 1.31.651.2 image version. Or is there another way to unbrick my phone.

help
Now I cannot get into TWRP.

Can you get into bootloader?
wondernad said:
Now I cannot get into TWRP.
Click to expand...
Click to collapse
1) Get into bootloader (Power and volume down)
2) go to fastboot
3) Copy the recovery you want to the directory you use for abd and rename it recovery.zip
4) fastboot flash recovery recovery.zip
5) Run fastboot erase cache
6) Then open recovery
7) Go to sideload and sideload a ROM you want. Make sure that is for SPRINT HTC ONE
8) Reboot and good luck

imurg said:
1) Get into bootloader (Power and volume down)
2) go to fastboot
3) Copy the recovery you want to the directory you use for abd and rename it recovery.zip
4) fastboot flash recovery recovery.zip
5) Run fastboot erase cache
6) Then open recovery
7) Go to sideload and sideload a ROM you want. Make sure that is for SPRINT HTC ONE
8) Reboot and good luck
Click to expand...
Click to collapse
Ok so im in fastboot. Is the recovery the 1.31.651.2ruu? or should it be twrp or the like?

wondernad said:
Ok so im in fastboot. Is the recovery the 1.31.651.2ruu? or should it be twrp or the like?
Click to expand...
Click to collapse
Get your recovery here
http://www.teamw.in/project/twrp2/171
After that you should be able to get to sideload in advanced

sideload
how long should the sideload take?

wondernad said:
how long should the sideload take?
Click to expand...
Click to collapse
It takes a while depending on how big the ROM is. Buy you can see the advance in the % dont worry it'll get there
Patience... is it grasshopper?

imurg said:
It takes a while depending on how big the ROM is. Buy you can see the advance in the % dont worry it'll get there
Patience... is it grasshopper?
Click to expand...
Click to collapse
It doesn't give me a %. I'm wondering if its recognizing my device. I do cmd adb devices and it doesn't show the phone. but the phone says it is waiting for package. I've tried it on my desktop(xp but runs ok) and my laptop(windows 7, but slow).

wondernad said:
It doesn't give me a %. I'm wondering if its recognizing my device. I do cmd adb devices and it doesn't show the phone. but the phone says it is waiting for package. I've tried it on my desktop(xp but runs ok) and my laptop(windows 7, but slow).
Click to expand...
Click to collapse
It doesn't seem to recognize the phone. Do you have the latest HTC SYNC Manager? it has the drivers

imurg said:
It doesn't seem to recognize the phone. Do you have the latest HTC SYNC Manager? it has the drivers
Click to expand...
Click to collapse
Yes I did reinstall the drivers. trying to update my android sdk right now.

wondernad said:
Yes I did reinstall the drivers. trying to update my android sdk right now.
Click to expand...
Click to collapse
Just run "adb version" latest is 1.0.31

imurg said:
Just run "adb version" latest is 1.0.31
Click to expand...
Click to collapse
That seams to open a command window for about a millisecond.

wondernad said:
That seams to open a command window for about a millisecond.
Click to expand...
Click to collapse
You need to open a command window. Double click command prompt (The black icon with the c:\_)

imurg said:
You need to open a command window. Double click command prompt (The black icon with the c:\_)
Click to expand...
Click to collapse
ok it is the latest version

wondernad said:
ok it is the latest version
Click to expand...
Click to collapse
Now do not close the command window and try adb devices
If you see your device then try the sideload again without closing the command window until you are finished.

imurg said:
Now do not close the command window and try adb devices
If you see your device then try the sideload again without closing the command window until you are finished.
Click to expand...
Click to collapse
It still does not see the device. says list of devices attatched and has a blank space. then the command prompt comes back up

wondernad said:
It still does not see the device. says list of devices attatched and has a blank space. then the command prompt comes back up
Click to expand...
Click to collapse
Still not seeing the device. I've tried switching versions of twrp and twrp sideload keeps saying failure. so I put CWM on it and it is opening sideload but the device is not recognized by the computer.

wondernad said:
It still does not see the device. says list of devices attatched and has a blank space. then the command prompt comes back up
Click to expand...
Click to collapse
I think the safest at this point where FASTBOOT recognizes your devices but ADB doesn't is to go back to stock flashing a RUU this only requires FASTBOOT.
This thread will show you how
http://forum.xda-developers.com/showthread.php?t=2251800
Best of lucks

imurg said:
I think the safest at this point where FASTBOOT recognizes your devices but ADB doesn't is to go back to stock flashing a RUU this only requires FASTBOOT.
This thread will show you how
http://forum.xda-developers.com/showthread.php?t=2251800
Best of lucks
Click to expand...
Click to collapse
That isn't working either. the only RUU file I can find is for 1.29.651.10RUU instead of the 1.31.651.2RUU. I have tried running it anyway hoping to limp it back to life but it won't take it. I really need the 1.31.651.2RUU. but can't find it.

http://forum.xda-developers.com/showthread.php?t=2391161&page=4
chack this

[Pure Edition][Root] Superboot style root for MotoX 2014 Pure Edition

Follow directions, do NOT flash this image. Flashing the image will bootloop you (easily fixed by flashing proper boot.img). You must only BOOT this image. Again DO NOT FLASH IT, I won't help you out of any mess you get yourself into with this.
Unlock your device with Motorola's site
Boot Image
Device will boot up, install su and quickly reboot.
Then install Chainfire's SuperSU from the Play Store
unzip pure2014sb.zip
adb reboot bootloader
fastboot boot pure2014sb.img

Running up in Moto X Retail BR, Tks

Thanks!!! Now my weekend is complete.
Sent from my SCH-I545 using XDA Free mobile app

I am a new user can you elaborate how should i start?
I have a Pure Edition Indian Variant

Does this wipe your phone data at all? My phone data was completely wiped when I unlocked the bootloader, so I want to make sure that doesn't happen again.

TBayTom said:
Does this wipe your phone data at all? My phone data was completely wiped when I unlocked the bootloader, so I want to make sure that doesn't happen again.
Click to expand...
Click to collapse
No man, wipe completely is only when unlock bootloader.

Can Someone help me with elaborated steps ?

kartik.bose said:
Can Someone help me with elaborated steps ?
Click to expand...
Click to collapse
Check your inbox.
Sent from my Sexus X XT1095

Can you send that info my way too please? I've unlocked my bootloader but not sure where to go from here...

jcase, awesome as always. You are such a great help to all of us "regular people" here at XDA.

From Droidviews: http://www.droidviews.com/root-motox-2014-pure-edition-with-superboot/
Prerequisites
A Moto X 2014 with unlocked bootloader. You can unlock the bootloader by following the instructions given at Motorola official page.
Set up ADB and Fastboot on your computer or download the minimal ADB and fastboot tool from here (unzip it).
Install Motorola USB Drivers on your computer.
Download the modified boot image by jcase: pure2014sb.zip
Open Settings> Developer options and enable USB Debugging on your device.
Root MotoX 2014 Pure Edition with Superboot
Having taken care of the prerequisites mentioned above, you can now proceed to root your Moto X 2014. Just follow the steps given below.
1. Extract the pure2014sb.zip file and copy the pure2014sb.img file into the platform-tools folder (in case you have Android SDK installed) or copy the files into the mfastboot v2 folder.
2. While the folder with ADB and fastboot files is open, right-click on an empty space and select “Open command window here” option to launch a cmd.
3. Connect your Moto X 2014 to computer using a USB cable.
4. Now type the following command in the cmd window and press the Enter key:
adb reboot bootloader
5. Your phone will reboot into the Fastboot mode.
6. Then issue the following command:
fastboot boot pure2014sb.img
7. When the phone boots up, install su and quickly reboot it.
8. When the device boots up again, go to Google Play store and install the SuperUser app.

Motorola site says my phone is not elgible for unlocked bootloader. Have Tmo pure edition 2014 Moto X. Any ideas?

So for the rest of us that got a carrier phone (not the pure edition) -
I got the ATT one with all the bloat on it. I'd really like to get rid of that crap.
Is there some way I could flash one of the factory gsm images here? via the stock recovery or via adb?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images

iNiREALiZED said:
Motorola site says my phone is not elgible for unlocked bootloader. Have Tmo pure edition 2014 Moto X. Any ideas?
Click to expand...
Click to collapse
I had the same issue go through the whole code and make sure all spaces are gone including in front of the first character and you should be good

cpolly69 said:
So for the rest of us that got a carrier phone (not the pure edition) -
I got the ATT one with all the bloat on it. I'd really like to get rid of that crap.
Is there some way I could flash one of the factory gsm images here? via the stock recovery or via adb?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Click to expand...
Click to collapse
As of now, no you cant. ATT may or may not (probably not) get a bootloader unlock. It probably will eventually get root though, and when it does you can use a root app to uninstall those system apps from ATT. No guarantee the phone will work properly after you get rid of them though, it is possible that some OS modifications rely on parts of those apps.

yeah i pretty much can't wait until i get root access -
i'm pretty confident killing the att bloat isn't going to affect the it- i disabled every one of their apps within 10 minutes of having the phone...
i just wish i could load up ti backup and get rid of them...

bostonirishguy13 said:
From Droidviews: http://www.droidviews.com/root-motox-2014-pure-edition-with-superboot/
Prerequisites
A Moto X 2014 with unlocked bootloader. You can unlock the bootloader by following the instructions given at Motorola official page.
Set up ADB and Fastboot on your computer or download the minimal ADB and fastboot tool from here (unzip it).
Install Motorola USB Drivers on your computer.
Download the modified boot image by jcase: pure2014sb.zip
Open Settings> Developer options and enable USB Debugging on your device.
Root MotoX 2014 Pure Edition with Superboot
Having taken care of the prerequisites mentioned above, you can now proceed to root your Moto X 2014. Just follow the steps given below.
1. Extract the pure2014sb.zip file and copy the pure2014sb.img file into the platform-tools folder (in case you have Android SDK installed) or copy the files into the mfastboot v2 folder.
2. While the folder with ADB and fastboot files is open, right-click on an empty space and select “Open command window here” option to launch a cmd.
3. Connect your Moto X 2014 to computer using a USB cable.
4. Now type the following command in the cmd window and press the Enter key:
adb reboot bootloader
5. Your phone will reboot into the Fastboot mode.
6. Then issue the following command:
fastboot boot pure2014sb.img
7. When the phone boots up, install su and quickly reboot it.
8. When the device boots up again, go to Google Play store and install the SuperUser app.
Click to expand...
Click to collapse
what mean's :
7. When the phone boots up, install su and quickly reboot it
install su = superSU apk ?
thanks for help

jonata said:
what mean's :
7. When the phone boots up, install su and quickly reboot it
install su = superSU apk ?
thanks for help
Click to expand...
Click to collapse
This 7th step is automatic. The phone will boot and install su files and quickly reboot after that.
Once it boots up, go to the store and download SuperSU.

MaKTaiL said:
This 7th step is automatic. The phone will boot and install su files and quickly reboot after that.
Once it boots up, go to the store and download SuperSU.
Click to expand...
Click to collapse
and where is su files ?
or, where I can Find it ?
need to copy in the memoty of phone ?
thanks for help

I would think the su files are in the img file that was previously flashed in an earlier step. Please correct me if I'm wrong!

[Q] sideloading of 5.0.1 OTA fails

Okay, I have the Nexus 6 (T-Mobile), rooted stock. I also have the Nexus 10. On both, I tried to sideload the 5.0.1 OTA update... and it failed in the exact same manner.
Obviously, I'm doing something wrong, but I have no idea what.
I did the Nexus 10 on a Windows 7 box, and I'm trying the Nexus 6 on a Linux machine. Same. Exact. Problem.
What I'm doing is this:
adb reboot bootloader
Arrow up to recovery, hit the power button to select
Hold down the power button and press the up button
Select "Sideload from ADB" (can't remember the exact wording, but basically, that)
adb sideload <verylongfilename.zip>
The update starts... and gets to 48% on my computer, and then ends. (I don't mean that it pauses or hangs, I mean it "finishes" -- it's done and back at the prompt). On the phone, at that time, it says "system has been remounted r/w; reflash device to reenable ota updates"
So that's where I'm at. On my Nexus 10, I ended up wiping it and just doing the full stock image install to get 5.0.1 -- that worked fine. On my phone, though, I really don't want to lose my entire setup just to get the bump from 5.0 to 5.0.1.
Can anyone tell me what the heck I'm doing wrong? It has to be something I'm doing or something I have configured wrong or ... I don't know. But the process clearly works for many, many people, and the fact that I have the same problem with two different devices on two different computers... it has to be my process, or something I've done to my devices.
Both devices are rooted stock, with stock recovery.
Any help you guys can provide would be greatly appreciated!!

you cant update it via your phone. you need to flash the update via fastboot, while you are in your bootloader.

simms22 said:
you cant update it via your phone. you need to flash the update via fastboot, while you are in your bootloader.
Click to expand...
Click to collapse
Right, I'm not trying to do it from my phone, I'm doing it from my computer. What am I doing wrong with my adb sideload process?

commonplace said:
Right, I'm not trying to do it from my phone, I'm doing it from my computer. What am I doing wrong with my adb sideload process?
Click to expand...
Click to collapse
then why are you trying to sideload it???
download it via your computer, extract the files from the zip, boot your phone into the bootloader, connect it to your computer, run fastboot devices(to make sure that the computer sees your device, then run the flash-all script.

simms22 said:
then why are you trying to sideload it???
download it via your computer, extract the files from the zip, boot your phone into the bootloader, connect it to your computer, run fastboot devices(to make sure that the computer sees your device, then run the flash-all script.
Click to expand...
Click to collapse
I was following directions found elsewhere (AndroidCentral and another site). I see now that adb sideload is not the answer, and that fastboot flash IS.
Phone = upgraded. Thanks for steering me in the right direction!

I had rooted 5.0 and read on Google+ that update over the air would not work. I used this guide to update to 5.0.1 and lost no data, nor had to reinstall anything.
http://forum.xda-developers.com/nexus-6/help/help-5-01-wipe-t2970924

I need some help unbricking my fire...

Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA!

Do you know if you had amazon FireOS version 5.0.1 or 5.1.1?
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
drillster said:
I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
Click to expand...
Click to collapse
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.

Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740

hAtE NeVeR dIeS said:
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
Click to expand...
Click to collapse
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36

blueberry.sky said:
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
Click to expand...
Click to collapse
I have 5.1.1... yeah, thanks.

blueberry.sky said:
Do you know if you had amazon FireOS ve wrsion 5.0.1 or 5.1.1?
Click to expand...
Click to collapse
I have 5.1.1.
blueberry.sky said:
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
Click to expand...
Click to collapse
Yeah I selected apply update from adb, adb devices was blank, didn't work.
blueberry.sky said:
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Click to expand...
Click to collapse
I went into fastboot mode, installed twrp, and nothing happened because yes, its 5.1.1.

I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..

blueberry.sky said:
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
Click to expand...
Click to collapse
Do you have any ideas on how to do this? I would greatly appreciate it.
Thank you!

Since I haven't read anyone try it before, there would be some risk. I suppose you are already bricked, seemingly without a way to fix it, but you could brick it harder. You might be able to get adb working. I may not have any ideas on how to get adb working for you, but someone else might know. If you try flashing the stock OS via fastboot, there is a chance you could brick it in a different way.
The command would be
Code:
fastboot update <filename-of-stock-firmware.zip>
But we don't have a .zip stock firmware file. In twrp recovery you can just rename the .bin file to .zip & it works. Not sure if that will also work for fastboot. My guess is it won't work & might brick you.
Also be aware, on Fires that self-updated to FireOS 5.1.1 (or came with 5.1.1 new) you must only flash 5.1.1. Attempting to flash 5.0.1 will brick it 100% of the time & it's unrecoverable.

drillster said:
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
. . .
Click to expand...
Click to collapse
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.

I have same issue.
[QUOTE=drillster;64617577]Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA![/QUOTE]
I did the same thing. Slim worked great, tried to flashfire CM12, ot bricked. Can get fastboot, but nothing else. Afraid to try update from fastboot.

I just want to say thanks to everybody who contributed, I'm really appreciative of the support, especially because I didn't expect it, haha! Listening to blueberry.sky I'm going to try the flashboot update, because it's either that or a bricked device. School just started so I got busy with that.
DoLooper said:
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
Click to expand...
Click to collapse
So when I have it in adb mode, the fire doesn't seem to show up anywhere in any of my devices, and I can only find it when it's in fastboot mode. So when it's in that mode, I've tried Android ADB Interface, Android ADB Composite Interface, and when I go back to adb sideload, it's just not there in device manager. I don't know what this means, so any speculation? But no matter what mode I'm in or what driver I'm using, I can't seem to get it to show up in adb when in sideload mode.
Again, thanks everybody, and I hope anybody else in the future with this issue can refer to this thread for a lead!

So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I didn't rename the Slim and this is what I get:
C:\path\to\SuperTool>fastboot update Slim-ford-5.1.1.build.2.2b-20151210.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!

drillster said:
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
Click to expand...
Click to collapse
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?

thekrakah said:
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
Click to expand...
Click to collapse
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip

drillster said:
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
Click to expand...
Click to collapse
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.

thekrakah said:
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
Click to expand...
Click to collapse
On my device, I can get fastboot, but not adb. if I reboot from fastboot, I only get the
CM logo and it sticks there permanently until I power off. When I boot to fastboot, the screen is blank but my Windows PC can see the device and return the SN. I can issue the command to reboot to bootloader, but reboots to fastboot with "fastboot" in small letters at the bottom of the screen. What else can I try? Thanks for all the help offered so far.

What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.

blueberry.sky said:
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
Click to expand...
Click to collapse
When I try to get into recovery, it boots with a blank screen. At that point, I can connect to my PC, type fastboot devices, and it will show me device. Then I try to reboot-bootloader, and it reboots to fastboot, but this time it says fastboot on the screen. I can't seem to get to recovery

watch this video to see if it helps.
https://www.youtube.com/watch?v=RQLoH-ahjy4

Question S21 Ultra will not go into download mode

My s21 Ultra has the October update and has stopped at that point. I haven't been able to get One UI 5 Android 13 update. I've tried putting the phone into download mode from instructions I've picked up here and just can't get it to cooperate. Can I use the files needed for Odin to sideload using adb or do I need the OTA update file. Located in US with an unlocked S21 Ultra

You probably have a snapdragon device being a US phone. I would post something on the snapdragon forum. Aside from that to put mine in download mode i have the device switched off, hold volume up while inserting the cable (which is already connected to the pc).

jpylez71 said:
My s21 Ultra has the October update and has stopped at that point. I haven't been able to get One UI 5 Android 13 update. I've tried putting the phone into download mode from instructions I've picked up here and just can't get it to cooperate. Can I use the files needed for Odin to sideload using adb or do I need the OTA update file. Located in US with an unlocked S21 Ultra
Click to expand...
Click to collapse
If you have adb installed on your computer, you can run the command adb reboot bootloader which is foolproof method to get into download mode. The button combo is hit-and-miss most of the time.

amirage said:
If you have adb installed on your computer, you can run the command adb reboot bootloader which is foolproof method to get into download mode. The button combo is hit-and-miss most of the time.
Click to expand...
Click to collapse
You can also run the same command without the adb part in any terminal app(e.g, termux)

amirage said:
If you have adb installed on your computer, you can run the command adb reboot bootloader which is foolproof method to get into download mode. The button combo is hit-and-miss most of the time.
Click to expand...
Click to collapse
I've tried that method also and it just boots to the phone, that's one of the reasons why I'm stumped at this point. This is the first Samsung phone that has given me this issue.