Hello,
I flashed TWRP-3.0.3-1 and the latest Resurrection Remix OS and gapps, went through set up process, no problems.
However, whenever I go to TWRP and then boot to System from there, it does a factory reset and I'm back at the Welcome screen (and also prompts me to log in to my Google account as a result of being factory reset).
How do I fix this?
Thanks in advance
Mr Mop said:
Hello,
I flashed TWRP-3.0.3-1 and the latest Resurrection Remix OS and gapps, went through set up process, no problems.
However, whenever I go to TWRP and then boot to System from there, it does a factory reset and I'm back at the Welcome screen (and also prompts me to log in to my Google account as a result of being factory reset).
How do I fix this?
Thanks in advance
Click to expand...
Click to collapse
use the recovery 3.0.4.0
Mr Mop said:
Hello,
I flashed TWRP-3.0.3-1 and the latest Resurrection Remix OS and gapps, went through set up process, no problems.
However, whenever I go to TWRP and then boot to System from there, it does a factory reset and I'm back at the Welcome screen (and also prompts me to log in to my Google account as a result of being factory reset).
How do I fix this?
Thanks in advance
Click to expand...
Click to collapse
I read through the RR thread and many people have mentioned formatting your data partition from f2fs to ext4 file system. This should solve your problem.
pooch11 said:
I read through the RR thread and many people have mentioned formatting your data partition from f2fs to ext4 file system. This should solve your problem.
Click to expand...
Click to collapse
Just tried that and it worked, thanks!
Related
Here's the whole story:
I was on an unofficial build of RR CM13, encrypted, using TWRP 3.0.2-1.
I wiped data, dalvik, cache, and flashed the newest Official RR 7.1.1 and open-gapps.
I boot into the new ROM and start setting stuff up.
I restore some apps' data using Titanium Backup, then reboot.
On reboot I'm greeted with the device setup screen
I reboot, wipe, reflash a bunch of times
A few times:
When I rebooted after using the system my PIN doesn't decrypt the system/data (booting into the system)
When I rebooted after using TWRP my PIN does decrypt (booting into the system)
At some point during this I try wiping everything from TWRP, but it freezes, goes black, and then the notification LED turns white. I hold the power button and boot back to TWRP.
Apparently wiping /data is the problem (everything else wipes just fine if I do them individually)
I boot back into the system, set it up, and do a full factory reset from there (after offloading my stuff from Internal Storage)
Back to TWRP, now no matter what I flash or restore, I don't end up booting into the system, only into TWRP
I've also tried TWRP 3.0.4-0 (which wouldn't decrypt my data), and I've reflash TWRP a few times.
How do I actually boot into my system? It's been 7 hours, and I'm losing my mind.
Deleted
Boot to your ROM through the power button...
Manually..
Just Passing By said:
Not sure if you've tried this yet, but considering you've already backed your phone up, I'd just recommend to start clean and use the unbricker tool.
Click to expand...
Click to collapse
Do what he said. You've already wiped your internal storage, so just start from scratch.
Just Passing By said:
Not sure if you've tried this yet, but considering you've already backed your phone up, I'd just recommend to start clean and use the unbricker tool.
Click to expand...
Click to collapse
Thanks, that worked, but now when I try to boot into recovery I get a black screen.
I was able to use the Toolkit to boot into TWRP and flash my ROM. Any ideas how to fix this?
RustySpackleford said:
Thanks, that worked, but now when I try to boot into recovery I get a black screen.
I was able to use the Toolkit to boot into TWRP and flash my ROM. Any ideas how to fix this?
Click to expand...
Click to collapse
flash twrp
adb push os zip
adb push su
flash all , if needed format data.
This is what I have done yesterday,
edit: If u brick I don't take any responsibility.
Deleted
TWRP has enormous potential and so does ADB try to use them.
First ensure TWRP is working, If it works you're 80℅ safe , then further do some XDA search as per your need. I am sure it will work again.
This is purely my experience since 6 years I am flashing .
uttam.ace said:
TWRP has enormous potential and so does ADB try to use them.
First ensure TWRP is working, If it works you're 80℅ safe , then further do some XDA search as per your need. I am sure it will work again.
This is purely my experience since 6 years I am flashing .
Click to expand...
Click to collapse
hi bro, i facing 'white led black screen' on my 3T, can you explain what should i do for fix this?
please.. :crying:
bluuquthug said:
hi bro, i facing 'white led black screen' on my 3T, can you explain what should i do for fix this?
please.. :crying:
Click to expand...
Click to collapse
Hi ! Do not worry try this
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
uttam.ace said:
Hi ! Do not worry try this
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
it cant bro, i tried using that unbrick tool but still facing same problem after i update or flashing ROM again.
or can you explain step by step to fix that? almost all ROM i tried but still happening, am i wrong?
bluuquthug said:
it cant bro, i tried using that unbrick tool but still facing same problem after i update or flashing ROM again.
or can you explain step by step to fix that? almost all ROM i tried but still happening, am i wrong?
Click to expand...
Click to collapse
Your TWRP is working right!
go to TWRP/ Advanced/ADB Sideload
type "adb sideload /path/to/rom.zip"
Mate, recommend using ADB Sideload on TWRP itself is the only viable option you have. OR if that doesn't work and you still have the PIN issues, you should definitely use the Unbrick Tool and get everything back to Stock, and then reflash everything
Note: Using the unbrick tool will cause it to relock bootloader, so you're gonna have to start over again.
Cheers!
Just wanted to update my EX kernel with the kernel manager app, it reboots to TWRP and than requires password.
I've never set a password to TWRP and my PIN doesn't work. It also happened to my brother's 3T, that's so weird.
I would like to know if there is any solution that doesn't include factory reset or re-flashing TWRP.
Thanks from advanced, Lidor.
Update:
I tried to disable the PIN when you boot up the device. Now TWRP doesn't even work. It just shows the logo...
Guess I will have to re-flash TWRP... Just tell me if I am right.
HeroPlane said:
Just wanted to update my EX kernel with the kernel manager app, it reboots to TWRP and than requires password.
I've never set a password to TWRP and my PIN doesn't work. It also happened to my brother's 3T, that's so weird.
I would like to know if there is any solution that doesn't include factory reset or re-flashing TWRP.
Thanks from advanced, Lidor.
Update:
I tried to disable the PIN when you boot up the device. Now TWRP doesn't even work. It just shows the logo...
Guess I will have to re-flash TWRP... Just tell me if I am right.
Click to expand...
Click to collapse
Hmm random encryption?
sakumaxp said:
Hmm random encryption?
Click to expand...
Click to collapse
I guess so.
My TWRP is just useless now.
HeroPlane said:
I guess so.
My TWRP is just useless now.
Click to expand...
Click to collapse
I guess factory reset and then start from scratch? IDK what else you can do
Try reflash twrp to yr phone.
If you are on oxygen os twrp will take time to load (without pin enabled) as OOS uses f2fs format which is relatively newer format and allegedly considered better than more traditional ext4 format
So if twrp logo shows after booting in recovery then wait for sometime (can take upto 10 min)
I tried to flash lineage iOS after wiping my resurrection ROM doing factory wipe and system data cache internal everything so I would start clean. When I flashed it said error 7 boot loader was out of date need to be updated. Tried to update my ROM but resurrection Remix has never done one update for my SMT713 . Re-flashed my twrp recovery backup with success but now will not boot into system. Will only boot to recovery. How do I fix this problem of not being able to boot into my system?
Same here...
Two solutions, either reflash TWRP with Odin or open up the terminal in TWRP and run the following:
dd if=/dev/zero of=/dev/block/platform/7824900.sdhci/by-name/misc count=1 bs=32
Then reboot
info from Reddit thread
Bmj09bj said:
I tried to flash lineage iOS after wiping my resurrection ROM doing factory wipe and system data cache internal everything so I would start clean. When I flashed it said error 7 boot loader was out of date need to be updated. Tried to update my ROM but resurrection Remix has never done one update for my SMT713 . Re-flashed my twrp recovery backup with success but now will not boot into system. Will only boot to recovery. How do I fix this problem of not being able to boot into my system?
Click to expand...
Click to collapse
CrashHouse said:
Same here...
Click to expand...
Click to collapse
Lineage OS requires boot loader NRD90M.T813XXU2BQD1 for versions from 4/26/17 forward. You can find the info in the thread at this link - https://forum.xda-developers.com/tab-s2/orig-development/rom-lineageos-14-1-t3543920/page34. Read post #338. You also need TWRP 3.1.0-1 flash Nougat updates. I suggest you read this thread thoroughly before doing anything. It has a lot of info on how to do the upgrades properly. https://forum.xda-developers.com/tab-s2/general/t813-nougat-official-update-t3592597
You can get by with just the boot loader files found here - https://drive.google.com/file/d/0B3i4Cdm8QYlLck5LU2dIRng2S2c/view.
Read, read, read before doing anything and you can't go wrong.
Thnx
Everything you said is good and true, but not really helpful for the immediate issue in the thread. The reboot recovery loop is acknowledged by the TRWP thread OP as a known bug along with the reflashing of recovery as a fix.
Psiuyo said:
Everything you said is good and true, but not really helpful for the immediate issue in the thread. The reboot recovery loop is acknowledged by the TRWP thread OP as a known bug along with the reflashing of recovery as a fix.
Click to expand...
Click to collapse
It is helpful if it keeps him from making the same dumb mistake. The problem all began when he flashed the latest Lineage without having the proper version bootloader. Although in my initial post I used the numbers for the T813, it is JUST AS APPLICABLE for the T713. Reflashing TWRP as a fix doesn't do squat for him if he tries to flash Lineage again without updating his bootloader or if he uses the wrong version TWRP. Just sayin'.
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...
Hi All,
Today, I unlocked bootloader and installed TWRP and took the backup of the existing MIUI and Installed Pixel OS. Phone is bootlooped now whenever i reboot it goes to TWRP
and all the data in the system is gone.
can somebody help me resolve this
Thanks in advance
Dharshan Parasu said:
Hi All,
Today, I unlocked bootloader and installed TWRP and took the backup of the existing MIUI and Installed Pixel OS. Phone is bootlooped now whenever i reboot it goes to TWRP
and all the data in the system is gone.
can somebody help me resolve this
Thanks in advance
Click to expand...
Click to collapse
Did you format data with "yes"? You must do it.
Hellera said:
Did you format data with "yes"? You must do it.
Click to expand...
Click to collapse
No, but cleared cache, is there any solution
Dharshan Parasu said:
Hi All,
Today, I unlocked bootloader and installed TWRP and took the backup of the existing MIUI and Installed Pixel OS. Phone is bootlooped now whenever i reboot it goes to TWRP
and all the data in the system is gone.
can somebody help me resolve this
Thanks in advance
Click to expand...
Click to collapse
Format data with yes, reinstall Pixel OS and boot into system.
Dharshan Parasu said:
No, but cleared cache, is there any solution
Click to expand...
Click to collapse
That is not enough, you MUST format data after installing a new rom to remove the old encryption.
With starting up the new installed rom, new encryption will be done again.
Elinx said:
That is not enough, you MUST format data after installing a new rom to remove the old encryption.
With starting up the new installed rom, new encryption will be done again.
Click to expand...
Click to collapse
Thanks it worked perfectly
Xavind said:
Format data with yes, reinstall Pixel OS and boot into system.
Click to expand...
Click to collapse
Thank you, Worked