Database Info

[Q] Asus Unlock Tool says device unlocked, but it actually is not

Hi there,
I have a TF300T which I am trying to unlock. I downloaded the Asus APK file, and initially it did not work. After a bit of troubleshooting I was able to get it to work by registering my device on the Asus website.
However, even though the application ran, the bootloader is not unlocked.
Code:
C:\Program Files\android_sdk\sdk\platform-tools>fastboot -i 0x0b05 getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d15b51c0c0e04
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
[B][COLOR="Red"](bootloader) unlocked: no[/COLOR][/B]
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.104s
Each time I run the Unlocking application from Asus, I get a toast message saying "Device is unlocked". I take this to mean that the APK has detected somehow that the bootloader is unlocked and doesn't attempt to unlock the device.
I tried using an older version of the Unlock tool (Version 7 instead of 8) but it's the same problem.
Has anyone had this issue before? Any ideas?

CatalystNZ said:
Hi there,
I have a TF300T which I am trying to unlock. I downloaded the Asus APK file, and initially it did not work. After a bit of troubleshooting I was able to get it to work by registering my device on the Asus website.
However, even though the application ran, the bootloader is not unlocked.
Code:
C:\Program Files\android_sdk\sdk\platform-tools>fastboot -i 0x0b05 getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d15b51c0c0e04
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
[B][COLOR="Red"](bootloader) unlocked: no[/COLOR][/B]
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.104s
Each time I run the Unlocking application from Asus, I get a toast message saying "Device is unlocked". I take this to mean that the APK has detected somehow that the bootloader is unlocked and doesn't attempt to unlock the device.
I tried using an older version of the Unlock tool (Version 7 instead of 8) but it's the same problem.
Has anyone had this issue before? Any ideas?
Click to expand...
Click to collapse
I'm not home, if no one helps you by time I get home I will. But I believe there's a modified apk or an apk not from Asus here on the forums for unlocking the boot loader. That's what I used when I unlocked my tf300t, not the one from Asus.
Edit. I just saw you said you used v7 and 8, don't remember if it's needed but is USB debugging on?
Sent from my LG-P769 using Tapatalk

I can't find any tools other than the official Asus one

CatalystNZ said:
I can't find any tools other than the official Asus one
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2094746&page=1
Try that toolkit
Sent from my LG-P769 using Tapatalk

I tried the toolkit, all it does is install the official Asus Unlock app... which as before, tells me that it has worked, however it does not actually unlock the device

CatalystNZ said:
I tried the toolkit, all it does is install the official Asus Unlock app... which as before, tells me that it has worked, however it does not actually unlock the device
Click to expand...
Click to collapse
After some quick reading, if I understood correctly some people weren't able to unlock till a day or 2 later, and the Asus registration was suspected to be the issue like it takes a day or something to register in their system. Wait till tomorrow if you can and try again and if it still doesn't work I'll see what else I can find.
Sent from my LG-P769 using Tapatalk

When you boot up your device does it say Your device is unlocked in the top left? If it does, then it actually is unlocked.
Sent from my GS3 on 4.4 KitKat using Tapatalk 4

Actually fastboot doesn't see our bootloader status, so only hint is "device is unlocked" line during boot.

No, unfortunately I do not see the message when booting up. And all attempts to flash an unsigned Recovery image fail with the message
Code:
C:\Program Files\android_sdk\sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery.img
sending 'recovery' (6890 KB)...
OKAY [ 2.666s]
writing 'recovery'...
[COLOR="Red"][B]FAILED (remote: (InvalidState))[/B][/COLOR]
finished. total time: 5.215s
I have tried flashing TWRP, and have tried a couple of versions intended for 4.2, none have worked, all with the same error.
My suspicion is that the Unlock tool only works one time per device. Mine failed during the initial unlock and now my device is flagged as unlocked on the Asus servers and cannot be unlocked again. This makes sense, otherwise people could spoof/change their device serial number and a cracked version of the Unlock tool could be made which would not void your warranty on the Asus side.
I feel like my only hope is to contact Asus, however I don't feel hopeful about that. This is the sort of thing which makes me not recommend Asus.
If they just unlocked the bootloader, without the need to phone home, it would be a lot better.

Well I contacted Asus 24 hours ago... still nothing back from their Email support.
The Unlock tool is giving now me a different error now, which is different than the usual "Device is unlocked" message from before.
The message is "An unknown error occurs...". From what I understand, this happens if the Serial Number is not in their Database, or if their server is down.. or if there is a local network problem.
I will keep trying it periodically.

First Asus response today
Hi, we're very glad to help you. For this issue, I have emailed your problem to our BU(technical department) in Taipei,I will give you the answer as soon as I receive it and I have written down your checking number.
So sorry for waiting and causing your inconvenience.
If you not get any reply from asus within 48 hours, please feel free to contact us again.
Sorry for the inconvenience.
Click to expand...
Click to collapse
I tried to run the unlock tool, and it worked this time!
So in summary, use the vip.asus.com support site to email Asus if this happens to you!

