Database Users

Bricked 2012 Wifi Only Nexus 7, Please Help

Sorry if this has been addressed but I've been searching and reading and freaking out because I can't find out how to recover my Nexus 7.
I'm trying to manually update my 2012 Wifi Only Nexus 7 to Lollipop and my computer will not see the device any longer in ADB.
I downloaded the latest sdk and the latest image file (Nakasi 5.0.2 (LRX22G).
Ran through the steps found here: http://www.androidcentral.com/how-manually-upgrade-your-nexus
At this step fastboot flash bootloader [bootloader file].img it just sat there for about an hour and didn't do anything.
***Edit- I got it to work and then got the invalidstate error.
I then read that others have had success updating to Lollipop without updating there bootloader here: http://android.stackexchange.com/qu...t-flash-bootloader-failed-remote-invalidstate
***This is because my bootloader was already on 4.23.***
I then proceeded with fastboot -w update [image file].zip
The image failed after wiping everything with an error about too many links.
Now when I try I get "C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>fastboot -w upd
ate image-nakasi-lrx22g.ziparchive does not contain 'boot.sig'"
At this point, I can't get any adb commands to work as the device is not showing up as a connected device. I've rebooted my pc and the tablet multiple times. Fastboot keeps crashing as well.
Please help me get my Nexus back up and running. Thanks so much.

The Bootloader in the factory image is not valid see here
If you still can get into fastboot on your device,
Extract the img files from the zip file and manually flash each of them.
Alternatively, you could extract all the .img files in the zip file and flash them manually one at a time. This makes things really handy if you're using the factory image to act as an update rather than a complete return to stock. If trying to update using the factory image, extract the .img from the zip file into the same directory as your bootloader and radio img files and execute the following commands in order:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
Click to expand...
Click to collapse
Quote taken from here

corkiejp said:
The Bootloader in the factory image is not valid see here
If you still can get into fastboot on your device,
Extract the img files from the zip file and manually flash each of them.
Quote taken from here
Click to expand...
Click to collapse
Thanks, this is what I get
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>fastboot flash
system system.img
sending 'system' (648819 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.016s
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>

touch_rules said:
Thanks, this is what I get
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>fastboot flash
system system.img
sending 'system' (648819 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.016s
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
Are you in fastboot mode?
Step 4: Make sure the device is connected to the computer while in fastboot mode. Different devices may require different commands to get into fastboot mode. Make sure the device is powered off and then use the following button commands:
Nexus 7 - Vol Down + Power
Click to expand...
Click to collapse
Since you issued an Adb command first, suggest your not?
Another option would be to use Wugfresh Nexus Root toolkit and set the option to "Force Flash Mode" in Options Flash Stock.

corkiejp said:
Are you in fastboot mode?
Since you issued an Adb command first, suggest your not?
Another option would be to use Wugfresh Nexus Root toolkit and set the option to "Force Flash Mode" in Options Flash Stock.
Click to expand...
Click to collapse
Yes, I am. Please take a look at this picture. Thanks.
View attachment 3085046

Now I'm getting this At least it's different
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>fastboot flash
system system.img
erasing 'system'...
FAILED (status read failed (Too many links))
finished. total time: 0.176s

corkiejp said:
Another option would be to use Wugfresh Nexus Root toolkit and set the option to "Force Flash Mode" in Options Flash Stock.
Click to expand...
Click to collapse
Noticed this part after I posted last, seems to be working....I'll let you know. Thanks so much. Wish I would have seen the toolkit earlier today when I started haha.

You rock corkiejp! Working like a champ now! Thanks so much.

I had exactly the same problem and ended up using Wug's toolkit and the individual images.
Sent from my Nexus 7 using XDA Free mobile app

I literally had it restore the factory image and it did it all. Made sure I had force flash checked.

Man, I really need some help here. i am in a almost exact situation here. Only thing different is that my tablet is locked. I go to wugs and flash stock image and get stuck on "waiting for device".
{
"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"
}
Any help would be highly appreciated!!!

Your bootloader is locked.
rayandreas said:
Man, I really need some help here. i am in a almost exact situation here. Only thing different is that my tablet is locked. I go to wugs and flash stock image and get stuck on "waiting for device". View attachment 3237509
Any help would be highly appreciated!!!
Click to expand...
Click to collapse
Hi, rayandreas...
Something is definately not quite right with your posted screenshot/output.
Transcribing it as follows, we have...
Code:
erasing 'boot'...
OKAY [ 1.154s]
finished. total time: 1.155s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 3.045s]
finished. total time: 3.045s
erasing 'recovery'...
OKAY [ 0.240s]
finished. total time: 0.241s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.014s]
finished. total time: 0.014s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.014s]
finished. total time: 0.014a
So far, so good.
I can see nothing wrong with this output, thus far... and I've seen something similar on my Nexus 7 many times when I've fastboot flashed stuff.
----
But then this bombshell hits!!
Code:
sending 'bootloader' <2100 KB>...
[COLOR=RED][B]
FAILED <remote: Bootloader is locked.>
[/B][/COLOR]
finished. total time: 0.015s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
----
WTF!!!
Bootloader is now locked!
How is this even remotely possible?
----
If the bootloader is locked, the first half of your posted output simply shouldn't have been possible... But yet, your screenshot proves otherwise.
The bootloader is either locked and NO fastboot flash commands are possible, or the bootloader is unlocked and ALL fastboot flash commands are possible...
Your Nexus 7 seems to have 'changed its mind' about its bootloader lock status, halfway through fastboot flashing!!!
----
To determine the bootloader lock status of your Nexus 7, you need to boot your Nexus 7 into it's bootloader manually...
*** shut down the device completely.
*** press and hold VOL DOWN, and press POWER ON.
*** the text in the lower left hand corner of the screen should indicate the devices bootloader locked status.
See my attached screenshot for the sort of thing you should expect to see if the bootloader is unlocked.
---
If it's locked, try unlocking it manually (ie, via fastboot), with...
Code:
fastboot oem unlock
Hope this helps.
Rgrds,
Ged.

