Locked out after LineageOS update - Galaxy S6 Q&A, Help & Troubleshooting

Hi,
II have LineageOS 17.1 installed on my S6 920F. I received an update like every months and this time I tried to install it.
Few monts ago I did the same process witout issue but to day...
- After download by the OS I switch off it then reboot in TWRP 3.3.1-0.
- Nothing happened automaticaly, so I click Install, and reach /data/lineageos_updates and select the last .zip file
- Select signature verification and swipe to flash
- At the end, clean Dalvik cache and click reboot.
The phone had the black screen then the Samsung logo and stick at this screen. I could not switch off and had to wait until the battery drain out.
- After that I could restart it to the login screen but could not pass the pin, looping back to the login every time. No error message.
To try to fix that, back to the TWRP and I tried to flash an older .zip file. No luck.
So, now I an locked out at the login window. How to fix?
Thanks

Fortunately, I have a nandroid backup 4 days old. I restored it with TWRP and all is back working. I think I didn't lost anything important.
Next time I'll make a partial backup as well to find where is the issue when update.

Related

Stuck in a loop, need help

Hi all
I’m a complete noob at this and it seems like I have got myself into a bit of a pickle. Sorry for the massive description but I thought it would make it easier to get a good answer.
My Phone:
Samsung Galaxy S4 GT 19505 LTE
PDA I9505XXUEMK8
CSC I9505BTUEMK5
MODEM I9505XXUEMK8
I successfully rooted my phone using Odin. In Odin I added the "CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5" file to the PDA field then rebooted the device. Then I added the "openrecovery-twrp-2.6.3.1-jfltexx" file to the PDA field, rebooted the device and the phone automatically opened in TWRP recovery. In recovery mode I wiped the cache, system and dalvik cache. I then went to install, browsed to the "I9505 Official_Google_Edition_4.3_by_Jamal2367_Finaly_v2.0" file on my SD card, rebooted the device and the Google logo came up on the screen for a few minutes and all was good. Got my new ROM, ran a root checker and all was good.
After some research I decided I wanted to use the Pacman ROM as it seemed to a lot more customisable. Using the same method I went to TWRP recovery wiped the cache, system, and dalvik cache. I then went to Install, browsed for the pacman ROM and the Gapps file on my SD card and everything installed ok, the phone restarted and the pacman logo came up everything was fine. Although I did notice on start up that I got this message.(and have had this error message ever since)
kernel is not seandriod enforcing
set warranty bit : kernel
After using the Pacman ROM for a day I noticed a lot of bugs like my apps would disappear, I couldn't use my banking apps and my phone was generally performing very badly. So I decided to remove the ROM and use CyanogenMod ROM under the recommendation of a friend. So again I pressed home+power+vol up to enter recovery mode but this time it didn’t enter the TWRP recovery it entered the stock recovery mode. This was slightly concerning but I proceeded to use the list menu and cleared the cache etc, browsed the SD card and went to the CyanogenMod 10.2 ROM I previously downloaded. It began to install but in red I got the error message stating that I didn’t have the right permission or signature. The phone rebooted back to the Pacman ROM. I tried the above three times and it still continued to boot back into Pacman ROM sometimes I struggled to even get back into recovery mode.
Soooooo I decided to try and go back to the Google Edition 4.3 ROM and play it safe, using the method from my first paragraph. But when it installed through TWRP I got an error message saying cant find MD5 file. The device rebooted and the Google edition logo came up on the screen but it seems to be locked in a loop. The Google logo wont go away and the phone vibrates once then three times quickly every 10 seconds.
I can still enter both TWRP recover and Download Mode. But I don’t want to mess around with it anymore without getting some advice. Any help would be much appreciated as I really need my phone working.
Thanks again
Aiden
Did you create a backup while on your first run with google edition? If so wipe cache, system, and dalvik and restore to your backup. Should put you back to where you began.
Sent from my LGMS769 using XDA Premium 4 mobile app
I know I should, but I didnt. Is it still fixable ?
*Update*
Couldnt help myself had to have a tinker around. Managed to get Cyanogenmod 10 working with Gapps. Gonna see how I get on with this. Although still would like to know I have been having all these problems.
Sometimes things just dont go as planned: p I have easily soft bricked my phone around 10 times and always able to fix it. You really should have made a stock backup before flashing anything. I recommend doing it now so you at least have a known working configuation backed up for future use. Trust me backups are your friends!
Sent from my LGMS769 using XDA Premium 4 mobile app
Thanks for your replies.
Ye gonna that right now Cyan Mod so far is running very smooth without any problems.
Regards
Aiden