CatalystNZ said:
First Asus response today
I tried to run the unlock tool, and it worked this time!
So in summary, use the vip.asus.com support site to email Asus if this happens to you!
Click to expand...
Click to collapse
Hi guys,
I have resolved.
I confirm that the reburbished tablet isn't right registered on Taipei Asus's server.
You must contact your Asus country support and ask to update this serve with your right serial number.
My italian support good ask me a screenshot but after they help me without problem.
The day after you can unlock the tablet.
Have a good enjoy with your unlocked tablet

device tracker is down
I want to use the device tracker excuse since my last 3 vip support tickets got denied /closed with no resolution over a year ago but now the device tracker website has been phased out. Any advice? Help! I won't give up.

diesburg said:
http://forum.xda-developers.com/showthread.php?t=2094746&page=1
Try that toolkit
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
Thanks sir, you saved so much time, that root kit worked like charm, as ASUS is not providing "Unlocker apk" download.

[Q] IMEI 0 needs to recovery WHO CAN HELP?

Hi everyone,
i recieved yesterday my Moto G, 16GB,Retailversion, bought and live in Germany, bought used. Everything works well on it. This phone comes with KITKAT 4.4.2 with an unlocked bootloader, CMW and Superuser.
The phone is resettet, all clear. The only thing is, that the IMEI=0
The phone is on the latest german 175.44.1.falcon_umts.RETAIL.en.DE
Build Number: KLB20.9.10-1.9.1
If i am move with this phone the signal will be 1 to 5 or loss. If this phone is placed on my desk it chows the whole day 3 to 5 signalbars.
I tried to use this command in terminal or adb: echo 'AT +EGMR=1,7,"XXXXXXXXXXXXXXXX"> /dev/pttycmd1 but no success.
I have currently no backup from this phone, i have the IMEI of this phone.
Who can help me to write my original IMEI back to phone? This is quite urgent. PLEASE HELP ME OUT.
Thanks

How much did you pay for it you can try flashing stock ROM or firmware to see if you can recover imei
Sent from my XT1034 using xda app-developers app

serophia said:
How much did you pay for it you can try flashing stock ROM or firmware to see if you can recover imei
Sent from my XT1034 using xda app-developers app
Click to expand...
Click to collapse
I got quite the same problem, tried that many times, flashed different stock and custom roms, radio images, nothing worked..
Quite bad to have such a great "Tablet".. I'd really need to use the normal phone functions..

i think we need a imei backup from someone and change the imei to our original one. WHO can help us please?
Some files are missing in root, same was with wifi before, i found a file, that changes the state, but phone signal doesn't comming back without help.

From fastoboot you can get:
Fastboot getvar imei (you can view you imei)
Fastoboot oem writeimei your imei. (Take original imei from box)
You must have bootloader unlocked

cicciocant said:
From fastoboot you can get:
Fastboot getvar imei (you can view you imei)
Fastoboot oem writeimei your imei. (Take original imei from box)
You must have bootloader unlocked
Click to expand...
Click to collapse
If I try this it just gets out
FAILED (remote failure)
finished. total time: 0.020s

RestlessScreams said:
If I try this it just gets out
FAILED (remote failure)
finished. total time: 0.020s
Click to expand...
Click to collapse
hi, i did this command: Fastboot getvar imei
IMEI is listed correctly , but i can't do this command after too: Fastoboot oem writeimei "your imei"
Same problem as user "RestlessScreams"
FAILED (remote failure)
finished. total time: 0.016s

Jerome-X said:
hi, i did this command: Fastboot getvar imei
IMEI is listed correctly , but i can't do this command after too: Fastoboot oem writeimei "your imei"
Same problem as user "RestlessScreams"
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
Try using :
fastboot oem writeimei "your imei".... I think "cicciocant" made a typo, if i'm not mistaken.

mardobloom said:
Try using :
fastboot oem writeimei "your imei".... I think "cicciocant" made a typo, if i'm not mistaken.
Click to expand...
Click to collapse
This is what i got in fastboot: (fastboot.exe getvar all)
(bootloader) version: 0.5
(bootloader) version-bootloader: 4105
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA8900FI4F
(bootloader) cid: 0x0007
(bootloader) uid: 28F911020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 3X5XX2X5XX16XX7 (the IMEI is shown correctly)
(bootloader) meid:
(bootloader) date: 12-26-2013
(bootloader) sku: XT1032
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Feb 24 8:58:15 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retde/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.2/KLB20.9-1.10-1.24-1.1/1:user
(bootloader) ro.build.fingerprint[2]: /release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.176.44.1.falcon_umts
(bootloader) ro.build.version.full[1]: .Retail.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2.3.04.03.0
(bootloader) ro.build.version.qcom[1]: 0.166.006
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-gc6fc9e1-00001-gf3bf
(bootloader) kernel.version[1]: 628 ([email protected]) (gcc version 4.
(bootloader) kernel.version[2]: 7 (GCC) ) #1 SMP PREEMPT Thu Feb 6 23:07
(bootloader) kernel.version[3]: :13 CST 2014
(bootloader) sdi.git: git=MBM-NG-V41.05-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V41.05-0-g6863770
(bootloader) rpm.git: git=MBM-NG-V41.05-0-g4018bbe
(bootloader) tz.git: git=MBM-NG-V41.05-0-g11658be
(bootloader) aboot.git: git=MBM-NG-V41.05-0-gf4ab363
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
all: listed above
finished. total time: 0.062s
but IMEI shows 0 while running system.
No signal, no provider, only WIFI is useable

