Related
Hey people.
I'm just looking to findout how many of us have the issue of bootlooping (splash screen) overclock kernel is installed...?
I have seen at least 10 ppl on here - please post so it gets known how many we are.
I have tried formatting SD-card w both HP-formatter and Panasonic SD Formatter - neither helped -
I have Cleared Dalvik, Wiped Cache, Wiped to Factory Settings - and redone it over and over.
Nothing helps. Bootloop. As soon as i reflash Froyo kernel official (0050 on WildPuzzle Rom) everything works perfectly.
I have ruled out that the problem would be in SD-card. I have tried three diff cards of various brands and sizes - and also tried without SD-Card. All resulting in Bootloop when OC is flashed.
ADB won't let me get a logcat - as it don't find a device connected - or - as in the latest v5 OC kernel, says Device is offline.
How many - and who - has this issue - There has gotta be something we can do? POST to show the devs you exist please.
I have the same problem too. I've just installed new roms and also kernels. Nothing happened. My wildfire won't boot-up
I understand your frustration guys, really.
Unfortunately though, it is hard for me to be able to fix it without any logs, and I don't have time to play around with potential causes at the moment.
Hope you guys understand
We so do.
But is there noway to get a log w-o booting past splash?
HCDR.Jacob said:
I understand your frustration guys, really.
Unfortunately though, it is hard for me to be able to fix it without any logs, and I don't have time to play around with potential causes at the moment.
Hope you guys understand
Click to expand...
Click to collapse
Here's a question to everyone who cant boot OC - what color is your phone?
the 2 i gave physically encountered that have the problem are both red...?
I solved my bootloop by simply removing my SD-card and then booting. :O Format didnt work forme neither.
try it out
I have - made no difference. As i said before - there is no way that the issue is with the sd-card... I have tried everything regarding that. Results are the very same with - or without sd-card...
But thanks for trying to help...
danne_jo - adeadrat? any of you two live anywhere near stockholm..? if yes i could meet either of you and you can see the issue 1st hand..? maybe you can dig out a log somehow?
worst case scenario (i am desperate yes) maybe i can mail my phone to you jacob and you send it back in two weeks or so? (can't believe i'm saying this)
Phinxy said:
I solved my bootloop by simply removing my SD-card and then booting. :O Format didnt work forme neither.
try it out
Click to expand...
Click to collapse
fireplayer said:
We so do.
But is there noway to get a log w-o booting past splash?
Click to expand...
Click to collapse
Perhaps you can get the logcat via adb when in recovery?
naserbaser said:
Perhaps you can get the logcat via adb when in recovery?
Click to expand...
Click to collapse
There's a kernel debug message system too, although I'm not sure if it'd work if adb doesn't
fireplayer said:
I have - made no difference. As i said before - there is no way that the issue is with the sd-card... I have tried everything regarding that. Results are the very same with - or without sd-card...
But thanks for trying to help...
danne_jo - adeadrat? any of you two live anywhere near stockholm..? if yes i could meet either of you and you can see the issue 1st hand..? maybe you can dig out a log somehow?
worst case scenario (i am desperate yes) maybe i can mail my phone to you jacob and you send it back in two weeks or so? (can't believe i'm saying this)
Click to expand...
Click to collapse
I don't want you to mail me your phone. I'll help out where I can, but if you send your phone to me and it gets lost in the post or I accidentally kill it, I'll feel really bad so I'd rather you didn't :/
hehe, no im not living close to stockholm, and sorry I can help out either
I had the bootlooping too, but that was untill i used the Remove HTC apps puzzle piece, maybe it's sense / rosie thats causing the issue, i'll try my best to look into it.
Been stupidly busy as of late, haven't had time to even work on my own rom lol, peace yall
So how would I get to that..? Everything is worth a try..
HCDR.Jacob said:
There's a kernel debug message system too, although I'm not sure if it'd work if adb doesn't
Click to expand...
Click to collapse
Sent from my HTC Wildfire using XDA App
understandable lol. just trying to make something happen ;p it's frustrating...
HCDR.Jacob said:
I don't want you to mail me your phone. I'll help out where I can, but if you send your phone to me and it gets lost in the post or I accidentally kill it, I'll feel really bad so I'd rather you didn't :/
Click to expand...
Click to collapse
tried that - didn't help, tried openfire rom too - same result.
Elbie said:
I had the bootlooping too, but that was untill i used the Remove HTC apps puzzle piece, maybe it's sense / rosie thats causing the issue, i'll try my best to look into it.
Been stupidly busy as of late, haven't had time to even work on my own rom lol, peace yall
Click to expand...
Click to collapse
fireplayer said:
tried that - didn't help, tried openfire rom too - same result.
Click to expand...
Click to collapse
Curious but which version of the touch screen do you have?
You can find out by pressing the Vol Down button and Power button at the sam time when turning on the wildfire.
A Load of txt will come up, Will tell you if you have the Atmel or not.
Could be that as I know the PSFreedom guys are having issues with the other type of touch panel.
Elbie said:
Curious but which version of the touch screen do you have?
You can find out by pressing the Vol Down button and Power button at the sam time when turning on the wildfire.
A Load of txt will come up, Will tell you if you have the Atmel or not.
Could be that as I know the PSFreedom guys are having issues with the other type of touch panel.
Click to expand...
Click to collapse
I have the same problem.
My touch panel is ATMELC03_16ac.
I too have the atmel, and I have no issues, although I have gone back to the non OC kernel as it seams more stable. I had a few force closes on a few apps...allllll the time, double twist mainly lol.
Ummm confusing one this..
Hi all the guru,
Please..Need help.. My wildfire have problem that is always bootlooping also..
I just updated from puzzlerom 8.07 to 8.10.. successfull then I do partition sdcard ext.. the WF rebooting it seft... until now..
Just flash rom again, but this theme is about OC problems...
Afternoon all!
I would REALLY like to completely wipe my phone and SD and start all over from scratch. I'm rooted, and I've tried WAY too many codes/flashes/apps that I'm sure embedded code in my system that causes some of the errors I get now. I've been told that if I wipe the SD, it'll properly reset, but I've also read of problems after wipe. I'm wondering if anyone knows of a fool proof way to start all the way over for a brand new phone feel. I'll un/re-root if necessary.
Any ideas?
Thanks in advance!
IP IHI II IL
I remember last time having this idea on a random day feeling that my phone was too much, I decided to go to my sd card on my phone from my PC and deleted every folder there WHICH IS NOT GOOD AT ALL, so I'd suggest you wait for someone who knows or can tell you how to properly start over fresh on your new phone.
impatient, but not stoopid!
yeah, I was thinking of goin' rogue and just randomly deleting crap, but my better side made me hold off... I DID get impatient, though and try a suggestion from the Virus forums. I ran the format SD from the phone, then replaced all my ROM zips, and rebooted to recovery first wiping everything 2-3 times, then re flashing Virus ROM 4.X, and my favorite functions/kernel/radios/font... So far so good, though I still would REALLY like to start all the way from scratch. There were some settings embedded into the phone it seems, as I still have my custom splash, even before flashing again... For now, I guess I'm ok with a semi-clean slate, but would still like to know whether or not I can completely start from scratch...
Thanks for the reply, alekosy!
IP IHI II IL said:
yeah, I was thinking of goin' rogue and just randomly deleting crap, but my better side made me hold off... I DID get impatient, though and try a suggestion from the Virus forums. I ran the format SD from the phone, then replaced all my ROM zips, and rebooted to recovery first wiping everything 2-3 times, then re flashing Virus ROM 4.X, and my favorite functions/kernel/radios/font... So far so good, though I still would REALLY like to start all the way from scratch. There were some settings embedded into the phone it seems, as I still have my custom splash, even before flashing again... For now, I guess I'm ok with a semi-clean slate, but would still like to know whether or not I can completely start from scratch...
Thanks for the reply, alekosy!
Click to expand...
Click to collapse
Maybe this'll help, I tested myself and it works fine.
http://forum.xda-developers.com/showthread.php?t=855424
alekosy said:
Maybe this'll help, I tested myself and it works fine.
http://forum.xda-developers.com/showthread.php?t=855424
Click to expand...
Click to collapse
GET OUTTA' MY HEAD!
I used that as well, and yeah, it works great! Thanks!
IP IHI II IL said:
GET OUTTA' MY HEAD!
I used that as well, and yeah, it works great! Thanks!
Click to expand...
Click to collapse
Glad I helped you there, It's really useful for me too xD
Hi guys.
i'm new here and greatly appreciate the knowledge here. I recently installed purenexus on my 6p. first time installing a custom rom. worked beautifully until i decided to try out the lockscreen scramble pin feature. Now when I try to unlock my phone it doesn't recognize my PIN. i've tried many times and something undoubtedly went wrong. is this a known issue with scrambling your pin?
So what should i do? A quick google search suggested I restore a backup. Is this the recommended method? I did a factory back up, i think. i did the back up after the factory reset but before flashing purenexus. i used the default twrp back up settings, which i believe did not include the vendor file.
i'm a complete novice when it comes to this sort of thing so if someone can give me a step-by-step explanation for me to unscrew myself here i'd greatly appreciate it.
thanks.
ent3rpryze said:
Hi guys.
i'm new here and greatly appreciate the knowledge here. I recently installed purenexus on my 6p. first time installing a custom rom. worked beautifully until i decided to try out the lockscreen scramble pin feature. Now when I try to unlock my phone it doesn't recognize my PIN. i've tried many times and something undoubtedly went wrong. is this a known issue with scrambling your pin?
So what should i do? A quick google search suggested I restore a backup. Is this the recommended method? I did a factory back up, i think. i did the back up after the factory reset but before flashing purenexus. i used the default twrp back up settings, which i believe did not include the vendor file.
i'm a complete novice when it comes to this sort of thing so if someone can give me a step-by-step explanation for me to unscrew myself here i'd greatly appreciate it.
thanks.
Click to expand...
Click to collapse
Are you sure you're hitting the right numbers? They'll be in a different position every time.
Heisenberg said:
Are you sure you're hitting the right numbers? They'll be in a different position every time.
Click to expand...
Click to collapse
I am. 100% certain.
it really seems as if my password was for some reason changed. before someone asks i am definitely using the correct pin. its the same PIN i've been using for years.
how do i regain control of my phone?
ent3rpryze said:
I am. 100% certain.
it really seems as if my password was for some reason changed. before someone asks i am definitely using the correct pin. its the same PIN i've been using for years.
how do i regain control of my phone?
Click to expand...
Click to collapse
i rebooted to recovery mode and i discovered that i moved my backup to my laptop. so now backup file is available.
can i just wipe my phone and reinstall the purenexus rom which is still on my phone
ent3rpryze said:
i rebooted to recovery mode and i discovered that i moved my backup to my laptop. so now backup file is available.
can i just wipe my phone and reinstall the purenexus rom which is still on my phone
Click to expand...
Click to collapse
Yes, if you clean flash the ROM you'll be able to get back into it. Had you restored a nandroid backup recently by any chance?
Heisenberg said:
Yes, if you clean flash the ROM you'll be able to get back into it. Had you restored a nandroid backup recently by any chance?
Click to expand...
Click to collapse
thanks a lot for clarifying that. i guess i have no other option.
has this been known to happen? scrambling PIN causing the pin to change.
I dont have a recent nandroid backup because my purenexus flash is only days old. is there a way to automate nandroid backups? is it wiser to keep the backups on the phone?
ent3rpryze said:
thanks a lot for clarifying that. i guess i have no other option.
has this been known to happen? scrambling PIN causing the pin to change.
I dont have a recent nandroid backup because my purenexus flash is only days old. is there a way to automate nandroid backups? is it wiser to keep the backups on the phone?
Click to expand...
Click to collapse
I've never seen this happen before. I'm pretty sure you can use Tasker to automate backups. I usually advise people to keep at least one backup or ROM zip on their phone, just in case.
IT HAPPENED AGAIN!
Per the ever hepful Heisenberg's recommendation, I wiped my phone and reflashed purenexus. This was yesterday. Everything went smoothly. Recreated my security PIN. Was able to unlock my phone with it without incident...until just now. Incorrect PIN error 3 times.
What is going on?!?!
It should be noted that both times this has happened has come after I turned my phone off. This time I happened to be charging my phone while it was off. I can't recall if it was the same case the first time it happened. Is this a purenexus issue?
found the solution.
"Delete this file /data/system/locksettings.db from TWRP."
I wish I had known this the first time it happened. Oh well. I sure hope this helps someone else in the future.
ent3rpryze said:
found the solution.
"Delete this file /data/system/locksettings.db from TWRP."
I wish I had known this the first time it happened. Oh well. I sure hope this helps someone else in the future.
Click to expand...
Click to collapse
This is usually over necessary after a user has created (and later restored) a nandroid backup without removing lockscreen security first. Are you saying you hadn't done this at all prior to the problem occurring?
Heisenberg said:
This is usually over necessary after a user has created (and later restored) a nandroid backup without removing lockscreen security first. Are you saying you hadn't done this at all prior to the problem occurring?
Click to expand...
Click to collapse
i dont know what qualifies as a nandroid backup. the only backup i created was with the TWRP backup function which i later moved to my laptop, as previously mentioned. and yes, i did that before the problem occured. it was before I had even installed pure nexus.
btw, it happened AGAIN (#3 for those keeping score). i'm going to assume there's a bug in the rom and forego the use of a security pin. also, for the first time, when i went back into twrp to once again delete the locksettings.db file i was prompted to enter a password before i could modify the system. Odd.
ent3rpryze said:
i dont know what qualifies as a nandroid backup. the only backup i created was with the TWRP backup function which i later moved to my laptop, as previously mentioned. and yes, i did that before the problem occured. it was before I had even installed pure nexus.
btw, it happened AGAIN (#3 for those keeping score). i'm going to assume there's a bug in the rom and forego the use of a security pin. also, for the first time, when i went back into twrp to once again delete the locksettings.db file i was prompted to enter a password before i could modify the system. Odd.
Click to expand...
Click to collapse
When making a nandroid (backup) in TWRP remove any pin, patter or fingerprints before backup or getting locked out will continue.
elevatorguy said:
When making a nandroid (backup) in TWRP remove any pin, patter or fingerprints before backup or getting locked out will continue.
Click to expand...
Click to collapse
thanks for that, but i believe i did that because i backuped a clean factory 6.0.1, sans any security setup. not sure if that was necessary but that's what i did.
ent3rpryze said:
i dont know what qualifies as a nandroid backup. the only backup i created was with the TWRP backup function which i later moved to my laptop, as previously mentioned. and yes, i did that before the problem occured. it was before I had even installed pure nexus.
btw, it happened AGAIN (#3 for those keeping score). i'm going to assume there's a bug in the rom and forego the use of a security pin. also, for the first time, when i went back into twrp to once again delete the locksettings.db file i was prompted to enter a password before i could modify the system. Odd.
Click to expand...
Click to collapse
The problem isn't with the ROM, I (along with what I'm guessing is pretty much every other user) use fingerprint and/or PIN/pattern security on Pure Nexus with no issues. A nandroid backup is one of those backups you create with TWRP, so yes it's what you described. But this problem shouldn't be occurring on a clean flash of Pure Nexus, can you please explain in detailed steps how you installed the ROM?
ent3rpryze said:
Hi guys.
i'm new here and greatly appreciate the knowledge here. I recently installed purenexus on my 6p. first time installing a custom rom. worked beautifully until i decided to try out the lockscreen scramble pin feature. Now when I try to unlock my phone it doesn't recognize my PIN. i've tried many times and something undoubtedly went wrong. is this a known issue with scrambling your pin?
So what should i do? A quick google search suggested I restore a backup. Is this the recommended method? I did a factory back up, i think. i did the back up after the factory reset but before flashing purenexus. i used the default twrp back up settings, which i believe did not include the vendor file.
i'm a complete novice when it comes to this sort of thing so if someone can give me a step-by-step explanation for me to unscrew myself here i'd greatly appreciate it.
thanks.
Click to expand...
Click to collapse
On Marshmallow, the scramble pin option is bugged if you use a long pin. Some rom devs choose to leave this out entirely. I haven't played with it to determine the cut off point but 4 digits is fine. I think I tried 8 digits once and it locked me out.
Sent from my Nexus 5X using Tapatalk
ent3rpryze said:
found the solution.
"Delete this file /data/system/locksettings.db from TWRP."
I wish I had known this the first time it happened. Oh well. I sure hope this helps someone else in the future.
Click to expand...
Click to collapse
Awesome.. Thanks a bunch for posting this... I am using Oneplus 3T , Resurrection Remix 5.7.4 ( Marshmallow) . Had turned on Scrambled PIN.. Ran into same issue as yours.. Last option left for me was to do factory reset from TWRP but I was scared to lose Google Authenticator Setup on my phone and many other things... Your solution saved me!! :good::good:
I also had a similar problem:
- freshly installed Carbon ROM with TWRP
- added lockscreen password in phone
- locked screen
- tried accessing using password
The password just fails. Using a shorter password works normally. The failing password is 13 characters long.
As the title says, my phone just isn't unlocking, no matter what.
I know for a fact I'm using the right password, it's successfully decrypting my phone. Entering the same password or any password I've used doesn't unlock the right screen, though.
I tried flashing a backup from a couple days ago, but it's having the same problem too.
Any advice?
Did you remove all security from your devices before making a backup?
I've seen several posts that tell people to do so before backing up. So I think that's where the issue is.
Yreisolgakig said:
As the title says, my phone just isn't unlocking, no matter what.
I know for a fact I'm using the right password, it's successfully decrypting my phone. Entering the same password or any password I've used doesn't unlock the right screen, though.
I tried flashing a backup from a couple days ago, but it's having the same problem too.
Any advice?
Click to expand...
Click to collapse
That's the known issue with TWRP and has been fixed with v3.0.2-0. Try that one.
DJBhardwaj said:
That's the known issue with TWRP and has been fixed with v3.0.2-0. Try that one.
Click to expand...
Click to collapse
It's affecting the OS?
Yreisolgakig said:
As the title says, my phone just isn't unlocking, no matter what.
I know for a fact I'm using the right password, it's successfully decrypting my phone. Entering the same password or any password I've used doesn't unlock the right screen, though.
I tried flashing a backup from a couple days ago, but it's having the same problem too.
Any advice?
Click to expand...
Click to collapse
Did this start occurring after restoring a backup? And before making the backup did you forget to remove all security?
DJBhardwaj said:
That's the known issue with TWRP and has been fixed with v3.0.2-0. Try that one.
Click to expand...
Click to collapse
He's talking about the OS, not TWRP.
Heisenberg said:
Did this start occurring after restoring a backup? And before making the backup did you forget to remove all security?
He's talking about the OS, not TWRP.
Click to expand...
Click to collapse
Nandroid backup issue with security is solved, isn't it @Heisenberg ?
Please correct me if I am wrong.
DJBhardwaj said:
Nandroid backup issue with security is solved, isn't it @Heisenberg ?
Please correct me if I am wrong.
Click to expand...
Click to collapse
Not that I'm aware of, I could be wrong though.
Heisenberg said:
Not that I'm aware of, I could be wrong though.
Click to expand...
Click to collapse
I hope it is. In the meantime, I just backed up PN ROM with fingerprint and PIN, and restored it successfully. :victory:
DJBhardwaj said:
I hope it is. In the meantime, I just backed up PN ROM with fingerprint and PIN, and restored it successfully. :victory:
Click to expand...
Click to collapse
Interesting. I'll have to give it a try myself at some point when I get the time.
Heisenberg said:
Interesting. I'll have to give it a try myself at some point when I get the time.
Click to expand...
Click to collapse
Sure. If you confirm, we will know that the issue has been resolved with the latest update. :highfive:
2 days ago, I made a backup of the Pure Rom I had so I could try another asop rom. Today I decided I wanted to go back to pure and when I did the restore, all went well, except when I had to enter a pin right after it booted. It would not recognize my pin that I know 100% was correct.
Any advice on that?
joey3002 said:
2 days ago, I made a backup of the Pure Rom I had so I could try another asop rom. Today I decided I wanted to go back to pure and when I did the restore, all went well, except when I had to enter a pin right after it booted. It would not recognize my pin that I know 100% was correct.
Any advice on that?
Click to expand...
Click to collapse
Which TWRP recovery version did you use?
joey3002 said:
2 days ago, I made a backup of the Pure Rom I had so I could try another asop rom. Today I decided I wanted to go back to pure and when I did the restore, all went well, except when I had to enter a pin right after it booted. It would not recognize my pin that I know 100% was correct.
Any advice on that?
Click to expand...
Click to collapse
If the backup you restored had a security pin still active then it won't restore properly or you won't be able to deactivate the pin code when asked for a screen pincode. At least that's how it has been in the past. They may of fixed it by now but that's only in the latest version.
This happened to me the other day when updating to the new PureNexus. There's a file in MM you can delete through TWRP so the OS will boot without a passcode, and then you can set a new one. I'm not sure whether I'm allowed to post it here as it seems dodgy but I found it in another XDA forum.
joey3002 said:
2 days ago, I made a backup of the Pure Rom I had so I could try another asop rom. Today I decided I wanted to go back to pure and when I did the restore, all went well, except when I had to enter a pin right after it booted. It would not recognize my pin that I know 100% was correct.
Any advice on that?
Click to expand...
Click to collapse
Go into TWRP>Advanced>File Manager>data>system.......delete locksettings.db, locksettings.db-shm, and locksettings.db-wal. Reboot the phone and you'll be able go into the OS just fine after that. You'll have to do this every time unless you make a backup with security removed.
DJBhardwaj said:
Sure. If you confirm, we will know that the issue has been resolved with the latest update. :highfive:
Click to expand...
Click to collapse
I can confirm that the issue has been resolved. Performed a backup and restore of my PN setup today.
Everything on my phone was successfully backed up and restored, including pin and fingerprint.
bouchigo said:
Go into TWRP>Advanced>File Manager>data>system.......delete locksettings.db, locksettings.db-shm, and locksettings.db-wal. Reboot the phone and you'll be able go into the OS just fine after that. You'll have to do this every time unless you make a backup with security removed.
Click to expand...
Click to collapse
This is how I fixed mine a couple days ago. Easy and quick. I also recommend this method. Although all I deleted was the locksettings.db because I couldn't find the others lol either way it worked
Sent from my Nexus 6P using XDA-Developers mobile app
Yreisolgakig said:
As the title says, my phone just isn't unlocking, no matter what.
I know for a fact I'm using the right password, it's successfully decrypting my phone. Entering the same password or any password I've used doesn't unlock the right screen, though.
I tried flashing a backup from a couple days ago, but it's having the same problem too.
Any advice?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3AOKwsYI1C5WWVTeDZSSFhXZ0U/view?pref=2&pli=1
Try flashing this zip it will remove your current lock security. It is working on my phone though. (Don't have nexus 6p yet ) just be sire to make a backup before as i have never tested this for nexus 6P.
Hey there. I was wondering if anyone could help me out. I was running CM 13 on my Nexus 6P for a while but then I kept getting this message that said that there was something wrong internally and that I should contact the manufacturer. I just ignored it. I decided to download the latest nightly and try to freshly install it. I did a full wipe and installed the new CM13 nightly (7-1) and then gapps. When I tried booting the phone up it wouldnt go into the system. I went back into the recovery and tried installing a back up. I did that and tried booting up again into that restored backup and stilled didnt work. So I'm stuck right now with a non working phone. My bootloader is unlocked if that helps any.
XAL2 said:
Hey there. I was wondering if anyone could help me out. I was running CM 13 on my Nexus 6P for a while but then I kept getting this message that said that there was something wrong internally and that I should contact the manufacturer. I just ignored it. I decided to download the latest nightly and try to freshly install it. I did a full wipe and installed the new CM13 nightly (7-1) and then gapps. When I tried booting the phone up it wouldnt go into the system. I went back into the recovery and tried installing a back up. I did that and tried booting up again into that restored backup and stilled didnt work. So I'm stuck right now with a non working phone. My bootloader is unlocked if that helps any.
Click to expand...
Click to collapse
Have you tried flashing a factory IMG?
Sent from my Nexus 6P using XDA-Developers mobile app
XAL2 said:
Hey there. I was wondering if anyone could help me out. I was running CM 13 on my Nexus 6P for a while but then I kept getting this message that said that there was something wrong internally and that I should contact the manufacturer. I just ignored it. I decided to download the latest nightly and try to freshly install it. I did a full wipe and installed the new CM13 nightly (7-1) and then gapps. When I tried booting the phone up it wouldnt go into the system. I went back into the recovery and tried installing a back up. I did that and tried booting up again into that restored backup and stilled didnt work. So I'm stuck right now with a non working phone. My bootloader is unlocked if that helps any.
Click to expand...
Click to collapse
What options did you select when creating and restoring your backup? And, as above, have you tried flashing the factory images?
Heisenberg said:
What options did you select when creating and restoring your backup? And, as above, have you tried flashing the factory images?
Click to expand...
Click to collapse
I actually just did that. All is well. I was having trouble with fastboot commands because my phone wasnt being recognized but i just googled nexus 6p drivers installed them again and ran through the fastboot commands to get my phone back to stock.
XAL2 said:
I actually just did that. All is well. I was having trouble with fastboot commands because my phone wasnt being recognized but i just googled nexus 6p drivers installed them again and ran through the fastboot commands to get my phone back to stock.
Click to expand...
Click to collapse
Cool, glad you got it worked out. With your backup you may have selected the wrong options, have a look in my guide, there's a section dedicated to backups.
Heisenberg said:
Cool, glad you got it worked out. With your backup you may have selected the wrong options, have a look in my guide, there's a section dedicated to backups.
Click to expand...
Click to collapse
I actually have a question about that. When you say check vendor boxes are we supposed to check them both or just the vendor box and not the vendor image box to backup?
XAL2 said:
I actually have a question about that. When you say check vendor boxes are we supposed to check them both or just the vendor box and not the vendor image box to backup?
Click to expand...
Click to collapse
Only the ones that I mention, leave the system image and vendor image boxes alone.
Heisenberg said:
Cool, glad you got it worked out. With your backup you may have selected the wrong options, have a look in my guide, there's a section dedicated to backups.
Click to expand...
Click to collapse
Heisenberg said:
Only the ones that I mention, leave the system image and vendor image boxes alone.
Click to expand...
Click to collapse
Noted for sure. Thank you for your help. Oh hey can you answer one question for me though? When I was running CM13 how come I always got that alert that something internal was messed up and that I should contact my manufacturer? Also how come when I tried to do a clean install it wouldn't boot? Like that confuses me a lot because it was a clean install but I ran into problems.
XAL2 said:
Noted for sure. Thank you for your help. Oh hey can you answer one question for me though? When I was running CM13 how come I always got that alert that something internal was messed up and that I should contact my manufacturer? Also how come when I tried to do a clean install it wouldn't boot? Like that confuses me a lot because it was a clean install but I ran into problems.
Click to expand...
Click to collapse
Perhaps you had the wrong vendor image installed? Other than that I'm not sure. As for why the clean flash didn't boot I'm not sure either, there could be multiple causes for that so it's a bit hard to narrow down.
Heisenberg said:
Perhaps you had the wrong vendor image installed? Other than that I'm not sure. As for why the clean flash didn't boot I'm not sure either, there could be multiple causes for that so it's a bit hard to narrow down.
Click to expand...
Click to collapse
Oh man who knows. Thank you again though for the help and answering to quickly! Also thank you for that guide! Saved my phone's life. Lol
XAL2 said:
Oh man who knows. Thank you again though for the help and answering to quickly! Also thank you for that guide! Saved my phone's life. Lol
Click to expand...
Click to collapse
No probs, happy to help.