Database Info

[Q] HELP - NVFlash Bootloader failed

I'm on ICS and never upgraded to JB. I've just unlocked my bootloader so I can do NVFlash Backup and start flashing ROM's.
I unlocked without any problems. I've rebooted into bootloader and selected the USB icon. My computer found the drivers and correctly identified as 'ASUS Android Bootloader Interface'.
From the guide http://androidroot.mobi/pages/tegra3-guide-nvflash/
I ran the command
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
I got the following output from my Windows console
Code:
sending 'staging' (1002KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 7.935s
On my tablet appears
Code:
Failed to process command download:000fa98d error(0x120003)
Also the device now appears in my windows device manager with the following error
Code:
This device cannot start. (Code 10)
{Operation Failed}
The requested operation was unsuccessful.
I've not rebooted my tablet for fear of this question...
Have I bricked my tablet?
P.S. At this point I haven't attempted to reboot my device because I'm worried it might never come back.

So I've been crawling around the internet for anyone else who's had this problem and the only person with a similar issue is
http://forum.xda-developers.com/showpost.php?p=32222050&postcount=110
So since my OP, I've removed the USB cable from my laptop, plugged it back in and I can see my TF300.
When I run
Code:
fastboot devices
I get
Code:
00000 fastboot
Which I assume means my computer can see it?
At the moment I've still not rebooted. From what I've read Staging partition is applied at boot, which I assume means no changes have been made yet?
Because my transfer failed, will anything be applied from Staging on next reboot? Or should I run a command now to prevent any changes?
Thanks

Any help on this will be much appreciated.
Just to clarify, I've still not rebooted my device since I attempted the flash and seem to have access to Fastboot. I don't want to reboot unless I know it's safe to do so.
Thanks!

I thought this morning I'd try and change my drivers and run the command again.
I thought first I'd use Universal Naked Drivers, when I select the INF 'android_winusb.inf' file I get two options both called 'Asus Fastboot Interface'.
If I select either of these I get the following error
The hash for the file is not present in the specified catalogue file. The file is probably corrupt or has been tempered with.
The other option I do seem to have is under manufacturer 'Google, Inc.' I've got 'Android Bootloader Interface'. Is that any better?

So I eventually got the Universal Naked Drivers to work (after disabling Driver signature enforce from Windows boot options) and I could see my device in device manager and from 'fastboot devices'.
So I re-ran
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
And this time it also failed with another message. In my console showed
Code:
sending 'staging' (1002 KB)...
FAILED (remote: (AccessDenied))
finished. total time: 0.014s
And my TF300 displayed the line
Code:
Failed to process command download:000fa98d error(0x30010)
But this time, I can no longer see my device from device manager or 'bootloader devices'. Windows doesn't even make the 'device inserted' sound when I plug it in.

So I finally gave in and rebooted my tablet.
To my great relief it booted successfully!
I was so nervous about doing this before hand and this experience has really knocked my confidence down.
What I'd like to know is: Is it down to the driver I'm using that I'm getting my original error? Is it a problem with my PC or my tablet?
Thanks

psjw12 said:
So I finally gave in and rebooted my tablet.
To my great relief it booted successfully!
I was so nervous about doing this before hand and this experience has really knocked my confidence down.
What I'd like to know is: Is it down to the driver I'm using that I'm getting my original error? Is it a problem with my PC or my tablet?
Thanks
Click to expand...
Click to collapse
I've seen posts where problems similar to this have been solved by just using a different USB port, one at the back if you're using a PC. At least it might be worth a try.

daws said:
I've seen posts where problems similar to this have been solved by just using a different USB port, one at the back if you're using a PC. At least it might be worth a try.
Click to expand...
Click to collapse
I'll give that a try. I'm also gonna try updating my Android toolkit and using the Android Fastboot drivers (rather than the ASUS ones).
I'll let you know how I get on with that.

psjw12 said:
I'll give that a try. I'm also gonna try updating my Android toolkit and using the Android Fastboot drivers (rather than the ASUS ones).
I'll let you know how I get on with that.
Click to expand...
Click to collapse
Did you have luck with your device? The thing is i have a similiar problem with my device. The only difference might be that my mainboard has been exchanged during an RMA. But apart from that I also have a unlocked ics bootloader and when tried:
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
everything seemed to be ok, because i got the following message:
Code:
sending 'staging' (1002 KB)...
OKAY [ 0.257s]
writing 'staging'...
OKAY [ 0.293s]
finished. total time: 0.550s
However if I check for devices afterwards, using:
Code:
fastboot devices
I get the following wierd message:
Code:
???????????? fastboot
Luckily when I restart the device it is like nothing happend. It still says "The device is unlocked" on the top left corner of the screen and the fastboot commands work as usual. I really appreciate your help.
Jan

Claudii said:
Did you have luck with your device? The thing is i have a similiar problem with my device. The only difference might be that my mainboard has been exchanged during an RMA. But apart from that I also have a unlocked ics bootloader and when tried:
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
everything seemed to be ok, because i got the following message:
Code:
sending 'staging' (1002 KB)...
OKAY [ 0.257s]
writing 'staging'...
OKAY [ 0.293s]
finished. total time: 0.550s
However if I check for devices afterwards, using:
Code:
fastboot devices
I get the following wierd message:
Code:
???????????? fastboot
Luckily when I restart the device it is like nothing happend. It still says "The device is unlocked" on the top left corner of the screen and the fastboot commands work as usual. I really appreciate your help.
Jan
Click to expand...
Click to collapse
That's odd, it's like Fastboot says image was deployed but then it doesn't apply the change. Thank goodness there's a staging partition on Asus! I also had the problem of the device disconnecting whilst trying to flash and then not showing up.
How does the tablet show up in your device manager? As 'Asus Fastboot' or 'Android Fastboot'? Mine was ASUS and I was thinking of trying the Android driver instead.
I've not tried to flash mine again since trying, I'm going to wait for an appropriate time for me to have a heart attack if it all goes wrong
Edit: The next command it wants to issue is
Code:
fastboot -i 0x0b05 reboot
I wonder if that what makes it commit the changes? Hopefully someone can answer that for me.

Unlocking Bootloader: "command write failed" after most fastboot commands.

So 10 hours ago I decided I wanted to root my phone to install some apps and maybe even a cool ROM.
I read that the first step is to unlock the bootloader. I have trying my hardest to do this first step for 10 hours.
I've read 4-5 different tutorials twice on xda.
My phone is:
HTC One A9(hiae), bought in Sweden
hTc download mode
*** LOCKED ***
htc_hiaeuhl PVT S-ON
LK-1.0.0.000
[email protected]
OpenDSP-7.8.2.00197-8952_1228
OS-1.56.401.70
Jan 22 2016....
I have tried the normal way through htcdev.com even had the Unlock_code.bin at one point. But I had to reinstall all drivers twice to get it.
I have tried using the WinDroid Toolkit, no better than the manual way.
I got my hard earned token ID through both ways.
I find that every time I want to use fasstboot to send over a file i.e. "fastboot flash recovery twrp.img" hTc download mode is stuck at Start download, like I need to confirm it but can't because the command failed. The same goes for the Unlock_code.bin, can't send it over.
Code:
C:\adb>fastboot devices
HT5AVBE04449 fastboot
C:\adb>fastboot flash unlocktoken Unlock_code.bin
target didn't report max-download-size
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.003s
I can get past this next problem temporarily by reinstalling all drivers, tedious.
Code:
C:\adb>fastboot oem get_identifier_token
...
FAILED (command write failed (Unknown error))
finished. total time: 5.002s
Possible problems:
hTc download mode: I need to accept the download before fastboot give up, instant.
Win10: Bad OS for this?
USB connectors: Not enough power? Some other USB devices don't work here normally.
HTC Sync Manager: I've not bother installing the software.

Solution
I've made it;
I'm not sure if I was in the real download mode at the time, but that might have been it.
Also this time I redid everything, deleted all the drivers correctly and installed via Universal Naked Drivers

Hello,
Did you check OEM unlocking to allow the bootloader to be unlocked in Settings/Developper options (hidden by default, appears when you tap Build number 10x in Setting/About/ Software information/More/ Build number) ?

ouioui01 said:
Hello,
Did you check OEM unlocking to allow the bootloader to be unlocked in Settings/Developper options (hidden by default, appears when you tap Build number 10x in Setting/About/ Software information/More/ Build number) ?
Click to expand...
Click to collapse
For my phone it is 8 taps and yes. Every time I start a new Android I do a OEM unlock.
But I might be correct to change USB connector.

Fastboot Mode Not Working in Windows 10

I cannot get fastboot mode to work under Windows 10. I see lots of posts regarding this issue but none of the suggestions have worked for me.
I am seeing my OPO with adb and can maipulate it and reboot it:
Code:
C:\adb>adb devices
List of devices attached
15b00da9 device
But when I reboot into fastboot, "fastboot devices" gives me nothing. The phone shows fastboot mode.
Some things I have tried:
Currently using Samsung drivers
Have manually switched USB driver in device manager to Samsung ADB
Have tried 15-second usb drivers and UniversalADBDriverSetup. Neither help. Same problem.
Have followed several suggestions on installing Google USB drivers. They don't seem to show up when manually switching USB drivers. Only the Samsung ADB drivers show up.
Currently have driver signing turned off.
Does anyone have any other suggestions?

Have you tired installing the drivers while in "Test mode" ? I currently have Windows 10 insider build 14965 and I have no issue, both adb and fastboot work.
I always use this installer on all PCs I need fastboot/adb. https://drive.google.com/file/d/0B9fZIF6vzIBzT2ZtZkNSVFI5ZHc/view?usp=drivesdk
It's an all-in-one pack of the drivers and fastboot+adb. Never had problems with it and always worked for me, it gets installed in system so you can run them from any CMD

Yup I tried adb-setup.1.4.3 with driver signing disabled. I tried uninstalling what I could find and then reinstalling.
The Google drivers are confusing. Selecting update driver and then navigating to the driver location yields "No drivers for your device could be found."

Just tried it again. These are the 15-second drivers I mentioned. I say yes to "install drivers". But attempting to change USB driver either gives the error mentioned in my last post. Or if I try to choose from drivers already installed, all I see are the Samsung drivers. I cannot see Google USB drivers.

This is kinda the summary of what I've tried:
http://android.stackexchange.com/questions/118823/how-to-install-adb-drivers-on-windows-10-opo
But I can't get the Google drivers to install. Again, Windows says no software found for your hardware.

Seems more of a Windows problem at this point, I usually install that, plug the phone and that's it, never had problems (on multiple computers and OS) I can only suggest you to refresh windows installation, either from the settings "Update and recovery" (you can chose between keeping data or full wipe) or from the CD if you have it.

Okay that was weird. I tried completely removing the Samsung drivers through Add/Remove Software then I reinstalled the 15-second drivers and rebooted. I happened to leave my phone in fastboot mode. When I went into device manager I saw "Kedacom USB Device | Android Bootloader Interface" but fastboot still gave nothing.
I manually changed that driver to "Marshall London Bootloader Interface" and viola:
Code:
C:\adb>fastboot devices
15b00da9 fastboot
Now adb isn't working but I'll try manually changing that driver too.

So ADB has now stopped working. Still manually selecting the Google drivers folder yields no software for your hardware. I will now try re-adding the Samsung drivers and see if the fastboot interface remains intact.

Before I get to the Samsung driver, with the phone in normal booting and PTP mode I now see that same Kedacom USB Device with three models listed:
#recovery
Android Bootloader Interface
Kedacom KDB Interface
None of them work with ADB.

[SOLVED] Fastboot Mode
I think I figured it out. All the help postings talk about manually selecting the driver. What I found out was that I had to do this *twice*: once for regular ADB mode and once for Fastboot mode. I set the ADB mode to the Samsung ADB drivers. To change the Fastboot driver I needed to boot the phone into Fastboot. I could then change that driver to the Marshall London Bootloader Interface.
I was then able to unlock the bootloader (remember to set the OEM Unlock option under Developer Options) and then install TWRP.
What a pain.
Edit: TWRP *said* it installed but I still have the OnePlus recovery software.

kbocek said:
Edit: TWRP *said* it installed but I still have the OnePlus recovery software.
Click to expand...
Click to collapse
https://dl.twrp.me/bacon/
You got the last image from here?
Code:
fastboot oem unlock
Then
Code:
fastboot flash recovery twrp-xxxxx.img

Yes, it's unlocked.
Code:
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ -0.000s]
finished. total time: -0.000s
Full disclosure time. I'm actually doing this on a OnePlus X. I was also testing with a OPO and so started posting here.
Two things I think were important. 1. I didn't rename the recovery file to recovery.img. Second, I didn't issue the fastboot boot command. However:
Code:
C:\adb>fastboot flash recovery twrp-3.0.2-0-onyx-OnePlusX.img
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.469s]
writing 'recovery'...
OKAY [ 0.281s]
finished. total time: 0.750s
I also tried renaming the file to recovery.img. TWRP still doesn't show up. So I tried the boot command after installing:
Code:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.469s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.516s
I've tried several versions of TWRP, 3.0.2.0, 2.8.7.0 and some other ones supposedly for the OnePlus X. The fastboot boot command does not reboot the phone. Still can't figure out the "dtb not found" message.

