Related
I recently bought a used Nexus 6 in mint condition, but I noticed after a factory reset in TWRP that I still see old install folders and even some of the previous owner pics and docs.
How do I do a proper wipe without missing something up like the rom itself? What settings in TWRP should I use without killing the rom.
Thanks in advance
rsalas187 said:
I recently bought a used Nexus 6 in mint condition, but I noticed after a factory reset in TWRP that I still see old install folders and even some of the previous owner pics and docs.
How do I do a proper wipe without missing something up like the rom itself? What settings in TWRP should I use without killing the rom.
Thanks in advance
Click to expand...
Click to collapse
Do a data factory reset in /settings/backup and restore/factory reset/. Backup first off course, this will wipe the device.
gee2012 said:
Do a data factory reset in /settings/backup and restore/factory reset/. Backup first off course, this will wipe the device.
Click to expand...
Click to collapse
So don't even use the TWRP factory reset?
Format Data
Factory reset in twrp doesn't wipe sdcard. Also factory reset in settings uses recovery default which if twrp also, doesn't wipe sdcard.
In twrp go to wipe > advanced wipe > internal storage
rsalas187 said:
So don't even use the TWRP factory reset?
Click to expand...
Click to collapse
If you prefer that you can:
Wipe cache and dalvik cache, data factory reset and reboot. Also backup apps and files/pics etc first. Do not wipe system or sdcard!
gee2012 said:
If you prefer that you can:
Wipe cache and dalvik cache, data factory reset and reboot. Also backup apps and files/pics etc first. Do not wipe system or sdcard!
Click to expand...
Click to collapse
He wants to wipe sdcard...
rootSU said:
He wants to wipe sdcard...
Click to expand...
Click to collapse
Don't think so if I read the op right, at least don't hope so ?
Verstuurd vanaf mijn Nexus 6 met Tapatalk
gee2012 said:
Don't think so if I read the op right, at least don't hope so ?
Verstuurd vanaf mijn Nexus 6 met Tapatalk
Click to expand...
Click to collapse
Yeah he does. He wants to wipe all the pictures from previous owner on sdcard but can't because twrp doesn't do that unless he follows my instructions s
rootSU said:
Yeah he does. He wants to wipe all the pictures from previous owner on sdcard but can't because twrp doesn't do that unless he follows my instructions s
Click to expand...
Click to collapse
Oké, doesn't do data factory reset in settings do the same? Wipe user data.
Verstuurd vanaf mijn Nexus 6 met Tapatalk
gee2012 said:
Oké, doesn't do data factory reset in settings do the same? Wipe user data.
Verstuurd vanaf mijn Nexus 6 met Tapatalk
Click to expand...
Click to collapse
Twrp does not wipe sdcard. This is done on purpose to save sdcard for ROM flashers. It is no good wiping a device before flashing a ROM if the ROM you want to flash is wiped from sdcard.
Only stock ROM wipes sdcard with factory reset
Reset from settings uses recovery. So of stock recovery installed, using setting wipes sdcard. If twrp installed, using settings does not wipe sdcard.
rootSU said:
Twrp does not wipe sdcard. This is done on purpose to save sdcard for ROM flashers. It is no good wiping a device before flashing a ROM if the ROM you want to flash is wiped from sdcard.
Only stock ROM wipes sdcard with factory reset
Reset from settings uses recovery. So of stock recovery installed, using setting wipes sdcard. If twrp installed, using settings does not wipe sdcard.
Click to expand...
Click to collapse
Oké got it bro.
Verstuurd vanaf mijn Nexus 6 met Tapatalk
you can always wipe the sd storage with twrp, but you have to specificly choose your storage to be wiped.
Failure of Factory Reset
I bought a Nexus 6 today, and listen to the "father" tell me that his "son" placed TWRP for recovery and installed PureNexus ROM on the device. Of course, I figured that this wasn't and issue, and the first thing that I did was do a factory reset. I issued the reset and once I was in TWRP, I immediately received a fail. I did a fastboot to a newer version of TWRP, but still no joy.
I have tried advance wipe and still nothing. Is there any pointers on where I might find the answer to being able to do a factory reset.
kcallis said:
I bought a Nexus 6 today, and listen to the "father" tell me that his "son" placed TWRP for recovery and installed PureNexus ROM on the device. Of course, I figured that this wasn't and issue, and the first thing that I did was do a factory reset. I issued the reset and once I was in TWRP, I immediately received a fail. I did a fastboot to a newer version of TWRP, but still no joy.
I have tried advance wipe and still nothing. Is there any pointers on where I might find the answer to being able to do a factory reset.
Click to expand...
Click to collapse
Need some details here... First and foremost, what kind of fail are you talking about? Is there an error message?
(It's also interesting to know what kind of factory reset you did. The "normal" way in settings or in TWRP?)
Didgeridoohan said:
Need some details here... First and foremost, what kind of fail are you talking about? Is there an error message?
(It's also interesting to know what kind of factory reset you did. The "normal" way in settings or in TWRP?)
Click to expand...
Click to collapse
The first time I did a Factory Reset was via the Setting --> Backup & reset --> Factory data reset. At which time, TWRP kicked in and attempted the automatic Factory reset.
Code:
Updating partition details..
... done
Full SELinux support is present.
Simulating actions...
At the top was the following:
Code:
OpenRecoveryScript Complete
Failed
So I thought there might be an issue with the version I was running so I followed up with going into the bootloader and then:
Code:
fastboot flash recovery openrecovery-twrp-2.8.5.0-shamu.img
I even tried to fastboot oem unlock:
Code:
[email protected]:~/Downloads/Nexus 6$ fastboot oem unlock
...
(bootloader) Device state transition will erase userdata.
(bootloader) Are you sure you want to continue this transition?
(bootloader)
(bootloader) Press POWER key to continue.
(bootloader) Press VOL UP or VOL DOWN key to cancel state transition.
(bootloader) State transition confirmed!
(bootloader) Please select 'YES' on screen if you want to continue...
(bootloader) Unlocking bootloader...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 38.915s
I booted back into recovery and then tried to do a wipe. That one failed! I tried other partitions and still failed. So while the ROM seems to be working fine, I have not been able to do the factory reset and as such have not been able to first time boot where I could start the 1st time start so I could get the google cloud stuff downloaded to the device. I guess I could just go into Play and download stuff, but I would like to truly make this into my own device.
Sounds like the bootloader is locked. Go to settings in the ROM and tap on the build number seven times to expose Developer Options. Go to Developer Options and make sure "Enable OEM Unlock" is checked. Then try unlocking the bootloaded.
If you're successful, you can then replace TWRP with an updated version and go from there to customize the Nexus. This includes using TWRP to wipe the Nexus.
Didgeridoohan said:
Need some details here... First and foremost, what kind of fail are you talking about? Is there an error message?
(It's also interesting to know what kind of factory reset you did. The "normal" way in settings or in TWRP?)
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
Sounds like the bootloader is locked. Go to settings in the ROM and tap on the build number seven times to expose Developer Options. Go to Developer Options and make sure "Enable OEM Unlock" is checked. Then try unlocking the bootloaded.
If you're successful, you can then replace TWRP with an updated version and go from there to customize the Nexus. This includes using TWRP to wipe the Nexus.
Click to expand...
Click to collapse
It is already in Developer Mode and the OEM is unlocked. One of the first things that I checked...
kcallis said:
It is already in Developer Mode and the OEM is unlocked. One of the first things that I checked...
Click to expand...
Click to collapse
Try instead to flash a factory image. Might work and your device will be nice and clean.
And TWRP 2.8.5.0 is ancient (sort of). Latest is 3.0.2-0.
Didgeridoohan said:
Try instead to flash a factory image. Might work and your device will be nice and clean.
And TWRP 2.8.5.0 is ancient (sort of). Latest is 3.0.2-0.
Click to expand...
Click to collapse
That was the trick... 3.0.2 made the factory reset a breeze
So I was following this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684 and when it came to the step to allow modification in twrp I had already goofed up and kept it read only. How do I change this. I cannot find the setting anywhere in twrp???
CombustLemonz said:
So I was following this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684 and when it came to the step to allow modification in twrp I had already goofed up and kept it read only. How do I change this. I cannot find the setting anywhere in twrp???
Click to expand...
Click to collapse
Reflash TWRP.
Sent from my Droid Turbo.
Resurrection Remix.
Straight Talk/Verizon.
Tapatalk.
Reflashing did not work at first so I went to reboot and selected bootloader. It loaded up TWRP again and gave me the option! We are good! Thanks!
CombustLemonz said:
Reflashing did not work at first so I went to reboot and selected bootloader. It loaded up TWRP again and gave me the option! We are good! Thanks!
Click to expand...
Click to collapse
No problem señor!
Sent from my Droid Turbo.
Resurrection Remix.
Straight Talk/Verizon.
Tapatalk.
CombustLemonz said:
Reflashing did not work at first so I went to reboot and selected bootloader. It loaded up TWRP again and gave me the option! We are good! Thanks!
Click to expand...
Click to collapse
Could you please be more specific about how you got the option to reappear. I have the exact same issue. Thanks
Not sure if this will fix it or not... but I did the same thing when I first loaded twrp, I didnt allow system mods (or whatever it said) but in recovery if you go to Mount... theres a selection "Mount system partition read-only" that had a check and I unchecked it.
I am only assuming this corrects that issue... hopefully someone can come along and confirm.
jlang11 said:
Not sure if this will fix it or not... but I did the same thing when I first loaded twrp, I didnt allow system mods (or whatever it said) but in recovery if you go to Mount... theres a selection "Mount system partition read-only" that had a check and I unchecked it.
I am only assuming this corrects that issue... hopefully someone can come along and confirm.
Click to expand...
Click to collapse
I can confirm that unchecking that option solves this. I tried to flash a ROM update once and it gave me an error saying my system partition was read only, and after unchecking that option it flashed correctly.
The reason for having to run adb flash recovery.img (the TWRP custom recovery) is because you chose the read-only mode introduced in v2.8.7.0 of TWRP. It means that the stock recovery will overwrite it if you reboot without selecting keep modifications on that first screen. Tapping on the Keep Read Only button will keep it temporary, but swiping the blue arrows to the right (like I did in the video), will install TWRP permanently. Reference: http://www.androidexplained.com/oneplus-3-install-twrp/
Latiken said:
I can confirm that unchecking that option solves this. I tried to flash a ROM update once and it gave me an error saying my system partition was read only, and after unchecking that option it flashed correctly.
Click to expand...
Click to collapse
omg thank you so much, that was driving me mental.
can anyone confirm if this works? also, if i flash a new nightly via TWRP is CM going to overwrite the TWRP recovery? or I just have to wipe the cache and the update is done?
i91004ever said:
can anyone confirm if this works? also, if i flash a new nightly via TWRP is CM going to overwrite the TWRP recovery? or I just have to wipe the cache and the update is done?
Click to expand...
Click to collapse
It will overwrite TWRP if you have the developer option checkmark to use CM Recovery. Go into Settings/Developer Options and UNcheck that box.
Hi guys i have the twrp but i flashed a rom called cm13 on my galaxy s5 sm-g900p and i want to go back to touch wiz but the restore says at the twrp
"Cannot restore Modem -- mounted read only. What should i do also the "Mount system partition read-only" box was already unchecked
Wazup20 said:
Hi guys i have the twrp but i flashed a rom called cm13 on my galaxy s5 sm-g900p and i want to go back to touch wiz but the restore says at the twrp
"Cannot restore Modem -- mounted read only. What should i do also the "Mount system partition read-only" box was already unchecked
Click to expand...
Click to collapse
You should probably ask in the Galaxy S5 help section. That SM-G900p model is for Sprint.
Sprint Galaxy S 5 Q&A, Help & Troubleshooting
http://forum.xda-developers.com/sprint-galaxy-s5/help
Latiken said:
I can confirm that unchecking that option solves this. I tried to flash a ROM update once and it gave me an error saying my system partition was read only, and after unchecking that option it flashed correctly.
Click to expand...
Click to collapse
Confirmed ! :highfive:
zefir738 said:
Reflash TWRP.
Sent from my Droid Turbo.
Resurrection Remix.
Straight Talk/Verizon.
Tapatalk.
Click to expand...
Click to collapse
how can i reflash it again? i am having trouble with swipe to modification. swipe is not working i wiped data cache dalvik and system and the backup which i created is not restoring it says system--mounted read only. now i can neither boot to old OS nor the new OS is installing in my phone. im in great trouble please could you help me.
sizzlingsuraj said:
how can i reflash it again? i am having trouble with swipe to modification. swipe is not working i wiped data cache dalvik and system and the backup which i created is not restoring it says system--mounted read only. now i can neither boot to old OS nor the new OS is installing in my phone. im in great trouble please could you help me.
Click to expand...
Click to collapse
Either
how you flashed in the first place, probably fastboot via PC?
or if it's still in your download folder, go to TWRP "install" and check install "image". Flash it TWRP (reinstall) from there, boot to bootloader and then go back to "recovery".
I use the 2nd method all the time to update to newer versions of TWRP.
ChazzMatt said:
Either
how you flashed in the first place, probably fastboot via PC?
or if it's still in your download folder, go to TWRP "install" and check install "image". Flash it TWRP (reinstall) from there, boot to bootloader and then go back to "recovery".
I use the 2nd method all the time to update to newer versions of TWRP.
Click to expand...
Click to collapse
very important to do int hese order
fastboot flash recovery twrp-3.0.3-0-hammerhead.img
fastboot reboot-bootloader
enter the twrp
:good:
ironia. said:
very important to do int hese order
fastboot flash recovery twrp-3.0.3-0-hammerhead.img
fastboot reboot-bootloader
enter the twrp
:good:
Click to expand...
Click to collapse
That's basically what I said. But for this phone, you would want QUARK TWRP recovery – not hammerhead.
Latest QUARK TWRP:
https://www.androidfilehost.com/?w=files&flid=39562
(Use most recent date.)
yes, sorry for the wrong model
Ran into the same problem.
Made my device read only at the start up of TWRP by mistake.
Then I followed the advice by unticking the "mount system partition read only" option.
That's when the menu with the question came up again.
I swiped to the right to allow system modifications.
Rebooted into my phone.
Everything working fine phonewise.
Rebooted into bootloader.
Selected recovery.
Stock Recovery appears. :/
Any idea why stock recovery is returning despite having swiped right for allowing modifications on TWRP?
I am on stock rom, rooted with magisk, and I cannot seem to get this phone decrypted. Every time I try to format data in twrp, I get an error, and I get stuck in a bootloop to recovery. Is there a step(s) I am missing here? I've tried looking through the forum but all I've seen are the same instructions on formatting data.
Use Advanced Wipe, select all except sdcard. Then flash any custom rom you like. Flash Magisk too. Reboot. After reboot try running your custom rom os for a few. Then go back to twrp, do it again advanced wipe except sdcard. Reboot. See if it decrypt now.
Note: Make sure you backup everything in it first before doing so. Goodluck
Sent from my XT1805 using Tapatalk
jdesignz said:
Use Advanced Wipe, select all except sdcard. Then flash any custom rom you like. Flash Magisk too. Reboot. After reboot try running your custom rom os for a few. Then go back to twrp, do it again advanced wipe except sdcard. Reboot. See if it decrypt now.
Note: Make sure you backup everything in it first before doing so. Goodluck
Sent from my XT1805 using Tapatalk
Click to expand...
Click to collapse
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
L4ndon said:
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
Click to expand...
Click to collapse
UPDATE:
I tried to redo the process again, just to verify the process, and I am still having the same network issues. I have 3g every once in a while, but its iffy and I no longer have LTE.
L4ndon said:
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
Click to expand...
Click to collapse
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
IT WORKED! Thank you so much. This was the post I needed, it really helps when everything is put in a step by step format, I am not the best when it comes to this stuff, the only reason I wanted a custom rom was to be able to use wifi tether, being on sprint makes that hard. But now that i have the first step down hopefully everything else goes this smooth. Thank you so much again!
Well, as long as you have done backup with twrp you have nothing to worry about.
Sent from my XT1805 using Tapatalk
L4ndon said:
IT WORKED! Thank you so much. This was the post I needed, it really helps when everything is put in a step by step format, I am not the best when it comes to this stuff, the only reason I wanted a custom rom was to be able to use wifi tether, being on sprint makes that hard. But now that i have the first step down hopefully everything else goes this smooth. Thank you so much again!
Click to expand...
Click to collapse
Doing things the right way always works! Trouble is finding that right way (heed my warning about bad info in these threads - there is a lot of it - as you found out). Just so happens I also know how to splain things to users, I've done it for something like 25+ years (yeah, I am old - make that experienced). Tethering - used to be ya add a build.prop entry to allow it, but that was many years ago and most of not all enable it by default now.
Anyways, enjoy the ride. It may be a little bumpy, but it's the bumps that keep ya awake!
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
THX for that, got stuck in recovery process (loop).
I followed your instructions, but need of stock recovery.
My Path :
Backup DATA (w/o /media/)
Manually Backup Media with TWRP to Ext.SD
FORMAT /Data (use the DATA Button in TWRP), in my case it showed Errors, i ignored it and did it once again - this time it worked.
flashed Magisk
ended up in Recovery Loop - flashed stock recov. via FASTBOOT, reboot
a rainbow lightning circle turned up, said " DELETING", device rebooted by itself.
Now the Phone boots to Android, shut it down, restart with PWR BUTOON + VOL DOWN pressed to access bootloader and flash twrp again with FASTBOOT ( fastboot flash recovery nameoftheimage.img ENTER).
Now u can restore /DATA TWRP Backup and then the manually part - in my case that worked.
THX!
//EDIT
After first boot, i noticed missing write permissions for most Apps - so i decided to Reset SELinux via TWRP, worked !
te amo hice format data con r15 y al parecer se soluciono todo son lo maximo cauros
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
still sim not showing on my device which is xt1804
Never had the problem so can't help.
Hello guys ,
i am a newbie, i wanted to go for custom rom lineage os for op3t since i was fascinated by my friend's customisation.
i am in a stock rom with december patch 2017 updated.
i went to install twrp and headache started where i ended up decryption problem.
i havent set any password for twrp but it prompts for password. tried and tired of other bluesparks custom twrp also
before i go ahead with format/erase data (everything) i have a question can i able to decrypt mounted storage ??
none of the posts i found have clearly mentioned .. i tries updated twrp from webiste also but of nos usee
anybody's kind enough to explain procedures to be followed
Thx in advance
If TWRP requires you to insert a PW when you haven't one, try "default_password".
try the commands
fastboot format userdata
fastboot format cache
fastboot format system
fastboot erase boot
fastboot reboot
then reboot phone to recovery by pressing the volume keys and select recovery.
If you're able to boot into system, go to Settings > Security and set a password. You will be prompted then whether you want to use this password during boot, select Yes. This way TWRP should accept the password.
ersandeepkr said:
try the commands
fastboot format userdata
fastboot format cache
fastboot format system
fastboot erase boot
fastboot reboot
Click to expand...
Click to collapse
Your tip be like: destroy most partitions on the phone and reboot.
Why even erase boot? Never do this.
Anusha Rao said:
Hello guys ,
i am a newbie, i wanted to go for custom rom lineage os for op3t since i was fascinated by my friend's customisation.
i am in a stock rom with december patch 2017 updated.
i went to install twrp and headache started where i ended up decryption problem.
i havent set any password for twrp but it prompts for password. tried and tired of other bluesparks custom twrp also
before i go ahead with format/erase data (everything) i have a question can i able to decrypt mounted storage ??
none of the posts i found have clearly mentioned .. i tries updated twrp from webiste also but of nos usee
anybody's kind enough to explain procedures to be followed
Thx in advance
Click to expand...
Click to collapse
Password it ask for is the one you have set for lockscreen in last OS you used, just enter the same pin or password you used in last OS and it will decrypt
If default password doesn't work you need to wipe internal storage using above commands given by @ersandeepkr
Anusha Rao said:
Hello guys ,
i am a newbie, i wanted to go for custom rom lineage os for op3t since i was fascinated by my friend's customisation.
i am in a stock rom with december patch 2017 updated.
i went to install twrp and headache started where i ended up decryption problem.
i havent set any password for twrp but it prompts for password. tried and tired of other bluesparks custom twrp also
before i go ahead with format/erase data (everything) i have a question can i able to decrypt mounted storage ??
none of the posts i found have clearly mentioned .. i tries updated twrp from webiste also but of nos usee
anybody's kind enough to explain procedures to be followed
Thx in advance
Click to expand...
Click to collapse
I would definitely not wipe anything. I would first:
Set my password again (you can use the same one you are currently using) in Settings>Security>Screen lock and select the Require password to start option.
Then boot into TWRP and see if your password decrypts the data.
I would also only use either the latest official TWRP from https://dl.twrp.me/oneplus3/
Or the Blu Spark v8.61 TWRP from https://forum.xda-developers.com/on...vice-development/kernel-t3404970/post67463496
Sent from my OnePlus3T using XDA Labs
przemcio510 said:
If you're able to boot into system, go to Settings > Security and set a password. You will be prompted then whether you want to use this password during boot, select Yes. This way TWRP should accept the password.
Your tip be like: destroy most partitions on the phone and reboot.
Why even erase boot? Never do this.
Click to expand...
Click to collapse
I have used above commands without any problem.
The most dangerous command that will destroy your phone is
"fastboot erase bootloader"
and not the boot.
ersandeepkr said:
The most dangerous command that will destroy your phone is
"fastboot erase bootloader"
and not the boot.
Click to expand...
Click to collapse
Still you shouldn't provide such tips to other, espiecially those less skilled.
przemcio510 said:
Still you shouldn't provide such tips to other, espiecially those less skilled.
Click to expand...
Click to collapse
ok
After installing Nitrogen OS and gapps, I have restarted the phone and the following message appears:
Decryption unsuccessful, the password you entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have opportunity to restore any data that was backep up to your Google Account
I have formatted all the partitions, I have repaired them, I have reinstalled the operating system again and the same thing keeps appearing ...
TWRP is updated.
Help me! Thank's!
Jonny6921 said:
After installing Nitrogen OS and gapps, I have restarted the phone and the following message appears:
Decryption unsuccessful, the password you entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have opportunity to restore any data that was backep up to your Google Account
I have formatted all the partitions, I have repaired them, I have reinstalled the operating system again and the same thing keeps appearing ...
TWRP is updated.
Help me! Thank's!
Click to expand...
Click to collapse
Perhaps you should say which version of NitrogenOS you're using. Also asking in Nitrogen's thread has a higher chance of answers for your question.
I wonder if you think wipe is the same as format. That is not always the case. You need a real format of the data partition.
runekock said:
I wonder if you think wipe is the same as format. That is not always the case. You need a real format of the data partition.
Click to expand...
Click to collapse
Additionally TWRP's format function is broken.
Try "fastboot format userdata" if TWRP isn't properly formatting.
Elektroschmock said:
Additionally TWRP's format function is broken.
Click to expand...
Click to collapse
Can you elaborate on this?
I usually try to erase and format in fastboot anyway. But fastboot throws a can't format raw partition or something like that.
format (not wipe) data or use oreo builds
i've already done it
upgrade your twrp if it keeps failing, i'm using the latest release
Can someone help here? I followed all of the necessary steps to install LineageOS 16 on the Nexus 6 using TWRP and I am having this problem. I am not supremely skilled when it comes to these things, but I did it very carefully and made sure to read the instructions many times and go step by step as indicated. I was really looking forward to injecting new life into my N6, but now I basically have a brick.
Flaco05 said:
Can someone help here? I followed all of the necessary steps to install LineageOS 16 on the Nexus 6 using TWRP and I am having this problem. I am not supremely skilled when it comes to these things, but I did it very carefully and made sure to read the instructions many times and go step by step as indicated. I was really looking forward to injecting new life into my N6, but now I basically have a brick.
Click to expand...
Click to collapse
Without explaining what the problem is, it is hard to help you. Since you are using TWRP, you should have backup to restore.
Thank you for replying. I have the exact problem described by OP. And yes, I have a backup, so technically not bricked, you are right. Just very disappointed that following the flashing instructions let to this problem. Thank you again.
With great respect, I doubt that you actually followed the instructions as closely as you think. Unless your N6 has a hardware problem, the instructions will be correct - and I say this not knowing which instructions you followed, but any bad instructions are generally corrected pretty quickly.
To recap (and anyone please correct or amend anything for accuracy - I'll write this from memory):
- download TWRP 3.3.1 from https://twrp.me/motorola/motorolanexus6.html
- flash it in Bootloader - fastboot flash recovery twrp.img
- while you're there, format data - fastboot format userdata (you can also do this in TWRP, but as Elektroschmock says that TWRP formatting isn't perfect...)
- boot into recovery
- wipe everything - all partitions
- transfer your ROM & Gapps - and Magisk if you want root - to your device (recovery allows a direct connection to your PC)
- flash ROM, Gapps, Magisk
- reboot
- report back
Edit: One more thing just in case. If you get a "can't mount system" message, go back to TWRP main screen, Mount, and ensure that the "system read-only" checkbox is unchecked.
Hi, that is exactly what I did! I have repeated the process with LineageOS 15.1 (and the matching GApps) and it worked. Might this be an encryption problem related to LinerageOS 16? And thank you for responding.
Incidentally, what GApps package is the one most recommend? I used Open GApps Stock, but some of the Google Apps are acting up.
I use Opengapps Pico Arm (not Arm64).
All I can say is that I've installed LineageOS 16 on 2 N5s, 2 N4s and a Lenovo 8" tablet, all with no problems at all. Your problem is not device-specific, since the original query was not for an N6, and I myself know about this "corrupt" problem because I suffered from it myself a year or so ago on my own N6. The procedure I specified has always worked 100% for me every time.
Looking at the LineageOS 16 thread, there is a specific TWRP linked, and MindTheGapps is also linked which is different than openGapps.
If you haven't decrypted by FORMATING user data (not wiping), that may also be a problem.
Thanks, ktmom. The format was part of my instructions, and Flaco05 says he did exactly that. Normally I don't use fastboot to format - I just rely on TWRP and it's worked fine.
I've always used the standard Opengapps Pico and TWRP 3.3.1, no special versions, and they have always worked flawlessly - never any problems. Still, since Flaco05 is having problems, I guess he has nothing to lose by trying the recommended versions...
Thank you all. I will try some of these things tomorrow. I love this community!
dahawthorne said:
With great respect, I doubt that you actually followed the instructions as closely as you think. Unless your N6 has a hardware problem, the instructions will be correct - and I say this not knowing which instructions you followed, but any bad instructions are generally corrected pretty quickly.
To recap (and anyone please correct or amend anything for accuracy - I'll write this from memory):
- download TWRP 3.3.1 from https://twrp.me/motorola/motorolanexus6.html
- flash it in Bootloader - fastboot flash recovery twrp.img
- while you're there, format data - fastboot format userdata (you can also do this in TWRP, but as Elektroschmock says that TWRP formatting isn't perfect...)
- boot into recovery
- wipe everything - all partitions
- transfer your ROM & Gapps - and Magisk if you want root - to your device (recovery allows a direct connection to your PC)
- flash ROM, Gapps, Magisk
- reboot
- report back
Edit: One more thing just in case. If you get a "can't mount system" message, go back to TWRP main screen, Mount, and ensure that the "system read-only" checkbox is unchecked.
Click to expand...
Click to collapse
OK, I did all this, but have been stuck at the Google screen upon reboot for 30 minutes. Is this bad news, or this normal?
No, definitely not normal. A new ROM takes longer to boot but it's generally ten minutes maximum.
Have you tried flashing only the ROM & Gapps, without Magisk? Once you boot successfully you can then flash Magisk later. Try starting again from the top and see if that works.
(P.S. In a slow quiet thread, as this one is at the moment, there's no need to copy the entire post to which you're replying... )
Edit: No, sorry, not from the top. TWRP will still be there after formatting & wiping, so start at the third (format data) part.
Thank you. There is still some kind of a problem. After I finish flashing ROM and Gapps using the instructions, and then reboot (after wiping cache/davlik, right?), I get the Lineage OS logo in motion, and then finally boots into recovery (not system) again. Not sure what to do. Maybe try a different build? I am currently using the latest LineageOS 16 nightly.
Strange. Maybe try LineageOS 15.1?
I enjoy playing with bleeding-edge software, but when you can't get it to work at all then it sort of ruins the fun. A lot of people seem to prefer the stability of 15.1. Personally I never see much difference between even major versions. Maybe I'm just a bit unobservant...