Closed ferdydek closed 6 years ago
Could you try to manually delete the FT folder in the SDCARD... after you are in 139
Hi, although I am not the OP I have the same issue. After upgrading to 139 the hack is gone (no ssh, rtsp access) - even I remove the 'ft' dir in the SD. Could it be that the camera dials home somehow with 139 and blocks the initial hack/script to run?
The 139 changes the logic but the "tools" should managed that. In the logs you should see " miio_ota: Inject Success" as it is happening to the OP
I have created a new release (attached), please replace the one in the SDCARD and run the process again.
Send the folder log too next time. (attach everything to a zip instead of copy-paste the logs as a comment, I cannot read half of the lines)
OK. Starting the process will post once its complete. meantime, is this a typo in the language notification part of the script (I think its there since ever):
parent=`ls -al /mnt/data/sounce/booting`
/mnt/data/sounce/
or /mnt/data/sound/
?
when you go from the recovery firmware and run valhalla first time the sound folder changes to:
# ls /mnt/data/sound/
bin etc lib linuxrc mnt proc run sys usr
dev gm lib32 media opt root sbin tmp var
#
@ferdydek that was fixed in the latest release...
https://github.com/Filipowicz251/mijia-1080P-hacks/releases/tag/0.6b
it seems in the release page version is in the top, instead of b... when they were released in a different order...
Fixed release page. Version 0.6c is the latest.
To give full image of the upgrade process, the MiHome app shows progress only up to 69%, then rolls back to the "old version <> new version, update" screen, but the camera's orange led keeps flashing and the update will eventually complete (and camera will reboot with the click of night-vision switch).
6c_upgrade_logs.zip
After the upgrade the SSH and RTSP is no longer working. ft
folder is automatically deleted.
MiHome normally detects the camera and work OK (except date)
I've reset everything, went back to _099, hack works but now cant install the update. Should I change the DISABLED_OTA=1
for it to actually go through ?
s1.6c.zip
:) yep, set it to 0 to be able to upgrade.
issue in my case is that initial run of tool against version .099 removes the ft folder. recreating (creating backup ft folder and renaming it to ft via ssh) it before update solves the issue. closing issue.
@willthrom Will this be automated as part of the hack or needed to be done manually going forward?
it was already part of the version 0.7.
Get the latest 0.7.1 in any case.
Ah ok then it still is broke here then... Works on .099 but no longer available after firmware update
Could you upload the logs files and the log folder?
Yep here you go...
@AshPowell
It seems there were some error when trying to upgrade to the latest version. Oct 29 18:04:04 kernel: [ 360.390000] Node totlen on flash (0x0000000d) != totlen from node ref (0x00000034) Oct 29 18:04:04 kernel: [ 360.400000] Node totlen on flash (0x6fc2390c) != totlen from node ref (0x00000308) Oct 29 18:04:04 kernel: [ 360.420000] Node totlen on flash (0x00000004) != totlen from node ref (0x00000044)
From what version were you upgrading?
Can you try upgrade with RTSP off?
From the version in 0.3 release as per docs.
Will try with rtsp off and report back
No joy still same... upgrades fine but the hack isnt loading
mmm, that is weird.. if you check "https://github.com/Filipowicz251/mijia-1080P-hacks/issues/21#issuecomment-340279392" you can see someone having your same problem and after following the instructions they make it work.
Note. from the 0.3 release you only need the ft_recovery.bin file.. the rest has to come from the 0.7.1 release
Ah ok I just disabled rtsp I didn't adjust the other configs... Will try that tomorrow. Thanks!
Tried several times and I'm always failing to update to latest version after the hack.
Always ending up on the recovery image, then installing the hack. Have access through SSH. Then I'm trying to update the fw via MiHome app and always end up with latest version but the hack is gone.
last info before update starts:
then the application is downlaoded so camera is basically frozen, after few minutes even though the MiHome app does not indicate it, the upgrade is successful and device reboots:
from this point on there is no access to the SSH. Scenario is always the same.
any ideas?