You van try this:
http://forum.xda-developers.com/showthread.php?t=2623587
Inviato dal mio XT1032 utilizzando Tapatalk

doesent work, how to get my imei back? any possible solution here let me not write my imei back to phone. Why do i see my imei in fastbootmode and not in Android OS?
Gesendet von meinem LG-D802 mit Tapatalk

Got same problem since three weeks.
Tried re flashing stock, changing radio, break fastboot... Nothing worked, i was going to give it back to Motorola but i see many people got same problem so I think i'll wait a bit for a potential solution.
Getvar all gave me correct imei, system shows 0.
Sent from my XT1032 using Tapatalk
---------- Post added at 08:09 AM ---------- Previous post was at 07:39 AM ----------
sorry to add more to my previous reply:
"AT +EGMR=1,7,"XXXXXXXXXXXXXXXX"> /dev/pttycmd1" only works for MTK based phones.
And
writeimei isn't supported in fastboot
I was thinking if there is a way to physically remove battery from Moto G, haven't found any in google

Did you flash your phone without Sim Card?
If i understand this statement right, he had the same problem while flashing his phone without sim card.
herbesi01 said:
I solved the problem, place to charge the phone, let him take some of the load and flash the original ROM, after that flash CM11, and run perfectmente, I think at first it was because I had done without the SIM, the second time you make with the SIM sunset ...
Click to expand...
Click to collapse

mokkami said:
Did you flash your phone without Sim Card?
If i understand this statement right, he had the same problem while flashing his phone without sim card.
Click to expand...
Click to collapse
I tried flashing always with SIM Card on it, i even changed Cards but still 0 imei.

Maybe this is compatible with Moto G?!

The go back to stock without SIM, skip all and going home, boot off, reinsert another SIM isn't working.
will try other solutions, i hope

any news, about restore IMEI?

Jerome-X said:
any news, about restore IMEI?
Click to expand...
Click to collapse
Not yet unluckly...

Edit

mokkami said:
Maybe this is compatible with Moto G?!
Click to expand...
Click to collapse
DId someone try ?

Messed up installing 5.1.11. now only fastboot boots and can't boot twrp image.

i tried to install the newest 5.1.11 in full ( as i am magisk rooted, twrp installed, and bootloader unlocked). i kept getting system ui crashes over and over and eventually, after so many, the phone just powers down by itself. I had tried clearing cache after going back into twrp. Rebooted. Same ui issue. Then i decided to restore a backup in twrp i had made a few weeks ago stored on internal memory. This was a bad idea. It said it restored successfully but upon reboot, i only get fastboot now. i think it is communicating with fastboot but when i try to fastboot boot twrp-3.2.1-0 (or 3.2.2-0) i get, "remote: Failed to load/authenticate boot image: Load Error". I do not know what to do and am hoping you guys can figure out how to fix this. Any attempt to enter recovery via buttons results in fastboot booting. restart is also fastboot.
This is what my phone says:
FastBoot mode
Product_name- sdm845
variant- sdm ufs
basband version-
serial- it's there
secure boot- yes
device state- unlocked
Don't know if this helps fastboot getvar all reports this:
C:\Adb\OnePlus 6 Files>fastboot getvar all
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3837
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B800B7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xB2C00000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno: omitted
(bootloader) product:sdm845
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.047s
Is there anyone that has had this set of circumstances and got out of it? Any help is appreciated. There are some things i've seen that i can do but don't want to do further damage. Thanks to all for any and all help.

thejase said:
i tried to install the newest 5.1.11 in full ( as i am magisk rooted, twrp installed, and bootloader unlocked). i kept getting system ui crashes over and over and eventually, after so many, the phone just powers down by itself. I had tried clearing cache after going back into twrp. Rebooted. Same ui issue. Then i decided to restore a backup in twrp i had made a few weeks ago stored on internal memory. This was a bad idea. It said it restored successfully but upon reboot, i only get fastboot now. i think it is communicating with fastboot but when i try to fastboot boot twrp-3.2.1-0 (or 3.2.2-0) i get, "remote: Failed to load/authenticate boot image: Load Error". I do not know what to do and am hoping you guys can figure out how to fix this. Any attempt to enter recovery via buttons results in fastboot booting. restart is also fastboot.
This is what my phone says:
FastBoot mode
Product_name- sdm845
variant- sdm ufs
basband version-
serial- it's there
secure boot- yes
device state- unlocked
Don't know if this helps fastboot getvar all reports this:
C:\Adb\OnePlus 6 Files>fastboot getvar all
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3837
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B800B7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xB2C00000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno: omitted
(bootloader) product:sdm845
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.047s
Is there anyone that has had this set of circumstances and got out of it? Any help is appreciated. There are some things i've seen that i can do but don't want to do further damage. Thanks to all for any and all help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 your solution lies here

