[Q] Can't boot after encryption - Galaxy Tab 3 Q&A, Help & Troubleshooting

Hi everyone,
Long time lurker posting for the first time, I hope I'm doing it in the right forum. I own a Samsung Galaxy Tab 3 7.0 with TWRP recovery and a custom ROM.
I was on RocketTab rom when this happened. I tried to encrypt the device using the built-in tool and followed the instructions. However, after a few minutes, my tab rebooted and got stuck on a screen asking for a password in German. I tried to enter my lockscreen password, it didn't worked. I triend another one and this time it seemed to work (even if it was an old password). The device was displaying a bugdroid with some kind of gear-belly. Then I had the RocketTab bootscreen and that was it. The screen stayed like this for a long time, so I rebooted, entered the password again and I got the same thing. That screen stayed like this until the battery dried out.
I went into TWRP and tried a restore, but all it changed was the bootscreen which got stuck in the exact same way. After a couple of failed attempts, I went deeper into TWRP and tried to wipe things. TWRP couldn't do that because /data failed to mount. I then went in the advanced settings and formatted /data. I was able to wipe it again if I would, so I thought my issue was resolved. It wasn't. Now I have the message asking for a password (now in English) but none of my previously used password are working :/
What do you guys think I can do? I don't care about the data, all I want is to make it work again.
Help me XDA people. You're my only hope.
Thanks!
Taz

BlackTaz said:
Hi everyone,
Long time lurker posting for the first time, I hope I'm doing it in the right forum. I own a Samsung Galaxy Tab 3 7.0 with TWRP recovery and a custom ROM.
I was on RocketTab rom when this happened. I tried to encrypt the device using the built-in tool and followed the instructions. However, after a few minutes, my tab rebooted and got stuck on a screen asking for a password in German. I tried to enter my lockscreen password, it didn't worked. I triend another one and this time it seemed to work (even if it was an old password). The device was displaying a bugdroid with some kind of gear-belly. Then I had the RocketTab bootscreen and that was it. The screen stayed like this for a long time, so I rebooted, entered the password again and I got the same thing. That screen stayed like this until the battery dried out.
I went into TWRP and tried a restore, but all it changed was the bootscreen which got stuck in the exact same way. After a couple of failed attempts, I went deeper into TWRP and tried to wipe things. TWRP couldn't do that because /data failed to mount. I then went in the advanced settings and formatted /data. I was able to wipe it again if I would, so I thought my issue was resolved. It wasn't. Now I have the message asking for a password (now in English) but none of my previously used password are working :/
What do you guys think I can do? I don't care about the data, all I want is to make it work again.
Help me XDA people. You're my only hope.
Thanks!
Taz
Click to expand...
Click to collapse
It was a long time ago, a other has user done The same ,but i dont find The thread at The Moment.
I think The onlyest what will hell is flash a Stockrom with a Pit.file
A Pit.file erase and Format your hole tab.
Search in this thread for a pit.file, download The Stockrom from sammobile and this with Odin.

Thank you, it worked!

Related

[Q] Stuck at Android logo.

