Unlocked and rooted with encryption issue - X Style (Pure) Q&A, Help & Troubleshooting

hey all. I unlocked my boot loader and rooted my pure tonight and when I goto encrypt the device it fails to encrypt. I enter my password in the encryption settings menu and hit the Encrypt button and it shows the black screen with the android like normal for about 1-2 seconds then goes to the white screen that has the big blue mono M and says "powered by android". It then just sits on this screen and nothing happens.
I had the phone encrypted before unlocking and rooting and when I previously encrypted the phone it would have a black screen and say something about encrypting the phone. If I hold down the power button and reboot the phone it reboots fine so I don't think it even starts the encryption process.
Has anyone had luck encrypting with a unlocked/rooted pure?
I just did a factory reset via twrp and it still is not working.

wicked0ne said:
hey all. I unlocked my boot loader and rooted my pure tonight and when I goto encrypt the device it fails to encrypt. I enter my password in the encryption settings menu and hit the Encrypt button and it shows the black screen with the android like normal for about 1-2 seconds then goes to the white screen that has the big blue mono M and says "powered by android". It then just sits on this screen and nothing happens.
I had the phone encrypted before unlocking and rooting and when I previously encrypted the phone it would have a black screen and say something about encrypting the phone. If I hold down the power button and reboot the phone it reboots fine so I don't think it even starts the encryption process.
Has anyone had luck encrypting with a unlocked/rooted pure?
I just did a factory reset via twrp and it still is not working.
Click to expand...
Click to collapse
I unlocked bootloader and then encrypted. Have not rooted yet. Maybe you could unroot and encrypt, then root again?

I did a factory reset which removed root and still would not work. Thanks for the idea though!