tabletalker7 said:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 your solution lies here
Click to expand...
Click to collapse
I saw this. Will i keep my data with this method?

thejase said:
I saw this. Will i keep my data with this method?
Click to expand...
Click to collapse
no, but if you can't even boot to TWRP then you have nothing left to save at this point.

Try booting the latest twrp (3.2.3.0) before giving up and wiping. If you can get to fastboot, you're not bricked.

iElvis said:
Try booting the latest twrp (3.2.3.0) before giving up and wiping. If you can get to fastboot, you're not bricked.
Click to expand...
Click to collapse
thanks for the suggestions but no dice.

According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot rom to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.

tabletalker7 said:
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot rom to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
Click to expand...
Click to collapse
That's alright. I appreciate the point in the right direction. Doing that fastboot method bat file that you suggested now... Thanks for the help.

thejase said:
That's alright. I appreciate the point in the right direction. Doing that fastboot method bat file that you suggested now... Thanks for the help.
Click to expand...
Click to collapse
tabletalker7 said:
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot ROM to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
Click to expand...
Click to collapse
So as it turns out that method worked using the bat file flash all fastboot. Though, not at first. When it first rebooted after the bat file finished flashing. system UI was still crashing. When you initially run the bat file at the beginning, it asks if you want to delete your data. First time around i said no, just to see what it would do. Well it booted, but kept getting that system ui crash that I had in the beginning of all this mess. I rebooted and this time chose to erase data and then it re-flashed all again (same bat file). Turns out, when it booted, same deal, system UI crash. So this time i was looking things up while the crashes where happening and then it just rebooted on its own (as it does with a number of system UI crashes in succession). When it came up it was that Chinese menu (which i assume to be download mode or something). Anyway, i chose English and it's a menu to clear dalvik and cache, system settings reset, and one other i can't remember. i did system settings then dalvik and finally, when i rebooted, it was like it was booting for the first time with no crashes. Only thing i can figure is that setting in the bat file at first launch actually didn't erase user data since when it booted, all my icons where there in the background. doing it "on device" in download mode seems to have worked. I am only adding this information as an f.y.i.. Thanks again for all your help, guys.

thejase said:
When it came up it was that Chinese menu (which i assume to be download mode or something).
Click to expand...
Click to collapse
That's stock recovery.

maigre said:
That's stock recovery.
Click to expand...
Click to collapse
Oh, ok. Funny thing is, I had never seen what that looked like as I immediately installed twrp from the time I bought it. Makes sense, though I still wonder why it booted to stock recovery after systemui crashing. Unless it senses the crashes and does that by default to clear system settings and data for a successful boot?

moto one vision hard bricked

i unlocked the bootloader and then unknowingly i gave command " fastboot erase all ".
now the device is not powering on and not even responding,no screen on (even when inserting charger).
can anyone suggest a solution??

D A R K 9 said:
i unlocked the bootloader and then unknowingly i gave command " fastboot erase all ".
now the device is not powering on and not even responding,no screen on (even when inserting charger).
can anyone suggest a solution??
Click to expand...
Click to collapse
Take it to a service center for flashing the firmware?

D A R K 9 said:
i unlocked the bootloader and then unknowingly i gave command " fastboot erase all ".
now the device is not powering on and not even responding,no screen on (even when inserting charger).
can anyone suggest a solution??
Click to expand...
Click to collapse
Don't take strictly right but I've done it some time ago on a Snapdragon phone . For this you absolutely need for Motorola One Vision Qfil files and Flashone app for Windows . The whole process is very simple but finding proper Qfil files ROM is a pain in the butt .
If you find these files somehow , anywhere , anytime don't forget to share .
...............................
Or use this : https://forum.xda-developers.com/moto-z/help/help-moto-z-dead-brick-t3809740
Or this : https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183

muppetz said:
Don't take strictly right but I've done it some time ago on a Snapdragon phone . For this you absolutely need for Motorola One Vision Qfil files and Flashone app for Windows . The whole process is very simple but finding proper Qfil files ROM is a pain in the butt .
If you find these files somehow , anywhere , anytime don't forget to share .
...............................
Or use this : https://forum.xda-developers.com/moto-z/help/help-moto-z-dead-brick-t3809740
Or this : https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183
Click to expand...
Click to collapse
ya but i used to do same cmd for sony and mi mobile but never faced this issue,i didnt expect this thing from a motorola device.now they are saying to change sub board for not power on reason reason at service center.

