Does anyone know where the ota updates are stored on this device? I will pull the updated boot.img and patch accordingly so the bootloader unlock is more simple if i can find the ota...OGs in the original hacking forum have fell silent on this, furthermore it seems that the epson file systems team only wants to utilize my input for their own development so I have stopped communications with the contact I had.
I can post a full nandroid backup on here if others would like to revert to software 4.0
You can flash this boot.img, check it out with image kitchen if you like. (boot it first and see if you can acomplish unlock with the boot command, then the rest of the unlock protocol. You may be able to boot to the image and follow the rest of my theory to acheive unlock without acually having to downgrade versions, if you follow my logic?) https://drive.google.com/file/d/1_2q...w?usp=drivesdk
Then unlock the bootloader
Next boot the prototype twrp and flash the update 4.0 zip
This is how I would proceed, given my experiencece with the device and android in general. If you have problems and can acheive flashing the prototype twrp I can share the nandroid backup that I used this morning to rescue myself from a boot loop.
Alternatively I believe you could derrive all relevant .img files from my backups/ I can capture more data if needed.
-- a closing note this boot.img I shared is the boot.img I had on my device when I originally unlocked the device for the first time on version 4.0
This should not cause you issues so long as you are working from fastboot for the unlock then boot the recovery then flash the 4.0 update zip. I doubt it will boot to system with the old boot.img but I am not adept enough to know what exactly to look for in order to know that so...It could boot despite my caution. Regardless it is best practice to carry out this operation without booting to system in my oppinion.
Thanks for your help and assistance. Unfortunately I seem to be falling over at the 1st hurdle so any suggestions most appreciated. I have the following settings in the android (v5.1.1) Settings / Developer options:
OEM Unlocking -> On
USB Debugging -> On
The output of 'fastboot getvar all' settings for the following variables are:
device-state -> verified
boot-state -> green
The output of 'fastboot oem unlock' (after quite a long wait) is:
ERROR: usb_read failed with status e00002ed
FAILED (Status read failed (No such file or directory))
Finished. Total time: 140.740s
The output of 'fastboot boot boot.img' is:
Downloading 'boot.img' OKAY [ 0.371s]
booting FAILED (remote: 'command not allowed in verified state')
Finished. Total time: 0.382s
So can download image but not install/execute its content!!!
Things I have tried:
Change of USB lead
Change of USB port
Change of computer
Change of Operating System (macOS and Windows)
Change of ADB/Fastboot version (about 3 different versions)
My understanding of the problem I have is that I need to get the device-state to unlocked and boot-state to orange and to do that I need to use the command 'fastboot oem unlock'. However, in my case because I have v1.5.0 of bootloader I need to run command 'fastboot boot boot.img' to enable the previously stated command to be run successfully. As you can see from my output the boot.img command is failing, hence preventing me from issuing the unlock command!!! That was why I mentioned that I was trying to roll back to v1.4.0 of the bootloader in the previous post. Its looking like I've hit a brick wall!!!
As mentioned previously, any suggestions would be most welcome.
interesting, okay it seems that we have eliminated the boot command as a possibility on this bootloader in the green state it was worth a try. I would now flash the boot.img I provided that's unlockable, unlock with that one and then revert to 4.0 with twrp img we have by flashing the 4.0 update zip and boot and recovery .img backups I have provided. The fastboot unlock failure issue is due to a change in the configuration of the fstab files.
I am looking for the directory the ota download link is sent. If I find that and patch the boot.img you all will no longer have to completely downgrade
In the boot.img in the link I have provided I disabled dm-verity and user data encryption so no one gets locked out of their file systems,
I also confirmed that the unlock boot loader code lines were present. One can check my work with img kitchen
I am sorry many are experiencing difficulty with the boot loader unlock. I would appreciate the help of the community in locating "where the ota update lives" so that I can capture it and provide a simply flashable v5.0 zip with unlockable boot loader. Until then I believe fastboot will obey the flash command (rather than boot) and that the downgrade through our prototype twrp is possible.
Well the problem of not being able to unlock the bootloader has gone away.... Gone and got my BT-300 into a boot loop... Damn!!!! Just boots the EPSON logo screen now repeatedly, so if anyone has the key presses to get it to bootloader/recovery on switch on would be very grateful.
For those wondering how I managed to screw it up..... I thought I would have a go at flashing the boot.img file in fastboot mode. Tried it 1st with v1.5.0 boot.img and that seemed to upload and install etc without any failures and it booted up as per a normal android screen. Thought I would try a stock boot.img v1.4.0 with no modifications. Didn't like that, although it seemed to upload and install ok but when I rebooted, just got the dreaded boot loop screen. I suspect the modified boot.img file provided by alecthenice was based on v1.4.0 so if anyone is thinking of giving it a go, I would advise proceeding with caution... or with a lot more knowledge than I have . I'll just have to keep trying different keypress combinations until I can get it booting into the other mode.
Oh and on the 'looking for the location of the OTA', I was originally thinking about looking around in the android partition but was wondering if the OTA file might get sent to the recovery partition (as in the partition booted when in recovery mode) as that is the partition that has booted up when I have manually tried to update an OTA update (installing from the sdcard or via sideloading).
Thanks to tarkus1000 I now have the v5.0 boot.img. I will patch this to make it boot loader unlockable and share the link shortly!! This will likely spare you the headache he is experiencing. The key combonations for fastboot mode are trickey, it took me weeks to discover them. I will post a youtube video to provide a visual reference in the form of youtube of how to boot into fastboot mode to hopfully aleviate frustration.
The patch and youtube video will come after my work day is completed.
|a/r, bt-300, epson, root|
|Thread Tools||Search this Thread|