I am so frustrated. I tried rooting the kindle last week and it went into an endless loop of turning on and off. So I ordered a factory cable and when I plugged it in, it stayed on and fastboot recognized the device.
I tried a few commands and now it's turning on and off again! I can no longer get commands to read the device through fastboot.
what the hell do I do?
EDIT: Sorry I forgot to check off "this thread is a question"
Ok so if I leave the tablet unplugged for a while and replug it, I can send a command and have it go through before the tablet resets again.
But I don't know how to get it to stay in fastboot mode, and I don't know what to do once i'm actually IN fastboot mode (I dont have TWRP or whatever installed).
Any help is appreciated
EDIT: I tried this command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot -i 0x1949 boot c:\twrp-fire-2.1.0.img
creating boot image...
creating boot image - 10240 bytes
< waiting for device >
downloading 'boot.img'...
FAILED (command write failed (No such file or directory))
finished. total time: 0.005s
Hmmm did you try the kfu or the kindle fire unbrick utility?
Step-by-step
1) Make sure you have some charge left in your bricked Kindle. (one of my mistakes
2) Download "Kindle Fire Utility" or other utility that has the fastboot.exe command available.
3) Download twrp-blaze-2.0.0RC0.img (just google it)
4) Without connecting anything, run the command:
fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5) Connect the factory cable to your Kindle Fire
6) Connect the factory cable to you PC
7) Wait about 10 seconds.
8) DONE!!!!
all these steps above taken from http://forum.xda-developers.com/showthread.php?p=25113108&posted=1#post25113108
the OP deserves the credit if this works for you
You're doing it wrong. Unlike TWRP 2.0.0RC0, 2.1.0 is not supposed to be loaded into boot and your system is probably panicking. You need a bootloader first.
First you need a bootloader with recovery selection. There are several to choose from at this point.
I would recommend FIREFIREFIRE 1.3 or 1.2
Download one of them and extract the bin somewhere. Lets say c:\firebuild\
Next we need a recovery partition, you already have that in the twrp-fire-2.1.0.img, so you should be set. Copy that to c:\firebuild\ as well.
Now, lets make sure you have the andriod sdk in your path. This way you don't have to be in the C:\Program Files (x86)\Android\android-sdk\platform-tools folder to run commands and your images can be elsewhere.
1. right click on computer and select properties.
2. click on advanced settings on the left of the window.
3. click on environment variables at the bottom right of the window.
4. in the system variables section scroll down until you find path, highlight it, and select edit.
5. paste the following at the end of the line.
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
For example, my path is:
Code:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;;C:\Program Files\Lucidlogix Technologies\VIRTU;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
Now that your path is set, lets go into the command prompt.
First lets change the directory to c:\firebuild\ :
Code:
cd c:\firebuild
In this folder we should have u-boot.bin and twrp-fire-2.1.0.img.
First lets load your bootloader.
Code:
fastboot -i 0x1949 flash bootloader u-boot.bin
and start your device.
I would recommend rebooting after flashing this, so run
Code:
fastboot reboot
if it does not reboot on its own.
Now lets run
Code:
fastboot flash recovery twrp-fire-2.1.0.img
Note: Because we have the bootloader now the -i 0x1949 is no longer needed.
After running the above, the kindle should automatically start into recovery.
From here you will be able to mount it as an external drive and copy over any rom you would like to use.
Pick something from here Kindle Fire Development *FULL LIST* - 17.04.2012 - under the Custom / Stock Roms section.
three-p-o said:
You're doing it wrong. Unlike TWRP 2.0.0RC0, 2.1.0 is not supposed to be loaded into boot and your system is probably panicking. You need a bootloader first.
First you need a bootloader with recovery selection. There are several to choose from at this point.
I would recommend FIREFIREFIRE 1.3 or 1.2
Download one of them and extract the bin somewhere. Lets say c:\firebuild\
Next we need a recovery partition, you already have that in the twrp-fire-2.1.0.img, so you should be set. Copy that to c:\firebuild\ as well.
Now, lets make sure you have the andriod sdk in your path. This way you don't have to be in the C:\Program Files (x86)\Android\android-sdk\platform-tools folder to run commands and your images can be elsewhere.
1. right click on computer and select properties.
2. click on advanced settings on the left of the window.
3. click on environment variables at the bottom right of the window.
4. in the system variables section scroll down until you find path, highlight it, and select edit.
5. paste the following at the end of the line.
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
For example, my path is:
Code:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;;C:\Program Files\Lucidlogix Technologies\VIRTU;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
Now that your path is set, lets go into the command prompt.
First lets change the directory to c:\firebuild\ :
Code:
cd c:\firebuild
In this folder we should have u-boot.bin and twrp-fire-2.1.0.img.
First lets load your bootloader.
Code:
fastboot -i 0x1949 flash bootloader u-boot.bin
and start your device.
I would recommend rebooting after flashing this, so run
Code:
fastboot reboot
if it does not reboot on its own.
Now lets run
Code:
fastboot flash recovery twrp-fire-2.1.0.img
Note: Because we have the bootloader now the -i 0x1949 is no longer needed.
After running the above, the kindle should automatically start into recovery.
From here you will be able to mount it as an external drive and copy over any rom you would like to use.
Pick something from here Kindle Fire Development *FULL LIST* - 17.04.2012 - under the Custom / Stock Roms section.
Click to expand...
Click to collapse
Thank you SO MUCH! I was able to get both files on. I don't know how to get into recovery, but here is the output:
c:\firebuild>fastboot -i 0x1949 flash bootloader u-boot.bin
< waiting for device >
sending 'bootloader' (203 KB)...
OKAY [ 0.055s]
writing 'bootloader'...
OKAY [ 0.051s]
finished. total time: 0.106s
c:\firebuild>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.002s
c:\firebuild>fastboot flash recovery twrp-fire-2.1.0.img
sending 'recovery' (6 KB)...
OKAY [ 0.006s]
writing 'recovery'...
OKAY [ 0.045s]
finished. total time: 0.051s
c:\firebuild>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.003s
c:\firebuild>fastboot -i 0x1949 boot twrp-fire-2.1.0.img
creating boot image...
creating boot image - 10240 bytes
downloading 'boot.img'...
OKAY [ 0.006s]
booting...
OKAY [ 0.003s]
finished. total time: 0.010s
When you first turn the kindle on you will get a yellow triangle (FFF 1.2) or a Kundle Fire logo with the Android (FFF 1.3). When in that screen tap the power button until it turns orange. It should then boot you into TWRP.
From there you can goto mount and then click mount usb storage, this will allow you to copy the rom you picked to the SDCard.
After copied, unmount, then goto install and select to install the rom.
Oh, one more thing. Don't forget to wipe cache, dalvik-cache, and factory restore.
So, the instructions are below pulled out of the Back to Sense thread.(http://forum.xda-developers.com/showthread.php?t=2733523) got to the end of what i've pasted no problems......
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Everything went well until the after that... I stuffed up royally.. my failure is below...
PS C:\adb> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.014s
PS C:\adb> fastboot flash recovery TWRP_Recovery_2.8.6.2_M8_CPTB.img
target reported max download size of 1830711296 bytes
sending 'recovery' (16804 KB)...
OKAY [ 1.515s]
writing 'recovery'...
OKAY [ 0.940s]
finished. total time: 2.455s
fastboot boot TWRP_Recovery_2.8.6.2_M8_CPTB.img
I realize i skipped the below steps...
Boot into stock recovery
Factory reset
Reboot into bootloader
It would seem that what i've gone and done is flashed TWRP into the Boot Partition or something? now whenever i boot up, it won't show the fastboot screen, it goes straight to "entering recovery" and sits there forever.... one thing worth noting, i can see the internal storage(well some of it) the device is recognized in windows and then internal storage is 10.5gb free out of 10.6gb, Navigating to the internal directory shows 3 directories: 0, obb, and TWRP. 0 is a neverending folder. every 3rd layer deep click it shows the root directory again...
Help would be very very much appreciated!
cheers!
EDIT: Sorted! It turns out i'm an idiot and wasn't pushing volume down fast enough to get into bootloader. Sorry guys!!!!
Cameltoemcgee said:
It would seem that what i've gone and done is flashed TWRP into the Boot Partition or something? now whenever i boot up, it won't show the fastboot screen, it goes straight to "entering recovery" and sits there forever....
EDIT: Sorted! It turns out i'm an idiot and wasn't pushing volume down fast enough to get into bootloader. Sorry guys!!!!
Click to expand...
Click to collapse
If the bootloader was overwritten, damaged or corrupted, the phone would be bricked, and the screen would not come on at all.
This is the second post on the first page where the OP solved their own issue. You guys are getting good at fixing your own problems.
Hey guys !
So since i messed up with the recovery mode, i'm stucked in the fastboot with no Download mode (recovery doesnt work neither).
So after searching 3 days in the internet i found the acces to fast through adb by puting a new laf.img in order to restore the download mode and flash a stock firmware !
My problem is that when i try to enter the command on the cmd, i get severals errors, take a look :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase laf
erasing 'laf'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 2147483648 bytes
sending 'laf' (18432 KB)...
OKAY [ 0.581s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.615s
Also command : "fastboot boot laf.img" result to "Failed(remote: dtb not found) instead of flash write failure..
Of course i have my G3 855 32GB in download mode (but it goes into fastmode), so when i try a command, lines are added in the screen etc..
Does that mean that my laf.img don't work? I assumed that so i try several, but does it have to be the exact same one as the one who was in my phone before( v20a if i record correctly ) or could it be from any 855 32GB version ?
I also thought it could be a recognition problem as when i type "adb devices" or "adb shell" nothing is found..
If someone has any clue or a link to some guide i'll be more than joyful, thanks in advance !
Try adb fastboot when writing command hope it helps
Anik49 said:
Try adb fastboot when writing command hope it helps
Click to expand...
Click to collapse
Hey thank you so much for answering !
What do you mean by that, i already download the adb/fastboot driver and launch a cmd in the directory they are at, writing "adb fastboot" has no result neither, can you be more specific please ?
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again:
Click to expand...
Click to collapse
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly http://forum.xda-developers.com/lg-g...-9008-t3072091
BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
Click to expand...
Click to collapse
Like @BigsyBiggins said, this is the guide which could fix your phone. HW Part is not too hard!
Anik49 said:
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly
Click to expand...
Click to collapse
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
SisGG said:
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
Click to expand...
Click to collapse
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Ernesto0023 said:
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Click to expand...
Click to collapse
Well I think i'm still under warranty, so i dont wanna touch to much on the hardware.
So do you think, if i send it back without touching anything, saying i put it on charge one night and the next morning it was like this, the warranty could work?
If they found it's rooted or they understand you did something with your software your warrenty is void ?
SisGG said:
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
Click to expand...
Click to collapse
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
miguexneox said:
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
Click to expand...
Click to collapse
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
SisGG said:
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
Click to expand...
Click to collapse
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
datrmon said:
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
Click to expand...
Click to collapse
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Ghikya said:
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Click to expand...
Click to collapse
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
datrmon said:
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
Click to expand...
Click to collapse
It seems that your phone's bootloader is locked, you can try to execute this command: "fastboot oem unlock", and then check state with "fastboot oem device-info". But some people says that it does nothing, so you can try and check for yourself.
You can also try to boot directly an image from fastboot for eaxmple:
Code:
fastboot boot laf.img
or
Code:
fastboot boot twrp.img
So if you could successfully boot a laf image you would be able to access download mode, and if you could boot a custom recowery then you could access ADB and to try to flash other partitions, or even flash a custom rom...
Hello all,
I am having trouble flashing lineageos on my pixel 4 device.
The bootloader is unlocked.
When I try to flash the recovery I get the error "cannot load recovery.img.IMG"
I tried a few things to solve this:
-I added the recovery file in windows to the folder "platform tools"
-I added ".IMG" to the recovery file itself
-I updated fastboot & adb
-I updated my system (windows 10)
-I tried different commands: flashboot flash recovery, fastboot flash boot and fastboot boot recovery + drag&drop the recovery file to cmd
Reaching out to you for a little help, please.
Thx & regards
caraman said:
Hello all,
I am having trouble flashing lineageos on my pixel 4 device.
The bootloader is unlocked.
When I try to flash the recovery I get the error "cannot load recovery.img.IMG"
I tried a few things to solve this:
-I added the recovery file in windows to the folder "platform tools"
-I added ".IMG" to the recovery file itself
-I updated fastboot & adb
-I updated my system (windows 10)
-I tried different commands: flashboot flash recovery, fastboot flash boot and fastboot boot recovery + drag&drop the recovery file to cmd
Reaching out to you for a little help, please.
Thx & regards
Click to expand...
Click to collapse
Ok, I managed the problem, I guess.
I startet power shell from the "platform tools" folder.
Now there is a other issue:
PS C:\Program Files\platform-tools> fastboot flash boot recovery.img
target reported max download size of 268435456 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.535s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 1.836s
PS C:\Program Files\platform-tools>
The problem seems to be the partition, but I have no idea where to start troubleshooting...
Still reaching out to you for a little help, please...
Thx, regards
Hello guys,
Please help me because I'm stuck. I'm trying to install latest TWRP on my OP5 with no success. Let me tell you what I tried.
- I'm running on OOS 10.0.1
- sucessfully installed ADB and drivers on Windows 10.
- sucessfully unlocked bootloader
Then I downloaded latest TWRP, renamed it to twrp.img and placed it in a folder where ADB and fastboot are. Device is seen in both ADB and fastboot.
When in fastboot I tried first the command:
C:\>fastboot boot twrp.img
fastboot: error: cannot load 'twrp.img': No such file or directory
then I googled and tried with file directory:
C:\>fastboot flash recovery c:\adb\twrp.img
Sending 'recovery' (35228 KB) OKAY [ 1.025s]
Writing 'recovery' OKAY [ 0.164s]
Finished. Total time: 1.220s
The second command with direct source I tried both using USB 3.0 and via USB hub and it doesn't work. When I reboot to recovery it enters to the stock OP recovery and no sign of TWRP.
Can you please help me?
Thanks in advance!
Maciej
Hi, i could be misreading your steps but have you tried renaming the twrp image to twrp and then try fast booting with twrp.img again. It may be that by including the .img in the file name it is looking for twrp.img.img.
I'm no ADB expert but that may be all that's needed as it reads like everything else is working as should from my limited experience.