D A R K 9 said:
ya but i used to do same cmd for sony and mi mobile but never faced this issue,i didnt expect this thing from a motorola device.now they are saying to change sub board for not power on reason reason at service center.
Click to expand...
Click to collapse
You're right . It doesn't explain their proposals if you just did a simple cmd to the phone as you said . Maybe they try to squeeze some extra bucks from you . I'm sorry , man .

hard bricked one vision
its showing as exynos9610 in device manager,any leads from here??

D A R K 9 said:
its showing as exynos9610 in device manager,any leads from here??
Click to expand...
Click to collapse
good news , it seems pc recognize phone , further steps to bring back phone , no clue, but I supose it's primordial to flash partitions . Google it .

D A R K 9 said:
its showing as exynos9610 in device manager,any leads from here??
Click to expand...
Click to collapse
Look in the OP for a rom to flash in fastboot.

gee2012 said:
Look in the OP for a rom to flash in fastboot.
Click to expand...
Click to collapse
sadly its not going to fastboot mode.as of matter still screen not showing anything,only thing just pc shows a device connected in usb as exynos9610

D A R K 9 said:
sadly its not going to fastboot mode.as of matter still screen not showing anything,only thing just pc shows a device connected in usb as exynos9610
Click to expand...
Click to collapse
Try the adb command ` fastboot devices` and see if you get a serial number.

I'm also in this same situation. Been looking all around for solutions but all i come across are fixes for qualcom devices. Even all the blankflashing posts are qualcom. My guess is that we need to find software that'll work with exynos chips that isn't samsung. Adb, fastboot and mfastboot commands don't work because in its current state the device is only recognized as "Exynos9610"

I have the same problema. Im trying to follow this thread:
https://forum.xda-developers.com/galaxy-s6/general/guide-repair-hard-bricked-devices-t3573865/amp/
My problem is that my computer is Windows 10 and it can't load the Exynos drivers, I hope that you have good look with that. You should try to change the cfg archive to load bootloader.

Found something intresting on "lolinet" today. A "blankflash" for kane.
Could be worth a try for sure, if you're hardbricked.
I have not tried it so I've no idea if this is legit.
The procedure would probably be something like:
Unzip all files.
Install drivers (ImageWriterUSBDriver_1113_00.exe).
Open "Multidownloader_64bit_1.4.1.exe".
Connect device to usb and let multidownloader detect it.
In the "box", browse for the "usbbooting.cfg" that is present in the kane_blankflash and hit start.
My guess is that it's supposed to reboot to fastboot once it's done writing the files so that you can reflash full firmware from fastboot, like it is with blankflash for other moto devices.
Let us know how it goes if anyone tries it.

Error
I'm in trouble, too.
I can even enter fastboot but do not accept to update, the following error appears.
target max-sparse-size: 256MB
sending 'fwbl1' (16 KB)...
OKAY [ 0.040s]
writing 'fwbl1'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fwbl1
FAILED (remote failure)
finished. total time: 0.082s
Click to expand...
Click to collapse
My phone get vars
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.2-kane_retail-523afc7-190729
(bootloader) product: kane
(bootloader) board: kane
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: ufs
(bootloader) ufs: 128GB WDC SDINDDH4-128G FV=1268
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: Exynos9609
(bootloader) serialno: 0057049924
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 000003B54E4B96FA0000000000000000
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 354154101426432
(bootloader) meid:
(bootloader) date: 05-09-2019
(bootloader) sku: XT1970-1
(bootloader) carrier_sku: XT1970-1
(bootloader) battid: SB18C43602
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Aug 28 2:48:21 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/kane/kane_sprout:9/PSAS29
(bootloader) ro.build.fingerprint[1]: .137-16-4/fc9db:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.221.4.kane.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.samsung: 20190510
(bootloader) version-baseband: S337AP_KANE_SGCS_QB2190425
(bootloader) kernel.version[0]: Linux version 4.14.56-g1007313 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld115) (Android (4691093 based on
(bootloader) kernel.version[2]: r316199) clang version 6.0.2 (]
(bootloader) kernel.version[3]:
(bootloader) kernel.version[4]: 83abd29fc496f55536e7d904e0abae47888fc7f)
(bootloader) kernel.version[5]: (
(bootloader) kernel.version[6]: hain/llvm 34361f192e41ed6e4e8f9aca80a4ea
(bootloader) kernel.version[7]: 7e9856f327) (based on LLVM 6.0.2svn)) #1
(bootloader) kernel.version[8]: SMP PREEMPT Mon Jul 29 06:52:16 CDT 201
(bootloader) kernel.version[9]: 9
(bootloader) bootloader.git: MBM-2.2-kane_retail-523afc7-190729
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
Click to expand...
Click to collapse
Anyone can helpme?

