Related
i tried installing a system font from the rom toolbox and when it rebboted it wasnt booting up... i can switch on my device but it remains in the glowing (X) and doesnt load up... i tried a factory reset i didnt work... i dont have a custom recovery nor do i have a nandroid backup on my device. i have rooted it using wugfresh's toolkit.
i have been trying many methods over the day and nothing seems to work. i have dowloaded a stock image from google's site but its on my pc. some help pls!!!!
i have the drivers installed on my windows 8 . atleast they were wokring intially when i got the root done on it . i have no clue what to do now !!
Your gonna have to flash the stock image from download mode. Never make changes to system files without doing a nandroid backup.
Wayne Tech Nexus
zelendel said:
Your gonna have to flash the stock image from download mode. Never make changes to system files without doing a nandroid backup.
Wayne Tech Nexus
Click to expand...
Click to collapse
i am sorry but i am new to nexus 4 ... how do i get into the download mode?
Irthu said:
i am sorry but i am new to nexus 4 ... how do i get into the download mode?
Click to expand...
Click to collapse
Read the stickies. They will get you all the info you need. If you are gonna try mods like this I would advise a full custom set up. As what your gonna do is gonna fully wipe your device.
Wayne Tech Nexus
zelendel said:
Read the stickies. They will get you all the info you need. If you are gonna try mods like this I would advise a full custom set up. As what your gonna do is gonna fully wipe your device.
Wayne Tech Nexus
Click to expand...
Click to collapse
is it possible to flash the img. file if my phone is recognised only in the bootloader mode? and i am assuming we have to flash the img. file using an adb software ?
Irthu said:
is it possible to flash the img. file if my phone is recognised only in the bootloader mode? and i am assuming we have to flash the img. file using an adb software ?
Click to expand...
Click to collapse
yes you will need to use fastboot which is part of adb
follow this thread: http://forum.xda-developers.com/showthread.php?t=2010312
PhantomGamers said:
yes you will need to use fastboot which is part of adb
follow this thread: http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
i have downloaded a zip from google's site and its about 300 odd mb. i am assuming i have to extract the the img. files and then do it ? but there are about 3-4 img. files such as :
system
boot
boot loader
radio
recovery
user data
since my phone does get into bootloader can u pls tell me which all img. files i need to flash? do i have to everyone of them?
the thread i linked answers all of your questions
(you really only need to flash the system image but to avoid confusion i would just follow the thread verbatim)
PhantomGamers said:
the thread i linked answers all of your questions
(you really only need to flash the system image but to avoid confusion i would just follow the thread verbatim)
Click to expand...
Click to collapse
thanks alot i will try doing it... i havent used the command prompt in windows ever before guess its time to learn how to do this..
Hello,
This is probably a noob question & I tried to research around myself. I've always rely on someone making a flashable stock rom for every update. I usually keep my phone rooted but run on stock rom with xposed. There's hasn't been a stock rom for m build published. Could anyone share the appropriate adb manual update instructions without factory resetting my phone? Thanks in advance.
Try this. http://forum.xda-developers.com/showpost.php?p=63774219&postcount=15
jimbotron said:
Hello,
This is probably a noob question & I tried to research around myself. I've always rely on someone making a flashable stock rom for every update. I usually keep my phone rooted but run on stock rom with xposed. There's hasn't been a stock rom for m build published. Could anyone share the appropriate adb manual update instructions without factory resetting my phone? Thanks in advance.
Click to expand...
Click to collapse
All you need to do is flash the factory images, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
All you need to do is flash the factory images, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Won't flashing the factory image wipe his data any way?
I think only when you unlock and relock the bootloader is when it'll erase data.
B_I_N_G_E said:
Won't flashing the factory image wipe his data any way?
Click to expand...
Click to collapse
No, you can do it without erasing data.
gqukyo said:
I think only when you unlock and relock the bootloader is when it'll erase data.
Click to expand...
Click to collapse
Using the flash-all batch file in the factory images will wipe the device, but you can do it manually without wiping.
Do I need to flash everything if I want to keep root? Or can I skip bootloader, recovery, and boot image files since the k build boot image works with m build?
Thanks in advance again
Sent from my Nexus 6P using XDA Free mobile app
jimbotron said:
Do I need to flash everything if I want to keep root? Or can I skip bootloader, recovery, and boot image files since the k build boot image works with m build?
Thanks in advance again
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
You can only skip the boot, recovery, and userdata images but all other files need to be flashed.
OK. How about bootloader file? Can I skip that too? Do I need to do anything new with su?
Sent from my Nexus 6P using XDA Free mobile app
jimbotron said:
OK. How about bootloader file? Can I skip that too? Do I need to do anything new with su?
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
As I said, you need to flash everything except for recovery, boot, and userdata. Just follow the usual process to root the updated build.
probably been asked a bunch but i have been reading and im all confused:
I'm rooted, TWRP, unlocked and stock. how do i take the newest update without wiping data? do i just let the phone go for it? and what's this about vendor stuff? my old device needed one zip and one zip only to update as root
reinaldistic said:
probably been asked a bunch but i have been reading and im all confused:
I'm rooted, TWRP, unlocked and stock. how do i take the newest update without wiping data? do i just let the phone go for it? and what's this about vendor stuff? my old device needed one zip and one zip only to update as root
Click to expand...
Click to collapse
Bonus points: how will it work in the future? some have been saying some updates are different than others
FlashFire.
If you want to flash an OTA update, you have to return to stock. Download Google's factory image, extract the boot. system. and Recovery images from the image and Flash those leaving your data alone. You are now back to stock and can let the OTA install normally
Sent from my Nexus 6P using Tapatalk
I'm rooted, twrp, and stock rom, just like you.
To update my phone I use this guide and works like a charm. You keep your system intact.
STEP 9
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
joooe said:
I'm rooted, twrp, and stock rom, just like you.
To update my phone I use this guide and works like a charm. You keep your system intact.
STEP 9
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
This.
joooe said:
I'm rooted, twrp, and stock rom, just like you.
To update my phone I use this guide and works like a charm. You keep your system intact.
STEP 9
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
that guide has multiple guides, which one did you use? the "How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)" seems to erase userdata as well...
uicnren said:
FlashFire.
Click to expand...
Click to collapse
please elaborate... all i get in a google search is "it's a tool" but there doesn't seem to be anything on how to use it to update and not loose userdata
reinaldistic said:
please elaborate... all i get in a google search is "it's a tool" but there doesn't seem to be anything on how to use it to update and not loose userdata
Click to expand...
Click to collapse
FlashFire.
And more info here.
And this is the first link returned when doing a google search for 'flashfire'.
reinaldistic said:
that guide has multiple guides, which one did you use? the "How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)" seems to erase userdata as well...
Click to expand...
Click to collapse
He said step 9.
Heisenberg said:
He said step 9.
Click to expand...
Click to collapse
and like i said that one reads like i have to erase userdata as well, just wondering how it's done without doing that.
As in is it just as simple as not flashing userdata.img and not formatting? or will that break something?
reinaldistic said:
and like i said that one reads like i have to erase userdata as well, just wondering how it's done without doing that.
As in is it just as simple as not flashing userdata.img and not formatting? or will that break something?
Click to expand...
Click to collapse
No, you don't have to format userdata when updating. He put that in there because people may want to flash all of the images including the userdata.img, which you shouldn't ever do. If you happen to want to wipe everything while updating (who knows), that is how you would do it.
reinaldistic said:
and like i said that one reads like i have to erase userdata as well, just wondering how it's done without doing that.
As in is it just as simple as not flashing userdata.img and not formatting? or will that break something?
Click to expand...
Click to collapse
Section 9 makes no mention of wiping userdata as part of the process. That section at the bottom only serves as a warning not to flash the userdata.img, and that if the user wishes to wipe they can use the format command instead.
nathanchance said:
No, you don't have to format userdata when updating. He put that in there because people may want to flash all of the images including the userdata.img, which you shouldn't ever do. If you happen to want to wipe everything while updating (who knows), that is how you would do it.
Click to expand...
Click to collapse
Perfect thanks
Heisenberg said:
Section 9 makes no mention of wiping userdata as part of the process. That section at the bottom only serves as a warning not to flash the userdata.img, and that if the user wishes to wipe they can use the format command instead.
Click to expand...
Click to collapse
meh it seemed like it did, i dont want bricks so jsut doublechecking
So I flashed the 7.1.1 update and everything was fine. I then tried to root through TWRP with the most recent version of recovery and and SuperSu and when I went to reboot it would get to the "Google" splash screen and go back to the warning. I then tried to restore to my Nandroid that I made right before the 7.1.1 flash but it does the same thing. I ended up doing a factory reset, still looping. I tried flashing an old firmware but it still would loop. I got desperate and did a full wipe and then flashed the old firmware from September's update but it still will not boot. I'm a long time lurker I just don't post much. Any help will be appreciated. Thanks in advance!
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Ahh, great. I tried searching to see if anyone else posted anything, couldn't find it.
jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Wait are you able to get into Recovery?
ChazLanier said:
Wait are you able to get into Recovery?
Click to expand...
Click to collapse
Nope. And so are other folks.
But if you can, there's still hope to save your device.
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
jamaniek said:
Nope. And so are other folks.
But if you can, there's still hope to save your device.
Click to expand...
Click to collapse
I can still get into recovery. I just can't get it past the Google splash screen.
ChazLanier said:
I can still get into recovery. I just can't get it past the Google splash screen.
Click to expand...
Click to collapse
Have you tried installing custom ROM, instead of a stock one?
And tell us what @ArminasAnarion asked for. There may be a pattern here. :good:
I haven't tried a custom ROM. I'll try that if I get any down time at work. Also, I'll check for you @ArminasAnarion in a bit.
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
ChazLanier said:
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
Click to expand...
Click to collapse
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
ArminasAnarion said:
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
Click to expand...
Click to collapse
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
ChazLanier said:
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
Click to expand...
Click to collapse
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
ArminasAnarion said:
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
Click to expand...
Click to collapse
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
ChazLanier said:
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
Click to expand...
Click to collapse
Oh okay cool! Good luck!
ArminasAnarion said:
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
Click to expand...
Click to collapse
Samsung storage, and I thought I was on -2 but it seems like I was on -1.
ArminasAnarion said:
Oh okay cool! Good luck!
Click to expand...
Click to collapse
Newest image didn't work either..
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
FWIW, I successfully updated to 7.1.1 NPF10C and rooted by using fastboot to flash bootloader, radio, boot, system, and vendor. Then used TWRP 3.0.2-2 to flash SuperSU 2.78 SR1. No issues.
Howie Dub said:
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
Click to expand...
Click to collapse
No luck on this either.
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.
nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.
tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.