I recently bought an amazon echo dot second generation with the idea of hacking it to install my own OS onto it. I have tried poking at it with fastboot tools but I haven't been able to unlock the bootloader, let alone install a custom rom. When I run
Code:
fastboot getvar all
, I get this:
Code:
(bootloader) lk_build_desc: f379dba-20170906_000423
(bootloader) pl_build_desc: 531fa14-20170929_175430
(bootloader) prod: 1
(bootloader) unlock_status: false
(bootloader) unlock_code: 0xea7ab546330135bf
(bootloader) serialno: G090LF1182070BR6
(bootloader) max-download-size: 0x6d00000
(bootloader) warranty: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: BISCUIT
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.005s
I'd like to draw attention to the unlock_code line. I can't seem to find what that means, but it could allow me to unlock the bootloader and get one step closer.
Before you comment something like "Oh yeah that's not possible", Don't. That's not helpful and could possibly be wrong.
You can already exploit them using amonet if you want to boot your own code. Take a look at http://andygoetz.org/tags/dot/
Related
So,
I ended up buying a very nice display unit from a walmart(for a steal!)
It had demo software on it(that wasnt able to be removed from inside the ROM) and was missing some functionality due to it being a display unit. I unlocked it, and flashed me some ICS the first day I got it. I just realized a few days ago it is a 32 gb even though the demo ROM on it said it was a 16gb. Thought that was odd. Now, Im wondering.......Could it also be a verizon xoom dsiplay, and the demo software just didnt support the 4G? How can I easily tell what exact model number it is?
Thanks!!
if you go Settings - About Tablet
Under building bumber it will show something like
1.6.0_218.3-MZXXX
the MZ number is your model number.
OR
the long way...use adb
abd reboot-bootloader
Click to expand...
Click to collapse
device reboots
then from command run
fastboot getvar -all
Click to expand...
Click to collapse
you will then get an output like this
c:\Android\android-sdk\platform-tools>fastboot getvar -all
(bootloader) max-download-size: 994148352
(bootloader) version: 0.3
(bootloader) qe: qe 0/0
(bootloader) version-bootloader: 0A69
(bootloader) serialno: TA312004XJ
(bootloader) msn: N056QW2347
(bootloader) modelno: MZ607-16
(bootloader) carrier: wifi-only
(bootloader) apdieid: 1100011820FA3B0A010000000600
(bootloader) product: FLEMING
(bootloader) model-id: 0010
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) sstdiag: 3d0577480cf68efc12ef366e161acd6
(bootloader) cpu: OMAP4430 S
(bootloader) sbd_dis: ff
(bootloader) cid: 7
-all: Done
finished. total time: 0.032s
Click to expand...
Click to collapse
Hi all,
I've just got given a Chinese Hisense phone. I'd like to root the phone and install a custom ROM. Problem is, I can't find too much info on this device. On the package, it shows as a "Hisense F25M".
Navigating through the device, it shows as Model Number HLTE100M.
Hopefully someone on here can direct me to the right rooting and ROM.
Many thanks,
Arj
Hi all,
I have a Hisense A2M (Hisense A2 Pro) running Vision 5 Android 7.1.2
with Hardware V1.00 Software L1414.6.01.02.00 Kernel 3.18.31 and
I cannot unlock the bootloader and thus I cannot root it.
fastboot does not accept the command "oem unlock".
These are all available fastboot variables:
fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4125000
(bootloader) variant:QRD eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xd295faa00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x100000000
(bootloader) serialno:35601126
(bootloader) kernel:lk
(bootloader) product:A2M
all:
finished. total time: 0.213s
Hints are highly appreciated.
Many thanks, Siegfried
Hi,
There are software versions on the Chinese forum fans"dot"hisense"dot"com , e.g. thread-132062-1-3.html which I could not manage to download.
Any idea how to get an international software version for that phone?
Thanks, Siegfried
Good Night, a pleasure
I have a problem with my motoG 2013 XT1032 unisim, the bootloader was blocked and I followed the steps to request the unlock key, using the commands fastboot oem get_unlock_data and then I went to the page of motorola and I got my email the key to unlocking, I introduced it after this command
fastboot oem unlock ......... (in the points goes the key)
Everything worked perfect I installed a rom 4.4.2 and the cell started without problems, then I made the biggest mistake that I got an update via ota and I gave him from that moment the phone was completely brickeo and I could save was with the blankflash , but from there the phone is in fastboot and tried to install the same flash but everything says denied permissions, when I check the screen well, I get device is LOCKED Status Code: 0. I understand that the bootloader is blocked again but when I try to perform The same steps of deblocking bootloader with this line tells me the following:
D: \ MotoG \ ADB Tools> fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [0.006s]
finished Total time: 0.011s
Then I thought it was because I already had the password, I entered the password and it says the following:
D: \ MotoG \ ADB Tools> fastboot oem unlock (CLAVE)
...
(bootloader) fastboot oem unlock disabled!
FAILED (remote failure)
finished Total time: 0.015s
Now when introducing
D: \ MotoG \ ADB Tools> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A (*)
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV = 06 PRV = 07 TYPE = 17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE = 4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: 1c5580f
(bootloader) cid: 0xFFFF
(bootloader) channelid: 0xDEAD
(bootloader) uid: ABF178040F000000000000000000
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sdi.git:
(bootloader) sbl1.git:
(bootloader) rpm.git:
(bootloader) tz.git:
(bootloader) aboot.git: git = MBM-NG-V41.1A-0-g80481ae
(bootloader) qe:
(bootloader) ro.carrier:
all: listed above
finished Total time: 0.103s
Please can you help me and see how to solve, excuse my english.
rcheo22 said:
Good Night, a pleasure
I have a problem with my motoG 2013 XT1032 unisim, the bootloader was blocked and I followed the steps to request the unlock key, using the commands fastboot oem get_unlock_data and then I went to the page of motorola and I got my email the key to unlocking, I introduced it after this command
fastboot oem unlock ......... (in the points goes the key)
Everything worked perfect I installed a rom 4.4.2 and the cell started without problems, then I made the biggest mistake that I got an update via ota and I gave him from that moment the phone was completely brickeo and I could save was with the blankflash , but from there the phone is in fastboot and tried to install the same flash but everything says denied permissions, when I check the screen well, I get device is LOCKED Status Code: 0. I understand that the bootloader is blocked again but when I try to perform The same steps of deblocking bootloader with this line tells me the following:
D: \ MotoG \ ADB Tools> fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [0.006s]
finished Total time: 0.011s
Then I thought it was because I already had the password, I entered the password and it says the following:
D: \ MotoG \ ADB Tools> fastboot oem unlock (CLAVE)
...
(bootloader) fastboot oem unlock disabled!
FAILED (remote failure)
finished Total time: 0.015s
Now when introducing
D: \ MotoG \ ADB Tools> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A (*)
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV = 06 PRV = 07 TYPE = 17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE = 4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: 1c5580f
(bootloader) cid: 0xFFFF
(bootloader) channelid: 0xDEAD
(bootloader) uid: ABF178040F000000000000000000
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sdi.git:
(bootloader) sbl1.git:
(bootloader) rpm.git:
(bootloader) tz.git:
(bootloader) aboot.git: git = MBM-NG-V41.1A-0-g80481ae
(bootloader) qe:
(bootloader) ro.carrier:
all: listed above
finished Total time: 0.103s
Please can you help me and see how to solve, excuse my english.
Click to expand...
Click to collapse
try factory reset.
I'm trying to keep my problem short. I had unlocked my bootloader for years now and I know the whole subject quite well. I decided to lock my bootloader and put everything back.
Because I was at the official beta of android 9 I decided to flash a factory image of the latest version.
Also the start in the new environment worked out. Therefore I locked the bootloader in the OS and did the same in the bootloader via fastboot.
Now I have a locked bootloader which I cannot unlock due to the os settings.
At boot I get the error: Slot Unbootable: Load Error.
fastboot continue ends in the same error
I don't recover from the same error either.
I cannot change boot slot because of the locked recovery.
fastboot works.
adb sideload not because I only hang in the bootloader.
Do I only have some chance to lock the bootloader or to cause some kind of factory reset?
fastboot getvar all tells me that slot a is unbootable...yeah i know. however b is not. So how can i tell my bootloader to start from B????
I've read a lot now but I'm at a loss. I am grateful for any help or advice.
I hope I don't have to take care of an RMA =(
I hope i missed some way to bypass this locked bootloader. im going crazy
Pleaaaaaase need help =( i spend paypal-beer for help
Here some more infos:
Code:
fastboot getvar all
(bootloader) avb_err:0(0)
(bootloader) is_avb_critical_error:no
(bootloader) have_oem_lock_id:yes
(bootloader) avb_stored_rollback_indexes:
(bootloader) avb_user_settable_key_set:no
(bootloader) avb_version:1.0.0
(bootloader) mid:G011A
(bootloader) version-main:
(bootloader) imei:***censored***
(bootloader) boot-mode:FASTBOOT
(bootloader) logical-block-size:0x1000
(bootloader) erase-block-size:0x1000000
(bootloader) unlocked:no
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4111
(bootloader) version-baseband:g8998-00253-1809191716
(bootloader) version-bootloader:mw8998-002.0073.02
(bootloader) variant:
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xD49BFB000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x1F400000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x1F400000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0xA0000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xA0000000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2000000
(bootloader) has-slot:radio:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) has-slot:vbmeta:yes
(bootloader) has-slot:dtbo:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:6
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) cid:00000000
(bootloader) secure:yes
(bootloader) serialno:FA7C61A00757
(bootloader) hw-revision:MP1
(bootloader) product:walleye
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
all:
finished. total time: 0.090s
Did you ever resolve this? The December update doesn't play well with bootloader enumeration. This thread here should help. As always, there's never a guarantee of data preservation, so unless you have a Titanium Backup, i'd manually backup the really important stuff. Hope it helps!
D3RP_ said:
Did you ever resolve this? The December update doesn't play well with bootloader enumeration. This thread here should help. As always, there's never a guarantee of data preservation, so unless you have a Titanium Backup, i'd manually backup the really important stuff. Hope it helps!
Click to expand...
Click to collapse
Your post wont work for me because i cannot unlock my bootloader as a result of the bricked boot slot. So i cant flash images or flash ota's . But Thanks!!!
I couldn't solve the problem, but I could at least figure out what it is.
Never ever relock the bootloader in the os again until you are 100% sure. In my case i was sure but i didnt recognized that one boot slot is unable to start. that would have been verifiable with fastboot getvar all (see first post).
In the end i am stucked now with a hard bricked phone. I contacted google and at this moment my mobile phone is at google for an RMA. I hope it doesn't take too long.
And yes in my case the December update in combination with my (wrong) relock hard bricked my phone.
Never ever relock the bootloader in the os
Solved for me
I had the same problem with the bootloader locked but I solved it unlocking it "fastboot flashing unlock" then you have flashing the factory image
Camiloecu said:
I had the same problem with the bootloader locked but I solved it unlocking it "fastboot flashing unlock" then you have flashing the factory image
Click to expand...
Click to collapse
If the bootloader shows 'Device State: locked' this command will return an error: 'Flashing Unlock is not allowed'.
Hi i flashed lineage OS 16 to my u11 , problem is now i want to sim unlock it i believe i need to revert back to stock. Ive been trying lots that appear to match but to no avail. Can I sim unlock without going back toorig firmware if not can some point in the direction of a rom , posted getvar below
C:\>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_ocnuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) serialno: HT75K1800461
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 356124080054164
(bootloader) version-main: 2.33.91.7
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711161638
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC10000
(bootloader) cid: EVE__001
all:
finished. total time: 0.009s
C:\>
CorinOB said:
Hi i flashed lineage OS 16 to my u11..........
Click to expand...
Click to collapse
I don't have this device myself but, you should be able to obtain some member guidance within one of the following threads that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=2411840
https://forum.xda-developers.com/showthread.php?t=3619042
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Asking for 2.33.91.7 EE UK rom
did u find it i need it