I am having this exact same issue. Unlocked bootloader, flashed TWRP, and rooted.
I go to encrypt the phone, the Android guy appears for 1-2 seconds, then it gets stuck on the blue Motorola "M" logo. I left it this way for 7 hours before giving up.
On a MXPE with 64GB internal storage. No SIM or sdcard inserted. Performed a factory reset and immediately tried again, same result. Tried it again using adb logging, when it hangs on the "M" logo I get this:
Code:
E/Cryptfs ( 398): Bad magic for real block device /dev/block/bootdevice/by-name/metadata
D/Cryptfs ( 398): Just asked init to shut down class main
I/ServiceManager( 397): service '$WHATEVER_PROCESS_HERE' died
Followed by this, repeatedly forever:
Code:
I/ServiceManager( 8687): Waiting for service media.audio_flinger...
W/AudioSystem( 8687): AudioFlinger not published, waiting...
Ok, so I guess I'll stop the service:
Code:
am force-stop media.audio_flinger
That reports something about package manager isn't running. Probably because it shut everything down in order to start encrypting. So I restart, then right before I press the final "Encrypt" button I run the force-stop command. It appears to work, but after pressing the button the logcat is spitting out the same errors as before.
Huh, ok, so I'll just kill whatever processes are related to the audio flinger.
Code:
kill $PID_HERE
Tried it with a few different processes, each time restarting the whole encryption process before trying to kill a different process. Killing some would result in the screen going black. Under no circumstance did the encryption process move forward, if anything it made matters worse (I won't bother putting the logcat here).
Ok then, I'll try just doing the encryption using adb, so I run the command using su:
Code:
/system/bin/vdc cryptfs enablecrypto inplace PASSWORD
It returns without error, but nothing happens on the phone. Take a look at the logcat:
Code:
W/vdc ( 7808): type=1400 audit(0.0:14): avc: denied { read write } for uid=0 path="/dev/pts/2" dev="devpts" ino=5 scontext=u:r:vdc:s0 tcontext=u:object_r:devpts:s0 tclass=chr_file permissive=0
W/vdc ( 7808): type=1400 audit(0.0:15): avc: denied { read write } for uid=0 path="/dev/pts/2" dev="devpts" ino=5 scontext=u:r:vdc:s0 tcontext=u:object_r:devpts:s0 tclass=chr_file permissive=0
W/vdc ( 7808): type=1400 audit(0.0:16): avc: denied { read write } for uid=0 path="/dev/pts/2" dev="devpts" ino=5 scontext=u:r:vdc:s0 tcontext=u:object_r:devpts:s0 tclass=chr_file permissive=0
W/vdc ( 7808): type=1400 audit(0.0:17): avc: denied { read write } for uid=0 path="/dev/pts/2" dev="devpts" ino=5 scontext=u:r:vdc:s0 tcontext=u:object_r:devpts:s0 tclass=chr_file permissive=0
W/vdc ( 7808): type=1400 audit(0.0:18): avc: denied { read write } for uid=0 path="/dev/pts/1" dev="devpts" ino=4 scontext=u:r:vdc:s0 tcontext=u:object_r:devpts:s0 tclass=chr_file permissive=0
Ok... I'll try using TWRP to completely recreate the data partition (including internal storage). It fails with error "unknown MTP status 1". So I use TWRP to change the partition type of data to F2FS (it was already F2FS), and that appears to work just fine (did it remake it? no idea). Still no dice with encryption.
I've read online that perhaps the filesystem is overlapping the necessary 16KB at the end of the partition, so I try to run the command to check filesystem info (tune2fs) but it complains of a bad superblock. Frankly I have no idea how the data partition is being mounted. The "userdata" partition is /dev/block/mmcblk0p47 which has the total size equal to /dev/block/mmcblk0, even though there are a 46 other partitions on mmcblk0, each taking up their own space. An example is /dev/block/mmcblk0p46 (system) is about 6GB total. What the hell? How can 6GB + 62GB = 62GB? To add further confusion, it also mounts /sdcard using mmcblk0p47 (data) even though no sdcard is in the device. So I have no idea how this mystical mmcblk047 partition is working. Any insight on this would be very helpful.
A phone without encryption is useless to me. I am really hoping I can figure this out by October 13th, otherwise I'll have to return it .
UPDATE: Big shoutout to rOOb85 from Reddit (see this thread) for explaining a process that works. Apparently being rooted causes this. The solution is to do a FULL UNROOT within SuperSU (disabling superuser is not enough).

So it looks like the phone must be unrooted to encrypt. There is a way to unroot to encrypt, if the phone was rooted.
What about rooting a phone that is already encrypted?
My phone has unlocked bootloader. It is encrypted. It is not (yet) rooted. Can it be rooted? Or will the encrypted condition prevent that?

This tripped me up too, 'til I remember having experienced the same issue before using a pre-rooted ROM on some older phone.
I think you should be able to root a bootloader-unlocked encrypted phone just fine. The SuperSU flashable ZIP only applies itself to /system afaik. Root is kept if you reformat the data partition.

I've been reading something that interested me.
https://www.reddit.com/r/MotoX/comments/2kx2lv/how_do_you_encrypt_a_rooted_moto_x/
Specifically.
I had the same issue today. Booted into safe mode, then I was able to encrypt.
Press power button to get power off popup menu. Press and hold power off. You will get another popup offering to reboot in safe mode.
Safe mode worked. This uncomplicates my process of rooting, unrooting, encrypting, and having issues rerooting after encryption. This is also a crazy easy single step process for an issue that has given me months of headaches.
You shall be the first person ever that I have given gold to.
Thank you so much!
Click to expand...
Click to collapse
My question would be, how do you encrypt in safe mode after applying the safe mode option? Within Safe Mode or?
I enter my password in the encryption settings menu and hit the Encrypt button
Click to expand...
Click to collapse
And how would encryption effect flashing a new rom?

Related

Acer A200 Bricked - Can't Recover

Hello. I have an Acer Iconia Tab A200, and recently I tried a factory reset. However, due to my meddling with system files, it won't reset.
I've tried to do a hard reset (Power on, Volume+, Orientation lock switch) but it says the following:
Erasing Userdata...
Erasing Cache...
It then reboots, and does nothing. It hangs on the Acer logo.
When trying to go into recovery (Power On, Volume-), it says the following:
Erasing Cache before SD update...
SD update cmd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified fail ...
Now, I mentioned that I meddled with the System Files. Here is what I did:
1. Removed unwanted Vendor Apps
2. Removed the DEFAULT LAUNCHER <-- I think this plays a big part in this
3. Placed a CUSTOM LAUNCHER in the VENDOR APPS FILE
4. Did a FACTORY RESET
My brother is more techy than me, so he tried to fix it. However, he somehow re-locked the bootloader and even replaced the bootloader with a newer version.
I talked to Acer Support claiming it's system files corrupted itself, but they won't fix it unless I also pay to fix my cracked screen. I'm willing to do so, but hey, I'd like to see if I could save $120. I don't mind the cracked screen.
NOTES:
The Acer Iconia Tab A200, along with their other tablets, has a USB port. I can probably load stuff from there somehow, but not sure.
It is a 16GB model with a 32GB Class 10 MicroSD card in it.
Any ideas? All help is appreciated.
Vuciz said:
Hello. I have an Acer Iconia Tab A200, and recently I tried a factory reset. However, due to my meddling with system files, it won't reset.
I've tried to do a hard reset (Power on, Volume+, Orientation lock switch) but it says the following:
Erasing Userdata...
Erasing Cache...
It then reboots, and does nothing. It hangs on the Acer logo.
When trying to go into recovery (Power On, Volume-), it says the following:
Erasing Cache before SD update...
SD update cmd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified fail ...
Now, I mentioned that I meddled with the System Files. Here is what I did:
1. Removed unwanted Vendor Apps
2. Removed the DEFAULT LAUNCHER <-- I think this plays a big part in this
3. Placed a CUSTOM LAUNCHER in the VENDOR APPS FILE
4. Did a FACTORY RESET
My brother is more techy than me, so he tried to fix it. However, he somehow re-locked the bootloader and even replaced the bootloader with a newer version.
I talked to Acer Support claiming it's system files corrupted itself, but they won't fix it unless I also pay to fix my cracked screen. I'm willing to do so, but hey, I'd like to see if I could save $120. I don't mind the cracked screen.
NOTES:
The Acer Iconia Tab A200, along with their other tablets, has a USB port. I can probably load stuff from there somehow, but not sure.
It is a 16GB model with a 32GB Class 10 MicroSD card in it.
Any ideas? All help is appreciated.
Click to expand...
Click to collapse
Do you have access to any a200 Update roms? Sometimes, you can pull the update.zip from the rom, place it on your ext sd card, reboot holding Vol+ and PWR, and it might install.
MD
Moscow Desire said:
Do you have access to any a200 Update roms? Sometimes, you can pull the update.zip from the rom, place it on your ext sd card, reboot holding Vol+ and PWR, and it might install.
MD
Click to expand...
Click to collapse
I have searched for some A200 ROMs, but can't find any that work using that method. I'm open for ANY Acer A200 official ROM, then simply updating using OTA. I tried an Acer A200 Recovery Pack I found. It is the exact stock Honeycomb image, but it didn't go. It always says recovery verified fail. I cannot unlock the BootLoader either.
Stockimage flashable while having bricked /DATA Partition
Hi Vuciz,
do you still have the issue with your bricked A200 ?
I got the same problem with mine, the only solution was to send it to repair, it seems the storage controller chip has some bug which destroyed the /DATA partition unrecoverable.
if you need to revert your Tablet to an locked bootloader you have to download an StockRom and modify it by removing the partition check (called "assert") in the update script.
please send me an message if you need further assistance.
regards and good luck with your tab.
Nickbert said:
Hi Vuciz,
do you still have the issue with your bricked A200 ?
I got the same problem with mine, the only solution was to send it to repair, it seems the storage controller chip has some bug which destroyed the /DATA partition unrecoverable.
if you need to revert your Tablet to an locked bootloader you have to download an StockRom and modify it by removing the partition check (called "assert") in the update script.
please send me an message if you need further assistance.
regards and good luck with your tab.
Click to expand...
Click to collapse
Yes I do. However the screen is also cracked so they want me to pay for that. Which I'm unable to do at this time.
anything I do, fails
Vuciz said:
Yes I do. However the screen is also cracked so they want me to pay for that. Which I'm unable to do at this time.
Click to expand...
Click to collapse
I also have this tablet. I bought it for 20 bucks because the screen was cracked. replaced the screen and then found out that the bootloader was trashed. I've done almost everything I can think of to fix it. Used APX mode to get UID from ubuntu, tried to use that UID to get sbk, got the SBK and then tried using blackthunder's tool got connection failure, tried using babsector same thing, even went in ubuntu, with tablet in manual apx mode for all three and when I attempt to reflash the bootloader, all I get is that command failure message with a nvflash connection failed nv error 0x30011 message and when that happens in windows, the tablet disappears from device manager, and in ubuntu when I run nvflash with the sbk function --sbk XXXX and so on, I get the command sent failure message, and then when i rerun lsusb, the nvidia device that represents my tablet in apx mode that showed before is no longer listed unless i reboot the tablet in apx mode again. If i boot it normally, the acer logo appears and then goes to the little animation and then the iconia tab screen and thats it. I've tried attempting to flash the bootloader from that screen which i know probably wasn't going to work anyways. If anyone has any advice on something I've missed, or anything that could help, i'll all eyes. thanks in advance.
twanhines said:
I also have this tablet. I bought it for 20 bucks because the screen was cracked. replaced the screen and then found out that the bootloader was trashed. I've done almost everything I can think of to fix it. Used APX mode to get UID from ubuntu, tried to use that UID to get sbk, got the SBK and then tried using blackthunder's tool got connection failure, tried using babsector same thing, even went in ubuntu, with tablet in manual apx mode for all three and when I attempt to reflash the bootloader, all I get is that command failure message with a nvflash connection failed nv error 0x30011 message and when that happens in windows, the tablet disappears from device manager, and in ubuntu when I run nvflash with the sbk function --sbk XXXX and so on, I get the command sent failure message, and then when i rerun lsusb, the nvidia device that represents my tablet in apx mode that showed before is no longer listed unless i reboot the tablet in apx mode again. If i boot it normally, the acer logo appears and then goes to the little animation and then the iconia tab screen and thats it. I've tried attempting to flash the bootloader from that screen which i know probably wasn't going to work anyways. If anyone has any advice on something I've missed, or anything that could help, i'll all eyes. thanks in advance.
Click to expand...
Click to collapse
Just so you know, I was never able to resolve this issue.
Hello,
I search help for my Acer Iconia Tab A200.
During a flash with TWRP, it block and I have to set my A200 off using Power.
And then, my A200 don't work, don't vibrate.
I try :
Reset + Power : nothing, no vibration
Power + Vol- : nothing, no vibration
Power + Vol+ + switch : same result
Connected to PC : adb devices : nothing
All commands adb or fastboot : waiting for device
I don't know what to do...
where can I send my Acer tablet to fixed stuck on bootloader
hello I have an acer iconia 200 stuck bootloader cant find anyone to fix it. Acer wont touch it unless its under warrenty! my 90 day store warrenty has been way past! taken to 2 local computer tech both told me I needed to send it back to acer but I cant! so what can ido i or where can I send it?? anyones time and effort would greatly appreicated!!! thanx for your time

Stuck with "unsuccessful encryption" dialog, have not activated phone encryption!

Stuck with "unsuccessful encryption" dialog, have not activated phone encryption!
Received my OPT about 3 weeks ago.
Today, I cannot get past the SIM unlock dialog. With a successful PIN code, I see a dialog "encryption unsuccessful", some more text and at the bottom a button with "reset phone". However, nothing happens when I hit that button.
I did perform a factory reset in the recovery mode, but I still see the "encryption unsuccessful" dialog.
I never activated encryption of the phone in the first place.
The phone is un-rooted, no attempt was made to change that.
What is the best appoach now ?
I have the identical issue. Have raised a ticket but not heard back yet. Has yours been resolved?
But mine was rooted
I had the same result encrypting my phone.
I was rooted and lost everything.
I had the luxury of atill being able to boot into twrp to recover.
So the recovery was not effected by the screw up.
You maybe able to simply run through the root process to gain access to a recovery like twrp that is worth somehting to format the space back tp something you can use and reflash the Rom
ahgillett said:
I have the identical issue. Have raised a ticket but not heard back yet. Has yours been resolved?
Click to expand...
Click to collapse
Mine was addressed, I had my device replaced.

OP2 Powers ON Automatically into Recovery

Hello Fellows,
First I'd like to explain my situation in details.
my phone fell while i was walking on the street and it got some dirt on it, so ( foolishly ) I decided to clean it.... and yeah... i washed my phone like washing a dish... i like rinsed the phone in water and in other cleaning liquids for no more than 3 seconds it was all quick thingy... anyway after washing it.... i directly powered it ON and it powered but the screen was OFF ( so i decided to power it OFF, solder it and to remove any clues of water inside on the board or something... after that i used a hairdryer ( which is not recommended ) but i used it at a descent distance so that no harm would be caused to the board... as i was only subjecting air to let water if any existed to dry..
i put the phone in rise and kept it for 1 day... after 1 day i wanted to check out how stuff went.. so i powered it ON and the screen actually turned ON and the vibrator, even the hardware back-light lighted up perfectly but here's the problem I'm facing.
the phone only boots into TWRP 3.1.0.0 no matter what i do.. things i tried:
1- flashed some ROM, through TWRP
2- used "Fixed Contexts" in TWRP
3- Repair File System "System partition" through TWRP
4- used file manager inside TWRP and checked if the internal storage is working and indeed i can show all my files, through TWRP
5- also used the file manager to access "System" Partition and everything was there, through TWRP
6- change File System into EXT4 "System partition" through TWRP
7- Resize File System "System partition" through TWRP
8- Wiping all Partitions "Excluding the internal storage"
and NON WORKED..
note that whenever i attempt to flash a ROM the result shows successful with no errors ..
so whats the problem in here?
i have a guess but i need help in order to apply it.. i think the VOL- is pressed and stuck somehow Electrically on the board ( but no physically as i can press the volume down and hear its tap or whatever you call it.. i even managed to boot into fast-boot and it worked.
is there anyway i can disable the vol- button temporary to see if its causing the problem?
the only thing is i cant see my ROM booting... not even the boot animation showing... just the boot-loader and automatically it goes into the recovery
also i have kernel log attached below followed by the recovery log
EDIT: i also forgot to mention that my PC recognize the phone and i have access to my internal storage.. no problems with transfer speed as well
after tons of attempts and searching online and flashing stuff and blablabla... (i flashed every recovery image op2 support )
FINALLY
I found the solution my self, and everything is back to normal...
the phone was stuck at the early stage of the booting process and maybe couldn't find the boot image in order to boot up the android OS, so all i did was i plugged in the phone into the PC, i started everything in fastboot mode on phone and on PC then i just sent the following command to my phone.
Code:
fastboot continue
fastboot then(meaning after the command) wasnt able to recognize the phone anymore so i knew that its now trying to search for partitions other than recovery.. i waited like 10 seconds and booom it booted into the best ROM i've ever used ( and actually missed ) which is Official RR from our great maintainer "nicesoni_ash"
P.S: the vol- as i said was really stuck and i noticed it not working while on RR ROM, so i just clicked it many times and tried mixing vol+ with vol- .. after many many attempts vol- worked and i then rebooted to make sure if everything is back to normal and no recovery auto boots and indeed it smoothly booted up :laugh:
thanks a lot for all who tried to help out in here or on oneplus forums :highfive:
#back_to_resurrect_and_will_always_remix
Did you try reverting to stock ?
Try getting files from here..
https://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
I would consider it as bricked, after all attempts failed and go with the unbrick guide here on xda or oneplus forums, maybe this way it can be ressurected.
You probably have already backed up your data..
Damn, that hurts..
mithu.creative said:
Did you try reverting to stock ?
Try getting files from here..
https://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Click to expand...
Click to collapse
sorry for this late reply but yes i have tried flashing every ROM from stock to Custom ones even i flashed EVERY SINGLE RECOVERY IMAGE OUR PHONE SUPPORTS XD and non worked... first aid.. qualcomm toolkit... non...
hello bro, i updated a magisk module v4android and when i reboot, it boots up in twrp. and since then it keeps booting into twrp. So, i used fastboot continue and when it boot int the home i deleted that module.
but fastboot continue only works once. After that if i switch-off and switch-on the phone, it goes into twrp. it needs fastboot continue everytime.
please provide me a permanent solution. few other users are facing this too. plz reply i'm waiting.
Hey,
with the help of some others in a Discord server (thanks @thesanjayp#6251 on discord) i managed to find the issue. Appearantly there was a change in /dev/block/bootdevice/by-name/misc for some reason. There was a similar problem on the old LG Optimus G Pro which i owned, so i remembered this.
As I'm not sure if we can just wipe the partition or not, i got a working misc.img attached.
In any terminal (adb shell, twrp terminal or an terminal app in a rom) make sure you have su rights, and then execute the following command:
Code:
dd if=/path/to/misc.img of=/dev/block/bootdevice/by-name/misc
Make sure to adapt the path to the misc.img though to the location you saved it to.
The misc.img I used is attached to this post.
PS: Im not responsible for any broken phones if this didnt work for you.

Huawei Nova 3i software install failed

So here's what happened:
my phone's screen(huawei nova 3i) is destroyed. i left it for a year then decided to repair it. The phone has a password and unfortunately, i forgot its password(a pin type password). I tried factory resetting it through its bootloader by pressing volume up and down and the power button simultaneously and was greeted by this error saying "Software intall failed" and was forced to restart the phone. I tried using adb and boot my phone to its bootloader again and its showing that its updating and its on 5%. I tried adb devices and my phone was detected but when i command adb shell rm/data/system/gesture.key as mentioned in this article"https://www.tenorshare.com/unlock-android/unlock-huawei-phone-without-resetting.html" it says access denied. and my phone just turn off on its own over time. and just to add, my phone doesn't have a forgot password feature displayed in the pin/code area.
i hope someone can help me in this issue and i would be thankful to any response.
noobieintechnicality said:
So here's what happened:
my phone's screen(huawei nova 3i) is destroyed. i left it for a year then decided to repair it. The phone has a password and unfortunately, i forgot its password(a pin type password). I tried factory resetting it through its bootloader by pressing volume up and down and the power button simultaneously and was greeted by this error saying "Software intall failed" and was forced to restart the phone. I tried using adb and boot my phone to its bootloader again and its showing that its updating and its on 5%. I tried adb devices and my phone was detected but when i command adb shell rm/data/system/gesture.key as mentioned in this article"https://www.tenorshare.com/unlock-android/unlock-huawei-phone-without-resetting.html" it says access denied. and my phone just turn off on its own over time. and just to add, my phone doesn't have a forgot password feature displayed in the pin/code area.
i hope someone can help me in this issue and i would be thankful to any response.
Click to expand...
Click to collapse
Huawei Nova 2 Plus Bootloader Unlock (Solution)
Hello Developers! I have found an easy way to unlock the bootloader of our Huawei Nova 2 Plus. No need to use Testpoint or pay for software to unlock. it is an Python Script which would brute force the code through the IMEI number you have...
forum.xda-developers.com

Samsung A52s 5G stuck in reboot-freeze loop

Hi, I have a Samsung Galaxy A52s 5G that goes into the following loop for two days:
boots up, waits for me to unlock the phone through the draw pattern, I unlock the phone, "Phone Starting" pops up, phone starts, I am able to navigate the phone and phone apps for something like 20 seconds and then it freezes.
Model Number: SM-A528B/DS
The firmware shown in recovery mode is the following: A528BXXS1CVI6
Why I am trying all this
This is my wife's phone. I thought she was backing up photos through google photos and she told me that she was doing it. Unfortunately, she was only uploading them on the local app and the backup was not working since her storage was full for several months. So, if there is a way to access her stuff from any Operating System please let me know. The problem, I think, is that I can't without unlocking the phone (of course).
Note
If I don't unlock the phone, the phone does not freeze but of course, I cannot do anything. Therefore, I suspect it is some thread that starts by default as soon as the phone is unlocked.
What I tried
I tried the following things:
Remove the SD/SIM card tray (just because it was easy)
I tried to boot my phone in Safe mode. I correctly entered in safe mode, the third-party apps were disabled but then the phone froze again.
I connected the phone to a laptop (running Ubuntu 22.04) and entered in recovery mode. Once in recovery mode, I tried basically all the options without any luck so far:
Reboot system now
Reboot to bootloader
Apply update from ADB:
I tried to download a firmware for my phone and then send it through ADB with the following command
`$ ./adb sideload ~/Downloads/A525FXXS4CVK4_A525FOXM4CVJB_HUI.zip`
and I got stuck at
`serving: '/PATH_TO/Downloads/A525FXXS4CVK4_A525FOXM4CVJB_HUI.zip' (~0%)" `
I don't know why
I did not try "Apply update from SD Card" yet
I did not try "Wipe data/factory reset" yet
I tried "Mount /system" but it got me the following error:"Error updating for slotselect"
I tried "Repair apps"
I tried "Run Graphics test"
I tried "Run Locale test"
I tried and then did "./adb reboot recovery" to test that I was able to reboot through adb and it did reboot the phone indeed.
Let me know if you have any ideas on what to try next.
Having a similar issue right here, please notify me what you did afterwards and if you managed to solve it
I am in the same situation and same try outs. Only one slight different. Phone does not start at all. Only "SAMSUNG" and "powered by android" logos. Then starts to bootloop again.
Did you find a solution?
@minidiable did you try to flash with Odin? You should have a try using CSC that avoid erasing data.
In any case, I'm coming back here to give my result after several try-outs and finally going to a Samsung Center.
My phone, entering in recovery mode, had from the begining a message at the bottom saying " E:[libfs_mgr]Error updating for slotselect ".
At Samsung Service Center they told me that this error may probably warn about motherboard failure. And after tearing down the phone and checked it, they changed the moterhboard. Sadly, All data lost. That's all.

Categories

Resources