Okay, I know the last message here was almost 2 years ago, but I'm just here to confirm, that I've tried this blankflash and indeed, it works.
So I've rewritten both bootloader A and B slots with /dev/zero and tried to reboot. Of course, nothing happened, but the device was detected and booted into fastboot. Everything was working there. Than just flashed bootloader_a and bootloader_b and it booted like nothing happened.

danmaya said:
Error
I'm in trouble, too.
I can even enter fastboot but do not accept to update, the following error appears.
My phone get vars
Anyone can helpme?
Click to expand...
Click to collapse
So here you have probably broken UFS (device's internal storage). If the files you try to flash are signed, but you still can't load them, then it means, you have corrupted memory. With this, go to service, they could try to replace UFS chip with another one. From what I can see, your bootloader is locked, so try to unlock it and then flash the firmware, maybe this will work.

Fire HD 8 (9th Generation) Onyx Engineering Sample (with Root access, full fastboot)

I recently got my hands on a Fire HD 8 (9th gen, 2020?), specifically a pre-production model that is both really locked down and not super locked down. For instance, I can pull a bunch of files from system directories and look at them on my PC, but I can't get it to install apps outside of a small selection Amazon seems to think are okay. I'm trying to rip sensor and spec data off the thing but I haven't had any luck.
after looking a bit closer at things, I can tell that your actually given root perms out of the box. I'm able to do stuff like disable every app, chmod, and overall just mess around. The codename is onyx and it seems the 10th gen is just the 9th gen but slightly altered.
Images:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://imgur.com/a/XJMwNuG <-- More here
Here's the unit itself: https://youtu.be/v1BrM1GdoM4?t=4467
That timestamp is when I have it pulled apart and I do some close-ups of parts of the board.
More pics and some dumped data (incl. dumped partitions) https://drive.google.com/drive/folders/1Xl3CfJnkY7NuR_sEkEf2XlifT7S7wE2S
Let me know if there's anything interesting to try on this thing that you're aware of.
If you wanna chat about this somewhere, I've got a discord server for general purposes: https://discord.gg/pPQtYnS

It seems you have the same model (onyx) as the one currently on sale (HD 8 2020/ 10th generation): https://forum.xda-developers.com/showpost.php?p=82747107&postcount=1.

MontysEvilTwin said:
It seems you have the same model (onyx) as the one currently on sale (HD 8 2020/ 10th generation): https://forum.xda-developers.com/showpost.php?p=82747107&postcount=1.
Click to expand...
Click to collapse
If the specs are the exact same, then I basically have an OEM image containing working fastboot and a rooted-stock version of Fire OS that just needs patching to allow me to install apps.
Amazon's impl of PackageManager (iirc) has some checks in it that prevent me from installing anything but whitelisted apps, but I have yet to find a way to either disable that check or intercept and manipulate the whitelist.

lokio27 said:
I recently got my hands on a Fire HD 8 (9th gen, 2020?), specifically a pre-production model that is both really locked down and not super locked down. For instance, I can pull a bunch of files from system directories and look at them on my PC, but I can't get it to install apps outside of a small selection Amazon seems to think are okay. I'm trying to rip sensor and spec data off the thing but I haven't had any luck.
after looking a bit closer at things, I can tell that your actually given root perms out of the box. I'm able to do stuff like disable every app, chmod, and overall just mess around. The codename is onyx and it seems the 10th gen is just the 9th gen but slightly altered.
Here's the unit itself: https://youtu.be/v1BrM1GdoM4?t=4467
That timestamp is when I have it pulled apart and I do some close-ups of parts of the board.
Let me know if there's anything interesting to try on this thing that you're aware of.
Click to expand...
Click to collapse
Hey there,
First time I see something like this.
Would you mind dumping your bootloader/preloader/tz?
You should run in adb shell:
Code:
dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin
dd if=/dev/block/platform/bootdevice/by-name/lk of=/sdcard/lk.bin
dd if=/dev/block/platform/bootdevice/by-name/tee1 of=/sdcard/tee1.bin
After you ran those commands, just exit the shell and pull out the files.
EDIT: Also, if you reboot to bootloader (adb reboot bootloader) and you run
Code:
fastboot getvar all
what's the output?
EDIT2: Assuming this is a non-production device (engineering?) you should be able to use SP Flash Tools? Maybe @diplomatic can throw us here some light.
Regards!

I wonder why Amazon have so tightly controlled which apps can be installed on a pre-production device which looks like it has an unlocked bootloader and allows root access? Are they experimenting with blocking apps from Google and other non-Amazon sources?
If you know the name of the gatekeeper app you can try 'pm disable-user --user 0' plus the name of the app to disable it and test. This is reversible.

Rortiz2 said:
Hey there,
First time I see something like this.
Would you mind dumping your bootloader/preloader/tz?
You should run in adb shell:
Code:
dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin
dd if=/dev/block/platform/bootdevice/by-name/lk of=/sdcard/lk.bin
dd if=/dev/block/platform/bootdevice/by-name/tee1 of=/sdcard/tee1.bin
After you ran those commands, just exit the shell and pull out the files.
EDIT: Also, if you reboot to bootloader (adb reboot bootloader) and you run
Code:
fastboot getvar all
what's the output?
EDIT2: Assuming this is a non-production device (engineering?) you should be able to use SP Flash Tools? Maybe @diplomatic can throw us here some light.
Regards!
Click to expand...
Click to collapse
Here's the folder with all my dumps: https://drive.google.com/drive/folders/1Xl3CfJnkY7NuR_sEkEf2XlifT7S7wE2S
All the files are compressed, and everything should be there.
Also, here's the fastboot getvar all output
Code:
C:\platform-tools>fastboot getvar all
(bootloader) unlock_status: false
(bootloader) unlock_code: 0xcbc541c615958bf408416cfd
(bootloader) antirback_tee_version: 0x0001
(bootloader) antirback_lk_version: 0x0102
(bootloader) antirback_pl_version: 0x0102
(bootloader) rpmb_state: 1
(bootloader) prod: 0
(bootloader) secure: yes
(bootloader) lk_build_desc: 6930388-20191017_215445
(bootloader) pl_build_desc: 1087595-20191021_214610
(bootloader) max-download-size: 0x8000000
(bootloader) variant:
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x0
(bootloader) hw-revision: 0
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 4313mV
(bootloader) partition-size:userdata: 64e27be00
(bootloader) partition-type:userdata: f2fs
(bootloader) partition-size:vendor: e000000
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:system: c0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 1f400000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:recovery: 2800000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 2000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:cam_vpu3: f00000
(bootloader) partition-type:cam_vpu3: ext4
(bootloader) partition-size:cam_vpu2: 2000000
(bootloader) partition-type:cam_vpu2: ext4
(bootloader) partition-size:cam_vpu1: f00000
(bootloader) partition-type:cam_vpu1: ext4
(bootloader) partition-size:nvcfg: 800000
(bootloader) partition-type:nvcfg: ext4
(bootloader) partition-size:boot_para: 100000
(bootloader) partition-type:boot_para: raw data
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:lk: 100000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:misc: 100000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:keys: 800000
(bootloader) partition-type:keys: raw data
(bootloader) partition-size:dkb: 100000
(bootloader) partition-type:dkb: raw data
(bootloader) partition-size:kb: 100000
(bootloader) partition-type:kb: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) serialno: [[REDACTED]]
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) kernel: lk
(bootloader) product: onyx
(bootloader) slot-count: 0
(bootloader) version-baseband: N/A
(bootloader) version-bootloader: onyx-6930388-20191017120652-20191017215
(bootloader) version-preloader: 0.1.000
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.099s
MontysEvilTwin said:
I wonder why Amazon have so tightly controlled which apps can be installed on a pre-production device which looks like it has an unlocked bootloader and allows root access? Are they experimenting with blocking apps from Google and other non-Amazon sources?
If you know the name of the gatekeeper app you can try 'pm disable-user --user 0' plus the name of the app to disable it and test. This is reversible.
Click to expand...
Click to collapse
Disabling the gatekeeper app just breaks the notification, things are still being blocked by an internal implementation of the package manager service.

