Database Users

ROM installation help

I managed to flash correct following the sticky:
http://forum.xda-developers.com/showpost.php?p=12898827&postcount=3
I decided to use this ROM:
http://forum.xda-developers.com/showthread.php?t=1121333
I already had 2.3.7 installed with an older kernal, but this was first time I did a manual installation. Anyway, from both guides, they say to type "fast flash boot boot.img" etc but this didn't work for me, so I had to type "fastboot flash boot openswift5.0b4_boot.img". I had to do the same for the system image as well. Is this still okay?
Secondly, from that ROM, there were two boot img files. One was called boot, the other was called "nohack boot". I just used the "boot" one then proceeded with the "system" img file. Was this okay as well or have I done something incorrectly?
Thankfully, my phone appears okay and everything worked, but I just want to make sure I did follow the steps correctly so that I don't have any major problems in the future.
Also, I remember reading somewhere that there was a "memory fix" which made things faster. Does this ROM include it or is this memory fix something else I must do.
Fianally, for this current ROM, did I need to change my memory settings because I have never altered any partition sizes etc.
Sorry for the noobie questions, I did try and follow the stickies etc, just want to make 100% sure cheers.
PS: I know it mentions something in he changelog for the ROM about memory fixes etc, but I didn't fully understand what it meant.

djpailo said:
Anyway, from both guides, they say to type "fast flash boot boot.img" etc but this didn't work for me, so I had to type "fastboot flash boot openswift5.0b4_boot.img". I had to do the same for the system image as well. Is this still okay?
Click to expand...
Click to collapse
So far so good...
djpailo said:
Secondly, from that ROM, there were two boot img files. One was called boot, the other was called "nohack boot". I just used the "boot" one then proceeded with the "system" img file. Was this okay as well or have I done something incorrectly?
Click to expand...
Click to collapse
also good!
djpailo said:
Also, I remember reading somewhere that there was a "memory fix" which made things faster. Does this ROM include it or is this memory fix something else I must do.
Click to expand...
Click to collapse
I think you are talking about the V6-supercharger. You can try it out, but for me it didn't work very well. (But that was on IceCreamSwift, don't know about this rom. So just try it.)
djpailo said:
Fianally, for this current ROM, did I need to change my memory settings because I have never altered any partition sizes etc.
Click to expand...
Click to collapse
As a rule of thumb, if the startpost of the rom doesn't say anything about the sizes, leave them to default. If you are still in doubt, check in Titanium Backup or some file explorer or another program how much space is left in your /system partition. I always try to keep at least 10 MB free, just in case, but even 1 kb should be fine.
Good luck!

thanks for your help!
I have noticed a fairly annoying problem, the play store app is gone!
I tried downloading it again from an apk from another website. Every time I open it, it asks me to add an account, but I already successfully added my google account and synced contacts from it etc.
??

Its been nearly two days:
- I have tried flashing to a new version of recovery and then reflashing the same ROM all using the following commands:
fastboot flash recovery recovery_clockwork_3.0.2.4_swift.img
fastboot -w
fastboot erase boot
fastboot erase system
fastboot flash boot boot.img
fastboot flash system system.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
I still have these major problem with the market. I tried downloading the market application, and whenever it says I need to add an account, I press the add button and it just exits the application and goes back to the previous page.
From the ROM I'm trying to install, the installation instructions are:
use fastboot
adb reboot bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
The one in bold I never used. Doing some digging, apparently this means "this will reboot your phone back into the bootloader (white screen with the android on wheels" but I think I just did a few longer steps to do the same thing..
So does no-one know what my problem is?

adb reboot bootloader is the same like booting into fastboot (camera + power buttons)
try to add your google account in settings>accounts & sync>add new google account
because setup wizard is facing problems sometimes

