Internal Problem? - Nexus 6P Q&A, Help & Troubleshooting

After updating device using the MDB08M factory images via fastboot, booting up causes a window to pop up on the lock screen with the header Android System saying "There's an internal problem with your device. Contact your manufacturer for details." I've never seen this before and only popped up after I updated using the factory image. Any ideas why it says that, and also how to get rid of it? Thanks

OmarEvo said:
After updating device using the MDB08M factory images via fastboot, booting up causes a window to pop up on the lock screen with the header Android System saying "There's an internal problem with your device. Contact your manufacturer for details." I've never seen this before and only popped up after I updated using the factory image. Any ideas why it says that, and also how to get rid of it? Thanks
Click to expand...
Click to collapse
The /system/build.prop and the /vendor/build.prop values don't match. Flash the MDB08M vendor.img using "fastboot flash vendor vendor.img" and then reboot - warning will be gone

gt7143c said:
The /system/build.prop and the /vendor/build.prop values don't match. Flash the MDB08M vendor.img using "fastboot flash vendor vendor.img" and then reboot - warning will be gone
Click to expand...
Click to collapse
Will this wipe anything else?
Edit: and it does not.

gt7143c said:
The /system/build.prop and the /vendor/build.prop values don't match. Flash the MDB08M vendor.img using "fastboot flash vendor vendor.img" and then reboot - warning will be gone
Click to expand...
Click to collapse
confirmed this fixes the issue, thanks!

gt7143c said:
The /system/build.prop and the /vendor/build.prop values don't match. Flash the MDB08M vendor.img using "fastboot flash vendor vendor.img" and then reboot - warning will be gone
Click to expand...
Click to collapse
I flashed the vendor.img and it still didn't work for me, any idea what else it could be? I can't view any files on my computer.

Related

Stuck on the Google Splach Screen

I unlocked and rooted. I then installed the update from Google. Upon reboot, it went back into Clockwork Recovery and then asked about installing the untrusted update. I try to install but it errored and restarted into Clockwork Recovery. I tried to wipe cache and wipe data/factory reset. When I select restart it gets hung on the Google Splash Screen. How do I fix this? Also, everytime I go into Recovery now it is Clockwork and not stock. I thought it would only flash Clockwork Recovery temporarily.
xda6969 said:
I unlocked and rooted. I then installed the update from Google. Upon reboot, it went back into Clockwork Recovery and then asked about installing the untrusted update. I try to install but it errored and restarted into Clockwork Recovery. I tried to wipe cache and wipe data/factory reset. When I select restart it gets hung on the Google Splash Screen. How do I fix this? Also, everytime I go into Recovery now it is Clockwork and not stock. I thought it would only flash Clockwork Recovery temporarily.
Click to expand...
Click to collapse
Go here and download the factory firmware for the Nexus 10:
https://developers.google.com/android/nexus/images
Then follow these steps:
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
Its for a Nexus 7 but they helped me fix my Nexus 10 too after I got stuck in the bootloop. Just use the different file names for the Nexus 10. You will need something to extract a tgz and a tar file for this process. You will also have to manually boot into the bootloader by powering the 10 off, then hold down volume up + volume down + power until you get the bootloader screen. Then follow those steps. It took me a few tries to get into the bootloader, not sure what that was about.
Initially, flashing a bad recovery got mine stuck, so make sure you grab a confirmed working recovery before you flash it. You will just have to start over, with the exception of unlocking as that would be sticky through this process.
Good luck!
When I flashed the image as in step 8, it said archive does not contain boot.sig, recovery.sig, system.sig. Then when it completed, it rebooted on its own and then it was still stuck on the Google Splash. I went back into stock recovery and did a Wipe Data/Factory Reset and now it works again. Thanks a lot!
xda6969 said:
When I flashed the image as in step 8, it said archive does not conatin boot.sig, recovery.sig, system.sig. Then when it completed, it rebooted on its own and then it was still stuck on the Google Splash. I went back into stock recovery and did a Wipe Data/Factory Reset and now it works again. Thanks a lot!
Click to expand...
Click to collapse
I had the same problem, u have to flash first the userdata.img and than the cache.img ,manually. Booth via fastboot command
bigdwg71, thanks a million! :good:
beama said:
I had the same problem, u have to flash first the userdata.img and than the cache.img ,manually. Booth via fastboot command
Click to expand...
Click to collapse
I also had to flash system.img manually as well...
beama said:
I had the same problem, u have to flash first the userdata.img and than the cache.img ,manually. Booth via fastboot command
Click to expand...
Click to collapse
Mine is up and running now and I didn't flash userdata.img and cache.img. Why is this not in the steps? What will happen if these are not flashed first? I don't think it matters. This thread says don't worry about it. http://forums.androidcentral.com/ne...e-factory-image-restore-your-nexus-7-a-2.html
When it was flashing the, I got OKAY for everything.
xda6969 said:
Mine is up and running now and I didn't flash userdata.img and cache.img. Why is this not in the steps? What will happen if these are not flashed first? I don't think it matters. This thread says don't worry about it. http://forums.androidcentral.com/ne...e-factory-image-restore-your-nexus-7-a-2.html
When it was flashing the, I got OKAY for everything.
Click to expand...
Click to collapse
Those images act like a wipe for the /data & /cache partitions... similar to using fastboot -w
Also, this thread does not belong in the Development forum... Mods, please move this!!
xda6969 said:
Mine is up and running now and I didn't flash userdata.img and cache.img. Why is this not in the steps? What will happen if these are not flashed first? I don't think it matters. This thread says don't worry about it. http://forums.androidcentral.com/ne...e-factory-image-restore-your-nexus-7-a-2.html
When it was flashing the, I got OKAY for everything.
Click to expand...
Click to collapse
Also, how do you flash Clockwork so it is not there permanantly? I only want to use it to install Superuser and then I want to be able to go to stock recovery.
xda6969 said:
Also, how do you flash Clockwork so it is not there permanantly? I only want to use it to install Superuser and then I want to be able to go to stock recovery.
Click to expand...
Click to collapse
From fastboot, you type something like "fastboot boot RECOVERY.img" instead of "fastboot flash RECOVERY.img"
espionage724 said:
From fastboot, you type something like "fastboot boot RECOVERY.img" instead of "fastboot flash RECOVERY.img"
Click to expand...
Click to collapse
I've used fastboot flash RECOVERY.img on my Galaxy Nexus many times and it was always temporary.
You can use the "fastboot boot" command to boot to CWRM temporarily. "Fastboot flash" will flash it permanently. I think there some devices that would reinstall the default recovery image if I recall. The Nexus 10 is not one of them.
Sent from my Nexus 10 using XDA Premium HD app
bigdwg71 said:
You can use the "fastboot boot" command to boot to CWRM temporarily. "Fastboot flash" will flash it permanently. I think there some devices that would reinstall the default recovery image if I recall. The Nexus 10 is not one of them.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the clarification.

