hi , i have rooted my n1 and loaded ( recovery-RA-nexus-v1.5.3) into it , but because i had problems with the wifi i decided to flash back the original rom , i did everything as instructed , but when i booted my n1 i get stuck on the boot image with the unlock , can you help me please ?
Can you boot into recovery or fastboot and reflash a known good image (download one and check the md5)? If you can get into recovery then you should be able to reflash without any problems.
Wipe the phone with recovery then try the new rom and radio that got leaked today. I am using it with no issues. In this post there is update.zip that you can flash using recovery if you are having issues with fastboot.
http://forum.xda-developers.com/showthread.php?t=632187
yes i can log to fastboot i will try and let you know what will happen
I had to wipe my SD card after rooting and installing Boot rom.
its not working
hi , i did try to flash Passion_Google_WWE_1.07.1700.1
i keep getting the following
Aegean-iMac:1.1-nexusone-superboot apple$ ./fastboot-mac flash boot PASSIMG_Passion_Google_WWE_107.zip
sending 'boot' (80061 KB)... OKAY
writing 'boot'... FAILED (remote: image error! (BootMagic check fail))
aegean-iMac:1.1-nexusone-superboot apple$
the zip file size is 82 MB on disk (81,983,271 bytes)
and when i try to flash it through the recovery mood i end up with " cant open /sdcard/..... (bad )
i did try to download different roms with the same rustles what im doing wrong ?
I was working on an interesting app on my N7 (grouper). I left it on for about a week after the week I found the N7 stuck in a boot loop. I can get it into the boot loader and can do fastboot things but I can't flash a recovery or rom.
I get this error when I try.
sending 'recovery' (7766 KB)...
OKAY [ 1.013s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 4.848s
I was able to get to the recovery splash screen if I booted recovery (no flash) but thats it.
Trying to start from the bootloader gives me a "Booting failed" error.
My guess is I managed to cook the flash so no more writing or reading is possible. What say you fine fellows have I made it into masonry?
Can you boot into stock recovery.If yes try factory reset otherwise
Try the wugs toolkit
It has options to restore your phone
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.
So i have been trying to flash TWRP 3.0.0.1 onto my phone using the guide, http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928, and at first when i got to step 2 and tried to flash TWRP file, it would say "error: cannot load twrp.img"
and that went away and i was finally able to flash it after installing universal adb driver.
When i flash it i get this:
C:\SDK\android-sdk-windows\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 494927872 bytes
sending 'recovery' (16904 KB)...
OKAY [ 0.415s]
writing 'recovery'...
OKAY [ 0.244s]
finished. total time: 0.665s
and when i try to reboot to the bootloader, it shows up the standard stock recovery. What am i doing wrong?
please help
Also, when i do adb devices, it wont show my device. But i saw on the forum that adb doesnt even matter.
NEVERMIND i got it to work. But now im having trouble flashing the lastest march update. It says error 7 and something about my SD card.
LifeOfNexus said:
So i have been trying to flash TWRP 3.0.0.1 onto my phone using the guide, http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928, and at first when i got to step 2 and tried to flash TWRP file, it would say "error: cannot load twrp.img"
and that went away and i was finally able to flash it after installing universal adb driver.
When i flash it i get this:
C:\SDK\android-sdk-windows\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 494927872 bytes
sending 'recovery' (16904 KB)...
OKAY [ 0.415s]
writing 'recovery'...
OKAY [ 0.244s]
finished. total time: 0.665s
and when i try to reboot to the bootloader, it shows up the standard stock recovery. What am i doing wrong?
please help
Also, when i do adb devices, it wont show my device. But i saw on the forum that adb doesnt even matter.
NEVERMIND i got it to work. But now im having trouble flashing the lastest march update. It says error 7 and something about my SD card.
Click to expand...
Click to collapse
I flashed twrp 5 times.. before it "stick" and shows up twrp recovery.
I'm new to XDA and flashing my Nexus, I had a buddy of mine unlock and flash a custom ROM on my device. I'm working on getting my system to stock and upgrading to Android 'N'. I followed the guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 I had success in flashing all the images one time and rebooted the device. Only to find that it will not start so I loaded up the bootloader once again, checking recovery, still nothing. Now I'm rerunning the flash process everything runs fine all the way up to flashing vender.img
Code:
C:\SDK\platform-tools>fastboot flash vender C:\Angler\Images\vendor.img
target reported max download size of 494927872 bytes
sending 'vender' (185129 KB)...
OKAY [ 4.528s]
writing 'vender'...
FAILED (remote: Permission denied!)
finished. total time: 4.544s
This is where I'm stuck. Thanks for any help on this matter.
Hey, no problem bro! It's called vendor, not vender, and the command is: fastboot flash vendor etc. This should solve your problem (Sorry for my english)
NHagney said:
I'm new to XDA and flashing my Nexus, I had a buddy of mine unlock and flash a custom ROM on my device. I'm working on getting my system to stock and upgrading to Android 'N'. I followed the guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 I had success in flashing all the images one time and rebooted the device. Only to find that it will not start so I loaded up the bootloader once again, checking recovery, still nothing. Now I'm rerunning the flash process everything runs fine all the way up to flashing vender.img
Code:
C:\SDK\platform-tools>fastboot flash vender C:\Angler\Images\vendor.img
target reported max download size of 494927872 bytes
sending 'vender' (185129 KB)...
OKAY [ 4.528s]
writing 'vender'...
FAILED (remote: Permission denied!)
finished. total time: 4.544s
This is where I'm stuck. Thanks for any help on this matter.
Click to expand...
Click to collapse
I'm a Linux guy so you may wish to take this with a grain of salt. I have a vague memory of the same error and it was a case of a misspelled and/or miscapitalized command. I am assuming 2 things -
1) everything has worked up to this point
2)the code presented is exactly what you typed on your computer
Your error may simply be that your misspelled vendor after "fastboot flash"
Thats what i get for being hung over. I'm over here trying to run this as admin all kinds of nonsense. Wondering why this went so smooth last night now running into this. I still don't have a working device. After restarting the device I don't get the OS only the initial google screen. Edit: nevermind. It just posted. TY guys. On to Android 'N' maybe Nuttybar?