Hi, thanks for reading and helping, I would really appreciate that if you helped me.
I've got a Samsung galaxy tab 3 model SM210.
I have to tell you that I have set a memory encryption on that device in addition to the lock screen password.
The encryption uses the same password as the lock screen uses, just when I reboot the device. Without decrypting the device, you won't be able to fully load the OS.
I'm telling you this because I have a feeling that this is the source for the problem I have.
The OS felt really slow and I wanted to upgrade. I had 4.1.2.
I have downloaded version 4.2 jelly bean and installed TWRP recovery using Odin.
Then I have installed the root kit and the jellybean.
After rebooting, I noticed that that all data and apps were still there and I have had a problem turning on the wifi from 'settings', it crashed every time.
I loaded back the TWRP and formatted the device.
The installed again the jellybean.
Since then, the device is asking me to enter decryption code (the same one from before).
I wonder why this message still appear after formatting the whole device?
Anyway, I enter the code and then the android logo appears and stuck there.
I have tried multiple times to reinstall an format etc.
every time I get to this place.
How do I fix this?
EDIT:
more bad news.
TWRP has stopped working, even after relfashing it with Odin.
I have installed CWM and succeeded installing StockRom V2.0 (not the samsung stock rom, its name is "stockrom v2.0) and after that the OS loaded up and I have got the screen which asks me to enter the code for decryption.
The code was "l1212", it does not work anymore. How can I bypass this screen?
I also installed right now the first rom I have told about above, the jelly bean, then the decryption screen comes up and the code above is ACCEPTED and then stuck again on the Android logo...
What a nightmare.
I think the onlyst what help, is flash Org. Stockrom with Odin. Flash a Custom recovery and root you Tab, after that make a backup.
I now since a lot of month ago a other user has done the same.

Weird crashes &reboots

Hi everyone,
today I woke up and as usual i turned on my Gnex GSM (that has TWRP 2.8.0.0 and PA 4.6 beta 3 release1) and after a few minutes it started rebooting. i tried to remove battery at first but nothing happened; every time I put in the battery it starts, ask me for PIN, seems everything ok but reboots again.
I tried to enter in recovery mode to do a factory reset and even if TWRP says successful wipe nothing happens because when i reboot everything is like before. Itried to change recovery from TWRP to CWM but I can't even do that it "stucks" with TWRP. Fortunately I made a backup recently so I don't mind losing everything but if everyone has a solution please tell me because I don't know what to do!!
Another thing that compared in the log of TWRP during wipes was some strange ( for me, I'm not a developer) errors like "E: enable to stat '/data/media/.....'
If anyone can help I'll appreciate a lot!!! :laugh::laugh::laugh:
Thanks all!!
Same thing happened to me too....
Everything was working butter smooth when **** hit the fan.
I own GSM Gnex, rooted with stock 4.3 with Xposed installed. Custom recovery was TWRP
One fine day I was sitting with a friend in an restaurant when my phone suddenly started rebooting after reaching the homescreen. Mind you I can unlock my phone but after a couple of seconds, it would reboot
For two days, I did everything I could, used Wugs NRT, did a factory reset using TWRP, used ODIN, Flashed stock using toolkit and did that again manually using ADB. Nothing happened.
It says 'successful' when I flash using NRT, but nothing really changes and it freezes halfway while using ODIN and 'FAIL' error shows up.
After two days, I gave it to the shop from where I bought the device and its fourth day today but he still isnt able to repair my phone.
Mind you, I can access TWRP and all the functions, even factory reset but nothing happens.
At first I thought it might be moisture but it wasnt the case. I think it has to be an hardware issue

[Soft-Brick] Stuck at boot screen

Hi guys,
(Samsung S4 Mini GT-i9190)
I could really use some help.
I have been searching all over and perhaps I'm not understanding what is being said so if it sounds familiar and there is a solution then i'm thankful.
So about a week ago, the phone came back from repairs and had the motherboard replaced after the phone was washed by accident. Nonetheless, there hasn't been any hardware defects besides signal loss now and then.
When the phone came back, it had 4.2.2 and it automatically picked up the update to 4.4.2 which I did. The phone worked fine until 2 days ago, where it just stuck at the Samsung galaxy gt-i9190 screen and just freezes there.
I can boot into a custom recovery (Philz) (not stock recovery for some reason) and download mode. I then attempted to install CM 11.0 as I got frustrated. It worked, booted past animated logo and install the apps until i came to the language section where the touchscreen which didn't work (unresponsive). I then reverted back to the stock ROM found at sammobile (i9190xxxCOD2XFA - South Africa), loaded the custom recovery and still no booting past the first screen. The custom recovery touchscreen (Philz) is also non responsive (besides using the volume keys, home button and power for navigation).
I flashed a couple of times, nothing works.
Is there a root cause to these issues? The unresponsive screen, not booting properly?
Some info: KNOX is voided 0x1
Please help!! Thank you in advance
It's not „root“ that cause your problem. You should have to choose right recovery for your model. Flash back to original ROM and look for one of fully supported custom ROM here on the XDA and fallow all steps how to flash it properly. Succes ! Cheers !
Alright, I'll try that. What I did in the meantime was flash, Slimkat 4.4.4 UNOFFICIAL rom for I9190 (http://forum.xda-developers.com/showthread.php?t=2708677).
The rom booted into the andoird system but the touchscreen is still unresponsive.
@Boombastical .. If you can help me by giving me a guide in order to do what you say, then please do help. Even in recovery especially TWRP the touchscreen is unresponsive except for ClockWorkMod and Philz. So i don't know if it is hardware related or I'm doing something wrong.
Its driving me crazy :crying:
Update
So what I did last night:
I loaded the SlimKat rom and based on the stock bootloader and after doing a couple of battery pulls the screen starting functioning properly. However it was just luck or could've been something more technical.
I need help in understanding why that happened.
Then I decided I dont trust my method and reloaded the stock 4.4.2 firmware from sammobile. What then happened, is that it booted past the "Galaxy GT-I9190" screen into the samsung logo and then installed the applications. Come to the choose language screen, the touchscreen became once again unresponsive.
Bear in mind, that when I did a reboot with the stock rom, it didn't want to boot past the screen and just hung there.
So what could my problem be?
Is it the rom that I used? Using Unified Android Tool, I saw my region code is GB which I haven't seen anywhere in the stock roms.
Could the system somehow become corrupted? Emmc, partitions? Could the screen calibration be out of sync?
Must the bootloader always be the stock one? Are there custom bootloaders that one can use?
Please help, thanks
GeezyTab88 said:
So what I did last night:
I loaded the SlimKat rom and based on the stock bootloader and after doing a couple of battery pulls the screen starting functioning properly. However it was just luck or could've been something more technical.
I need help in understanding why that happened.
Then I decided I dont trust my method and reloaded the stock 4.4.2 firmware from sammobile. What then happened, is that it booted past the "Galaxy GT-I9190" screen into the samsung logo and then installed the applications. Come to the choose language screen, the touchscreen became once again unresponsive.
Bear in mind, that when I did a reboot with the stock rom, it didn't want to boot past the screen and just hung there.
So what could my problem be?
Is it the rom that I used? Using Unified Android Tool, I saw my region code is GB which I haven't seen anywhere in the stock roms.
Could the system somehow become corrupted? Emmc, partitions? Could the screen calibration be out of sync?
Must the bootloader always be the stock one? Are there custom bootloaders that one can use?
Please help, thanks
Click to expand...
Click to collapse
Possible solution:
So I thought it could be screen calibration so this is what I did to make my phone work.
I loaded the CARBON Rom as I somehow lost root privileges with SlimKat. It loaded into the OS as per normal but the touch screen didn't work. So after numerous battery pulls, i read this post http://forum.xda-developers.com/showthread.php?t=2353972&page=1 .
So then I connected the phone to the pc (having had the samsung drivers installed as well as adb) and booted into cmd promt as admin.
This is what I did in cmd prompt:
cd adb
adb shell (make sure there is a "#" as that ensures you that your phone is rooted)
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
@xcxa23
It then still didn't work (the touch screen) then somewhere on one of the pages in the above post, someone mentioned holding home button. I switched the phone off, I then held the home button (until it booted into the OS) and then powered the phone on. The phone booted into the OS and presto the screen worked again. I did a reboot and the screen is still fine.
Again I'm not sure if its that exact method but what I am sure of, is that I did a clean rom install (an option in Philz touch recovery), wiped the cache, formatted the options (boot, system, cache, preload, data) in mounts and storage and then proceeded to install the rom from the sd card.
I haven't tried with the stock rom as yet so if this helps you, goodluck and if you can help improve on this method or help me understand why this is happening, it would also be appreciated.
Thanks
Confirmed for that is
GeezyTab88 said:
Possible solution:
So I thought it could be screen calibration so this is what I did to make my phone work.
I loaded the CARBON Rom as I somehow lost root privileges with SlimKat. It loaded into the OS as per normal but the touch screen didn't work. So after numerous battery pulls, i read this post http://forum.xda-developers.com/showthread.php?t=2353972&page=1 .
So then I connected the phone to the pc (having had the samsung drivers installed as well as adb) and booted into cmd promt as admin.
This is what I did in cmd prompt:
cd adb
adb shell (make sure there is a "#" as that ensures you that your phone is rooted)
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
@xcxa23
It then still didn't work (the touch screen) then somewhere on one of the pages in the above post, someone mentioned holding home button. I switched the phone off, I then held the home button (until it booted into the OS) and then powered the phone on. The phone booted into the OS and presto the screen worked again. I did a reboot and the screen is still fine.
Again I'm not sure if its that exact method but what I am sure of, is that I did a clean rom install (an option in Philz touch recovery), wiped the cache, formatted the options (boot, system, cache, preload, data) in mounts and storage and then proceeded to install the rom from the sd card.
I haven't tried with the stock rom as yet so if this helps you, goodluck and if you can help improve on this method or help me understand why this is happening, it would also be appreciated.
Thanks
Click to expand...
Click to collapse
Hey guys, just a quick update.
I reloaded Cyanogenmod mod CM13. I can confirm that my screen didn't freeze up and booted perfectly. I also then decided to take a chance adn reload the stock rom 4.4.2 and it also worked perfectly and booted directly into the OS.
I'm guessing the screen calibration was out.
So if this happens to you, I would suggest loading a custom rom and doing the screen calibration reset through adb and then test again with another custom rom. Once you comfortable, you can reload a stock rom.
I used Philz Touch for recovery
Thanks to everyone who put posts up .. Time to rest
Not working again!!
Hey,
So in my previous post I said I got it to work. Well I did, up until a few minutes ago when the phone just decided to freeze up again. I restarted the phone and would you know, back to square one!
I've noticed issues that I'm wondering if they could be the problem:
1) The audio didn't work at all. By audio, I mean the mic. When I did voice recording, it just gave static, whatsapp calls, the other person can't hear you as well as regular phone calls.
2) I just rooted the phone in order to change the audio_policy.cnf and delete lines relating to the above audio problem but then the screen, return, and menu button didn't function. The screen could still rotate until I pressed the power button to lock then unlock and then it didn't unlock :crying:
So once again, some help guys please. Is it rom related, hardware (motherboard, chip) or software that just isn't working right? Could it be KNOX?
Thanks

