I'm going nuts here. I use a mac, have had the 6p since preorder (well...since they shipped it) and I haven't had a need for unlocking or rooting (first phone ever to leave it stock) but I've got a few glitches and what not and wanted to flash the newest update released today rather than wait for OTA. Figured a complete wipe can't hurt. unfortunately the fastboot flashing unlock command isn't working. Developer options enabled, OEM unlock tab enabled...usb debugging enabled.....but when I enter ./fastboot flashing unlock this is what I get in terminal (yes mac requires the ./ before any command)
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
Perhaps you have an outdated version? Just a wild guess here but usually if an option is invalid, that's the case.
Sent from my Nexus 6P using Tapatalk
Yep - as @funnel71 said - outdated version.
I unlocked the bootloader on my shiny new 6p yesterday, and initially I got exactly the same result initially. I were doing it on my ubuntu desktop (14.04) at work which has adb installed from packages, which was working perfectly fine with other devices. I manually installed the latest android sdk - and in no time at all I had unlocked and rooted goodness
As others have said, your fastboot package is outdated. You need to install the Android SDK and make sure the platform-tools package is updated.
Thanks. I was thinking that. But it's been so long since I've done that... I got read up again lol
Sent from my Nexus 6P using XDA-Developers mobile app
Updated the SDK. Thanks everyone. It's unlocked now. I knew I was missing something.
Ok, now I'm really getting frustrated. Got the bootloader unlocked, but now I can't flash anything. I've never been able to get the flash-all.sh to work ........ever in the past with my N7, and it's not working here either. Get this message. ./flash-all.sh: line 17: tbfastboot: command not found
./flash-all.sh: line 19: fastboot: command not found
./flash-all.sh: line 20: fastboot: command not found
./flash-all.sh: line 22: fastboot: command not found
When I try to flash the bootloader, radio, or image separately I get this messagem8994f-2.6.31.1.09.img
target reported max download size of 494927872 bytes
sending 'radio' (56758 KB)...
OKAY [ 1.727s]
writing 'radio'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.74yt
318sugarhill said:
Ok, now I'm really getting frustrated. Got the bootloader unlocked, but now I can't flash anything. I've never been able to get the flash-all.sh to work ........ever in the past with my N7, and it's not working here either. Get this message. ./flash-all.sh: line 17: tbfastboot: command not found
./flash-all.sh: line 19: fastboot: command not found
./flash-all.sh: line 20: fastboot: command not found
./flash-all.sh: line 22: fastboot: command not found
When I try to flash the bootloader, radio, or image separately I get this messagem8994f-2.6.31.1.09.img
target reported max download size of 494927872 bytes
sending 'radio' (56758 KB)...
OKAY [ 1.727s]
writing 'radio'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.74yt
Click to expand...
Click to collapse
What is the exact command you're issuing?
318sugarhill said:
Ok, now I'm really getting frustrated. Got the bootloader unlocked, but now I can't flash anything. I've never been able to get the flash-all.sh to work ........ever in the past with my N7, and it's not working here either. Get this message. ./flash-all.sh: line 17: tbfastboot: command not found
./flash-all.sh: line 19: fastboot: command not found
./flash-all.sh: line 20: fastboot: command not found
./flash-all.sh: line 22: fastboot: command not found
When I try to flash the bootloader, radio, or image separately I get this messagem8994f-2.6.31.1.09.img
target reported max download size of 494927872 bytes
sending 'radio' (56758 KB)...
OKAY [ 1.727s]
writing 'radio'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.74yt
Click to expand...
Click to collapse
Have you edited the flash-all.sh script to include a ./ in front of all of the fastboot commands?
./flash-all.sh is what type in and it gives me the error above.
When I tried to flash just the bootloader first I used
./fastboot flash bootloader (bootloader name).img
It gives me this error
target reported max download size of 494927872 bytes
sending 'bootloader' (4387 KB)...
OKAY [ 0.160s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.182s
Same with the radio. I've never had an issue with terminal and flashing on any other phone prior.
Sent from my Nexus 6P using XDA-Developers mobile app
nathanchance said:
Have you edited the flash-all.sh script to include a ./ in front of all of the fastboot commands?
Click to expand...
Click to collapse
yes. nothing works on a mac in terminal for android without the ./ learned that lesson years ago.
318sugarhill said:
yes. nothing works on a mac in terminal for android without the ./ learned that lesson years ago.
Click to expand...
Click to collapse
Have you tried flashing the images manually like in Heisenberg's guide? I hate the flash-all script, it rarely works properly.
nathanchance said:
Have you tried flashing the images manually like in Heisenberg's guide? I hate the flash-all script, it rarely works properly.
Click to expand...
Click to collapse
agree, very hit or miss, personally I flash each file manually. just the best results this way. I also agree that a outdated version of fastboot/you're gonna have a bad time.
nathanchance said:
Have you tried flashing the images manually like in Heisenberg's guide? I hate the flash-all script, it rarely works properly.
Click to expand...
Click to collapse
Yes.....this is what I get
./fastboot flash bootloader (bootloader name).img
It gives me this error
target reported max download size of 494927872 bytes
sending 'bootloader' (4387 KB)...
OKAY [ 0.160s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.182s
Same with the radio. I've never had an issue with terminal and flashing on any other phone prior.
318sugarhill said:
Yes.....this is what I get
./fastboot flash bootloader (bootloader name).img
It gives me this error
target reported max download size of 494927872 bytes
sending 'bootloader' (4387 KB)...
OKAY [ 0.160s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.182s
Same with the radio. I've never had an issue with terminal and flashing on any other phone prior.
Click to expand...
Click to collapse
Did you ever use the following command?
Code:
fastboot erase bootloader
DJBhardwaj said:
Did you ever use the following command?
Code:
fastboot erase bootloader
Click to expand...
Click to collapse
No. I have to erase first? I've never had to with other phones. is that a Nexus thing? I'm hesitant to erase anything without know I can flash something.
318sugarhill said:
No. I have to erase first? I've never had to with other phones. is that a Nexus thing? I'm hesitant to erase anything without know I can flash something.
Click to expand...
Click to collapse
No! Not at all. Was just curious to ask, since your output showed that the partition table doesn't exist.
Never erase the bootloader.
DJBhardwaj said:
No! Not at all. Was just curious to ask, since your output showed that the partition table doesn't exist.
Never erase the bootloader.
Click to expand...
Click to collapse
When I try to flash anything that what I get. Radio, image, bootloader.....i get the remote partition table doesn't exist error. It's beyond frustrating.
318sugarhill said:
When I try to flash anything that what I get. Radio, image, bootloader.....i get the remote partition table doesn't exist error. It's beyond frustrating.
Click to expand...
Click to collapse
Just to confirm, while flashing the bootloader, you are using the exact same command as follows?
Code:
fastboot flash bootloader bootloader-angler-angler-03.51.img
DJBhardwaj said:
Just to confirm, while flashing the bootloader, you are using the exact same command as follows?
Code:
fastboot flash bootloader bootloader-angler-angler-03.51.img
Click to expand...
Click to collapse
yes.....just with a ./ in front. I've shorted the name of the booloader to bootloader.img just to keep the typing down.....but I've tried with the original name too. It's not angler.....it's ......
Holy F..........!!!!!!!!! I downloaded the factory image for the 5X.....it's friggin bullhead! AHHHHHHHHH
Facepalm.
Related
My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 2.526s]
finished. total time: 2.526s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.200s]
finished. total time: 0.200s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.015s]
finished. total time: 0.015s
sending 'bootloader' (2100 KB)...
OKAY [ 0.264s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.402s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
< waiting for device >
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
brad3626 said:
My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Click to expand...
Click to collapse
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
adomol said:
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
Click to expand...
Click to collapse
Thank you for the help, unfortunately, it did not work.
I followed the instructions above, but the Nexus displayed "neither up nor cac partitions found" over and over
While cmd displayed:
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.281s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.213s
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.205s
Erovia said:
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
Click to expand...
Click to collapse
Wi-Fi
I have tried every one that the NRT offered.
Just read this guide and download the latest factory image from here.
Good luck.
Erovia said:
Just read this guide and download the latest factory image from here.
Good luck.
Click to expand...
Click to collapse
I read that guide.
But that guide seems to be written with the assumption that the device can boot into the OS
No ADB device is found because I can only boot into bootloader.
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Erovia said:
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Click to expand...
Click to collapse
Following from "Extract the Factory Image" part, this is what I am getting:
C:\Users\Brad>cd \Users\brad\AppData\Local\Android\android-sdk\platform-tools
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
XXX fastboot
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>adb reboot-bootlo
ader
error: device not found
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlo
ck
...
FAILED (command write failed (Unknown error))
finished. total time: 0.590s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase bo
ot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase ca
che
erasing 'cache'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase re
covery
erasing 'recovery'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.022s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase sy
stem
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase us
erdata
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.018s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot flash bo
otloader bootloader-grouper-4.23.img
error: cannot load 'bootloader-grouper-4.23.img': Invalid argument
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Erovia said:
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Click to expand...
Click to collapse
lock state - unlocked
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Erovia said:
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Click to expand...
Click to collapse
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
error: out of memory
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Erovia said:
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Click to expand...
Click to collapse
I restarted, ran cmd as admin and tried every USB port and got this as the result each time:
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: XXX
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4992 KB)...
OKAY [ 5.460s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 8.518s
The Nexus was frozen at this point and had to be manually forced to restart bootloader.
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Erovia said:
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Click to expand...
Click to collapse
Thanks for your help
I bought it 13 months ago (perfect timing, coincidentally, right?), so if I could find the receipt I would still be screwed.
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Erovia said:
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Click to expand...
Click to collapse
fastboot oem lock
...
(bootloader) Bootloader is locked now.
OKAY [ 36.032s]
finished. total time: 36.032s
But then the N7 freezes and after manually restarting in bootloader it is still unlocked.
Then send is as it is. You can't do any more about it.
Good luck.
looks like yet another ota update for the hd6 was released today
kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.4_user_454006120.bin
if you havent already disabled ota updates i suggest doing so now
thanks for the info
can anyone confirm whether or not the latest KingRoot works with v4.5.4 as well?
HamishAhern said:
can anyone confirm whether or not the latest KingRoot works with v4.5.4 as well?
Click to expand...
Click to collapse
You need to unlock your bootloader & flash twrp and boot in to it, then reboot to system and it says Flash SuperSu?
Root Voila.
meganoahj said:
You need to unlock your bootloader & flash twrp and boot in to it, then reboot to system and it says Flash SuperSu?
Root Voila.
Click to expand...
Click to collapse
And how do you flash twrp without root ? You need to be in 5.4.3 where you have root, and can proceed further.
bibikalka said:
And how do you flash twrp without root ? You need to be in 5.4.3 where you have root, and can proceed further.
Click to expand...
Click to collapse
Sorry i forgot that you need root for flashing recovery
i think that you need to downgrade to 4.5.3 (Later available)
or reboot to bootloader (adb reboot-bootloader) and
try (After Bootloader Unlock): fastboot flash recovery recovery.img
or when its not work try: fastboot -i 0x1949 flash recovery recovery.img
meganoahj said:
or reboot to bootloader (adb reboot-bootloader) and
try (After Bootloader Unlock): fastboot flash recovery recovery.img
or when its not work try: fastboot -i 0x1949 flash recovery recovery.img
Click to expand...
Click to collapse
I tried your commands but they both fail: FAILED (remote: flashing not allowed for locked hw)
devicer said:
I tried your commands but they both fail: FAILED (remote: flashing not allowed for locked hw)
Click to expand...
Click to collapse
You need to unlock your bootloader
meganoahj said:
You need to unlock your bootloader
Click to expand...
Click to collapse
Well, I did it, or I think so:
Code:
[[email protected] /tmp]$ adb shell cat /sys/block/mmcblk0/device/manfid
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0x0000XX
[[email protected] /tmp]$ adb shell cat /sys/block/mmcblk0/device/serial
0xSSSSSSSS
[[email protected] /tmp]$ python2 cublock.py XX SSSSSSSS
Your unlock code is in 'unlock.img'.
[[email protected] /tmp]$ adb reboot-bootloader
[[email protected] /tmp]$ fastboot -i 0x1949 flash unlock unlock.img
target reported max download size of 52429824 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.036s]
writing 'unlock'...
OKAY [ 0.089s]
finished. total time: 0.125s
[[email protected] /tmp]$ fastboot reboot
rebooting...
[[email protected] /tmp]$ adb reboot-bootloader
[[email protected] /tmp]$ fastboot flash recovery openrecovery-twrp-2.8.6.0-ariel.img
target reported max download size of 52429824 bytes
sending 'recovery' (7002 KB)...
OKAY [ 0.295s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.318s
[[email protected] /tmp]$ fastboot -i 0x1949 flash recovery openrecovery-twrp-2.8.6.0-ariel.img
target reported max download size of 52429824 bytes
sending 'recovery' (7002 KB)...
OKAY [ 0.297s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.321s
[[email protected] /tmp]$ fastboot reboot
rebooting...
devicer said:
Well, I did it, or I think so:
Code:
[[email protected] /tmp]$ adb shell cat /sys/block/mmcblk0/device/manfid
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0x0000XX
[[email protected] /tmp]$ adb shell cat /sys/block/mmcblk0/device/serial
0xSSSSSSSS
[[email protected] /tmp]$ python2 cublock.py XX SSSSSSSS
Your unlock code is in 'unlock.img'.
[[email protected] /tmp]$ adb reboot-bootloader
[[email protected] /tmp]$ fastboot -i 0x1949 flash unlock unlock.img
target reported max download size of 52429824 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.036s]
writing 'unlock'...
OKAY [ 0.089s]
finished. total time: 0.125s
[[email protected] /tmp]$ fastboot reboot
rebooting...
[[email protected] /tmp]$ adb reboot-bootloader
[[email protected] /tmp]$ fastboot flash recovery openrecovery-twrp-2.8.6.0-ariel.img
target reported max download size of 52429824 bytes
sending 'recovery' (7002 KB)...
OKAY [ 0.295s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.318s
[[email protected] /tmp]$ fastboot -i 0x1949 flash recovery openrecovery-twrp-2.8.6.0-ariel.img
target reported max download size of 52429824 bytes
sending 'recovery' (7002 KB)...
OKAY [ 0.297s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.321s
[[email protected] /tmp]$ fastboot reboot
rebooting...
Click to expand...
Click to collapse
Ok i think you need to downgrade, ask amazon for rollback like “my device have problems with fire os 4.5.4“, or wait for method for downgrade
Or try fastboot boot recovery.img then flash your recovery with twrp
devicer said:
Well, I did it, or I think so:
Code:
[[email protected] /tmp]$
[[email protected] /tmp]$ fastboot flash recovery openrecovery-twrp-2.8.6.0-ariel.img
target reported max download size of 52429824 bytes
sending 'recovery' (7002 KB)...
OKAY [ 0.295s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.318s
[[email protected] /tmp]$ fastboot -i 0x1949 flash recovery openrecovery-twrp-2.8.6.0-ariel.img
target reported max download size of 52429824 bytes
sending 'recovery' (7002 KB)...
OKAY [ 0.297s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.321s
[[email protected] /tmp]$ fastboot reboot
rebooting...
Click to expand...
Click to collapse
How about you run the command to check if you have unlocked your bootloader :
adb shell
su
idme print
You should now see unlock_code: AAAAAAAA and on and on.
bibikalka said:
How about you run the command to check if you have unlocked your bootloader :
adb shell
su
idme print
You should now see unlock_code: AAAAAAAA and on and on.
Click to expand...
Click to collapse
Maybe you missed the part when I say that the Fire is at version 4.5.4, un-rooted...
devicer said:
Maybe you missed the part when I say that the Fire is at version 4.5.4, un-rooted...
Click to expand...
Click to collapse
Yes, looks like you are SOL !
Between 4.5.3 (Feb) and 4.5.4 (May) Amazon prob fixed the issue of the bootloader unlock, as well as the root exploit.
Call Amazon and beg them to downgrade you to 4.5.3 !
On the other hand, with rooted and unlocked 4.5.3 one should be able to update to 4.5.4, and keep root and unlock (after the update file is patched properly !).
bibikalka said:
On the other hand, with rooted and unlocked 4.5.3 one should be able to update to 4.5.4, and keep root and unlock (after the update file is patched properly !).
Click to expand...
Click to collapse
Bibikalka--Can you elaborate on patching the file and updating to 4.5.4? You haven't tried this yet? thx
DoLooper said:
Bibikalka--Can you elaborate on patching the file and updating to 4.5.4? You haven't tried this yet? thx
Click to expand...
Click to collapse
No, I have not tried this. I started looking at the upHDX script from here :
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
But then real work and life got in the way Basically, in the update script one should disable writing to 3 places, recovery, UBOOT, and TEE1, and also delete those images (just to be sure).
$ grep by-name 20-4.5.3/META-INF/com/google/android/updater-script
...
package_extract_file("boot.img", "/dev/block/platform/mtk-msdc.0/by-name/boot");
package_extract_file("images/lk.bin", "/dev/block/platform/mtk-msdc.0/by-name/UBOOT");
package_extract_file("images/tz.img", "/dev/block/platform/mtk-msdc.0/by-name/TEE1");
upHDX covers most of this, but not all. Also, upHDX updates kernel for HDX and signs it. For now I want to extract the existing boot.img for 4.5.3, compare to the one from the update, create a package to write 4.5.3 kernel via TWRP, and make sure that I can recover to a working kernel. Then I'll play with the actual updating.
When click the power button i launch on screen with the Fastboot Flash Mode. I tried all the options but nothing happens.
Select Normal Powerup then also nothing happens.
Select Factory nothing happens. I am stuck on fastboot when starting phone.
I tried to flash factory images and install again using steps mentioned by moto but receive error when below command is entered:
fastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.095s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.266s
On mobile i see this:
cmd: getvar;partion-type;partion
cmd: getvar:max-download-size
cmd: download:0008000
cmd: flash;partition
hab check failed for primary_gpt
Failed to verify hab image primary.gpt
When doing motoboot.img I get this:
fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2022 KB)...
OKAY [ 0.115s]
writing 'motoboot'...
(bootloader) Motoboot;Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
on mobile I see this:
cmd: getvar;partion-type:motoboot
cmd: getvar:max-download-size
cmd: download:001f9a00
cmd: flash:motoboot
Mismatched partition size (tz)
If you have any information about this please do in the quickest way possible.
What factory images? Are you unlocked?
lafester said:
What factory images? Are you unlocked?
Click to expand...
Click to collapse
I ment the Flash stoke images when using the bootloader thing
ymx75 said:
I ment the Flash stoke images when using the bootloader thing
Click to expand...
Click to collapse
ignore that one. I ment to say the Flash images when using the bootloader and yes I am unlocked
I would download the return to stock zip and run flash all .bat. Then use twrp to make a backup so you don't have to do this again.
lafester said:
I would download the return to stock zip and run flash all .bat. Then use twrp to make a backup so you don't have to do this again.
Click to expand...
Click to collapse
thanks for the info. the thing is, I feel stupid, but I deleted the zip and can't remember wat website I got it from. if you could help me find it, it would mean the world to me
ymx75 said:
thanks for the info. the thing is, I feel stupid, but I deleted the zip and can't remember wat website I got it from. if you could help me find it, it would mean the world to me
Click to expand...
Click to collapse
Here is the thread with the "return to stock" zip file.
ymx75 said:
thanks for the info. the thing is, I feel stupid, but I deleted the zip and can't remember wat website I got it from. if you could help me find it, it would mean the world to me
Click to expand...
Click to collapse
Under Android development or original development
Sent from my XT1575 using Tapatalk
So I've been encountering this problem whenever I'm trying to do anything to the Modem Partitions on the Essential Phone:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
PM1LHMA7C1303309 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
FAILED (remote: Flashing is not allowed for Modem Partitions
)
finished. total time: 0.032s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modemst1 modemst1.img
target reported max download size of 536870912 bytes
sending 'modemst1' (2048 KB)...
OKAY [ 0.765s]
writing 'modemst1'...
FAILED (remote: Flashing is not allowed for Modem Partitions
)
finished. total time: 0.794s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
FAILED (remote: Flashing is not allowed for Modem Partitions
)
finished. total time: 0.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modemst2 modemst2.img
target reported max download size of 536870912 bytes
sending 'modemst2' (2048 KB)...
OKAY [ 0.168s]
writing 'modemst2'...
FAILED (remote: Flashing is not allowed for Modem Partitions
)
finished. total time: 0.240s
And... flashing the img file using
Code:
fastboot flash modem_a or modem_b
didn't provide the result I wanted.
If anyone have some inputs would be really appreciated. Thanks...
Did you unlock critical? I don't remember the exact commands but it's similar to unlocking the bootloader.
gk1984 said:
Did you unlock critical? I don't remember the exact commands but it's similar to unlocking the bootloader.
Click to expand...
Click to collapse
I did. I've done both
Code:
fastboot flashing unlock
and
Code:
fastboot flashing unlock_critical
I'll be trying to flash older essential fastboot.img(s) to see wether that would change anything. Because from the r/essential on reddit, people actually were able to flash onto the modemst partitions.
reddit*com/r/essential/comments/9e9to8/invalid_sim_network_locked_fix_for_the_september/
I was doing the automatic steps, but the phone literally doesn't respond to .bat file provided. So I tried doing it manually, and it was when I hit this partition problem.
If it's not asking to much, would someone confirm wether or not flashing onto this partition is possible? Thanks
You must unlock and downgrade bootloader (old android 7 rom) on last android 7 and 8,9 roms you cannot flash modemst part bcs security patches
flash NMK24B factory image first and after unlock_critical you can flash modemst parts
download rom from here https://www.essential.com/developer/current-builds
and after flash modemst parts you can flash android 8.1 rom and check if is it unlocked bcs after flash modemst parts phone stay in locked state on android 7
veisen said:
You must unlock and downgrade bootloader (old android 7 rom) on last android 7 and 8,9 roms you cannot flash modemst part bcs security patches
flash NMK24B factory image first and after unlock_critical you can flash modemst parts
download rom from here essential*com/developer/current-builds
and after flash modemst parts you can flash android 8.1 rom and check if is it unlocked bcs after flash modemst parts phone stay in locked state on android 7
Click to expand...
Click to collapse
So I've been trying to flash the NMK24B, I hadn't been successful these previous days, but I found a trick from this youtube video;
youtube*com/watch?v=RrMLqSXcxjI
So I'll proceed to flash the modemst partitions, and give you guys update.
Phone is Sim Unocked Now
So this is the manual process to do all this, if your phone isn't responding to the automatic procedure according to https://www*reddit*com/r/essential/comments/9e9to8/invalid_sim_network_locked_fix_for_the_september/.
Flash NMK24B on fastboot by running flashall.bat. If it's not sending package to the phone, then install Minimal ADB and copy fastboot.exe from Minimal ADB directory to NMK24B directory, the run the flashall.bat.
After the above procedure you will boot into adroid, re-enable usb debugging, then go to fastboot again. Open cmd from Minimal ADB and flash modemst, which you can find from reddit post above on Essential Unlock>Data>Modemst:
Code:
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
Resources are from the reddit post above. Credits goes to the creator of this trick (in which I do not know who).
Need your help. I just accidently selected radioband USA settings on my htc one m8. Now the network is completely gone. I saw on the internet to erase my modemst1 and modemst2 using fastboot. But it says that "failed (remote:not allowed). What does this mean? And how it'll allow me?
---------- Post added at 09:49 AM ---------- Previous post was at 09:45 AM ----------
Khan97bilal said:
Need your help. I just accidently selected radioband USA settings on my htc one m8. Now the network is completely gone. I saw on the internet to erase my modemst1 and modemst2 using fastboot. But it says that "failed (remote:not allowed). What does this mean? And how it'll allow me?
Click to expand...
Click to collapse
I also have s off. Bootloader unlocked. And device rooted.
Hi All,
I am trying to flash Android TV 13 beta 4 ~ to the developer tools adt-3. After flash ... the adt-3 keep reboot. And cna't load the bootloader and OS. when I try to flash the device again ... adt-3 said that FAILED (remote: 'locked device').
I would like to know how to unlock adt-3 !?
ToTo
./fastboot flashing unlock
FAILED (remote: 'unlock_ability is 0, can not unlock')
./fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 0
OKAY [ 0.049s]
Finished. Total time: 0.050s
sudo ./flash-all.sh
[sudo] password for toto:
error: no devices/emulators found
FAILED (remote: 'unlock_ability is 0, can not unlock')
fastboot: error: Command failed
FAILED (remote: 'locked device')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.258s
FAILED (remote: 'unlock_ability is 0, can not unlock')
fastboot: error: Command failed
******** Did you mean to fastboot format this ext4 partition?
Erasing 'data' FAILED (remote: 'locked device')
fastboot: error: Command failed
Sending 'bootloader' (1591 KB) FAILED (remote: 'locked device')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.258s
--------------------------------------------
Bootloader Version...: 01.01.220621.133524
Baseband Version.....: N/A
Serial Number........: ACHE0000xxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.015s]
Checking 'version-bootloader' OKAY [ 0.014s]
extracting boot.img (16 MB) to disk... took 0.031s
archive does not contain 'boot.sig'
Sending 'boot' (16384 KB) FAILED (remote: 'locked device')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.258s
OKAY [ 0.023s]
Finished. Total time: 0.023s
Rebooting OKAY [ 0.003s]
Finished. Total time: 0.305s
Need help to unlock adt-3
fastboot oem 'setenv lock 10101000;save'
fastboot reboot bootloader
fastboot flashing unlock
Many thanks, I using adt-3. I think oem not working ... many thanks. Here is the result.
./fastboot oem 'setenv lock 10101000;save'
FAILED (remote: 'locked device')
fastboot: error: Command failed
./fastboot flashing unlock
FAILED (remote: 'unlock_ability is 0, can not unlock')
fastboot: error: Command failed
That is the command that is within flash-all.sh for build adt3_gtv-stt1.211025.001.z3-factory-91f7efe7.
It was designed specifically to fix this particular issue/bug with the adt-3.
This problem started before android 12. Read article;
[Update: Fixed] Android TV 12 preview builds for ADT-3 can't be flashed
The first builds of Android TV 12 for Google's own ADT-3 developer device are completely broken, leaving developers unable to install them.
9to5google.com
Yes, I know ... I also go through that issue when I did Android TV 12. Right now I have the issue again. When I was doing Android TV 13 beta 4. Here flash-all.sh come with Android TV 13 beta 4.
if ! [ $($(which ./fastboot) --version | grep "version" | cut -c18-23 | sed 's/\.//g' ) -ge 2802 ]; then
echo "fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"
exit 1
fi
./adb reboot bootloader || true
if ! ./fastboot flashing unlock ; then
./fastboot oem 'setenv lock 10101000;save' || true
./fastboot reboot bootloader; sleep 3
./fastboot flashing unlock || true
fi
./fastboot erase data
./fastboot flash bootloader bootloader-adt3_gtv-01.01.220621.133524.img
./fastboot reboot bootloader; sleep 3
./fastboot -w --skip-reboot update image-adt3_gtv-trb4.220715.005.zip
./fastboot reboot bootloader; sleep 3
./fastboot flashing lock
./fastboot reboot
But this time ... it is not working
Are you sure that your fastboot version/drivers are new/good?
Within a few days I will try to update mine, in order to see if there are any issues.
Are you familiar with worldcup burn mode?
Obtain worldcup drivers and command line "update" program for your OS.
Once worldcup drivers are installed, hold button, starting from before power is applied, until you have a worldcup usb connection. Then run these commands using the "update" program for worldcup;
update bulkcmd "setenv lock 10100000"
update bulkcmd "saveenv"
Then reboot and see if fastboot works.
./fastboot --version
fastboot version 33.0.3-8952118
Installed as /opt/platform-tools/fastboot
I just upgrade it b4 I do the Android TV 13 Beta 4.
Sorry ... I have no idea of "worldcup burn mode"
Latest Update: The final release of Android 13 for TV is now available.
ADT-3 (Android TV)ADT3-TTT1.220909.001.B7-FACTORY-CA1F5F01.ZIP
ADT-3 (Google TV)ADT3_GTV-TTT1.220909.001.B7-FACTORY-36544A4B.ZIP
but this release ... still no help for the locked adt-3
ToToHayashi said:
Latest Update: The final release of Android 13 for TV is now available.
ADT-3 (Android TV)ADT3-TTT1.220909.001.B7-FACTORY-CA1F5F01.ZIP
ADT-3 (Google TV)ADT3_GTV-TTT1.220909.001.B7-FACTORY-36544A4B.ZIP
but this release ... still no help for the locked adt-3
Click to expand...
Click to collapse
Did you try the update method as suggested by "Deleted member 11959327" ?
To get the tool i recommend the Khadas Git (khadas/utils) then the aml-flash-tool/ is the folder with Amlogic tools
for the update tool its in tools/linux-x86/update