So as far as I know, I am one of the first people to have the bootloader unlocked on the Chinese Mate 9.
I have some unfortunate findings. Mainly, you cannot flash large files over fastboot. Here's what happens:
target reported max download size of 471859200 bytes
sending sparse 'system' (433085 KB)...
OKAY [ 10.825s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 10.869s
We can flash small files, can flash recovery, etc. So we need someone to make TWRP in order to do anything with the unlocked BL. Since there's no source out for the Mate 9, I'm worried about that, but hopefully @raimondomartire can get it done!
Update: I've built a preliminary TWRP, but I don't understand TWRP well, and the mount points are incorrect. However, I believe we will have a working TWRP very soon.
Solid info. Thanks. Once more developers start hopping on, I'm sure we'll get to this faster especially after the fact that you managed to already get the bootloader unlock.
Ahh, progress. Almost there.
{
"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"
}
Good job !!!!
Congrats
أرسلت من HUAWEI NXT-L29 بإستخدام تاباتلك
duraaraa said:
I have some unfortunate findings. Mainly, you cannot flash large files over fastboot. Here's what happens:
target reported max download size of 471859200 bytes
sending sparse 'system' (433085 KB)...
OKAY [ 10.825s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 10.869s
Click to expand...
Click to collapse
I don't think, that it can stop xda community
http://forum.xda-developers.com/showthread.php?t=2749797
Job well done!
5[Strogino] said:
I don't think, that it can stop xda community
http://forum.xda-developers.com/showthread.php?t=2749797
Click to expand...
Click to collapse
Thank you for the idea. Unfortunately, when I tried this tool, it required that the image size is a multiple of 4096 bytes. So I appended null bytes to the end until it was a multiple, split, and flashed all the files, but it doesn't boot.
An update. I hate TWRP mounting /system, /data, /cache, and so on. The only one that doesn't mount is 3rdmodem (I can't even find it in the filesystem.) The data partition and /sdcard partition seem to be encrypted. USB doesn't work (yet)
When I try to flash supersu, the phone crashes and reboots just after the message that it's trying to do a systemless install and creating space...
I tried flashing the zip from Huawei's google services download. That flash worked.
I can't flash any regular huawei updates without a lot of work, so I haven't made an honest effort at unpacking the update.app's partitions and making them into flashable zip files.
So we're kind of stuck unfortunately, with not very much we can do, despite the bootloader being unlocked.
That's all I've got for you all for now.
How do you do to unlock the bootloader once you got the code
playa77176 said:
How do you do to unlock the bootloader once you got the code
Click to expand...
Click to collapse
If you don't know how to do it you might be better off not doing it because there is some risk involved with it at this point.
If you want to try anyway turn off the phone and plug in a USB cable while holding volume down key.
Then run the command on your computer
fastboot oem unlock CODE
Replace code with your code.
Update. I just figured out how to flash a rom via fastboot. Going to try flashing European newest rom on Chinese mate momentarily.
Update: The error I mentioned in my previous post (sending sparse 'system' (433085 KB)...
OKAY [ 10.825s]
writing 'system'...
FAILED (remote: sparse flash write failure)
)
This error doesn't occur if I'm flashing the Chinese firmware. Only if I flash the European firmware.
Something is not quite right. I'm download other version of Euro firmware to check.
Update: The results of which firmwares I can and can't flash via fastboot are pretty much the same as the ones that I could and couldn't flash through eRecovery/HiSuite, without unlocking the bootloader. We need to find a way to flash the system partition from TWRP, with original Huawei images, if we hope to get European builds on the Chinese Mate. Looking pretty bad right now unfortunately. Much more difficult than the Mate 8 / Android 6.
duraaraa said:
Update: The results of which firmwares I can and can't flash via fastboot are pretty much the same as the ones that I could and couldn't flash through eRecovery/HiSuite, without unlocking the bootloader. We need to find a way to flash the system partition from TWRP, with original Huawei images, if we hope to get European builds on the Chinese Mate. Looking pretty bad right now unfortunately. Much more difficult than the Mate 8 / Android 6.
Click to expand...
Click to collapse
Maybe you need an updated fastboot files?
It's possible to unlock With srktool ?
playa77176 said:
It's possible to unlock With srktool ?
Click to expand...
Click to collapse
I think it's best you stick to the regular fastboot commands. SRKTool is for the older Mate, so it might want to flash an incompatible TWRP or something like that.
gm007 said:
Maybe you need an updated fastboot files?
Click to expand...
Click to collapse
I've tried every version of fastboot I can find, on every platform. That's not the issue. I'm going to try and find a way though!
duraaraa said:
Update: The results of which firmwares I can and can't flash via fastboot are pretty much the same as the ones that I could and couldn't flash through eRecovery/HiSuite, without unlocking the bootloader. We need to find a way to flash the system partition from TWRP, with original Huawei images, if we hope to get European builds on the Chinese Mate. Looking pretty bad right now unfortunately. Much more difficult than the Mate 8 / Android 6.
Click to expand...
Click to collapse
The problem is that fastboot does not allow flash very big files.
Solution is to divide file on chunks.
Unfortunately, i don'y have Mate 9.
Try this:
Code:
fastboot -S 256M system path_to_system.img
p.s. You should use actual fastboot version (SDK version)
Related
So after rooting and unlocking my bootloader, I decided to install a custom recovery. However, it keeps failing every time.
C:\Users\Alberto\Desktop\ck>fastboot flash recovery twrp.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7594 KB)...
OKAY [ 0.597s]
writing 'recovery'...
OKAY [ 2.864s]
finished. total time: 3.461s
finished. total time: 0.007s
The phone reboots and still works as usual, but now I can't get into recovery. Is there any way to fix this problem? I am running .4.4.2 Kitkat
It looks like it's flashing correctly, but since you can't reboot into recovery, I would be willing to bet you're flashing the wrong file. What file are you using? Once you flash recovery, you need to boot straight into it so the install completes.
Sent from my HTC6525LVW using Tapatalk
ozeyguy said:
So after rooting and unlocking my bootloader, I decided to install a custom recovery. However, it keeps failing every time.
C:\Users\Alberto\Desktop\ck>fastboot flash recovery twrp.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7594 KB)...
OKAY [ 0.597s]
writing 'recovery'...
OKAY [ 2.864s]
finished. total time: 3.461s
finished. total time: 0.007s
The phone reboots and still works as usual, but now I can't get into recovery. Is there any way to fix this problem? I am running .4.4.2 Kitkat
Click to expand...
Click to collapse
Flashify works pretty well, maybe give it a shot. Also, make sure you have the correct versions.
RikRong said:
It looks like it's flashing correctly, but since you can't reboot into recovery, I would be willing to bet you're flashing the wrong file. What file are you using? Once you flash recovery, you need to boot straight into it so the install completes.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I am using the right files.
Works like a charm. Thanks!
i am having the same problem even with flashify i am using recovery-clockwork-touch-6.0.4.4-xt907.img
after flashing with either flashify or adb i boot into recovery and it hangs at the unlocked bl screen, unlocked bl screen again, then it boots.
deathwithafi said:
i am having the same problem even with flashify i am using recovery-clockwork-touch-6.0.4.4-xt907.img
after flashing with either flashify or adb i boot into recovery and it hangs at the unlocked bl screen, unlocked bl screen again, then it boots.
Click to expand...
Click to collapse
i was having the exact same problem. if you check out this post (http://forum.xda-developers.com/show....php?t=2785214) they suggest using CWM 6.0.4.9 recovery for KK bootloader. i did a fastboot with this and haven't had any problems since.
chuck solid said:
i was having the exact same problem. if you check out this post (http://forum.xda-developers.com/show....php?t=2785214) they suggest using CWM 6.0.4.9 recovery for KK bootloader. i did a fastboot with this and haven't had any problems since.
Click to expand...
Click to collapse
Thank you i will try that
That link goes to 404 error
i found it and it works. thank you
deathwithafi said:
Thank you i will try that
That link goes to 404 error
i found it and it works. thank you
Click to expand...
Click to collapse
Where did you find it? I'm having the same issue, but I can't locate it.
Thanks.
drenze said:
Where did you find it? I'm having the same issue, but I can't locate it.
Thanks.
Click to expand...
Click to collapse
Second link
We cannot teach people anything; we can only help them discover it within themselves.
ezknives said:
Second link
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Thanks!
ezknives said:
Second link
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Link is dead... is there another? TIA!
ozeyguy said:
So after rooting and unlocking my bootloader, I decided to install a custom recovery. However, it keeps failing every time.
C:\Users\Alberto\Desktop\ck>fastboot flash recovery twrp.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7594 KB)...
OKAY [ 0.597s]
writing 'recovery'...
OKAY [ 2.864s]
finished. total time: 3.461s
finished. total time: 0.007s
The phone reboots and still works as usual, but now I can't get into recovery. Is there any way to fix this problem? I am running .4.4.2 Kitkat
Click to expand...
Click to collapse
Im having the same exact problem. I cannot get into recovery. I've tried mfastboot to load CWM (recovery-clockwork-6.0.4.4-xt907.IMG) and TWRP (XT901-XT907-TWRP-2.6.3.0-recovery.img) as well as TWRP Manager and Flashify on the phone. My bootloader is UNLOCKED and This is my config:
{
"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"
}
Does it have something to do with the version of KK? TIA
I believe the TWRP built for this phone is still unofficial, so you probably can't flash it with the app. When you flash with fastboot, do you power off after flashing, and then reboot straight back into recovery? If you don't do this, the stock recovery will over write.
Sent from my Nexus 5
When you flash with fastboot, do you power off after flashing, and then reboot straight back into recovery?
Click to expand...
Click to collapse
I did. I would get a (I dont know how to describe it) but a small "blip" at the bottom of the screen then it boot normal. I tried it several times and the same thing happened, like it was "trying" to get into recovery then just simply boots. I tried different IMG's thinking maybe they were corrupt. Also different USB ports and cables (motorola). NADA. Does it have something to do with the stock KK (I have a verizon phone) is there something in there that is keeping it from "sticking"?
UPDATE: Problem Solved... found in another post that someone was having a similar issue and they used xt926-KK-CWM-6048.img (which is compatible with xt907) I flashed it and CWM came up like normal! Thanks for all your efforts...I hope this helps someone in the future! Cheers!~
Update on the update!
KarmaKid said:
UPDATE: Problem Solved... found in another post that someone was having a similar issue and they used xt926-KK-CWM-6048.img (which is compatible with xt907) I flashed it and CWM came up like normal! Thanks for all your efforts...I hope this helps someone in the future! Cheers!~
Click to expand...
Click to collapse
So I was having issues with that version of CWM ... I found the version of TWRP that works with xt907 and now I get this?!
the screen is not sized properly. Thoughts? TIA
KarmaKid said:
So I was having issues with that version of CWM ... I found the version of TWRP that works with xt907 and now I get this?!
the screen is not sized properly. Thoughts? TIA
Click to expand...
Click to collapse
Though that version will flash to the 907, it's still designed for the 926's screen. You need to find the correct file.
Sent from my Nexus 5
I got the same thing before - It happens when using the wrong version of TWRP
I believe the correct versions are here : http://downloads.blissroms.com/Recovery/Recovery/xt907/
beeewell said:
I got the same thing before - It happens when using the wrong version of TWRP
I believe the correct versions are here : http://downloads.blissroms.com/Recovery/Recovery/xt907/
Click to expand...
Click to collapse
FIXED: THANKS! TWRP 2850...no issues!
First of all:Remember:im just making a thread, all of this wasn´t possible if not for @ccfries(He works at motorola, and sent the files to shamu´s device tree repo)
and @Casper34
See: http://forum.xda-developers.com/showpost.php?p=59562745&postcount=9 and https://android-review.googlesource.com/#/c/143010/
Requirements:
Motorola Drivers:
http://storage.googleapis.com/tetheredupgrades/MotorolaDeviceManager_2.5.4.exe
Qualcomm Drivers:
http://forum.xda-developers.com/attachment.php?attachmentid=631288&d=1308601930
Optional: If having issues use:
http://forum.xda-developers.com/showthread.php?t=2263822
Unbrick Stuff:
https://www.dropbox.com/s/8783ohne2mufiwc/Nexus6Unbrick.rar?dl=0
or
https://drive.google.com/file/d/0BwduAK2l37Oaa1BQZncwaEpNb1E/view?usp=sharing
Factory Images for Nexus 6(needs to be 5.1)
https://dl.google.com/dl/android/aosp/shamu-lmy47d-factory-6c44d402.tgz
or via RSD Lite
http://motofirmware.center/files/file/1069-shamu-lmy47e-release-keys-subsidy-default-cfcxmlzip/
FASTBOOT AND ADB NEEDS TO BE ALREADY SETTED UP
Pre Requirements:
- Disable driver signature checking
Windows 7:
https://www.youtube.com/watch?v=k4RwaI4mn6Y
Windows 8:
https://learn.sparkfun.com/tutorial...abling-signed-driver-enforcement-on-windows-8
Windows 8.1:
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
- Install the drivers:
Go to device manager, Unknown devices, double click qhusb_bulk, install driver, select location and select where you extracted the drivers.
{
"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"
}
- Next you should extract both zip files (Unbrick and factory images)
- Then Connect your nexus 6 on your computer (now should appear as Qualcomm HS-USB QD-Loader 9008 under "COM PORTS"):
- Open the Unbrick folder and run blank-flash.bat:
- Flash Stock factory images: (Problems see #2)
Your phone should show up on the computer as fastboot.Just flash stock factory images. (Motorola via "RSD Lite" or Google one should do the trick).
Thanks:
@ccfries(HUGE Thanks to him, turns out he is the one who made the commit with the necessary files, props to him!)
@Casper34 (Huge help with his working nexus 6)
@bitdomo (helped me a lot, and i got some images from another thread of his)
Problems that may occur during or after:
Stuck at waiting for device
Check if drivers are installed correctly and restart pc
Check if you have an updated fastboot
THESE TWO ARE THE MAIN REASON OF PROBLEMS (mostly outdated fastboot)
-Drivers
http://forum.xda-developers.com/showthread.php?t=2263822
http://storage.googleapis.com/tetheredupgrades/MotorolaDeviceManager_2.5.4.exe
Fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
Problems while flashing factory images:
ccfries said:
First, fastboot flash partition gpt.bin
Then flash the other images.
If you just bricked by downgrading bootloader, the persist and modem calibration should still be happily where it was when you started.
This won't help you if you're stuck with Allow OEM Unlock. Be careful locking on 5.1. There's accurate information elsewhere in the forum on that.
-Chris
Click to expand...
Click to collapse
PS:
ccfries said:
If you lock, it clears the setting by design, so you can't lock and unlock without booting up and checking the box.
Click to expand...
Click to collapse
Wifi / Bluetooh dosen´t work:
See http://forum.xda-developers.com/showpost.php?p=59561966&postcount=3
No IMEI / No Signal
Restore EFS Backup
If wifi/bt/camera dosen´t work Then probably your /persist got somehow corrupted. (Post Under construction)
For a fix:
Flash a custom recovery, and open a terminal with the phone booted to it
run
umount /persist
mkdir /persist
mount /dev/block/platform/msm_sdcc.1/by-name/persist /persist
#e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
you will be propmpted to check / repair errors, keep pressing enter for each that it appears
then run
umount /perist
and reboot phone
Wow! Very nice. I bet you just saved some poor guys from getting yelled at from wifey. Good job and thanks for helping the community. :highfive:
wow indeed!
jayharper08 said:
Wow! Very nice. I bet you just saved some poor guys from getting yelled at from wifey. Good job and thanks for helping the community. :highfive:
Click to expand...
Click to collapse
simms22 said:
wow indeed!
Click to expand...
Click to collapse
Thanks to both, thankfully cm already merged a check for the bootloader, but i hope this can fix phones that are already bricked for people who cant use warranty (outside area, on a trip, etc).
Oh yeah, or in the case of my friend, his mom
This needs stickied
Sent from my Nexus 6 using XDA Free mobile app
@opssemnik
No worries, glad to help out!
Sent from my Nexus 6
opssemnik said:
@ccfries(Huge thanks for him, for finding an un merged commit that had the partition layout)!.
Click to expand...
Click to collapse
I authored the commit this afternoon so finding it was pretty easy. :good:
ccfries said:
I authored the commit this afternoon so finding it was pretty easy. :good:
Click to expand...
Click to collapse
Oh no wait, I DIDN´T SEE THE AUTHOR LOL.
may i ask was it hard for you to get the permission to post? afaik these files are proprietary (aside from the paritition table) or aren´t they?.
also can i ask you something a bit more offtopic?
i noticied the nexus 6 works directly with QPST (at least it can communicate with it)
but some other devices (like the nexus 5) can´t, its something that qualcomm or the manufacturer decide / make?
Once again ,props to you and motorola!
Never thought of an oem doing that, even more that the bricks can only be achieved when messing with things you shouldnt be :good::good::good:
Erm, don't mind me asking one question.
How do you back up your efs if your phone is bricked?
So I thought I would rid myself of no Xposed or CM12 on 5.1 (LMY47D) by going back to 5.0.1 and flashing CM12 again from an older nightly I had downloaded already....I think we all know what happened.
I managed to get through it all and have the blank-flash boot loader screen up but I get hung up on <waiting for device> when trying to flash factory image (LMY45D). The boot loader shows as locked and as a result I am unable to flash a factory image. Hopefully I am not breaking any rules or anything by posting this here but this is the error I am getting when running the flash-all.sh:
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.181s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.769s]
writing 'radio'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.772s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(665,0xa03911d4) malloc: *** mach_vm_map(size=1779851264) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1778070480 bytes
error: update package missing system.img
and when I try to run em unlock:
fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s
Looks good. Does this only help the CM12 people or does it override the "enable OEM Unlock" people too?
serdaj said:
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
Click to expand...
Click to collapse
First, fastboot flash partition gpt.bin
Then, fastboot reboot-bootloader
Then flash the other images.
If you just bricked by downgrading bootloader, the persist and modem calibration should still be happily where it was when you started.
This won't help you if you're stuck with Allow OEM Unlock. Be careful locking on 5.1. There's accurate information elsewhere in the forum on that.
-Chris
Damn, wish this was on here last week. Had to send my N6 off to repair centre for this as I thought it was a gonner. Fault diagnosed as 'Electrical issue - Replacement required'. Replacement is coming tomorrow hopefully. Will bookmark this, thanks.
Delboyd12 said:
Damn, wish this was on here last week. Had to send my N6 off to repair centre for this as I thought it was a gonner. Fault diagnosed as 'Electrical issue - Replacement required'. Replacement is coming tomorrow hopefully. Will bookmark this, thanks.
Click to expand...
Click to collapse
That was when he started this.... After many bricks. I know a lot of people RMAed their phones, but this can still help others!
ccfries said:
This won't help you if you're stuck with Allow OEM Unlock. Be careful locking on 5.1.
Click to expand...
Click to collapse
It would be helpful if the OP would add this to his first post.
@opssemnik Great Job can you please help me to do so with my HTC One M8 ?
i had the same problem " qualcomm hs-usb qdloader 9008 "
Thanks
bradputt said:
Erm, don't mind me asking one question.
How do you back up your efs if your phone is bricked?
Click to expand...
Click to collapse
Restore he wrote
Shamu/Hammerhead/Flounder Dkwhq www.jsand.dk
Please can someone help me?
I am stuck in the bootloader, which is locked. I can't boot the phone up. I am trying to flash stock images but nothing is happening. Just booting to the bootloader every time.
I can detect my device using fastboot devices, but every time I try and write an img it fails, because the bootloader's locked! Argh!
Thanks in advance,
Tom
I cant enter adb. only something like fastboot (bootloader) . also can start like ZTE Handset Diagnostic Interface(DFU)
can you help me? nothing works
{
"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"
}
C:\adb> adb devices
List of devices attached
C:\adb>fastboot devices
2a47d296 fastboot
C:\adb>fastboot flash recovery twrp-3.0.3-1-ailsa_ii.img
target reported max download size of 536870912 bytes
sending 'recovery' (13536 KB)...
OKAY [ 0.316s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.331s
I HAVE THE SAME ISSUE!(A2017G) SOMEONE HELP! :crying:
You're not bricked, you're just down ATM. If you can get into bootloader or EDL mode you're fine. Just gotta put some work in. First, you've probably got a bootloader that doesn't allow fastboot commands. (the reason why you're getting the unknown command error). You need to flash that via EDL if you don't want to downgrade/unlock your bootloader. There is SOOOO much to read out there that with a little searching and reading you'll be up in no time. This toolkit is a good place to start looking. https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
nolimit78 said:
You're not bricked, you're just down ATM. If you can get into bootloader or EDL mode you're fine. Just gotta put some work in. First, you've probably got a bootloader that doesn't allow fastboot commands. (the reason why you're getting the unknown command error). You need to flash that via EDL if you don't want to downgrade/unlock your bootloader. There is SOOOO much to read out there that with a little searching and reading you'll be up in no time. This toolkit is a good place to start looking. https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Click to expand...
Click to collapse
Hey, I CAN use Fastboot commands. but i cant get to recovery mode even tho i flash it. my bootloader is unlocked. please help!! i am stuck
Well with the error message you posted, "unknown command" means that you're on the wrong bootloader. You have two methods to install TWRP. Bootloader or EDL. If you want to do it via bootloader you need to load the B20 bootloader and that'll allow for the fastboot flash recovery "name of img file".img command. If you're wanting to use EDL you'll need to use a tool to force the recovery image.
nolimit78 said:
You're not bricked, you're just down ATM. If you can get into bootloader or EDL mode you're fine. Just gotta put some work in. First, you've probably got a bootloader that doesn't allow fastboot commands. (the reason why you're getting the unknown command error). You need to flash that via EDL if you don't want to downgrade/unlock your bootloader. There is SOOOO much to read out there that with a little searching and reading you'll be up in no time. This toolkit is a good place to start looking. https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Click to expand...
Click to collapse
fastboot flash recovery twrp-3.0.3-1-ailsa_ii.img
target reported max download size of 536870912 bytes
sending 'recovery' (13536 KB)...
OKAY [ 0.316s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.331s
I cant go to edl. Only DFU.
C:\adb>fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.034s
FAILED to all commands in fastboot
nolimit78 said:
Well with the error message you posted, "unknown command" means that you're on the wrong bootloader. You have two methods to install TWRP. Bootloader or EDL. If you want to do it via bootloader you need to load the B20 bootloader and that'll allow for the fastboot flash recovery "name of img file".img command. If you're wanting to use EDL you'll need to use a tool to force the recovery image.
Click to expand...
Click to collapse
Check This;;
:\Users\Bumthimble\Desktop\ADB>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (17917 KB)...
OKAY [ 0.424s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 0.565s
I get this but when i try to boot into recovery, it boots into fastboot mode. Help
Ok that means that both of you are using the G model. If you're able to get to your bootloader try using the tool that I linked above. I have the U model so I can't relate with some of your issues but I believe that if you can reach the bootloader the tool can help. Have you tried manually booting to EDL?
nolimit78 said:
Ok that means that both of you are using the G model. If you're able to get to your bootloader try using the tool that I linked above. I have the U model so I can't relate with some of your issues but I believe that if you can reach the bootloader the tool can help. Have you tried manually booting to EDL?
Click to expand...
Click to collapse
I did. but it doesnt boot into EDL ever. I dont know why, i doesnt recognise its commands
nolimit78 said:
Ok that means that both of you are using the G model. If you're able to get to your bootloader try using the tool that I linked above. I have the U model so I can't relate with some of your issues but I believe that if you can reach the bootloader the tool can help. Have you tried manually booting to EDL?
Click to expand...
Click to collapse
I have China version. I cant manually booti to EDL. it booting in DFU
i can only boot it to fastboot
See this thread: https://forum.xda-developers.com/axon-7/help/edl-twrp-stuck-fastboot-luck-t3569879
don't work.
ZTE Handset Diagnostic Interface(DFU)
with handmade deepflash cable
if I connect with a closed cable, it blinks the symbol of charging(empty battery with the lightning bolt) several times and boot in DFU
fatax said:
don't work.
ZTE Handset Diagnostic Interface(DFU)
with handmade deepflash cable
if I connect with a closed cable, it blinks the symbol of charging(empty battery with the lightning bolt) several times and boot in DFU
Click to expand...
Click to collapse
I have exactly the same issue.
And 2 weeks already. Can't find any solution. Searched all the internet.
There is no solution so far.
Have to wait untill someone will create a flashtool for DFU mode for Snapdragon 820.
Vick78 said:
I have exactly the same issue.
And 2 weeks already. Can't find any solution. Searched all the internet.
There is no solution so far.
Have to wait untill someone will create a flashtool for DFU mode for Snapdragon 820.
Click to expand...
Click to collapse
I gave the phone to a service center (unofficial) they will try to flash the phone directly to memory
fastboot still locked. they can not do anything
fatax said:
fastboot still locked. they can not do anything
Click to expand...
Click to collapse
that's a sad news. did they say anything?
what do they need to fix?
Vick78 said:
that's a sad news. did they say anything?
what do they need to fix?
Click to expand...
Click to collapse
I do not know, but my acquaintance with 4pda wrote: Hello. It's JOY NEWS! We HAVE RISE ONE BRICK! So wait soon we will lay out the instruction how to raise. The phone will have to be dismantled.
I have now the same problem how did you solved the problem? Or is there generaly any solution?
cybertronixx said:
I have now the same problem how did you solved the problem? Or is there generaly any solution?
Click to expand...
Click to collapse
Did you search on the forum before bumping a year-old thread?
So far there are 2 DFU guides, mine is the latest. (Google "dfu unbrick"). Though you might want to try an EDL cable before doing the process on the guide. Just use MiFlash or EDL Tool along with the cable, and you might fix it.
Hi i've done something stupid, i've blocked bootloader idk why, anyway im in LineageOs 16, but now i can't back to stock or flash something else ¿i cant re-unlock bootloader?
What is the error that you're getting?
Fastboot flash bootloader permission denied
elHeisen said:
Fastboot flash bootloader permission denied
Click to expand...
Click to collapse
Yes you can't flash before unlocking? How about 'fastboot unlock bootloader' or was it 'fastboot bootloader unlock'? Sorry, tired hehe.
weazie said:
Yes you can't flash before unlocking? How about 'fastboot unlock bootloader' or was it 'fastboot bootloader unlock'? Sorry, tired hehe.
Click to expand...
Click to collapse
yep i've tried too but i get this
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
and i can't enable OEM unlocking in Android P
elHeisen said:
yep i've tried too but i get this
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
and i can't enable OEM unlocking in Android P
Click to expand...
Click to collapse
Did you find any solution?
Same problem!
Works for me!
elHeisen said:
yep i've tried too but i get this
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
and i can't enable OEM unlocking in Android P
Click to expand...
Click to collapse
First, install gnirehtet for reverse tethering internet with usb and pc
https://github.com/Genymobile/gnirehtet
Then you will see that you can enable OEM
I'm still not able to unlock oem in settings. I have WIFI on and did all the updates to the latest
elHeisen said:
Fastboot flash bootloader permission denied
Click to expand...
Click to collapse
Same error here. Did anyone find a solution?
Constantinologia said:
Same error here. Did anyone find a solution?
Click to expand...
Click to collapse
Can you update your phone in settings? if not wait 7 days with phone on and try again. An update fixed my phone.
mrsiri said:
Can you update your phone in settings? if not wait 7 days with phone on and try again. An update fixed my phone.
Click to expand...
Click to collapse
I can't even load the system. The only two screens i can see are the Fastboot and "your device is corrupted". The Flashing option is locked and every rom i try to flash gives me the access denied error.
{
"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"
}
Constantinologia said:
I can't even load the system. The only two screens i can see are the Fastboot and "your device is corrupted". The Flashing option is locked and every rom i try to flash gives me the access denied error.
View attachment 5251849 View attachment 5251851
Click to expand...
Click to collapse
Can you download the stock rom from your current version flashed and boot it? use command "fastboot boot boot.img". Boot.img is inside of the flashable stock rom zip. After this try toggling the oem unlock if not wait 7 days and try to update phone like regular ota in setings
mrsiri said:
Can you download the stock rom from your current version flashed and boot it? use command "fastboot boot boot.img". Boot.img is inside of the flashable stock rom zip. After this try toggling the oem unlock if not wait 7 days and try to update phone like regular ota in setings
Click to expand...
Click to collapse
I found a stock rom that matches the descriptions from ro.build.fingerprint[0]: motorola/rav_retail/rav:10/QPJS30 and 63-35-1-15. Coudn'd find a match for 37df17:user/release-key.
Still got the error for fastboot boot boot.img:
downloading 'boot.img'...
OKAY [ 1.463s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 37.486s
Constantinologia said:
I found a stock rom that matches the descriptions from ro.build.fingerprint[0]: motorola/rav_retail/rav:10/QPJS30 and 63-35-1-15. Coudn'd find a match for 37df17:user/release-key.
Still got the error for fastboot boot boot.img:
downloading 'boot.img'...
OKAY [ 1.463s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 37.486s
Click to expand...
Click to collapse
I don't remember the steps to reproduce, but I remember being possible to take the very own boot.img currently flash on your phone. I think it was through adb commands, what if you try booting that one instead? That's what I did on mine, but it didn't help with toggling oem unlock, only entering the system
I accidentally locked mine and im in the same situation as everyone here, but i think the only solution is BlankFlashing or sideloading a signed OTA on it... Im trying everyday new possible methods of fixing it and if i get into some ill share here
hi guys, had exact same issue, spent hours trolling through the net, forums etc and this forum fixed it for me. I was about to throw the phone out.
something tells me that you have to have the boot image from the software you had installed before the crash/brick. Run the "fastboot boot boot.img"
i tried numerous boot.img's thinking I've spent too much time this device so as I turned my back on the phone I hear a 'Hello Moto' WTF...Up and running again. Good Luck
thehulk1969 said:
hi guys, had exact same issue, spent hours trolling through the net, forums etc and this forum fixed it for me. I was about to throw the phone out.
something tells me that you have to have the boot image from the software you had installed before the crash/brick. Run the "fastboot boot boot.img"
i tried numerous boot.img's thinking I've spent too much time this device so as I turned my back on the phone I hear a 'Hello Moto' WTF...Up and running again. Good LuckView attachment 5274327
Click to expand...
Click to collapse
It would be the solution if the stock was corrupted, but i have locked mine on StyxOS, and there isn't any boot.img for it so stock boot.img gives a system corrupted error. But nice idea.
Edit: Does it need to match the ro.fingerprint on getvar all? only tested with latest pie, so
1. Download F10 abl.img
2. Reboot to fastboot and flash F10 abl
adb reboot fastboot
fastboot flash abl abl.img
3.. Reboot fastboot reboot and you can use dual SIM.
Worked like a charm!
I am running OOS13 KB2003 converted from T-Mobile
I got:
FAILED (remote: 'Flashing is not allowed for Critical Partitions.')
running
Code:
fastboot flash abl abl.img
I tried to run
Code:
fastboot flashing unlock_critical
But got :
FAILED (remote: ' Device already : unlocked!')
Is there a work around?
Thanks in advance!
Stylishly said:
I am running OOS13 KB2003 converted from T-Mobile
I got:
FAILED (remote: 'Flashing is not allowed for Critical Partitions.')
running
Code:
fastboot flash abl abl.img
I tried to run
Code:
fastboot flashing unlock_critical
But got :
FAILED (remote: ' Device already : unlocked!')
Is there a work around?
Thanks in advance!
Click to expand...
Click to collapse
As far as i remember, you need to be in fastbootd to flash critical partitions.
{
"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"
}
Code:
fastboot reboot fastboot
fastboot flash abl abl.img
Does this require bootloader unlock? Would someone be able to provide more step by step confirmation on this? Also what does the updated abl.img do in order to enable dual-sim?
raven911 said:
Also what does the updated abl.img do in order to enable dual-sim?
Click to expand...
Click to collapse
It's taken from OOS13 F.10 beta release, where sim-lock is not present.
C:\adb>fastboot flash abl abl.img
target reported max download size of 268435456 bytes
sending 'abl' (220 KB)...
OKAY [ 0.009s]
writing 'abl'...
FAILED (remote: No such file or directory)
finished. total time: 0.014s
try on op 8t t mobile original firmware kb2007_11_F46 not working on it
Can you flash this in custom recovery like Orange Fox?
amine tenes said:
C:\adb>fastboot flash abl abl.img
target reported max download size of 268435456 bytes
sending 'abl' (220 KB)...
OKAY [ 0.009s]
writing 'abl'...
FAILED (remote: No such file or directory)
finished. total time: 0.014s
try on op 8t t mobile original firmware kb2007_11_F46 not working on it
Click to expand...
Click to collapse
You forgot to reboot to fastbootd.
Code:
fastboot reboot fastboot
kevinco1 said:
Can you flash this in custom recovery like Orange Fox?
Click to expand...
Click to collapse
As far as i remember in recovery you can flash .img to boot or recovery partition directly.
So you'll have to pack in update.zip where in script it will be specified which partition should abl.img be flashed to.
Excellent! Thanks Jookean !
Now my (originally) TMo 8T has been converted to a dual SIM KB2003 that works better (in the US) than my old (dual IMEI) KB2003 that I hard bricked (in FastbootD) trying to get an A12 OTA working right.
I rarely got 5G indicated on my Euro original, but now mostly 4G and low-ish signal strength issues are history! No longer being tied to T-Mobile's software updates and being able to have 5G options on my device from Verizon and Tmobile was my goal.
My eBay bargain Pixel 6 Pro will have to wait a while longer. I prefer flat screens and lighter devices. Guessing Oneplus anticipated fumbling of Android 14 may entice me to switch. Wish it had two physical SIM slots.