OK, so I was trying to flash the Minimal Matte theme onto my N1, and I seem to have bricked the phone.
The phone now just sticks at the "X" logo when trying to boot.
I cannot access recovery - I get the exclamation mark.
I've tried download the Nexus One FRG83 system image from HTC and put it on the SD card and renamed it passimg.zip to try and get it up and running again - it did the update on the bootloader screen, but it hasn't helped.
Any ideas?
If your getting the exclamation mark, I would say the recovery has been lost somehow, and its on standard again.
Try re flashing recovery via fastboot, amon ra or clockwork, which ever one. Then re flashing whatever rom
Rellikzephyr
Sent from my Nexus One using Tapatalk
OK I've tried this and get the following
Code:
C:\AndroidSDK\tools>fastboot flash recovery d:\recovery.img
sending 'recovery' (2906 KB)... OKAY [ 0.415s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.813s
Any ideas?
ETA: I've tried several different recovery images to no avail.
tameracingdriver said:
OK I've tried this and get the following
Code:
C:\AndroidSDK\tools>fastboot flash recovery d:\recovery.img
sending 'recovery' (2906 KB)... OKAY [ 0.415s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.813s
Any ideas?
ETA: I've tried several different recovery images to no avail.
Click to expand...
Click to collapse
Did you unlock the bootloader?
Also, have you tried:
Code:
fastboot boot recovery.img
Try the nandroid back up in the recovery.
I've just unlocked the bootloader, and ran the command again and I can now get into recovery, and am now trying the CM6 ROM... so we'll see what happens...
And that has worked
Thanks very much for your help
tameracingdriver said:
And that has worked
Thanks very much for your help
Click to expand...
Click to collapse
Glad it worked out for ya ^_^
What size was the image that you've downloaded from HTC?
If it was ~5MB rather than ~90MB - you've downloaded an update, and not a full system image. That would explain why your phone wasn't working after applying it.
Jack_R1 said:
What size was the image that you've downloaded from HTC?
If it was ~5MB rather than ~90MB - you've downloaded an update, and not a full system image. That would explain why your phone wasn't working after applying it.
Click to expand...
Click to collapse
It was about 80ish Mb IIRC.
Hmm.. FRG83 Passimg.. Could you share it or a link to it?
Jack_R1 said:
Hmm.. FRG83 Passimg.. Could you share it or a link to it?
Click to expand...
Click to collapse
http://developer.htc.com/ 2nd link...
http://dl3.htc.com/RomCode/Source_and_Binaries/signed-passion-img-FRG83_0923.zip
That what you are looking for?
Yep Thanks. I'll try to see, why didn't this flash the system clean.
Related
Hi all,
I have a samsung nexus s GT-I9020 ( no rooted , no custom recovery ) and 1 week ago I received the OTA update for Ice Cream Sandwich. I updated but, after 1 week usage, I noticed serious issues with the battery. So I decided to revert back to gingerbread, by downloading a stock firmware 2.3.2-GRH78C nandroid backup and trying to do
fastboot flash boot boot.img
fastboot flash system system.img
and so on.
But I do have a problem here. When, in fastboot, I first ran fastboot flash boot boot.img I got an error on the terminal
sending 'boot' (8192 KB)...
OKAY [ 1.185s]
writing 'boot'...
FAILED (remote: Write Fail)
finished. total time: 1.191s
Click to expand...
Click to collapse
and on the phone screen I can see
FAILED exceed blocks 0x0000001e > 0x0000001c
Click to expand...
Click to collapse
Similar error happens if I try the system partition, with the following error on the terminal
sending 'system' (151476 KB)...
OKAY [ 22.184s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 22.189s
Click to expand...
Click to collapse
and on the phone screen
Invalid Magic Code 0x00000003
The phone now has a recovery image ( clockwork ) which I have been able to install, but this is not able to browse any of the filesystems available. So I was looking at some stock img files I could flash via fastboot, At the moment the phone just hangs at fastboot mode saying no boot image is available.
I am using a ubuntu oneiric 32 bit and I have the latest android sdk tools.
This is not the first time I flash images using fastboot and I really have no idea why this is happening. It might be because my android version was icecream ? I have never had issues when flashing different versions of gingerbread. Also I used the encryption feature of icecream sandwich, if this is useful for you to know.
Thank you very much, hope someone can help me with that.
Click to expand...
Click to collapse
Maybe u got bad downloads try redownloading the files and make sure u have the boot loader unlocked first.
Sent from my Nexus S 4G using xda premium
I would suggest trying to fastboot boot cwr and flashing a zip.
Sent from my Nexus S using xda premium
I cannot use CWR to flash it.
The reason is: I can start CWR but the nandroid backup I got from xda developers is not on the nexus s itself. Moreover CWR cannot browse the contentes of the sd, it says cannot open device.
Regardig the files, I have issued md5sum and they seem all right.
I am really struggling with it.
Terminal spit this out after doing the following
4. Flash CWM -
fastboot flash recovery path-to-img/CWM-grouper-recovery.img
Now it boots straight into recovery mode.
What do I do? Thank you.
EDIT: Additionally when I try to flash SU it copies fine but in recovery mode, it errors with "Couldn't open directory", and "No files found".
sending 'recovery' (122307 KB)...
OKAY [ 15.868s]
writing 'recovery'...
FAILED (remote: (InvalidSize))
finished. total time: 16.045s
Click to expand...
Click to collapse
did you check to make sure the image you are flashing is the correct size and checksum?
krelvinaz said:
did you check to make sure the image you are flashing is the correct size and checksum?
Click to expand...
Click to collapse
I think so.
EOS-grouper-20120815-20.zip - 125.2MB
The checksum is: 80bd014a06bf760de07d0ab8adc60848
ripeart said:
I think so.
EOS-grouper-20120815-20.zip - 125.2MB
The checksum is: 80bd014a06bf760de07d0ab8adc60848
Click to expand...
Click to collapse
wait. you're trying to flash a recovery? you're using a rom zip.
Here's the link to cwm for the recovery. Go to nexus 7 and install whichever version you want.
http://www.clockworkmod.com/rommanager
use that file when flashing.
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
bauwoo said:
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
Click to expand...
Click to collapse
Your command is wrong, The command to use is: fastboot flash recovery twrp.the name of your file.img
Just like @jawmail said, you're flashing twrp on the bootloader """slot""
-fastboot flash recovery ***TWPR***.img
-fastboot reboot-bootloader
When your phone reboots, using your volume keys, search for "recovery" and using the power button, confirm it.
PROFIT
bauwoo said:
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
Click to expand...
Click to collapse
Whoa! Does your phone still boot to the bootloader? If so, you're extremely lucky. Flashing a non-bootloader image to the bootloader is pretty much the only way to hard brick a Nexus. You need to take much greater care when doing these things.
Haha. Thanks. Yeah I am really lucky. My phone is working now thanks. Just coming from the S6 Edge. Very different rooting method from that, so yeah I should be way more careful. Thanks for the awesome guide, btw Heisenberg. Running PureNexus with ExperimentalX kernel. Such an amazing combo.
Heisenberg said:
Whoa! Does your phone still boot to the bootloader? If so, you're extremely lucky. Flashing a non-bootloader image to the bootloader is pretty much the only way to hard brick a Nexus. You need to take much greater care when doing these things.
Click to expand...
Click to collapse
Update: nvm, figured it out myself.
I have a similar problem. I flashed the TWRP recovery and it booted into it. Made a nandroid and an EFS backup. Copied the backups to my PC. Wanted to flash the systemless root zip. Issued adb reboot recovery and I get the little Android on his back and saying "no command". Tried flashing recovery again, got this:
sending 'recovery' (16880 KB)...
OKAY [ 0.515s]
writing 'recovery'...
OKAY [ 0.238s]
finished. total time: 0.756s.
And still, I can't boot into twrp by either method. Getting the "no command".
What gives?
Puck24 said:
Update: nvm, figured it out myself.
I have a similar problem. I flashed the TWRP recovery and it booted into it. Made a nandroid and an EFS backup. Copied the backups to my PC. Wanted to flash the systemless root zip. Issued adb reboot recovery and I get the little Android on his back and saying "no command". Tried flashing recovery again, got this:
sending 'recovery' (16880 KB)...
OKAY [ 0.515s]
writing 'recovery'...
OKAY [ 0.238s]
finished. total time: 0.756s.
And still, I can't boot into twrp by either method. Getting the "no command".
What gives?
Click to expand...
Click to collapse
Please explain how you fixed your problem so the info is there for folks in future.
Sent from my Nexus 6P
Heisenberg said:
Please explain how you fixed your problem so the info is there for folks in future.
Sent from my Nexus 6P
Click to expand...
Click to collapse
guess it's a corrupted file?
Actually, I just tried flashing it one more time, rebooted to the bootloader with the phone, not with the command. Then I also used the phone to enter into recovery, not by issuing commands. And it works
Sent from my Nexus 6P using XDA Free mobile app
Hi guys,
I need some help, I'm rooted running on the stock rom.
I was running the 6.0 L and decided to update to 6.0.1 vie fastboot.
I followed this guide (http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) section 10- and did the exact same thing.
Every thing was flashing fine till I reached system.img and this is what I get.
C:\SDK\android-sdk-windows\platform-tools\6.0.1>fastboot flash sysytem C:\SDK\android-sdk-windows\platform-tools\6.0.1\system.img
target reported max download size of 494927872 bytes
sending sparse 'sysytem' (463062 KB)...
OKAY [ 10.395s]
writing 'sysytem'...
FAILED (remote: Permission denied!)
finished. total time: 10.410s
I did not flash the recovery because it says it's optional. I proceeded with the vendor and rebooted the device. When the device starts I get a pop up saying : There's an internal problem with your device. Contact your manufacture for details.
In the setting im still on 6.0 L build but bootloader and radios are on the latest firmware.
any suggestions?
Thanks
I did some search and couldn't find a decent answer.
If this is copy/paste directly from Terminal, then you misspelled "system" in your initial command:
C:\SDK\android-sdk-windows\platform-tools\6.0.1>fastboot flash sysytem C:\SDK\android-sdk-windows\platform-tools\6.0.1\system.img
target reported max download size of 494927872 bytes
sending sparse 'sysytem' (463062 KB)...
OKAY [ 10.395s]
writing 'sysytem'...
FAILED (remote: Permission denied!)
finished. total time: 10.410s
Click to expand...
Click to collapse
Notice the bold, the command is looking for "sysytem" which does not exist. You'll be good to go, if the typo is removed.
SlimSnoopOS said:
If this is copy/paste directly from Terminal, then you misspelled "system" in your initial command:
Notice the bold, the command is looking for "sysytem" which does not exist. You'll be good to go, if the typo is removed.
Click to expand...
Click to collapse
:| facepalm...... thanks man, I should not flash things at 1 AM.
I assume I dont need to flash the BL and radios again? just wipe cache install boot, system and vendor?
mr.dj26 said:
:| facepalm...... thanks man, I should not flash things at 1 AM.
I assume I dont need to flash the BL and radios again? just wipe cache install boot, system and vendor?
Click to expand...
Click to collapse
Correct, as long as you flashed the proper bootloader and radio. Just keep it all matching and you should be set. I try to avoid doing phone tinkering at night lol just never feel like troubleshooting at that time if I mess up.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Correct, as long as you flashed the proper bootloader and radio. Just keep it all matching and you should be set. I try to avoid doing phone tinkering at night lol just never feel like troubleshooting at that time if I mess up.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
lol, ya i'm falling asleep so i'll do it tomorrow, thanks again and good night.
FIXED
Hi all! Been a member of XDA for a few years now, but only just had the pleasure of becoming a nexus user. Yesterday I decided to install the Android N preview to try it out, but decided I didn't want it on my phone. So when I got home, I wiped the phone and proceeded to flash the factory image, but no matter which image I flash it, it says "error: update package missing system.img". I have tried manually flashing each file in fastboot as I have seen in many threads, but nothing is working. I have tried restoring old TWRP backups and flashing custom ROMs in TWRP, but nothing is working. Help!
This is what the Command Prompt is saying:
sending 'bootloader' (3526 KB)...
OKAY [ 0.106s]
writing 'bootloader'...
OKAY [ 0.206s]
finished. total time: 0.314s
rebooting into bootloader...
OKAY [ 0.118s]
finished. total time: 0.119s
< waiting for device >
sending 'radio' (48600 KB)...
OKAY [ 1.151s]
writing 'radio'...
OKAY [ 2.172s]
finished. total time: 3.327s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1733501396 bytes
error: update package missing system.img
Press any key to exit...
Did you download the right image from here?
Are you following THIS guide, TO THE LETTER?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Specifically step 10
irule311 said:
Did you download the right image from here?
Click to expand...
Click to collapse
Yep, straight from the Angler section. I've tried the latest one, as well as a few older ones. Nothing.
Soulfly3 said:
Are you following THIS guide, TO THE LETTER?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Specifically step 10
Click to expand...
Click to collapse
Hi, I followed the steps exactly, before updating my 6P to N developer preview, I had previously flashed the factory image. Thanks!
Unzip it yourself and flash em each manually.
Make sure you have the lastest fastboot tools. Im going to go out on a limb and say yours are out of date
Rxpert said:
Unzip it yourself and flash em each manually.
Make sure you have the lastest fastboot tools. Im going to go out on a limb and say yours are out of date
Click to expand...
Click to collapse
Tried that as well. Everything flashes, except the system.img.
g4slyness said:
Tried that as well. Everything flashes, except the system.img.
Click to expand...
Click to collapse
Had the same problem when ai first got it.
Wugs toolkit fixed me up!
http://forum.xda-developers.com/nexus-6p/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258493
The logs make me feel like the file you downloaded is corrupted. Check the md5 maybe?
Sent from my Nexus 6P using Tapatalk
g4slyness said:
Tried that as well. Everything flashes, except the system.img.
Click to expand...
Click to collapse
Probably a corrupt download, did you check the MD5 after downloading?
g4slyness said:
Tried that as well. Everything flashes, except the system.img.
Click to expand...
Click to collapse
It looks like you are not in the directory with the boot.img, et al. (your post shows no boot.img,, ... ) Make sure you unzipped the image. There are 2 files you need to unzip, the one containing the bootloader and radio. In that unzipped folder will be another zip. Unzip that second folder and you'll see the boot.img, cache.img, et al. The change in to that folder from your terminal or move those files into the folder you created (if following Heisenberg's guide), then proceed.
g4slyness said:
Hi all! Been a member of XDA for a few years now, but only just had the pleasure of becoming a nexus user. Yesterday I decided to install the Android N preview to try it out, but decided I didn't want it on my phone. So when I got home, I wiped the phone and proceeded to flash the factory image, but no matter which image I flash it, it says "error: update package missing system.img". I have tried manually flashing each file in fastboot as I have seen in many threads, but nothing is working. I have tried restoring old TWRP backups and flashing custom ROMs in TWRP, but nothing is working. Help!
This is what the Command Prompt is saying:
sending 'bootloader' (3526 KB)...
OKAY [ 0.106s]
writing 'bootloader'...
OKAY [ 0.206s]
finished. total time: 0.314s
rebooting into bootloader...
OKAY [ 0.118s]
finished. total time: 0.119s
< waiting for device >
sending 'radio' (48600 KB)...
OKAY [ 1.151s]
writing 'radio'...
OKAY [ 2.172s]
finished. total time: 3.327s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1733501396 bytes
error: update package missing system.img
Press any key to exit...
Click to expand...
Click to collapse
I think you are using an old version of fastboot. Update it and try again. Problem was fastboot couldn't allocate enough system ram to hold the whole image or something. In the newer fastboot the file transfer was broken in to several segments.
Maybe try another USB port too won't hurt.
Gytole said:
Had the same problem when ai first got it.
Wugs toolkit fixed me up!
http://forum.xda-developers.com/nexus-6p/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258493
Click to expand...
Click to collapse
Thanks!!! It actually worked. Not sure what was wrong before, seemed as though every file I downloaded off of the google website was corrupted. Cheers!
g4slyness said:
Thanks!!! It actually worked. Not sure what was wrong before, seemed as though every file I downloaded off of the google website was corrupted. Cheers!
Click to expand...
Click to collapse
You're welcome!
Like I said I had the same problem back in November. It ended up being an outdated version of fastboot like others have stated. I coyld flash my friends Moto X Pure but not my Nexus 6P..mit was awful and brain racking. Glad all is good!