This thread describes my problem exactly. It mentions a custom bootloader that's supposed to work from eng.stk. Trying to find it.
http://forum.xda-developers.com/oneplus-x/help/users-twrp-t3258756

Finally. I installed the custom bootloader from here:
http://forum.xda-developers.com/devdb/project/dl/?id=20236
Bluespark V41. *Now* the bootloader is replaced and works. So, yes, there is a problem with the standard Onyx TWRP images.
Edit:
I misspoke. It's the *recovery* image that is being replaced.

thanks
thank u so much...now its working

Razer bootloader unlock

Hi,
I'v got used Razer phone today with Oreo 8.1, tried to unlock boot but it failed. Commands I've ran so far (debug and oem unlock both on)
adb reboot bootloader
got the download mode
android bootloader interface version 11 driver from google.
fastboot -i 0x1532 devices
xxx40xxxx fastboot (xx are numbers)
then
fastboot -i 0x1532 flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.004s
on the phone download mode words disappeared and no driver appear in the PC
also tried another root method with posted here in XDA for Oreo but still not working.
Please I need help as I bought the phone to root and enjoy it
Majed

NeverMind, used another laptop and i was able to do it... I think AMD has some usb filters or something

Android - Corrupted system after security update

After installing a security update, my device won’t boot. Is there a way out of this without losing my data?
In more details:
My device is a Moto e7 XT2095-2 with Android 10.
Today I got a notification for the latest security update. I downloaded it. My phone tried to restart but failed, and looped several times.
In the end it displayed a black screen with a barcode and “fastboot mode ...”.
After trying to reboot again, now I’m getting this message:
Android Recovery
motorola/malta_reteu/malta
10/QOFS30.569-36-31/095c7
user/release-keys
Use volume up/down and power
Can’t load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
If I select “Try again”, I’m getting an “Error!” screen then the device reboots (tries to, I mean).
The device is not rooted. I haven’t unlocked the bootloader, installed a custom ROM, or a custom recovery.
Developer options are enabled – that’s the only difference from the average person’s smartphone.
I have no backup of my data.
I know very little about Android, but as a developer I’m comfortable enough learning about it.
I searched online what I could do, and tried to ADB sideload the stock OTA as described here:
https://www.droidwin.com/fix-cant-load-android-system-your-data-may-be-corrupt-without-reset/
with the 2 latest files from here https://mirrors.lolinet.com/firmware/moto/malta/official/RETEU/
On my laptop terminal, I got this:
serving: 'update.zip' (~0%) adb: failed to read command: Undefined error: 0
And on the device:
Finding update package…
Opening update package…
Verifying update package…
E:footer is wrong
Update package verification took 0.2s (result 1)
E:Signature verification failed
E:error: 21
Install from ADB completed with status 2.
Installation aborted.
I’m a bit confused from reading a lot of contradictory information. Is this method supposed to work or is it failing because my bootloader is locked or because I’m using the stock recovery?
Is there a way to fix this bootloop without losing my data? Is there any way to backup the device’s data before a factory reset?
I would really appreciate if someone could point me to things worth trying!
Thanks

