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
Related
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?
I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki
this seems more like a user made htc dev, not what true s-off "bootloader unlocked" would be. non the less it should work fine. this probably wont touch the write enabled protection on the device. the only issues i see is until we are truly unlocked we will always have that "samsung custom" on out bootscreens.
spyz88 said:
I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki
Click to expand...
Click to collapse
He released his source code and such so we need to have someone compile it into a .bat or .exe so we can flash a custom recovery/rom
its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...
shabbypenguin said:
its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...
Click to expand...
Click to collapse
well i cant use it as i don't use linux lol.
Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with
fix-this! said:
well i cant use it as i don't use linux lol.
Click to expand...
Click to collapse
well if you dont use linux you cant make kernels or recoveries
luckily the loki_flash utility that is used to actually put the patched img onto the device works on android so it doenst matter what kind of computer you have
alacrify said:
Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with
Click to expand...
Click to collapse
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.
just means soon we will have bootloader unlocked.... patience
lorijuan1024 said:
just means soon we will have bootloader unlocked.... patience
Click to expand...
Click to collapse
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.
Bjray said:
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.
Click to expand...
Click to collapse
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Update: nand backup was successful. Good start for us, just need the perm fix, but for now, it rocks, it was so nice to see the recovery screen. SWEET
TheAxman said:
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Click to expand...
Click to collapse
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.
fix-this! said:
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.
Click to expand...
Click to collapse
what i meant was a tool that us people that aren't good with the programming language can use.
fix-this! said:
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.
Click to expand...
Click to collapse
Agreed, but I do have a jtag box here in hand, and there is no fix for that either, I might have one phone down soon..:
Incoming update from Samsung in 3....2....1.....
I flashed what shabbypenguin provided in his recovery thread and now have a working recovery on my ATT i337!!! :laugh::good::highfive::fingers-crossed:
Thanks to djrbliss for his awesome work!
mr_blanket said:
Incoming update from Samsung in 3....2....1.....
Click to expand...
Click to collapse
simple solution is to not take the OTA. but yes, i see one coming to.
fix-this! said:
simple solution is to not take the OTA. but yes, i see one coming to.
Click to expand...
Click to collapse
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.
mattdm said:
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.
Click to expand...
Click to collapse
hopefully adam can get us a more permanent solution. but props to dan for his tool.
Couldn't be happier after I get home from watching the hangover I get to unlock this bad boy
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Android Police Article About Bug - "Bug Caused Devices To Download Stock 4.4.3 Update Repeatedly And Obliterate Data Caps"
How can I fix this issue without flashing a copy of the latest build? I ask only bc im running Beanstalk rom which hasn't been updated in a while and I'd really like to stay on it. Any Ideas?
R.Suave said:
Android Police Article About Bug - "Bug Caused Devices To Download Stock 4.4.3 Update Repeatedly And Obliterate Data Caps"
How can I fix this issue without flashing a copy of the latest build? I ask only bc im running Beanstalk rom which hasn't been updated in a while and I'd really like to stay on it. Any Ideas?
Click to expand...
Click to collapse
you need to read that article again. it doesnt say aosp, it clearly says its a cm bug. and the title is "CyanogenMod 11 M6 Bug Caused Devices To Download Stock 4.4.3 Update Repeatedly And Obliterate Data Caps, Fixed In Newly Released M7 Build".
simms22 said:
you need to read that article again. it doesnt say aosp, it clearly says its a cm bug. and the title is "CyanogenMod 11 M6 Bug Caused Devices To Download Stock 4.4.3 Update Repeatedly And Obliterate Data Caps, Fixed In Newly Released M7 Build".
Click to expand...
Click to collapse
Only reason I left "CM" out is because of this comment. Is this not true?
R.Suave said:
Only reason I left "CM" out is because of this comment. Is this not true?
Click to expand...
Click to collapse
what comment?
simms22 said:
what comment?
Click to expand...
Click to collapse
If you let the page load, it links to a comment stating "It isn't really the fault of cm devs. You'd face the exact same problem even if you compiled aosp and added Google apps to them."
R.Suave said:
If you let the page load, it links to a comment stating "It isn't really the fault of cm devs. You'd face the exact same problem even if you compiled aosp and added Google apps to them."
Click to expand...
Click to collapse
generally, if you have root, and modified anything in your system, youll get an ota but it wont install. at that point, it would redownload itself eventually for an other attempt . itll stop if you update the rom manually. but if you never update, itll keep attempting. but that isnt a bug.
simms22 said:
generally, if you have root, and modified anything in your system, youll get an ota but it wont install. at that point, it would redownload itself eventually for an other attempt . itll stop if you update the rom manually. but if you never update, itll keep attempting. but that isnt a bug.
Click to expand...
Click to collapse
Awesome. Can you help now or are you only interested in nitpicking the wording used?
Is there a way to stop the update from downloading over and over without flashing a new rom?
R.Suave said:
Awesome. Can you help now or are you only interested in nitpicking the wording used?
Is there a way to stop the update from downloading over and over without flashing a new rom?
Click to expand...
Click to collapse
i dont nitpick wording, never ever have, as not all of us use english as a first or second language. anyways, busy i always am, since i spend lots of time here helping people while im busy at work. how exactly to stop it, i dont know for sure as i have never tried(never been an issue for me). what you can try if you have root is install the disable service app from the play store, open it, go to system apps, find google play services, then disable SystemUpdateService. but really, im not sure
simms22 said:
i dont nitpick wording, never ever have, as not all of us use english as a first or second language. anyways, busy i always am, since i spend lots of time here helping people while im busy at work. how exactly to stop it, i dont know for sure as i have never tried(never been an issue for me). what you can try if you have root is install the disable service app from the play store, open it, go to system apps, find google play services, then disable SystemUpdateService. but really, im not sure
Click to expand...
Click to collapse
Thank you.
R.Suave said:
Thank you.
Click to expand...
Click to collapse
let me know if that works. if it does, ill spread the word
Hi, I read that anyone with a developer's account can access the developers' preview build of Android L, that was supposed to be available today, I have a developer's account (to upload apps to the market) but I don't see any build of android L, is this the required account? or is there any other type of account required? thanks!
saman0suke1 said:
Hi, I read that anyone with a developer's account can access the developers' preview build of Android L, that was supposed to be available today, I have a developer's account (to upload apps to the market) but I don't see any build of android L, is this the required account? or is there any other type of account required? thanks!
Click to expand...
Click to collapse
it will be here when its released, as of yet it is not released
http://developer.android.com/index.html
keep refreshing the page like the rest of us
saman0suke1 said:
Hi, I read that anyone with a developer's account can access the developers' preview build of Android L, that was supposed to be available today, I have a developer's account (to upload apps to the market) but I don't see any build of android L, is this the required account? or is there any other type of account required? thanks!
Click to expand...
Click to collapse
I guess it'll be available in a few hours.
I guess they just haven't released it, yet.
Don't forget their different timezone.
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
saman0suke1 said:
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
Click to expand...
Click to collapse
Considering that the images will have to be flashed through fastboot, you'll probably lose root and everything else on data/system partitions (unless they don't wipe it, but I think it does).
saman0suke1 said:
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
Click to expand...
Click to collapse
maybe it will be problem to root new androi L cause I've read somwhere that there is a lot of security updates and also samsung knox in new android so we will see if it will be able to root
saman0suke1 said:
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
Click to expand...
Click to collapse
if it's a factory image it'll wipe the whole phone and root probably wont work until its updated to support L
MidnightDevil said:
Considering that the images will have to be flashed through fastboot, you'll probably lose root and everything else on data/system partitions (unless they don't wipe it, but I think it does).
Click to expand...
Click to collapse
That's fine, I believe that flash through fastboot does not include a total wipe including camera folder and all that right? never done it that way, better be prepared. Thanks!
saman0suke1 said:
That's fine, I believe that flash through fastboot does not include a total wipe including camera folder and all that right? never done it that way, better be prepared. Thanks!
Click to expand...
Click to collapse
As long as you don't flash the userdata.img, all /sdcard data will be fine. You don't have to flash userdata.img to bump android versions! System, boot would do just fine (and bootloader if they bump it as well)
Or you could just wait till a flashable zip is posted. Someone will have one up within hours of release.
Roxas598 said:
if it's a factory image it'll wipe the whole phone and root probably wont work until its updated to support L
Click to expand...
Click to collapse
Whole phone means photos, and any kind of files? I prefer to ask so I make a backup first :S , never done it this way, thanks!
saman0suke1 said:
Whole phone means photos, and any kind of files? I prefer to ask so I make a backup first :S , never done it this way, thanks!
Click to expand...
Click to collapse
Read my previous post.
saman0suke1 said:
Whole phone means photos, and any kind of files? I prefer to ask so I make a backup first :S , never done it this way, thanks!
Click to expand...
Click to collapse
Yep every single thing on the phone will be gone so backup everything you need
saman0suke1 said:
That's fine, I believe that flash through fastboot does not include a total wipe including camera folder and all that right? never done it that way, better be prepared. Thanks!
Click to expand...
Click to collapse
You'll lost everything... Photos,data file...
vin4yak said:
As long as you don't flash the userdata.img, all /sdcard data will be fine. You don't have to flash userdata.img to bump android versions! System, boot would do just fine (and bootloader if they bump it as well)
Click to expand...
Click to collapse
Unless they changed the folder structure like they did a few releases ago - if they did, best to do a clean install.
I'm backing up right now just in case.
Don't wanna mess with the installation script by flashing some things and not others (although there would be virtually no risk by flashing system and boot partition), but better safe than sorry, after all, we can just shove everything back when finished
Consider ir a backup routine, and you'll have an updated bk
jj14 said:
Unless they changed the folder structure like they did a few releases ago - if they did, best to do a clean install.
Click to expand...
Click to collapse
That's an entirely different scenario. Each and everyone of us would need to wipe clean if that happens but usually a system and boot flash would do just fine
The N5 has been my FIRST of many, many, many Android phones and even Windows Pocket PC phones that I haven't felt the need to unlock/root etc. Everything has just worked great on it and I have always been able to do everything I wanted to do from this phone. I have been so satisfied with the phone that it has kept me away from XDA for a while. Don't know if that is a good thing or bad, lol. I used to be on this site for hours every single day and now I feel like I am light years behind in rooting. HA!
L has me interested though and I am contemplating unlocking my bootloader for it which just becomes a PITA with losing your data and adding things back and all that great stuff that takes so much of your time. Then if things suck you have to flash back to something else and the never ending process continues. The N5 has gotten me so much time back in my life but I feel like it might demand some of my time back to it. Oh I hate this stuff!!!!
I think I'll make a backup, just in case, as someone said previously, I would prefer to make a clean installation if it's needed and use the image provided by Google.
Thanks!
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.