hey guys
I do some wrong
I try to factory reset on my n9 and after this everthing goes wrong
my bootloader is locked and I can't unlock it
if I try I get (bootloader) Permission denied for this command!
and my n9 stuck in a bootloop
c:\android-sdk-windows\platform-tools>fastboot oem unlock
< waiting for device >
...
(bootloader) ability is 0
(bootloader) Permission denied for this command!
OKAY [ -0.000s]
finished. total time: -0.000s
Checking Bootloader Lock State + Tamper Flag:
---------------------------------------------
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.007s
Click to expand...
Click to collapse
I try to flash the bootloader from bootloader-flounder-3.43.0.0114.img and this dont work after this I try to flash the bootloader
bootloader-hammerhead-hhz12d.img but this also not work -.-
now I have no system on my n9 no recovery on it
someone has a idea what I can do?
In fastboot try,
fastboot format cache
fastboot format userdata
Sent from my Nexus 9 using XDA Free mobile app
fastboot format cache I get this
Code:
C:\WINDOWS\system32>fastboot format cache
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
target reported max download size of 518205818 bytes
erasing 'cache'...
(bootloader) Device State : Locked
FAILED (remote: Can not erase any partition while device state is locked!)
finished. total time: 0.157s
and by fastboot format userdata
Code:
C:\WINDOWS\system32>fastboot format userdata
Formatting is not supported for filesystem with type 'f2fs'.
Try holding the volume down button, booting into Fastboot, then running WugFresh Nexus Root Toolkit http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451 with 'Flash Stock/Unroot' and 'Soft-bricked/bootload'' option then in the next window '5.0.2 Android' and 'Force Flash Mode'
Can't promise it'll work but worth a try.
@kedarrWolf I tryed your way but it dosn'T work
Code:
target reported max download size of 518205818 bytes
erasing 'system'...
(bootloader) Device State : Locked
FAILED (remote: Can not erase any partition while device state is locked!)
finished. total time: 0.141s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
Hello, I need help.
I have a Nexus 9 Wifi 16gb black. It was a gift from Google in USA, but I live in Uruguay.
THe problem is:
Yesterday I tried to install Android M (with unlocked bootloader).
Then, installed supersu..
After rebooted I was seeing "Your device is corrupt." and a bootloop.
So, I locked the bootloader, maybe that was the cause of bootloop (ofc no. I figured out it wasnt....)
And I can't do anythig, I can't access to Android to enable the oem unlock option.
I don't have a custom recovery..
I entered in "oem verified" mode, and was able to format userdata/cache partitions. But still the problem...
Here is what I've been trying to do
Code:
[email protected]:~/Descargas$ fastboot oem unlock
...
(bootloader) ability is 0
(bootloader) Permission denied for this command!
OKAY [ 0.007s]
finished. total time: 0.007s
[email protected]:~/Descargas$ fastboot flash recovery twrp-2.8.7.0-flounder.img
target reported max download size of 518205818 bytes
sending 'recovery' (13320 KB)...
OKAY [ 1.022s]
writing 'recovery'...
(bootloader) Device State : Locked
FAILED (remote: Can not flash any images while device state is locked!)
finished. total time: 1.161s
[email protected]:~/Descargas$ fastboot oem verified
...
(bootloader) Start Verify: 0
(bootloader) [hboot query] query 24 is not implemented
(bootloader) [hboot query] query 24 is not implemented
(bootloader) Start Verify: 0
(bootloader) [hboot query] query 24 is not implemented
(bootloader) [hboot query] query 24 is not implemented
(bootloader) Device is in veified state!
OKAY [ 2.600s]
finished. total time: 2.600s
[email protected]:~/Descargas$ fastboot flash recovery twrp-2.8.7.0-flounder.img
target reported max download size of 518205818 bytes
sending 'recovery' (13320 KB)...
OKAY [ 1.017s]
writing 'recovery'...
(bootloader) Device State : Verified
FAILED (status read failed (Value too large for defined data type))
finished. total time: 6.447s
[email protected]:~/Descargas$ fastboot format userdat
Formatting is not supported for filesystem with type ''.
[email protected]:~/Descargas$ fastboot format userdata
Cannot generate image.
erasing 'userdata'...
OKAY [ 2.415s]
finished. total time: 2.415s
[email protected]:~/Descargas$ fastboot format cache
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
target reported max download size of 518205818 bytes
erasing 'cache'...
OKAY [ 0.463s]
sending 'cache' (6248 KB)...
OKAY [ 0.482s]
writing 'cache'...
(bootloader) Device State : Verified
OKAY [ 0.637s]
finished. total time: 1.583s
[email protected]:~/Descargas$
:-/
And stil the problem.
Can someone help me?
-Sorry for my bad english-
Greetings
If no way, how to contact Google for reparation? Is there any email?
You should not have relocked bootloader. It needs to be unlocked to do anything if it will not boot. "Enable oem unlock" must be checked.
Hey I wanted to restore my OPX back to the OxygenOS and the stock recovery. I Somehow ****ed up and now only fastboot is booting.
Here is the fastboot log:
Code:
C:\Users\Fifi\Downloads>fastboot devices
5c9c4816 fastboot
C:\Users\Fifi\Downloads>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\Fifi\Downloads>fastboot format cache
erasing 'cache'...
OKAY [ 0.047s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
sending 'cache' (10432 KB)...
writing 'cache'...
OKAY [ 0.641s]
finished. total time: 0.688s
C:\Users\Fifi\Downloads>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Fifi\Downloads>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.297s]
finished. total time: 0.828s
C:\Users\Fifi\Downloads>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\Fifi\Downloads>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.578s
I hope you can help. Thanks
Use this command in fastboot.
Fastboot boot recovery recovery.img
Sent from my XT1022 using Tapatalk
That gives me the same Error:
FAILED (remote: dtb not found)
I found that the Error often comes up when the recovery.img is corrupted or wrong.
I tried a lot of different download for different OPX recoverys, all the same error.
I tried to re lock and to re unlock the bootloader. First worked, the unlock did not. So i cant accsess the phone at all.
Ill close this thread and send the phone to Oneplus.
EDIT... Dont know how to close this.
Well yeah that error usually ocuurs when the recovery file is corrupted or is for a different device.
You can try to flash stock recovery once.
Sent from my XT1022 using Tapatalk
Struck at 1+ logo
Hello developers,
I have rooted OPX and stock rom.
I am struck at 1+ logo after rebooting,
tried flashing recovery again since the recovery.img I just flashed is not working,
Device bootloader not unlocked and I cannot unlock it as phones gets struck at 1+ logo.
Please Help friends....
Hi guys,
I just got a Zenwatch 2 WI501Q Sparrow,
I had some issues with calls on my phone and decided to update the firmware, but something went wrong during the flashing.
After that, the watch will keep rebooting every 10 seconds, unless i swipe to get into Fastboot mode.
Fastboot works and i can send commands from prompt, but whenever i try to unlock it, in order to be able to reflash, the unlock screen does not respond to pressing the button.
I know the button is working, because it was working before flashing, and holding it for 9 seconds turrns the watch off, but at the lock screen, there´s no effect in pressing it, short or long press, unles is long enough to turn off, but in that case, when reboot, it remains locked.
In this scenario, is there anything that i could try to recover my watch? Or did I killed the poor little guy?
Image that failed to flash was "Google-sparrow-img-M6E69Z-signed", but i also have files of "Google-sparrow-img-LCA49B-signed" ans factory image "Factory_V4_15_1_19_sparrow-eng_20151222"
Use the fastboot image provided here if you ever get it working: https://forum.xda-developers.com/zenwatch-2/general/dump-zenwatch-2-sparrow-wi501q-build-t3601596
Also I don't even recall that it asks for a button press tho the last time I unlocked mine was about 7 months ago haha Can you take a photo and upload it? Maybe I can help.
EpicLPer said:
Use the fastboot image provided here if you ever get it working: https://forum.xda-developers.com/zenwatch-2/general/dump-zenwatch-2-sparrow-wi501q-build-t3601596
Also I don't even recall that it asks for a button press tho the last time I unlocked mine was about 7 months ago haha Can you take a photo and upload it? Maybe I can help.
Click to expand...
Click to collapse
When I use the command [fastboot oem unlock], the device goes to the following screen:
{
"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"
}
That´s where i get stuck, because it should unlock by long pressing the button, but nothing is happening here.
Like I said, no image can be flashed due to the LOCKED state.
Is there any way to make the device select the Unlock option, by sending some command from console?
For the system image, as I said before, I have ASUS original firmware files
"Google-sparrow-img-M6E69Z-signed"
"Google-sparrow-img-LCA49B-signed"
"Factory_V4_15_1_19_sparrow-eng_20151222"
You may check all from the link below:
https://drive.google.com/drive/folders/0B2Ru4ATp1lY0cXhhTnpsVHF0bkU
Any help on this will be welcome.
JoseBatista said:
When I use the command [fastboot oem unlock], the device goes to the following screen:
That´s where i get stuck, because it should unlock by long pressing the button, but nothing is happening here.
Like I said, no image can be flashed due to the LOCKED state.
Is there any way to make the device select the Unlock option, by sending some command from console?
For the system image, as I said before, I have ASUS original firmware files
"Google-sparrow-img-M6E69Z-signed"
"Google-sparrow-img-LCA49B-signed"
"Factory_V4_15_1_19_sparrow-eng_20151222"
You may check all from the link below:
https://drive.google.com/drive/folders/0B2Ru4ATp1lY0cXhhTnpsVHF0bkU
Any help on this will be welcome.
Click to expand...
Click to collapse
That is super weird...
Maybe try "fastboot -w" to format all userdata on the watch, last bet. And then update the watch the normal way, maybe they fixed something in the bootloader for later versions.
EpicLPer said:
That is super weird...
Maybe try "fastboot -w" to format all userdata on the watch, last bet. And then update the watch the normal way, maybe they fixed something in the bootloader for later versions.
Click to expand...
Click to collapse
Nothing.
[fastboot -w] requires the device to be unlocked first.
The command gisves me the following:
Creating filesystem with parameters:
Size: 2759831552
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 10527
Label:
Blocks: 673787
Block groups: 21
Reserved block group size: 167
Created filesystem with 11/168672 inodes and 22128/673787 blocks
target reported max download size of 63963136 bytes
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
erasing 'userdata'...
(bootloader) Device is locked.
(bootloader) Please unlock device first!
FAILED (remote failure)
finished. total time: 0.011s
I also have tried
[fastboot flash bootloader bootloader.img]
[fastboot flash recovery recovery.img]
[fastboot flash system system.img]
[fastboot flash boot boot.img]
Any flash commands require unlock in order to work.
I did [fastboot oem device-info] and that´s the info that came up:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Debug Uart Disabled!
(bootloader) ASUS Dongle authorized: false
(bootloader) Sparrow
(bootloader) APQ_8026 - V1
(bootloader) eMMC=HYNIX-4G-1-748000
(bootloader) CPU_RV=108040e1
(bootloader) SB=Y
OKAY [ 0.020s]
finished. total time: 0.021s
I´m reaching the conclusion that what I would need is some way to command the unlock straight from the console, without having to confirm in the device.
If there´s no such command, nor any workaround to this, then i´m thinking I may be fully dead.
JoseBatista said:
Nothing.
[fastboot -w] requires the device to be unlocked first.
The command gisves me the following:
Creating filesystem with parameters:
Size: 2759831552
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 10527
Label:
Blocks: 673787
Block groups: 21
Reserved block group size: 167
Created filesystem with 11/168672 inodes and 22128/673787 blocks
target reported max download size of 63963136 bytes
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
erasing 'userdata'...
(bootloader) Device is locked.
(bootloader) Please unlock device first!
FAILED (remote failure)
finished. total time: 0.011s
I also have tried
[fastboot flash bootloader bootloader.img]
[fastboot flash recovery recovery.img]
[fastboot flash system system.img]
[fastboot flash boot boot.img]
Any flash commands require unlock in order to work.
I did [fastboot oem device-info] and that´s the info that came up:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Debug Uart Disabled!
(bootloader) ASUS Dongle authorized: false
(bootloader) Sparrow
(bootloader) APQ_8026 - V1
(bootloader) eMMC=HYNIX-4G-1-748000
(bootloader) CPU_RV=108040e1
(bootloader) SB=Y
OKAY [ 0.020s]
finished. total time: 0.021s
I´m reaching the conclusion that what I would need is some way to command the unlock straight from the console, without having to confirm in the device.
If there´s no such command, nor any workaround to this, then i´m thinking I may be fully dead.
Click to expand...
Click to collapse
Even "fastboot format userdata" won't work? I never thought they'd be locked down when the bootloader is locked...
Can you try to boot up TWRP via "fastboot boot TWRP...img"? Should be somewhere in the Original Android Development section here. I know for a fact that you can boot TWRP while locked since I did it and tried to make an image from partitions which f*cked them up then lol... managed to recover tho
Anyways, try that and in TWRP choose to wipe the data then.
Phone started to loop through booting, crashes at different points of booting. Preformed a wipe data/factory reset and is doing the same loop though booting. Last ditch effort i want to try flashing but looks like i can't as it's locked any ideas?
error = FAILED (remote: device is locked. Cannot flash images)
bullhead LGH791 16GB
HW Version - rev_1.0
Bootloader version BHZ11m
Baseband Version - M8994F-2.6.37.2.21
Carrier info - N/A
Signing - production
Secure boot - enabled
Device - State - locked
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'bootloader' (4616 KB)...
OKAY [ 0.180s]
writing 'bootloader'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.210s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio' (56630 KB)...
OKAY [ 1.300s]
writing 'radio'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.330s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 11773390848
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 2874363
Block groups: 88
Reserved block group size: 703
Created filesystem with 11/719488 inodes and 84965/2874363 blocks
wiping cache...
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
--------------------------------------------
Bootloader Version...: BHZ11m
Baseband Version.....: M8994F-2.6.37.2.21
Serial Number........: 00bf02fa89e421b5
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.010s]
checking version-baseband...
OKAY [ 0.010s]
sending 'boot' (12045 KB)...
OKAY [ 0.341s]
writing 'boot'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.501s
Press any key to exit...