OTA Update Problem

Hi Community ,
Today one of my friends bought me the Alcatel Onetouch Idol 3 the 4.7 version Single SIM 8GB, Contract-free from Germany. During the first boot he was instructed to install the new firmware updates, everything went fine "I guess" until the phone restarted, he told me that the recovery mode screen appeared, but frankly i think that he got this screen by accident maybe he was pressing the power key and the volume up key while the phone was restarting who knows, anyways he selected Reboot system now from the menu, and when the phone starts up, no notifications were found and nothing says that the system was updated successfully.
So after all of this he checked the system firmware version, And it was 5.0.2-010 05,and a message saying new updates are available appeared. He proceeded the installation of this update, And everything went fine this time and he system is now 5.0.2-010 07.
So is it normal or the android system will be corrupted, The fact that i have the 5.0.2-010 07, does it mean that all the previous updates are applied correctly to the system ?
How can i please remove all the firmware updates and remove any changes so i can reinstall the system updates properly ?
P.S: I'm an android noob don't be harsh to me please
Hello and welcome to the comunity.
If everything works as it should be, that means the update was succesfull. Sometimes OTA updates are a small files about 50MB which only fixes some bugs, and thats why you dont need to see "android is upgrading" in the boot and also sometimes the OTA reboots the phone to recovery to be able to flash system files correctly.
So when you have 010.07 that means the update was successfull. If you maybe encounter some problems, just do factory reset the phone (you will lost all installed apps, sms, call log, but no photos and music).
DallasCZ said:
Hello and welcome to the comunity.
If everything works as it should be, that means the update was succesfull. Sometimes OTA updates are a small files about 50MB which only fixes some bugs, and thats why you dont need to see "android is upgrading" in the boot and also sometimes the OTA reboots the phone to recovery to be able to flash system files correctly.
So when you have 010.07 that means the update was successfull. If you maybe encounter some problems, just do factory reset the phone (you will lost all installed apps, sms, call log, but no photos and music).
Click to expand...
Click to collapse
Thanks a lot for the reply, So when the OTA reboot to recovery, choosing reboot system now from the recovery menu was the right choice ?
i think when the OTA has to reboot to recovery then there you should see some instalation progress which should end with automatic reboot. But anyway, when all works as it should dont bother with it.
DallasCZ said:
i think when the OTA has to reboot to recovery then there you should see some instalation progress which should end with automatic reboot. But anyway, when all works as it should dont bother with it.
Click to expand...
Click to collapse
I saw the installation progress only in the second update, in the first update the phone rebooted into recovery mode in which there is a static menu that i don't really remember the choices.
but yeah, anyways thanks
i am on custom rom, so i don't know how exactly the updates work. I am waiting to next update to android 6.0, but it will come not before march as i have i formations (more likely in summer )

April 2016 CM13 update - soft brick - Google Play lockscreen error

