I have a HTC One m8(Marshmallow 6.0) from Verizon. It's unlocked and I'm using it on the cricket network. I got S-off(sunshine) and put the latest TWRP on it. However ever root method(kingroot, kingoroot, etc) I try it's not working. Don't want to pay One Click Root $30 to root it. Any suggestions? Thanks
Download SuperSU from the app store and try the built in methods.
If neither work, you need the root installation zip and to flash it through TWRP>Install
I just rooted on a Verizon HTC One M8 with Marshmallow and was navigating to this forum to find a good rom and radio.
I got it done by downloading the supersu zip file and used TWRP to flash it. I wasn't rooted so I had to do it this way ... none of the apps will work if you aren't already rooted. Make sure you have downloaded the supersu .zip file and not the .adk file, otherwise it won't be available in supersu to flash.
I did that and now it's stuck on the verizon red screen. I tried factory resetting(fastboot). And that didn't work. The only way i seem to be able to get the phone to turn on is to let it die and charging it to like 2% and go into fastboot mode and if i reboot it.... it goes to the verizon red screen and just stays there.
Msmala85 said:
I did that and now it's stuck on the verizon red screen. I tried factory resetting(fastboot). And that didn't work. The only way i seem to be able to get the phone to turn on is to let it die and charging it to like 2% and go into fastboot mode and if i reboot it.... it goes to the verizon red screen and just stays there.
Click to expand...
Click to collapse
Try flashing current stable SuperSU 2.78 in zip version (flash with TWRP) from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Also, you need to be on a relatively recent TWRP version. Current is 3.0.2
https://dl.twrp.me/m8/
Also, no need to let the battery die, to restart to bootloader. Force a reboot by holding Power+Vol up for a minute or so. Once the screen goes dark to reboot, slide your finger from vol up, to vol down, to boot into bootloader.
Also, you should always do a TWRP backup before trying to root, so you can revert if something like this goes wrong.
Related
Just got my One X two days ago Decided not to root it, wanting to keep it vanilla. But really didn't want to re-enter all the settings for mail apps and wanted to preserve some save data of a few apps, so I decided to root it so i could use titanium backup to restore some apps with their save data. used htcdev to unlock the bootloader, which reset all the settings that i did already install (!!$#[email protected]$!). flashed cwm recovery and supersu. rebooted, the phone started reinstalling all the apps that were already installed automatically. got a notification about the 1.28 update, did that too. thought that while i was flashing anyway, i might as well remove the 3dots overlay crap with one of the hacks that could be flashed via cwm. bam. now the phone is stuck at boot. it shows the HTC logo, then shows it again with crackling sound and animated "quietly brilliant", then goes into the HTC One Beats logo screen and stays there.
i tried flashing the RUU (RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.26.401.2_Radio_1.1204.90.13_release_251208_signed.zip, i am on Vodafone NL) in windows, before and after relocking, restoring original recovery 1.26 and 1.28. But the only time that it did seem to work it borked at the end giving a "bootloader version error". oh, and i didn't mention yet that the download of the RUU took me more than 5 hours!!!! the filehosting service is slow as ****.
Next attempt. extracted the rom.zip from the RUU.exe and extracted the boot.img, system.img and recovery.img from that rom.zip file. Thought i'd flash it with fastboot. recovery.img flashed fine. Gave an error 00000006 when flashing system.img. (phone was in unlocked state (again)).
Tried flashing a custom rom and the extracted ruu rom.zip with "fastboot update rom.zip". doesn't work.
USB doesn't work in recovery and i haven't copied any rom update file onto the phone before everything went wrong. so i can't just reflash the rom from within recovery.
running out of ideas. can't post to the dev section. anyone know how i can get the phone back into a working state? i need it to work in 12 hours, i can't stick the microSIM in my old desire (thank you steve). i think maybe it's time to panic.... or bang my head against a wall.
any help in getting the phone working again is appreciated.
i have the same problem
and now i out of battery ....
i was about to try and flash the recovery and boot extracted from ruu-1.26 but it gave a low battery error. when holding the power button to turn off the stuck phone it will power up again immediately. so it seems it can't be turned off. if you keep volume down pressed while turning it off, and keeping it pressed when it turns itself on again you will enter the bootloader, where you can select "power off". if you use that to power off the device will stay off. mine is charging now in off mode, which seems to be working (unless that charging led light is actually a battery low light)
i thing is problem with recovery that , i hope to fix them
Issues being examined:
Cant mount USB in recovery
No charging while in recovery
Cant flash from Rom Manager
my story is exactly the same, my battery is also down. now i try to load while the phone stuck on htc-logo...
ok i find solutions
first download and flash the stock recovery
from here
Link to stock 1.26 recovery (Courtesy of TeamARHD)
http://www.androidrevolution.nl/ARHD/OneX/Recovery/endeavoru_recovery_signed.img
MD5: 4AF6F2B658D2E13F72E928A72FCDE9CD
Link to stock 1.28 recovery (Courtesy of Baadnewz)
http://mirror.rawempire.org/baadnewz/recovery.img
MD5: dfa1f95028b6ba22080368e7e490b616
after relock with this comend
fastboot oem lock
and after this download from there
the right ruu
http://www.xdafileserver.nl/index.php?dir=HTC/One+X/Stock+Rom/Endeavour
and install in boatload mod , is simple and the ruu is in in exe mod
if you are battery is under 30% from recovery press the power down
it works only with stock recovery
may work for others, but my phone was OTA updated to 1.28, so i can't use RUU to restore the phone, because there is no 1.28 RUU out yet for my phone (Vodafone NL), tried the Chinese one which didn't work (of course. but had to try anyways).
Can you Explain More
I HAVE PHONE IS SAME CONDITION BUT IT NOT I CANNOT ACCESS TO THE SD CARD. ITS SHOW ONLY STARTUP LOGO
hierophantis said:
first download and flash the stock recovery
from here
Link to stock 1.26 recovery (Courtesy of TeamARHD)
http://www.androidrevolution.nl/ARHD/OneX/Recovery/endeavoru_recovery_signed.img
MD5: 4AF6F2B658D2E13F72E928A72FCDE9CD
Link to stock 1.28 recovery (Courtesy of Baadnewz)
http://mirror.rawempire.org/baadnewz/recovery.img
MD5: dfa1f95028b6ba22080368e7e490b616
HOW TO FLASH THIS FILE TO PHONE WITCH SOFTWARE I HAVE TO USE.
after relock with this comend
fastboot oem lock
EXPLAIN MORE ABOUT THIS
and after this download from there
the right ruu
http://www.xdafileserver.nl/index.php?dir=HTC/One+X/Stock+Rom/Endeavour
and install in boatload mod , is simple and the ruu is in in exe mod
if you are battery is under 30% from recovery press the power down
it works only with stock recovery
Click to expand...
Click to collapse
PROBLEM SOLVED.
So at first I used Kingroot to rood my device, and it failed, but then i just realized few days later that Kingroot was installed and used root checker to check and said that it does have root access. After that decided to change the Kingroot to SuperSU by following this video https://www.youtube.com/watch?v=WevWdErXWy4 (It's the SuperSU Me app). I then updated SuperSU binaries and restarted the phone, and now its stuck at the loading screen. I tried hard resetting my phone but it would only show the screen with the android logo and shapes in its belly for about 2 second and go back to the stuck logo screen. Now I'm wondering if there's any fix for it, and if there's no fix then I'm going to try resetting it through this http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/ guide and I was wondering if I should download and use the bell stock factory firmware (I have a virgin mobile version).
Edit: fixed to be more clear.
I Nid 2P said:
So at first I used Kingroot to rood my device, and it failed, but then i just realized few days later that Kingroot was installed and used root checker to check and said that it does have root access. After that decided to change the Kingroot to SuperSU by following this video https://www.youtube.com/watch?v=WevWdErXWy4 (It's the SuperSU Me app). I then updated SuperSU binaries and restarted the phone, and now its stuck at the loading screen. I tried hard resetting my phone but it would only show the screen with the android logo and shapes in its belly for about 2 second and go back to the stuck logo screen. Now I'm wondering if there's any fix for it, and if there's no fix then I'm going to try resetting it through this http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/ guide and I was wondering if I should download and use the bell stock factory firmware (I have a virgin mobile version).
Edit: fixed to be more clear.
Click to expand...
Click to collapse
if you can get into recovery you can probably do it without unbricking. to you have stock recovery or twrp or what? If you have stock recovery then boot into recovery and just run it and itll hard reset your phone, if you have twrp or something just download the flashable rom of your choice (there are stock modded roms too if you like stock) put it on an sdcard and wipe and install that rom.
if you don't know how to get into recovery then make sure your phone is off (if ur not sure do a battery pull and put it back in). hold volume down and power button until the screen comes on. when it comes on let go of vol down and power and then push vol and power again and hold again until you see the writing)
btw if you do a stock recovery hard wipe then you will lose root.
I also faced this problem...
Sent from my SM-E500H using Tapatalk
Problem solved. I just flashed the stock firmware onto my phone and it fixed the stuck on logo problem.
So, i recently have tried flashing Xposed on the MM 6.0.1 on G920P a.k.a Sprint S6
( ALL_SPT_G920PVPU3CPB6_G920PSPT3CPB6_CL7280193_QB8664149_REV02_user_low_ship.tar )
I have root and recovery, but Xposed doesnt seem to comply with me.
from multiple sources or builds.
And each Xposed file that i've tried so far that i've been flashing over and over again, rinse and repeat.
( Flash Stock through Odin, Go through setup process on the phone, Reboot Back to Download mode to Flash TWRP, Reboot, Back to TWRP to Flash Xposed, Once flashed i Restart it again, back to the s6 screen to becoming a black screen bootloop, thus having me restart the whole flashing process again )
from android file host website. And Default xda unofficialy build on this website.
xposed-v79-sdk23-arm64-by-romracer-20151218
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - ABDYASAR 7.8MB
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - SANOC 7.8mb
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 -WANAM 7.8MB
xposed-v80-sdk23-arm64-by-romracer-20160202
It would go from the Galaxy S6 Boot Menu startup to black screen and bootloop back to the original BootMenu or screen.
NO LED cycles nothing, but i can access Download Mode and Recovery But Updating Nor Uninstalling doesn't do anything to the rom, it just keeps boot looping unless i Flash the Stock back into place.
I'd like to have Xposed working i havent found a version for me that would work for this but i would really appreciate if everyone could help out.
IAmTechFreq said:
So, i recently have tried flashing Xposed on the MM 6.0.1 on G920P a.k.a Sprint S6
( ALL_SPT_G920PVPU3CPB6_G920PSPT3CPB6_CL7280193_QB8664149_REV02_user_low_ship.tar )
I have root and recovery, but Xposed doesnt seem to comply with me.
from multiple sources or builds.
And each Xposed file that i've tried so far that i've been flashing over and over again, rinse and repeat.
( Flash Stock through Odin, Go through setup process on the phone, Reboot Back to Download mode to Flash TWRP, Reboot, Back to TWRP to Flash Xposed, Once flashed i Restart it again, back to the s6 screen to becoming a black screen bootloop, thus having me restart the whole flashing process again )
from android file host website. And Default xda unofficialy build on this website.
xposed-v79-sdk23-arm64-by-romracer-20151218
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - ABDYASAR 7.8MB
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - SANOC 7.8mb
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 -WANAM 7.8MB
xposed-v80-sdk23-arm64-by-romracer-20160202
It would go from the Galaxy S6 Boot Menu startup to black screen and bootloop back to the original BootMenu or screen.
NO LED cycles nothing, but i can access Download Mode and Recovery But Updating Nor Uninstalling doesn't do anything to the rom, it just keeps boot looping unless i Flash the Stock back into place.
I'd like to have Xposed working i havent found a version for me that would work for this but i would really appreciate if everyone could help out.
Click to expand...
Click to collapse
Did it work. Ive only noticed a tad bit longer boot up the 1st time but all good.
i've tried most of them and i tried v80.0 or v80 and i got one part success half i didnt which was from it i got to the LTE spectrum screen and it just would go past that before it would just be the led flashing and bglank screen, i waited about and hour and still nothin changed from that screen.
Nevermind i made an update
This is what i've managed so far.... what am i missing here?
So here's what i"d take place in order to attempt a flash of Xposed Framework.
I start with Pre- Downloading the files for the MM 6.0.1 Stock Rom, it's in the forums Somewhere.
TWRP ( New_S6_Spr_TWRP_MM_Bootloader2 ) a.k.a 3.0.1
(This is a special version only for the Sprint SM-G920P and is meant to be flashed with Odin)
SuperSU 2.68 a.k.a ( BETA-SuperSU-v2.68-20160228150503 )
and obviously, Odin ( Odin3 v3.10 )
The steps that are taken place.
1st. I'd Boot my device into download/odin mode.
or
( while the device is powered off, i press and hold the home+power+volume down buttons.
and from there I'd be taken to a light blueish screen saying "Warning", and i follow through by pressing volume up)
2nd.
Once the device is in download/odin mode, and ready to go, i'd take my phone, plug it into my windows PC and open Odinv3 and from there
i'd select in odin, or i'd click the "AP" button and select the, tar file.
After that has been flashed thoroughly, I'd then proceed with the follow on screens, the 1st reboot and it updates or it says
Optimizing app 1 to 30.... the 2nd reboot where the hand free activation commences and
from that 3rd time it reboots and boots up again, i'd follow up with my login information.
3rd. once my device has been fully booted from the 2nd part, i'd then shut it down or restart it into "download mode again" and connect it to my pc again
and from there i'd load odin, and search or i'd find where I downloaded the special "TWRP .tar" or recovery file
and select the "Ap" option again and press start Afterwards.
After it flashes, right when its done i automatically hold the home+power+volume up buttons,
turn the device off and hold home+power+volume up and your should get some red text in the upper left hand corner with recovery not enforcing, that's okay dont be worried,
and from there it should boot into and be brought into TWRP...finally lol.
Now that's where you can flash SuperSU
4th. I'd leave my phone connected to my pc until, it's fully booting into twrp or i'd just connect it once im in the recovery.
I let my pc detect my phone and i'd copy both of these files.
SuperSU 2.68
and
Xposed
4th. After its copied, i'd go back into my phone, i tap install, and i select supersu and let it run, afterwards, i press reboot.
And let it sit for about another 2 minutes to do its own thing. Afterwards. once the phone is fully booted up.
I'd then go back into recovery, and flash Xposed and i'd wait about another 2-3 minutes for it to cycle
from the LTE Spectrum Screen to the, torquise colored screen where it's finally optimizing apps from 0 to 331.
5th. Once done, i'd finally have my advantage to install what i'd like which i'm doing as of right now still testing it out.
P.S if you do what i do for the SnapPrefs Module then i'd take in high note that before you flash the Xposed to download latest Snapchat 9.26
log in, once logged in then proceed with the rest and download XInstaller to downgrade from 9.26 to 9.17.1.0 to take full advantage of Snapprefs coolness.
upon note so far, after installing the modules, i rebooted my phone and it boots until it hits the LTE Spectrum screen and it has a light blueish pusling cycle and im stuck here.
maybe i can try another version. to be continued...
If you need any help feel free, i will try as best as i can, as i am a n00b but i have plenty of free time and have some decent knowledge about this.
After , i went back into recovery, i went to uninstall xposed thru the other flash file and its says optimizing 0 to 36 items and it booted so far, mayber after i flash the cache again and reinstall i should be fine but until further notice...tbc
Alright after a good amount of time i;ve finally concluded that the versions i;ve tired from xposed were the ones from the OFFICIAL thread and id always bootloop with that puling blue led and black screen, BUT with Wanams Xposed Version 80, and 79 they worked EXCEPT i can only get to the LTE SPecturm white boot screen and it does nothing from there BUT when i flash 80.1 it completely pulls through with the boot and completes but i had forgotten to mention that for some people on aanother thread that Xinstaller may leave you with bootloops and as it did for me thats exactly what happened. But i m still confused as to why the officials dont work by wanams does even after wiping cache,and dalvik cache multiple times and uninstall and reinstalling xposed.
Does yours still bootloop or did it finally pull through?
Hi XDA-Fellows
1) thanks for all the help of this community so far
2) my problem: I had my HTC One M8 rooted, installed TWRP (I think in the end I had 2.7.8.0 as last version) and Cyanogenmod with a nightly build of around 18. March 2016 installed! THEN the big mistake happened. In advanced developers menu of cyanogenmod I activated the option that was called something like "on update of system also replace recovery software". That obviously was stupid.
Upon rebooting normally TWRP launched and installed the latest nightly. This time I see the white screen with HTC logo on it, red text in bottom, top part of the screen shows "ENTERING RECOVERY", 3 seconds later I see a black screen and every like 2 or 3 seconds it looks like the screen gets powered, it flashes darkgrey shortly (again, looks like it gets powered but instantly shuts off immediately).
This just can be stopped by pressing either P+U or P+D for like 10 seconds. Then again, white screen with HTC logo and ENTERING RECOVERY and the screen switch on/off-loop.
Is my device bricked? What can I do now?
Any help is appreciated.
Hi,
Can you enter to your bootloader ? So maybe you can just reflash it to see if it's going to work..
BelDev said:
Hi,
Can you enter to your bootloader ? So maybe you can just reflash it to see if it's going to work..
Click to expand...
Click to collapse
Yes I can enter bootloader. How should I go on from here on?
Well you just need to download the new TWRP from their web site https://dl.twrp.me/m8/ after that you put your device into bootloader and you plug your phone into your computer and download a toolkit from xda like htc one m8 toolkit and you follow the instructions..
BelDev said:
Well you just need to download the new TWRP from their web site https://dl.twrp.me/m8/ after that you put your device into bootloader and you plug your phone into your computer and download a toolkit from xda like htc one m8 toolkit and you follow the instructions..
Click to expand...
Click to collapse
Thanks. I will give it a try and give feedback.
It worked. I could enter bootloader, switched to FASTBOOT mode, installed ADB Drivers for windows and replaced recovery with latest TWRP! THanks a lot for your help! I thought I could throw away my M8
Well. It worked not completely. I was able to reboot my phone into the Cyanogenmod. But upon entering recovery mode (which I expected now to be TWRP) I get the same result again ... Screen off/on within seconds, repeating endlessly
I think you need to reflash the boot.img and the ROM completely. Because i don't know why do you have a black screen.
I activated root access for apps and tried ROM Manager first! It failed, then I used flashify which worked. Automatically downloaded latest TWRP (3.0.0.1) and flashed it, reboot into recovery. Everything works like a charm again! Thanks again for your help!
Hey all,
So I updated my pixel xl to Android O, and then used the modified TWRP to flash Super Su, SUhide. The phone booted up and everything was perfect. It was a little sluggish so I decided to do a full factory reset... again, phone reset, booted perfectly. I then restored all my apps from the google play store cloud... phone was functioning fine.
I went to reboot the phone after a while... and now the phone is stuck on the G logo after the bouncing dots... and just continues to load.
It's been like that for over 20 minutes.
Is this normal? Anyway I can fix this?
Thanks!
8.0.0 rooting nightmare
gaw54 said:
Hey all,
So I updated my pixel xl to Android O, and then used the modified TWRP to flash Super Su, SUhide. The phone booted up and everything was perfect. It was a little sluggish so I decided to do a full factory reset... again, phone reset, booted perfectly. I then restored all my apps from the google play store cloud... phone was functioning fine.
I went to reboot the phone after a while... and now the phone is stuck on the G logo after the bouncing dots... and just continues to load.
It's been like that for over 20 minutes.
Is this normal? Anyway I can fix this?
Thanks!
Click to expand...
Click to collapse
I have the same exact issue after following the exact process described above. After a weekend of frustration, I was thrilled to see this post, but then bummed there are no suggestions. There is no way I can get it back to recovery, no matter what power/volume combination I try. The phone is not detectable by ADB either, so unless a kind soul has a suggestion, there seems to be nothing to do except let the battery die and hope.
Umm boot into bootloader and flash stock boot.img and system.img?
george241312 said:
Umm boot into bootloader and flash stock boot.img and system.img?
Click to expand...
Click to collapse
I would love to do that, but how is it possible if there is no power or volume button combination that can get me off of the Google boot screen and into bootloader?
Have you tried Power + volume down ? It'll turn off after release power button only. That or let the battery die and when you try to plug it up next time leave vol down pressed.
george241312 said:
Have you tried Power + volume down ? It'll turn off after release power button only. That or let the battery die and when you try to plug it up next time leave vol down pressed.
Click to expand...
Click to collapse
I have tried that, thank you. I will let battery die and do the Volume Down method you suggest, and report back.
edjanx said:
I have tried that, thank you. I will let battery die and do the Volume Down method you suggest, and report back.
Click to expand...
Click to collapse
That did the trick. Back to stock 8.0.0, and hoping to find a stable root method that doesn't hang-up on the first reboot. Thanks for the help!
First of all. Hold the power button for about 20 secs and the phone will reboot.
Hold vol - and you are straight to bootloader.
Second flash full factory to both slots.
And third stop using the - w solution when you are coming from another rom or a different stock version. We had this problems on other forums and it was every time - w or not flashing both slots. I know for many people there will be no problem but some apps are just misbehaving when you do so. And they are causing reboots and bootloops.
mikaole said:
First of all. Hold the power button for about 20 secs and the phone will reboot.
Hold vol - and you are straight to bootloader.
Second flash full factory to both slots.
And third stop using the - w solution when you are coming from another rom or a different stock version. We had this problems on other forums and it was every time - w or not flashing both slots. I know for many people there will be no problem but some apps are just misbehaving when you do so. And they are causing reboots and bootloops.
Click to expand...
Click to collapse
OK, thank you! I am not familiar with the -w method. This is a new Pixel XL I received from Google to replace a nexus 6p with a bootloader issue. I made the mistake of not attempting this before it updated from 7.1.2 to 8.0.0, or it may have been a different story.
So I have the the phone restored to 8.0.0 and was going to attempt root. But I didn't realize there are two slots to flash. I simply ran flash-all.bat and the phone came back up. So I guess I'd have to move the Sept security stock image over to the phone along with the SU, SU Config (which may not be needed if on 8.0.0?), and Su Hide. Then I boot up TWRP 3.1.1 and flash stock image to both slots, reboot, then get back into TWRP and run the SU, then SU Hide on *both* slots?
Thanks!
Janx
Run flashall.bat on the slot you are now in. Reboot to system
Back to bootloader. Switch slots through fastboot
fastboot --set-active=_b
fasboot reboot bootloader
Now you should be on the other slot
Flashall.bat
Reboot to system
Back to bootloader
fastboot boot twrp.img (latest)
In twrp put latest su or in my case magisk 14.2, twrp zip on device.
If you use su just flash it
If you use magisk. Flash magisk, flash twrp.zip and magisk again. With magisk twrp will stick.
Reboot and you are good to go.
If you want a kernel you have to flash twrp and magisk after again.
mikaole said:
Run flashall.bat on the slot you are now in. Reboot to system
Back to bootloader. Switch slots through fastboot
<SNIP>
If you want a kernel you have to flash twrp and magisk after again.
Click to expand...
Click to collapse
Thank you! I will be able to perform this sequence in a few hours and will report back. :good:
Ok. Will be in bed than. If you have any problems give me a PM and we can do it together via hangouts.
Update: I successfully flashed A & B, got to the step where I flash Magisk 14.2. It finished unmounting partitions, but when updating partition details fails, "failed to mount '/system' (device or resource busy)...done
It said successfully installed, so I flashed twrp to the boot image, flashed magisk again, and it is now rebooting endlessly. Wrong place to flash the twrp image I'm guessing?
EDIT: Just noticed your message, good night - thanks again. I'm working through it and will take you up on your kind offer should I not find success.
I did a 'flash-all.sh' on both A and B again, copying over my old phone, then will attempt to gain root by booting into TWRP 3.1.1, installing "SR3-SuperSU-v2.82-SR3-20170813133244", reboot bootloader, go into TWRP again and then install "UPDATE-suhide-v1.08-20170815171034"
EDIT #2: EDIT #2: Stable root achieved using newer versions of files "SR5-SuperSU-v2.82-SR5-20171001224502" & after booting, applying "UPDATE-suhide-v1.09-20171001222116". So far it has survived several reboots, so I'm hoping it's all good now.