Question A bit of problem...... - Google Pixel 7 Pro

I flashed a kernel and broke my system.Now it can only boot to fastboot.The enter reason is BL1 requested.Is there any way to save it?

Hi,
Can you boot into bootloader?
Press power button until phone reboots while keeping volume down pressed.
From there you can install a factory image.
What version are you actually on?
Good luck,
Sébastien.

niftyXD said:
I flashed a kernel and broke my system.Now it can only boot to fastboot.The enter reason is BL1 requested.Is there any way to save it?
Click to expand...
Click to collapse
Flash the stock kernel (partitions) via Fastboot.

most users having issues like this end up getting it up and running using Google's official Android Flash Tool . It takes a lot of guesswork and/or misfires that a lot of users end up hitting the wall at...
I suggest making sure to check "don't wipe" or "keep data" (sorry, I've only used it twice, so going off of memory is foggy) so it doesn't return the device to stock...

niftyXD said:
I flashed a kernel and broke my system.Now it can only boot to fastboot.The enter reason is BL1 requested.Is there any way to save it?
Click to expand...
Click to collapse
did you disable Verity and verification before flashing the kernel?

It's frustrating when someone posts a problem then never follows up

HipKat said:
It's frustrating when someone posts a problem then never follows up
Click to expand...
Click to collapse
It's why I've relegated myself to editing the title "SOLVED" for members on their threads, as a service for those of us who roam around here assisting and helping...
it's not much, but it's sometimes helpful to be able to see in the title and/or be able to tell from a glance if/when someone followed up...

simplepinoi177 said:
It's why I've relegated myself to editing the title "SOLVED" for members, as a service for those of us who roam around here assisting and helping...
it's not much, but it's sometimes helpful to be able to see in the title and/or be able to tell from a glance if/when someone followed up...
Click to expand...
Click to collapse
Hey,
Most likely solved it by himself, since he didn't show up since 5 minutes after his post
Anyways, hopefully, people's experiencing the same issue will find this thread with possible solutions (before opening a new thread).
Cheers,
Sébastien.

Related

Issues with Video on Cory's Unofficial Cyanogen

Sorry my first post is a plea for help, but here we are.
I flashed the latest (2013-5-10) version of ..Cory..'s unofficial Cyanogenmod this morning and I'm having issues with video, including my camera viewfinder. Both Youtube and my camera lag to the point of uselessness, though audio on videos plays just fine.
Also sometimes my desktop icons stick around when I pull up the recent apps or notification drawer.
Has anyone else experienced either one of these? I'd post this in the thread for the ROM, but I need to hit my post count first.
And lest I sound ungrateful, big thanks to ..Cory.. for keeping things moving forward while the official version is on hiatus!
greategress said:
Sorry my first post is a plea for help, but here we are.
I flashed the latest (2013-5-10) version of ..Cory..'s unofficial Cyanogenmod this morning and I'm having issues with video, including my camera viewfinder. Both Youtube and my camera lag to the point of uselessness, though audio on videos plays just fine.
Also sometimes my desktop icons stick around when I pull up the recent apps or notification drawer.
Has anyone else experienced either one of these? I'd post this in the thread for the ROM, but I need to hit my post count first.
And lest I sound ungrateful, big thanks to ..Cory.. for keeping things moving forward while the official version is on hiatus!
Click to expand...
Click to collapse
So I tried disabling HW in dev settings, and that seems to work for now. Still curious if anyone else has run into this issue.
greategress said:
So I tried disabling HW in dev settings, and that seems to work for now. Still curious if anyone else has run into this issue.
Click to expand...
Click to collapse
Not that I could see on my end. But I did do a factory reset in TWRP first before I flashed?
imutau said:
Not that I could see on my end. But I did do a factory reset in TWRP first before I flashed?
Click to expand...
Click to collapse
So did I, unfortunately. Might have to just try it again this weekend and see if that works. :fingers-crossed:
greategress said:
So did I, unfortunately. Might have to just try it again this weekend and see if that works. :fingers-crossed:
Click to expand...
Click to collapse
Check MD5 of your ROM, make sure it matches up if you haven't.
Also, If you haven't done so, try fastboot erase cache prior to wiping and flashing.
exad said:
Check MD5 of your ROM, make sure it matches up if you haven't.
Also, If you haven't done so, try fastboot erase cache prior to wiping and flashing.
Click to expand...
Click to collapse
Thanks for the advice, exad! I'll try to fastboot erase cache step this weekend. Didn't do it this time because I thought I didn't have to use fastboot now that I have S-OFF.
greategress said:
Thanks for the advice, exad! I'll try to fastboot erase cache step this weekend. Didn't do it this time because I thought I didn't have to use fastboot now that I have S-OFF.
Click to expand...
Click to collapse
That command clears the cache for fastboot and recovery, this will ensure that recovery is properly wiping your partitions so be sure to do it before wiping and flashing your rom.
exad said:
That command clears the cache for fastboot and recovery, this will ensure that recovery is properly wiping your partitions so be sure to do it before wiping and flashing your rom.
Click to expand...
Click to collapse
Do you know a decent guide that includes this step? None of the ones I used previously included this step. I get this is an ADB command, but I try to avoid using ADB directly as much as possible due to noobness. Not sure what state my phone has to be in to use the command, etc.
greategress said:
Do you know a decent guide that includes this step? None of the ones I used previously included this step. I get this is an ADB command, but I try to avoid using ADB directly as much as possible due to noobness. Not sure what state my phone has to be in to use the command, etc.
Click to expand...
Click to collapse
There are no guides because it's assumed that you are familiar with ADB and fastboot if you are on this forum.
fastboot and adb don't rely on states.
fastboot is a tool for pushing and pulling information/files to and from your phone while in bootloader
ADB is a tool that allows you to access your phone via a command line shell interface.
If this is confusing to you, why would you root your phone? And I'm not trying to be rude, this isn't an iphone jailbreak, rooting is COMPLETELY different and can be dangerous if you don't understand. Avoiding adb and fastboot does not make it any less dangerous either.
exad said:
There are no guides because it's assumed that you are familiar with ADB and fastboot if you are on this forum.
fastboot and adb don't rely on states.
fastboot is a tool for pushing and pulling information/files to and from your phone while in bootloader
ADB is a tool that allows you to access your phone via a command line shell interface.
If this is confusing to you, why would you root your phone? And I'm not trying to be rude, this isn't an iphone jailbreak, rooting is COMPLETELY different and can be dangerous if you don't understand. Avoiding adb and fastboot does not make it any less dangerous either.
Click to expand...
Click to collapse
I considered not asking for advice, but then I thought "Naw, he's already here. I'm sure he won't mind." My apologies for forcing you to deal with my inexperience.
I used the word "state" incorrectly, not remembering at the time it had a specific programming meaning. You still managed to answer my question, though, pointing out my phone needs to be in the bootloader. You also cleared up that fastboot is its own tool rather than just a command used in ADB. Thank you for both those things. I'll figure it out from here.
As for why I'd want to root my phone? Who wouldn't? I don't want to be stuck with whatever AT&T thinks is good enough. I'm sorry if I'm making this club less exclusive, but if people here are going to hack together all this great stuff and give it away for free, I'm going to take advantage of that.
greategress said:
I considered not asking for advice, but then I thought "Naw, he's already here. I'm sure he won't mind." My apologies for forcing you to deal with my inexperience.
I used the word "state" incorrectly, not remembering at the time it had a specific programming meaning. You still managed to answer my question, though, pointing out my phone needs to be in the bootloader. You also cleared up that fastboot is its own tool rather than just a command used in ADB. Thank you for both those things. I'll figure it out from here.
As for why I'd want to root my phone? Who wouldn't? I don't want to be stuck with whatever AT&T thinks is good enough. I'm sorry if I'm making this club less exclusive, but if people here are going to hack together all this great stuff and give it away for free, I'm going to take advantage of that.
Click to expand...
Click to collapse
You're misunderstanding, the exclusivity of this site makes no difference to me, I want everyone to be able to root and do cool things with their phones, hell, it's your phone, you bought it, own it, you should be able to do whatever you want with it. You didn't need me to tell you what fasboot and adb are. They're well documented tools with help manuals included. Even a quick google search would tell you everything you need to know about them and more.
You chose to ignore them and hope it won't affect you that you're not understanding what you're doing to your phone. You ask in here hoping for the quick and lazy way to accomplish your task without taking the time to learn what you're doing. I love helping people that's why I'm here posting every day. but you're taking advantage of my good nature and not trying to help yourself by reading, learning and understanding what you're doing.
I wish you luck and I don't want to discourage you for asking for help here when you need it, but please take the time to help yourself first.
Same issue
I have the same issue with Youtube in landscape mode. I've noticed others have run into it as well.
exad said:
You're misunderstanding, the exclusivity of this site makes no difference to me, I want everyone to be able to root and do cool things with their phones, hell, it's your phone, you bought it, own it, you should be able to do whatever you want with it. You didn't need me to tell you what fasboot and adb are. They're well documented tools with help manuals included. Even a quick google search would tell you everything you need to know about them and more.
You chose to ignore them and hope it won't affect you that you're not understanding what you're doing to your phone. You ask in here hoping for the quick and lazy way to accomplish your task without taking the time to learn what you're doing. I love helping people that's why I'm here posting every day. but you're taking advantage of my good nature and not trying to help yourself by reading, learning and understanding what you're doing.
I wish you luck and I don't want to discourage you for asking for help here when you need it, but please take the time to help yourself first.
Click to expand...
Click to collapse
*sigh* You're right. I'm sorry for getting snappy. Just not used to being the guy who doesn't know what he's doing, y'know?
Anyway, I sincerely appreciate the help, exad. And I doubly appreciate the reminder that I need to turn to Google before I come begging to you guys.
nlyang said:
I have the same issue with Youtube in landscape mode. I've noticed others have run into it as well.
Click to expand...
Click to collapse
Hmm. Heard anything about how to fix it?
greategress said:
Hmm. Heard anything about how to fix it?
Click to expand...
Click to collapse
Have you tried flashing a different kernel? Like jacob.b2 or oc-vm-linaro?
exad said:
Have you tried flashing a different kernel? Like jacob.b2 or oc-vm-linaro?
Click to expand...
Click to collapse
I actually just got done following your original advice about clearing the cache via fastboot. Did that, then re-flashed the ROM and everything seems to be working. Thanks again for the help (and tough love )!
greategress said:
I actually just got done following your original advice about clearing the cache via fastboot. Did that, then re-flashed the ROM and everything seems to be working. Thanks again for the help (and tough love )!
Click to expand...
Click to collapse
Anytime friend!
the only thing that worked for me...
greategress said:
Hmm. Heard anything about how to fix it?
Click to expand...
Click to collapse
i tried erasing the cache via fastboot before the wipe+flash, but unfortunately I still had the issue. the only temp fix that works for me so far is disabling HW overlays in the developer options.
You could also try another kernel.
Sent from my One X using xda app-developers app
exad said:
You could also try another kernel.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Any kernel you'd recommend over the others? You mentioned the jacob.b2 and oc-vm-linaro before. Like one more than the other?

Please Help~ rooted inspire 4g with Jellytime R7, after boot-blackscreen

Hey guys,I have a rooted inspire 4g with Jellytime R7 and I turned it on and after the bootanimation It goes into blackness and does nothing....This has happened before but I would simply just factory reset it and all would be good until now...My volume down is broken and I can't get into recovery please help.It would mean a ton
Please help guys!
LogicDeifying said:
Please help guys!
Click to expand...
Click to collapse
A couple things,
1~ The title of your thread is simply to vague. Try re-naming it to something other then I need help.
2~ It is Sunday, you will probably have a better chance of receiving help tomorrow. Please do not bump your own thread you need to have some patients.
Thank you
TonyStark said:
A couple things,
1~ The title of your thread is simply to vague. Try re-naming it to something other then I need help.
2~ It is Sunday, you will probably have a better chance of receiving help tomorrow. Please do not bump your own thread you need to have some patients.
Thank you
Click to expand...
Click to collapse
Ok thank you Stark,Do you have any advise?
LogicDeifying said:
Ok thank you Stark,Do you have any advise?
Click to expand...
Click to collapse
It sounds like you may be having more going on then the rom. From the little you have said, it sounds like your hardware my now be causing additional issues. Have you checked YT for "How to's" for the device?
TonyStark said:
It sounds like you may have more going on then the rom. It sounds like your hardware my now be causing additional issues. Have you checked YT for "How to's" for the device?
Click to expand...
Click to collapse
I have I tried doing this one that un-roots the device with Ace Hack...And It requires Usb Debugging but it's not on...
Frankly I don't see how you are going to get out of this one unless you go in there and find a way to press the vol down button, either by sticking a pin in your phone in that area or opening it up to get it pressed.
You cannot get into Fastboot or Recovery unless you do so.
You did not enable USB debugging so you can't input ADB commands during the boot-loop.
Is there an emergency reset button on this phone? (the HD2 had a small one in the back that could be used to hard reset the phone i believe).
Mine showed similar until I flashed the kernel.
Is it unlocked? S-On? S-off? Have you run a RUU to return to stock get debugging back? Have you tried flashing anything from fastboot? And...have you changed your incredibly undescriptive title?

How to update to 4.4.1?

So basically I have my nexus 5 and it’s completely stocked. I don’t want to root or do anything that could prevent me from receiving OTA updates?
What are the steps to update my phone rom stock 4.4 to 4.4.1.
Thanks
I found this video very helpful.
http://www.youtube.com/watch?v=rfZ4f5Bdgfc&list=FLJJ5N1JCwlum5OdXVTemjHw&index=2
richport29 said:
I found this video very helpful.
http://www.youtube.com/watch?v=rfZ4f5Bdgfc&list=FLJJ5N1JCwlum5OdXVTemjHw&index=2
Click to expand...
Click to collapse
I have a nexus 5.
rayoubi said:
I have a nexus 5.
Click to expand...
Click to collapse
Exact same process.
---------- Post added at 06:05 PM ---------- Previous post was at 06:04 PM ----------
Obviously use the Nexus 5 4.1.1 ota
Be patient and receive the update directly from Google as an OTA within a week, or so. There might need to be a revision to this update, due to issues with the new radio seeming to not get good signal strength and so forth, which is why Goofle sends it out incrementally.
Sent from my Nexus 5 using Tapatalk
F n a I've never seen so many dopes in a row
http://forum.xda-developers.com/showthread.php?p=47369234
jd1639 said:
F n a I've never seen so many dopes in a row
http://forum.xda-developers.com/showthread.php?p=47369234
Click to expand...
Click to collapse
People need to search first, but that guide doesn't work for everyone.
My phone wouldn't reboot into actual recovery...it came up saying "No error" or some nonsense and wouldn't get into recovery. It makes the guide useless.
hotleadsingerguy said:
People need to search first, but that guide doesn't work for everyone.
My phone wouldn't reboot into actual recovery...it came up saying "No error" or some nonsense and wouldn't get into recovery. It makes the guide useless.
Click to expand...
Click to collapse
The guide is not useless. If you can't boot into recovery you're doing something wrong or your recovery is borked. If its borked you can fix it.
jd1639 said:
The guide is not useless. If you can't boot into recovery you're doing something wrong or your recovery is borked. If its borked you can fix it.
Click to expand...
Click to collapse
Oh, I didn't realize the guide explained how to fix it if something happened to your recovery. If so, I redact my statement.
(Obviously that's sarcasm and I don't redact my statement, since it doesn't do that)
My phone is completely bone-stock. I haven't rooted or unlocked. It doesn't boot into recovery using the method listed in the guide, and booting into the system menu and selecting Recovery just boots the phone normally for me.
hotleadsingerguy said:
Oh, I didn't realize the guide explained how to fix it if something happened to your recovery. If so, I redact my statement.
(Obviously that's sarcasm and I don't redact my statement, since it doesn't do that)
My phone is completely bone-stock. I haven't rooted or unlocked. It doesn't boot into recovery using the method listed in the guide, and booting into the system menu and selecting Recovery just boots the phone normally for me.
Click to expand...
Click to collapse
Then your recovery is broken. Look at the how to flash factory images sticky in General and fastboot flash a fixed recovery.
Nothing to do with the fact that this is another OTA thread when there is an OTA sticky. The guide is not useless, your phone is.
rootSU said:
Then your recovery is broken. Look at the how to flash factory images sticky in General and fastboot flash a fixed recovery.
Nothing to do with the fact that this is another OTA thread when there is an OTA sticky. The guide is not useless, your phone is.
Click to expand...
Click to collapse
And, as I mentioned, I haven't modified a thing on the phone. If my recovery is broken, it was broken from the factory.
And, again, the guide had nothing to do with that. If anyone else has the issue (which people are having, according to a few other topics I've seen), the guide makes no account for it -- for anyone with the issue, the guide is of no help.
hotleadsingerguy said:
And, as I mentioned, I haven't modified a thing on the phone. If my recovery is broken, it was broken from the factory.
Click to expand...
Click to collapse
I never said it was anything to do with what you had done or when it had broken.
hotleadsingerguy said:
And, again, the guide had nothing to do with that. If anyone else has the issue (which people are having, according to a few other topics I've seen), the guide makes no account for it -- for anyone with the issue, the guide is of no help.
Click to expand...
Click to collapse
And why would it? It also doesn't help people with a smashed screen or broken volume buttons. The guide is a guide to do what needs to be done on a fully working phone. It does NOT need to cover every fault that someone might have that prevents them doing the things in the guide. The fact your phone is broken bears no relevance to the usefulness of the guide. Besides, I already advised you what you could try to fix it.
Anyway, this thread is a duplicate and I have requested it be closed.
hotleadsingerguy said:
Oh, I didn't realize the guide explained how to fix it if something happened to your recovery. If so, I redact my statement.
(Obviously that's sarcasm and I don't redact my statement, since it doesn't do that)
My phone is completely bone-stock. I haven't rooted or unlocked. It doesn't boot into recovery using the method listed in the guide, and booting into the system menu and selecting Recovery just boots the phone normally for me.
Click to expand...
Click to collapse
hi
i am a noob. my phone is also compleely stock. not rooted and locked. i just activated with my carrier and downloaded speedtest. thats it. i have android sdk and platform tools and universal naked driver with adb support installed on my pc.
Code:
adb boot recovery
takes me to recovery. and i side loaded from there. :good:

[Q] TWRP and encrypted storage

I just updated to Lollipop. I tried to run TWRP without flashing (use fastboot boot command) and it run smoothly. However, after I encrypted my phone TWRP cannot decrypt the storage like it could in Kitkat even though I enabled encryption in Kikkat too
nerodarknight said:
TWRP cannot decrypt the storage like it could in Kitkat
Click to expand...
Click to collapse
Correct.
rootSU said:
Correct.
Click to expand...
Click to collapse
So no worry then, I thought it's only my phone lol. Do you happen to know if TWRP or CWM will make it compatible with Lollipop encryption?
nerodarknight said:
So no worry then, I thought it's only my phone lol. Do you happen to know if TWRP or CWM will make it compatible with Lollipop encryption?
Click to expand...
Click to collapse
Forget CWM, it doesn't even support encryption for KK.
Anybody know how long it has taken the devs of TWRP to update to the new encryption for previous versions? Just curious about when this will work again.
Thanks for any info,
Fly
FlyOnTheWall43 said:
Anybody know how long it has taken the devs of TWRP to update to the new encryption for previous versions? Just curious about when this will work again.
Thanks for any info,
Fly
Click to expand...
Click to collapse
It will come when it comes.
Lethargy said:
Forget CWM, it doesn't even support encryption for KK.
Click to expand...
Click to collapse
Forget encryption, It doesn't even support /sdcard for JB!
Lethargy said:
It will come when it comes.
Click to expand...
Click to collapse
Is it just me or are these responses the least productive thing on the internet?
I would understand if I came in here demanding an exact ETA, but I feel like I respectfully asked for estimated past turn around times so that I could have a basic idea (2 weeks/2 months/2 years) of when I'll be able to use TWRP on my phone again.
And I understand that the devs are probably working very hard on getting this done (I see that there is version 2.8.2 for the Nexus 9 that allows decryption on Lollipop, so maybe they're really close), and although I am an entry level programmer, this kind of stuff goes way over my head, I do really appreciate the work that they do.
I am fairly new to the wonderful world of this level of Android customization and I'm just trying to learn how the process works.
Does anybody else have any useful info?
FlyOnTheWall43 said:
Is it just me or are these responses the least productive thing on the internet?
I would understand if I came in here demanding an exact ETA, but I feel like I respectfully asked for estimated past turn around times so that I could have a basic idea (2 weeks/2 months/2 years) of when I'll be able to use TWRP on my phone again.
And I understand that the devs are probably working very hard on getting this done (I see that there is version 2.8.2 for the Nexus 9 that allows decryption on Lollipop, so maybe they're really close), and although I am an entry level programmer, this kind of stuff goes way over my head, I do really appreciate the work that they do.
I am fairly new to the wonderful world of this level of Android customization and I'm just trying to learn how the process works.
Does anybody else have any useful info?
Click to expand...
Click to collapse
There isn't anything else to say other than what I did in the post. Check repos and see if there is any progress.
But still.
As mentioned, we don't know anything. We haven't had any feedback. You have access to the same info we do (TWRP dev thread and github). There is no point asking us the answer. You'd be more upset if no one answered at all.
Again, I wasn't asking for when the next version will be released, I understand nobody knows that... I asked for:
FlyOnTheWall43 said:
for estimated past turn around times so that I could have a basic idea (2 weeks/2 months/2 years)
Click to expand...
Click to collapse
Just a rough guess, that's all I'm wondering.
FlyOnTheWall43 said:
Again, I wasn't asking for when the next version will be released, I understand nobody knows that... I asked for:
Just a rough guess, that's all I'm wondering.
Click to expand...
Click to collapse
Without knowing the complexities of encryption and the development involved and the fact that past development turn around has nothing to do with the future, we can give only the same answer.
I'd say you can only ask the dev, but since that's against the rules, you'll just have to wait and find out when everyone else does. You have the same information available as we have, including past turn around dates.
New 2.8.2.0 with Android 5 encryption support is available at the TWRP site and confirmed working on my Nexus 5

Verizon Pixel stuck in bootloop. Please help.

Hey guys. I really messed up. I was running 7.1 from launch, and have had the systemless root basically since the beginning. I attempted to mount /system as /r/rw (for the stupidest reason) and my phone booted into a "no command" bootloop. Is there any hope for me? I can access recovery (I think). I can get into adb and fastboot and get the device recognized by the computer.
I will donate, buy coffee, anything for some love. Thank you so much for your time!
junkshot9112 said:
Hey guys. I really messed up. I was running 7.1 from launch, and have had the systemless root basically since the beginning. I attempted to mount /system as /r/rw (for the stupidest reason) and my phone booted into a "no command" bootloop. Is there any hope for me? I can access recovery (I think). I can get into adb and fastboot and get the device recognized by the computer.
I will donate, buy coffee, anything for some love. Thank you so much for your time!
Click to expand...
Click to collapse
Well if you have an unlocked bootloader you can simple flash the stock images.
NBreunig3 said:
Well if you have an unlocked bootloader you can simple flash the stock images.
Click to expand...
Click to collapse
Thank you so much for the reply. I think I could even do a factory reset from recovery, but I'm not sure. I'm pretty new at this. I was really hoping there may be a way I could backup my data first, or even fix the issue, as I'm pretty sure I know what happened. I think my permissions are set wrong, but I could be entirely wrong. I found this guide that sounds like my issue, but it is for a different device. I've tried adapting it to the best of my ability, but I can't get the phone in ADB mode from recovery. http://www.gizbeat.com/2103/how-to-change-file-permissions-through-adb/
Wouldn't hurt to try knowing you can also just flash stock images.
NBreunig3 said:
Wouldn't hurt to try knowing you can also just flash stock images.
Click to expand...
Click to collapse
Can you point me in the direction of someone who may be able to help me do just that? I've tried just about all I can think to do. I really am new at this and feel I am in over my head. I really appreciate any and all help and would gladly donate to this site or any individual user who is able to help me solve my problems (I hope it isn't against your rules to say things like that).
Thanks again.
This site straight from Google has all the files and instructions. https://developers.google.com/android/images
Follow directions but don't lock bootloader.
NBreunig3 said:
This site straight from Google has all the files and instructions. https://developers.google.com/android/images
Follow directions but don't lock bootloader.
Click to expand...
Click to collapse
Sorry, I was unclear, that was my fault. I believe I know how to flash stock images. That is something I have done since the OG Droid. I was asking if you may know anyone who may be able to help me attempt to backup my data, reset my permissions, or even get the phone into ADB mode before I resort to losing everything. Again, apologies for being unclear.
No worries. I would just look online and possibly post another thread here or just wait for replies.
Flash the stock image but remove the -w from the script to keep from losing data. Search around here for instructions. It's been described a zillion times.
cntryby429 said:
Flash the stock image but remove the -w from the script to keep from losing data. Search around here for instructions. It's been described a zillion times.
Click to expand...
Click to collapse
Is this what is referred to as a "dirty flash"?
junkshot9112 said:
Is this what is referred to as a "dirty flash"?
Click to expand...
Click to collapse
I suppose one could think of it that way but it really isn't. Everything other than data will be wiped and flashed. It'll all be new with the exception of your data partition. Removing the w allows you to keep all your apps and their settings in tact. The rest will all be new though. It can't hurt to try it. If it doesn't fix your problem (which it should) you can always run it again and wipe data along with everything else.
robocuff said:
I suppose one could think of it that way but it really isn't. Everything other than data will be wiped and flashed. It'll all be new with the exception of your data partition. Removing the w allows you to keep all your apps and their settings in tact. The rest will all be new though. It can't hurt to try it. If it doesn't fix your problem (which it should) you can always run it again and wipe data along with everything else.
Click to expand...
Click to collapse
I was successful. Thank you so much. What can I do for you to show thanks?
junkshot9112 said:
Is this what is referred to as a "dirty flash"?
Click to expand...
Click to collapse
Yes. But in reality it is not much different than taking an OTA. That never wipes data. I only clean flash if I am having issues after a dirty flash and I can't remember the last time that happened.
Sent from my Pixel XL using XDA Labs
junkshot9112 said:
I was successful. Thank you so much. What can I do for you to show thanks?
Click to expand...
Click to collapse
Your thanks is more than enough.?

Categories

Resources