Updating rooted Nexus 6 (Marshmallow) + OTA - Nexus 6 Q&A, Help & Troubleshooting

So I have a Nexus 6 stock room rooted (Systemless root). I have been a cm user ever since my Evo supersonic. I am unfamiliar with the correct way to apply the OTA that came out recently.
I have read that all that is needed is to flash system.img from the new archive. Is this true? Keep in mind I want to update without wiping my apps and data. I have been asking myself if I can give up phone-wide adblocking, and I'm going to give it a shot. The reason I've been asking this is because as I understand it, updating will remove twrp. This I don't really understand... Why would flashing system wipe recovery? Aren't they in different partitions?
I have done a lot of searching over a stupidly long period of time and have not found satisfactory answers.
Can I simply :
fastboot flash system system.img
or is there more to it than that?
Could someone please lay it all out for me?
Thanks

And yes I did see this thread: http://forum.xda-developers.com/nexus-6/general/easily-apply-ota-update-to-rooted-nexus-t3204018
And this one as well: http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
There are unanswered questions with both.
On the first link, why the hell would I erase the system partition? Wouldn't that be like doing a factory reset???
On the second one, why the hell would I flash the bootloader? Would it have changed from version to version and why would it matter if it had?
Why do I need anything other than to flash system.img over what is already there and flash the new radio?

So, erasing system before flashing is not really necessary, but it doesn't hurt, and definitely it's not factory reset. Erasing only makes sure that while flashing erases all files before flashing a partition, you want to be extremely sure.
And no, erasing system is not factory reset. Factory reset is erasing the data partition where the application data is stored, even for the system and private system apps. Actually TWRP only deletes the /data/data folder and some Android folders and leaves your other files safe when performing "factory reset".
You might need the boot.img, because it contains the kernel itself, so as these updated are security updates, it's probable they have patched some security hole in the kernel itself.
Finally the radio might have changed, but it usually doesn't. In fact AFAIK it hasn't changed since after the M previews, and the bootloader is the same as in the M previews. But if you don't have the previous factory images to do quick file diffs, it won't hurt to update them anyway.
So you need to flash boot and system, the re-flash SuperSu, and that"s that. If you want to make sure you won't have some system apps FC-ing in TWRP delete cache and dalvik. And if it'S TWRP prior to 3.0 don't let it modify your system partition.
And that's that.

Thank you

Forboding Angel said:
And yes I did see this thread: http://forum.xda-developers.com/nexus-6/general/easily-apply-ota-update-to-rooted-nexus-t3204018
And this one as well: http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
Click to expand...
Click to collapse
Did you also take a look at this one: http://forum.xda-developers.com/nexus-6/help/how-security-update-ota-twrp-t3307409 ? Post #23 in that thread may answer your question as to why TWRP might get replaced with stock recovery.

Ahhhh ok that explains a lot. I think I'm going to try going straight stock with adblock browser and no root and see if I can put up with it.

Related

[Q] Install Android only