GedBlake said:
Hi, rayandreas...
Something is definately not quite right with your posted screenshot/output.
Transcribing it as follows, we have...
Code:
erasing 'boot'...
OKAY [ 1.154s]
finished. total time: 1.155s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 3.045s]
finished. total time: 3.045s
erasing 'recovery'...
OKAY [ 0.240s]
finished. total time: 0.241s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.014s]
finished. total time: 0.014s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.014s]
finished. total time: 0.014a
So far, so good.
I can see nothing wrong with this output, thus far... and I've seen something similar on my Nexus 7 many times when I've fastboot flashed stuff.
----
But then this bombshell hits!!
Code:
sending 'bootloader' <2100 KB>...
[COLOR=RED][B]
FAILED <remote: Bootloader is locked.>
[/B][/COLOR]
finished. total time: 0.015s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
----
WTF!!!
Bootloader is now locked!
How is this even remotely possible?
----
If the bootloader is locked, the first half of your posted output simply shouldn't have been possible... But yet, your screenshot proves otherwise.
The bootloader is either locked and NO fastboot flash commands are possible, or the bootloader is unlocked and ALL fastboot flash commands are possible...
Your Nexus 7 seems to have 'changed its mind' about its bootloader lock status, halfway through fastboot flashing!!!
----
To determine the bootloader lock status of your Nexus 7, you need to boot your Nexus 7 into it's bootloader manually...
*** shut down the device completely.
*** press and hold VOL DOWN, and press POWER ON.
*** the text in the lower left hand corner of the screen should indicate the devices bootloader locked status.
See my attached screenshot for the sort of thing you should expect to see if the bootloader is unlocked.
---
If it's locked, try unlocking it manually (ie, via fastboot), with...
Code:
fastboot oem unlock
Hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you for even taking time for helping me thus far. I can say that it states the boot loader is locked. I have tried using wugs to unlock it but it doesn't work. I can't boot it up either. Just stays on the google splash screen. I am at a loss at what to do as of now. If I could get some help on how to rescue this thing I would be glad to donate a 12 pack or a 10 coffee or something. I received the tablet this way. I am hoping to fix it so my wife can use it.

rayandreas said:
Thank you for even taking time for helping me thus far. I can say that it states the boot loader is locked. I have tried using wugs to unlock it but it doesn't work. I can't boot it up either. Just stays on the google splash screen. I am at a loss at what to do as of now. If I could get some help on how to rescue this thing I would be glad to donate a 12 pack or a 10 coffee or something. I received the tablet this way. I am hoping to fix it so my wife can use it.
Click to expand...
Click to collapse
Hi again, rayandreas...
If it where my tablet, I'd just fastboot flash the Google factory stock image for your device.
The Google factory stock image for your device can be found here...
https://developers.google.com/android/nexus/images#nakasi
There's little point in my re-inventing the wheel by writing yet another tutorial... full details and instructions can be found here...
[GUIDE] Flashing a Factory Image with fastboot / return to stock
----
But all of this is contingent upon successfully UNLOCKING THE BOOTLOADER.
The bootloader needs to be unlocked, before anything can be fastboot flashed.
Whilst this can be done with toolkits (such as Wugs), I personally prefer to deal with fastboot directly (instead of through a layer of GUI polished menus and dialogue boxes).
----
From power-down state, or to force boot the device into its bootloader...
** Press and hold VOL-DOWN.
** Whilst holding VOL-DOWN, press POWER ON.
** Keep BOTH buttons pressed for a good 30 seconds.
If successful, you should see a GREEN ANDROID lying on its back...
----
USB connect it to your laptop/PC. Ensure you have the correct drivers installed on your laptop/PC as per the instructions detailed in the above link.
The command is as follows...
Code:
fastboot oem unlock
Due to security considerations, this command will wipe the Nexus 7, and you will be advised of this by the Nexus 7 itself, and you'll also need to confirm the bootloader unlock request at the Nexus 7 end via a confirmation dialogue box.
(See the attached screenshot for the sort of thing you should expect to see).
If successful, you should see an unlocked padlock symbol at the bottom of the screen, underneath the Google logo, whenever the device boots.
----
Unlocking the bootloader is critical if you wish to fastboot flash anything. Even official Google factory stock images require an unlocked bootloader to be fastboot flashed. And with the Google recommendation that the bootloader is re-locked afterwards with...
Code:
fastboot oem lock
This is optional of course, and I would generally recommend against it, because if you wish to unlock the bootloader again at some future date, it will wipe/factory reset the device...
General point of advice: Once Unlocked - Leave it Unlocked.
---
Hope this helps... and good luck.
Rgrds,
Ged.

View attachment 3240619
Man, it was looking promising. Went into boot loader, asked me if I wanted to unlock and then it failed : ( This is crazy!!! Please see attached pics. Any other ideas? I am at a loss...

rayandreas said:
View attachment 3240618
View attachment 3240619
View attachment 3240620
Man, it was looking promising. Went into boot loader, asked me if I wanted to unlock and then it failed : ( This is crazy!!! Please see attached pics. Any other ideas? I am at a loss...
Click to expand...
Click to collapse
Maybe your bootloader is corrupted? @GedBlake, can you provide him with latest 4.23 bootloader? I was searching the web and found out some bootloaders can be bad. Someone correct me if I said something wrong(just trying to help xD)

Fobos531 said:
Maybe your bootloader is corrupted? @GedBlake, can you provide him with latest 4.23 bootloader? I was searching the web and found out some bootloaders can be bad. Someone correct me if I said something wrong(just trying to help xD)
Click to expand...
Click to collapse
Man, I'll try anything. It is really racking my brain!
Thanks guys, for all the help so far...

rayandreas said:
Man, I'll try anything. It is really racking my brain!
Thanks guys, for all the help so far...
Click to expand...
Click to collapse
According to this article, some of bootloaders were corrupted or what. Update NRT masterlists in the toolkit and try flashing the latest bootloader if that is possible through the toolkit. Maybe it will let you to unlock the bootloader afterwards. If the toolkit can't do that for you, download latest factory image(4.4.4 or 5.1, what you desire) and extract the bootloader from the image. It will probably be named "bootloader-nakasi....." Try manually flashing it through CMD/ADB using "fastboot flash bootloader "name of bootloader file". I repeat, I don't have much experience with this tablet, but I'm doing what I can. Try doing what I suggested, maybe it'll work. You can't make it worse after all Good luck!
EDIT: In the link I posted, there are some neat instructions and a link to the new bootloader down the page. Make sure to check that out too.

I did update the NRT images and tried again with no luck. I also tried going into recovery and this is what I get. So, it looks like I have a crazy locked boot loader and no recovery at all. I am trying the other method now. We shall see!
Thanks for all the help so far. It means a lot!

rayandreas said:
I did update the NRT images and tried again with no luck. I also tried going into recovery and this is what I get. So, it looks like I have a crazy locked boot loader and no recovery at all. I am trying the other method now. We shall see!
Thanks for all the help so far. It means a lot!
View attachment 3242733
Click to expand...
Click to collapse
You actually have a recovery, a stock one. While at that screen, press Volume Up + Power for 1 sec( or only Volume Up, not sure) to access it. You can try doing a factory reset there if that helps anyhow.

Findings after unlocking bootloader

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)

DFU and fastboot. Brick Axon 7 A2017

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.

Can't Re-Unlock bootloader?

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

How to unlock a Moto G7 xt1962-6

I rebooted my G7 into fastboot to wipe the cache and I got stuck in it. I wasn't trying to load a new image or replace anything. When I try any option (Start, Restart Bootloader, Recovery mode, Factory Mode, etc) it fails with the following message in the log:
Code:
SSM: Android image rollback: 8.9
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
So, I downloaded adb/fastboot, got the drivers installed, and tried to download the latest image from https:__mirrors.lolinet.com/firmware/moto/river/official/RETEU/ and then tried to flash it.
When I try to replace boot.img:
Code:
C:\temp\moto-g7-firmware> fastboot flash boot boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (32768 KB) OKAY [ 0.990s]
Writing 'boot_a' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Well, that's probably because I didn't unlock my bootloader first? I didn't know I'd be doing this. Maybe there's a stock boot image that wouldn't cause me problems?
I tried to unlock my bootloader. I got my boot key but when I run:
Code:
C:\temp\moto-g7-firmware> fastboot oem unlock XXXXXXXXXXXXXXXXXXXXXX
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.021s]
Finished. Total time: 0.027s
Well, this sucks. I can't get into the phone to get to the Android Settings menu. I feel stuck. Does anybody have any ideas for me?

