hey i may have messed up my nexus 6 already. unlocked the bootloader, rooted it with no problem. downloaded the twrp from play store and installed. got an install error. i looked online for someone having the issue and they said they got error and booted into recovery and it was working. i did the same. once in recovery i did a hard reset just to see if it was working, it worked. after that i hit fix permissions. and then phone would never boot. i was a little drunk so i went into recovery again, and wiped but this time i checked system. not smart i know, but what can i say. now phone boots upto google screen with unlock icon? what do i do?
Reflash factory imagine
Boot into the bootloader and flash the factory image.
Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
El Daddy said:
Boot into the bootloader and flash the factory image.
Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
when i downloaded factory image and flash all like in guide i keep getting an error saying fast boot is not recognized as an internal or external command. i have adb set up because when i did the test and got an adb version back.
uncfan44 said:
when i downloaded factory image and flash all like in guide i keep getting an error saying fast boot is not recognized as an internal or external command. i have adb set up because when i did the test and got an adb version back.
Click to expand...
Click to collapse
Sometimes you have to install the drivers on your computer again while your phone is connected and in the boot loader.
Also, if you don't have your environment variables set up correctly, you'll have to open the command prompt from the same folder in which fastboot.exe lies. As well as putting the image files in that folder.
Sent from my Nexus 5 using Tapatalk
and when i try to do the method 2 it says can not load file when i issue the flash bootloader command as in the guide.
uncfan44 said:
and when i try to do the method 2 it says can not load file when i issue the flash bootloader command as in the guide.
Click to expand...
Click to collapse
Make sure you have fastboot selected in bootloader and try this tool to make sure fastboot is installed in your machine properly.
http://forum.xda-developers.com/showthread.php?t=2588979
ok i went through the steps in method 2 again this time like u said with all the files in one place and got error saying data size exceeds download buffer when i went to flash the system file. phone still does the same thing where it boots to google screen whether i want it to turn on or not. ps thanks for all your help i really appreciate it!
uncfan44 said:
ok i went through the steps in method 2 again this time like u said with all the files in one place and got error saying data size exceeds download buffer when i went to flash the system file. phone still does the same thing where it boots to google screen whether i want it to turn on or not. ps thanks for all your help i really appreciate it!
Click to expand...
Click to collapse
Yep. I get the same thing saying it exceeds max download size on system.img
EDIT: Nevermind. You have to wait and let it send sparse file.
Long method works great! Thanks!
Make sure you have the newest fastboot and flash everything manually. If you don't have the newest fastboot it'll throw errors.
12MaNy said:
Yep. I get the same thing saying it exceeds max download size on system.img
EDIT: Nevermind. You have to wait and let it send sparse file.
Long method works great! Thanks!
Click to expand...
Click to collapse
here is my command line log maybe someone can see the error im having from this.
C:\android\platform-tools>fastboot flash bootloader C:\android\platform-tools\bo
otloader-shamu-moto-apq8084-71.05.img
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.391s]
finished. total time: 0.515s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash radio C:\android\platform-tools\radio-s
hamu-d4.0-9625-02.55.03a.img
sending 'radio' (67170 KB)...
OKAY [ 2.106s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.931s]
finished. total time: 3.039s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash system C:\android\platform-tools\system
.img
sending 'system' (1640227 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.005s
C:\android\platform-tools>
uncfan44 said:
here is my command line log maybe someone can see the error im having from this.
C:\android\platform-tools>fastboot flash bootloader C:\android\platform-tools\bo
otloader-shamu-moto-apq8084-71.05.img
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.391s]
finished. total time: 0.515s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash radio C:\android\platform-tools\radio-s
hamu-d4.0-9625-02.55.03a.img
sending 'radio' (67170 KB)...
OKAY [ 2.106s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.931s]
finished. total time: 3.039s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash system C:\android\platform-tools\system
.img
sending 'system' (1640227 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.005s
C:\android\platform-tools>
Click to expand...
Click to collapse
You have the latest fastboot installed? Also the system image from Google was extracted to platform tools? And lastly did u check md5 of original download?
Definitely not something wrong with the commands your using.
yep installed latest fastboot like they told me b4 and i put it in platform tools just to have it in same folder i opened cmd in, someone suggested that too i think so i did it. thats why im baffled as to y it wont work.
uncfan44 said:
yep installed latest fastboot like they told me b4 and i put it in platform tools just to have it in same folder i opened cmd in, someone suggested that too i think so i did it. thats why im baffled as to y it wont work.
Click to expand...
Click to collapse
I know im a little late but you can just use wugfresh nexus toolkit and flash back to stock.
Related
I recently rooted my Sprint Nexus 6 and everything was going fine. But then I started to run into issues when running the disabling the decryption. I was able to resolve those and install Pure Rom and customize it to my liking before taking a backup. But I logged into my WiFi immediately when setting up that phone. Soon after I turned off the wifi when stepping out, and I saw an Exclamation Point show up next to what was previously a semi full signal strength meter. I tried calling a few numbers and nothing was working.
I updated my PRL to the latest prior to rooting, etc. I know that this is a risk when you root, but does anyone know a possible solution?
My Recovery, ADB, Fastboot and everything works, I just can't get the signal.
I have also tried to update with the factory image from google:
https://developers.google.com/android/nexus/images
It does seem to update the Radio and a few other things, but ultimately fails:
pkalaria-ltm:tools pkalaria$ bash ./flash-all.sh
< waiting for device >
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.121s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.378s]
finished. total time: 0.499s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (67170 KB)...
OKAY [ 2.109s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.905s]
finished. total time: 3.015s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(96115,0xa11b21a8) malloc: *** mach_vm_map(size=1681272832) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679592636 bytes
error: update package missing system.img
pkalaria-ltm:tools pkalaria$
Click to expand...
Click to collapse
Any help is appreciated, thanks.
Pl2lNCE said:
I recently rooted my Sprint Nexus 6 and everything was going fine. But then I started to run into issues when running the disabling the decryption. I was able to resolve those and install Pure Rom and customize it to my liking before taking a backup. But I logged into my WiFi immediately when setting up that phone. Soon after I turned off the wifi when stepping out, and I saw an Exclamation Point show up next to what was previously a semi full signal strength meter. I tried calling a few numbers and nothing was working.
I updated my PRL to the latest prior to rooting, etc. I know that this is a risk when you root, but does anyone know a possible solution?
My Recovery, ADB, Fastboot and everything works, I just can't get the signal.
I have also tried to update with the factory image from google:
https://developers.google.com/android/nexus/images
It does seem to update the Radio and a few other things, but ultimately fails:
Any help is appreciated, thanks.
Click to expand...
Click to collapse
I'm also on Sprint and had the same issue myself, I thinking that since these ROMs are so new that maybe they need our APNs added or something.
Maybe there is another way around this issue for the time being but I didn't investigate it further, I just didn't have time.
Mistertac said:
I'm also on Sprint and had the same issue myself, I thinking that since these ROMs are so new that maybe they need our APNs added or something.
Maybe there is another way around this issue for the time being but I didn't investigate it further, I just didn't have time.
Click to expand...
Click to collapse
I found a workaround, you can manually flash the images inside image-shamu-lrx21o.zip:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Click to expand...
Click to collapse
I just flashed the decrypted boot.img, system, userdata, and cache and I was good to go. Fresh install of Stock Rom without Envrcption., and I was able to Update the PRL/Device Config. Now just gotta get it set up and Root again.
Hi!
I'm trying to flash the stock image and I'm getting an error...
Code:
mw:shamu-lrx21o$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.136s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.339s]
finished. total time: 0.474s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (67170 KB)...
OKAY [ 2.649s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.712s]
finished. total time: 3.361s
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(4484,0xa0ead1d4) malloc: *** mach_vm_map(size=1681272832) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679592636 bytes
error: update package missing system.img
mw:shamu-lrx21o$
Does anybody know what this means, and why this is happening?
wiz561 said:
Hi!
I'm trying to flash the stock image and I'm getting an error...
Does anybody know what this means, and why this is happening?
Click to expand...
Click to collapse
Try method # 2. It'll work just fine..
http://forum.xda-developers.com/showthread.php?t=2954008
Sent from my Nexus 7 using Tapatalk
BRKotucs said:
Try method # 2. It'll work just fine..
http://forum.xda-developers.com/showthread.php?t=2954008
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick response. I did the manual, and it went through everything fine. When I rebooted, I got an android that had a warning sign on it. I couldn't do the factory reset, but it booted up to some dancing balls. At this point, it was stuck here for quite some time. Tried to do it again (manual method), and same thing. Tried to flash TWRP, and it flashed TWRP for a quarter second and then rebooted again. Flashed it again doing the auto method, same errors. Ran through the manual method, and this time, it luckily booted up just fine.
I am a little uneasy that I can't boot to recovery, but maybe I'll wait a few more hours and get use to the device. I mostly want that damn att ding gone. When I ran through the 'oem erase', I get a permission denied. But again, this is for a different thread.
So.... my question is why did Google release something that doesn't work in auto mode? Is it just because I have the ATT version of the Nexus, or is it really broke?
wiz561 said:
Thanks for the quick response. I did the manual, and it went through everything fine. When I rebooted, I got an android that had a warning sign on it. I couldn't do the factory reset, but it booted up to some dancing balls. At this point, it was stuck here for quite some time. Tried to do it again (manual method), and same thing. Tried to flash TWRP, and it flashed TWRP for a quarter second and then rebooted again. Flashed it again doing the auto method, same errors. Ran through the manual method, and this time, it luckily booted up just fine.
I am a little uneasy that I can't boot to recovery, but maybe I'll wait a few more hours and get use to the device. I mostly want that damn att ding gone. When I ran through the 'oem erase', I get a permission denied. But again, this is for a different thread.
So.... my question is why did Google release something that doesn't work in auto mode? Is it just because I have the ATT version of the Nexus, or is it really broke?
Click to expand...
Click to collapse
There seems to be an issue when executing the flas-all.bat script but the manual method works just fine.
Flashing the stock images won't get rid of the att stuff I believe. You might wanna check here http://forum.xda-developers.com/showthread.php?t=2947581 for more info.
Sent from my Nexus 7 using Tapatalk
BRKotucs said:
There seems to be an issue when executing the flas-all.bat script but the manual method works just fine.
Flashing the stock images won't get rid of the att stuff I believe. You might wanna check here http://forum.xda-developers.com/showthread.php?t=2947581 for more info.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes sir.... I started there but when executing the 'oem erase', it says something about permission being denied. That's why I thought I would flash it back to stock and see what happens...which then led me to this problem.
I appreciate the response but still kind of tasting the waters with the Nexus 6 phone. It's my first Nexus and it's quite an adjustment.
I'm having some difficulty flashing Marshmallow onto my Nexus 6. It is the first time I am flashing a rom onto this.
I'm running Linux for this. (Mint 17.2) as I ran into trouble with Windows 10 and OSX El Capitan and recognising my device.
I've got the rom unpacked but when I go to flash with flash-all.sh I get an error.
Code:
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 4.620s
It then dumps me back to the bootloader on the device. I did come across this thread from a while back.
http://forum.xda-developers.com/nexus-6/help/flash-factory-images-flashing-image-t2948624/page3
It hasn't resolved my problem. I've tried following the long method for installing the rom but it isn't working. I can't get the first stage to execute. I don't seem to actually have a file called bootloader.img anywhere. Is that the problem? Is it missing in this rom?
I'm perfectly happy to completely wipe the device. (It is only 3 days old) I just want to get the stock firmware up and running.
spudbynight said:
I'm having some difficulty flashing Marshmallow onto my Nexus 6. It is the first time I am flashing a rom onto this.
I'm running Linux for this. (Mint 17.2) as I ran into trouble with Windows 10 and OSX El Capitan and recognising my device.
I've got the rom unpacked but when I go to flash with flash-all.sh I get an error.
It then dumps me back to the bootloader on the device. I did come across this thread from a while back.
http://forum.xda-developers.com/nexus-6/help/flash-factory-images-flashing-image-t2948624/page3
It hasn't resolved my problem. I've tried following the long method for installing the rom but it isn't working. I can't get the first stage to execute. I don't seem to actually have a file called bootloader.img anywhere. Is that the problem? Is it missing in this rom?
I'm perfectly happy to completely wipe the device. (It is only 3 days old) I just want to get the stock firmware up and running.
Click to expand...
Click to collapse
Looks like your fastboot binary is out of date. Did you get it from the latest sdk?
I've downloaded the SDK, but (yes, noob alert) I can't figure out how to actually install it.
I've downloaded fastboot from the terminal and it says I have the latest version.
OK - I installed the SDK. I followed the instructions here
When attempting to flash it seems to go a little bit further but is still failing.
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.394s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.693s]
finished. total time: 1.087s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (115487 KB)...
OKAY [ 4.084s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.555s]
finished. total time: 5.639s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: moto-apq8084-71.15
Baseband Version.....: D4.01-9625-05.27+FSG-9625-02.104
Serial Number........: ZX1G425T8L
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (8197 KB)...
OKAY [ 0.269s]
writing 'boot'...
OKAY [ 0.125s]
sending 'recovery' (8915 KB)...
OKAY [ 0.300s]
writing 'recovery'...
OKAY [ 0.133s]
sending 'system' (2043261 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.841s
From there I went into the "long way" and flashed the files individually from system.img
I selected recovery and rebooted. I got an Android with a red triangle but held power and volume up. The phone rebooted without me being asked to wipe data/factory reset.
Currently booted up and restoring. How do I check this is stable? I want to make sure I get OTA updates...
So the bootloader and radio worked, then it failed. Is this using the flash-all script?
I'd try extracting the contents of image-shamu-mra58k.zip and flashing each of them manually with fastboot. I've had trouble like that when using the flash-all script.
KnifeSkills said:
So the bootloader and radio worked, then it failed. Is this using the flash-all script?
I'd try extracting the contents of image-shamu-mra58k.zip and flashing each of them manually with fastboot. I've had trouble like that when using the flash-all script.
Click to expand...
Click to collapse
Sorry, I edited my post with an update...
This seems to be working OK now on Marshmallow.
How do I ensure I get OTA updates from here? Do I need to lock the bootloader again?
spudbynight said:
This seems to be working OK now on Marshmallow.
How do I ensure I get OTA updates from here? Do I need to lock the bootloader again?
Click to expand...
Click to collapse
Nope. Just stay 100% stock. No root, no mods.
Cheers
folks
I installed N preview 4 on my nexus 6 and it seemed successful but it's constantly booting back into recovery. What do I do so it boots into the actual OS?
Thanks
sam008 said:
folks
I installed N preview 4 on my nexus 6 and it seemed successful but it's constantly booting back into recovery. What do I do so it boots into the actual OS?
Thanks
Click to expand...
Click to collapse
reflash
Already did, didn't help
how are you flashing N?
Do a factory reset from recovery, that might help.
Edit: I'm assuming you're on stock recovery.
---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------
simms22 said:
how are you flashing N?
Click to expand...
Click to collapse
This... what did you exactly do?
This phone has had quite a few modifications - it ran cataclysm before. Bootloader is unlocked. Then it ran preview 3. Now, I did a factory reset first and then did a flash-all using instructions on method 2 of this page
forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
On rebooting, it always comes back to Recovery (TWRP 3.0.2-2)
From recovery, I tried doing Reboot-System and it still comes back into recovery
Should I try flashing stock firmware - can someone provide me a link?
Thanks
sam008 said:
This phone has had quite a few modifications - it ran cataclysm before. Bootloader is unlocked. Then it ran preview 3. Now, I did a factory reset first and then did a flash-all using instructions on method 2 of this page
forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
On rebooting, it always comes back to Recovery (TWRP 3.0.2-2)
From recovery, I tried doing Reboot-System and it still comes back into recovery
Should I try flashing stock firmware - can someone provide me a link?
Thanks
Click to expand...
Click to collapse
the latest 6.0.1, it flashes the same way https://dl.google.com/dl/android/aosp/shamu-mob30m-factory-55e10749.tgz
I have the version of nexus 6 - will this link work or should I use another one? thx
Strange error at the end - I opened image-shamu-mob30m and it seems it does have all the required .img files
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.328s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.567s]
finished. total time: 0.898s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (115508 KB)...
OKAY [ 4.698s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.524s]
finished. total time: 6.227s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 2098202380 bytes
error: update package missing system.img
Press any key to exit...
It does have all the required img. How are you flashing it?
I flash it manually file by file and it never fails.
sam008 said:
Strange error at the end - I opened image-shamu-mob30m and it seems it does have all the required .img files
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.328s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.567s]
finished. total time: 0.898s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (115508 KB)...
OKAY [ 4.698s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.524s]
finished. total time: 6.227s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 2098202380 bytes
error: update package missing system.img
Press any key to exit...
Click to expand...
Click to collapse
instead of using flash-all, flash each partition separate.
Flash all doesn't work. Flash each partition.
Eg:
Fastboot flash bootloader bootloader-xxx. Img
Fastboot reboot-bootloader
Fastboot flash radio radio-xxx.img
Fastboot reboot-bootloader
Fastboot flash recovery recovery.img
..... And so on.....
Sent from my Nexus 6 using Tapatalk
mannrecaged said:
Flash all doesn't work. Flash each partition.
Eg:
Fastboot flash bootloader bootloader-xxx. Img
Fastboot reboot-bootloader
Fastboot flash radio radio-xxx.img
Fastboot reboot-bootloader
Fastboot flash recovery recovery.img
..... And so on.....
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
The flash-all.bat file DOES work as long as you have the latest version of Fastboot, which can be obtained by following the instructions under "Flashing Instructions" here. That being said I prefer to flash each image file separately as mentioned above. That method has never failed me and it is easier to see what the error is if any occur.
I just used the flash-all.bat file
Hi,
I was trying to reflash everything on my phone and wipe. When I boot into fastboot and run fastboot -w, I get an error saying Download is not allowed on locked device. Im using platform tools 29.05.
ahsank128 said:
Hi,
I was trying to reflash everything on my phone and wipe. When I boot into fastboot and run fastboot -w, I get an error saying Download is not allowed on locked device. Im using platform tools 29.05.
Click to expand...
Click to collapse
Does the bootloader screen show unlocked?
Have you tried to run the flashing unlock again?
Mackay53 said:
Does the bootloader screen show unlocked?
Have you tried to run the flashing unlock again?
Click to expand...
Click to collapse
Okay, so I locked the bootloader, and unlocked it again. Successfully flashed. But I am geting the following message
"Erase successful, but not automatically formatting. File system type raw not supported"
I cant run the fastboot format (partition) command. I am on latest platform tools and latest factory image
ahsank128 said:
Okay, so I locked the bootloader, and unlocked it again. Successfully flashed. But I am geting the following message
"Erase successful, but not automatically formatting. File system type raw not supported"
I cant run the fastboot format (partition) command. I am on latest platform tools and latest factory image
Click to expand...
Click to collapse
Does your phone boot up? If so, I would check to see if your still getting good recognition from your pc. What does adb devices show when you enter that with your phone in transfer data mode?
Badger50 said:
Does your phone boot up? If so, I would check to see if your still getting good recognition from your pc. What does adb devices show when you enter that with your phone in transfer data mode?
Click to expand...
Click to collapse
Yes, the factory image gets flashed, but now everything seems to be on partition B as opposed to A. I believe everything was going to A when I first got the phone and did the unlock. ADB working fine, managed to root the phone. i enter ADB devices and shows serial. I can boot to fastboot. I wanted to see what would happen if I run fastboot flashing unlock again, and it said device is unlocked
ahsank128 said:
Yes, the factory image gets flashed, but now everything seems to be on partition B as opposed to A. I believe everything was going to A when I first got the phone and did the unlock. ADB working fine, managed to root the phone. i enter ADB devices and shows serial. I can boot to fastboot. I wanted to see what would happen if I run fastboot flashing unlock again, and it said device is unlocked
Click to expand...
Click to collapse
Well, then I guess all is well for you again. Just FYI going forward, when you fastboot the factory image without the -w, it only flashes to your active slot, whereas, if you leave the -w, it'll flash to both slots, but wipe your device. This is why when I update the factory images every month without the -w, I manually change slots so I get a full flash to both slots. Many think this is overkill, however, I have never had any wonky problems for the last 2+ years with my P2XL, and now my P4XL by using this methodology :good:
Badger50 said:
Well, then I guess all is well for you again. Just FYI going forward, when you fastboot the factory image without the -w, it only flashes to your active slot, whereas, if you leave the -w, it'll flash to both slots, but wipe your device. This is why when I update the factory images every month without the -w, I manually change slots so I get a full flash to both slots. Many think this is overkill, however, I have never had any wonky problems for the last 2+ years with my P2XL, and now my P4XL by using this methodology :good:
Click to expand...
Click to collapse
Right, but the thing is I left the -w in the bat file. Even so it only flashed to b, saying device is locked. I think there is some internal issue going. Im the same guy who cant get the blackenedmod script to run properly lol
ahsank128 said:
Right, but the thing is I left the -w in the bat file. Even so it only flashed to b, saying device is locked. I think there is some internal issue going. Im the same guy who cant get the blackenedmod script to run properly lol
Click to expand...
Click to collapse
I know who you are? At least your up and running again. But yeah, sounds like your internals might be a little wonky for sure. ?
Badger50 said:
I know who you are At least your up and running again. But yeah, sounds like your internals might be a little wonky for sure. ?
Click to expand...
Click to collapse
Any idea on the best way to completely wipe the internals and flash again? This would be easy with TWRP or custom recovery, but we've some time before that is made for Android10
ahsank128 said:
Any idea on the best way to completely wipe the internals and flash again? This would be easy with TWRP or custom recovery, but we've some time before that is made for Android10
Click to expand...
Click to collapse
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:
Badger50 said:
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:
Click to expand...
Click to collapse
Will attempt this, my attempt last night was to do factory reset within the settings (when phone is booted up) and then flashed with -w. But I will try again using the stock recovery. I even changed computers, this stuff is wonky sometimes
Badger50 said:
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:
Click to expand...
Click to collapse
Code:
C:\Users\akhan37\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 5.477s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.203s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.178s
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Code:
Sending 'bootloader_b' (8761 KB) OKAY [ 0.349s]
Writing 'bootloader_b' (bootloader) Flashing Pack version c2f2-0.2-5940465
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition logfs
OKAY [ 0.435s]
Finished. Total time: 1.046s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
Sending 'radio_b' (82676 KB)
DELETED
ahsank128 said:
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Click to expand...
Click to collapse
Interesting. Just a simple experiment if your willing. Go into your platform-tools, and just double click the flash-all.bat file and see if you get the same result, or if it even initializes
ahsank128 said:
Code:
C:\Users\akhan37\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 5.477s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.203s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.178s
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Code:
Sending 'bootloader_b' (8761 KB) OKAY [ 0.349s]
Writing 'bootloader_b' (bootloader) Flashing Pack version c2f2-0.2-5940465
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition logfs
OKAY [ 0.435s]
Finished. Total time: 1.046s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
Sending 'radio_b' (82676 KB)
Click to expand...
Click to collapse
If you have done a factory reset, you also need to make sure you enable "oem unlocking" in Developer options and usb debugging before you do anything else. Flashing a factory stock image which includes the '-w' in your flash-all.bat file would come afterwards.
I am assuming you are not flashing any kernals on top? Check to make sure you are flashing the correct image, Nov and December had 3 different images each month.
Badger50 said:
Interesting. Just a simple experiment if your willing. Go into your platform-tools, and just double click the flash-all.bat file and see if you get the same result, or if it even initializes
Click to expand...
Click to collapse
Wont work from home screen (this is fine? should be in fastboot)
Looks like it flashed this time from the fastbootd screen (so damn strange)
from fastbootd screen:
Code:
Sending 'bootloader' (8761 KB) OKAY [ 0.218s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
Sending 'radio_b' (82676 KB) OKAY [ 2.180s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g8150-00041-191016-B-5945070
(bootloader) Flashing partition modem_b
OKAY [ 0.650s]
Finished. Total time: 3.090s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.051s
--------------------------------------------
Bootloader Version...: c2f2-0.2-5940465
Baseband Version.....: g8150-00041-191016-B-5945070
Serial Number........: 99171FFAZ006J5
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.069s]
Checking 'version-bootloader' OKAY [ 0.069s]
Checking 'version-baseband' OKAY [ 0.068s]
Setting current slot to 'b' OKAY [ 0.077s]
extracting boot.img (64 MB) to disk... took 0.387s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.139s]
Writing 'boot_b' OKAY [ 0.455s]
extracting dtbo.img (8 MB) to disk... took 0.025s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.310s]
Writing 'dtbo_b' OKAY [ 0.117s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB) OKAY [ 0.138s]
Writing 'vbmeta_b' OKAY [ 0.072s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.101s]
Writing 'vbmeta_system_b' OKAY [ 0.072s]
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.069s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_b' OKAY [ 0.004s]
Resizing 'system_b' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.004s]
Resizing 'vendor_b' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.004s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (2127 MB) to disk... took 15.801s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.005s]
and got stuck there
One more thing: When on stock boot image, OEM Unlock frozen on bootloader already unlock. But after flashing magsik, I can switch between allow and not allow. This is normal?
bb709394 said:
If you have done a factory reset, you also need to make sure you enable "oem unlocking" in Developer options and usb debugging before you do anything else. Flashing a factory stock image which includes the '-w' in your flash-all.bat file would come afterwards.
I am assuming you are not flashing any kernals on top? Check to make sure you are flashing the correct image, Nov and December had 3 different images each month.
Click to expand...
Click to collapse
No, this issue happens on stock kernel. And yes USB debugging and OEM Unlock both are checked. I believe the image is correct. US Unlocked Pixel from google store. file ends in 011
ahsank128 said:
Wont work from home screen (this is fine? should be in fastboot)
Looks like it flashed this time from the fastbootd screen (so damn strange)
from fastbootd screen:
and got stuck there
One more thing: When on stock boot image, OEM Unlock frozen on bootloader already unlock. But after flashing magsik, I can switch between allow and not allow. This is normal?
Click to expand...
Click to collapse
Yes, it only works in fastboot mode.
I don't think it's strange at all. I've never come across the..fastboot -w..command that you were using, which is why I suggested what I did.
Sometimes it takes a while for the script to finish. You might no have been stuck per-se, but just not patient enough. December was a big update, so it takes a little longer.
Yes, this is normal for OEM unlocking while rooted.
So...are you up and running now?
Badger50 said:
Yes, it only works in fastboot mode.
I don't think it's strange at all. I've never come across the..fastboot -w..command that you were using, which is why I suggested what I did.
Sometimes it takes a while for the script to finish. You might no have been stuck per-se, but just not patient enough. December was a big update, so it takes a little longer.
Yes, this is normal for OEM unlocking while rooted.
So...are you up and running now?
Click to expand...
Click to collapse
I am up and running, I'll check to see if I can get that script running later on
ahsank128 said:
I am up and running, I'll check to see if I can get that script running later on
Click to expand...
Click to collapse
Kinda sounds like you already got the script to work