andreas__ said:
adb reboot bootloader is the same like booting into fastboot (camera + power buttons)
try to add your google account in settings>accounts & sync>add new google account
because setup wizard is facing problems sometimes
Click to expand...
Click to collapse
Yes, I had tried that before.
I tried it again after reflashing and it still doesn't work. I have the account added and email synced, but when I open google play, it still asks me to add an account, and clicking either yes or no just returns to the previous page.
I also tried downloading the gmail app (which didn't come with this rom). It installed, but whenever I open it, it just opens and closes very quickly???

djpailo said:
Yes, I had tried that before.
I tried it again after reflashing and it still doesn't work. I have the account added and email synced, but when I open google play, it still asks me to add an account, and clicking either yes or no just returns to the previous page.
I also tried downloading the gmail app (which didn't come with this rom). It installed, but whenever I open it, it just opens and closes very quickly???
Click to expand...
Click to collapse
Maybe create anther Google account and test if it works
Edit: don't use other market.apk ! Just add Google account and play store will appear
Sent from my LG GT540 using xda premium

Pls delete

andreas__ said:
adb reboot bootloader is the same like booting into fastboot (camera + power buttons)
try to add your google account in settings>accounts & sync>add new google account
because setup wizard is facing problems sometimes
Click to expand...
Click to collapse
andreas__ said:
Maybe create anther Google account and test if it works
Edit: don't use other market.apk ! Just add Google account and play store will appear
Sent from my LG GT540 using xda premium
Click to expand...
Click to collapse
Thanks for your reply! Before I saw this, I decided to try a different ROM and everything worked fine! I'm now using SDSL v2.1. Thanks for your help, and when I flash again and things go wrong, I'll remember your advice to try adding a different account. It was a weird problem though thats for sure!

I messed up for sure. Need help

Basically what I did was follow this guide here http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I used step number 9 to install the MHC19I update while I was on Pure Nexus ROM and Elemental X Kernel. Then, I went ahead and dirty flashed the newer version of the ROM and kernel, but I made a nandroid back-up beforehand on TWRP 3.0.0.1. So when it finished and reboot, none of the apps worked. Everything I tried to open gave me a message saying "unforunately X has stopped" with a report and ok button options. Couldn't really use the phone at all. So I tried restoring the back up that I made and now it's either 1)taking a really long time or 2) not booting up at all because all it says is Google with the white unlocked lock at the bottom and hasn't changed.
I'm pretty sure I messed up pretty bad, so I'd appreciate some guidance on what to do. Thank you

suckafoola said:
Basically what I did was follow this guide here http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I used step number 9 to install the MHC19I update while I was on Pure Nexus ROM and Elemental X Kernel. Then, I went ahead and dirty flashed the newer version of the ROM and kernel, but I made a nandroid back-up beforehand on TWRP 3.0.0.1. So when it finished and reboot, none of the apps worked. Everything I tried to open gave me a message saying "unforunately X has stopped" with a report and ok button options. Couldn't really use the phone at all. So I tried restoring the back up that I made and now it's either 1)taking a really long time or 2) not booting up at all because all it says is Google with the white unlocked lock at the bottom and hasn't changed.
I'm pretty sure I messed up pretty bad, so I'd appreciate some guidance on what to do. Thank you
Click to expand...
Click to collapse
If you followed step 9 you should be on the latest vendor, bootloader and radio. Go to the pure nexus thread and download the the newest Gapps release. I would verify the rom download and make sure it wasn't corrupted. Maybe redownload it to make sure. Boot in to TWRP and go to advance wipe. Select everything except internal data. Once it is wiped go to install and flash PureNexus rom, Gapps and then your custom kernal if you wish. You should be good to go after that.

murphyjasonc said:
Go to the pure nexus thread and download the the newest Gapps release... Once it is wiped go to install and flash PureNexus rom, Gapps and then your custom kernal if you wish. You should be good to go after that.
Click to expand...
Click to collapse
Thanks, I will try this right now. Just a question though, once I download Gapps, how do I flash it on the phone since I don't have it downloaded on my phone?