you will find lot of contradictory information, also on xda. so please handle my information with care, too
1) no problem for official OTAs, stock recovery is intented to flash (proper signed) update.zip on locked bootloader. have a look into zip META-INF/com/google/android/updater-script and figure out where the error 21 comes from, or search for it...
2) it is A/B device so you might be able to switch slot from fastboot and boot into other working slot (if not flagged as invalid)
3) you can backup (encrypted) userdata partition from mtkclient. unfortunately this won't help on factory reset, as every android device run several proprietary OS (which can't backed up) so factory reset will destroy encryption regardless of your backup

(replied to the wrong post)

aIecxs said:
you will find lot of contradictory information, also on xda. so please handle my information with care, too
1) no problem for official OTAs, stock recovery is intented to flash (proper signed) update.zip on locked bootloader. have a look into zip META-INF/com/google/android/updater-script and figure out where the error 21 comes from, or search for it...
2) it is A/B device so you might be able to switch slot from fastboot and boot into other working slot (if not flagged as invalid)
3) you can backup (encrypted) userdata partition from mtkclient. unfortunately this won't help on factory reset, as every android device run several proprietary OS (which can't backed up) so factory reset will destroy encryption regardless of your backup
Click to expand...
Click to collapse
Thanks for the suggestions!
2) I had never heard of A/B slots before, I will read a bit about it and try
1) Error 21 seems to be caused by a ROM that isn’t signed by the manufacturer. https://gossipfunda.com/android-update-error-21/
All the ROMS on https://mirrors.lolinet.com/firmware/moto/malta/official/RETEU/ seem to be “user signed”, the 2 I tried have these filenames:
XT2095-2_MALTA_RETEU_10_QOFS30.569-36-29_2201_220222_user_SIGN_008_SVC.zip
XT2095-2_MALTA_RETEU_10_QOFS30.569-36-31_2203_220331_user_SIGN_008_SVC.zip
I read that the signature verification can be bypassed using a custom recovery, but this requires unlocking the bootloader and erasing all data.
I will try to find a signed ROM.