Hello All;
I have decided to try and male my HP touch pad an Android only touch pad.
I need help though as i am a novice at best.
I am looking for help on the files i will need. Want to install CM 10 recent and CWM.
Do i need a boot loader or will that be in the ROM?
And what other files will i need?
i am assuming i need a ROM, Recovery, and GAPPS. Other than that i am not sure.
Found someone on the WebOS Nation who is willing to help so i dont want to go into this like and idiot, i want to have my ducks in a row.
Any help will be appreciated
thanks
This is a good guide: http://forum.xda-developers.com/showthread.php?t=2147284. As for Android-only, I don't recommend it. WebOS has gotten me out of Android trouble before.
Install Android only
bananagranola said:
This is a good guide: http://forum.xda-developers.com/showthread.php?t=2147284. As for Android-only, I don't recommend it. WebOS has gotten me out of Android trouble before.
Click to expand...
Click to collapse
Good point, Hey let me ask you something.
I like flashing ROMs but I always end up with a mess. Moboot, i dont think updates as grub2 does. So, i have thought the best way to switch ROMs would be treating the ROM as a first install, does that make sense and do you agree?
Or do you know a method to change ROMs that works well for you?
geomonroe said:
Good point, Hey let me ask you something.
I like flashing ROMs but I always end up with a mess. Moboot, i dont think updates as grub2 does. So, i have thought the best way to switch ROMs would be treating the ROM as a first install, does that make sense and do you agree?
Or do you know a method to change ROMs that works well for you?
Click to expand...
Click to collapse
Android doesn't update the way Linux does, it only updates apps; the bootloader isn't going to update neatly from a package manager. At the same time, updating the TP's bootloader (moboot) is usually unnecessary. On the other hand I usually like to keep my recovery (TWRP/CWM) up to date. When I switch ROMs I just wipe and flash from recovery. Never had a problem.
Install Android only
bananagranola said:
Android doesn't update the way Linux does, it only updates apps; the bootloader isn't going to update neatly from a package manager. At the same time, updating the TP's bootloader (moboot) is usually unnecessary. On the other hand I usually like to keep my recovery (TWRP/CWM) up to date. When I switch ROMs I just wipe and flash from recovery. Never had a problem.
Click to expand...
Click to collapse
I wander what i am doing wrong? i had skizoid and wanted to go back to cyanogenmod. followed the rules for flashing a rom and at the bootloader i had an entry still on the list for skiziod and the cyanogen entry, when i clicked the cyan entry i got the eternal loading screen.
geomonroe said:
I wander what i am doing wrong? i had skizoid and wanted to go back to cyanogenmod. followed the rules for flashing a rom and at the bootloader i had an entry still on the list for skiziod and the cyanogen entry, when i clicked the cyan entry i got the eternal loading screen.
Click to expand...
Click to collapse
What rules are you following? Full wipe? Leaving extra stuff in moboot is normal. You can delete the extras if they really bother you.
wipe cache and dalvik and factory reset
geomonroe said:
wipe cache and dalvik and factory reset
Click to expand...
Click to collapse
You should wipe system as well and if the extra uimage is still there you can delete it using a file manager after booting
4catalyst2cI said:
You should wipe system as well and if the extra uimage is still there you can delete it using a file manager after booting
Click to expand...
Click to collapse
As far as I know, most ROM install scripts automatically wipe system for you. Can't hurt to try, though.
Thankfully I have this zip again thanks to sstar posting it the other day. This zip will wipe your ulmage clean. Just flash it as you would a rom, than flash rom and gapps after.
https://copy.com/3F9kE

[Q] Deleted system partition

