Hello guys! Some help would be nice... Thanks in advance.
So i enrolled to Android 7 Beta and downloaded the latest OTA update. I was fine until i saw some apps i have didnt work in Android 7. So i wanted to go back to Android 6.
I tried unrolling my device from the beta but it didnt gave me an update from the Settings menu.
Then i downloaded the factory image and flashed it with fastboot.
I flashed everything and now it is stuck at Google Logo. I tried wiping cache, wiping data and reseting the phone in different manners.
What else should i do?
Thanks in advance.
akumalol said:
Hello guys! Some help would be nice... Thanks in advance.
So i enrolled to Android 7 Beta and downloaded the latest OTA update. I was fine until i saw some apps i have didnt work in Android 7. So i wanted to go back to Android 6.
I tried unrolling my device from the beta but it didnt gave me an update from the Settings menu.
Then i downloaded the factory image and flashed it with fastboot.
I flashed everything and now it is stuck at Google Logo. I tried wiping cache, wiping data and reseting the phone in different manners.
What else should i do?
Thanks in advance.
Click to expand...
Click to collapse
Re-flash MM stock package again via fastboot. Among the .img files flash bootloader and radio first but make sure you do "fastboot reboot-bootloader" after flashing each of the two.
blitzkriegger said:
Re-flash MM stock package again via fastboot. Among the .img files flash bootloader and radio first but make sure you do "fastboot reboot-bootloader" after flashing each of the two.
Click to expand...
Click to collapse
Downloaded the first factory image for Nexus 6p and did flash everything and followed your suggestion exactly. 10 Minutes still Google Logo.
:/
akumalol said:
Downloaded the first factory image for Nexus 6p and did flash everything and followed your suggestion exactly. 10 Minutes still Google Logo.
:/
Click to expand...
Click to collapse
FYI. I managed to finally boot again on Android 7 using the OTA update from here. https://www.reddit.com/r/Nexus6P/comments/4z4ru1/android_n_ota_link_for_nexus_6p_from_601_to_70/
The problem is i cant get back to MM and i guess i have to wait somehow for the updated apps to work with Nougat.
My computer isn't even detecting my phone within ADB... any help?
Licensedbeast said:
My computer isn't even detecting my phone within ADB... any help?
Click to expand...
Click to collapse
When you select "Apply updated from ADB" i had to unplug and re plug my phone to my computer in order to see it. If windows says it is unrecognized i guess you need some drivers.
I officially hate Android 7. Boot loops galore. Factory reset without restoring ANYTHING is the only way to keep it from looping right now.... But its only been an hour so we'll see. Like you I'm unable to rollback to MM. My computer also is working with adb. I've updated my sdk to the newest version too. I can get the device serial number in fastboot, but the reboot commands give me error device not found.
akumalol said:
When you select "Apply updated from ADB" i had to unplug and re plug my phone to my computer in order to see it. If windows says it is unrecognized i guess you need some drivers.
Click to expand...
Click to collapse
Damn... I tried Factory Resetting... and all I had to do was unplug and re plug. Thanks that worked
I have been on the beta program just to get Nougat and downloaded and installed it just fine a week ago. Now all of a sudden today my phone goes off and then to the never ending Google logo. I turned it back off, and now it wont come on, wont charge, etc. Nothing. How can I get it back live again. Even when I had the Google logo earlier I couldnt boot to anything else. Holding power and volume down does nothing.
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!
bogomil4e said:
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!
Click to expand...
Click to collapse
Was running the Nougat 7.0 WETA ROM, and had some issues with sound performance, plus battery life was tanking, so went to using Vanir 6.0.
Wiped and installed (I assume from the process that backup and restore is part of this process), then pico gapps, and stuck on boot screen.
Found this thread and followed instructions. The first ABD command works flawlessly, but the second one returns the standard printscreen when a command isn't recognized, and lists all the adb options. Possibility it's entered incorrectly?
Boot issue persists
hifiaudio2 said:
I have been on the beta program just to get Nougat and downloaded and installed it just fine a week ago. Now all of a sudden today my phone goes off and then to the never ending Google logo. I turned it back off, and now it wont come on, wont charge, etc. Nothing. How can I get it back live again. Even when I had the Google logo earlier I couldnt boot to anything else. Holding power and volume down does nothing.
Click to expand...
Click to collapse
Have you found a solution? Mine is doing the exact same thing
Device is corrupt, stuck on google logo
It's been a while since my crack flashing days but i just got my N6P, updated to MTC20F, Unlocked Bootloader, installed TWRP 3.0.2-2, rooted, Tried to install CM13, I got the wrong gapps tho, forgot to check ARM64 instead of ARM. so i got a bad install with the gapps, said it wasn't compatible. So I tried to wipe and restore my backup i made in TWRP, but i keep getting the "device is corrupt and cannot be trusted" then stuck at Google logo. I would think if i could push the factory img or the correct Gapps to the phone, I could flash with no problem. How do i get new files onto the phone while in TWRP? Sorry if it's a noob question, but i need help. Thanks!
wonton9224 said:
It's been a while since my crack flashing days but i just got my N6P, updated to MTC20F, Unlocked Bootloader, installed TWRP 3.0.2-2, rooted, Tried to install CM13, I got the wrong gapps tho, forgot to check ARM64 instead of ARM. so i got a bad install with the gapps, said it wasn't compatible. So I tried to wipe and restore my backup i made in TWRP, but i keep getting the "device is corrupt and cannot be trusted" then stuck at Google logo. I would think if i could push the factory img or the correct Gapps to the phone, I could flash with no problem. How do i get new files onto the phone while in TWRP? Sorry if it's a noob question, but i need help. Thanks!
Click to expand...
Click to collapse
You can push the file via adb or just connect your phone through usb cable while in twrp and drag and drop from pc to your phones storage drive
Yeah I couldn't get the internal storage to mount on xp but it does on win 7, window pops right up after drivers install. I tried flashing cm13 with the correct gapps but it still hangs at Google. I'm using the skipsoft toolkit to try and flash back to stock right now
Hope everyone here can help me.
I was flashing a 7.0 ROM on my phone with the NRDU90 vendor. The flashing failed so I restored from my backup made by TWRP. The restore was successful, but now I'm stuck in a bootloop. The phone goes to the Google splash screen with the lock(it is in the unlocked position) and then goes right back to the screen that mentions about device corruption and please relock the bootloader.
When it wasn't booting, I was able to boot into fastboot and then into recovery with no issues. I tried the fastboot flash of NRDU90 and also MCT20L builds direct from google. All flash but continues to loop. Only success that saw a small part of the Android splash boot was flashing Tupac's 7.0 rom but that never got any further.
Hoping y'all can help. I personally do not have a spare phone so this is my only device. Willing to try any steps and if need to, can do like a hangout session for any help.
Flash kernel for mm and then rom
pctechdroid said:
Hope everyone here can help me.
I was flashing a 7.0 ROM on my phone with the NRDU90 vendor. The flashing failed so I restored from my backup made by TWRP. The restore was successful, but now I'm stuck in a bootloop. The phone goes to the Google splash screen with the lock(it is in the unlocked position) and then goes right back to the screen that mentions about device corruption and please relock the bootloader.
When it wasn't booting, I was able to boot into fastboot and then into recovery with no issues. I tried the fastboot flash of NRDU90 and also MCT20L builds direct from google. All flash but continues to loop. Only success that saw a small part of the Android splash boot was flashing Tupac's 7.0 rom but that never got any further.
Hoping y'all can help. I personally do not have a spare phone so this is my only device. Willing to try any steps and if need to, can do like a hangout session for any help.
Click to expand...
Click to collapse
Read post #10.
Sent from my Nexus 5X using Tapatalk
Two weeks ago I updated my nexus 6p to the latest may security patch update of 7.1.2, I was out of station for a week I left my phone switch off at home when I came back home and tried to start the phone it got stuck on the Google logo I tried to clear cache but it too didn't work out for me what should I do to bring my phone back to normal, my phone is not under warranty it has expired almost 5 months ago, plz plz help worried about it
[email protected] said:
Two weeks ago I updated my nexus 6p to the latest may security patch update of 7.1.2, I was out of station for a week I left my phone switch off at home when I came back home and tried to start the phone it got stuck on the Google logo I tried to clear cache but it too didn't work out for me what should I do to bring my phone back to normal, my phone is not under warranty it has expired almost 5 months ago, plz plz help worried about it
Click to expand...
Click to collapse
try flashing the newest 7.1.2 vendor i was having the same issue when i tried going back to 7.1.2 from android O
Related
Need some help.
I just sideloaded the 4.3 update to phone and now it's stuck on the 'X' loading screen.
My phone was rooted, but all stock (including the bootloader). I used the sideload ADB command and everything went fine, but the phone now won't boot.
How do I fix this?
did you data wipe(factory reset) before flashing?? if not, you have too.
I applied the OTA...didn't think I had to
Any idea on how I fix it now?
Really don't want to lose all my data
Install a custom recovery and wipe or apply factory image
favaroooo said:
Install a custom recovery and wipe or apply factory image
Click to expand...
Click to collapse
Is there a way I can fix it without wiping everything?
theprodigy85 said:
Is there a way I can fix it without wiping everything?
Click to expand...
Click to collapse
I do not think because you have to change recovery you must unlock the bootloader and unlock bootloader wipe the phone
theprodigy85 said:
Is there a way I can fix it without wiping everything?
Click to expand...
Click to collapse
no, its the data(and other stuff) causing it not to boot. same thing when flashing custom rom, you wipe when fkashing different roms. and going from android 4.2.2 to 4.3, theres many changes, enough to consider it a different rom.
Shoot...I should have done more research before doing this.
I did a factory reset through the stock bootloader...but it's still looping on the 'X' screen.
Can someone walk me through this or point me to a guide?
Bootloader is currently unlocked and I'm able to get into the factory recovery.
theprodigy85 said:
Shoot...I should have done more research before doing this.
I did a factory reset through the stock bootloader...but it's still looping on the 'X' screen.
Can someone walk me through this or point me to a guide?
Bootloader is currently unlocked and I'm able to get into the factory recovery.
Click to expand...
Click to collapse
are you flashing a zip or an img file??
simms22 said:
are you flashing a zip or an img file??
Click to expand...
Click to collapse
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...
Try to restore using the factory image
theprodigy85 said:
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...
Click to expand...
Click to collapse
yea, the zip youd want to wipe data/factory reset, then flash the rom. dirty flashing wont help since the changes are big enough.
theprodigy85 said:
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...
Click to expand...
Click to collapse
I bought my ole lady a Nexus 4 for Valentines day, anyway, today she got the OTA update and let it install the update. Now mind you she is 100% stock, adb debugging was not enabled, and her bootloader was still locked. (She would not let me touch her Nexus 4 lol) When the device rebooted it stuck on Android Upgrading finishing boot. So I said well let me see what I can do, this is what I did to fix it.
I use only Ubuntu so this may not work on windows i do not know. I Booted the device to the bootloader, connected it to my laptop via USB. I opened a terminal and typed in "sudo fastboot devices" and entered my password when promted and this gave me the device ID and fastboot letting me know fastboot was working. I then typed in "sudo fastboot reboot" and the device rebooted but was stuck on the bootanimation. I opened the internal storage up on my laptop in my file explorer and made a copy of her internal storage. Next I booted the device back into the bootloader then opened a terminal and typed in "sudo fastboot oem unlock" and the device gave me the unlock warning and the yes or no options. I selected yes so it would factory reset. After it did the factory reset the device reboot and booted to the setup welcome screen. Hope this helps others, also thanks to my good good friend Ljjehl for reminding me to use "sudo".
Edit: If you open the command promt with Administrative permissions in Windows this will work in Windows as well. Go to C:\Windows\System32\cmd.exe and right click on the cmd.exe file and select run as administrator. Then CD to the location with your fastboot.exe command. Thanks to another good friend TheBr0ken.
Thanks for the help...
I just ended up flashing each of the 4.3 components from the factory image. Just annoyed that I lost everything...
I'm stuck at the same screen. I received the OTA update, I didn't do anything special. My phone is unlocked and rooted (or WAS) but that was months ago, the rest is stock.
I think having encryption on my phone may have made it do this. I don't think Google anticipated doing the update properly for encrypted phones. Now I fear I've lost everything because even if I could connect, all data is encrypted...
similar problem
After starting to OTA update it was going smoothly, i was making breakfast, came back to find my screen at the "starting apps" screen frozen. The little circle that rotated wasnt doing anything so i left it there for awhile longer and still nothing. It would not move off that screen so i held power button down and restarted. now its stuck at the X screen also.
Yeah, I'm stuck there too. Already tried Factory Rest, didn't work. So what can I do?
I was on stock 4.2.2 and unrooted. I used the 'Google Services Framework' hack to force the 4.3 OTA update. The update downloaded successfully, phone restarted to apply the update and then restarted again. And now its stuck at the Google screen and keeps on restarting :crying:
I dont have the USB drivers installed on my PC too.
Same Problem
I have a nexus 4 (stock and unrooted),after 4.3 update,it is lagging during phone lock on/off (2 sec/5 sec).Hence I restarted my phone,and it stuck at "x" logo.Did clean data 3 times and then its working.
The problem is,in 2 days,I have experienced and done above thrice?
What could have gone wrong?
Hi guys,
I've just found how to correct this problem. All you have to do is to correctly wipe your phone before flashing factory image.
So :
Fastboot erase boot
Fastboot erase recovery
Fastboot format cache
Fastboot format system
Fastboot format userdata
I've just unbrick a n4 this way 15 minutes ago.
I have found the problem in recovery where you can see error log saying "cannot mount cache"
So formating correct the issue.
Hope it can help, fingers crossed.
Sent from my Galaxy Nexus using xda premium
Hopefully someone can help me here.
I have the N10 and it is rooted. I flashed the stock recovery and flashed the stock kernel.
So I should have been pretty much stock cause I had the 4.4.4 factory image on it except it was unlocked.
So then I let it do the OTA for lollipop.
When it rebooted into recovery it got about 1/3 and then hit an error (just said error).
Now I can only get it to the recovery screen and the reboot Mode Flag is 'Recovery'
The only thing I can do at that point is hit the power button and it reboots to recovery with a "No Command" error.
Help please!
EDIT: The thing finally booted up on it's own. Should I leave it alone or try to take the OTA update again?
sl2222 said:
Hopefully someone can help me here.
I have the N10 and it is rooted. I flashed the stock recovery and flashed the stock kernel.
So I should have been pretty much stock cause I had the 4.4.4 factory image on it except it was unlocked.
So then I let it do the OTA for lollipop.
When it rebooted into recovery it got about 1/3 and then hit an error (just said error).
Now I can only get it to the recovery screen and the reboot Mode Flag is 'Recovery'
The only thing I can do at that point is hit the power button and it reboots to recovery with a "No Command" error.
Help please!
EDIT: The thing finally booted up on it's own. Should I leave it alone or try to take the OTA update again?
Click to expand...
Click to collapse
Same for me. I'm trying to even manually flash the factory image, but it will not detect fastboot. I'm trying to research this now. The device just keeps restarting itself over and over into No Command.
IT Rider said:
Same for me. I'm trying to even manually flash the factory image, but it will not detect fastboot. I'm trying to research this now. The device just keeps restarting itself over and over into No Command.
Click to expand...
Click to collapse
Hi, I have exactly the same problem after installing Android 5.0 OTA. Please post a solution here if you find it. Thanks!
I didn't try the OTA again. I installed Lollipopalooza from this thread...
http://forum.xda-developers.com/showthread.php?t=1998585
No problem with it so far
sl2222 said:
I didn't try the OTA again. I installed Lollipopalooza from this thread...
http://forum.xda-developers.com/showthread.php?t=1998585
No problem with it so far
Click to expand...
Click to collapse
But I cannot flash any rom as none of ADB commands can be run (device is not connected, though I connected it with OEM cable). I tried factory reset but it didn't help.
Just wanted to share what worked for me after the OTA update failed and flashing stock images didn't work. Put the tablet in fastboot. Installed stock image, tablet wouldn't boot. Restarted went into recovery got the android on its back with the red x coming out of it (did not say bad command at thia point). I presses volume up and power at the same time on this screen. Cleared cache and rebooted then the tablet booted up.
I cannot believe companies still get away with this inadequate device "killing" type of software. Did no-one at the company do any testing before release?????
Rant over, onto solution - for me anyway.
The issue I had was that I could not get ADB to be of any use so switched to fastboot. Should have used fastboot from the getgo. Hohum.
So, into recovery with android on it's back with red triangle and reboot into fastboot.
Connect N10 to PC with USB cable.
Downloaded "Minimal ADB and Fastboot"(MAF)
Downloaded Lollipop for Nexus 10 - image-mantaray-lrx21p.zip and saved to c: drive (this saves loads of typing at command prompt)
File path for update is c:\image-mantaray-lrx21p.zip
Open MAF and ensure folder path points to your MAF install folder..
At command prompt type fastboot update c:\image-mantaray-lrx21p.zip
If you want to wipe device prior to update then type fastboot -w update c:\image-mantaray-lrx21p.zip
This may take a while so go make a drink - or something.
If all goes well, mine did, you should eventually be presented with the lollipop opening screen and a working device.
Just finally got it working!
ROM updates from ADB Sideload or Fastboot failed every time for different reasons.
What I had to do is to flash custom recovery (latest TWRP) with "fastboot flash recovery <recovery.img>" command.
From TWRP flashing the official ROMs also failed. But flashing Lollipopalooza as sl2222 suggested finally succeeded.
Thanks for all the help!
HI all,
I've come from flashing Samsung S4's for years but after trying to flash an update I got the boot screen and nothing happens.
Here's the situation.
I had originally installed PureNexus, rooted, unlocked the boot loader and probably turned off USB ADB settings (and I don't typically want an alert when plugging in the USB cable) as I usually transfer media and ROM's to the download folder for future flashing.
I saw that 6.01 was released and saw that the bootloader and radio were updated. So I tried to flash those before updating with PureNexus 6.01.
I did a nandroid backup before I did this, knowing something might go wrong.
I think my camera wasn't working so I tried a nandroid recovery to get it back.
Unfortunately I didn't read about the password encryption bug which TWRP had as I did the restore in my car and didn't have internet as it was free down time. When it was completed, I got the failed password issue. So I decided just to format everything. I used TWRP and formatted everything including the vendor partition. Of course, I forgot it would delete the Nandroid, too. I'm too used to having a spare external SD card to store all of the Nandroids on.
Anyway after that I can only get to TWRP.
I've tried installing the original 6.0 ROM, PureNexus ROM through TWRP with the appropriate ZIP files. It says it's completed, no errors but just the boot screen.
I've tried restoring through ADB with Windows 10 and through the USB. I don't get to an ADB selection on the bootloader, but can get to the ADB sideload throught TWRP. The problem is when I tried to restore through ADB nothing happens as it says "waiting" when I use fastboot flash-all. ADB devices does give me an ID when I do ADB so it is connecting. However, I believe ADB is waiting for the USB-ADB to be turned on which I can't do because I can't get to the OS system partition.
I've tried using several of the Skip Soft Toolkit and again, it waits and says closed.
I'm assuming that USB-ADB is closed and not turned on. I don't know why TWRP can't overwrite the system partitions if I try to flash, unless it's still encrypted but shouldn't be as I formatted everything, except for the boot loader and that is unlocked as I get the screen that I should lock the bootloader because the OS can't tell if it is corrupted.
Any ideas? I can only think if someone sends me a Nandroid of a configuration that may flash it back to a level I can get into Android and then get back to USB ADB and do a clean install with fastboot flash-all.
Please help!! Thanks in advance for your suggestions. I hope I gave you enough information to help me out.
Update. I apparently found a way. Luckily TWRP has a Flash image feature as well as flashing the vendor image. Flashed PureNexus 6.01 and PureNexus Gapps and thank goodness that worked! No idea why ADB was not flashing except for the configuration for USB ADB was turned off on the ROM originally.
so there I was in my car, my phone plugged in via aux cable and playing some music
suddenly I notice the music stops and my phone goes into a reboot,
I was using a pure nexus rom on marshmallow ( the latest marshmallow one i believe) and had xposed, and sometimes my phone would randomly reboot,
it was annoying but I could live with it
so i thought it was having another one of it's moment
but now it doesn't actually reboot,
my phone is stuck in a reboot loop and I can't even get into recovery mode, (I had TWRP installed and could boot into it numerous times before this)
anyone have any ideas?
I've installed twrp via fastboot
but I can't use the adb command to boot into recovery since device is not found,
when i try
adb devices
the list is empty,
and yes I've installed the latest google drivers via android studio
I've installed hi-suite
someome please help
jay0514 said:
so there I was in my car, my phone plugged in via aux cable and playing some music
suddenly I notice the music stops and my phone goes into a reboot,
I was using a pure nexus rom on marshmallow ( the latest marshmallow one i believe) and had xposed, and sometimes my phone would randomly reboot,
it was annoying but I could live with it
so i thought it was having another one of it's moment
but now it doesn't actually reboot,
my phone is stuck in a reboot loop and I can't even get into recovery mode, (I had TWRP installed and could boot into it numerous times before this)
anyone have any ideas?
I've installed twrp via fastboot
but I can't use the adb command to boot into recovery since device is not found,
when i try
adb devices
the list is empty,
and yes I've installed the latest google drivers via android studio
I've installed hi-suite
someome please help
Click to expand...
Click to collapse
Hi... You can't use adb commands while in bootloader... Only fastboot commands. Use the volume rocker till you see recovery mode displayed and press power button. If it still bootloop, try formatting cache and data with fastboot in bootloader and reboot in recovery again. If it still bootloop. Finally try fastboot flash a stock Google image. If none of these steps work, your phone is probably dead and you'll have to try to RMA your N6P.
Check this thread for further infos: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page21
5.1 said:
Hi... You can't use adb commands while in bootloader... Only fastboot commands. Use the volume rocker till you see recovery mode displayed and press power button. If it still bootloop, try formatting cache and data with fastboot in bootloader and reboot in recovery again. If it still bootloop. Finally try fastboot flash a stock Google image. If none of these steps work, your phone is probably dead and you'll have to try to RMA your N6P.
Check this thread for further infos: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page21
Click to expand...
Click to collapse
ohhh i see
yeh I dones't let me get to the recovery mode in the options from bootloader
and what are the commands to format cache and data in fastboot??
5.1 said:
Hi... You can't use adb commands while in bootloader... Only fastboot commands. Use the volume rocker till you see recovery mode displayed and press power button. If it still bootloop, try formatting cache and data with fastboot in bootloader and reboot in recovery again. If it still bootloop. Finally try fastboot flash a stock Google image. If none of these steps work, your phone is probably dead and you'll have to try to RMA your N6P.
Check this thread for further infos: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page21
Click to expand...
Click to collapse
and im trying to flash a stock google image
im following steps from the official android page
but how do I execute a .sh file?
the instruction is to go to the folder with files and execute 'flash-all.sh'
jay0514 said:
and im trying to flash a stock google image
im following steps from the official android page
but how do I execute a .sh file?
the instruction is to go to the folder with files and execute 'flash-all.sh'
Click to expand...
Click to collapse
First try:
fastboot format cache
fastboot format userdata
If the above doesn't solve your issue it's probably dead...
Check this thread for factory image flashing tutorial: https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page552
Good luck...
5.1 said:
First try:
fastboot format cache
fastboot format userdata
If the above doesn't solve your issue it's probably dead...
Check this thread for factory image flashing tutorial: https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page552
Good luck...
Click to expand...
Click to collapse
followed the guide to install stock rom,
still in reboot loop
how can a fine phone just die suddenly? :S
jay0514 said:
followed the guide to install stock rom,
still in reboot loop
how can a fine phone just die suddenly? :S
Click to expand...
Click to collapse
Sorry... Known issue with the N6P... Have you checked the tread I linked you in my first answer?
Good luck...
jay0514 said:
and im trying to flash a stock google image
im following steps from the official android page
but how do I execute a .sh file?
the instruction is to go to the folder with files and execute 'flash-all.sh'
Click to expand...
Click to collapse
Fastboot flash-all.sh is for Mac computers so presumably you have a Mac. Flash-all.bat is for windows. You need to unzip the Google image and move everything into the same folder where you have the fastboot program. Just open a command prompt window inside that folder and type the command. That's how I do it in Windows. Presumably the process is similar with a Mac. You will still have a zipped archive after you unzip the Google image but you want to leave that one as is. So far flashing flash-all.bat has gotten me out of every boot loop I've gotten into on my 6P but my phone never spontaneously bootlooped. I was always doing something (updating a rom, trying to restore a nandroid backup) that resulted in a bootloop. The fact that your phone boot looped without warning is probably a bad sign. If you still have warranty I would try to flash stock and see if you can RMA phone. If that isn't possible you might want to try staying on stock or using a different rom and seeing if the random reboots still occur. Good luck.
Well that really sucks. Sorry for your loss but it is a long running phone failure problem. I'm on my second 6P because this. Even worse to me is the fact your were running almost the exact same setup I am now. I refrained from running 7.x.x to try and minimize my chances of another BLOD so now w4on knows what to do. Lol
Sent from my Nexus 6P using XDA-Developers Legacy app
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition
Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding