*CUSTOM* Padlock icon mysteriously disappeared... - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Cliff Notes
Bug during ODIN after failed flash of MDL
battery pull to reset phone after bad flash of MDL
ODIN flash MDB worked fine
Rooted/recovery TWRP worked fine
ODIN flash to MDL worked fine
Rooted/recovery TWRP worked fine
Reboot and NO custom/padlock
wiped/reset and flashed new ROM
STILL have root/recovery and custom ROM/Kernel work 100%
restored old (that had Custom/Padlock on boot) backup
STILL no custom/padlock, but everything works
Had Goldeneye ROM 1.3, Ktoosez kernel running perfectly. Went to flash Goldeneye ROM 2.0 and Ktoonsez kernel, and decided to do a clean install, so used ODIN to go back to UCUAMDB baseband. At first i tried to flash a good copy of UCUAMDL, but it kept failing, and i used ODIN to flash UCUAMDB over the *still technically part done at 'download' mode* UCUAMDL, when the UCUAMDB flash worked, I then used 3-Way tool to Root/install TRWP, ODIN flashed to UCUAMDL, used 3-Way again to Root/install TWRP, when it booted, there was no padlock screen. I had to reinstall (rerooted too, to be safe) TWRP, then wiped/reset and flashed Goldeneye 2.0 and Ktoonsez kernel.
The padlock 'custom' screen is gone. I have root. I have custom recovery. I dont know why or how. So i made a full Nandroid backup. I then wiped/reset, and restored the Goldeneye 1.3 backup i had (also TiBU with all data/apps), i STILL have root, recovery, everything back to 1.3, and NO CUSTOM/PADLOCK screen.
I have no idea why; but i know it might be useful to figure out what happened so others with custom rom/kernel can get rid of the Custom/Padlock image as well; i couldnt get rid of it via other methods, and had given up. This happened randomly. Again, i have root, recovery, and custom ROM/Kernel working perfectly, i can even reflash 2.0 via recovery and not get Custom/Padlock screen, or restore the 2.0 backup and no Custom/Padlock screen.

Related

[Flashing Problem] Am i doing something wrong?

I am trying to get Ktoonsez kernel running on MDOB ROM so i can create a perfect sRGB profile and FULLY eliminate screen flicker/color shift, running into some problems.
I am rooted with TWRP recovery and debloated via Motochopper CASUAL R527b
I also have Nottach Xposed mod installed.
I attempted to flash version 1.7 of the TouchWiz version of MDOB
Here is where i have a problem; i have a FULL backup of AT&T ROM with the above all installed and running PERFECTLY (which im running on again). I reboot into TWRP recovery, have the aforementioned full backup, i swipe to factory reset, davlik/system/data/cache wipe, then flash the ROM
I did NOT perform a full system/data wipe the first 2 times, and the ROM worked but not on second reboot (had to reboot system via recovery but it worked afterwords. I also got Ktoonsez TouchWiz kernel working, but it would not fully boot unless i booted from TWRP).
I cannot get past the Custom/padlock screen when i hit reboot system, so i cannot flash the kernel and then clear davlik and cache (which i am supposed to do in that order, correct?)
If someone could give me a complete step by step i would appreciate it. i have been waiting to fix the damn screen flicker and create the first perfect sRGB settings for this phone; i cant get this figured out or working, and i dont want to screw something up.
I have linked to EVERY bit of root/hack/ROM/kernel software i have downloaded, only difference is the ROM i have is version 1.7 instead of version 1.8. I believe perhaps something to do with the previous mods ive done may be inhibiting my ability to boot properly. i DID have it running, both MDOB, and later MDOB with Ktoonsez kernel, but i had to reboot from TWRP every time, which i knew was not right, so i flashed the backup AT&T ROM with all system/user/apps/data, the Motochopper Casual R527b Root/debloat mod, and Nottach Xposed mod which are part of my only backup (works flawlessly, im happy with it but i want to perfect an sRGB profile for these phones, its in my area of work and i would love to be able to show stuff that is absolutely correct to clients).
Everything should be annotated correctly, and i flashed everything correctly as per the directions found in appropriate threads, ie reset, davlik/data/system/cache wipe, flash ROM, reboot (worked twice, second reboot i installed Ktoonsez kernel, wiped davlik/cache, rebooted, got in, enjoyed it, rebooted, and it hung at custom/padlock screen). Now after i flash the same MDOB file, it will NOT boot, just hangs at custom/lock screen. i DID fully wipe the device to try to reset everything (via TWRP), and flash the new ROM.
Thanks!
anyone? this is really frustrating; same issue trying to flash v1.8 of MDOB