I was wiping data and cache on twrp and I accidentaly deleted the system partition. The thing is, I was in the 4.4.3 brazil retail stock rom and I can't find this firmware to flash with rsd. So, what should I do?
Guilhermewpds said:
I was wiping data and cache on twrp and I accidentaly deleted the system partition. The thing is, I was in the 4.4.3 brazil retail stock rom and I can't find this firmware to flash with rsd. So, what should I do?
Click to expand...
Click to collapse
Oh boy....this is a tricky one.
The full STOCK 4.4.3 SBF for the Brazil Retail Rom has not been 'leaked' yet....
Be VERY careful or you could end up with a brick.
Here are my suggested instructions, but DO NOT FOLLOW THEM until another user comments and verifies that I have given you the correct method -- we are in uncharted territory here.
I would suggest downloading the ENTIRE stock 4.4.2 Brazil Retail SBF, extracting it, and running JUST the following commands:
mfastboot flash system system.img
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot erase cache
mfastboot erase userdata
THEN, reboot, and accept the 4.4.3 OTA to get you back on track. This SHOULD work, but wait for another user to verify my suggestions.
The thing is, you cannot flash gpt.bin from the 4.4.2 ROM. Fortunately, the bootloader version did not change, so if we can get you safely booted into 4.4.2, you SHOULD be able to accept the OTA and be back to 4.4.3 without any mismatched partition tables or bootloader.
I hightly suggest making a backup afterwards, so you can restore if something like this happens again...
I also suggest (as you have seen) erasing all userdata (and cache) because it is unknown what problems might arise if you flash the 4.4.2 system.img with your existing userdata.
Unfortunately, this means you will need to set everything up from scratch, but --better safe than sorry--.
Good Luck with this, and one last time - please wait for another experienced user to verify my methods. I do NOT want to be responsible for you bricking your device...
EDIT: Still no reply/confirmation. @KidJoe , @KJ , what do you guys think??
@Guilhermewpds and @samwathegreat
I would be careful.
even though the bootloader did not change between 4.4.2 and 4.4.3, the GPT.BIN (partition table) did. So there could still be issues when trying to "downgrade"
My gut reaction would be, try to flash only the system.img from the 4.4.2 SBF along with erasing userdata and cache, and if it works to get the phone up and running, make sure to NOT take any OTAs. Stick on that until the 4.4.3 SBF leaks, and then flash the SBF to get back to 4.4.3 and bring everything back in line.
keep in mind that erasing userdata will wipe the data and apps you've added to the phone, so I would flash system.img, see if the phone boots, copy any data from it that you can, and then go back and use mfastboot to erase userdata and cache.
I forgot to mention, but i have an unlocked bootloader, so I believe I could, for instance, install a 4.4.3 rom too, couldn't I? I just want to know what is the less risky thing to do in this situation
Guilhermewpds said:
I forgot to mention, but i have an unlocked bootloader, so I believe I could, for instance, install a 4.4.3 rom too, couldn't I? I just want to know what is the less risky thing to do in this situation
Click to expand...
Click to collapse
Although I hate to say it, in this case the less risky method would be to download the entire 4.4.3 SBF for the T-Mobile XT1053, and flash the entire ROM using either fastboot, or RSD Lite.
This should get you up and running in NO time, with much less risk. If and when the Brazil 4.4.3 SBF is released, you can flash it back on, if you want.
---------- Post added at 10:33 AM ---------- Previous post was at 10:30 AM ----------
KidJoe said:
@Guilhermewpds and @samwathegreat
I would be careful.
even though the bootloader did not change between 4.4.2 and 4.4.3, the GPT.BIN (partition table) did. So there could still be issues when trying to "downgrade"
My gut reaction would be, try to flash only the system.img from the 4.4.2 SBF along with erasing userdata and cache, and if it works to get the phone up and running, make sure to NOT take any OTAs. Stick on that until the 4.4.3 SBF leaks, and then flash the SBF to get back to 4.4.3 and bring everything back in line.
keep in mind that erasing userdata will wipe the data and apps you've added to the phone, so I would flash system.img, see if the phone boots, copy any data from it that you can, and then go back and use mfastboot to erase userdata and cache.
Click to expand...
Click to collapse
So exactly the same as my suggestion, except NOT accepting the OTA. Thanks for the input
Guilhermewpds said:
I forgot to mention, but i have an unlocked bootloader, so I believe I could, for instance, install a 4.4.3 rom too, couldn't I? I just want to know what is the less risky thing to do in this situation
Click to expand...
Click to collapse
I usually don't recommend flashing a full ROM/SBF from another carrier and/or model X.. There are a bunch of caveats to keep in mind which makes it risky.
Since you mention you are Brazil, do you have an XT1052, XT1058 or XT1053? My guess is XT1058.
The Only 4.4.3 SBF out there right now appears to be the T-Mobile USA (same as GSM Dev Edition) 4.4.3. You could try it.
If you have an XT1053, its less risky to flash the T-Mo USA SBF, but if your X is an XT1052 or XT1058, then know that the modems will be different and would change the process of flashing the T-MO SBF, or you will lose support of some frequencies.
---------- Post added at 10:54 AM ---------- Previous post was at 10:46 AM ----------
samwathegreat said:
So exactly the same as my suggestion, except NOT accepting the OTA. Thanks for the input
Click to expand...
Click to collapse
Kind of. But I suggested backing up before doing the erase userdata and left off the erase modemst1 & modemst2 because I'm not sure it is really needed.
KidJoe said:
Kind of. But I suggested backing up before doing the erase userdata and left off the erase modemst1 & modemst2 because I'm not sure it is really needed.
Click to expand...
Click to collapse
Modemst1 / Modemst2 = baseband cache partitions. Probably NOT necessary, but definitely can't hurt.
What a tricky situation
I can't think of a way to to express in any more urgency how important it is to not downgrade.....it is already stickied at the top of almost every subforum on here.....I just hate to see these guys end up bricking such a great phone
EDIT: and yes, ALL Brazil Moto X's are XT1058
EDIT2: I also want to point out that although I would normally NEVER recommend flashing another carrier's ROM...I feel it is irresponsible to advise users at it is "perfectly safe", without providing any disclaimer. Think about @bernardomendez181 , who blames another user on this forum for his phone getting bricked. He was advised that it was perfectly safe, and didn't even say "do it at your own risk". That gentleman ended up with a brick, sadly
BUT, you are already in a pickle here. Seems to me that flashing a ROM with the same version of GPT.bin is less risky than having mismatched versions, etc.
Also, @KidJoe, I very much value your advice, which is why I asked for you comment in the first place. Your advice and solutions seem well-thought-out and methodical. I appreciate the contributions you make to our community.
So, with the XT1058 being my variant, what would you guys do in my situation: flash the T-Mobile SBF with/without the modems or downgrade to 4.4.2?
Guilhermewpds said:
So, with the XT1058 being my variant, what would you guys do in my situation: flash the T-Mobile SBF with/without the modems or downgrade to 4.4.2?
Click to expand...
Click to collapse
NEVER DOWNGRADE attempt to 4.4.2 (i.e. once you have 4.4.3 on your phone do NOT fully flash a 4.4.2 SBF on your phone.)
It would be a "no brainer" if the 4.4.3 SBF for your XT1058 and carrier was leaked. Just flash the System.img from your carrier's 4.4.3 SBF.
BUT Your situation is tricky. Brazil XT1058 with 4.4.3, and you need to re-flash, BUT there is no Brazil XT1058 SBF available yet.
I think @samwathegreat and I are both in agreement that anything you proceed with at this point (since the Brazil XT1058 4.4.3 SBF hasn't leaked) will be RISKY!!!
There is the potential to brick your phone in the process, or in the future (when taking an upgrade or flashing back to stock), or might end up just being unstable until you can flash with the proper SBF!
That being said, I think what samwathegreat suggested in Post #2 might be the best course of action, but do NOT take any OTAs, instead wait until the full XT1058 4.4.3 SBF for your carrier leaks, or 4.4.4 SBF should it leak, then flash it to get your files back in line and matched up again. And remember that the erase userdata statement will clear your apps, files, etc from the phone, so back up first if you can! You might find some things that don't work properly (like those with 4.4.2 who flashed 4.4 system.img found that their Settings ->Security menu stopped working)
Flashing only parts of an SBF will put your phone in a state with mismatched files (i.e. files from different versions), so its an undesirable state. Take an OTA, in this state, and you will most likely brick, or possibly get lucky and have the OTA fail its validation checks and not attempt to install.
And I can also agree with samwathegreat's EDIT2 in post #7, that flashing a ROM with with same version GPT.BIN might be less risky than flashing just system.img of an older version and running with mismatched files. However, I've seen people successfully run with a lower system.img and do a FULL SBF back to the current rom version when it was released without bricking.
Then again, another option is flash the system.img from the T-Mobile 4.4.3 SBF, and run with that ( i would still recommend erase cache and erase userdata, and do NOT take any OTA's), and again flash the Brazil XT1058 4.4.3 SBF (or 4.4.4 sbf) if/when it leaks.
So I followed @samwathegreat guide and could put it running again. Thank you so much! The only problem that I've found is that I can't turn wifi on. There's something I could do to fix it or I'll have to wait for the brazilian 4.4.3 SBF?
Guilhermewpds said:
So I followed @samwathegreat guide and could put it running again. Thank you so much! The only problem that I've found is that I can't turn wifi on. There's something I could do to fix it or I'll have to wait for the brazilian 4.4.3 SBF?
Click to expand...
Click to collapse
I seriously doubt that your WiFi not working is a result of what we have done.
I have a very strong idea on what the problem is.
Are you rooted? Please use a the app "Root Browser" to find your /persist folder.
What files are inside?
I have a suspicion that somehow you formatted your persist partition.
Your persist partition should have (among other folders) the following files inside:
.bt_nv.bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
I bet that you are MISSING your WCNSS_qcom_wlan_nv.bin file!
Let me know if you are missing that file. If so, I will send you a copy and your WiFi should start working again immediately. You can NOT get the file from any of the STOCK firmwares or SBF files, because the /persist partition is SUPPOSED to remain untouched between flashes, and is never supposed to be deleted.
Please advise.
samwathegreat said:
I seriously doubt that your WiFi not working is a result of what we have done.
I have a very strong idea on what the problem is.
Are you rooted? Please use a the app "Root Browser" to find your /persist folder.
What files are inside?
I have a suspicion that somehow you formatted your persist partition.
Your persist partition should have (among other folders) the following files inside:
.bt_nv.bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
I bet that you are MISSING your WCNSS_qcom_wlan_nv.bin file!
Let me know if you are missing that file. If so, I will send you a copy and your WiFi should start working again immediately. You can NOT get the file from any of the STOCK firmwares or SBF files, because the /persist partition is SUPPOSED to remain untouched between flashes, and is never supposed to be deleted.
Please advise.
Click to expand...
Click to collapse
Well, I just checked and I do have those files. Everytime I switch the wifi on it switches back to off.
Guilhermewpds said:
Well, I just checked and I do have those files. Everytime I switch the wifi on it switches back to off.
Click to expand...
Click to collapse
Bummer. The missing file results in the same issue. This is likely due to running mismatched versions.
There is a third option that I failed to consider earlier. If you can find someone willing, with a Brazil xt1058 on 4.4.3, you could have them do a factory reset, erase cache, then do a twrp backup of JUST /system
EDIT: upon further review, it shouldn't be necessary for the person who does this for you to reset and erase cache. JUST making a twrp backup of /system should suffice, IF that user has not modified their /system partition.
You can then flash the backup from within twrp and be in good shape.
This will get you 100% back to stock 4.4.3 Brazil ROM, since the rest of your partitions are already on 4.4.3
This is by far the best option for you, but you will need to convince another user with the Brazil retail xt1058 to do this for you.
Good luck
I'm late to the party. Lol. No matter what I do, I am only getting Tapatalk or XDA premium notifications for a bit...then nothing. Lol. I have to uninstall them, then reinstall...and they work...for hours only. Can't solve it either. ?
Glad the X gurus got you running! Kudos guys! ?
Another example tho that downgrading is evil. Never do it.
All this happened when 4.4.2 came out as well.
Patience is the key. Wait for your OTA's guys. Don't flash other carriers, and don't downgrade. (I know other carrier firmware fixed this issue...but it was that or no phone.).
Glad its running!!
Guilhermewpds said:
Well, I just checked and I do have those files. Everytime I switch the wifi on it switches back to off.
Click to expand...
Click to collapse
If you are interested in trying to get someone to share a TWRP backup of /system, I suggest this:
Make a new post in Q&A Section with this title: [REQUEST] TWRP backup of /system on Brazil Retail XT1058 4.4.3
And explain why you need the backup. It is very likely that another user will do this for you! If you haven't already, read my edit in the previous post: they should NOT have to reset and clear cache.
Just make sure you point out that you ONLY want a backup from someone who has not modified their /system partition, and also make it very clear that you need a backup of JUST /system.
This is fairly easy to do with TWRP. The user who provides you with their /system backup will simply boot into TWRP, click "BACKUP", and UNCHECK everything EXCEPT "System".
Then you will copy this backup provided to you to your internal memory into your TWRP backup folder.
Then YOU will boot into TWRP, press "WIPE", click "Advanced Wipe", then check "Dalvik Cache, Data, Cache, and System".
Next, press RESTORE, and find the backup that you copied to your internal memory, and start the restore.
This should do it for you!!!! Good Luck, and hope you get the needed backup
These instructions were written by memory, so I hope I haven't left out any steps. If you get stuck, let me know and I'll try to help.
samwathegreat said:
If you are interested in trying to get someone to share a TWRP backup of /system, I suggest this:
Make a new post in Q&A Section with this title: [REQUEST] TWRP backup of /system on Brazil Retail XT1058 4.4.3
And explain why you need the backup. It is very likely that another user will do this for you! If you haven't already, read my edit in the previous post: they should NOT have to reset and clear cache.
Just make sure you point out that you ONLY want a backup from someone who has not modified their /system partition, and also make it very clear that you need a backup of JUST /system.
This is fairly easy to do with TWRP. The user who provides you with their /system backup will simply boot into TWRP, click "BACKUP", and UNCHECK everything EXCEPT "System".
Then you will copy this backup provided to you to your internal memory into your TWRP backup folder.
Then YOU will boot into TWRP, press "WIPE", click "Advanced Wipe", then check "Dalvik Cache, Data, Cache, and System".
Next, press RESTORE, and find the backup that you copied to your internal memory, and start the restore.
This should do it for you!!!! Good Luck, and hope you get the needed backup
These instructions were written by memory, so I hope I haven't left out any steps. If you get stuck, let me know and I'll try to help.
Click to expand...
Click to collapse
I tried asking in a brazilian forum for the Moto X, but it seems more likely to get it here. I've run out of thanks, so thank you once again. I really appreciate your assistance!
This is simple suggestions, but worth a shot.
WiFi won't stay on at all? Or does it turn off while connecting? If you are able to...try forgetting your WiFi network if it let's you....and sign in again.
Also, reboot your router/modem.
And try a factory reset if all that fails. Yes, all apps and data will be gone. But with a try.
Basic suggestions....but who knows, something might work.
samwathegreat said:
....There is a third option that I failed to consider earlier. If you can find someone willing, with a Brazil xt1058 on 4.4.3, you could have them do a factory reset, erase cache, then do a twrp backup of JUST /system
Click to expand...
Click to collapse
Duh, I completely forgot about that too... Its been a while since I did backup/restore in CWM/TWRP that it completely slipped my mind. :crying:
KidJoe said:
Duh, I completely forgot about that too... Its been a while since I did backup/restore in CWM/TWRP that it completely slipped my mind. :crying:
Click to expand...
Click to collapse
Yep, I understand. Since we are using the STOCK rom (mostly), I rarely use TWRP anymore. Back in my "HTC Droid Incredible" days, flashing all kinds of different roms, I used to use CWM backups on a daily basis....
Oh well. OP has made a request and hopefully someone will share soon.
I finally got it in a brazilian forum. Thank you, @samwathegreat, @KidJoe and @KJ for your assistance and guidance! I really appreciate your help!

best way to decrypt a tmobile phone running pure rom

so, just got my nexus a couple of days ago, and loving it!
would like to decrypt, but not 100% sure on the best/safest way to do it at this point..
running pure rom, with lots of tweaks, and I originally unlocked and rooted with Wugs great toolkit.
I know if I decrypt at this point I will lose all my data and stuff, but of course its already backed up in a couple of places, and I have the "fixes" to flash after I decrypt to keep me that way, if I flash a "encrypted" rom by mistake.
Just wondering if someone could make a straightforward post, telling me the 3 or 4 things I need to do/flash to get to that point.
Thanks so much!:good:
you need to flash a custom kernel that allows for decryption, then you have to format your storage. only then will you boot up decrypted. if you dont actively decrypt(format your storage), you wont be decrypted. this will delete everything in your storage.
ok, then do you know of a kernel for Tmobile that allows for that?
do I flash that kernel in twrp, then also format everything else in TWRP?
if I do that, how do I then boot my phone into something useable so I can rebuild it once again?
thanks
wase4711 said:
ok, then do you know of a kernel for Tmobile that allows for that?
do I flash that kernel in twrp, then also format everything else in TWRP?
if I do that, how do I then boot my phone into something useable so I can rebuild it once again?
thanks
Click to expand...
Click to collapse
You can use the Nexus Root Toolkit to decrypt as well. I believe its under advanced utilities-flash boot image. You will have to be on a stock build however, so you could also use flash stock plus unroot. I believe there is an option there for flashing a no encrypt kernel in the process.
Sent from my Nexus 6 using Tapatalk
wase4711 said:
ok, then do you know of a kernel for Tmobile that allows for that?
do I flash that kernel in twrp, then also format everything else in TWRP?
if I do that, how do I then boot my phone into something useable so I can rebuild it once again?
thanks
Click to expand...
Click to collapse
any custom kernel does. and there is no such thing on any nexus device as aa rom or kernel for a specific carrier, they all work on tmobile.
Othoric said:
You can use the Nexus Root Toolkit to decrypt as well. I believe its under advanced utilities-flash boot image. You will have to be on a stock build however, so you could also use flash stock plus unroot. I believe there is an option there for flashing a no encrypt kernel in the process.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
simms22 said:
any custom kernel does. and there is no such thing on any nexus device as aa rom or kernel for a specific carrier, they all work on tmobile.
Click to expand...
Click to collapse
thanks guys, I got it now!
Final question; is there a REAL difference in performace when you are decrypted, or is it mostly placebo?
this phone, on Pure Rom, is super fast and smooth, and I cant imagine it getting much better if decrypted, but as a Nexus N00b, I just dont know.
Thanks again for your help and feedback :good:
Most likely Pure has a decrypt kernel. Haven't looked. Beans usually adds all those tweaks. Just need to format data. May Lose your data and have to start over. Not sure as I run encrypted. If run decrypted might as well welcome Stagefright too.
ah, good point, so running decrypted makes you vulnerable to that krap...
wase4711 said:
ah, good point, so running decrypted makes you vulnerable to that krap...
Click to expand...
Click to collapse
Decrypted makes you vulnerable to any data exploit. Stagefright is different but both are security risks. Probably won't see a performance boost with decrypt. Only can be seen with large data files. Won't see with apps or daily use.
wase4711 said:
thanks guys, I got it now!
Final question; is there a REAL difference in performace when you are decrypted, or is it mostly placebo?
this phone, on Pure Rom, is super fast and smooth, and I cant imagine it getting much better if decrypted, but as a Nexus N00b, I just dont know.
Thanks again for your help and feedback :good:
Click to expand...
Click to collapse
I've ran both. And I actually just decrypted for a second time to see if I noticed any difference. To be perfectly honest, and this is just my personal experience, I haven't seen any noticeable difference between being encrypted or not since the release of 5.1. And since there are some ROMs out there that do have force encryption, I personally am going to go back to being encrypted just so I have one less thing to worry about when flashing ROMs. But there is a flashable zip that you can flash after any ROM that will disable force encryption if you want to go that route.
Sent from my Nexus 6 using Tapatalk
Let's clear things up. There is only one way to do it. You first need a kernel that doesn't force encryption (most don't force) so check the rom thread as its kernel probably doesn't either.
Then, you have to format userdata, which means all your apps, data (including sdcard) and settings will be gone.
Granted, there are a few ways to get these 2 steps done, but "fastboot format userdata" or format /data from TWRP recovery are the best.
As for TMobile, its the exact same phone as every other in north America, so all roms and kernels work. Actually there is.only one other model.(international) .and that works.with all the same.ROMs.and kernels.too.
Thanks for clarification. The format userdata was what I wasn't sure about. Recovery format I know clears all data. Fastboot format userdata restores data after format. Fastboot erase userdata wipes data. Wasn't sure which type format was required.
danarama said:
Let's clear things up. There is only one way to do it. You first need a kernel that doesn't force encryption (most don't force) so check the rom thread as its kernel probably doesn't either.
Then, you have to format userdata, which means all your apps, data (including sdcard) and settings will be gone.
Granted, there are a few ways to get these 2 steps done, but "fastboot format userdata" or format /data from TWRP recovery are the best.
As for TMobile, its the exact same phone as every other in north America, so all roms and kernels work. Actually there is.only one other model.(international) .and that works.with all the same.ROMs.and kernels.too.
Click to expand...
Click to collapse
thanks man, I am out of thanks for the day, but I do appreciate the input!
it sounds like with 5.1, there isn't a real strong reason to decrypt, and with all the stagefright nonsense floating around, and what ever other hidden exploits there are, its probably better at this point to just stay encrypted, since it doesn't sound like there are any major advantages to decrypt right now.
I appreciate everyone who posted in here for their knowledge and insight, and I will make sure I help anyone else going forward with a similar question.:good::good:
prdog1 said:
Thanks for clarification. The format userdata was what I wasn't sure about. Recovery format I know clears all data. Fastboot format userdata restores data after format. Fastboot erase userdata wipes data. Wasn't sure which type format was required.
Click to expand...
Click to collapse
fastboot erase userdata wipes all data but doesn't recreate the file system so the filesystem will retain the encryption flag.
fastboot format userdata will recreate the filesystem losing the encryption flag and since the kernel won't re-add the flag on boot, ,you're good to go.
Neither restore data.
Same in recovery, erase/wipe data won't format, only format will.
danarama said:
fastboot erase userdata wipes all data but doesn't recreate the file system so the filesystem will retain the encryption flag.
fastboot format userdata will recreate the filesystem losing the encryption flag and since the kernel won't re-add the flag on boot, ,you're good to go.
Neither restore data.
Same in recovery, erase/wipe data won't format, only format will.
Click to expand...
Click to collapse
You are correct. Thanks for the clarification. I run modified stock rooted so don't run into a lot of these scenarios that break their devices. All my mods are hard coded.
Mod Edit
Thread Closed - At OP request
ronnie498
Forum Moderator

Fastboot question.

Hello guys! I have a simple and probably obvious question for you all! So, when a new update comes out and it's the same Android version, can you get away with just flashing the Bootloader, Radio, and System partition? Leaving your userdata intact and keeping your apps? Thanks!
H4X0R46 said:
Hello guys! I have a simple and probably obvious question for you all! So, when a new update comes out and it's the same Android version, can you get away with just flashing the Bootloader, Radio, and System partition? Leaving your userdata intact and keeping your apps? Thanks!
Click to expand...
Click to collapse
yes. you don't have to flash the bootloader nor the radio either
Not required. If you look inside the factory image files, often times, the bootloader and radio are just being recycled from prior versions.
Thanks guys! So just the system is required for an update? I can leave my custom kernel alone, with systemless root? You guys are so helpful! Thanks again!
H4X0R46 said:
Thanks guys! So just the system is required for an update? I can leave my custom kernel alone, with systemless root? You guys are so helpful! Thanks again!
Click to expand...
Click to collapse
Personally, I've never gotten the "flash-all" command to work, maybe some of you here have, but it never works for me, so I open the factory image and fastboot each component in. The wiping of data is in the flash-all script which I don't use. In your case, I'd just pull the system image and flash it, then delete everything else. I haven't checked to see if there is a new bootloader or radio. I'm downloading right now.
mikeprius said:
Personally, I've never gotten the "flash-all" command to work, maybe some of you here have, but it never works for me, so I open the factory image and fastboot each component in. The wiping of data is in the flash-all script which I don't use. In your case, I'd just pull the system image and flash it, then delete everything else. I haven't checked to see if there is a new bootloader or radio. I'm downloading right now.
Click to expand...
Click to collapse
Cool thanks! From now on, I'll probably md5 check the radio and Bootloader files to see if they match between versions. And I've always flashed my images manually, I like to know what's being done to my phone, I don't trust the flash-all script and never used it before lol
H4X0R46 said:
Cool thanks! From now on, I'll probably md5 check the radio and Bootloader files to see if they match between versions. And I've always flashed my images manually, I like to know what's being done to my phone, I don't trust the flash-all script and never used it before lol
Click to expand...
Click to collapse
I just checked. The most recent version has the same bootloader and baseband. Save yourself the 1GB download LOL. No need.

Stock M7 won't take ota update because it thinks it's modified?

Friend bought his M7 new and never modified it but it won't take an ota update (Telstra) saying in the log that framework.apk has unexpected contents. Even after factory reset.
What's the quickest way to fix this? I had a look around and there's a looooot of (general and varied) info floating around but nothing relating to this particular issue so I'm hoping there's a bit easier fix than reading through dozens of threads and maybe ending up in a worse position.
Thanks
defroster said:
Friend bought his M7 new and never modified it but it won't take an ota update (Telstra) saying in the log that framework.apk has unexpected contents. Even after factory reset.
What's the quickest way to fix this? I had a look around and there's a looooot of (general and varied) info floating around but nothing relating to this particular issue so I'm hoping there's a bit easier fix than reading through dozens of threads and maybe ending up in a worse position.
Thanks
Click to expand...
Click to collapse
A factory reset will only wipe the /data partition (note that i'm saying "wipe" not "restore"). Framework.apk is on the /system partition, if the file has been modified or somehow got corrupt, a factory reset will not restore that file. (cause factory reset isn't touching /system and neither restoring anything, just deleting user data)
/system files are normally write protected by the stock kernel and to bypass this protection you need at least a custom recovery. So either the phone wasn't really new (someone tampered it before the update) or something went wrong and the file got corrupt.
Flashing a RUU should bring back the phone 100% stock and restore the ability to take ota updates. Look at stickies in the general section.
alray said:
A factory reset will only wipe the /data partition (note that i'm saying "wipe" not "restore"). Framework.apk is on the /system partition, if the file has been modified or somehow got corrupt, a factory reset will not restore that file. (cause factory reset isn't touching /system and neither restoring anything, just deleting user data)
/system files are normally write protected by the stock kernel and to bypass this protection you need at least a custom recovery. So either the phone wasn't really new (someone tampered it before the update) or something went wrong and the file got corrupt.
Flashing a RUU should bring back the phone 100% stock and restore the ability to take ota upduates. Look at stickies in the general section.
Click to expand...
Click to collapse
It definitely wasn't modded, he wouldn't know how and he got it new from Telstra.
Don't you need s-off to flash an ruu?
defroster said:
It definitely wasn't modded, he wouldn't know how and he got it new from Telstra.
Don't you need s-off to flash an ruu?
Click to expand...
Click to collapse
It can be easier with s-off but it's not mandatory.
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

Categories

Resources