Been getting frustrated over the past day.
Currently am up and running on a backup of Hyperdrive RLS 8.1, but I am afraid to reboot because for all of last night, any backup or clean install of any ROM I flashed would either
1) boot up the first time, but any subsequent reboots would result in stuck at the Samsung Custom Lock screen
2) not boot up at all, stuck at the Samsung Custom Lock screen
When I get stuck at the Custom Lock screen, I do a battery pull and then attempt to reboot into recovery. However, trying to boot recovery would not work (phone reboots itself after briefly showing "booting recovery" every time) until I plugged in the charger and tried to boot recovery (not sure if just coincidence?). Currently running TWRP 2.5.0.2
At this point, the recovery asks for a password (I have never set a password, don't know why this happens?). This prevents me from factory resetting (gives me an operation failed) because I need to "decrypt data" or something along those lines, using a password which I am sure I have never set. The internal storage is apparently unable to mount without decrypting data using a password..?
I found that in the WIPE menu I can perform the FORMAT DATA action which is successful and fixes the decrypt data problem, and I am able to factory reset and then restore a working ROM or install a new one (I tried CleanROM 1.6 with patch to 1.6.5 since it was on my sdcard).
This brings me to this position at the current moment. After formatting and factory resetting, I have done the following with such results:
1) Restoring my STOCK, ROOTED TWRP backup from before my install of Hyperdrive 8.1. Booted up fine, but a reboot gave the same results of stuck at the custom lock screen
2) Installing CleanROM, booted up fine the first time, but got stuck on the first reboot at the first bootup screen (it changed it to the original
Samsung Galaxy S4" instead of the custom lock?). I went back to recovery and went through the same process (decrypt by formatting data, factory reset, restore/install new rom)
3) Restoring my Hyperdrive 8.1 TWRP backup (first backup of the ROM while it was apparently running fine, reboots were normal and no problems yet). I am currently running this right now but have not attempted a reboot because I do not have the time for the next few days to mess around with my phone.
Summary: Stuck at initial boot screen (Custom Lock or Samsung Galaxy S4), TWRP 2.5.0.2 asks for password for decrypt?? & cannot factory reset, able to format data which allows factory reset after, restored Hyperdrive 8.1 backup, currently afraid to reboot in fear of getting stuck again.
Any help or suggestions would be appreciated. I am considering ODIN a stock image and completely starting over, but that will have to wait until the weekend.
Related
After rooting, I installed safe trap on my razr 912 CDMA, (no bootstrap).
1. Went to safetrap 1.0 recovery, data wipe, safetrap ENABLED and tried installing GUMMY 1.0.0 and gapps.
Tried rebooting but, after pressing the 'search button' key to start the ROM boot, it doesnt show anything , complete blank screen. rebooted few times, factory reset ,etc, didnt help.
2. Went back and DISABLED safetrap, which restored my initial copy of the stock, rebooted and it worked fine, my intial Stock ROM was up and running.
3. I doubted that this was issue with safetrap and not gummy installation; so to check that, I went to safetrap recovery, ENABLED safetrap. DID NOT INSTALL anything else.
Simply rebooted the phone, hoping the stock ROM to boot up since I did not install anything this time.
Result was the same...nothing on the screen....blank screen.
4. I went back and DISABLED safetrap and all was fine. Now stuck with stock ROM cant install new ROMS.
(I have no intention of trying bootstrap, because i did that on earlier Razr while installing Gummy 1.0.0 and it bricked the phone)
Question: it seems enabling safetrap, i am not able to bootup , no matter what. Any solution to this?
So... I'm trying to update to the current AOKP release, but seem to have an issue where the phone gets stuck on first boot.
Currently the process I'm using to flash is below:
1) Factory reset+wipe everything from recovery and reboot to bootloader
2) Flash boot.img, go to hwboot and reboot back in to recovery.
3) Push rom to sdcard, install rom/wipe cache and reboot
4) Watch that little X glow for 10-20 minutes.
This isn't the first time I've reinstalled the rom, however (I think) it is the first time I've wiped absolutely everything on the phone first. Is there some extra step I need to go through as a result? Or does first boot really take more than half an hour if I wipe all internal memory prior to reinstalling the OS?
Using TWRP 2.6 and hwboot 1.3(?) I think. Will check next time I'm in fastboot (leaving it on boot screen at the moment to see if it does anything).
First off I am on mdk and rooted and up until today have been running hd 10.2. I had been having some weird things happen with twrp 2502 so I went into goo and tried to update to the newest version of twrp. it downloaded and went through with everything and I rebooted into recovery. once I got into recovery it was showing I was still on 2502, but it was asking for a password which I had never seen before. I backed out and tried to boot into my rom again and it got stuck on the samsung custom screen. pulled the battery a few times and still kept getting stuck. went back into recovery and tried to restore a known good backup that I had restored before, but it keeps failing. I had rls12 on my phone so I tried installing it dirty since I cant wipe anything due to the whole password thing in twrp which said it was succesful but still gets stuck on the samsung custom screen. it sits there for about 10 seconds and loops. I tried about 10 more times to get my backup restored and it finally finished and booted into the rom. I left it this way for an hour or so and did some stuff with my phone, tried to update twrp again which did the same thing again and still shows 2502. after the reboot I am back to the same problem of not being able to do anything in twrp except restore or dirty flash, I cant get the usb to mount in twrp so I cant try putting another rom on the phone unless I go and buy a micro sd adapter.
I am in the process of downloading a stock mdk rom to try and flash in odin, but is there anything I can try before I go through with this, or is it pretty much my only option.
after some more research I think I figured out what caused all this. I wiped the data partition with the old version of twrp which screwed it up pretty bad. Apparently the older versions of twrp were known to have this problem. I kept trying to restore, but trying to restore kept failing on the data partition. After about 25 attempts of trying to restore just the data partition I was able to get it to work finally, and then I restored the the others and got it to boot back into the rom. like an idiot I rebooted the phone back into recovery after it finished and had the same problem again. another couple hours wasted trying to restore the data partition and it worked again and this time i was able to get twrp to update and then went back to recovery and formated the data partition again and it seems to have fixed the problem. Now to figure out why hd rls 12 wont install.
I did something stupid when trying to root a SM-T380 that I just got as a backup tablet. I am new to the samsung world and ODIN.
I got as far as flashing TWRP and booting into TWRP using the instructions from androidinfotech and I actually had to do this multiple times as the system kept rebooting (I did not uncheck the auto reboot at first) and resetting the boot loader.
So I got TWRP installed, but...
I was trying to clear the cache as the instructions were saying, but I could not get anything mounted and cleared. So I followed some stupid video that had me go into the advanced and change the file system to F2FS, wipe and then go back to I guess EXT4. Well, Now I am in a boot loop. I still can get into twrp and at this point would love to go back to stock and call it a day. I am "Slow" downloading a stock image for the device, but that is still hours from completion.
Is there anything I can try in twrp while i'm waiting?
So, I can't restore my backup due to the error above. When I restore my backup, I get that error and a reboot loops me straight back into TWRP. You can read all that stuff below if you need the backstory.
(I had Lineage OS 18.1 installed and wanted to restore a backup from two weeks ago. So, I booted into TWRP, did a normal factory reset and restored the Backup of Lineage. However, it put out an error regarding something in root (structure needs cleaning). I tried rebooting into system, but it ended in fastboot mode. So I googled it and one thread said you can solve that by formatting system. "System" is backed up anyway, so I thought there was no harm, wiped it and restored the same backup once again. No error this time.
However, when I rebooted into system, the unlock pattern didn't work any more, even though I never changed it and always use the same one. I had to reboot into recovery, and now the TWRP unlock pattern didn't work either. Had to skip it and did another reset.
Now, every time I restore a backup (and those backups contain basically every partition available) it works, but when I reboot into system it just stops at the boot logo, then reboots into recovery. Basically a boot loop plus. Tried a fresh flash, same loop.
Also, all of my pictures and downloaded files are gone, because it's encrypted. I had to wipe data, which led to the whole encryption issue going away, however, I'm still stuck in that loop.
Does anyone know how to solve this cluster****? How do I get it to boot into system?
Edit: Managed to flash LIneage new after wiping data and system and it actually boots, hallelujah, but when I flash the back up I'm still at square one with the same fail and it fails to boot. )