Related
Hi everybody!! I have a BIG issue: my nexus 4 is unlocked, with the CWM recovery and CyanogenMod 10.1 installed. Due to some technical problems, I decided to flash the factory rom again (following this guide http://forum.xda-developers.com/showthread.php?t=2010312) but I can't do it!! Indeed when I try to flash the factory rom the prompt says
file:could not allocate 544035848 bytes
error:cannot load system.img :not enough space
And when i checked the system capacity the result is that my system partition doesn't exist (as you can see on the pic attached)!
I wish to send my phone back to google with the RMA (it was delivered 7 days ago) but I'm not sure that the warranty is still valid (what do you think about that?). Indeed there is no OS now, and everything is unlocked.
Anybody could help me?
Thanks a lot!!
StefanoRedi said:
Hi everybody!! I have a BIG issue: my nexus 4 is unlocked, with the CWM recovery and CyanogenMod 10.1 installed. Due to some technical problems, I decided to flash the factory rom again (following this guide http://forum.xda-developers.com/showthread.php?t=2010312) but I can't do it!! Indeed when I try to flash the factory rom the prompt says
file:could not allocate 544035848 bytes
error:cannot load system.img :not enough space
And when i checked the system capacity the result is that my system partition doesn't exist (as you can see on the pic attached)!
I wish to send my phone back to google with the RMA (it was delivered 7 days ago) but I'm not sure that the warranty is still valid (what do you think about that?). Indeed there is no OS now, and everything is unlocked.
Anybody could help me?
Thanks a lot!!
Click to expand...
Click to collapse
use the fastboot commands to erase system, boot, and data. then use flashboot to flash bootloader, then stock recovery, then stock system.
EvoXOhio said:
use the fastboot commands to erase system, boot, and data. then use flashboot to flash bootloader, then stock recovery, then stock system.
Click to expand...
Click to collapse
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?
StefanoRedi said:
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?
Click to expand...
Click to collapse
That sounds right but Fiona search to be safe. No reboots needed.
StefanoRedi said:
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?
Click to expand...
Click to collapse
I tryed to do it without results. I attach the screen.
Have you some other advises? I really don't know what i can do it with my phone. If i send it back to google, do you think that they will check if my phone is locked/unlocked, with/without os, ecc? Because I'm afraid to have wasted my money!
Have you tried booting into recovery and wiping everything before flashing system? Also you're sure you have the right system.img? Maybe re-download the files from google and try again?
---------- Post added at 09:23 AM ---------- Previous post was at 09:22 AM ----------
also, do you have any nandroids or downloaded ROMs on the phone? If so, you could try flashing CWM, and then booting into it and restoring the nandroid or installing a ROM.
R: Cannot flash system.img, df shows no system partition
We tried wiping everything trough fast boot, he does not have any nandroid backup and I think he tried to flash another ROM (cm) with no luck.
We downloaded the right images, we tried both 4.2.1 and JOP40D from the Google site and from the mirror that we found in some thread here on xda.
(I'm his friend and I was helping him via Skype, that's why I know these informations)
I think now we'll try to flash cwm and wipe everything trough it and install a stock ROM or a custom one.
Ty for the help.
Sent from my Nexus 4
squalluca said:
We tried wiping everything trough fast boot, he does not have any nandroid backup and I think he tried to flash another ROM (cm) with no luck.
We downloaded the right images, we tried both 4.2.1 and JOP40D from the Google site and from the mirror that we found in some thread here on xda.
(I'm his friend and I was helping him via Skype, that's why I know these informations)
I think now we'll try to flash cwm and wipe everything trough it and install a stock ROM or a custom one.
Ty for the help.
Sent from my Nexus 4
Click to expand...
Click to collapse
It really sounds like someone made a mistake and ran the wrong command and actually remove the /system partition. Not erased or formatted, but actually removed the mount point. I'm sure there is a way to recreate it, but I have no idea how.
R: Cannot flash system.img, df shows no system partition
That's what I think too... this error appeared before we tried any wipe/erase command trough fastboot... hope someone can help us in recrate the mount point for the system partition...
Sent from my Nexus 4
EvoXOhio said:
It really sounds like someone made a mistake and ran the wrong command and actually remove the /system partition. Not erased or formatted, but actually removed the mount point. I'm sure there is a way to recreate it, but I have no idea how.
Click to expand...
Click to collapse
Thanks guys! I really hope that someone knows how to recreate it and, if it's possibile, very soon, because the RMA expiration day is coming!!
This is generally to be avoided, but I think this may actually be a last resort situation. Download the full factory image extract down a few levels until you have flash-all.bat extracted, at that point you'll also see the radio, bootloader, an image zip, and some linux scripts. Make sure you've actually extracted them and that you aren't just looking in the zip. Run flash-all.bat Don't touch anything until it's done, if you disrupt the write to bootloader or possibly radio, you brick.
By the way, the factory image is here and you may need to use 7zip to extract it. 7zip will have shell integration, so just right click what you want, drop down to 7zip and extract to.
Also, you may be able to accomplish the same thing with:
Code:
fastboot -w update image-occam-jop40c.zip
so maybe try that first.
USSENTERNCC1701E said:
This is generally to be avoided, but I think this may actually be a last resort situation. Download the full factory image extract down a few levels until you have flash-all.bat extracted, at that point you'll also see the radio, bootloader, an image zip, and some linux scripts. Make sure you've actually extracted them and that you aren't just looking in the zip. Run flash-all.bat Don't touch anything until it's done, if you disrupt the write to bootloader or possibly radio, you brick.
By the way, the factory image is here and you may need to use 7zip to extract it. 7zip will have shell integration, so just right click what you want, drop down to 7zip and extract to.
Also, you may be able to accomplish the same thing with:
Code:
fastboot -w update image-occam-jop40c.zip
so maybe try that first.
Click to expand...
Click to collapse
Fine, I will try when I come back home. Just a question: what do you think about the warranty? Do you think that google will check if the phone is unlocked and without os? It is better for me risk with the last suggested process and (maybe) brick the phone or send it back as it is now? It's because I'm just a beginner with mod, scripts, prompts, ecc..sorry!
StefanoRedi said:
Fine, I will try when I come back home. Just a question: what do you think about the warranty? Do you think that google will check if the phone is unlocked and without os? It is better for me risk with the last suggested process and (maybe) brick the phone or send it back as it is now? It's because I'm just a beginner with mod, scripts, prompts, ecc..sorry!
Click to expand...
Click to collapse
The phone was damaged from user error. It is unethical and probably illegal to RMA it. Try to fix it yourself, and if you can't, man up and buy a new phone. RMAs are for faulty products, not products ruined by an inexperienced user doing something wrong.
EvoXOhio said:
The phone was damaged from user error. It is unethical and probably illegal to RMA it. Try to fix it yourself, and if you can't, man up and buy a new phone. RMAs are for faulty products, not products ruined by an inexperienced user doing something wrong.
Click to expand...
Click to collapse
You are completely right. I wrote that just because I messed up the phone (following guides, using toolkit, using cmd in a proper way) trying to fix it (from the first day it was impossible to call due to microphone/speaker software problem). And sometimes, while a was doing the same stuff that everybody do with good results, the phone didn't do what it was supposed to do. Consequently I wanted to RMA it because i think it's my fault (I know it and I admit it) but not completely. I really don't want to cheat anyone.
Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:
StefanoRedi said:
Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:
Click to expand...
Click to collapse
Make sure flash stock recovery and relock the device before sending it in.
EvoXOhio said:
Make sure flash stock recovery and relock the device before sending it in.
Click to expand...
Click to collapse
Of course! In theory it will not be a problem if there is the CWM recovery and if the phone it's unlucked (at least, I read that for Google and LG is not a problem), but I flashed the stock recovery and then I lucked the phone again. Thanks for your advises.
system.img cannot load, not enough space error
StefanoRedi said:
Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:
Click to expand...
Click to collapse
hey can anyone help me i have this error when i flash Stock 5.0.1 Lollipop, Kitkat flashing is working!
Hello everybody! I have a nexus 4 since a couple of months, and I had a Samsung galaxy s before. With that phone if you got stuck on a boot loop and couldn't access recovery, you used Odin to save you..what if it happens on nexus 4? Flash original image with a tool? Or there is some recovery file I can flash? Or what?
Thanks!
Sent from my Nexus 4 using xda app-developers app
It's highly unlikely that you won't be able to boot into the recovery anymore on a nexus device as the recovery is pretty much "flash once, forget forever".
Meaning, you normally don't mess with the recovery partition.
If you, for whatever reason, really can't access the recovery anymore, you can flash a new one through the bootloader using fastboot.
fastboot flash recovery recovery.img
Should be the command to do so. Just check the tutorials around here.
Nuu~ said:
It's highly unlikely that you won't be able to boot into the recovery anymore on a nexus device as the recovery is pretty much "flash once, forget forever".
Meaning, you normally don't mess with the recovery partition.
If you, for whatever reason, really can't access the recovery anymore, you can flash a new one through the bootloader using fastboot.
fastboot flash recovery recovery.img
Should be the command to do so. Just check the tutorials around here.
Click to expand...
Click to collapse
What he said, and also should be noted that if you do backups of your roms, if you ever upgraded the recovery (say TWRP) you may wish to re-do a backup after you upgrade with the recovery option checked (or don't use it at all) since I've run into a situation once where I backed up my original stock on 2.4.4.0, and when I restored it, it downgraded my 2.5.0.0 to that, didn't cause problems just some options went bye-bye until I reflashed the recovery from fastboot (and just made sure to make a flashable-zip of just that recovery just in case).
As long as you can get to the bootloader on an N4 you can do just about anything to bring your device back to life, even if it's something like erasing the userdata, then formating /data in the new recovery because *cough*me*cough* stupidly flashed a galaxy nexus recovery from goomanager.
PS: Holding down the power for 10 seconds or more is pretty much the universal kill switch, from there should be able to bring up bootloader just fine.
kbeezie said:
What he said, and also should be noted that if you do backups of your roms, if you ever upgraded the recovery (say TWRP) you may wish to re-do a backup after you upgrade with the recovery option checked (or don't use it at all) since I've run into a situation once where I backed up my original stock on 2.4.4.0, and when I restored it, it downgraded my 2.5.0.0 to that, didn't cause problems just some options went bye-bye until I reflashed the recovery from fastboot (and just made sure to make a flashable-zip of just that recovery just in case).
As long as you can get to the bootloader on an N4 you can do just about anything to bring your device back to life, even if it's something like erasing the userdata, then formating /data in the new recovery because *cough*me*cough* stupidly flashed a galaxy nexus recovery from goomanager.
PS: Holding down the power for 10 seconds or more is pretty much the universal kill switch, from there should be able to bring up bootloader just fine.
Click to expand...
Click to collapse
Try booting in safe mode https://support.google.com/nexus/4/answer/2852139?hl=nl. 3rd party apps will not boot in that mode.
gee2012 said:
Try booting in safe mode https://support.google.com/nexus/4/answer/2852139?hl=nl. 3rd party apps will not boot in that mode.
Click to expand...
Click to collapse
Not sure why you linked that or how it even pertained to me (especially since it's been long since resolved and was using as an example). Also those tips do nothing if you couldn't get past the boot splash animation to begin with.
kbeezie said:
Not sure why you linked that or how it even pertained to me (especially since it's been long since resolved and was using as an example). Also those tips do nothing if you couldn't get past the boot splash animation to begin with.
Click to expand...
Click to collapse
It got me out of a bootloop mate, so if you speak for yourself that`s oke but that doesn`t mean it couldn`t work for others
gee2012 said:
It got me out of a bootloop mate, so if you speak for yourself that`s oke but that doesn`t mean it couldn`t work for others
Click to expand...
Click to collapse
How exactly do you get out of a boot-loop, when you can't even get into the rom to bring up the Power dialog in the first place like that instruction says? (The instructions you posted only works if you're already in the rom, holding down the ok button before it reboots, and I suspect all that's doing is clearing the Dalvik-cache which you can do from recovery anyways).
Also my problem wouldn't have anything to do with that, because if you flash a galaxy nexus recovery onto an N4, and reboot, it won't let you in because it'll ask for a password to decrypt storage, an the recovery will do the same thing, and my post which you quoted didn't have anything to do with a bootloop, just simply that you can get out of just bout any situations with a Nexus 4.
These are the most common bootloop solutions http://droidviews.com/2012/how-to-recover-when-your-android-device-is-caught-in-bootloop/.
Earlier today my phone was working fine running Stock 4.4.1/Kernel. I decided I wanted to get the franco kernel so I got the .img file from the xda thread. I flashed the .img file onto the boot partition using fastboot, and restarted my phone. After a few minutes of sitting at the "Google" screen I rebooted into the bootloader. I tried flashing the 4.4 factory image using the "flash-all.bat" without wiping anything. My phone continued to get stuck at the "Google" screen after multiple reboots. I then tried to wipe my device using fastboot. However, when using the command "fastboot erase system" I got an error that said "Failed: unknown chunk type." I kept on retrying the wipe to no avail. I found this thread: http://forum.xda-developers.com/showthread.php?t=2347060 and followed the steps. All the steps seemed to work up until I had to flash the given factory image using fastboot. I got the same "Unknown chunk type" when the cmd was trying to write files to the "system partition." Before you ask, yes my fastboot/adb is updated to the newest version. (I triple checked) And all my drivers work properly. I just flashed the 4.4.1 firmware 3 days ago using fastboot and everything went perfectly, including the wipe. Please offer any solutions you think could get me out of this situation. Thank you.
PandemicHD said:
Earlier today my phone was working fine running Stock 4.4.1/Kernel. I decided I wanted to get the franco kernel so I got the .img file from the xda thread. I flashed the .img file onto the boot partition using fastboot, and restarted my phone. After a few minutes of sitting at the "Google" screen I rebooted into the bootloader. I tried flashing the 4.4 factory image using the "flash-all.bat" without wiping anything. My phone continued to get stuck at the "Google" screen after multiple reboots. I then tried to wipe my device using fastboot. However, when using the command "fastboot erase system" I got an error that said "Failed: unknown chunk type." I kept on retrying the wipe to no avail. I found this thread: http://forum.xda-developers.com/showthread.php?t=2347060 and followed the steps. All the steps seemed to work up until I had to flash the given factory image using fastboot. I got the same "Unknown chunk type" when the cmd was trying to write files to the "system partition." Before you ask, yes my fastboot/adb is updated to the newest version. (I triple checked) And all my drivers work properly. I just flashed the 4.4.1 firmware 3 days ago using fastboot and everything went perfectly, including the wipe. Please offer any solutions you think could get me out of this situation. Thank you.
Click to expand...
Click to collapse
Never encountered something like this, but maybe from bootloader u can get into ur stock recovery & wipe cahce & wipe data.
once again I never had that issue...so its upto u...but might be worth a try...if u had made a backup or dont care about the data in ur phone then it did be easier for u u to try
Flash the factory images and erase all partitions on the device. If you want to get some data from the internal memory you could pull it through recovery. Next time read more do less. Franko's kernel uses different ram disk than the stock one. You could also try to flash a full stock kernel for your build first. Get it from the factory images and flash it through fastboot.
Sent from my Nexus 4 using xda app-developers app
i have the exact same problem here ! and i dont know what to do! its still stucked on the google logo!!!
alexvck said:
i have the exact same problem here ! and i dont know what to do! its still stucked on the google logo!!!
Click to expand...
Click to collapse
What's the exact same problem? Did you flash Franko kernel too. If so just dirty flash your current rom.
jd1639 said:
What's the exact same problem? Did you flash Franko kernel too. If so just dirty flash your current rom.
Click to expand...
Click to collapse
no i just had rooted it and loadedcwm and i was ready to flash paranoid anroid rom! and when it rebooted it stuck on the google logo! then i tried to reset my phone and load the official factory image with nexus root toolkit but when it did the usual procces with the command prmpt in some point after trying to write the new system it said "Failed: unknown chunk type." ! after that it rebooted and got stucked again in google logo!!
alexvck said:
no i just had rooted it and loadedcwm and i was ready to flash paranoid anroid rom! and when it rebooted it stuck on the google logo! then i tried to reset my phone and load the official factory image with nexus root toolkit but when it did the usual procces with the command prmpt in some point after trying to write the new system it said "Failed: unknown chunk type." ! after that it rebooted and got stucked again in google logo!!
Click to expand...
Click to collapse
Use this to flash the factory image http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
jd1639 said:
Use this to flash the factory image http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
my device is bricked i cant do these stuff :/
alexvck said:
my device is bricked i cant do these stuff :/
Click to expand...
Click to collapse
Can you get into bootloader mode. It's worth a try. Your not bricked if it can turn on. Your emmc may be bad and flashing the factory image won't work. But if that's the case then warranty or replacement are your only options.
jd1639 said:
Can you get into bootloader mode. It's worth a try. Your not bricked if it can turn on. Your emmc may be bad and flashing the factory image won't work. But if that's the case then warranty or replacement are your only options.
Click to expand...
Click to collapse
yes i can get in bootloader! but i cant do sth :/ ... whats the emmc ?!
Originally Posted by jd1639<br />
Can you get into bootloader mode. It's worth a try. Your not bricked if it can turn on. Your emmc may be bad and flashing the factory image won't work. But if that's the case then warranty or replacement are your only options.
Click to expand...
Click to collapse
<br />
<br />
yes i can get in bootloader! but i cant do sth :/ ... whats the emmc ?!
Click to expand...
Click to collapse
Emmc is the flash memory.
jd1639 said:
Emmc is the flash memory.
Click to expand...
Click to collapse
oo okay.. so is there sth else that i can try?!
alexvck said:
oo okay.. so is there sth else that i can try?!
Click to expand...
Click to collapse
have you tired the the toolkits?
I had problem with flash system.img, solved changing usb port. I hope help you.
Inviato dal mio Nexus 4 utilizzando Tapatalk
Everytime no matter what ROM I flash on this tablet I just get a bootloop and then I can't do anything in recovery like mounting SD card for instance.
I'm not completely new to this game, I have a nexus 5 that I'm always playing with and never had problems like this with the s3 or HTC one x. Could I be over looking something? Any help or guidance is much appreciated.
Cheers
Anyone?
I have a similar problem. I flashed ParanoidAndroid yesterday and everything seemed okay but now everything I try to launch or install an app the tablet reboots, and I tried to flash cyanogen, flash stock, do all the wipes and factory resets but always reboots to the damaged Paranoid Android ROM.
Reformat /system /cache /data
Then use a otg cable with a USB drive with the ROM you want
Mount in recovery then flash
USBhost said:
Reformat /system /cache /data
Then use a otg cable with a USB drive with the ROM you want
Mount in recovery then flash
Click to expand...
Click to collapse
In my case, reformat, wipe or erase from adb does absolutely nothing, so I don't know how properly erase all the content of the internal storage.
Amd64bits said:
In my case, reformat, wipe or erase from adb does absolutely nothing, so I don't know how properly erase all the content of the internal storage.
Click to expand...
Click to collapse
Tempary boot a recovery
You can do this in the bootloader
Using http://forum.xda-developers.com/showthread.php?t=1766475
USBhost said:
Tempary boot a recovery
You can do this in the bootloader
Using http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Yeah, I tried that also with CMW, but... didn't work...
Amd64bits said:
Yeah, I tried that also with CMW, but... didn't work...
Click to expand...
Click to collapse
Do it with twrp
USBhost said:
Do it with twrp
Click to expand...
Click to collapse
It is my default recovery but also did it, aaaand, no thing happened . I'm thinking of throwing it apart.
Amd64bits said:
It is my default recovery but also did it, aaaand, no thing happened . I'm thinking of throwing it apart.
Click to expand...
Click to collapse
Did booting a temporary recovery ever work or its your first time trying it
USBhost said:
Did booting a temporary recovery ever work or its your first time trying it
Click to expand...
Click to collapse
I have flashed many times before, always using the installed TWRP, with any problems, and I have booted temporary recoverys before with any issue. The recovery runs without problems, but when the device reboots, all remains the same.
Amd64bits said:
I have flashed many times before, always using the installed TWRP, with any problems, and I have booted temporary recoverys before with any issue. The recovery runs without problems, but when the device reboots, all remains the same.
Click to expand...
Click to collapse
Then try to flash a factory image
And see what happens
USBhost said:
Then try to flash a factory image
And see what happens
Click to expand...
Click to collapse
Nothing...
Amd64bits said:
Nothing...
Click to expand...
Click to collapse
Did the factory image flash good with no errors
USBhost said:
Did the factory image flash good with no errors
Click to expand...
Click to collapse
Yes, with the Succesfull text and all but when I reboot the ****ing Paranoid Android stills appears. I also tried with Adb Sideload, but failed because an error in the footer, although I downloaded it from google one time and from Wug Toolkit another; also the wipe from the stock recovery loaded by Wug Toolkit didn't work.
Amd64bits said:
Yes, with the Succesfull text and all but when I reboot the ****ing Paranoid Android stills appears. I also tried with Adb Sideload, but failed because an error in the footer, although I downloaded it from google one time and from Wug Toolkit another; also the wipe from the stock recovery loaded by Wug Toolkit didn't work.
Click to expand...
Click to collapse
Then I don't know what to do to help you with it
I'm sorry
But that is so interesting and unique
Even I copies the stock image to the SD, but when the Rom boots, it has been disappeared. So annoying.
Sent from my RM-821_eu_spain_435 using Tapatalk
USBhost said:
Then I don't know what to do to help you with it
I'm sorry
But that is so interesting and unique
Click to expand...
Click to collapse
Oh, well.. Thank you, anyways.
Hey, I'm having the exact (more or less) same issue: http://forum.xda-developers.com/showthread.php?t=2783720
I've been using Cyanogenmod, but other than that, I have the same thing going on.
I was actually glad to see this, as it means I'm not alone in this issue!
But still rather strange, and VERY frustrating.
I was flying yesterday, and noticed that the phone went into a bootloop when I took it out of my pocket during the flight.
My phone is on purenexus with TWRP installed already. When I got back home I tried clean flash the latest Feb ROM update, wiping all partition besides storage partition before the flash. Also flashed the latest vendor image. I did not see any error during the flash process.
No matter what I try, the phone would not get past the google screen and reboots just before it gets to the boot screen.
I am now backing up data on my phone via TWRP. It's going to be a PITA if I need to RMA the phone as it was bought in the US but I am now using it overseas.
Any magical fix to this issue?
Prior to the phone had issue, it was running Nougat Purenexus rom Jan 2017 version.
I got it yesterday. Try to flash the factory image in this post https://forum.xda-developers.com/showpost.php?p=62924118&postcount=2 (Step 10)
Add some more steps before the above:
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
It will works. Try it.
nhatminhng said:
I got it yesterday. Try to flash the factory image in this post https://forum.xda-developers.com/showpost.php?p=62924118&postcount=2 (Step 10)
Add some more steps before the above:
It will works. Try it.
Click to expand...
Click to collapse
As I do not want to format internal storage, I tried option 11 - How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
I followed all the steps and phone is still in bootloop.
Just backup your internal storage to somewhere in your PC and then you're free to go. Why dont try?
nhatminhng said:
Just backup your internal storage to somewhere in your PC and then you're free to go. Why dont try?
Click to expand...
Click to collapse
I haven't seen any evidence of wiping the internal storage will fix this issue.
Me. Yesterday. It's up to you to try.
nhatminhng said:
Me. Yesterday. It's up to you to try.
Click to expand...
Click to collapse
Just tried step 10 and format userdata - does not work. Phone is still stuck in bootloop.
The fact that you have access to the recovery means you have a high chance of getting the phone back to the should. The real BLOD only has boot loader available but nothing else besides the bar code screen.
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
The fact that you have access to the recovery means you have a high chance of getting the phone back to the should. The real BLOD only has boot loader available but nothing else besides the bar code screen.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have access to bootloader, and recovery (TWRP). Problem now is finding a solution to boot the phone past the google screen without going into a loop.
fustyler said:
I have access to bootloader, and recovery (TWRP). Problem now is finding a solution to boot the phone past the google screen without going into a loop.
Click to expand...
Click to collapse
Format your sytem, userdata and cache partitions then flash the latest full stock image using flash-all.bat.
v12xke said:
Format your sytem, userdata and cache partitions then flash the latest full stock image using flash-all.bat.
Click to expand...
Click to collapse
I have formatted every partition, and flashed latest full stock image. Still the same, google, google, google. Even tried the solution to format EFS partition and still bootloops.
So you have TWRP access still, and you have used the flash-all.bat method through the boot loader and it's still boned??
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
So you have TWRP access still, and you have used the flash-all.bat method through the boot loader and it's still boned??
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
I followed step 10 in this guide (which is the same as doing flash-all.bat, and it is still bootlooping. I then reflashed TWRP into recovery.
https://forum.xda-developers.com/showpost.php?p=62924118&postcount=2