Stuck on Startup

Having some serious trouble. I rebooted my phone and it asked for my password once it was done as always but this time it said it was wrong. I'm certain I used the correct password but even tried my other alternatives to be sure and still a no go. This isn't the decryption option password you get when booting but my lockscreen password. I booted into recovery and it asks me for an encryption password that I never set but I know this is a common issue with twrp. Tried to go back into android but wouldn't let me because of the "wrong" password so I used the failsafe and went into recoveries file manager and deleted my lockscreen settings to remove my lockscreen passcode (tried and proven method, done it dozen times before). Got past my lockscreen this time but now it was saying starting android forever. Figured it was something with the passcode being deleted so I just decidd to factory reset from the recovery and take that loss. NOW the problem is upon booting the rom in trying to start the setup, I'm stuck on the "just a sec..." screen that comes up after you click start. What do I do from here? I cant access anything in recovery because the encryption passcode issue so I'm kind of stuck. Also I'm a work right now and we cant connect our phones (or any USB for that matter) to the computers and laptops because theyre government property and on a secured line. Any help PLEASE, Ill be home later and can try more then.
Well since you already did a factory reset on the device you mine as well just do a clean install of the OFW then get twrp back and flash your ROM etc back. Would probably be better then to deal with everything going on with the device right now.
loeffler23 said:
Well since you already did a factory reset on the device you mine as well just do a clean install of the OFW then get twrp back and flash your ROM etc back. Would probably be better then to deal with everything going on with the device right now.
Click to expand...
Click to collapse
Hey, I got my phone back working after that and rooted again and flashed same rom. NOW another problem, I rebooted my phone and its not accepting my PIN anymore, nor my fingerprint, and I cant reset through TWRP because of encryption. WTF is the issue, how do I fix this or do I have to flash-all again?