[Q] phone not booting!

So I was following all the steps from this thread: http://forum.xda-developers.com/showthread.php?t=2010312
and I did flash the stock 4.2 img. Now, after unlocking the boot loader, i didnt exit the fastboot mode and stayed in. And continued the steps of section D (all of it). Then I did a fastboot reboot , and Google appeared and below it unlocked lock and then the jellybean logo. It's been almost 20 min and it hasn't passed that screen yet. The rainbow colour X.
What do I do to fix this?? I can go back to fastboot mode, but not sure what to do. I did the fastboot erase cache before rebooting my phone!
Look at the notes of section D.
You have to reboot into recovery, clear cache and factory reset.
Sent from my Nexus 4
El Daddy said:
Look at the notes of section D.
You have to reboot into recovery, clear cache and factory reset.
Sent from my Nexus 4
Click to expand...
Click to collapse
I did this though: 13) Erase the cache partition: fastboot erase cache
14) Reboot: fastboot reboot
Okay, and I will try to do that now.
El Daddy said:
Look at the notes of section D.
You have to reboot into recovery, clear cache and factory reset.
Sent from my Nexus 4
Click to expand...
Click to collapse
I booted myself into recovery via fastboot and it shows android laying down with a red triangle and inside that its " ! "
What now?
Press volume up and power at the same time. It will open the menu.
Sent from my Nexus 4
LimitsX said:
I booted myself into recovery via fastboot and it shows android laying down with a red triangle and inside that its " ! "
What now?
Click to expand...
Click to collapse
Flash it again using fastboot and the official Google image. Recent nexus devices are strange, i never had problems before but softbricked both nex4 and 7 just like that. If you can enter fastboot mode all is well though.
Ps. That tutorial, that was the longest one I've seen in my life. Are you aware that Google images contain clickme.bat files? You literally click it and it's done. Just make sure you have fastboot and adb installed. You can extract them from nexus toolkit as well.
If you do wanna make it by hand, also no problem. Download the image from here:https://developers.google.com/android/nexus/images
And type:
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot -w update image-yakju-icl53f.zip
Exchange the correct names of course. And make sure you're in fast boot mode.
El Daddy said:
Press volume up and power at the same time. It will open the menu.
Sent from my Nexus 4
Click to expand...
Click to collapse
Do I do that on that screen? I did, and it went into completely black screen.
molesarecoming said:
Ps. That tutorial, that was the longest one I've seen in my life. Are you aware that Google images contain clickme.bat files? You literally click it and it's done. Just make sure you have fastboot and adb installed. You can extract them from nexus toolkit as well.
If you do wanna make it by hand, also no problem. Download the image from here:https://developers.google.com/android/nexus/images
And type:
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot -w update image-yakju-icl53f.zip
Exchange the correct names of course. And make sure you're in fast boot mode.
Click to expand...
Click to collapse
Okay, im gonna go and do that! Thanks!
I was trying to mount the sdcard with nexus 4 but it wont do that with CWM and TWRP.
okay I think I just lost access to everything on my phone :|. I am still on TWRP, is there anything I can do with that?
I accidentally wiped the system files ugh. So I lost bootloader which means my phone is empty and useless and im still active on TWRP.
This is what I did in TWRP:
went to WIPE menu and did the following:
1)Wipe Cache
2)Dalvik Cache
3)Factory Reset
4)Wipe System
5)Wipe External storage ( didn't work - failed)
6)Wipe Internal storage (deleted)
So I have a boot loader still ?? or is that gone too? I am still active in TWRP. What are my options to fix this mess I've gotten myself into =\.
molesarecoming said:
Ps. That tutorial, that was the longest one I've seen in my life. Are you aware that Google images contain clickme.bat files? You literally click it and it's done. Just make sure you have fastboot and adb installed. You can extract them from nexus toolkit as well.
If you do wanna make it by hand, also no problem. Download the image from here:https://developers.google.com/android/nexus/images
And type:
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot -w update image-yakju-icl53f.zip
Exchange the correct names of course. And make sure you're in fast boot mode.
Click to expand...
Click to collapse
Yeah the thread is verbose, but its more of a tutorial than a "fix my fone nao!!!" Thread.
Efrant wrote it like that so users understand what they are doing.
Sent from my Nexus 4
so basically I have a dead phone?! =\. Anyone..help or point me in the right direction?
Nevermind. I figured it out and fixed it :victory: !!
El Daddy said:
Yeah the thread is verbose, but its more of a tutorial than a "fix my fone nao!!!" Thread.
Efrant wrote it like that so users understand what they are doing.
Sent from my Nexus 4
Click to expand...
Click to collapse
sure, didnt want to apply its not good or anything. its nice to know that google gives you some sort of emergency option, i've used it countless of times.
LimitsX said:
okay I think I just lost access to everything on my phone :|. I am still on TWRP, is there anything I can do with that?
I accidentally wiped the system files ugh. So I lost bootloader which means my phone is empty and useless and im still active on TWRP.
This is what I did in TWRP:
went to WIPE menu and did the following:
1)Wipe Cache
2)Dalvik Cache
3)Factory Reset
4)Wipe System
5)Wipe External storage ( didn't work - failed)
6)Wipe Internal storage (deleted)
So I have a boot loader still ?? or is that gone too? I am still active in TWRP. What are my options to fix this mess I've gotten myself into =\.
Click to expand...
Click to collapse
for the next time, you better learn what all this stuff is and means which you are flashing. i cant help but thinking its dangerous what you're doing there. if you are in twrp you're free to install any rom, your phone is pretty much safe if you can access it. wiping system wont kill your bootloader, system is a partition, your rom gets installed in there. you can wipe it, most roms even do it by default in the installation script. if your bootloader is gone you'll know.