Ive tried everything MF9/MJA stuck at boot

2 days ago i foolishly flashed to a stock rooted deodexed MJA zip from Cyanogenmod 10.2. (NO I DID NOT MAKE A BACK UP. I DID do a full data/cache wipe before i flashed) Things got really weird after that. Phone would not boot past the yellow sprint screen. I had a few different backups that must have been old so i tried restoring to an older Triforce MF9 backup that i had from 2 months ago. After that i was stuck on the triforce boot animation. I thought "maybe my kernel got mixed up when i tried flashing to MJA". Downloaded and flashed stock MF9 kernel NO LUCK.
Ended up using ODIN to install a factory stock .tar of MF9... same boot loop, cleared cache(this succeeded), tried clearing dalvik cache (but it failed). It booted up and YAY stock MF9 WITH ROOT. So after all the sprint bloatware loaded up i was prompted for an OTA 4.3 updated. I foolishly accepted. So my phone shuts down into recovery installs the update then goes to CWM and says "fix root? yes or no" i hit "yes". Since then NOTHING has worked.
I tried to ODIN back to MF9 again as mentioned before, nothing. I thought it may be a kernel issue, I found no info on the new MJA kernel. I successfully used ODIN to flash philz recovery.tar so now im on philz instead of CWM or TWRP. I attempted to flash the original stock rooted MJA.zip that got me into this mess, but no luck. I now can not get passed the "Samsung Galaxy S4 screen" (tried clearing caches, and battery pull too). Im downloading "KERNEL-SPR-L720VPUEMJA-1382157965.tar" & "SPR-L720VPUEMJA-20131030154609.zip" at the moment to flash with ODIN. Also i might add, it seems like any recovery i use, TWRP, CWM, Philz they dont fully install the rom .zip's. I hit "install zip from ext/sd-card" and its like a 2 second installation. NO MATTER WHAT ZIP I TRY. Kernels seem to flash okay.
I dont care about root, or knox. I just want my phone again lol.
Try going here
Tallyphillips said:
2 days ago i foolishly flashed to a stock rooted deodexed MJA zip from Cyanogenmod 10.2. (NO I DID NOT MAKE A BACK UP. I DID do a full data/cache wipe before i flashed) Things got really weird after that. Phone would not boot past the yellow sprint screen. I had a few different backups that must have been old so i tried restoring to an older Triforce MF9 backup that i had from 2 months ago. After that i was stuck on the triforce boot animation. I thought "maybe my kernel got mixed up when i tried flashing to MJA". Downloaded and flashed stock MF9 kernel NO LUCK.
Ended up using ODIN to install a factory stock .tar of MF9... same boot loop, cleared cache(this succeeded), tried clearing dalvik cache (but it failed). It booted up and YAY stock MF9 WITH ROOT. So after all the sprint bloatware loaded up i was prompted for an OTA 4.3 updated. I foolishly accepted. So my phone shuts down into recovery installs the update then goes to CWM and says "fix root? yes or no" i hit "yes". Since then NOTHING has worked.
I tried to ODIN back to MF9 again as mentioned before, nothing. I thought it may be a kernel issue, I found no info on the new MJA kernel. I successfully used ODIN to flash philz recovery.tar so now im on philz instead of CWM or TWRP. I attempted to flash the original stock rooted MJA.zip that got me into this mess, but no luck. I now can not get passed the "Samsung Galaxy S4 screen" (tried clearing caches, and battery pull too). Im downloading "KERNEL-SPR-L720VPUEMJA-1382157965.tar" & "SPR-L720VPUEMJA-20131030154609.zip" at the moment to flash with ODIN. Also i might add, it seems like any recovery i use, TWRP, CWM, Philz they dont fully install the rom .zip's. I hit "install zip from ext/sd-card" and its like a 2 second installation. NO MATTER WHAT ZIP I TRY. Kernels seem to flash okay.
I dont care about root, or knox. I just want my phone again lol.
Click to expand...
Click to collapse
you need to try to install the Triforce MJA/4.3.1 kernal/MJA modem all at the same time. IDK what happened on the first try to boot loop you but once you updated the modem to mja you can't flash MF9 modem/kernel on top of it. Try that and let me know.
Tallyphillips said:
2 days ago i foolishly flashed to a stock rooted deodexed MJA zip from Cyanogenmod 10.2. (NO I DID NOT MAKE A BACK UP. I DID do a full data/cache wipe before i flashed) Things got really weird after that. Phone would not boot past the yellow sprint screen. I had a few different backups that must have been old so i tried restoring to an older Triforce MF9 backup that i had from 2 months ago. After that i was stuck on the triforce boot animation. I thought "maybe my kernel got mixed up when i tried flashing to MJA". Downloaded and flashed stock MF9 kernel NO LUCK.
Ended up using ODIN to install a factory stock .tar of MF9... same boot loop, cleared cache(this succeeded), tried clearing dalvik cache (but it failed). It booted up and YAY stock MF9 WITH ROOT. So after all the sprint bloatware loaded up i was prompted for an OTA 4.3 updated. I foolishly accepted. So my phone shuts down into recovery installs the update then goes to CWM and says "fix root? yes or no" i hit "yes". Since then NOTHING has worked.
I tried to ODIN back to MF9 again as mentioned before, nothing. I thought it may be a kernel issue, I found no info on the new MJA kernel. I successfully used ODIN to flash philz recovery.tar so now im on philz instead of CWM or TWRP. I attempted to flash the original stock rooted MJA.zip that got me into this mess, but no luck. I now can not get passed the "Samsung Galaxy S4 screen" (tried clearing caches, and battery pull too). Im downloading "KERNEL-SPR-L720VPUEMJA-1382157965.tar" & "SPR-L720VPUEMJA-20131030154609.zip" at the moment to flash with ODIN. Also i might add, it seems like any recovery i use, TWRP, CWM, Philz they dont fully install the rom .zip's. I hit "install zip from ext/sd-card" and its like a 2 second installation. NO MATTER WHAT ZIP I TRY. Kernels seem to flash okay.
I dont care about root, or knox. I just want my phone again lol.
Click to expand...
Click to collapse
You cant go from aosp to tw. You need to go back to stock. Just odin back to mj9 stock. Then reroot and use that rom with philz rec
Sent from my SPH-L720 using xda app-developers app

