Database Users

*CUSTOM* Padlock icon mysteriously disappeared...

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.

[H] Flashing issues

about a week ago when 4.4 roms surfaced for mako, i wanted to try one out. when i did it failed, so i read that you had to either update TWRP or use CWM. so i tried to update TWRP with goo, and goo is down i guess, so someone posted a flashable zip of the newest TWRP(2.6.3.2) and CWM(6.0.4.4) so i got them both, and flashed the TWRP, and it flashed the 4.4 roms. and i used my nandroid to go back to 4.3(Carbon ROM) and now it fails when i try to flash a new nightly (i facrtory resetted) and it failed on my backup too, so i flashed CWM, and rebooted and it fails on everything too. (new nightly, and a copuple of roms i had been meaning to try) and i just fastbooted the official image from teamw.in website (2.6.3.3) and its failing on nightlies, but restored my backup.
what can i do to make it flash again?
should i downgrade to TWRP 2.6.3.0, i think that is where i was and it would flash, I THINK. lol.
please help.

Trouble Flashing Roms

I'm rooted correctly and have the newest TWRP recovery installed. I've successfully flashed the update for a newer recovery than the stock one when you first put a custom recovery and I flashed an update for the radio on my d800.
I haven't tried flashing any stock roms only new 4.4.1 or.2 Roms. My question is did I miss a step, do i need to flash something else like the latest OTA then wipe again and go for AOSP. I'm by no means new to flashing.
When i try to flash it this is what I get
"error executing updater binary in zip "
Any tips?

Nvm. I switched recovery. Used the unofficial CWR and even though it holds up on clearing the cache it installed beautifully.

[Q] Cannot re root after 4.4.3 upgrade

Hi,
I previously had purity rom on my nexus 10. I decided to back to stock and use the xposed framework. So with 4.4.3 I flashed the stock images (manualy so it didn't wipe my sdcard partition), wiped data, cache and dalvick.
Stock 4.4.3 works fine, no issues here, but in acquiring root by flashing supersu update (both 93 and 99r3) root doesn't seem to stick. I can adb in and su from terminal, but when booting android supersu days it couldn't acquire root. I have tried other clockworkmod recovery and team win recovery so see if it was a bug with recovery, but no dice. Clockwork did occasionally say it lost root and press Yes to put it back, it did this on my nexus 5 and I still kept root.
I have even tried the universal nexus toolkit but that didn't work either. All methods I have tried have run the zip output fine, saying success.
Any ideas what's wrong. I assume I have done something wrong but can't find much information about root not working like this.

Did you try chainfire 2.00?
Link to Chainfire page

Hi,
Some time ago I've faced the same issue as you, what worked for me was using an older supersu flashable zip and after flashing it I flashed the latest. Don't know if it was placebo or something, but always worked for me .
~Lord

I did the exact same couple days ago after running Omnirom. I used this odex stock image http://forum.xda-developers.com/showthread.php?t=2529492
After the initial factory wipe I wiped dalvik,cache,data, and flashed SU after flashing the ROM but before reboot. Using latest TWRP. Hope this helps.

SM-N900W8 (Canada) - CWM Recovery Bootloop?

EDIT:
Please delete thread. There is an issue with my SD card resulting in files being corrupted. Massive losses. I was able to successfully install ROM by uploading files to Internal Storage
Hello,
I have been attempting to flash AryaMod : http://forum.xda-developers.com/galaxy-note-3/development/rom-aryamod-v1-3-tw-lollipop-5-1-1-t3326976/post67619860#post67619860
on my SM-N900W8. From the stock rom, I rooted it using CF-Auto-Root, then installed TWRP.
After downloading and putting all the necessary files on my SD Card, I attempted to install this but TWRP kept giving me file errors "Error: Secure Check Fail : aboot" when attempting to install anything, the kernel, the rom, the bootloader and modem, etc. Nothing was working.
I read that TWRP isn't very good with Aroma stuff and I should be using CWM, so I attempted to install that. Everytime I installed CWM, it would say it is going into recovery, then restart the phone, over and over..
Figured that I needed to just do a fresh install. I get a new Stock Lollipop 5.0 DOH1 from Kies, reroot with CF-Auto-Root, then install CWM from ROM Manager. Same thing, recovery bootloops.
Is there a way to fix either CWM or to get Aryamod to work with TWRP? Is the CF-Auto-Root breaking the recovery install since it installs through recovery as well?
At this point I've spent an entire day trying to get Aryamod with no luck. What the heck am I doing wrong?