Hi - My OnePlus One is the one I purchased from OnePlus One - with all the over the air upgrades.
The most recent was the April 2016 CM13 marshmallow upgrade - but this causes a permanent Google Play Services error - which freezes the screen (soft brick) - right after any reboot.
I'm considering doing a factory reset - (I understand that the process is to hold the volume button down while rebooting?) - but I wanted to check if there were other, better options for fixing this?
Thanks!
I am having the same issue..
after every boot up it gets stucked at lockscreen and doesnt allow me to do anything.... after 2-3 minutes gets automatically restarted..
Please Help
So, i own an OPO, stock, running COS 13 ( received update a few days ago). No ROOT, no Bootloader unlocked.
Today, early in the morning (My local time) I restarted my OPO because my Google Fit was not able to record my activity. After the reboot, i tried to unlock my phone, but it got STUCK. Freeze if you will.
I tried from Cyanogen Recovery to Wipe Cache, it did not worked.
I tried from Cyanogen Recovery to Wipe Data, it did not worked.
i do not the reason for wipping not working but i was scared. Because whenever a tried to boot into system, I was stuck at lockscreen
I tried to perform a wipe from adb, but adb shell was printing a "error closed". So i got scared .
I thought that i could fix my issue by performing a Wipe...
I Download the OPO toolkit. Put my device into fastboot, and unlocked my bootloader ( yes i void my warranty). After that, the toolkit installed the TWRP ( Custom Recovery ) with just one click.
Then i boot into recovery and perform a wipe. Phone was no longer stuck at lockscreen (actually i lost all data)
After that, my phone has been working great. (more than 12 hours from the issue)
Good luck mate.!
Hi all,
Having the same problem, I'm inquiring me about a way to fetch data from the devices. Is there any way to pull data from an encrypted device?
Also had the lockscreen error after the update.
I did:
Wipe Cache,Dalvik, System but not Data
Install Full Rom (COS 13)
Install SuperSU Beta
Reboot
wipe cache/dalvik/system, not data
Afterwards i could login but play services crashed every second. Then I allowed play services all rights again in privacy settings.
Rebooted and i could not get past lockscreen any more.
I restored my last backup, updated all apps, allowed all google apps without restrictions in privacy, cleared their caches.
Disabled lockscreen.
Restarted and updated as above but did not Install SuperSu beta directly.
System booted fine. Then I installed SuperSu beta again. Still no problems
Hope this helps or gives some hints on the cause.

Samsung Galaxy S6 Edge is not booting even after a factory reset

My Samsung Galaxy S6 Edge is not booting even after a factory reset
A mobile app. for Android was installed successfully and since then I’m only having issues with my Samsung mobile:
- Since the installation of both the Hockey & Mobile Banking apps, my mobile freezes during any regular action and after a few seconds the device auto-restarts itself intermittently; this happened during the weekend while in use;
- Sunday night I uninstalled both the Hockey & Mobile Banking apps and the phone continued to freeze and restart intermittently. I was able to boot in SAFE MODE.
- This morning after the phone was turned off and turned on, the phone is not loading; the boot is looping and unable to reach the menu. I’m able to boot in SAFE MODE.
- This morning I did a Factory Reset, when done I get the “welcome” screen and right thereafter, the mobile freezes, auto-restarts and the boot keep looping.
Any help would be highly appreciated.
Hey guys, any suggestions...? I tried last night restoring the OS using Samsung Smart Switch application and the process went just fine the first time and during the setup process the phone just restarted against and for stuck in bootloop again.
I did a second attempt but after the PC is don and the phone boots it gets stuck.
Sometimes after restoring stock firmware and you get a bootloop, you have to boot to stock recovery and factory reset then wipe cache partition.
I know you said you did that once before you posted, you did that before you used SmartSwitch. Have you tried factory reset since restoring with SmartSwitch?
Yes, I did with SS last night; I did it again this morning and after completing the 100% software download, it started updating the device and at 97% it stopped and got the message "FAILED".
now as we speak, I restarted it again and now it's at 66^ downloading the files.
How can I perform a clean install using SS...? or do I need ODIN...? I want to keep the mobile as original as possible.
If you can find your stock firmware, download it and flash it with Odin, it's more reliable.
Maybe a stupid question: Where can I find my stock firmware...?
My info:
PDAIX / CSCI2 / PHONE: PHH (XFA)
I found the Firmware on SAMMOBILE: https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G925F/XFA/download/G925FXXU4DPIX/108273/
Is this a stock Firmware and reliable source...?
Sammobile is a very reliable source, if that firmware is the newest one for your model number and country/region/carrier then you're good to go.
I did install Firmware corresponding to my phone (PDAIX / CSCI2 / PHONE: PHH (XFA)) using Odin, I can use the phone for like 2 or 3 minutes and then it freezes, restarts and gets into boot loop.
Any more drastic measurements to take...? Is there an online tool to test the hardware function(s)...?
After flashing stock firmware, have you tried booting to stock recovery then do the factory reset and wipe cache then reboot.
Yes, I did...!
In ODIN, do I load only the "AP"...?
In most situations, AP is all you need if the firmware is an all in one firmware file, if you have a 4 part firmware then you need to put each part in its corresponding tab/slot in Odin.
Sometimes you have to flash more than once to be successful.
My phone is running like a horse now...! No more intermittent restarts nor boot looping.
I just did a clean install of Android 7.
The clean install of Android 7 went fine and now it's working back again, was because I changed the "Reactivation Lock" to OFF; I think this helped.