suckafoola said:
Basically what I did was follow this guide here http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I used step number 9 to install the MHC19I update while I was on Pure Nexus ROM and Elemental X Kernel. Then, I went ahead and dirty flashed the newer version of the ROM and kernel, but I made a nandroid back-up beforehand on TWRP 3.0.0.1. So when it finished and reboot, none of the apps worked. Everything I tried to open gave me a message saying "unforunately X has stopped" with a report and ok button options. Couldn't really use the phone at all. So I tried restoring the back up that I made and now it's either 1)taking a really long time or 2) not booting up at all because all it says is Google with the white unlocked lock at the bottom and hasn't changed.
I'm pretty sure I messed up pretty bad, so I'd appreciate some guidance on what to do. Thank you
Click to expand...
Click to collapse
The problem is most likely that you dirty flashed the ROM. Also, what partitions did you backup/restore?

Worse comes to worst, you can just flash the factory image to boot back up

suckafoola said:
Thanks, I will try this right now. Just a question though, once I download Gapps, how do I flash it on the phone since I don't have it downloaded on my phone?
Click to expand...
Click to collapse
You can add gapps to your phone using adb or just connect your phone to your computer when you are in TWRP, your computer should recognize your phone's internal storage and you can just move it there.

suckafoola said:
Thanks, I will try this right now. Just a question though, once I download Gapps, how do I flash it on the phone since I don't have it downloaded on my phone?
Click to expand...
Click to collapse
You can download it in your PC then just plug your phone in and transfer the file over. Your phone will most likely be defaulted to USB charge mode though. Once you plug it in to your USB port an option on your phone should pop up to be able to change it to mtp file transfer. Then just copy the file to your internal storage, reboot in to TWRp and flash it in the steps above.

I use Superbeam a lot to transfer files from my computer to my phone if I don't want to find the plug to hook up the phone to the computer. I have also used pushbullet to send the link to my phone, and then download the file directly to the phone.

Trying to Manually Downgrade from Android N Beta 3 to Marshmallow

I have been trying to go back to Marshmallow from the N beta 3 preview for a few days now, but it doesn't seem to be working any way I try. I originally tried to use the OTA method by unenrolling my device because that is the way I got the preview to begin with. Every time I tried that, though, it would end in an error after trying to install the update. So i tried flashing the Marshmallow images manually using fastboot. I flashed everything, including the bootloader, radio, recovery, boot, system, vendor, cache, and userdata, but when I tried rebooting, it would be stuck on the Google logo. Can someone please tell me if I am doing something wrong or can maybe help somehow? Thanks in advanced!

asadabbas95 said:
I have been trying to go back to Marshmallow from the N beta 3 preview for a few days now, but it doesn't seem to be working any way I try. I originally tried to use the OTA method by unenrolling my device because that is the way I got the preview to begin with. Every time I tried that, though, it would end in an error after trying to install the update. So i tried flashing the Marshmallow images manually using fastboot. I flashed everything, including the bootloader, radio, recovery, boot, system, vendor, cache, and userdata, but when I tried rebooting, it would be stuck on the Google logo. Can someone please tell me if I am doing something wrong or can maybe help somehow? Thanks in advanced!
Click to expand...
Click to collapse
Not trying to say you're lying but are you sure you flashed everything? Are you using the flash all script or are you doing each image manually?
Mainly you need to flash boot, system, vendor, and userdata. Userdata just wipes that partition.
The N bootloader and radio should be compatible with the latest marshmallow release.
My best guess is if you used the flash all it didn't work, because it never works.
If not that then maybe you got a corrupted file? Try redownloading it and try again.
Sent from my Nexus 6P using Tapatalk

Nah I don't use the flash all script. I flashed everything manually and I didn't forget anything. I actually tried this twice and used a new file the second time so it's really weird. I have no idea what's wrong

I am having the SAME EXACT issue. Found this on a search. Any solutions?

asadabbas95 said:
Nah I don't use the flash all script. I flashed everything manually and I didn't forget anything. I actually tried this twice and used a new file the second time so it's really weird. I have no idea what's wrong
Click to expand...
Click to collapse
Try this command first: "fastboot format userdata" - then flash all images, exept "userdata.img".

ADB Sidleoading this file worked for me https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip

I'm.at work or else I would try that method can anyone try it and see what happens . I'm trying to go back to mm also
Sent from my Nexus 6P using Tapatalk