please double check maybe it's zip in zip

aIecxs said:
please double check maybe it's zip in zip
Click to expand...
Click to collapse
It's not, the zip contains a few dozen files, mostly .img

aIecxs said:
you will find lot of contradictory information, also on xda. so please handle my information with care, too
1) no problem for official OTAs, stock recovery is intented to flash (proper signed) update.zip on locked bootloader. have a look into zip META-INF/com/google/android/updater-script and figure out where the error 21 comes from, or search for it...
2) it is A/B device so you might be able to switch slot from fastboot and boot into other working slot (if not flagged as invalid)
3) you can backup (encrypted) userdata partition from mtkclient. unfortunately this won't help on factory reset, as every android device run several proprietary OS (which can't backed up) so factory reset will destroy encryption regardless of your backup
Click to expand...
Click to collapse
I tried to change the slot, but no luck. It's only possible with an unlocked device.
That's a pity. If it's meant to help average users who just get into a bootloop caused by a faulty update, they're unlikely to have unlocked their device, why would they?
$ ./fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.003s
$ ./fastboot --set-active=b
Setting current slot to 'b' FAILED (remote: 'set_active command is not allowed on locked devices')
fastboot: error: Command failed
$
Also found this: https://www.droidwin.com/fix-failed-remote-slot-change-is-not-allowed-in-lock-state/