Att Skipsoft.. all I have now is a large white Google on my Screen..

I had a M build from the original D which I flashed and I saw the LTE was no different from the L so I tried to go back to MDA..D and I made an error or the file was corrupted as all I have is a large white Google. I can get to the bootloader and lock/unlock it but when it is unlocked there is an error message about unable to check corrupted files and press Pause and when I did that it still had message and to press Continue and still it only will go back to the large Google ?
Is my phone beyond repair now as I tried your toolkit and must not have chosen the right options as there is no escaping the White google screen?
I have used and supported your toolkit since the Nexus 5 days but now I am really stumped..
just fastboot flash the factory images. you should be good to go since you can get into the bootloader.
painfree said:
I had a M build from the original D which I flashed and I saw the LTE was no different from the L so I tried to go back to MDA..D and I made an error or the file was corrupted as all I have is a large white Google. I can get to the bootloader and lock/unlock it but when it is unlocked there is an error message about unable to check corrupted files and press Pause and when I did that it still had message and to press Continue and still it only will go back to the large Google ?
Is my phone beyond repair now as I tried your toolkit and must not have chosen the right options as there is no escaping the White google screen?
I have used and supported your toolkit since the Nexus 5 days but now I am really stumped..
Click to expand...
Click to collapse
Like the guy above said to fastboot the factory image.
See the link below, follow step 9
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
Also note in these commands that the xx.xx.img, the xx's are numbers. Just make sure you change the xx to whatever the number is. It will vary depending on version you flash.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
So you are saying that the Skipsoft Toolkit is NOT able to resolve this situation by using any of its options?
painfree said:
So you are saying that the Skipsoft Toolkit is NOT able to resolve this situation by using any of its options?
Click to expand...
Click to collapse
Why use a toolkit in the first place? As you've found out they're more trouble than they're worth. Plus, with a Nexus you really shouldn't need one anyway, these phones are simple to work with. Check out my guide, it has everything you need to know:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Why use a toolkit in the first place? As you've found out they're more trouble than they're worth. Plus, with a Nexus you really shouldn't need one anyway, these phones are simple to work with. Check out my guide, it has everything you need to know:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I am using windows 10 and I cannot for the life of me figure out the file locations .. How do I do a simple thing as find a file called fastboot.exe on my PC using windows 10 ? this is what I have so far :
http://screencast.com/t/qhapdJk8
I have no idea where bootloader.exe is located and I cannot figure out how to do a simple file search on Windows 10. As a result I cannot open up a command prompt there if I cannot find it..
painfree said:
I am using windows 10 and I cannot for the life of me figure out the file locations .. How do I do a simple thing as find a file called fastboot.exe on my PC using windows 10 ? this is what I have so far :
http://screencast.com/t/qhapdJk8
I have no idea where bootloader.exe is located and I cannot figure out how to do a simple file search on Windows 10. As a result I cannot open up a command prompt there if I cannot find it..
Click to expand...
Click to collapse
Did you follow the instructions in the beginning of the thread to install the SDK and in turn install adb/fastboot? I make no mention of bootloader.exe so I'm not sure where you're getting that from, there's no such thing, you don't know what the bootloader is? It might be a good idea for you to read the prerequisites section and the quick tips section at the beginning of the first post, and the FAQ section in the second post.
Heisenberg said:
Did you follow the instructions in the beginning of the thread to install the SDK and in turn install adb/fastboot? I make no mention of bootloader.exe so I'm not sure where you're getting that from, there's no such thing, you don't know what the bootloader is? It might be a good idea for you to read the prerequisites section and the quick tips section at the beginning of the first post, and the FAQ section in the second post.
Click to expand...
Click to collapse
yes I completed part 1 with all the command prompt tests and someone said to skip to step 9... I read this regarding bootloader and I assumed it was an exe file.. sorry..
"Like the guy above said to fastboot the factory image.
See the link below, follow step 9
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
Also note in these commands that the xx.xx.img, the xx's are numbers. Just make sure you change the xx to whatever the number is. It will vary depending on version you flash.
http://forum.xda-developers.com/nexu...nners-t3206928 "
painfree said:
yes I completed part 1 with all the command prompt tests and someone said to skip to step 9... I read this regarding bootloader and I assumed it was an exe file.. sorry..
"Like the guy above said to fastboot the factory image.
See the link below, follow step 9
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
Also note in these commands that the xx.xx.img, the xx's are numbers. Just make sure you change the xx to whatever the number is. It will vary depending on version you flash.
http://forum.xda-developers.com/nexu...nners-t3206928 "
Click to expand...
Click to collapse
Are you following my instructions as they're written? They're very thorough so should be easy to follow.
Heisenberg said:
Are you following my instructions as they're written? They're very thorough so should be easy to follow.
Click to expand...
Click to collapse
OK I am back to system but there is a message about internal system problem yet it is factory now. .." Android System There's an internal problem with your device. Contact your manufacturer for details"
painfree said:
OK I am back to system but there is a message about internal system problem yet it is factory now. .." Android System There's an internal problem with your device. Contact your manufacturer for details"
Click to expand...
Click to collapse
Which images did you flash? And which build?
Heisenberg said:
Which images did you flash? And which build?
Click to expand...
Click to collapse
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-
01.31.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-01.29.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
MDA089D I have t mobile and all the other builds K L M crippled my in home reception..
painfree said:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-
01.31.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-01.29.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
MDA089D I have t mobile and all the other builds K L M crippled my in home reception..
Click to expand...
Click to collapse
Ok, but you're able to actually boot into Android, right? Or are you not able to? If you're able to it's probably worth trying a factory reset (Settings>Backup & Reset>Factory Data Reset).
Heisenberg said:
Ok, but you're able to actually boot into Android, right? Or are you not able to? If you're able to it's probably worth trying a factory reset (Settings>Backup & Reset>Factory Data Reset).
Click to expand...
Click to collapse
I am able to set up the phone as I normally would but my replacement via RMA just arrived so I will be sending this one back but now I know to avoid the toolkits.