ClassickWORLD said:
ADB Sidleoading this file worked for me https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
So you wiped everything and used that ? Can we just flash that or does it have to be side loaded I'm.on N it works but I don't wanna go back to MM cuz it's causing issues to others from what I heard I can keep the bootloader and radio but everything else you gotta flash would you lose root or have to re unlock the bootloader?
Sent from my Nexus 6P using Tapatalk

Okay so I'm not the only one who's having this problem. Did the sideloading method format the sd card?

havy15 said:
So you wiped everything and used that ? Can we just flash that or does it have to be side loaded I'm.on N it works but I don't wanna go back to MM cuz it's causing issues to others from what I heard I can keep the bootloader and radio but everything else you gotta flash would you lose root or have to re unlock the bootloader?
Click to expand...
Click to collapse
Download the file and rename it whatever you want. I changed it to update.zip.
Go to stock recovery and then select update from adb.
Then type ---> adb sideload "name of zip".
You will then be downgraded to stock MM with everything working.
Well at least that's what worked for me. Because I was on Android N Preview 3. It was too buggy so I tried to manually flash 6.0.1. but kept getting stuck on the white Google logo. The above method worked for me.

Are you rooted still? Someone told me if I'm going to pure rom all I need to do is wipe like normal like when you u flash a ROM and with gaps and I'll be fine with the vender image . Or do I have to do it your way . Did you go back to stock mm or a rom ?
Sent from my Nexus 6P using Tapatalk

ClassickWORLD said:
ADB Sidleoading this file worked for me https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
This didn't work for me either. I tried sideloading and it was sending the file, but it stopped at .02% and it gave me an error 7 and the download failed...This is really starting to annoy me because so many apps are really buggy for me on N

Yeah Snapchat is super buggy and my phone stays crashing when it warms up lol . But I'm rooted unlocked bootloader Android N I'm trying to stay rooted unlocked bootloader and go back to MM how can I do that ?!?!?! ?? Like I'm legit frustrated lol
Sent from my Nexus 6P using Tapatalk

havy15 said:
Yeah Snapchat is super buggy and my phone stays crashing when it warms up lol . But I'm rooted unlocked bootloader Android N I'm trying to stay rooted unlocked bootloader and go back to MM how can I do that ?!?!?! Like I'm legit frustrated lol
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Lol trust me i know. I've been trying for so long and it's so frustrating that I can't do anything except wait for the official release to come out

​
asadabbas95 said:
Lol trust me i know. I've been trying for so long and it's so frustrating that I can't do anything except wait for the official release to come out
Click to expand...
Click to collapse
are you trying to back to stock or another mm rom

havy15 said:
​
are you trying to back to stock or another mm rom
Click to expand...
Click to collapse
I tried both..neither worked

asadabbas95 said:
I tried both..neither worked
Click to expand...
Click to collapse
well i just read to go back to a mm rom you just have to wipe like when you flash a rom in general then go and flash rom gapps and vender and it should be solid

havy15 said:
well i just read to go back to a mm rom you just have to wipe like when you flash a rom in general then go and flash rom gapps and vender and it should be solid
Click to expand...
Click to collapse
nah i tried that and was stuck on the google logo

asadabbas95 said:
nah i tried that and was stuck on the google logo
Click to expand...
Click to collapse
really thats what people are telling me to do and they say its working. you sure you are flashing the correct vender for that rom?

havy15 said:
really thats what people are telling me to do and they say its working. you sure you are flashing the correct vender for that rom?
Click to expand...
Click to collapse
yup flashed everything correctly. Try flashing and tell me if it works for you

Problem after root..HELP

So I was on the stock marshmallow ROM and decided to root and so after that I got a google play service force close error and then it wouldn't let me download Facebook and some other apps. So I wiped clean and flashed pure nexus and flashed the 2.47 (I think it was) Super user root .zip and still same issue. Anyone know why its doing this ? I can't even open Facebook ..it closes and gives me the google play services error.
Edit: now Snapchat instantly closes and says Snapchat has stopped

