Related
Hi guys I've been searching and cant seem to find an answer. My xt907 is rooted and my boot loader is unlocked I'm running CWM. If i install any 4.3 roms they work great for initial boot but as soon as i reboot it hangs at the warning boot loader unlocked screen. And the only way i can get the phone working again is to get to ap fastboot and use the DROID_RAZR_M_Utility_1.20 to factory reset everything. If i flash a 4.2.2 rom i don't have any problems. Any ideas guys ? Ive searched and cant seem to find an answer anywhere. Thanks in advance!
My first flash of 4.3 did this... after that I used twrp and haven't had it happen since...
Sent from my XT907 using xda app-developers app
The latest TWRP+mounting system prior to data/system wipes will probably solve your problems. Also, if you have a backup stored, you shouldn't need to fastboot every time.
I've been having the same problem. I thought it might be because I was using CWM, so I thought I'd give it a go with TWRP 2.323. I made a backup, wiped System, Formatted Data and wiped cache and Dalvik cache and installed [ROM][4.4.1][Official][OSE Rom][XT907].
It installed and booted up fine. After a restart, it hung on the bootloader screen. After booting up into TWRP and restoring the backup, it's still hanging on the bootloader unlocked screen. Doh!
I just reinstalled the new ROM and will hope I don't have to restart while I'm out today. Any ideas on things I can try to get things working?
Ryan F said:
I've been having the same problem. I thought it might be because I was using CWM, so I thought I'd give it a go with TWRP 2.323. I made a backup, wiped System, Formatted Data and wiped cache and Dalvik cache and installed [ROM][4.4.1][Official][OSE Rom][XT907].
It installed and booted up fine. After a restart, it hung on the bootloader screen. After booting up into TWRP and restoring the backup, it's still hanging on the bootloader unlocked screen. Doh!
I just reinstalled the new ROM and will hope I don't have to restart while I'm out today. Any ideas on things I can try to get things working?
Click to expand...
Click to collapse
twrp 2323???
You need twrp 2630
see my goodies.
aviwdoowks said:
twrp 2323???
You need twrp 2630
see my goodies.
Click to expand...
Click to collapse
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Ryan F said:
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Click to expand...
Click to collapse
Fastboot!
Extract the recovery.img from the zip.
But why do that, just flash the zip from your twrp you now have installed
Ryan F said:
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Click to expand...
Click to collapse
I believe the one that Avi has is a .zip, not a .xml, so it needs to be flashed in recovery. Load it up on your SD, boot into the recovery you have now, flash the new recovery, and then reboot recovery.
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Ryan F said:
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Click to expand...
Click to collapse
If your rom DL is corrupt?
Also
Arrrghhh has advice on twrp 263, http://forum.xda-developers.com/showthread.php?goto=newpost&t=2573153
It should apply to our 263 also.
---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------
I use their version (Q)(EDIT ONLY 261 HAS USB MOUNT) and it has usb mount! But it is hard to navigate but I am used to it
Ryan F said:
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Click to expand...
Click to collapse
Many people ran into this issue when 4.3 came out and then someone realized that we were forgetting something when wiping. It was something that we did when the BL was first unlocked, but everyone seemed to forget about it. We were forgetting to mount system, prior to performing wipes of the data/caches. Like Avi said, first, I would DL the ROM again and then place it in your SD. When you wipe, do the FDR option first. After that, go into mount and mount system. Then, go into the advanced wipe options and wipe data, system, cache/dalvik, and format data again. At this point, you can install the ROM as normal, don't re-mount system prior to installing, though. When I am done wiping, I always reboot recovery, but you don't have to do that.
aviwdoowks said:
If your rom DL is corrupt?
Also
Arrrghhh has advice on twrp 263, http://forum.xda-developers.com/showthread.php?goto=newpost&t=2573153
It should apply to our 263 also.
---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------
I use their version (Q)(EDIT ONLY 261 HAS USB MOUNT) and it has usb mount! But it is hard to navigate but I am used to it
Click to expand...
Click to collapse
Okay, I downloaded the zips again to make sure. This freezing at bootloader screen has happened with every of the dozen or so roms I've tried installing over the past 6 months since I unlocked the bootloader.
RikRong said:
Many people ran into this issue when 4.3 came out and then someone realized that we were forgetting something when wiping. It was something that we did when the BL was first unlocked, but everyone seemed to forget about it. We were forgetting to mount system, prior to performing wipes of the data/caches. Like Avi said, first, I would DL the ROM again and then place it in your SD. When you wipe, do the FDR option first. After that, go into mount and mount system. Then, go into the advanced wipe options and wipe data, system, cache/dalvik, and format data again. At this point, you can install the ROM as normal, don't re-mount system prior to installing, though. When I am done wiping, I always reboot recovery, but you don't have to do that.
Click to expand...
Click to collapse
Could you clarify a little bit?
1.) Mount system
2.) Wipe (Factory Reset: data, cache, dalvik)
3.) Format data
4.) Install zips
What's the FDR option?
---------- Post added at 09:21 AM ---------- Previous post was at 09:07 AM ----------
Ryan F said:
1.) Mount system
2.) Wipe (Factory Reset: data, cache, dalvik)
3.) Format data
4.) Install zips
Click to expand...
Click to collapse
Following the above steps didn't solve it The rom installs fine, boots up for first time normally, but still freezes on the bootloader screen after a restart.
Try geting to the bootloader options & choose normal pwr up.
The new twrp will stick at the big M sometimes.
Then the file is bad or you are missing the install steps. FDR (Factory Data Reset) is the first option you get when you go into the wipe menu, before you go into advanced options. Make sure you're wiping system too, after you mount. If it doesn't work, then it's a bad file or you're still doing something wrong. Upgrading to the most current TWRP and mounting system fixed the issues for 99% of the people. The other 1% just have one of those phones that is "quirky."
okay not sure if your still having this problem. But i never did solve my issue just kept using 4.2.2. But i just flashed the new jbx kernel and a KitKat rom the other along with the newest version on safestrap and i have no issues. Everything flashed and installed perfectly and it boots like a champ. So maybe just skip over 4.3 like i did and see if you still have the issues. Sorry didnt see you were trying to flash 4.4. Only thing i can suggest is make sure you have newest safestrap and wipe out the old etc. But im sure everyone already touched on this stuff before me
beady1 said:
okay not sure if your still having this problem. But i never did solve my issue just kept using 4.2.2. But i just flashed the new jbx kernel and a KitKat rom the other along with the newest version on safestrap and i have no issues. Everything flashed and installed perfectly and it boots like a champ. So maybe just skip over 4.3 like i did and see if you still have the issues. Sorry didnt see you were trying to flash 4.4. Only thing i can suggest is make sure you have newest safestrap and wipe out the old etc. But im sure everyone already touched on this stuff before me
Click to expand...
Click to collapse
Part of your problem is because you are using SS. If you're BL is unlocked, get rid of SS and use CWM or TWRP. SS is not a real recovery replacement, your stock recovery is still there. That's probably part of the reason you had issues.
possibly but i have 0 issues now so its not a big deal.
I have the stable Cyanogenmod 10.1 installed on my phone now. I'm able to restart my phone without any consequences finally. Yay.
I also tried the cm-11-20131221-NIGHTLY-xt907.zip build. That one would initially start up fine, but a restart gave me the frozen bootloader screen. I tried it twice, redownloading it, too. Gah, it's frustrating not being able to try out different roms, but at least I have one that works!
Well, thanks for the help guys. I'd still like to be able to install other roms, so if anyone else has something I can try, I'll do it!
Hi,
My nexus 4 was perfectly running the 4.4 kitkat when all of a sudden I received an OTA for build KRT16S. After the installation my phone didn't boot up and it's been stuck on google page ever since.
Details:
Rooted
twrp recovery 2.6.3.3
ART runtime
Encrypted.
My phone restarted straight into twrp, I typed the encryp. password and it started to install the new update automatically and it said successful.
I restart and it gets stuck on google page.
Please help guys
Many Thanks
You probably have too many customizations and especially running custom recovery. OTA is meant for stock Android.
Do a factory reset in TWRP and see if it boot. Otherwise search for a stock KRT16S rom in the development section, and use the TWRP sideload feature to install it.
eksasol said:
You probably have too many customizations and especially running custom recovery. OTA is meant for stock Android.
Do a factory reset in TWRP and see if it boot. Otherwise search for a stock KRT16S rom in the development section, and use the TWRP sideload feature to install it.
Click to expand...
Click to collapse
Thanks eksasol, I had the stock Android installed on this nexus and I got the ROM straight from google.
I will try doing a factory reset or installing the ROM from sideload. but would any of these erase my data?
Pulse.1995 said:
Thanks eksasol, I had the stock Android installed on this nexus and I got the ROM straight from google.
I will try doing a factory reset or installing the ROM from sideload. but would any of these erase my data?
Click to expand...
Click to collapse
Doing factory reset in TWRP won't wipe your internal storage, but it will clear your installed apps and its data ofcourse. Just don't select to wipe internal storage in the advance wipe. Installing rom zips will not wipe your data either.
If you want to backup everything from your internal storage, just connect the phone while in TWRP, then type: adb pull /data/media/ C:\backup\
I wiped and installed a fresh copy at the end and its working now.
Thanks eksasol for your help.
How do i mark this thread as resolved?
Pulse.1995 said:
I wiped and installed a fresh copy at the end and its working now.
Thanks eksasol for your help.
How do i mark this thread as resolved?
Click to expand...
Click to collapse
Just edit your thread title and write SOLVED before the title.
We’re excited to announce that we’ve released Remix OS 2.0 ROMs for Nexus 9 and Nexus 10. The Nexus 9 and Nexus 10 ROMs are now available for download here:
Nexus 9 ROM
http://www.jide.com/remixos/devices/nexus9
Nexus 10 ROM
http://www.jide.com/remixos/devices/nexus10
Flash Tutorial
http://support.jide.com/hc/en-us/articles/218081838
We’ve also been conscious of all the interest that Nexus 9 and 10 users have expressed in being able to experience Remix OS 2.0 on your tablets. And, although we’re still a relatively small team, we definitely heard your comments and are excited to finally have Remix OS 2.0 ready for you.
You can submit your bug report here:
http://bit.ly/1qh2jQq
Cheers
does this work on the lte variant?
Based on Android 5.11? No thanks.
I am not sure if I want to downgrade my nexus 9 to 5.11.
But Android 6.x and N are not good enough for me at least.
I am thinking if any other customize rom can be used.
Also Ubuntu for tablet might be a choice.
Any hopes of being able to load this via TWRP recovery? Or being able to load this via ADB while still keeping TWRP recovery?
Is there a possibility now to use google account and google services or still no?
Woofly said:
Any hopes of being able to load this via TWRP recovery? Or being able to load this via ADB while still keeping TWRP recovery?
Click to expand...
Click to collapse
You can fastboot flash while keeping twrp
maelfilk said:
Is there a possibility now to use google account and google services or still no?
Click to expand...
Click to collapse
It now comes with play store. Overall it's world's better than 1.5.
dictionary said:
You can fastboot flash while keeping twrp
It now comes with play store. Overall it's world's better than 1.5.
Click to expand...
Click to collapse
Sweet. Does it have Google Play Services as well? Are we able to run apps like Gmail and Play Music?
Woofly said:
Sweet. Does it have Google Play Services as well? Are we able to run apps like Gmail and Play Music?
Click to expand...
Click to collapse
Yes sir. Haven't tried play music, but running gmail and hangouts fine. When you fastboot flash things, just don't flash recovery. Also, I had to flash the old 5.1.1 bootloader and vendor first.
Anyone here NOT getting a bootloop after installing? what am i doing wrong here....
th3fallen said:
Anyone here NOT getting a bootloop after installing? what am i doing wrong here....
Click to expand...
Click to collapse
Working fine for me here. Was getting constant reboots and bootlooping before I flashed back to 5.1.1 first though. Bootloader and vendor especially. Then wiped everything but internal in TWRP, then fastboot flashed Remix except for twrp. Booted into TWRP before booting into the system. Worked great after that.
So does it work for LTE variant? Also anyone running custom kernel with it? (afaik FIRE-ICE has special kernel)
Bootloopers
To all those getting bootloop:
* Download latest 5.11 image LMY48T (not 6.x) https://developers.google.com/android/nexus/images#volantis
* In theory you only need to flash bootloader-flounder-3.44.1.0123.img however to be on the safe side I ran the whole ./flash-all.sh
* Now reboot the bootloader (even if you are already there, since we just flashed a different one), then run the following:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
# flashing vendor.img will solve the problem of annoying messages on boot/unstable play services
fastboot flash vendor vendor.img
# there is no userdata.img , so we can wipe userdata like so:
fastboot -w
* Now reboot and it should work great. With my experience so far it seems very stable
dictionary said:
Working fine for me here. Was getting constant reboots and bootlooping before I flashed back to 5.1.1 first though. Bootloader and vendor especially. Then wiped everything but internal in TWRP, then fastboot flashed Remix except for twrp. Booted into TWRP before booting into the system. Worked great after that.
Click to expand...
Click to collapse
Working fine for me here. Was getting constant reboots and bootlooping before I flashed back to 5.1.1 first though. Bootloader and vendor especially. Then wiped everything but internal in TWRP, then fastboot flashed Remix except for twrp. Booted into TWRP before booting into the system. Worked great after that.
Click to expand...
Click to collapse
That was my issue. Thanks
Bootloop on second boot
So after the tablet seemingly working perfectly and no boot loops on install, it is now only bootlooping after rebooting (even after wiping cache) And this is after installing 5.11 factory image before remix os.
Will try factory reset etc.
i am really interrested in this OS
but before i am doing anything i want to ask some questions
1) how far is google play and google play store integrated? can i open every app?
2) can i type without a manual keyboard?
3) is LTE supported in this version?
I will try this as soon as I get home. Can't wait to test it.
Fallon9111 said:
To all those getting bootloop:
* Download latest 5.11 image LMY48T (not 6.x) https://developers.google.com/android/nexus/images#volantis
* In theory you only need to flash bootloader-flounder-3.44.1.0123.img however to be on the safe side I ran the whole ./flash-all.sh
* Now reboot the bootloader (even if you are already there, since we just flashed a different one), then run the following:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
# flashing vendor.img will solve the problem of annoying messages on boot/unstable play services
fastboot flash vendor vendor.img
# there is no userdata.img , so we can wipe userdata like so:
fastboot -w
* Now reboot and it should work great. With my experience so far it seems very stable
Click to expand...
Click to collapse
What I find even easier, is to go into twrp. Do all the usual wipes (data, cache, dalvik, system), then reboot into bootloader. It'll say no OS installed in twrp, but that's fine. Then I fastboot flashed the 5.1.1 image manually, skipping recovery.img . Once done, I reboot recovery. It'll boot into twrp. (Doing this ensures that twrp won't be overwritten upon first boot). Then rebooted into 5.1.1. Just making sure it worked fine. Now reboot into twrp. Wipe the same things again, and this time install RemixOS. Again, reboot into twrp. Now reboot. Should be okay. I just don't like having to constantly reflash twrp. Either way works great though.
th3fallen said:
Working fine for me here. Was getting constant reboots and bootlooping before I flashed back to 5.1.1 first though. Bootloader and vendor especially. Then wiped everything but internal in TWRP, then fastboot flashed Remix except for twrp. Booted into TWRP before booting into the system. Worked great after that.
That was my issue. Thanks
Click to expand...
Click to collapse
No problem.
Fallon9111 said:
So after the tablet seemingly working perfectly and no boot loops on install, it is now only bootlooping after rebooting (even after wiping cache) And this is after installing 5.11 factory image before remix os.
Will try factory reset etc.
Click to expand...
Click to collapse
I've rebooted several times, including changing DPI, and no issues. I know you said you installed 5.1.1 prior, but did you do a complete wipe before flashing RemixOS?
oediv said:
i am really interrested in this OS
but before i am doing anything i want to ask some questions
1) how far is google play and google play store integrated? can i open every app?
2) can i type without a manual keyboard?
3) is LTE supported in this version?
Click to expand...
Click to collapse
1. I haven't tried every single app, nor will I, but gmail, hangouts, drive, Google+, all work fine.
2. You mean, is there an onscreen keyboard? If so, then yes. I haven't connected a hardware keyboard.
3. Not sure. Give it a try and let us know! It won't break LTE, so worst case scenario is you just flash back to whatever you had before.
---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------
maelfilk said:
So does it work for LTE variant? Also anyone running custom kernel with it? (afaik FIRE-ICE has special kernel)
Click to expand...
Click to collapse
The current 10.2.1 Fire and Ice will cause boot loops and break Wi-Fi. Elemental X for 5.1.1 works fine though. Running it now.
dictionary said:
I've rebooted several times, including changing DPI, and no issues. I know you said you installed 5.1.1 prior, but did you do a complete wipe before flashing RemixOS?
Click to expand...
Click to collapse
Yeah, I did a full factory image thing, and even let it boot once into 5.1.1 before rebooting back to fastboot and installing remix. I'm not sure what caused the boot loop problem, (wiping the caches and even a factory reset from twrp didn't fix this), but after flashing factory images then installing everything a 2nd time, the tablet seems to be working fine. So I'm not really sure why it went wrong (looking back in my terminal history I don't spot any obvious errors)...
Fallon9111 said:
Yeah, I did a full factory image thing, and even let it boot once into 5.1.1 before rebooting back to fastboot and installing remix. I'm not sure what caused the boot loop problem, (wiping the caches and even a factory reset from twrp didn't fix this), but after flashing factory images then installing everything a 2nd time, the tablet seems to be working fine. So I'm not really sure why it went wrong (looking back in my terminal history I don't spot any obvious errors)...
Click to expand...
Click to collapse
Yeah that's odd. After I flashed 5.1.1 and let it boot, I rebooted to TWRP, and wiped data, cache, system, and dalvik. Then rebooted to bootloader, then fastboot, and flashed boot.IMG, system.IMG, cache.IMG and vendor.IMG. Didn't have an issue. Glad it's working now for you though.
Okay, so I've been reading XDA for a while now to root my devices and install custom ROMs and its been incredibly helpful. However I have a huge issue with my nexus 6p and can't find a way to solve it.
Here goes....
I bought it of eBay a few months ago and unlocked the boot loader and rooted the phone plus i also installed twrp and made a nandroid backup. I then installed pure nexus rom and the phone was working incredibly well.
Fast forward to this week, I decided I wanted to upgrade to cm13, since I missed the cm theme engine. So I Wiped my device clean using twrp. And installed cm 13 and the gapps then rebooted.
The phone booted perfectly but on the optimising apps screen it would reboot and tell me to enter the password that I originally had on the pure nexus ROM. After doing so it would re optimise the apps but would crash and reboot. It was doing this continuously.
Twrp also asked for this password on every boot before it let me see the main recovery menu.
So then I took the logical next step and decided to wipe the phone clean again using twrp. Seeing as my password seemed to not clear the first time.
After the wipe, I decided to use the original nandroid backup to restore my device as the password thing was still showing up. And cm 13 was still not installing. Neither was pure nexus.
Okay this is where it went downhill. I hit restore and had everything checked. The process was going well but instead of the restore completing and twrp saying it was successful. It crashed halfway and rebooted.
Since then its stuck in a bootloop. Its on the google splash screen and then reboots to the google splash screen continuously. And does not boot to the os.
On another note. The bootloader is still unlocked. The recovery works. And so does adb/fastboot. So I wouldn't consider it hard bricked.
Here's what I've tried so far:
I've used the wugfresh root toolkit to flash stock and unroot the phone. With softbrick checked. Still nothing. Phone boots to the splash screen and then reboots to the splash screen.
I then reflashed twrp 3.0.2-1 . which worked And its not asking for my password anymore.
Again I tried restoring from my nandroid and it crashed midway which makes me think the nandroid backup is/was corrupted causing the issue in the first place?
I've also tried to just restore and Flash twrp again and then install pure nexus ROM. And still nothing?
I can also still mount my phone to the PC and copy and remove files.
On another note I find it interesting that although the ROM is installed. And the storage bar on my PC is partially filled showing that it clearly has a ROM installed. The phone does not have the standard android file system. Just the twrp backup folder and that's it.
I would be honoured if you could help me out here. And get my 6p up and running again.
Thank you . [emoji45]
I would suggest you flash the factory stock system image using fastboot to get your 6P back up and running.
If you don't have the factory image they can be downloaded from here
Extract the factory image then use fastboot to flash
Code:
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
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
Check out this guide which has all the information you need, especially around device encryption and flashing roms. Lastly gaining root is as simple as flashing SuperSU or Phh's SuperUser in TWRP.
I hope that helps, let me know if you get stuck.
Yea just flash stock image I had this happen to me before and flashing stock image fixed it.
Thanks guys. I'm going to read the guide and try it out. Then let you know how it all goes. Fingers crossed it all works
Sent from my ONE A2003 using Tapatalk
im_Zak said:
Thanks guys. I'm going to read the guide and try it out. Then let you know how it all goes. Fingers crossed it all works
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
FYI don't backup efs partition with that version of twrp. It's a known issue.
i did not realize that twrp had that issue
And guys, I followed the fastboot process by the letter and although everything worked well. The nexus 6p is still bootlooping on the google splash screen and not going any further. :crying:
What should I do? i've added the cmd window screenshot so you guys can have a look.
Try this thread:
http://forum.xda-developers.com/and...r-bootloop-t3454938/post68872362#post68872362
I worked for me when I was having issues. If it worked for you, please make sure to thank the OP in the thread.
this looks promising. thank you. i'll have a go now. might need your help if i get stuck somewhere though :good:
pctechdroid said:
Try this thread:
http://forum.xda-developers.com/and...r-bootloop-t3454938/post68872362#post68872362
I worked for me when I was having issues. If it worked for you, please make sure to thank the OP in the thread.
Click to expand...
Click to collapse
Thank you so so much dude. After countless hours trying everything to get my nexus 6p up and running to no avail this post did the trick.
Respect!!?✌✌??
im_Zak said:
Thank you so so much dude. After countless hours trying everything to get my nexus 6p up and running to no avail this post did the trick.
Respect!!
Click to expand...
Click to collapse
Upgrade to TWRP 3.0.2-2 real quick. You didn't need that guide(in terms of his nandroid) but I am glad it worked. Just need to wipe efs partition using adb commands.
I see. And I have upgraded to the latest twrp so hopefully it doesn't not happen again
Sent from my ONE A2003 using Tapatalk
im_Zak said:
I see. And I have upgraded to the latest twrp so hopefully it doesn't not happen again
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Good deal!!! There's a build that's unofficial of 3.0.2-3 that you can also jump onto. The current version 3.0.2-2 has a bug with backups on Android N. There was a comprehensive post that someone made about the issues with the different versions but I cannot find it for the life of me.
Jammol said:
Good deal!!! There's a build that's unofficial of 3.0.2-3 that you can also jump onto. The current version 3.0.2-2 has a bug with backups on Android N. There was a comprehensive post that someone made about the issues with the different versions but I cannot find it for the life of me.
Click to expand...
Click to collapse
Thanks for the heads up!
Hey guys so my phone appears to me to be bricked. I have a rooted angler on stock 7.0.0 (NBD90X, Oct 2016). I have ElementalX kernal.
A few weeks ago I was looking in to putting on MultiROM. After I flashed the custom TWRP recovery for MultiROM, the recovery wouldn't work. It just goes to the TWRP blue startup screen and freezes. I have been procrastinating on flashing a functioning recovery ever since. I know, I'm an idiot. Lesson learned. Well the November security update was pushed to my phone a few days ago. I ignored it. Last night I wanted to see if the update included 7.1 or if it was just security update, so I tapped on the update notification and it automatically downloaded the updates without prompt (which I did not want to do.)
Well an hour later my phone died. When I plugged in to the charger, it immediatly started up by itself and booted to the non-functioning recovery and froze. It does this every time I try to boot the device now. I booted in to the bootloader and tried plugging in to my PC to flash a working recovery, but the device will not get picked up by the PC anymore. I don't believe it's a driver issue I use adb all the time with this same device and pc.
Also want to add, factory reset from bootloader went to google startup animation, but then just shut off as soon as it was done. Also, when I select shutdown from bootloader with it plugged in to charger, it will turn off and stay off but does not appear to be charging in any way.
Well that's the backstory. Any help you all can provide is very much appreciated. Turns out the battery in my backup phone is only good for a couple hours anymore. You all know how helpless we are without our phones, ha! Please help! Is it bricked?
I'm confused. How did you factory reset from the bootloader? That's done from recovery. Also, when in the bootloader you use fastboot, not ADB. ADB is not used from the bootloader. Only while booted into android or from recovery.
Use fastboot to flash factory images and you should be Okay.
RoyJ said:
I'm confused. How did you factory reset from the bootloader? That's done from recovery. Also, when in the bootloader you use fastboot, not ADB. ADB is not used from the bootloader. Only while booted into android or from recovery.
Use fastboot to flash factory images and you should be Okay.
Click to expand...
Click to collapse
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Nebul0us said:
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Click to expand...
Click to collapse
Never messed with that so I'm not sure. Since your bootloader is unlocked just download and install what you need. Start by downloading and flashing TWRP. In the 6P original development section, find the thread and search it for 3.0.2-3. It's an unofficial version that fixes the issues since (-1). After you flash that boot into it and go to 'Wipe' > Factory reset. You can also do 'Wipe' > Advanced and select system, data, cache & dalvik. Do not select internal storage. After that download a factory image zip. Extract it and flash the bootloader and radio images from fastboot. Now extract the 2nd zip inside of the 1st one and in that folder you'll find system.img, boot.img, vendor.img, cache.img, recovery.img & userdata.img.
Flash those with the exceptions of userdata.img, cache.img & recovery.img. No need to flash recovery if you plan on keeping TWRP. Cache was taken care of from TWRP in the previous step and flashing userdata will wipe your internal storage. Plus you don't want to flash that anyways if your storage is more than 32gb. Refer to Heisenberg's guide for more info.
Edit: If you can boot to bootloader your device should be read with 'fastboot devices' - if it isn't, delete any Android / Nexus / Google drivers. **Reboot your PC** and install them again. After you install them again reboot your PC one more time and try again.
RoyJ said:
Never messed with that so I'm not sure. Since your bootloader is unlocked just download and install what you need. Start by downloading and flashing TWRP. In the 6P original development section, find the thread and search it for 3.0.2-3. It's an unofficial version that fixes the issues since (-1). After you flash that boot into it and go to 'Wipe' > Factory reset. You can also do 'Wipe' > Advanced and select system, data, cache & dalvik. Do not select internal storage. After that download a factory image zip. Extract it and flash the bootloader and radio images from fastboot. Now extract the 2nd zip inside of the 1st one and in that folder you'll find system.img, boot.img, vendor.img, cache.img, recovery.img & userdata.img.
Flash those with the exceptions of userdata.img, cache.img & recovery.img. No need to flash recovery if you plan on keeping TWRP. Cache was taken care of from TWRP in the previous step and flashing userdata will wipe your internal storage. Plus you don't want to flash that anyways if your storage is more than 32gb. Refer to Heisenberg's guide for more info.
Click to expand...
Click to collapse
I can't get the PC/fastboot to recognize the device. I've never had a problem getting my pc to pick it up before. I even reinstalled the drivers.
Nebul0us said:
I can't get the PC/fastboot to recognize the device. I've never had a problem getting my pc to pick it up before. I even reinstalled the drivers.
Click to expand...
Click to collapse
How are you installing them? Using a toolkit? If so, stop and use the instructions in this thread. You shouldn't have any issues. Make sure you're rebooting your PC after deleting all Android / Nexus / Google drivers before installing them again. Install using the guide and reboot again.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page508
Edit/addition: Toolkits often use outdated or incomplete ADB/fastboot drivers. Always always always use the Android SDK to install them. That way you will always have the latest versions. If you ever have issues detecting your phone, just open the SDK and check for updates.
RoyJ said:
How are you installing them? Using a toolkit? If so, stop and use the instructions in this thread. You shouldn't have any issues. Make sure you're rebooting your PC after deleting all Android / Nexus / Google drivers before installing them again. Install using the guide and reboot again.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page508
Edit/addition: Toolkits often use outdated or incomplete ADB/fastboot drivers. Always always always use the Android SDK to install them. That way you will always have the latest versions. If you ever have issues detecting your phone, just open the SDK and check for updates.
Click to expand...
Click to collapse
Okay so I left the phone on the charger with the frozen screen in twrp multirom edition. After that rebooted in to the bootloader. I then selected the factory option. If loaded the google animation like before, but this time actually booted up the system. The notification bar had two diagnostic tools that said tap to run...one was called sims i think? Anyways I held power button and did a hard reboot. It booted up fine. I then used twrp manager to install 3.0.2.2....then i used fastboot to flash 3.0.2.3 that i had a copy of. Things seem to be working fine now. Close call. I'm not sure what the factory option is in the bootloader, but it's not factory reset and it was the only way I could boot. I think the phone was trying to boot to recovery to install the latest updates and I had to boot to factory to get it out of "update mode," if you will...
Does anyone know what the factory option is in the bootloader?
Thanks for your help RoyJ
Nebul0us said:
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Click to expand...
Click to collapse
Factory options is meant to restart the system with some manufacturers apps available just so you can test certain functions of the phone, mostly to see if all sensors and hardware are working properly.