Your device is corrupt ...HELP - Essential Phone Questions & Answers

I was trying to install TWRP got
writing 'recovery'...
FAILED (remote: No such partition.)
So since it was late decided to relock the boot loader
fastboot flashing lock
and now I am in panic mode since I am getting
your device is corrupt it can't be trusted and will not boot!
EDIT
sorry for the double thread
on the same page in red got a link to go to https://support.google.com/android/...26463373558015-753534547&p=verified_boot&rd=1
but how can I go back in fastboot to flash a factory image?

Actualy there is hope can boot in fastboot with power down but I tried to flash the original OPM1.170911.254_firmware.zip by unziping it and doing flash-all.bat but running into some error so I re unlock the boot loader
But stil stuck at
FAILED (remote: Flashing is not allowed for Critical Partitions
I found this command fastboot flashing unlock_critical
but now
the error message is
FAILED (remote: Flash Write Failure)

guliver365 said:
Actualy there is hope can boot in fastboot with power down but I tried to flash the original OPM1.170911.254_firmware.zip by unziping it and doing flash-all.bat but running into some error so I re unlock the boot loader
But stil stuck at
FAILED (remote: Flashing is not allowed for Critical Partitions
I found this command fastboot flashing unlock_critical
but now
the error message is
FAILED (remote: Flash Write Failure)
Click to expand...
Click to collapse
Fastboot flashing unlock_critical
But I urge you to review the firmware thread.
Sent from my PH-1 using XDA Labs

avd said:
Fastboot flashing unlock_critical
But I urge you to review the firmware thread.
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
It was exactly what I was doing before getting the last error.

guliver365 said:
It was exactly what I was doing before getting the last error.
Click to expand...
Click to collapse
You really need to review the thread.
---------- Post added at 12:14 PM ---------- Previous post was at 11:48 AM ----------
wolfu11 said:
You really need to review the thread.
Click to expand...
Click to collapse
Also the red screen fix is in this post read through it.....
https://mata.readthedocs.io/en/latest/

I went thru the thread https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
tried to flash NMJ88C_firmware.zip
got stuck for a while at:
D:\platform-tools>fastboot flash vendor_a vendor
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_a' 1/1 (0 KB)...
OKAY [ 0.092s]
writing 'vendor_a' 1/1...
OKAY [ 72.599s]
finished. total time: 72.694s
D:\platform-tools>fastboot flash vendor_b vendor
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_b' 1/1 (0 KB)...
OKAY [ 0.091s]
writing 'vendor_b' 1/1...
but continue till finish but got the orange warning about corrupted and goes back to fastboot
A little hint would be welcome.

guliver365 said:
I went thru the thread https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
tried to flash NMJ88C_firmware.zip
got stuck for a while at:
D:\platform-tools>fastboot flash vendor_a vendor
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_a' 1/1 (0 KB)...
OKAY [ 0.092s]
writing 'vendor_a' 1/1...
OKAY [ 72.599s]
finished. total time: 72.694s
D:\platform-tools>fastboot flash vendor_b vendor
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_b' 1/1 (0 KB)...
OKAY [ 0.091s]
writing 'vendor_b' 1/1...
but continue till finish but got the orange warning about corrupted and goes back to fastboot
A little hint would be welcome.
Click to expand...
Click to collapse
Once unlocked the phone will have the orange screen on boot.
The sparse format error is normal.
Not sure why you go back to fastboot.
I'm on Oreo B3 and have no issues flashing.

avd said:
Fastboot flashing unlock_critical
But I urge you to review the firmware thread.
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
tech_head said:
Once unlocked the phone will have the orange screen on boot.
The sparse format error is normal.
Not sure why you go back to fastboot.
I'm on Oreo B3 and have no issues flashing.
Click to expand...
Click to collapse
Now it' s getting worse I did fastboot -w
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.002s
Any way I did
flash-all.bat
NMJ88C_back_to_stock
and now the phone is dead no booting even vol down and power result to nothing!

guliver365 said:
Now it' s getting worse I did fastboot -w
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.002s
Any way I did
flash-all.bat
NMJ88C_back_to_stock
and now the phone is dead no booting even vol down and power result to nothing!
Click to expand...
Click to collapse
What computer are you flashing from?
What cable are you using?
There is a known issue with the factory cable.

tech_head said:
What computer are you flashing from?
What cable are you using?
There is a known issue with the factory cable.
Click to expand...
Click to collapse
Pc windows 10
no factory cable
usb a micro usb b with adapter micro usb to type C
How can I start the phone at least in fastboot?

guliver365 said:
Pc windows 10
no factory cable
usb a micro usb b with adapter micro usb to type C
How can I start the phone at least in fastboot?
Click to expand...
Click to collapse
That cable combination is worse than the factory.
All I can say is hold the power button.
You need a real USB-C cable. No adapter.

tech_head said:
That cable combination is worse than the factory.
All I can say is hold the power button.
You need a real USB-C cable. No adapter.
Click to expand...
Click to collapse
Hopefully you didn't brick it already, sometimes it has to sit for a couple hours to come back.
Sometimes it will switch to the other slot once you flash the red screen fix.
Either way you will need to reflash the phone
Have you plugged it into the computer?
If you see Qualcomm 9008 you r screwed.
Good Luck

tech_head said:
That cable combination is worse than the factory.
All I can say is hold the power button.
You need a real USB-C cable. No adapter.
Click to expand...
Click to collapse
I have an other USB C cable https://tinyurl.com/y7uqrgdx but my MSI computer USBC port will only Fast charge it so far probably something to change in Bios
holding the power button does nothing just starting to panic!

wolfu11 said:
Hopefully you didn't brick it already, sometimes it has to sit for a couple hours to come back.
Sometimes it will switch to the other slot once you flash the red screen fix.
Either way you will need to reflash the phone
Have you plugged it into the computer?
If you see Qualcomm 9008 you r screwed.
Good Luck
Click to expand...
Click to collapse
Does not turn on at all So cannot tell if I got Qualcomm 9008 no USB action detected I will wait like you said a couple of hours hopefully I never bricked a devce like that very strange

guliver365 said:
Does not turn on at all So cannot tell if I got Qualcomm 9008 no USB action detected I will wait like you said a couple of hours hopefully I never bricked a devce like that very strange
Click to expand...
Click to collapse
Hold power button 45 seconds
Sent from my PH-1 using XDA Labs

avd said:
Hold power button 45 seconds
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Does not turn on!

Sounds like a solid brick and I would assume it's because of the USB adapter combination you were using, but I hope it's not and that you can get it up and running somehow.

Update
Not completely dead led slow blinking Until charged I supposed
Faint slow green LED blinking when maintaining power button
but more important I just noticed now detected by my computer USB C port since I got the bell when a USB device is connected also in device manger USB 3.1 become triggered
Not sure if I should keep hope!

guliver365 said:
Update
Not completely dead led slow blinking Until charged I supposed
Faint slow green LED blinking when maintaining power button
but more important I just noticed now detected by my computer USB C port since I got the bell when a USB device is connected also in device manger USB 3.1 become triggered
Not sure if I should keep hope!
Click to expand...
Click to collapse
May be booting into fast boot.
Get a good cable.

I have just got your devices is corrupt, I also see that the bootloader is locked so cant get the phone to go into download, would like some help in fixing this, I am not using the cable that come with the phone but a USB to c cable. Thanks
---------- Post added at 12:16 PM ---------- Previous post was at 12:04 PM ----------
{
"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"
}

Related

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.

[FIX] fix hard brick / qhsub_bulk after bad flash / cm12 flash from 5.1

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

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.

[HELP] Bricked phone while trying to install custom rom

I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Did you unlock critical?
Sent from my ONEPLUS 3T using Tapatalk
seabro01 said:
Did you unlock critical?
Sent from my ONEPLUS 3T using Tapatalk
Click to expand...
Click to collapse
uhh no I did not see that in the tutorial.
I tried: ./fastboot flashing unlock_critical
and looks like it freezes after that command...
ytlei said:
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Click to expand...
Click to collapse
are you rooted?
have you tried downloading the file again?
and if you can still go to bootloader your phone is not bricked, just download stock boot from essential and flash it
yenkoPR said:
are you rooted?
have you tried downloading the file again?
and if you can still go to bootloader your phone is not bricked, just download stock boot from essential and flash it
Click to expand...
Click to collapse
no not rooted
now im trying to flash back to stock, but when I run flash-all.sh error keeps popping up:
remote: Error flashing partition.
FAILED (remote: Error flashing partition.)
finished. total time: 2.025s
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.735s]
writing 'boot_b'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.782s
target reported max download size of 536870912 bytes
sending 'cmnlib_a' (512 KB)...
OKAY [ 0.103s]
writing 'cmnlib_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 0.169s
target reported max download size of 536870912 bytes
sending 'cmnlib_b' (512 KB)...
OKAY [ 0.101s]
writing 'cmnlib_b'...
FAILED (remote: Error flashing partition.)
finished. total time: 0.188s
...
Dang now its totally bricked after the flashing failure... cannot boot up. what should I do? send it back to Essential?
What do you mean by can't boot up? Do you see boot animation and have you tried to go back to fast boot or recovery?
Sent from my ONEPLUS 3T using Tapatalk
Try different USB ports and cables. When 8.1 came out I had to swap my cable and change the port I was using on my desktop, for some reason the cable I had been using and the port I had been using since I got the phone was no longer adequate. There were a number of other people having the same issue. Some commands would look to complete properly, but following up with the same command (something un-damaging like fastboot --set-active=a | fastboot --set-active=b) would either error again or show that the 'completed' command hadn't actually done anything. I switched cables/ports around (ended up with an Antek USB-A to USB-C cable in a USB3.1 port) and everything worked properly.
If you're trying to flash a stock build image from Essential, you will probably need critical unlocked because those images do contain a bootloader that gets flashed, and that is secured behind critical.
ytlei said:
Dang now its totally bricked after the flashing failure... cannot boot up. what should I do? send it back to Essential?
Click to expand...
Click to collapse
What cable are you using?
Do not use the cable that came with the phone!!!!!
We are screwed mate, I am on the same boat with you. Essential took no responsibility and offered a 200$ replacement device. The phone doesn't power on anymore and no light indicators are working, so hard bricked.
I had a Asoip screw up(did not disable password) and was only able to get fastboot. Had to see what slot was active and flashed to that slot that was active boot.img,twrp,Asoip and was back up and running. My bootloader was unlocked. I read through all the posts and peoples screw ups and was able to get it up and running again in a day. I never posted as I wanted to learn it on my own. Good luck.........
ytlei said:
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Click to expand...
Click to collapse
What cable did you use while connecting to your computer?
And what is the status now? Are you able to turn it on at all by volume and power key combination?
same here. The phone doesn't power on anymore. btw I used the usb-c TDB cable came with my MacBook pro.
I sent email to essential and they say they can't help me since I tried to flash custom rom...
ytlei said:
same here. The phone doesn't power on anymore. btw I used the usb-c TDB cable came with my MacBook pro.
I sent email to essential and they say they can't help me since I tried to flash custom rom...
Click to expand...
Click to collapse
and pressing the volume down key + power key at the same time doesn't work?.. what happens when you plug your phone into the charger? does it vibrate?
ive had fastboot command problems previously myself with this device and found that the usb port can play a pretty large factor. Swapping usb ports and reattempting to run the commands (as others recommended may be useful) make sure you are using latest version of adb/fastboot and have up to date drivers installed for the phone.
Look at the rooting tutorial there is information in there about swapping active slots (the essential has both a and b paritions) if you set the other slot as the active slot you may be able to regain some communication within fastboot (i would suggest you verify with fastboot devices prior to attempting to flash to partitions).
Additionally you should be able to still recover back to stock without custom recovery using the default recovery partition. I would think that if you are able to access the bootloader you should be able to access the default essential recovery partition. If you can access the standard recovery you should be able to factory reset the phone and sideload a new rom (id suggest the default factory image from essential until you can get back to square one)
I'm in the same boat. Tried to flash twrp after upgrading to 8.1 and got the same Error flashing partition, and now I'm stuck on the bootloader.
I've found that if I lock/unlock and lock/unlock critical it will let me flash the stock 8.1 boot and every other partition except for system and vendor, but gives a flash write error for those. I'm still unable to get past the bootloader.
Essential basically said I'm SOL. $200 out of warranty replacement assuming I live in the US, which I don't.
Mine was doing this too, but it was only a few days old so I returned it. I'm pretty sure it's defective flash memory.
My phone was doing this exact thing. Botched factory installs rendered my phone hardbricked.
Tried a thousand+ things to get it to turn on to no avail. LUCKILY I bought it second hand and have no warranty D:
I want to cry

Unable to unlock bootloader on my Asus Zenfone Max Pro M1

So, I bought a new Asus Zenfone Max Pro M1 3 GB variant today. I was really excited for it to arrive. Obviously, I wanted to install custom recovery and flash magisk on it. However, now that I'm trying to unlock the bootloader, I'm getting a message saying 'Press any key to shutdown.' What might be the problem guys? I've installed all the drivers and my OS is Windows 10 64bit with an AMD Ryzen CPU.
Help would be greatly appreciated.
Utsav_vats said:
So, I bought a new Asus Zenfone Max Pro M1 3 GB variant today. I was really excited for it to arrive. Obviously, I wanted to install custom recovery and flash magisk on it. However, now that I'm trying to unlock the bootloader, I'm getting a message saying 'Press any key to shutdown.' What might be the problem guys? I've installed all the drivers and my OS is Windows 10 64bit with an AMD Ryzen CPU.
Help would be greatly appreciated.
Click to expand...
Click to collapse
Try launching from your C drive
jide1 said:
Try launching from your C drive
Click to expand...
Click to collapse
I am launching it from my C drive. I have unlocked the BL successfully but I am unable to flash any recovery or anything now.
Utsav_vats said:
I am launching it from my C drive. I have unlocked the BL successfully but I am unable to flash any recovery or anything now.
Click to expand...
Click to collapse
Initially you said u were not able to unlock, so after unlocking why can't u flash recovery, what exactly is the issue, can u be more specific ?
jide1 said:
Initially you said u were not able to unlock, so after unlocking why can't u flash recovery, what exactly is the issue, can u be more specific ?
Click to expand...
Click to collapse
I unlocked the bootloader successfully. But now that I'm trying to flash recovery it shows error saying target didn't report max-download-size.
{
"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"
}
Utsav_vats said:
I unlocked the bootloader successfully. But now that I'm trying to flash recovery it shows error saying target didn't report max-download-size.
Click to expand...
Click to collapse
To flash recovery do the following.
Fasboot devices. (your serial number will show up)
Fastboot flash recovery ( after this command hit the space key on keyboard, then drag the .img file to the command window and hit the enter key on keyboard)
jide1 said:
To flash recovery do the following.
Fasboot devices. (your serial number will show up)
Fastboot flash recovery ( after this command hit the space key on keyboard, then drag the .img file to the command window and hit the enter key on keyboard)
Click to expand...
Click to collapse
PS C:\unlock> .\fastboot flash recovery C:\unlock\recovery.img
target didn't report max-download-size
sending 'recovery' (60364 KB)...
FAILED (command write failed (No error))
finished. total time: 0.002s
Utsav_vats said:
PS C:\unlock> .\fastboot flash recovery C:\unlock\recovery.img
target didn't report max-download-size
sending 'recovery' (60364 KB)...
FAILED (command write failed (No error))
finished. total time: 0.002s
Click to expand...
Click to collapse
Try putting the recovery.img file on desktop.
jide1 said:
Try putting the recovery.img file on desktop.
Click to expand...
Click to collapse
Okay
Utsav_vats said:
Okay
Click to expand...
Click to collapse
Thanks Sir. It worked
jide1 said:
Try putting the recovery.img file on desktop.
Click to expand...
Click to collapse
C:\adb>fastboot devices
J8AAGF056032PP7 fastboot
C:\adb>fastboot flash recovery C:\adb\twrp-3.2.2-1-20180727-X00TD.img
sending 'recovery' (58328 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
And then the phone asked me to press any key to shut down.
---------- Post added at 06:27 AM ---------- Previous post was at 06:24 AM ----------
jide1 said:
Try putting the recovery.img file on desktop.
Click to expand...
Click to collapse
This is what happened when I added the file from desktop
C:\adb>Fastboot flash recovery C:\Users\Bubai\Desktop\twrp-3.2.2-1-20180727-X00T
D.img
sending 'recovery' (58328 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.002s
My max pro m1 is 6 gb variant. Any help?
Utsav_vats said:
So, I bought a new Asus Zenfone Max Pro M1 3 GB variant today. I was really excited for it to arrive. Obviously, I wanted to install custom recovery and flash magisk on it. However, now that I'm trying to unlock the bootloader, I'm getting a message saying 'Press any key to shutdown.' What might be the problem guys? I've installed all the drivers and my OS is Windows 10 64bit with an AMD Ryzen CPU.
Help would be greatly appreciated.
Click to expand...
Click to collapse
Use windows 7. work 100%. I have same issue .that problem solved
Utsav_vats said:
I unlocked the bootloader successfully. But now that I'm trying to flash recovery it shows error saying target didn't report max-download-size.
Click to expand...
Click to collapse
How did you unlock bro? I have 4gb variant and I am having the same issue.
---------- Post added at 11:14 AM ---------- Previous post was at 11:13 AM ----------
razisafe said:
Use windows 7. work 100%. I have same issue .that problem solved
Click to expand...
Click to collapse
I have windows 10. Same problem as the OP.
jide1 said:
Try launching from your C drive
Click to expand...
Click to collapse
I am trying, but could not unlock bootloader, please help.
Pran K. said:
C:\adb>fastboot devices
J8AAGF056032PP7 fastboot
C:\adb>fastboot flash recovery C:\adb\twrp-3.2.2-1-20180727-X00TD.img
sending 'recovery' (58328 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
And then the phone asked me to press any key to shut down.
---------- Post added at 06:27 AM ---------- Previous post was at 06:24 AM ----------
This is what happened when I added the file from desktop
C:\adb>Fastboot flash recovery C:\Users\Bubai\Desktop\twrp-3.2.2-1-20180727-X00T
D.img
sending 'recovery' (58328 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.002s
My max pro m1 is 6 gb variant. Any help?
Click to expand...
Click to collapse
Yeah i have same problem, too. Also have the 6gb variant.
Wmateria said:
Yeah i have same problem, too. Also have the 6gb variant.
Click to expand...
Click to collapse
i have same problem with you, i have the 4/64 devices, i try to flashboot in windows 10.. everytimes i found that FAILED (command write failed (Invalid argument). can anybody give a suggestion to solve this problem?
baikhaqi said:
i have same problem with you, i have the 4/64 devices, i try to flashboot in windows 10.. everytimes i found that FAILED (command write failed (Invalid argument). can anybody give a suggestion to solve this problem?
Click to expand...
Click to collapse
Have you tried with a USB 2.0 adapter? That should solve the problem.
Pran K. said:
C:\adb>fastboot devices
J8AAGF056032PP7 fastboot
C:\adb>fastboot flash recovery C:\adb\twrp-3.2.2-1-20180727-X00TD.img
sending 'recovery' (58328 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
And then the phone asked me to press any key to shut down.
---------- Post added at 06:27 AM ---------- Previous post was at 06:24 AM ----------
This is what happened when I added the file from desktop
C:\adb>Fastboot flash recovery C:\Users\Bubai\Desktop\twrp-3.2.2-1-20180727-X00T
D.img
sending 'recovery' (58328 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.002s
My max pro m1 is 6 gb variant. Any help?
Click to expand...
Click to collapse
Use usb 2.0 port and windows 7
---------- Post added at 06:26 PM ---------- Previous post was at 06:22 PM ----------
Wmateria said:
Yeah i have same problem, too. Also have the 6gb variant.
Click to expand...
Click to collapse
I also have 6gb variant. Try using usb 2.0 port and windows 7/ linux.
I installed linux on my old laptop (this also worked for some users) and instead of installing windows 7 (bc i know i will run into drivers issues) i installed linux mint.
Try following my guide here. If it didnt work, post your problem there and I will see what I can do

Categories

Resources