lokio27 said:
Here's the folder with all my dumps: https://drive.google.com/drive/folders/1Xl3CfJnkY7NuR_sEkEf2XlifT7S7wE2S
All the files are compressed, and everything should be there.
Also, here's the fastboot getvar all output
Code:
C:\platform-tools>fastboot getvar all
(bootloader) unlock_status: false
(bootloader) unlock_code: 0xcbc541c615958bf408416cfd
(bootloader) antirback_tee_version: 0x0001
(bootloader) antirback_lk_version: 0x0102
(bootloader) antirback_pl_version: 0x0102
(bootloader) rpmb_state: 1
(bootloader) prod: 0
(bootloader) secure: yes
(bootloader) lk_build_desc: 6930388-20191017_215445
(bootloader) pl_build_desc: 1087595-20191021_214610
(bootloader) max-download-size: 0x8000000
(bootloader) variant:
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x0
(bootloader) hw-revision: 0
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 4313mV
(bootloader) partition-size:userdata: 64e27be00
(bootloader) partition-type:userdata: f2fs
(bootloader) partition-size:vendor: e000000
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:system: c0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 1f400000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:recovery: 2800000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 2000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:cam_vpu3: f00000
(bootloader) partition-type:cam_vpu3: ext4
(bootloader) partition-size:cam_vpu2: 2000000
(bootloader) partition-type:cam_vpu2: ext4
(bootloader) partition-size:cam_vpu1: f00000
(bootloader) partition-type:cam_vpu1: ext4
(bootloader) partition-size:nvcfg: 800000
(bootloader) partition-type:nvcfg: ext4
(bootloader) partition-size:boot_para: 100000
(bootloader) partition-type:boot_para: raw data
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:lk: 100000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:misc: 100000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:keys: 800000
(bootloader) partition-type:keys: raw data
(bootloader) partition-size:dkb: 100000
(bootloader) partition-type:dkb: raw data
(bootloader) partition-size:kb: 100000
(bootloader) partition-type:kb: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) serialno:
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) kernel: lk
(bootloader) product: onyx
(bootloader) slot-count: 0
(bootloader) version-baseband: N/A
(bootloader) version-bootloader: onyx-6930388-20191017120652-20191017215
(bootloader) version-preloader: 0.1.000
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.099s
Disabling the gatekeeper app just breaks the notification, things are still being blocked by an internal implementation of the package manager service.
Click to expand...
Click to collapse
Hey!
Thanks for those images! Very appreciated!
Well, so definelety your tablet looks unlocked.
Would you mind dumping your boot1 (/dev/block/mmcblk0boot1) or just the "idme print" output and sharing it via PM (as it contains your serial, etc)? Having the idme unlock can be useful:good:
Regards.
PS: Delete the kb partition from the folder and your serial number from getvar all output