Stuck in 'waiting for any device' when trying to flash factory image with fastboot

Hi, I am trying to revert to stock Android (phone is stuck in a boot loop) by flashing the factory images (Heisenberg's thread, point 12) but am getting the 'waiting for any device' message and nothing happens when trying to execute fastboot commands.
The phone is recognized, however, when I get it into TWRP Recovey and type 'adb devices', shows the serial number and recovery status. When I'm in the bootloader the phone isn't recognized, "connect usb data cable" even though it is connected.
I am stuck at this point / out of my depth and out of any further ideas
go to bootloader and type "fastboot devices"
fastboot devices - no value
fastboot devices - returns no value; adb devices still gives me serial of the connected nexus 6p
could this be a driver (on my pc?) issue?
weird that fastboot devices returns no value
ciliax said:
fastboot devices - returns no value; adb devices still gives me serial of the connected nexus 6p
could this be a driver (on my pc?) issue?
weird that fastboot devices returns no value
Click to expand...
Click to collapse
Sounds like it. Try installing fastboot drivers again.
ok, I give that a shot
OK, so I installed the SDK package on a different PC, tried it with the Google USB drivers and then with the Huawei drivers instead. Same result as before...
ADB Devices shows my phone, fastboot devices returns no value. The phone is only recognized when in recovery Mode (TWRP) - not when in the bootloader.
This is very frustrating.
Any other ideas anyone?
Did you do all the prerequisites from the guide? http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 Or maybe a java being outdated? Last idea is installing usb drivers manually http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
ciliax said:
Hi, I am trying to revert to stock Android (phone is stuck in a boot loop) by flashing the factory images (Heisenberg's thread, point 12) but am getting the 'waiting for any device' message and nothing happens when trying to execute fastboot commands.
The phone is recognized, however, when I get it into TWRP Recovey and type 'adb devices', shows the serial number and recovery status. When I'm in the bootloader the phone isn't recognized, "connect usb data cable" even though it is connected.
I am stuck at this point / out of my depth and out of any further ideas
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/help/adb-fine-fastboot-t3297277
long story short, blame windows
If you can boot into TWRP, what about pushing the images into the phone via adb push ?
The new TWRP 3.0.0.0 can flash the .img files, but I am not sure if it will be able to flash the system, boot, and so on images... But I would give it a try though..
If not, please someone correct me.
neisor said:
If you can boot into TWRP, what about pushing the images into the phone via adb push ?
The new TWRP 3.0.0.0 can flash the .img files, but I am not sure if it will be able to flash the system, boot, and so on images... But I would give it a try though..
If not, please someone correct me.
Click to expand...
Click to collapse
If TWRP 3.0 can flash system, boot, radio, vendor, etc image files that would be awesome! OP keep us posted.
Pain-N-Panic said:
If TWRP 3.0 can flash system, boot, radio, vendor, etc image files that would be awesome! OP keep us posted.
Click to expand...
Click to collapse
Well, quoting the https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html where it says exactly this: "Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI" in the 4th dot/part of the "What’s new in 3.0.0-0" section.
So, I guess twrp should be able to do the job.
neisor said:
Well, quoting the https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html where it says exactly this: "Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI" in the 4th dot/part of the "What’s new in 3.0.0-0" section.
So, I guess twrp should be able to do the job.
Click to expand...
Click to collapse
Awesome! Anyone know what the select "some parts" of the factory image they're referring to?
Pain-N-Panic said:
Awesome! Anyone know what the select "some parts" of the factory image they're referring to?
Click to expand...
Click to collapse
On Nexus 5X and 6P, TWRP can flash system.img, boot.img, and vendor.img. TWRP cannot flash bootloader and radio.img.
Sent from my Nexus 5X using Tapatalk

please helpe me

i try instaling cortex 7.00( 7.1.2) after al is ok after the phone reboot evry time when i using i try wipe data with twrp
after reboot the phon don t rebot just bootloop i try unstaling stock image with toolkit evry think is ok but the same brob just bootloop i can enter in fastboot mode but not in stock recovery
samone know the solution ?or my fhone is dead
leroilion02 said:
i try instaling cortex 7.00( 7.1.2) after al is ok after the phone reboot evry time when i using i try wipe data with twrp
after reboot the phon don t rebot just bootloop i try unstaling stock image with toolkit evry think is ok but the same brob just bootloop i can enter in fastboot mode but not in stock recovery
samone know the solution ?or my fhone is dead
Click to expand...
Click to collapse
Since your phone is unlocked, I would try to flash a full Google image using the included flash-all.bat (instructions are on the same page as the image downloads). Not being able to access recovery mode may indicate a more serious problem.
v12xke said:
Since your phone is unlocked, I would try to flash a full Google image using the included flash-all.bat (instructions are on the same page as the image downloads). Not being able to access recovery mode may indicate a more serious problem.
Click to expand...
Click to collapse
do you think my phone still alive
leroilion02 said:
do you think my phone still alive
Click to expand...
Click to collapse
Too early to tell. Google intended the image files to be a foolproof way to "reset" the phone to factory stock. This is the first thing you have to try. Set up ADB/Fastboot on your PC and use it to communicate with, and send commands to your phone.
I've gotten myself into the same situation a few times and flashing the full stock image with flash-all.bat command has always gotten me out of it so far. After I'm back on stock I just start from scratch again and flash recovery, custom rom and root.
jhs39 said:
I've gotten myself into the same situation a few times and flashing the full stock image with flash-all.bat command has always gotten me out of it so far. After I'm back on stock I just start from scratch again and flash recovery, custom rom and root.
Click to expand...
Click to collapse
i flash the full factory image with fastboot all is ok after fishing just bootloop i don t know what is the probleme
leroilion02 said:
i flash the full factory image with fastboot all is ok after fishing just bootloop i don t know what is the probleme
Click to expand...
Click to collapse
fastboot FORMAT (not erase or wipe) userdata, cache and system capturing the screen (or text from each command). Try flash-all.bat again. Which image are you flashing?
v12xke said:
fastboot FORMAT (not erase or wipe) userdata, cache and system capturing the screen (or text from each command). Try flash-all.bat again. Which image are you flashing?
Click to expand...
Click to collapse
the last android 7.1.1
when i flash with flash-all.bat the note progresse he stop with message fichier not fond
leroilion02 said:
the last android 7.1.1
when i flash with flash-all.bat the note progresse he stop with message fichier not fond
Click to expand...
Click to collapse
do you think my phone can reboot
leroilion02 said:
do you think my phone can reboot
Click to expand...
Click to collapse
Can you enter recovery mode after all you have tried? Or do you only have access to fastboot in broader?
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Can you enter recovery mode after all you have tried? Or do you only have access to fastboot in broader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
just fastboot
leroilion02 said:
do you think my phone can reboot
Click to expand...
Click to collapse
I don't know, you're providing conflicting information. What happened when you fastboot formatted each of the 3 partitions?
v12xke said:
I don't know, you're providing conflicting information. What happened when you fastboot formatted each of the 3 partitions?
Click to expand...
Click to collapse
when i flash the phon on fastboot al is ok the bootloader after the radio after the system after vendor all ok the phon just bootloop
when i try flash with flash-all.bat the procedur don t progress just the radio and bootlaoder after just error message files don t exist
leroilion02 said:
when i flash the phon on fastboot al is ok the bootloader after the radio after the system after vendor all ok the phon just bootloop
when i try flash with flash-all.bat the procedur don t progress just the radio and bootlaoder after just error message files don t exist
Click to expand...
Click to collapse
No. Fastboot FORMAT the 3 partitions (for the 3rd time). Capture the response from each of these commands:
fastboot format userdata
fastboot format cache
fastboot format system
v12xke said:
No. Fastboot FORMAT the 3 partitions (for the 3rd time). Capture the response from each of these commands:
fastboot format userdata
fastboot format cache
fastboot format system
Click to expand...
Click to collapse
ok i try tomorow and i tell you the Result

Categories

Resources