rsshilli said:
I rebooted my G7 into fastboot to wipe the cache and I got stuck in it. I wasn't trying to load a new image or replace anything. When I try any option (Start, Restart Bootloader, Recovery mode, Factory Mode, etc) it fails with the following message in the log:
Code:
SSM: Android image rollback: 8.9
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
So, I downloaded adb/fastboot, got the drivers installed, and tried to download the latest image from https:__mirrors.lolinet.com/firmware/moto/river/official/RETEU/ and then tried to flash it.
When I try to replace boot.img:
Code:
C:\temp\moto-g7-firmware> fastboot flash boot boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (32768 KB) OKAY [ 0.990s]
Writing 'boot_a' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Well, that's probably because I didn't unlock my bootloader first? I didn't know I'd be doing this. Maybe there's a stock boot image that wouldn't cause me problems?
I tried to unlock my bootloader. I got my boot key but when I run:
Code:
C:\temp\moto-g7-firmware> fastboot oem unlock XXXXXXXXXXXXXXXXXXXXXX
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.021s]
Finished. Total time: 0.027s
Well, this sucks. I can't get into the phone to get to the Android Settings menu. I feel stuck. Does anybody have any ideas for me?
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714/

Thank you for the response. Unfortunately, LMSA doesn't work either . It says "This device isn't supported". I have no idea why not.
{
"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"
}

rsshilli said:
Thank you for the response. Unfortunately, LMSA doesn't work either . It says "This device isn't supported". I have no idea why not.
Click to expand...
Click to collapse
It seems that your USB debugging or OEM unlock toggle was un-ticked.
Do you have recovery available to format/reset device?
RSDLite doesn't work with your model?

Negative
Nope. I can't seem to get RSD Lite to work on Windows 10 to recognize my phone .

rsshilli said:
Nope. I can't seem to get RSD Lite to work on Windows 10 to recognize my phone .
Click to expand...
Click to collapse
It is possible to flash the stock firmware while the bootloader is locked.
BUT: You can't only flash a single image, like the boot.img. You must execute the whole fastboot commands in the same order as you can find in the flashfile.xml inside the firmware.zip!!
I don't know why, but only single commands do not work.
BEFORE TRYING THIS: Make sure you flash the correct firmware! IT MUST be the same build as currently installed!! No RETAIL version or an older build version!

Well, that's weird
Huh. I tried LMSA tonight again just for fun and it worked fine this time. It found the image, downloaded it, and reflashed the phone to factory settings. Yay! I'm back in. I tried it many times before. I know my firmware updated on the phone a few days before this happened. I guess I just needed to wait for a bit. Thank you everybody.
Ryan

WoKoschekk said:
It is possible to flash the stock firmware while the bootloader is locked.
BUT: You can't only flash a single image, like the boot.img. You must execute the whole fastboot commands in the same order as you can find in the flashfile.xml inside the firmware.zip!!
I don't know why, but only single commands do not work.
BEFORE TRYING THIS: Make sure you flash the correct firmware! IT MUST be the same build as currently installed!! No RETAIL version or an older build version!
Click to expand...
Click to collapse
For next time, how does one find the exact firmware needed? I could never figure that out.

rsshilli said:
For next time, how does one find the exact firmware needed? I could never figure that out.
Click to expand...
Click to collapse
Code:
fastboot getvar all