Rortiz2 said:
Hey!
Thanks for those images! Very appreciated!
Well, so definelety your tablet looks unlocked.
Would you mind dumping your boot1 (/dev/block/mmcblk0boot1) or just the "idme print" output and sharing it via PM (as it contains your serial, etc)? Having the idme unlock can be useful:good:
Regards.
PS: Delete the kb partition from the folder and your serial number from getvar all output
Click to expand...
Click to collapse
I'm not terribly concerned about the serial number or anything myself as it's already been shown like 30 times in all sorts of different media, including pics and videos of the unit. I uploaded boot1 to the folder so check the link again.
If there's a good reason to remove the s/n I will, but I'm not too terribly worried myself.

lokio27 said:
I'm not terribly concerned about the serial number or anything myself as it's already been shown like 30 times in all sorts of different media, including pics and videos of the unit. I uploaded boot1 to the folder so check the link again.
If there's a good reason to remove the s/n I will, but I'm not too terribly worried myself.
Click to expand...
Click to collapse
Hi again,
Thanks for the boot1 dump. Nothing interesting in idme unlock (blank).
If i'm allowed to ask, how did this tablet (prototipe?) ended in your hands...? Just wondering
EDIT: Could you verify if fastboot it's really unlocked? Try wiping misc:
Code:
fastboot erase misc
Regards!

Rortiz2 said:
Hi again,
Thanks for the boot1 dump. Nothing interesting in idme unlock (blank).
If i'm allowed to ask, how did this tablet (prototipe?) ended in your hands...? Just wondering
Regards!
Click to expand...
Click to collapse
Wandered into my possession via eBay. Didn't even spend half of what the 10th gen costed on it, funnily enough. I'd like to fix the app installation issue so I can install stuff on it (notably Discord and/or Google Chrome)
Also, yes I'll try that.

Rortiz2 said:
Hi again,
EDIT: Could you verify if fastboot it's really unlocked? Try wiping misc:
Code:
fastboot erase misc
Regards!
Click to expand...
Click to collapse
It does work!
Code:
C:\platform-tools>fastboot devices
XXXXXXXXXXXXXXXX fastboot
C:\platform-tools>fastboot erase misc
Erasing 'misc' OKAY [ 0.019s]
Finished. Total time: 0.026s

lokio27 said:
It does work!
Code:
C:\platform-tools>fastboot devices
XXXXXXXXXXXXXXXX fastboot
C:\platform-tools>fastboot erase misc
Erasing 'misc' OKAY [ 0.019s]
Finished. Total time: 0.026s
Click to expand...
Click to collapse
Hey,
Nice so yeah working fastboot.
Do you have telegram? I would like to talk with you via there.
Regards.

Rortiz2 said:
Hey,
Nice so yeah working fastboot.
Do you have telegram? I would like to talk with you via there.
Regards.
Click to expand...
Click to collapse
Sure, I'll DM you my Telegram.

Thanks to help from @Rortiz2, we were able to get a stock system image from the Fire HD 8 (2020) running on this tablet. Sure enough, still have root permissions, and now I can actually install apps! Will be updating as more things are discovered.

You guys are amazing.

a guide maybe?
hi guy/gals, is there a guide for rooting the Onyx variant? thanks for your efforts!!!

I hope you guys find a way to crack this baby.

joining in this baby as well

Welp i tried shorting every test point and wont work for some reason but when i disconnect the battery and connect it via pc it keeps rebooting to the Preloader already so was wondering if its possible to use that to exploit the bootloader?

Awesomeslayerg said:
Welp i tried shorting every test point and wont work for some reason but when i disconnect the battery and connect it via pc it keeps rebooting to the Preloader already so was wondering if its possible to use that to exploit the bootloader?
Click to expand...
Click to collapse
no there isnt a bootrom exploit at this time on the hd8 (10). Mediatek seems to have fixed the exploit on their chip. If anyone can find a way to get into the bootrom there is hope for the old exploit. Maybe someone will get a root exploit that will force a bootrom boot. still early in the device....