I Think I Broke it

i was running triforce rom 5.1 and was going to try sacs 4.4.2. it said that i had to use the new twrp or cwm recovery for 4.4.2. so i cleared all my data as i always do before flashing a new rom. then i flashed the new twrp and rebooted. now it will not reboot into recovery it starts then just reboots again. i tried putting cwm and philz back on with odin but it does the same thing. anyone know what i need to do?
edit: i tried a different version of odin and cwm loaded

What am I doing wrong?

Ok, so I odin'd to MJE...rooted MJE, installed safestrap...Booted into safestrap, installed the leaked NC2 build....Booted into download mode and flashed the firmware/radio or whatever you call it...Booted into NC2...installed the new safestrap 3.72, uninstalled the old recovery, then installed the new one...after I do that, I boot back into safestrap, and it always fails to mount system in stock slot...I find this out after I factory reset it...I have tried it twice, what gives?

Safestrap wont install custom rom correctly

I flash the stock firmware on the phone.
Installed root and safestrap recovery.
Booted into safestrap, wiped stock slot and installed Goldeneye by selecting all of the safestrap options.
Unselected reboot option and installed NB1 modules.
Rebooted into system
After this when it boots up, it shows safestrap disabled. If I wait, it goes to a black screen for a while and then reboots again into stock recovery. If I reboot again, it repeats the same thing over again. Yesterday, I got it to work using this same steps if I remember correctly, but the wifi wasn't working, so I needed to flash to stock again and try again making sure to install the modules.
UPDATE: I tried again, but with the GE-XXUGNK4-49.2 rom. I first tried to flash it to stock slot, but it didn't work. Then, I tried again by creating a new slot, flashing the rom to there. It didn't work, so I deleted it and tried the stock slot again. It worked this time. Now I'm going to try this again, but with the GE-XXUHOD7-53 rom.
UPDATE2: It didn't work. I'm not sure what's going on. It flashed just fine yesterday. I'm going to try again, but without wiping stock slot before installing.
UPDATE3: Didn't work. I'm so tired of this. Does anyone have any idea what's happening with this?
UPDATE4: I got it to work! I followed the safestrap instructions for GE EXACTLY. The thing that was throwing me off was that I thought I had to install the NB1 kernel and not the OC3 since I have NB1, but I did everything OC3. Also, I have no idea how I got it to work yesterday. I'm pretty sure all I did was just install and run.

Categories

Resources