*removed*
I attempted to use this as a base to flash the LYZ28E ota and it failed the system check, so it isn't very useful.
WugFresh modified this build for use with his root toolkit, so if you still need if for some reason, you can find it here:
http://forum.xda-developers.com/nex...kit-v1-9-8-t2947452/post60076292#post60076292
In for the ride!
I suggest changing "fastboot erase cache" to "fastboot format cache". When I flashed this, I went into a bootloop because it seems like "fastboot erase cache" turns cache into an unformatted partition, so I went back into the bootloader and did "fastboot format cache".
Just making sure... this isn't some April fool's joke, right? It was posted on 4/1. If I flash this it isn't going to brick my phone?
mlevin said:
Just making sure... this isn't some April fool's joke, right? It was posted on 4/1. If I flash this it isn't going to brick my phone?
Click to expand...
Click to collapse
Haha. You know I thought that when he 1st posted it but I flashed it and its good. Don't think anyone would go that far with April fools. Tks Q for these. Your the man!! :thumbup:
Cool. I'm already on LMY47D and it seems to have the same radio and bootloader as LMY47M so I'm just gonna flash the boot and system partitions and then format cache and see how that goes. I don't think I want/need all the steps in the script.
So if I have Franco kernel & wanna keep it, I can skip the boot.img right? All I should need is the system.img if I'm not wiping correct? Bootloader & radio should be the same as D, which I'm on. And I've never seen oem.img before. What is that?
Just got off the phone with T-Mobile after switching from Verizon (w00t w00t) and this is their firmware version. I'm running LMY47E now, can I flash all but the userdata.img and not have to re-install or setup any apps or device settings?
TIA
X
Related
Hi,
I seem to be bricked more than usual. Don't ask me how, I was doing something, rebooted and now I can't get into early usb mode or android recovery. I have no clue what half the other boot options are.
I can use rsd lite to flash sbfs, no problem. Phone is stuck at initial m, no animation. I suspect it is something dumb like the internal memory having an error, something is causing the linux bit to loop. Not reboot, not crash, just hang there.
i can use fastboot, but since it uses names for partitions, I don't know how to flash exact partitions or know what they all are, I have system, webtop, boot, recovery, cdrom, other things like pds are not allowed.
I have a dev usb cable made up, can do everything without a battery, which is cool, have an extra battery and external battery charger. Obviously, I have all the partitions available as backups.
Somehow, I need to get the partitions restored, and internal memory formatted perhaps.
Any ideas? Short of trying to send it back?
Thanks.
for my little experience a full wiped pds let you run the os...and you know better than me which are the others partitions not overwritten by a flash with full sbf
I had a backup of my pds, but no way to flash it or erase it.
Thanks!
in milestone i was having your problem when changing builds (froyo,ginger, eclair) via update.zip without the correct boot.img
but if you already flashed the sbf...
have you tried flashing boot and recovery partition, and then entering it? maybe you regain adb access
I think I am getting blocked before I even get to recovery, early usb, android recovery, etc.
I have fastboot access and nvflash, so in other words I have fastboot.
I can flash boot, recovery, system, webtop, cdt, cdrom, preinstall, but not pds, and I can't erase boot etc.
Thanks.
...i searched for nvram in android:
maybe it's useful (from droid incredible dev area)
dknlght said:
I finally successfully recovered my BootLooped Incredible after i incorrectly updated the NV item of my phone. My situation was a little different than most bootloop error because no matter which stock rom or recovery image I flash nothing would stop it from rebooting because the NV items weren't overwritten during the flash. Then I came across a solution for the EVO by cutthroatamft on how he recovered his EVO from the same Mistake but unfortunately all his files were geared toward the EVO. After much searching I accidentally came across a single comment that posted a link for the ENG-HBOOT for the incredible. Now i manage to replace all the EVO specific files with the Dinc equivalent. Below is the link to the files and instructions compile by cutthroatamft but I updated it for the Dinc. Hopefully this helps someone else that has this problem. can't post a live link but I think you can figure it out
www megaupload . com /?d=RCZBCDDA
Click to expand...
Click to collapse
hope it helps somehow
Well, the file is about HTC phones, so it doesn't really apply, no hboot to swap to get a fastboot.
"fastboot erase nv"
"fastboot erase userdata"
"fastboot erase system"
"fastboot erase recovery"
"fastboot erase microp"
"fastboot erase boot"
"fastboot erase radio"
"fastboot flash nv nv.img"
I could try to do a flash nv nv.img perhaps, probably not a good idea since I have no idea what is in it, and likely locked against flashing. Interesting to see more fastboot partition names, although erase system or boot won't work.
Cheers!
NFHimself said:
Well, the file is about HTC phones, so it doesn't really apply, no hboot to swap to get a fastboot.
"fastboot erase nv"
"fastboot erase userdata"
"fastboot erase system"
"fastboot erase recovery"
"fastboot erase microp"
"fastboot erase boot"
"fastboot erase radio"
"fastboot flash nv nv.img"
I could try to do a flash nv nv.img perhaps, probably not a good idea since I have no idea what is in it, and likely locked against flashing. Interesting to see more fastboot partition names, although erase system or boot won't work.
Cheers!
Click to expand...
Click to collapse
i did not say that file was for you.
but if you can flash boot recovery system and your system won't boot it's something else in the bootstrap process (excluding hardware failures, you could not access fastboot then).
as i read you can flash (already flashed?) almost every partition except pds (useless for your needs) and nv.
i reported a case of other guys experiencing your same problem, with i guess the same cause.
i give you an idea, unfortunately i'm not a dev to give you solution
cheers
I've been having a few issues with the root and rom as time has went on. First my fingerprint reader went, then I would have random crashing and shutdowns. Those errors began to get more frequent, and now the internal memory card decided it will wipe itself clean. So I'm done with what ever I had installed. According to the phone that was on April 4th.
I've read some confusing stuff on here about rooting and unrooting, and none of the information is the same. I imagine thats because of all the updates the phone has gone through.
I would like to install cm7 or cm9 since it seems much more stable.
Any help at all to even simply unroot the phone would be appreciated. I need full functionality back.
Atrix 4g
android ver. is 2.2.1
kernel ver is 2.6.32.9
Build number is 1.5.7
Rom: GingerBlur
Just wipe data,cache and dalivk from recovery and install which ever rom u want if u have a unlocked bootloader for completely erasing the previous rom u can use fastboot wit these commands.
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
And if u have not unlocked the bootloader check this link first
THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs
terminator1983 said:
Just wipe data,cache and dalivk from recovery and install which ever rom u want if u have a unlocked bootloader for completely erasing the previous rom u can use fastboot wit these commands.
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
And if u have not unlocked the bootloader check this link first
THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs
Click to expand...
Click to collapse
Actually, if you want the cleanest and least likely to cause problems method, you should do a full fastboot wipe prior to installing any new ROM. Just wiping data, cache, and dalvik does not give you a completely clean wipe and prep properly for the new ROM.
If you are updating a ROM from a previous release, you are usually OK with just wiping Dalvik and cache. The dev will normally state what to do in their thread.
Thanks for the replies. How would I be able to check if I've unlocked the boot loader? I did this almost a year ago so I don't remember if I also did that.
21q said:
Thanks for the replies. How would I be able to check if I've unlocked the boot loader? I did this almost a year ago so I don't remember if I also did that.
Click to expand...
Click to collapse
We couldn't unlock the bootloader a year ago. Was around end of June we had this ability.
If ur phone bootloader is unlocked u can see unlocked written on top corner of boot screen logo.
terminator1983 said:
If ur phone bootloader is unlocked u can see unlocked written on top corner of boot screen logo.
Click to expand...
Click to collapse
Not necessarily. If a SBF has been flashed after unlock, the word "unlocked" is not there.
So going off of what you two have said and another thread I looked at. I have time to do this sunday.
First I will unlock the bootloader
then run through these steps
boot to recovery
Wipe Dalvik
wipe cache
factory reset/data
boot into fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
From here I can then load cm7 rom onto my sd card and install it via recovery?
Also, reading further into cm7, it doesnt support he fingerprint reader or web/lap-top huh. Are there any nightly releases that have it? I've seen ONE, but I've been out of this scene too long to really know what good right now.
21q said:
So going off of what you two have said and another thread I looked at. I have time to do this sunday.
First I will unlock the bootloader
then run through these steps
boot to recovery
Wipe Dalvik
wipe cache
boot into fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
From here I can then load cm7 rom onto my sd card and install it via recovery?
Also, reading further into cm7, it doesnt support he fingerprint reader or web/lap-top huh. Are there any nightly releases that have it? I've seen ONE, but I've been out of this scene too long to really know what good right now.
Click to expand...
Click to collapse
Download CM7.2 RC1 > http://forum.xda-developers.com/showthread.php?t=1556246. It has full FP reader support, both security and navigation. (No webtop though).
After unlocking the bootloader (assuming you will be following these instructions > http://forum.xda-developers.com/showthread.php?t=1136261) You will need root again (instructions also in the previously linked thread), and then you will want to flash Romracers recovery through fastboot before flashing any ROM >
http://forum.xda-developers.com/showthread.php?t=1204500
After this you will be able to get into recovery and flash whatever you want. There is an automated script here for unlocking the bootloader also located here > http://forum.xda-developers.com/showthread.php?t=1182871.
Been a while since I did all this myself, but I think I covered everything!
Good luck.
***Ignore this post***
So I don't need to run any of those fastboot commands??
And should I update my phone to 2.3.4?
I just updated it to 1.8.3 by flashing the sbf so I've lost root and everything.
I ended up flashing using this method
http://forum.xda-developers.com/showthread.php?t=1138204
I used the sbf that was supposed to already have the bootloader unlocked and the do some things for root.
When I went to install romracers though I was getting the error (180002)
From what I have read that means the boot loader wasnt actually unlocked?
So I'm guess I should flash the regular 2.3.4sbf. Then manually unlocked the bootloader myself and then root?
Or could I still manage with whats currently installed some how?
Again thanks in advance for any advice.
CaelanT said:
Not necessarily. If a SBF has been flashed after unlock, the word "unlocked" is not there.
Click to expand...
Click to collapse
Does it mean u have relocked the bootloader or it is still unlocked ?
Sent from my MB860 using xda premium
Does doing a full fastboot wipe delete the cwm recovery?
arpit85 said:
Does it mean u have relocked the bootloader or it is still unlocked ?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I don't believe it was ever unlocked
When I flashed the sbf via rdslite it would go to 100% but would be stuck saying "in process"
I made a new thread though since my problem is completely different now
http://forum.xda-developers.com/showthread.php?t=1568347
21q said:
I ended up flashing using this method
http://forum.xda-developers.com/showthread.php?t=1138204
I used the sbf that was supposed to already have the bootloader unlocked and the do some things for root.
When I went to install romracers though I was getting the error (180002)
From what I have read that means the boot loader wasnt actually unlocked?
So I'm guess I should flash the regular 2.3.4sbf. Then manually unlocked the bootloader myself and then root?
Or could I still manage with whats currently installed some how?
Again thanks in advance for any advice.
Click to expand...
Click to collapse
If you flashed sbf with rsdlite and text unlocked is gone, thats mean that you have relocked BL.
You can unlock again by flashing via RSDLite this:
ATT ONLY(It works for 4.5.91 and 4.5.141- Tested myself yesterday) - http://diamantephoto.com/pudding.rar
It is from post:
http://forum.xda-developers.com/showthread.php?t=1136261
Hey guys, I have a quick question about my warranty and root with the Elemental recovery. I rooted my tablet and loaded the recovery and now am having some issues UNRELATED to the modding of my tablet. Now I am going to send it in for repair and want to make sure they don't receive a modded tablet. Do I just need to do a factory reset or are there some other steps I need to take to make sure that when they receive my tablet, they can't tell it was ever modified? I read about a flash counter somewhere, so I'm not sure if I have to do anything with that, or if it really is as easy as a factory reset. I would love any and all help and look forward to hearing back.
Thanks a bunch,
Chris
ChrispyChris said:
Hey guys, I have a quick question about my warranty and root with the Elemental recovery. I rooted my tablet and loaded the recovery and now am having some issues UNRELATED to the modding of my tablet. Now I am going to send it in for repair and want to make sure they don't receive a modded tablet. Do I just need to do a factory reset or are there some other steps I need to take to make sure that when they receive my tablet, they can't tell it was ever modified? I read about a flash counter somewhere, so I'm not sure if I have to do anything with that, or if it really is as easy as a factory reset. I would love any and all help and look forward to hearing back.
Thanks a bunch,
Chris
Click to expand...
Click to collapse
I would say to do a back up if possible. After what I did is a flash the factory image and I relock the bootloader. If you don't flash the factory image and you don't relock the bootloader , they would just send it back.
Here are the commends for the flashing of recovery images.
Fastboot flash bootloader bootloader...
Fastboot reboot
Fastboot erase boot
Fastboot flash boot boot.img
Fastboot erase recovery
Fastboot flash recovery recovery.img
Fastboot erase system
Fastboot flash system system.img (this can take up to 15 minutes do not cancel process)
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot erase vendor
Fastboot flash vendor vendor.img
Fastboot reboot bootloader
After you finish that, you must type the following command.
Command to relock your devices
Fastboot oem_lock
I hope this was helpful.
I don't see why you can't just use the "flash all" batch file. Does the batch file do something different?
whowatchlist said:
I don't see why you can't just use the "flash all" batch file. Does the batch file do something different?
Click to expand...
Click to collapse
Yes but must of the time it says the it could found files. Try it and if it doesn't flash all do the steps that I posted before
Just wanted to thank you jonny, I'm fresh on the newest factory image.
Its no problem
I was recently in a hot bowl of $h!t when I unlocked my bootloader for my new 6P already on 7.0 N90G latest build. Little did I know that it would be this hard to get twrp as it was relatively painless on my previous device prior to N. Anyways I'm making these for those who get stuck on the Twrp splash screen on any Android N build.
Explanation:
Your device isn't decrypted. You need to decrypt it before flashing TWRP.
Process:
Get a modified boot.img for the build you use. Flash it in fastboot. They can be found here.
Decrypt you device. Do this by rebooting into bootloader. The on your PC in a fastboot command use the commands below one after the other
"["fastboot format userdata" wipes the entire phone including pics/vids, texts, etc.]" @SlimSnoopOS
Code:
fastboot format userdata
Code:
fastboot format cache
Now install twrp using any method you know. Get the imgs here.
Yeah I lied it wasn't hard but just tricky. Enjoy!
Credit:
@Heisenberg
@Tigerstown
Thanks for the thought but you don't need to credit me here
You should mention that running "fastboot format userdata" wipes the entire phone including pics/vids, texts, etc. Someone will run this command ignorantly.
Sent from my Nexus 5X using Tapatalk
I recently installed nougat myself on my nexus5x. Couldn't install twrp. Thanks for the explanation and tutorial.
I have 2 questions.
Why do I need a modified boot.img?
And in a future update to final nougat, how do I proceed then with a modified boot.img and custom recovery?
chucky8 said:
I recently installed nougat myself on my nexus5x. Couldn't install twrp. Thanks for the explanation and tutorial.
I have 2 questions.
Why do I need a modified boot.img?
And in a future update to final nougat, how do I proceed then with a modified boot.img and custom recovery?
Click to expand...
Click to collapse
First off. TWRP couldn't decrypt N right now, so to overcome this, we decrypt the device.
Forced encryption is implemented through the kernel. The modified boot image disables that. So now upon booting, your device shall not be encrypted.
As for the future, you will have to do the same and flash the corresponding modified boot.img, when it comes out.
How do i know if my nexus is decrypted or not ?
ariefabuzaky said:
How do i know if my nexus is decrypted or not ?
Click to expand...
Click to collapse
If you don't know, then you are Encrypted. Look under Settings/Security/Encryption. It will either read "Encrypted" which is obvious or "Encrypt Phone" which means you are decrypted.
Sent from my Nexus 5X using Tapatalk
You don't have to decrypt. You can just push things you wanna flash to /tmp instead of decrypting data
farshad525hou said:
You don't have to decrypt. You can just push things you wanna flash to /to instead of decrypting data
Click to expand...
Click to collapse
Exactly. But then again, it is all about personal preference. I personally don't like connecting any external device to flash anything. Too slow to first download the files, then push 'em up to the HDD or Pen drive and then connecting it to the device to flash. I believe there are more users here, just like me.
For those who would need to decrypt, this is aptly the right process to begin with. Appreciations to @hackarchive for making this thread. Over at the three N based threads, I see several people asking about the decryption process, and this thread would definitely help the newcomers to get their foot in the right direction.
Just so that I'm clear on this. Is this the correct way/order
1. fastboot flash the boot.img
2. fastboot format userdata
3. fastboot format cache
4. flash twrp
Just want to be sure before I format userdata. Thanks
lbcary said:
Just so that I'm clear on this. Is this the correct way/order
1. fastboot flash the boot.img
2. fastboot format userdata
3. fastboot format cache
4. flash twrp
Just want to be sure before I format userdata. Thanks
Click to expand...
Click to collapse
NM, read that as flash userdata ...
Sent from my Nexus 6P using Tapatalk
I just did this and it worked but now I rebooted to TWRP to flash suhide, all I did was to swipe right on the warning twrp gives at the start and flash suhide, now I'm stuck at the splash screen again
What if i decrypt my phone prior to unlock boot loader? Or it doesn't work that way?
Sent from my ONEPLUS A3003 using Tapatalk
shamps said:
What if i decrypt my phone prior to unlock boot loader? Or it doesn't work that way?
Click to expand...
Click to collapse
Doesn't work that way.
The Fix is not needed anymore, newest TWRP is able to decrypt your phones storage. Only use newest twrp.
hackarchive said:
I was recently in a hot bowl of $h!t when I unlocked my bootloader for my new 6P already on 7.0 N90G latest build. Little did I know that it would be this hard to get twrp as it was relatively painless on my previous device prior to N. Anyways I'm making these for those who get stuck on the Twrp splash screen on any Android N build.
Explanation:
Your device isn't decrypted. You need to decrypt it before flashing TWRP.
Process:
Get a modified boot.img for the build you use. Flash it in fastboot. They can be found here.
Decrypt you device. Do this by rebooting into bootloader. The on your PC in a fastboot command use the commands below one after the other
"["fastboot format userdata" wipes the entire phone including pics/vids, texts, etc.]" @SlimSnoopOS
Code:
fastboot format userdata
Code:
fastboot format cache
Now install twrp using any method you know. Get the imgs here.
Yeah I lied it wasn't hard but just tricky. Enjoy!
Credit:
@Heisenberg
@Tigerstown
Click to expand...
Click to collapse
Dude you saved my ass. My phone would not show correct battery % reading and I decided to drain it completely. Then my phone got stuck in bootloop and recovery stuck on splash screen. I am really lucky I found out your post.
Tysm.
Stock kernels with the "forceencrypt" flag changed to "encryptable".
These are "IMG" files that need to be flashed with fastboot.
(Oct) N6F27M-noencrypt-boot.img - https://mega.nz/#!e4AmQJTa!-b9VEDCUHMa2YedScgHpSpStmKfhVWQMFWQf93L0OCU
(Oct) NGI77B-noencrypt-boot.img - https://mega.nz/#!XsBR0QBb!nkNQibCAT-IMpGH3pPVKLmHsGzE90JQfBcDzkWWwHEM
(Sept) NGI55D-noencrypt-boot.img - https://mega.nz/#!6sYSUbTb!dT-pBFhY4iJuHcqGWnRZiFvnUHLxVlNxrDDfgl0L_9w
(Aug) N6F27I-noencrypt-boot.img - https://mega.nz/#!atxQSZYK!y4H4uFt8pNW0szhUyWrp_QinytKIE3WhszAQMNJ4rO0
(Aug) N8I11B-noencrypt-boot.img - https://mega.nz/#!voxiWQqY!DtV5VWhRRLH3cvpxL37QJDFGMUjZU9uubBP8NuADG0k
Hi, and which one is to use? Are these carrier specific versions?
day242 said:
Hi, and which one is to use? Are these carrier specific versions?
Click to expand...
Click to collapse
Sounds like the N8I11B build has some Verizon specific code. After reviewing, it appears they devs used the same kernel in both builds, so it should not matter which is flashed.
Lose data?
Can these be flashed without losing data?
My Nexus 6 is currently not encrypted and I'd like to keep it that way, but don't want to have to reinstall all my apps and files. Again.
Thanks.
TheTomahawk said:
Can these be flashed without losing data?
My Nexus 6 is currently not encrypted and I'd like to keep it that way, but don't want to have to reinstall all my apps and files. Again.
Thanks.
Click to expand...
Click to collapse
You can update your phone and stay un-encrypted by flashing the latest "system.img", "cache.img", and the appropriate "noencrypt-boot.img" from the OP. (This is how I update each release and maintain the exisiting data)
Re: lose data
jbaumert said:
You can update your phone and stay un-encrypted by flashing the latest "system.img", "cache.img", and the appropriate "noencrypt-boot.img" from the OP. (This is how I update each release any maintain the exisiting data)
Click to expand...
Click to collapse
Cool. Em, could you provide instructions, please?
Tnx
TheTomahawk said:
Cool. Em, could you provide instructions, please?
Tnx
Click to expand...
Click to collapse
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
jbaumert said:
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
Much obliged.
im assuming one of these brings back ota? probably N6F27I
guessing one is official ota from 7.0 to 7.1.1
hello. can anyone please explain to me how do i get rid of encryption if i'm on lineage os? i am trying for hours now but every time my phone boots it is still encrypted. what i'm doing is i flash this modified boot.img through fastboot, then format userdata through fastboot, then go into recovery and wipe everything possible and then i flash latest los build from usb-otg. reboot and it's still encrypted :|
dudikaz said:
hello. can anyone please explain to me how do i get rid of encryption if i'm on lineage os? i am trying for hours now but every time my phone boots it is still encrypted. what i'm doing is i flash this modified boot.img through fastboot, then format userdata through fastboot, then go into recovery and wipe everything possible and then i flash latest los build from usb-otg. reboot and it's still encrypted :|
Click to expand...
Click to collapse
After flashing LOS and before booting the first time is when you need to flash a non-encrypted kernel. Flashing the boot.img before isn't doing any good as it's overwritten by the LOS install....
jbaumert said:
After flashing LOS and before booting the first time is when you need to flash a non-encrypted kernel. Flashing the boot.img before isn't doing any good as it's overwritten by the LOS install....
Click to expand...
Click to collapse
if i flash it after los it gets stuck on google logo and doesn't boot at all :/
---------- Post added at 01:08 AM ---------- Previous post was at 12:36 AM ----------
ok so now i've went back to stock N8I11B which is force encrypted. could you tell me exactly what steps should i take to make it not encrypted please? also what about the franco kernel does it get rid of encryption as well maybe?
If your flashing stock via fastboot, then you just need to replace the boot.img with the non-encrypted. That said, you will need to erase "userdata" also and start fresh. (Once user data is encrypted, it can't be "un-done" it's a start from scratch)
As for LOS, I've never used it with the stock kernel, but it sounds like its not compatible. Franco should work fine and is also not force-encrypt.
jbaumert said:
If your flashing stock via fastboot, then you just need to replace the boot.img with the non-encrypted. That said, you will need to erase "userdata" also and start fresh. (Once user data is encrypted, it can't be "un-done" it's a start from scratch)
As for LOS, I've never used it with the stock kernel, but it sounds like its not compatible. Franco should work fine and is also not force-encrypt.
Click to expand...
Click to collapse
it's really confusing as this is what it says in the official los thread here on xda - "Current lineage 14.1 shamu nightlies are based on the N8I11B August 2017 update from google. So you should be using the radio and bootloader img from that update. " also how do i erase this userdata properly? "fastboot format userdata"? i think last time i did it my device didn't boot at all afterwards. going to try it again now.
Added September 2017 "no encrypt" boot.img to OP
Added October 2017 "no encrypt" boot.img to OP
thumbs up !!!
i was looking all over for the latest img. really grateful for your work. thanks a lot
Thank you very much
jbaumert said:
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
Would we want to change the name of noencrypt-boot.img to boot.img before flashing or leave as is? Also can we make a backup in TWRP of our userdata and just restore after flashing as long as it's before booting the phone?
Jeffro64 said:
Would we want to change the name of noencrypt-boot.img to boot.img before flashing or leave as is? Also, can we make a backup in TWRP of our userdata and just restore after flashing as long as it's before booting the phone?
Click to expand...
Click to collapse
You can leave the name of the file (unless you just want to type in a short command with fastboot). As for the backup of "userdata", if you are updating the phone from one stock version to another and following the instructions you quoted, there is no need to backup. Coming from another ROM you would want to wipe and then yes, a backup is a good idea (needed).