tab s4 bootlooping

I know that there are many threads already about the tab s4 and other devices bootlooping but every in thread I saw the device also shows an error of some sorts or you can enter the recovery mode.
In my case it is a bit different, as I think it was caused by me being stupid and accidentaly deleting something I needed to boot with the universal android debloater. I deleted one partition that had no discription but seemed save to me but oh well. After deleting the package with UAD I used it for a while and the only reason I restarted it is because some app (i think overdrop) had a notification that I need to turn of battery optimisation for it and restart my tablet. So I did that today in the morning and in the beginning everything looked fine. I wondered why the Samsung logo was on the screen for so long but decided to let it do its thing. Then there was a menu that said something about it not being able to boot and told me what to do in 3 Steps: 1: retry the boot process (which just brought me back to the same menu); 2: reset the app data/cache (which seemed more promising) 3: contact support (which i didnt do because i feel like they would just tell me that they cant help me with that because its a device from 2018 and i used an "illegal" tool). So i reset the app data/cache and then tried to boot it up again. Then it bootlooped and I went into recovery mode and tried to hard reset the tablet hoping that the missing package would be restored with the factory reset but thats not a thing appearently.
So the things ive tried to solve this issue are:
using adb/aud to restore the missing package (didnt work because despite some thread saying that adb can be accessed while bootlooping I couldnt so that isnt gonna work)
Force shutdown and boot into recovery to look at the log and find something (I cant even get to the recoverymode anymore because the keycombination would just "restart" the booting process)
Sorry if my english isnt understandable, it isnt my first language

Categories

Resources