jordy787 said:
So I was on the stock marshmallow ROM and decided to root and so after that I got a google play service force close error and then it wouldn't let me download Facebook and some other apps. So I wiped clean and flashed pure nexus and flashed the 2.47 (I think it was) Super user root .zip and still same issue. Anyone know why its doing this ? I can't even open Facebook ..it closes and gives me the google play services error.
Edit: now Snapchat instantly closes and says Snapchat has stopped
Click to expand...
Click to collapse
Exactly what procedure did you follow to install the ROM?

jordy787 said:
So I was on the stock marshmallow ROM and decided to root and so after that I got a google play service force close error and then it wouldn't let me download Facebook and some other apps. So I wiped clean and flashed pure nexus and flashed the 2.47 (I think it was) Super user root .zip and still same issue. Anyone know why its doing this ? I can't even open Facebook ..it closes and gives me the google play services error.
Edit: now Snapchat instantly closes and says Snapchat has stopped
Click to expand...
Click to collapse
That would be an outdated version SuperSu. Try this one

DJBhardwaj said:
Exactly what procedure did you follow to install the ROM?
Click to expand...
Click to collapse
I wiped data (not SD data) and wiped cache and then flashed pure nexus,gapps and then the superus.zip

83097markcynt said:
That would be an outdated version SuperSu. Try this one
Click to expand...
Click to collapse
I just flashed that but same issue ..but noticed xposed works now with this

I tried 3 different Roms and Google play store keeps force closing when I try to install Facebook. If I install Facebook apk from Google it doesn't always open. And Snapchat won't open it just crashes...I don't know what to do ..did I not decrypt it or whatever ? I remember is asked Me for a password in twrp but I clicked back arrow and wiped..I never typed the password ..can that be why?

jordy787 said:
I wiped data (not SD data) and wiped cache and then flashed pure nexus,gapps and then the superus.zip
Click to expand...
Click to collapse
Are data and cache all you wiped? You should wipe system and dalvik cache too before flashing a ROM. Also, which gapps did you flash?

Heisenberg said:
Are data and cache all you wiped? You should wipe system and dalvik cache too before flashing a ROM. Also, which gapps did you flash?
Click to expand...
Click to collapse
I did that as well , I used purenexus gapps. I think I figured it out..whenever I used the modified wanam xposed install zip ,that is when it gives me the problems ? do you know the correct 6p xposed?

jordy787 said:
I did that as well , I used purenexus gapps. I think I figured it out..whenever I used the modified wanam xposed install zip ,that is when it gives me the problems ? do you know the correct 6p xposed?
Click to expand...
Click to collapse
I don't use Xposed but I'm guessing there's a thread for it in the general section for this device.

use http://www.wugfresh.com/nrt/
that tool is amazing.

i killed tupac said:
use http://www.wugfresh.com/nrt/
that tool is amazing.
Click to expand...
Click to collapse
There's literally nothing in this thread that requires a toolkit.

Heisenberg said:
There's literally nothing in this thread that requires a toolkit.
Click to expand...
Click to collapse
it will fix his softbricked phone with two clicks, he deosn't need most of what it can do, but its still the easiest way for him to fix it. Let him decide what to do.

This is the xposed version you want to use. I would suggest downloading the factory image and running the batch file in it. Then setting the phone up from there. also use the latest supersu 2.76 from HERE

i killed tupac said:
it will fix his softbricked phone with two clicks, he deosn't need most of what it can do, but its still the easiest way for him to fix it. Let him decide what to do.
Click to expand...
Click to collapse
Easiest doesn't mean best. A toolkit bypasses any learning that's required to keep this from happening again. Plus it's better to know how you're fixing something, a toolkit removes that.

6P still bootlooping after flashing stock.

So i was going to downgrade from android 7.0 (DigitalHigh6P rom). I flashed the newest 6.0.1 factory images, but no matter what i do, it still bootloops. I have tried sideloading an ota file, wiped everything several times. My bootloader is unlocked (of course).
I never get to the android boot animation.
what do?

