Apologies if I'm asking anything blatantly obvious, I'm relatively new to all things Android..
The Nexus 7 I have won't boot it just displays the Google logo & an open padlock.
I've been advised to try the Nexus Root Toolkit & it's Soft-Bricked/Bootloop option.. unfortunately this doesn't work:
erasing 'boot'
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
erasing 'cache'...
erasing 'recovery'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
erasing 'system'
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
erasing 'userdata'
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
sending 'bootloader' (3911 KB)
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
archive does not contain 'boot.sig'
error: out of memory
Any help would be greatly appreciated
Thanks.
If the padlock is opened chances are there is a custom recovery see if u can boot into it. Hold volume up and down together and power
Sent from my SGH-T679 using Tapatalk
...Awesome... said:
If the padlock is opened chances are there is a custom recovery see if u can boot into it. Hold volume up and down together and power
Sent from my SGH-T679 using Tapatalk
Click to expand...
Click to collapse
Nope, I can't do that.. it just starts the bootloader & I can't select anything when it's on
The bootloader screen info is as follows:
FASTBOOT MODE
PRODUCT NAME - grouper
BOOTLOADER VERSION - 3.34
LOCK STATE - Unlocked
you might be able to soft-boot it (that is, have it boot a custom recovery without actually flashing it to the eMMC chip) as in:
Code:
C:\blech> fastboot boot eg-custom-recovery-imagefile-of-your-choice-goes-here.img
and have a look using adb at the kernel boot messages from that custom recovery's boot log (once it has finished booting)
Code:
C:\blech> adb shell dmesg > dmesg_log.txt
my guess (because fastboot erases are failing) is that it might boot but will not recognize any valid partition tables - you will see messages to that effect in the kernel log.
If that's the case, there is nothing you can do to fix it.
My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 2.526s]
finished. total time: 2.526s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.200s]
finished. total time: 0.200s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.015s]
finished. total time: 0.015s
sending 'bootloader' (2100 KB)...
OKAY [ 0.264s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.402s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
< waiting for device >
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
brad3626 said:
My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Click to expand...
Click to collapse
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
adomol said:
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
Click to expand...
Click to collapse
Thank you for the help, unfortunately, it did not work.
I followed the instructions above, but the Nexus displayed "neither up nor cac partitions found" over and over
While cmd displayed:
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.281s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.213s
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.205s
Erovia said:
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
Click to expand...
Click to collapse
Wi-Fi
I have tried every one that the NRT offered.
Just read this guide and download the latest factory image from here.
Good luck.
Erovia said:
Just read this guide and download the latest factory image from here.
Good luck.
Click to expand...
Click to collapse
I read that guide.
But that guide seems to be written with the assumption that the device can boot into the OS
No ADB device is found because I can only boot into bootloader.
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Erovia said:
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Click to expand...
Click to collapse
Following from "Extract the Factory Image" part, this is what I am getting:
C:\Users\Brad>cd \Users\brad\AppData\Local\Android\android-sdk\platform-tools
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
XXX fastboot
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>adb reboot-bootlo
ader
error: device not found
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlo
ck
...
FAILED (command write failed (Unknown error))
finished. total time: 0.590s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase bo
ot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase ca
che
erasing 'cache'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase re
covery
erasing 'recovery'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.022s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase sy
stem
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase us
erdata
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.018s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot flash bo
otloader bootloader-grouper-4.23.img
error: cannot load 'bootloader-grouper-4.23.img': Invalid argument
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Erovia said:
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Click to expand...
Click to collapse
lock state - unlocked
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Erovia said:
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Click to expand...
Click to collapse
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
error: out of memory
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Erovia said:
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Click to expand...
Click to collapse
I restarted, ran cmd as admin and tried every USB port and got this as the result each time:
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: XXX
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4992 KB)...
OKAY [ 5.460s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 8.518s
The Nexus was frozen at this point and had to be manually forced to restart bootloader.
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Erovia said:
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Click to expand...
Click to collapse
Thanks for your help
I bought it 13 months ago (perfect timing, coincidentally, right?), so if I could find the receipt I would still be screwed.
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Erovia said:
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Click to expand...
Click to collapse
fastboot oem lock
...
(bootloader) Bootloader is locked now.
OKAY [ 36.032s]
finished. total time: 36.032s
But then the N7 freezes and after manually restarting in bootloader it is still unlocked.
Then send is as it is. You can't do any more about it.
Good luck.
Hi,
Today i tried to flash TWRP on my Mate 8 (again) and i became this error message:
>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (25236 KB)...
OKAY [ 0.727s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.736s
A few information about my device:
Android 7.0
EMUI 5.0
OEM Unlock disabled and greyed out
bootloader unlocked
Sorry for my bad English!
UselessIdiot said:
Hi,
Today i tried to flash TWRP on my Mate 8 (again) and i became this error message:
>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (25236 KB)...
OKAY [ 0.727s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.736s
A few information about my device:
Android 7.0
EMUI 5.0
OEM Unlock disabled and greyed out
bootloader unlocked
Sorry for my bad English!
Click to expand...
Click to collapse
I think u must unlock your phone bootloader again.
Same error happened to me after updated my phone to b580
Ww222 said:
I think u must unlock your phone bootloader again.
Same error happened to me after updated my phone to b580
Click to expand...
Click to collapse
I tried but I became an error message again:
>fastboot oem relock [Unlockcode]
...
FAILED (remote: root type is risk)
finished. total time: 0.007s
Or:
>fastboot oem unlock [Unlockcode]
...
FAILED (remote: Command not allowed)
finished. total time: 0.015s
I have my old unlock code but i dont know if it is the same because i have the test key preblem
UselessIdiot said:
I tried but I became an error message again:
>fastboot oem relock [Unlockcode]
...
FAILED (remote: root type is risk)
finished. total time: 0.007s
Or:
>fastboot oem unlock [Unlockcode]
...
FAILED (remote: Command not allowed)
finished. total time: 0.015s
I have my old unlock code but i dont know if it is the same because i have the test key preblem
Click to expand...
Click to collapse
Is USB debugging on?
If yes reinstall stock rom again
If no turn it on
Ww222 said:
Is USB debugging on?
If yes reinstall stock rom again
If no turn it on
Click to expand...
Click to collapse
USB debugging is on.
But is it possible to install a rom without twrp/custom recovery?
If yes, How?
Thank you for your help! :good:
UselessIdiot said:
USB debugging is on.
But is it possible to install a rom without twrp/custom recovery?
If yes, How?
Thank you for your help! :good:
Click to expand...
Click to collapse
1.Unroot your phone if rooted
2.install stock recovery
3.install stock rom using dload method
(Be sure download correct rom to your Device)
Ww222 said:
1.Unroot your phone if rooted
2.install stock recovery
3.install stock rom using dload method
(Be sure download correct rom to your Device)
Click to expand...
Click to collapse
It worked. THANK YOU VERRY MUCH!
UselessIdiot said:
It worked. THANK YOU VERRY MUCH!
Click to expand...
Click to collapse
Wlcm
fastboot flash recovery recovery.img will not work on EMUI-8 the proper method is:-
fastboot flash recovery_ramdisk (filename).img
dont know how ive done it but removed everything of the phone :crying: all i can do is get into bootloader
twrp is giving me this
fastboot boot twrp-3.2.3-1-fajita.img
downloading 'boot.img'...
OKAY [ 0.698s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.714s
cant sideload
any ideas im out of them
thanks
Msmdownload see in guide news section select the one fitted for your model
My Mate originally is L29C636 running on Nougat beta (I forgot the exact version)
Because I wanted to get Oreo, I downgrading to MM using rollback package, debrand to DL00 (Which I think unsuccessful) and then flash DL00 ROM. Along the way I think I mess up pretty badly. In MM TWRP I tried to flash Oreo ROM and it stuck halfway. I think the fastboot and EMUI dload got replaced during this process.
Now what is working are I can boot fastboot and it show my device is unlocked. eRecovery also can be accessed. EMUI dload can also be accessed. Don't have TWRP and no System/OS so can't boot up.
In fastboot I can't flash anything at all it seems. Oreo/Nougat/MM TWRP recovery, Nougat and MM system.img/userdata.img/cust.img/cache.img, all failed. I manage to get some info on my current brand:
Code:
C:\SDK\android-sdk-windows\platform-tools>fastboot oem get-product-model
...
(bootloader) NEXT
OKAY [ 0.003s]
finished. total time: 0.004s
C:\SDK\android-sdk-windows\platform-tools>fastboot oem get-build-number
...
(bootloader) :NXT-C00B103
OKAY [ 0.004s]
finished. total time: 0.005s
C:\SDK\android-sdk-windows\platform-tools>fastboot getvar vendorcountry
vendorcountry: dualcu/cn
finished. total time: 0.003s
C:\SDK\android-sdk-windows\platform-tools>fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.020s
C:\SDK\android-sdk-windows\platform-tools>fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.014s
With eRecovery, it always "Getting package info failed" message. I've tried changing my wifi DNS to 81.177.139.39 and also 188.225.84.142 but both same result. Maybe because my oeminfo all screw up?
In EMUI dload I tried using UPDATE.APP from L29C636's Nougat and MM, both fail. Oreo "DL00C17B828 (8.0.0.828) " and "DL00C17B839 (8.0.0.839)" also fail, but using HuaweiUpdateExtractor_0.9.9.5 when I tried to open UPDATE.APP content, it give
Code:
RECOVERY_RAMDIS.img: Invalid header crc - Expected: 65161 Got: 27292
So I don't know is it Oreo ROM not compatible with HuaweiUpdateExtractor? But the file that come together in the zip "update_NXT-DL00_dualcu_cn.app" content can be viewed by HuaweiUpdateExtractor, thought when I try to fastboot flash CUST.img and USERDATA.img that I extracted from "update_NXT-DL00_dualcu_cn.app", it still getting FAILED message.
I'm really out of idea now whats more can I do. I already spend tens of hours trying different ways or combination and reading as many info to see if I missed out something. If anyone can give some suggestion what else should I try, I really appreciate it. :crying: :fingers-crossed: