Related
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.
Ok i will explain ...
Got my Xoom ROOTED but decided to put it back to stock, so I UNROOTED by flashing my Canadian 3.0 version, boot it up update to the 3.1 OTA and then setup my market, the XOOM FC out alot so i want to try "hacked firmware".
Boot to fastboot to flash CWM recovery, all the flash show completed OK, reboot into recovery to only found out that it's not there ... ok, try factory reset from the Recovery, all good and then the Xoom reboot ... all my data is still there, then try Setting > Private > factory reset ... all OK, but can boot into the Recovery to fully reset ... no problem, i will reflash a different version via Fastboot.
Try the US-Wifi version, all the flash/erase when OK but still at Canadian 3.1 ... then try installing ROM manager, install fine and working (of cause no Root access). Reboot and the ROM manager is gone ...
Look like the Memory of the Xoom somehow is LOCKED?
Anyone have a idea? i'm taking out the battery for 1h now and hope to have some reaction ... but still nada!!!
Help!!! Thanks
y2k-inc said:
Ok i will explain ...
Got my Xoom ROOTED but decided to put it back to stock, so I UNROOTED by flashing my Canadian 3.0 version, boot it up update to the 3.1 OTA and then setup my market, the XOOM FC out alot so i want to try "hacked firmware".
Boot to fastboot to flash CWM recovery, all the flash show completed OK, reboot into recovery to only found out that it's not there ... ok, try factory reset from the Recovery, all good and then the Xoom reboot ... all my data is still there, then try Setting > Private > factory reset ... all OK, but can boot into the Recovery to fully reset ... no problem, i will reflash a different version via Fastboot.
Try the US-Wifi version, all the flash/erase when OK but still at Canadian 3.1 ... then try installing ROM manager, install fine and working (of cause no Root access). Reboot and the ROM manager is gone ...
Look like the Memory of the Xoom somehow is LOCKED?
Anyone have a idea? i'm taking out the battery for 1h now and hope to have some reaction ... but still nada!!!
Help!!! Thanks
Click to expand...
Click to collapse
When you flashed the stock Canadian images did you relock your bootloader?
If you followed Moto's instructions completely it ends with relocking.
It sounds like you need to unlock again and go from there. You will still get the OTA updates if you are unlocked as long as you are completely stock, if that's what you're worried about.
okantomi said:
When you flashed the stock Canadian images did you relock your bootloader?
If you followed Moto's instructions completely it ends with relocking.
It sounds like you need to unlock again and go from there. You will still get the OTA updates if you are unlocked as long as you are completely stock, if that's what you're worried about.
Click to expand...
Click to collapse
Yup! Locked up so i can get OTA, since instruction are differences from person to person ... now, no mater if i unlocked it, it's look like the memory locked out ... like i have copy some files over it, and upon shutdown and restart, the file are gone on the Xoom ... it's like your CMOS on your computer only save data when it on power but lost when you shut it down (is there a backup battery on XOOM?)
Thanks
please .... any one?
Start over from scratch. If you want stock U.S. then use the U.S. stock imgs. Make sure that you use no Canadian imgs. If you want Canadian use the Canadian stock imgs. It looks like you flashed the wrong files together. I see people flashing U.S. stock then trying to root with their country imgs and it messes up. Use adb and fastboot flash moto stock imgs again, boot img, recovery img, system, erase cache, etc. Just remember if you use canadian, the you have to root with a Canadian file as well.
Sent from my Xoom using xda premium
hammer4203 said:
Start over from scratch. If you want stock U.S. then use the U.S. stock imgs. Make sure that you use no Canadian imgs. If you want Canadian use the Canadian stock imgs. It looks like you flashed the wrong files together. I see people flashing U.S. stock then trying to root with their country imgs and it messes up. Use adb and fastboot flash moto stock imgs again, boot img, recovery img, system, erase cache, etc. Just remember if you use canadian, the you have to root with a Canadian file as well.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Been there, done that the fastboot flash toke all the flash steps but after it's just "like reversed back" to the original one ... i can even ERASE everything with fastboot and the Xoom still boot up with the "old image" is there a "Short or reset button" on the Motherboard? i have toke out the battery for 10h now
Thx
Sounds like you have not changed the files in your tools folder. I use a seperate folder for stock and root. Keeps me from flashing a file wrong. Make sure that is not happening. Did you try and oem unlock and reboot, then go back to fastboot and flash?
Sent from my ADR6400L using xda premium
done that but not work
C:\SDK_tools>fastboot oem unlock
... INFO To continue, follow instructions on the device's display...
OKAY [ 52.261s]
finished. total time: 52.261s
C:\SDK_tools>fastboot erase boot
erasing 'boot'... OKAY [ 0.289s]
finished. total time: 0.289s
C:\SDK_tools>fastboot erase system
erasing 'system'... OKAY [ 0.366s]
finished. total time: 0.366s
C:\SDK_tools>fastboot erase recovery
erasing 'recovery'... OKAY [ 0.294s]
finished. total time: 0.294s
C:\SDK_tools>fastboot -w
erasing 'userdata'... OKAY [ 13.663s]
erasing 'cache'... OKAY [ 0.529s]
finished. total time: 14.192s
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.637s]
writing 'boot'... OKAY [ 0.586s]
finished. total time: 1.224s
C:\SDK_tools>fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 16.741s]
writing 'system'... OKAY [ 7.270s]
finished. total time: 24.011s
C:\SDK_tools>fastboot flash recovery recovery.img
sending 'recovery' (12288 KB)... OKAY [ 0.894s]
writing 'recovery'... OKAY [ 3.590s]
finished. total time: 4.485s
C:\SDK_tools>fastboot flash userdata userdata.img
sending 'userdata' (139233 KB)... OKAY [ 8.946s]
writing 'userdata'... OKAY [ 8.166s]
finished. total time: 17.113s
C:\SDK_tools>fastboot erase cache
erasing 'cache'... OKAY [ 3.215s]
finished. total time: 3.215s
C:\SDK_tools>fastboot oem lock
... INFO To continue, follow instructions on the device's display...
Looks like this line:
C:\SDK_tools>fastboot oem lock
... INFO To continue, follow instructions on the device's display...
might be the cause of your problem. I think if you lock you can't write.
cadiken said:
Looks like this line:
C:\SDK_tools>fastboot oem lock
... INFO To continue, follow instructions on the device's display...
might be the cause of your problem. I think if you lock you can't write.
Click to expand...
Click to collapse
Yes, why lock?
Yep if you lock you can't flash. Go in and fastboot OEM unlock. Then you can update.
Sent from my Xoom using xda premium
problem is not if the Xoom is locked or not, i have tried all possibilities so far, but some place they tell to lock it for OTA.
If it is locked you can't load any cwm or custom firmware.
Sent from my ADR6400L using xda premium
Do you means the bootloader is locked? event "fastboot oem unlock" show successful unlock?
Please elaborate?
I wish there is nvflash that you can use like the Gtablet
Yeah bootloader locked. But if it says unlocked then try a different rom.
Sent from my ADR6400L using xda premium
I have done all the Fastboot things without luck, bootloader version 1045 if anyone know how this is can be fix?
like i said, all fastboot command response with success ... so only way now is to see how can i short the memory to wipe out and restart ... any idea?
Thx
I will clear something up for you. You absolutely do NOT need to lock the bootloader for a ota.
In fact there really is NO reason to re lock the bootloader unless you are sending it for repairs.
Where over or who ever said to re lock it you should ignore them from now on.
albundy2010 said:
I will clear something up for you. You absolutely do NOT need to lock the bootloader for a ota.
In fact there really is NO reason to re lock the bootloader unless you are sending it for repairs.
Where over or who ever said to re lock it you should ignore them from now on.
Click to expand...
Click to collapse
thanks for the heads up ... i think it's needed a jtag now
anyone know how to get the SFU file out from a working Xoom so it can be used be RSD Lite for restoring?
Yeah, I think the title is enough. The factory images are live now for volantis and volantisg. Maybe we can collect here some first impressions. I am unfortunately not able to flash atm.
https://developers.google.com/android/nexus/images
Flash-all script worked like a charm, setting everything up right now
But it's not February yet.
maarten08 said:
Flash-all script worked like a charm, setting everything up right now
Click to expand...
Click to collapse
Cool man , I'm waiting for your review, , but I'm sure to flash this into my N9 tomorrow . I'm just too eager to wait any longer
Good thing I reverted my n9 back to stock. Will flash tonight. No Ota also.
Flash.sh fail
maarten08 said:
Flash-all script worked like a charm, setting everything up right now
Click to expand...
Click to collapse
Mine fails at sending 'system' (2245234 KB)...
FAILED (remote: data length is too large)
Trying to do a manual flash now... we'll see!
I'll be flashing my 9 tonight too.
I kept my 6 on Lollipop rather than running the preview on it, but yesterday I did flash the preview so that it would use M's auto backup. That way I can flash it this week and not worry about signing into apps.....which is nice during tax season.
PhoenixIce22 said:
Mine fails at sending 'system' (2245234 KB)...
FAILED (remote: data length is too large)
Trying to do a manual flash now... we'll see!
Click to expand...
Click to collapse
Do u have latest fastboot? That error was happening to others because of old fastboot. Otherwise maybe just make sure the hash matches and u have a good download and usb debugging is on.
Sent from my SM-G900V using Tapatalk
Anybody tried flashing yet? I keep getting 'system cannot be loaded' error whilst carrying out manual flash. i.e. fastboot flash system system.img etc etc
I flashed each .IMG file separately, formatted date to remove encryption, flashed TWRP, flashed fed-patcher them FIRE-ICE kernel. Running great here
I was on 5.1.1 (Latest Image). I applied the 6.0 update, now I am just sitting at the black Google Screen and it won't boot. Any suggestions???
Diesel779 said:
I flashed each .IMG file separately, formatted date to remove encryption, flashed TWRP, flashed fed-patcher them FIRE-ICE kernel. Running great here
Click to expand...
Click to collapse
Do u need fed patcher if u flash a kernel that does not force encryption? I thought you wouldn't. Haven't tried it though.
Brian
Sent from my SM-G900V using Tapatalk
Is the installing process for rooted devices the same as for the former builds?
like here:
http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
How To Flash the Factory Image, LONG METHOD
In this method each factory image is flashed separately. This should be used if you have problems with the short method and as you get more familiar with fastboot you’ll be able to flash only the images that you need for your specific requirement. For instance, you might want to only flash the stock recovery if you’re trying to take an ota and you’ve installed a custom recovery. The order that you flash the images is not important.
In the folder you extracted the factory image it’s easiest if you re-name the bootloader image file to simply bootloader and radio. Then open a Windows command window in that folder and use the fastboot commands:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w (NOTE, this command does wipe your device. It’s possible to flash the factory image without this command but if you’re going from different revision numbers of android it’s highly recommend to wipe the device)
Now open a Windows command window in the same folder that you extracted the zip file in, the one where you find recovery, system, etc. Then run the fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img [Note, flashing system takes a long time, so let it do it's thing]
fastboot flash vendor vendor.img
gt43aw said:
Do u need fed patcher if u flash a kernel that does not force encryption? I thought you wouldn't. Haven't tried it though.
Brian
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
You don't need FED patcher if you flash an already un-force-encrypted kernel. FED patcher just takes the stock kernel and un-force-encrypts it.
Haven't updated my flashing VM in a while, so likely not. I know my ADB is 1.0.32, not sure what version of fastboot I have on there. I'm a bit of a Ubuntu noob, so I'm doing lots of web researching, LOL
Be sure to update the bootloader if getting a system partition size error! For M-preview this went from 3.44.1.0123 (LMY48M) to 3.48.0.0135 (confirmed the factory image is still this for MRA58K)... Otherwise you get system partition size errors (BIG update).
I will be making a rooted/no-force-encrypt ROM and kernel as soon as I see the newer manifests on googlesource... I am assuming selinux to permissive is still required for root. Once you have it unpacked:
fastboot flash bootloader bootloader-flounder-3.48.0.0135.img
fastboot reboot-bootloader
Then flash the system and boot images:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot flash system system.img
DO NOT DO THIS if your device is using a no-force-encrypt kernel! You WILL have to factory reset! Back up OFF the device to a PC or OTG FIRST... Then you can restore.
While flashing SYSTEM it will send the update in 5 chunks - from my device:
target reported max download size of 518205818 bytes
erasing 'system'...
OKAY [ 0.869s]
sending sparse 'system' (499853 KB)...
OKAY [ 26.326s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.701s]
sending sparse 'system' (495930 KB)...
OKAY [ 25.524s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 20.212s]
sending sparse 'system' (495450 KB)...
OKAY [ 25.732s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.792s]
sending sparse 'system' (443364 KB)...
OKAY [ 22.984s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.222s]
sending sparse 'system' (310634 KB)...
OKAY [ 16.188s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 12.593s]
finished. total time: 209.162s
NOOB Question:
where can I get the Information if my kernel is "no-force-encrypt kernel"?
I'm using the stock kernel 3.10.40 (28.jul) build LMY48M (rooted)
UDPATE:
in Settings -> security -> enrcypt tablet-> encrypted: means "force-encrypt kernel"?
Deleted
No force encryption stock kernel
For those who want to flash Marshmallow immediately but wanted to keep the device un-encrypted, download this zip, extract the boot image and flash through fastboot.
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.