I had the same issue upon installing N with complete stock. My bootloader was unlocked. I had to boot into recovery, wipe everything (I did it multiple times to be sure) and then in recovery I powered off the device. With N still installed I setup the phone WITHOUT restoring ANYTHING from Google. Upon the initial setup menu I started like it was a brand new phone and I had no Google account. Set that all up later. That ended my bootloop problem.
Unfortunately Wi-Fi password backup was huge for me and now it's gone. Everything else while a hassle was manageable, I'm hoping when the factory image is released I can start over and sign into my account and have that data restored.

318sugarhill said:
I had the same issue upon installing N with complete stock. My bootloader was unlocked. I had to boot into recovery, wipe everything (I did it multiple times to be sure) and then in recovery I powered off the device. With N still installed I setup the phone WITHOUT restoring ANYTHING from Google. Upon the initial setup menu I started like it was a brand new phone and I had no Google account. Set that all up later. That ended my bootloop problem.
Unfortunately Wi-Fi password backup was huge for me and now it's gone. Everything else while a hassle was manageable, I'm hoping when the factory image is released I can start over and sign into my account and have that data restored.
Click to expand...
Click to collapse
what did you use to update to N?

I was on the beta. I never flashed anything else. Like a dummy I had my adb commands backwards (was using adb instead of fastboot). Otherwise I would have reflashed MM.

Some other person had the exact same issue when going from 7.0 to 6.0.1
I will have to get a replacement. :/

same here.... guess this is the first brickable nexus device... the only thing that gets me to boot is if I flash N then flash the MM F vendor image, but it does not detect the sim card and camera don't work.

Mgrev said:
Some other person had the exact same issue when going from 7.0 to 6.0.1
I will have to get a replacement. :/
Click to expand...
Click to collapse
Look in the other post about botched nougat install , some of us got phone working

yeah some but like most people say they got no backup available so it doesnt help @rbouza1

minidude2012 said:
yeah some but like most people say they got no backup available so it doesnt help @rbouza1
Click to expand...
Click to collapse
I have a twrp backup, but it doesn't help at all.

Mgrev said:
I have a twrp backup, but it doesn't help at all.
Click to expand...
Click to collapse
From that thread, my solution.
FragmentsOfLife said:
Okay, this is the method I used to fix my phone. The issue was the phone constantly alternating between the "Your device cannot be checked for corruption" screen and the white Google screen with the lock.
1. Flash a stock image (I used the August stock image MTC20F)
2. Fastboot flash TWRP 3.0.2-0
3. Boot into TWRP
4. Select Wipe -> Advanced Wipe -> Select and repair each partition individually (some won't be able to, and that's fine, just move on to the next one)
5. Restore a full nandroid backup (make sure everything is selected) and reboot
6. You should now be free of the never ending boots, and if your device is bootlooped at this point (stuck at the boot animation), you can just flash stock again.
Click to expand...
Click to collapse

Mgrev said:
So i was going to downgrade from android 7.0 (DigitalHigh6P rom). I flashed the newest 6.0.1 factory images, but no matter what i do, it still bootloops. I have tried sideloading an ota file, wiped everything several times. My bootloader is unlocked (of course).
I never get to the android boot animation.
what do?
Click to expand...
Click to collapse
Please join this thread to help troubleshoot.
Hoping to find the answer for you!

Mgrev said:
So i was going to downgrade from android 7.0 (DigitalHigh6P rom). I flashed the newest 6.0.1 factory images, but no matter what i do, it still bootloops. I have tried sideloading an ota file, wiped everything several times. My bootloader is unlocked (of course).
I never get to the android boot animation.
what do?
Click to expand...
Click to collapse
Ur getting bootloops bcuz u didn't had cleared the dalvik and sys cache. try doing a sys format (along cleaning those ) and then do a fresh flash of android 6.0.1 then it'll definitely work. (Y)
-anidaniel

anidaniel said:
Ur getting bootloops bcuz u didn't had cleared the dalvik and sys cache. try doing a sys format (along cleaning those ) and then do a fresh flash of android 6.0.1 then it'll definitely work. (Y)
-anidaniel
Click to expand...
Click to collapse
I have already done that, and it does not work.
I have already contacted my retailer about getting a replacement.