Lost WiFi and other features after switching from Slot B to Slot A

I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
shagexpert said:
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
Click to expand...
Click to collapse
I had the same issue when I first got my 6 when I was playing around with the slots. Also my original TWRP install for some reason would crash and reboot whenever I plugged in the data cable while in TWRP. I ended up flashing back to stock OOS 5.1.5 through fastboot (used the flash-all command) and then reinstalled TWRP and everything has been working great since then.
MickyFoley said:
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
Click to expand...
Click to collapse
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
To be honest I didn't know they did the same thing (magisk and Super SU). I am curious now, what if I factory reset my phone and attempted to install Super SU instead of Magisk this time?
If I do a factory reset (let's say I want it just like it was out of the box and I format the data partition as well), will I need to root the phone again? I am asking because I don't know which part of the instructions I should ignore. I am sure TWRP will already be installed after the reset so I would only need to install the extra apps...
You don't have to format data. Just factory reset it. Then use "fastboot boot twrp.img", don't allow modifications, flash a kernel you want (if you want one - I really recommend ElementalX) and then the latest version of Magisk (16.4 BETA currently). Did so - all fine. And yes: Even Titanium Backup works without any issue with Magisk.
We had similar problems with TWRP on the Razer Phone when it was new. We solved the problem by using the TWRP boot image to flash the stock boot image and then flashing a TWRP zip. I just got the OnePlus 6 yesterday and haven't really messed with it yet but everything sounds the same to me so far.
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
shagexpert said:
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
Click to expand...
Click to collapse
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
shagexpert said:
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
Click to expand...
Click to collapse
When your phone booted straight into that mode with black screen and the led, then you bricked it. Same happened to me 2 days ago. The solution was to use the Msmtool from another thread and it worked great. Just follow the guide. But it will wipe your device. And you have to install oxygenos manually via "local upgrade". If you have a question, just ask
What I ended up doing was restoring from the backup I had. This was the "bad backup" without WiFi and broken finger print and facial recognition. After the restore, I did a normal wipe (not advanced). This reset the phone to factory settings. Once I configured WiFi and signed into my Google account, Google offered to recover from a cloud backup of my One Plus - I didn't know Google made these backups. It downloaded all the apps automatically. I don't know yet if I have sign into all of them all over again.
The bad back up saved my ass, I wasn't even planning on making it. I was just testing the backup feature. That's why you should always do a backup, even if the device isn't in ideal configuration.
shagexpert said:
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
Click to expand...
Click to collapse
I rooted my phone with Magisk and installed the 5.1.6 via OTA (and reroot via installed Magisk Manager). So no need to install TWRP so far.
Titanium Backup runs flawlessly with Magisk (already on my OP 3T and my OP 5).
So give Magisk a try, I never had such an easy and reliable update as the one from 5.1.5 to 5.1.6
Helium is a great alternative to titanium.

Categories

Resources