too bad. you can backup seccfg, unlock with mtkclient (no fastboot flashing unlock needed) switch slots and restore seccfg. it's a bit dangerous as accidentially booting into android while in unlocked state will make encryption invalid, so make sure you boot into fastboot mode only (maybe use hair tie for volume key?)
unlocking with mtkclient does not factory reset, but do not erase metadata, userdata or md_udc (backup recommended)

aIecxs said:
too bad. you can backup seccfg, unlock with mtkclient (no fastboot flashing unlock needed) switch slots and restore seccfg. it's a bit dangerous as accidentially booting into android while in unlocked state will make encryption invalid, so make sure you boot into fastboot mode only (maybe use hair tie for volume key?)
unlocking with mtkclient does not factory reset, but do not erase metadata, userdata or md_udc (backup recommended)
Click to expand...
Click to collapse
Thanks! I'll read more about this, to be sure I understand what I'm doing, then give it a go.
Is there a step to relock with mtkclient at some point, or should I leave it unlocked and boot normally at the end?

as mentioned, do not try to boot in unlocked state you will lose all data. re-lock bootloader by restoring (locked) seccfg first!

aIecxs said:
as mentioned, do not try to boot in unlocked state you will lose all data. re-lock bootloader by restoring (locked) seccfg first!
Click to expand...
Click to collapse
Ok, I didn't know that would restore the locked state as well.

aIecxs said:
too bad. you can backup seccfg, unlock with mtkclient (no fastboot flashing unlock needed) switch slots and restore seccfg. it's a bit dangerous as accidentially booting into android while in unlocked state will make encryption invalid, so make sure you boot into fastboot mode only (maybe use hair tie for volume key?)
unlocking with mtkclient does not factory reset, but do not erase metadata, userdata or md_udc (backup recommended)
Click to expand...
Click to collapse
I'm delayed by other issues while trying to get a win10 virtualbox running so that I can run mtkclient... Am I right to assume it can run in virtualbox, and doesn't require a non-virtual win OS?

virtalbox requires usb passthrough. why not use native OS all platform supported. or just try the Live DVD V4 provided?

aIecxs said:
virtalbox requires usb passthrough. why not use native OS all platform supported. or just try the Live DVD V4 provided?
Click to expand...
Click to collapse
You're right. I think I had seen only Win and Linux, not MacOS. I was probably confused with some other tool I came across in my search!

tom353 said:
You're right. I think I had seen only Win and Linux, not MacOS. I was probably confused with some other tool I came across in my search!
Click to expand...
Click to collapse
Actually that was for SP Flash Tool, not mtkclient. So that I can backup seccfg.

