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
Related
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,
How I bricked my phone:
I tried to flash the stock recovery because I wasn't able to flash any firmware upgrade using OxygenOS 2.2.3 and TWRP-3-0-2.
To do so I enabled USB-debugging and checked unlock OEM in the developer options and restarted the phone into fastboot mode.
Then I tried to flash the stock recovery:
Code:
~/oneplus » sudo fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.464s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.465s
The bootloader should have been unlocked already at this point but I tried to unlock it anyway:
Code:
~/oneplus » sudo fastboot oem unlock
...
OKAY [ 0.011s]
finished. total time: 0.011s
The phone rebooted and was stuck in the oneplus logo screen.
trying to boot into recovery mode (turn the phone off and restart pressing volume down) as well as 'fastboot reboot' and 'fastboot continue' produced the same results.
Using fastboot reboot bootloader brings the device back into fastboot mode.
'fastboot oem device-info' reveals:
Code:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
I also tried to erase cache and data but apparently I'm not allowed to touch the partitions in any way.
Code:
~/oneplus » sudo fastboot -w
wiping userdata...
Creating filesystem with parameters:
Size: 12611891200
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3079075
Block groups: 94
Reserved block group size: 751
Created filesystem with 11/770048 inodes and 88617/3079075 blocks
target reported max download size of 1073741824 bytes
wiping cache...
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
erasing 'userdata'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.000s
It seems to me that the key of resolving this problem is to somehow unlock the bootloader. Can you think of any way to do this?
Is it possible to flash anything without successfully unlocking the bootloader?
Any other suggestions?
Kind Regards
Malte
Mega Unbrick guide here.
Solved
Thank you. I thought I could avoid that but it works pretty flawless. :good:
xda-acc said:
Hi guys,
How I bricked my phone:
I tried to flash the stock recovery because I wasn't able to flash any firmware upgrade using OxygenOS 2.2.3 and TWRP-3-0-2.
To do so I enabled USB-debugging and checked unlock OEM in the developer options and restarted the phone into fastboot mode.
Then I tried to flash the stock recovery:
The bootloader should have been unlocked already at this point but I tried to unlock it anyway:
The phone rebooted and was stuck in the oneplus logo screen.
trying to boot into recovery mode (turn the phone off and restart pressing volume down) as well as 'fastboot reboot' and 'fastboot continue' produced the same results.
Using fastboot reboot bootloader brings the device back into fastboot mode.
'fastboot oem device-info' reveals:
I also tried to erase cache and data but apparently I'm not allowed to touch the partitions in any way.
It seems to me that the key of resolving this problem is to somehow unlock the bootloader. Can you think of any way to do this?
Is it possible to flash anything without successfully unlocking the bootloader?
Any other suggestions?
Kind Regards
Malte
Click to expand...
Click to collapse
You should've used
fastboot oem unlock
For unlocking the bootloader. The reason why your phone got bricked was because the bootloader wasn't unlocked. In order to flash zip files or flash recoveries (or do anything that is related to modifying the system) you need the bootloader to be unlocked
Hi,
I am trying to revive my Asus and running into following problem. I read multiple threads and forums and have executed multiple commands in cmd fastboot. Getting following errors:
First I was running into error that "vrl needs to be flashed" which I found a correct (I hope) file and flashed the vrl, and then flashed CM13 or stock ROM from Asus website. Which fastboot returns with "OKAY flashed partition system. Time 28 seconds" Still wont boot and stuck on boot logo.
C:\adb>fastboot devices
G5NPFP026657RFA fastboot
C:\adb>fastboot flash system UL-P023-CN-4.7.3.0-user.zip
(bootloader) system partition type: ext4
target reported max download size of 1019215872 bytes
erasing 'system'...
(bootloader) Erasing partition: system
OKAY [ 0.031s]
sending 'system' (907352 KB)...
(bootloader) Ready to receive: 0x376162fc size of data
OKAY [ 28.448s]
writing 'system'...
(bootloader) Flashing partition: system
FAILED (remote: VRL need to be flashed!)
finished. total time: 28.511s
C:\adb>fastboot flash vrl vrl2.bin
(bootloader) vrl partition type: raw
target reported max download size of 1019215872 bytes
sending 'vrl' (128 KB)...
(bootloader) Ready to receive: 0x00020000 size of data
OKAY [ 0.016s]
writing 'vrl'...
(bootloader) Flashing partition: vrl
OKAY [ 0.078s]
finished. total time: 0.094s
C:\adb>fastboot flash system UL-P023-CN-4.7.3.0-user.zip
(bootloader) system partition type: ext4
target reported max download size of 1019215872 bytes
erasing 'system'...
(bootloader) Erasing partition: system
OKAY [ 0.047s]
sending 'system' (907352 KB)...
(bootloader) Ready to receive: 0x376162fc size of data
OKAY [ 28.424s]
writing 'system'...
(bootloader) Flashing partition: system
OKAY [ 0.031s]
finished. total time: 28.518s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.016s
Any of the senior members or other who have more knowledge, please shade some light here and tell me what am I doing wrong??
I also get below error at times, and my computer gets stuck every time I execute below command and it takes forever for it to get back to working by itself unless I try to close the application.
C:\adb>fastboot update system "C:\adb\UL-P023-WW-4.7.3.0-user.zip"
W/ ( 448): Unable to open 'system': No such file or directory
error: failed to open zip file 'system': I/O Error
C:\adb>fastboot flash system UL-P023-WW-4.7.3.0-user.zip
(bootloader) system partition type: ext4
target reported max download size of 1019215872 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 175719111 is not a multiple of t
he block size 4096
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 1.102s
Very much keen to read some good replies. Thanks in advance guys.
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...