Related
please..
i have problem with bootloader version 41.1A
i want to Downgrade to version 41.18 or 41.19
anyone know ..??
please share it
thank you
Up
Me too
My bootloader v 41.1A I downgrade 41.18 Help
Why do you need to downgrade? Messing with Bootloaders can destroy your phone.
even i want to downgrade... I cant flash custom recovery on 41.1A
poran123 said:
even i want to downgrade... I cant flash custom recovery on 41.1A
Click to expand...
Click to collapse
Bootloader cannot be downgraded. You're stuck on w/e version you have currently installed.
Okay so I'm stuck on 41.1A and my phone will continue to restart itself and then stuck in bootloop till the battery dies... and then when I connect it to the charger boot's up normally...
@lost101
Can you please let me know how to check bootloader version?
I am using Moto G XT1033 model(Asia).
It was updated to Lollipop 5.0.2 by Motorola Stock Lollipop update.
Later on I had unlocked bootloader and downgraded it to Kitkat 4.4.4 using this thread.
I don't have any clue about current version of bootloader in my Moto G.
I want to try Lollipop 5.1 Optimized stock rom link here, so just wanted to ensure compatibility of bootloader so that my phone works after flashing it.
kalpesh.fulpagare said:
@lost101
Can you please let me know how to check bootloader version?
Click to expand...
Click to collapse
Enter bootloader (hold volume-down while turning it on), read text on screen (second line).
I too want to know if there is a way to downgrade or at least reflash my damaged bootloader which is causing weird behaviour.
Sent from my Nexus 6P using Tapatalk
I have the exact same problem.
Stuck on 41.1A
Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
SLATE21&MOTOG said:
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
Click to expand...
Click to collapse
Creating such a zip is possible, but flashing it may either not work or hard brick your phone.
How to install working recovery on 41.1A bootloader
I had the situation on my Moto G XT1039 where I had formatted the partitions on my phone (using my old CWM recovery), then flashed the 41.1A bootloader, but 41.1A would not allow me to flash any recovery.
So I had a working bootloader, but no recovery and no OS. And apparently no way to install a recovery, to install an OS...
I got the phone back like this:
- Flashed 4.4.4 stock manually using the bootloader (if you do this, DO NOT flash the 4.4.4 motoboot.img, according to everything on here that will permanently brick your phone; I am not sure about partition gpt.bin - I flashed this, but I was already on the 4.4.4 partition layout anyway). Do flash boot.img, that is the OS boot.
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
From there I now had the correct recovery in place to flash the 5.1 Optimized distro (which I would definitely recommend - clean, stable, excellent battery life!).
Yay!
Bmju said:
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
Click to expand...
Click to collapse
Why didn't you simply fastboot flash a TWRP image?
_that said:
Why didn't you simply fastboot flash a TWRP image?
Click to expand...
Click to collapse
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Bmju said:
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Click to expand...
Click to collapse
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
_that said:
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
Click to expand...
Click to collapse
Thanks! I definitely tried that first! Maybe this bit I didn't make clear in my post, but actually:
- fastboot boot was only working for me with older recovery ROMS, i.e. the older CWM recovery which I mentioned, which I had lying around from when I first rooted my phone on 4.4.4, and also - not that it's much use - with the recovery in the 4.4.4 image, which just brings up the dead Android logo
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Bmju said:
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
Click to expand...
Click to collapse
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Bmju said:
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
Click to expand...
Click to collapse
That doesn't make any sense. Not that I don't believe you, I just can't explain how fastboot could fail writing recovery but succeed in writing a different partition.
Bmju said:
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Click to expand...
Click to collapse
Thanks for sharing your experience though, maybe it will help someone who has the same weird issue.
_that said:
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Click to expand...
Click to collapse
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Bmju said:
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Click to expand...
Click to collapse
Yes, I've got that one too, but my flashed recovery then worked fine. However I upgraded my bootloader by installing the complete 5.1 stock ROM, maybe your bootloader update was somehow incomplete.
Hi,
Last month I've successfully switched my Oneplus One 16Gb to official Oxygen OS 2.1.4
Finaly I prefer the Cyanogen version and here I have a problem with the recovery tool.
I can't replace OxygenOS recovery at all and with it : not possible to install "super su" or cyanogen 12.1 rom.
With adb the installation of TWRP recovery or or cm12.1 recovery seems to work fine (transfer ok and no errors) but when I restart in recovery mode ((power + volume down) It's still OxygenOS Recovery in my phone.
Please help, I don't want to be stuck in this state :crying:
sylvainsjc said:
Hi,
Last month I've successfully switched my Oneplus One 16Gb to official Oxygen OS 2.1.4
Finaly I prefer the Cyanogen version and here I have a problem with the recovery tool.
I can't replace OxygenOS recovery at all and with it : not possible to install "super su" or cyanogen 12.1 rom.
With adb the installation of TWRP recovery or or cm12.1 recovery seems to work fine (transfer ok and no errors) but when I restart in recovery mode ((power + volume down) It's still OxygenOS Recovery in my phone.
Please help, I don't want to be stuck in this state :crying:
Click to expand...
Click to collapse
download the latest COS12.1.1 factory image to your pc, boot into fastboot mode and install the factory image via fastboot (flash aboot FIRST and do a "fastboot reboot bootloader" before you flash the rest ).
After that (or during, just replace recovery.img) you may install any custom recovery
Gesendet von meinem A0001 mit Tapatalk
Yes :good:
You brought me on the right track
I have successfully applied this method.
I nearly lost my phone because I had a power outage during the recovery but finally all is fine : I am back on COS 12.1.1 :victory:
A big thank-you
Revert from OxygenOS to Lineage - problem with recovery
Hi,
My phone OPO is currently running Oxygen Os
I am trying to switch to Lineage OS, however whenever the phone boots to the "Fast Boot" screen its just stuck at that.
Could someone please help me fix this?
[email protected] said:
Hi,
My phone OPO is currently running Oxygen Os
I am trying to switch to Lineage OS, however whenever the phone boots to the "Fast Boot" screen its just stuck at that.
Could someone please help me fix this?
Click to expand...
Click to collapse
Flash twrp with fastboot , then flash the lineage os :good:
Azhar_Fahry said:
Flash twrp with fastboot , then flash the lineage os :good:
Click to expand...
Click to collapse
Yes I am trying to flash TWRP
However, when I follow the below mentioned steps this is what i end up with :
List of devices attached
dc1c2a16 unauthorized
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>adb devices
List of devices attached
dc1c2a16 device
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>adb reboot bootloader
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot devices
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot oem unlock
< waiting for device >
And on the device screen it just reads "Fastboot mode"
So I kind of have the same problem but not exactly, I flashed the oxygen os and it worked perfectly but I wanted to change it to a nugget based rom and realized that I can not even boot into recovery. it gets stuck on the first oneplus logo that comes up and will not boot into the twrp. Any suggestions?
wait, so ur phone can't boot into the rom? or stuck at the fastboot mode everytime u try to turn on the phone ? I'm having that problem too, but I reinstall all the driver, and it worked.
Sent from my A0001 using Tapatalk
Azhar_Fahry said:
wait, so ur phone can't boot into the rom? or stuck at the fastboot mode everytime u try to turn on the phone ? I'm having that problem too, but I reinstall all the driver, and it worked.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
My device is just stuck at the Fast boot screen that shows a One Plus Logo under which "Fastboot Mode" is written after I try to boot into fast boot.
[email protected] said:
My device is just stuck at the Fast boot screen that shows a One Plus Logo under which "Fastboot Mode" is written after I try to boot into fast boot.
Click to expand...
Click to collapse
try to reinstall all the driver from this link ( https://goo.gl/MxKLjH ) and follow the instruction , i use that method and it worked
arashsh2002 said:
So I kind of have the same problem but not exactly, I flashed the oxygen os and it worked perfectly but I wanted to change it to a nugget based rom and realized that I can not even boot into recovery. it gets stuck on the first oneplus logo that comes up and will not boot into the twrp. Any suggestions?
Click to expand...
Click to collapse
Go to fastboot and flash latest twrp first. If you are rooted, you can do that also from running systen (flashify, twrp manager)
giaur said:
Go to fastboot and flash latest twrp first. If you are rooted, you can do that also from running systen (flashify, twrp manager)
Click to expand...
Click to collapse
Thank you for your response. I tried doing that but it gives me an error saying that there is already a twrp installed. I used Twrp Manager
giaur said:
Go to fastboot and flash latest twrp first. If you are rooted, you can do that also from running systen (flashify, twrp manager)
Click to expand...
Click to collapse
so I am still having the same issue, I got the latest twrp on there and still stuck, cant boot into recovery. everything I find online is about oneplus 2 and nothing about oneplus 1, can I use the same instructions for my oneplus1?
arashsh2002 said:
so I am still having the same issue, I got the latest twrp on there and still stuck, cant boot into recovery. everything I find online is about oneplus 2 and nothing about oneplus 1, can I use the same instructions for my oneplus1?
Click to expand...
Click to collapse
Yes, this is general procedure for any android phone. The only requirement is unlocked bootloader.
giaur said:
Yes, this is general procedure for any android phone. The only requirement is unlocked bootloader.
Click to expand...
Click to collapse
it is unlocked
So I've got a weird issue here, and after a sleepless night of Googling and using the MSM download tool, I still haven't figured this out. Basically, something got royally FUBARed while I was trying to flash LineageOS 16 to my OP6, and my phone got stuck in a point where not even TWRP would boot, and fastboot only brought up a black screen with a blue LED. After a bit of searching, I ended up using the MSM download tool to re-flash the stock ROM and recovery. I attempted to install TWRP after unlocking the bootloader, but every time I try to fastboot boot TWRP, it brings up that same black screen with blue LED, whether I use the official TWRP image or the blue_spark TWRP image.
TLDR; I got bricked, fastboot flashed back to stock, and now I can't boot TWRP to flash TWRP to my OP6. Anybody out there know what I should do?
Cheers,
Ph0enix_216 said:
So I've got a weird issue here, and after a sleepless night of Googling and using the MSM download tool, I still haven't figured this out. Basically, something got royally FUBARed while I was trying to flash LineageOS 16 to my OP6, and my phone got stuck in a point where not even TWRP would boot, and fastboot only brought up a black screen with a blue LED. After a bit of searching, I ended up using the MSM download tool to re-flash the stock ROM and recovery. I attempted to install TWRP after unlocking the bootloader, but every time I try to fastboot boot TWRP, it brings up that same black screen with blue LED, whether I use the official TWRP image or the blue_spark TWRP image.
TLDR; I got bricked, fastboot flashed back to stock, and now I can't boot TWRP to flash TWRP to my OP6. Anybody out there know what I should do?
Cheers,
Click to expand...
Click to collapse
With MSM tool your oneplus 6 is locked again...Maybe you should look if bootloader is locked!
Unlock BL
After its done you'll have to enable debug in developer options
Then fastboot boot twrp
Flash twrp
whizeguy said:
Unlock BL
After its done you'll have to enable debug in developer options
Then fastboot boot twrp
Flash twrp
Click to expand...
Click to collapse
My bootloader is unlocked. Still can't get into TWRP.
Ph0enix_216 said:
My bootloader is unlocked. Still can't get into TWRP.
Click to expand...
Click to collapse
Did you enable debug?
Sounds like you may have the active slot set to an unbootable OS. Check the active slot with fastboot getvar all, then use this to change to the other slot.
fastboot --set_active=[a or b depending on which is inactive]
Was this the end of this? I'm in the same boat. I was recovering from a google account remove device wipe and so I went to restore my TWRP back-up and it succeeds so I reboot. Device is bricked into fastboot mode only. So I msm restore and boot system, enable debugging, unlock bootloader, still can't get into TWRP or versions that worked before, just that taunting blue light.. I found this and changed my active slot but the issue is the same and I'm kind of at a dead end, any help would be appreciated. I can boot into 5.1.5 OOS and stock recovery fine.
Nevermind I had to incrementally update the ROM
angelsenvy said:
Nevermind I had to incrementally update the ROM
Click to expand...
Click to collapse
You can download both twrp zip & img from here: https://drive.google.com/drive/folders/1bnGBrkL5XE3yt7DmIRSDD2v4J6MzFOsH?usp=sharing
fastboot flash boot twrp-3.4.0-1-enchilada-Q-mauronofrio.img instead of fastboot boot .
That will work
Hi Guys,
I think I f...ed up big time...
My device was rooted and I tried to unroot/factory reset to give it to my wife. Since I'm now sitting here for about 5 hrs I try to summarize what I've been doing:
1. I started with trying to Flash a Factory Image with the ALL-IN-ONE Tool
- My Device was on the Latest Oxygen OS 11 and I just stupidly followed the instructions of the Tool and downloaded a OOS 10 based Stock Rom and flashed it (thats where my nightmare began)
- After I flashed the OOS 10 Stock Rom I was Stuck in at the Open Bootloader warning screen ("the boot loader is unlocked and software integrity cannot be guaranteed ...")
2. Since there is no (at least I couldn't find one for the life of me) OOS 11 fastboot stock ROM I tried to downgrade via an OOS Beta ROM I found in a downgrade guide
- That didn't work either and I ended up stuck at the same Screen
3. After some googling I came across this guide and tried to manually flash a none fastboot OOS 11 ROM by manually extracting all the images of the payload.bin
- After I extracted all the images I flashed them one by one as mentioned in the guide via fastboot and this ended up with
Qualcomm Crash Dump mode dm-verity device corrupted force dump Kernel restart
Click to expand...
Click to collapse
4. After that I panicked a little since I've never seen this error before and tried to Flash the OOS 10 based Stock rom via the ALL-IN-ONE Tool again
- This worked with no errors but now I'm still stuck in the "Open Bootloader warning Screen"
Since then I tried Step 4 with another OOS 11 none fastboot ROM but now I keep getting following error everytime I try to flash one of the extracted images via fastboot (which worked before):
FAILED (remote: Flashing is not allowed for Critical Partitions
Click to expand...
Click to collapse
I did some research, seems like this error indicates a locked bootloader which is wrong, bootloader is still unlocked.
Even if I try to unlock the bootloader again I get the reply that bootloader cannot be unlocked since it already is unlocked.
So now I'm stuck with a completely f...ed up device with absolutely no clue if and how I can fix this.
I really hope anyone of you guys can help ...
Apologies for the bad writing but it's 5 am and I'm tired and frustrated af ...
greetings from Germany.
Timo
EDIT: Oh and yes, I know about the MSM-Tool and tried it but I can't get it to work since my device is not showing. I followed this guide several time but nothing is happening and my device is not even showing in the device manager. Only time it shows in the device manager is when in fastboot mode.
Guys I finally did it.
I deinstalled all stale/inactive drivers and reinstalled the Qualcomm drivers and finally managed to get the MSM Tool up and running and revived the phone.
Solution: I hardbricked my device because of my dumbness. This device is not veux... It s viva. Be cautious my friends...
I unlocked my bootloader and wanted to install TWRP to flash a custom ROM to the device. Unfortunately, right after I tried, device got stuck in a bootloop (Mi logo showing, then closing.)
I tried flashing multiple TWRP files after that. Since there is no official file for this device, I tried the ones given in the forum and a youtube video.
Holding power+up does not open anything. Holding power+down I can go to fastboot. ADB does not see the device (adb devices does not show anything). But fastboot devices does show. (MiFlash tool also sees the device but can't flash the ROM.)
MiFlash first gives the classic crc error, I delete the lines, it passes this error and finally gives another error ("Command failed"). I tried flashing 2 versions (my local version and eu version) of the stock rom in both windows and ubuntu based linux. What am I doing wrong?
Am I doomed? What can be done? Why isn't ADB working? Thank you for replies
turbotales said:
I unlocked my bootloader and wanted to install TWRP to flash a custom ROM to the device. Unfortunately, right after I tried, device got stuck in a bootloop (Mi logo showing, then closing.)
I tried flashing multiple TWRP files after that. Since there is no official file for this device, I tried the ones given in the forum and a youtube video.
Holding power+up does not open anything. Holding power+down I can go to fastboot. ADB does not see the device (adb devices does not show anything). But fastboot devices does show. (MiFlash tool also sees the device but can't flash the ROM.)
MiFlash first gives the classic crc error, I delete the lines, it passes this error and finally gives another error ("Command failed"). I tried flashing 2 versions (my local version and eu version) of the stock rom in both windows and ubuntu based linux. What am I doing wrong?
Am I doomed? What can be done? Why isn't ADB working? Thank you for replies
Click to expand...
Click to collapse
ABD works only if you have enabled USB debugging.
Eventually check here that everything is correct:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Or try to install a Xiaomi Eu rom (Fastboot).
Extract the zip then run the scrip in the corresponding extracted folder to your O.S.
Fastboot_first install.
xiaomi.eu_multi_VEUX_V13.0.3.0.SKCCNXM_v13-12-fastboot.zip
https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/
NOSS8 said:
ABD works only if you have enabled USB debugging.
Eventually check here that everything is correct:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Or try to install a Xiaomi Eu rom (Fastboot).
Extract the zip then run the scrip in the corresponding extracted folder to your O.S.
Fastboot_first install.
xiaomi.eu_multi_VEUX_V13.0.3.0.SKCCNXM_v13-12-fastboot.zip
https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/
Click to expand...
Click to collapse
Hello, I do have my bootloader unlocked and USB debugger is also on.
I tried flashing twrp again, says it worked but does not boot into it. Goes back to boot loop
Then I tried flashing with MiFlash again. Same error
fastboot error remote: command failed
When I google it everyone says my bootloader should be locked. But it is not.
Can I use the hard brick solution with bypass for this problem?
turbotales said:
Hello, I do have my bootloader unlocked and USB debugger is also on.
I tried flashing twrp again, says it worked but does not boot into it. Goes back to boot loop
Then I tried flashing with MiFlash again. Same error
fastboot error remote: command failed
When I google it everyone says my bootloader should be locked. But it is not.
Can I use the hard brick solution with bypass for this problem?
Click to expand...
Click to collapse
All these procedures, Miflash, Twrp, Xiaomi Eu rom are done in Fastboot mode not ADB and obviously the bootloader must be unlocked.
Try the Xiaomi Eu rom.(TWRP included).
NOSS8 said:
All these procedures, Miflash, Twrp, Xiaomi Eu rom are done in Fastboot mode not ADB and obviously the bootloader must be unlocked.
Try the Xiaomi Eu rom.(TWRP included).
Click to expand...
Click to collapse
Tried doing this.. now it s hard bricked.
turbotales said:
Tried doing this.. now it s hard bricked.
Click to expand...
Click to collapse
You have flashed a Xiaomi Eu rom and it does not work?
And with Miflash?
NOSS8 said:
You have flashed a Xiaomi Eu rom and it does not work?
And with Miflash?
Click to expand...
Click to collapse
I tried flashing with Miflash didnt work,
Tried flashing with linux and said it is done, but now device does not open in any way. What should I do?
These are the screenshots of the Xiaomi Eu rom?
What is the version of your phone? (11 pro/Poco).
What rom were you on?
post the Miflash log.
NOSS8 said:
These are the screenshots of the Xiaomi Eu rom?
What is the version of your phone? (11 pro/Poco).
What rom were you on?
post the Miflash log.
Click to expand...
Click to collapse
Downloaded the rom from the link you sent me earlier. My device is veux and had MIUI13 before getting bricked.
Again the device got bricked from the last think i did. Do you know what wen wrong?
turbotales said:
Downloaded the rom from the link you sent me earlier. My device is veux and had MIUI13 before getting bricked.
Again the device got bricked from the last think i did. Do you know what wen wrong?
Click to expand...
Click to collapse
If you tried with Miflash post the log otherwise try and post the log.
Solved, I'm dumber than I thought. This phone is not veux. It's viva. If I were to re-check it I d not be in this position... Let this be a lesson to me. Going to have to take it to the service now.