Well, here we go again, I ran into a problem. I had a Freedom OS backup, and I decided to try LineageOS. After that, I flashed a kernel to allow for permissive selinux. After I booted it up, it was factory reset. I didn't have time to deal with the setup again, so I restored my backup, but that bootlooped. I flashed the same ROM again after a factory reset, got stuck at the Oneplus screen. I flashed Resurrection, that booted up. Then I rebooted to recovery, flashed VIPER, factory reset. Without warning. No dialog, no nothing, it just resets itself without telling me about it. And then it requires my pattern when I enter TWRP, it asks for it when I'm trying to boot my phone, and it's annoying. VERY ANNOYING.
I want encryption off. I don't want it not to ask for my pattern. I want it OFF. Is that possible?
I would also like to know why it factory resets EVERY SINGLE TIME I flash something.
Related
Last night I power cycled my phone and put it on my charger. When I woke up this morning and looked at my phone there were a ton of force close screens. I have no phone (cannot make calls) and not data.
I power cycled the phone over and over and have been searching the net all day but cannot get it to work. The only thing that I had done prior to the initial power cycle was a few updates from the market, so I uninstalled those apps, but it appears that was not the problem.
I have root access and was running gumbo's rom (now MaDoCo...thought that would help) and I really don't wanna do a factory reset. Is there anything I can do?
Factory reset is most likely gonna be your only option. If you dont wanna do that, do you still have the .zip for your rom on your mem card? If so, why not just reflash the zip? Might take care of the issue without having to do a hard reset. I am assumingm, though, that if you are rooted you would have created a nandroid backup? Why not just restore?
Tried reflashing the rom and that didn't work. Gonna do a Factory reset now. Lets see
tried factory reset and now i'm stuck on boot screen
Did you ever make a Nandroid backup?? I would suggest you run the Sprint RUU and bring your phone back to Stock, reroot, install recovery, and then a custom ROM. That looks like your best option.
But, just for the hell of it -- take out of your battery and then insert it back in and reboot, see if that does anything.
What kind of factory reset did you do? Wipe from recovery, go through setting, the home>back>power one, or what? And are you stuck at the HTC screen? That happened to me once, but it was because I flashed a GSM rom my first try. Boot into recovery, wipe the phone, and if that doenst do it, I agree with pseodo, time to RUU.
Well I tried resetting from the recovery and wiping, but it will not boot up. Then I tried the RUU, but it wont get past the boot screen in order for me to to connect it to the USB. I tried connecting the USB through recovery and although I can access my SD card via my PC, going through the steps for the RUU says its not connected.
I took my phone over to sprint and although they know I have a custom rom on there (which voided my warranty), they are still gonna give me a brand new one and send mine back through manufacture warranty. It'll be in on Tuesday. Luckily for me I have an online back up through by MyBackUpPro, so I should be good on restoring settings, apps, contacts and all other important stuff. (Minus Root and Custom Rom )
Thanks for all the suggestions, I appreciate it.
I flashed a new set of icons last week and had a bunch of force closes, restored a nandroid and everything was fine.
Hi,
I've got XT1068, updated to 6.0 Marshmallow. In the past, I got it FDE (full disk encrypted).
Few days ago I unlocked my bootloader to gain root access on my phone using http://forum.xda-developers.com/moto-g-2014/general/simplified-modifying-boot-img-t3317605
everything went as expected, but by unlocking it wiped all userdata, so I wanted to re-encrypt the phone (and the external SD especially). But now, encryption fails, telling me "encryption fails, you have to reset your phone" each time I start the encryption, ending in a userdata-wipe.
So I thought about going back to stock fw.
After locking the bootloader and applying stock 6.0 FW, I tried again to encrypt the phone, but I am still unable to do so.
Can someone help me giving some suggestions, how I can fix that behavior and (mainly) how to get some errors/debug shown?
When selecting "encrypt now", the green android symbol with black background is shown for 5seconds, then the phone reboots, shows the bootscreen with the M, then it restarts again (after ~30minute) and shows after another 20seconds the message that something went wrong encrypting.
Ok it seems that I found out the problem in my case by myself.
Instead of using mfastboot.exe -w to delete the data and cache partition, I used recovery mode to delete userdata. I did it twice, since the first run, returns some errors.
After reset, I started the phone and got the fresh-install screen. I skipped mobile and wifi networking and did not entered google account details. Then I restarted the phone and waited for ~5minutes and tried to encrypt - everything works. Everytime I started encryption without waiting for some time it failed.
I hope I can save someone else some time, since factory reset takes ~15minutes each time you do it.
Phone: Mi 5 64gb
This is crazy guys, after I flashed LOS, I wasn't able to connect to the wifi and whenever I do, the phone causes to reset and ruin the Internet for every temporarily. I thought it was just this phone so I went to shop and switched for a new one. And as soon as I flashed RR, guess what? Same thing happens. I'm so lost, what did I do wrong? These are the steps I took to flash custom ROMs. First, I unlocked bootloader and flash TWRP 3.0xx recovery. Next, I factory reset, wipe cache system data everything and flashed firmware, then ROM, finally the Gapps. I tried to flash back to official ROMs, the problem remained. I'm so screwed, don't know if the shop gonna let me switch to a new one, again.
P.S. on the bright side, I can mess with other's Wifi, make them unusable.
P.S. 2 during zip installing in TWRP, I saw two red lines like this "E:unknown command [log], detected filesystem ext4 for /dev/block/bootdevice/by-name/system, script succeeded: result was [1.000000]..." but it said done regardless
When I tried reinstalling Stable OxygenOS 4.1.6, the phone locks up upon install and setup screen. This goes for previous OS versions, as well. It takes force quits, restarts, and numerous install attempts and the phone still locks up. I tried stock recovery, old and new TWRP versions, all of which are clean installs, Nothing. LineageOS and other Hydrogen based roms still lock up, either at the setup screen, or when I try and activate developer options. Every Rom I tried after activating developer options, it doesn't leave the gear icon in the menu, either. It takes a restart (force quit) for it to show up. Also, WiFi doesn't work. Sometimes when I try and install OxygenOS either by sideloading, or through TWRP, the phone locks up at the wifi setup screen. This goes for every version of OxygenOS I tried. Your advice is appreciated. Thanks.
I had some problems last night while switching back and forth between Beta and stable. I could try to help but I'm not a guru at this, so wait for confirmation if you are not sure.
First I think you need the right TWRP version. 3.1.1-2 is the latest one, but I'm using 3.0.4-1 (flashed stableOOS with it) and everything is back to normal for me.
Try a clean flash of stableOOS. TWRP > Advanced wipe, select dalvik,cache,data,system and swipe.
Then install the OS. Don't reboot yet, and instead boot into recovery after going back. I read that this ensures you keep TWRP.
It may say No OS installed, but go ahead. Then boot into system again. This worked for me and I restored my backups
I just went from beta 10 to 4.1.6 and have no issues at all.
I followed the basic procedure, in TWRP (recommend to use the latest bluesparks one from his kernel thread - just TWRP no need for his kernel), I did a factory reset, (in TWRP just swipe to Factory reset from the WIPE screen where it says 'Most of the time this is all you need'), its correct nothing else needed, then flashed the full v416 file, then flashed Magisk 13.2, rebooted to system, that was all. TWRP was not lost with this method.
System booted to stable v4.1.6 and no issues.
Check what format are your partitions fornatted in. Make sure they are f2fs. Otherwise try the debrick tutorial. It helped me fix a lot of bugs on my 3T.
I tried all of the above, and I'm certain under the right circumstances, your advice would work. In the end, I used the unbrick tool which brought it back to it's original locked state, and I'm still running into issues. I wonder if there's a hardware issue somewhere that was the result of using Beta. The OS boots up and I'm finally able to access developer options, but no WiFi and the phone still refuses to restart or power off unless I do a hard shutdown. I've never seen anything like it. Numerous ROMS, recoveries, and sideload installs using the One Plus Recovery, and it still doesn't work.
Thanks for everyone's input, but I feel like this phone is done.
Trying to give the mother in law my old N6. It was rooted / bootloader unlocked. First attempt was to factory reset from within the OS. That worked fine, until I rebooted... it wouldn't boot.
I then downloaded the Shamu factory images from Google's website (shamu-n6f27m-factory-bf5cce08) and ran the flash-all.bat script. Multiple errors showed up during the script... but I chalked it up to ADB looking for boot slots etc, whereas this one has none.
Phone booted fine. Installed apps, set up the phone, power cycled it and promptly entered a bootloop.
Ran flash.all again, phone booted fine. Flashed TWRP, booted into recovery, checked things out in there (didn't do anything but flash the TWRP) tried to reboot, phone bootloops.
Flashed TWRP, booted into Recovery, tried to erase system, etc.... multiple errors again. Booted into bootloader, ran Flash-all... phone boots. Installed some apps, rebooted phone and bootloop again.
Then I did something REALLY stupid, I locked the bootloader from ADB. Now I'm on the bootloader, but can't OEM unlock because it's asking me to boot into the OS and enable the ability from Developer options.
I've no idea why this phone is doing this - booting fine into the OS once and then getting into a bootloop every time thereafter.
If anyone can shed some light on this, I'd appreciate it. Also, how in the hell do I unlock the bootloader now that I've locked it and I can't boot into the OS or run the Flash-all.bat anymore since it's locked?
Is your recovery stock? If it is, sideload the last OTA from Google and that should get you back into Android so you can toggle the OEM Unlock button.
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
usafle said:
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
Click to expand...
Click to collapse
So did you finally figure out what it could have been that you were doing wrong?
Strephon Alkhalikoi said:
So did you finally figure out what it could have been that you were doing wrong?
Click to expand...
Click to collapse
No. I could only assume I had messed something up when I was using it back in the day and really hosed something up. System wouldn't wipe, cache wouldn't wipe, userdata wouldn't wipe in "fasboot" just kept getting "unable to find XXXX".
So multiple flashes into TWRP and bootloops trying to really REALLY wipe the device finally fixed it. I just kept erasing / wiping every partition I could find in Stock Recovery, TWRP, and with fastboot commands. Finally I got them all wiped/cleared and was able to flash the stock OS back on and have it 'stick'.