mtkclient is replacement for SP Flash Tool, you can backup all partitions at once into directory out (rl = read all)
Code:
python3 mtk rl out

aIecxs said:
mtkclient is replacement for SP Flash Tool, you can backup all partitions at once into directory out (rl = read all)
Code:
python3 mtk rl out
Click to expand...
Click to collapse
Ah, great. Thanks!

In following the steps in https://github.com/bkerler/mtkclient I'm reading this:
If the device has a vendor interface 0xFF (like LG), make sure to add "blacklist qcaux" to the "/etc/modprobe.d/blacklist.conf".
How can I find out whether my device "has a vendor interface 0xFF"?

check bDeviceClass on lsusb -vv
https://www.beyondlogic.org/usbnutshell/usb5.shtml#DeviceDescriptors

It’s been a while (life happens...), but I haven’t given up on this!
I couldn’t get MTKClient to run on MacOSX, but I eventually got my hands on an old PC and used the liveDVD.
So, I did what you suggested. Backup up seccfg, unlocked bootloader with MTKClient, switched slots with fastboot, then restored seccfg.
Unfortunately, the device is still stuck in the same bootloop. Then after maybe 5 tries it goes into either fastboot, or that “Can’t load Android system. Your data may be corrupt.” screen from my first post.
Also, it switches back to slot A during that bootloop.
I could verify that after a ./fastboot reboot (into fastboot again) , the current-slot was indeed changed to B.
$ ./fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.003s
$ ./fastboot --set-active=b
Setting current slot to 'b' OKAY [ 0.011s]
Finished. Total time: 0.014s
$ ./fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.003s
$ ./fastboot set_active b
Setting current slot to 'b' OKAY [ 0.008s]
Finished. Total time: 0.011s
$ ./fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.003s
$ ./fastboot reboot
Rebooting OKAY [ 0.003s]
Finished. Total time: 0.003s
$ ./fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.003s
During the bootloop , I also diverted it into fastboot to verify, after 2 or 3 boot attempts, it was still on B. But later on it switched back to A.
Actually, I noticed that I could change the slot without unlocking the bootloader.
There are 2 ways to access fastboot on that device. One way is from within recovery mode, which I had been using initially, and in this fastboot I’m getting this message “set_active command is not allowed on locked devices”. But the other way is to access fastboot from the first menu, and that fastboot lets me use set_active.
This restriction that applies to one fastboot and not the other made me wonder whether the “OKAY” message actually did the job, but the different responses from getvar current-slot seem to confirm that.
Anyway, the short conclusion is that switching slots didn’t make the device to boot, and it sets itself back to slot A after trying to boot on B.
Another observation I made is that I’m not sure MTKClient effectively unlocked my device. It reported that it unlocked it, but then when I used it the second time to restore seccfg, it said “Device is protected”.
[09:56:23]: Loading payload from mt6765_payload.bin, 0x264 bytes
[09:56:23]: Kamakiri / DA Run
[09:56:23]: Trying kamakiri2..
[09:56:23]: Done sending payload...
[09:56:24]: Successfully sent payload: /opt/mtkclient/mtkclient/payloads/mt6765_payload.bin
[09:56:24]: Device is protected.
[09:56:24]: Device is in BROM mode. Trying to dump preloader.
[09:56:58]: Bootloader: unlock
[10:05:07]: Loading payload from mt6765_payload.bin, 0x264 bytes
[10:05:07]: Kamakiri / DA Run
[10:05:07]: Trying kamakiri2..
[10:05:07]: Done sending payload...
[10:05:07]: Successfully sent paylad: /opt/mtkclient/mtkclient/payloads/mt6765_payload.bin
[10:05:07]: Device is protected.
[10:05:07]: Device is in BROM mode. Trying to dump preloader.
[10:07:25]: test
[10:07:35]: write done!
I also went to see what fastboot was reporting after unlocking with MTKClient:
$ ./fastboot getvar unlocked
unlocked: no
Finished. Total time: 0.003s
However, that doesn’t necessarily matters, as I didn’t need to unlock it to switch slots.
Now, is there anything else I could try?
I was thinking of retrying to ADB sideload the stock OTA while the device is “maybe unlocked”.
I mean, by the look of it, it’s still locked, but I have limited trust in what my 2 inconsistent fastboot report.
So, assuming it is unlocked, is it safe to try ADB sideload while unlocked, or could this cause data loss?