yashsingh1/xdaforums huggingface dataset:
[AT&T HTC One (M7)] nthknd:
I simple told the Rep that I need my upgrade 2 months early because my current phone wasn't working for me anymore. she understood my problem and said retention department could help me. Five mins later she came back and said since I was nice and in good standing that she could approve my upgrade and wave my upgrade fee. I need a larger screen due to losing most of my eye sight in an accident she said the only draw back was I'd have to pay for whatever phone I wanted right then . So I told thanks and then spoke with her supervisor letting him know how great she was. Being very decent is the key even if you need to speak to a supervisor ask nicely and erasure the Rep that you understand that she help as much as they could. So I paid for my phone and they shipped it out ocernight. Be patient be pleasant they get ****tiy people calling all the time so it helps to be nice.
[AT&T HTC One (M7)] ameza001:
Co-worker got a similar deal. His problem was that the online system would cancel his order immediately after completing it. It happened twice. He called not to complain, but simply to order the phone and got it free with free overnight shipping. His account was eligible for an upgrade, though.
[AT&T HTC One (M7)] colts187:
The store manager has the power to give u an early upgrade within 30 days of the eligible date. Its funny BC some managers will say well it has to be in the same calendar month or ah it's gotta be within 14 days. U got lucky!
[Verizon Samsung Galaxy S 4] CyberZion:
I started having this problem after rooting and installing custom rom. It does not matter which rom you install. The only fix I have found is to unroot and return to stock..

Once you root and install your rom the phone works fine, until you reboot. Then it just hangs at the padlock screen. You have to pull the battery and reboot into recovery, format, and reinstall the rom, or go back to stock... HELP!!!!!! :(
[Verizon Samsung Galaxy S 4] imablackhat:
When originally rooting did you let supersu update and select normal?
[Verizon Samsung Galaxy S 4] CyberZion:
I did update, not sure about selecting normal. I don't remember seeing that option. What does the normal do?
[Verizon Samsung Galaxy S 4] imablackhat:
You need to select normal when updating supersu when you open the app. And what recovery are you using? Have you tried installing goo manager and installing the script which is twrp that has auto loki.
[Verizon Samsung Galaxy S 4] CyberZion:
Yea, I installed TWRP from goo.. I will root again and make sure I check normal.
[Verizon Samsung Galaxy S 4] CyberZion:
I don't see the Normal setting. Could you point it out..
[Verizon Samsung Galaxy S 4] CyberZion:
Ok... I'm a D.A. Both times I rooted, I missed the step of downloading SuperSU and updating it during the Root process. Thanks Black Hat.. Everything should be good now.
[Verizon Samsung Galaxy S 4] imablackhat:
You're welcome. Let me know how you turn out!
[Verizon Samsung Galaxy S 4] CyberZion:
I spoke to soon.. No Joy.. I managed to get it to reboot one time. Now stuck at Custom Padlock, again.
[Verizon Samsung Galaxy S 4] trbman:
i'm actually having the same issue. i followed the directions to root using the pre-release kernel and odin. i updated the SU binaries and selected Normal when it asked me. after that i installed the custom recovery using GooManager. now when i install a ROM and reboot it hangs. wonder whats going on. hopefully someone can help us out
[Verizon Samsung Galaxy S 4] tgumina:
You shoul be able to return to stock with one of the methods in the developers forum.
[Verizon Samsung Galaxy S 4] trbman:
i'm going to try returning to stock than trying everything all over again. i'll report back on how it goes
[Verizon Samsung Galaxy S 4] imablackhat:
I've seen another person reporting this issue in the hyper thread. I installed the hyper rom last night and rebooted fine like three to four times no issues but now I'm scared to reboot lol
[Verizon Samsung Galaxy S 4] trbman:
that other person was me. haha
[Verizon Samsung Galaxy S 4] imablackhat:
I wonder what's going on. If you're missing a step or something. Idk I've installed last night upon release. Rebooted a couple times. Didn't have an issue. When I wiped. I wiped data system cache and dalvik twice. Then installed the rom and rebooted. Restored my apps and settings. Let it settle for a sec and rebooted again. Didn't have any issues.

People that are stuck at padlock screen. You're using the latest twrp autoloki? Can you get back into recovery even though you can't get past padlock. And how long do you wait at the padlock?

---------- Post added at 09:45 PM ---------- Previous post was at 09:43 PM ----------

After rooting and updating supersu and hitting normal. you guys are going back and flashing the normal kernel not prerelease right through Odin?
[Verizon Samsung Galaxy S 4] trbman:
i installed TWRP using GooManager. it said it was version 2.5.0.2. yes, i can get back into recovery. and the padlock screen stays there indefinitely. i am in the process of odin-ing back to stock so i'm gonna start over and we'll see how it goes. hopefully this resolves it. can't live with Stock TouchWiz.

EDIT---

yes, i hit normal and flashed back to stock kernel from the pre-release.
[Verizon Samsung Galaxy S 4] imablackhat:
So it booted fine once. How long were you in it? Did you install anything or configure anything or did you install boot it up. And reboot and notice it won't come back up and hangs?

Because I've been told X posed doesn't work yet even though it's in the rom and if you install it. It'll soft brick and you'll need to dirty flash or reinstall.
[Verizon Samsung Galaxy S 4] CyberZion:
Already done that.. No help.. Maybe you will have better luck.
[Verizon Samsung Galaxy S 4] imablackhat:
Two people so far with the same issue. Doesn't matter whatever rom?.. ;/
[Verizon Samsung Galaxy S 4] CyberZion:
Done all of that. Rerooted twice! I'm getting frustrated with it. I am now back to stock with no problems.. But yea, I was able to get into recovery after pulling the battery. :crying:
[Verizon Samsung Galaxy S 4] trbman:
one mistake i made the first time around was not un-checking the 2 places where it says Verify Apps. I misread the instructions and thought it said to check them, not uncheck. maybe that'll resolve my issue. i doubt it, but we'll see. i'm back to stock and just did the root routine. i'm about to install a recovery and flash a custom rom again.
[Verizon Samsung Galaxy S 4] CyberZion:
Before you install a new rom, reboot a few times. And after you get a new rom, reboot a few times before installing anything.
[Verizon Samsung Galaxy S 4] trbman:
is that a suggestion? or did it work for you? i just installed my custom recovery via GooManager. i'll reboot a few times before i flash another rom.
[Verizon Samsung Galaxy S 4] CyberZion:
Just a Suggestion. I'm back on stock, waiting for your outcome.
[Verizon Samsung Galaxy S 4] trbman:
got it. i just rebooted a few times. i also booted into recovery to make sure it installed correctly. i didn't install any ROMs, but when i chose to reboot the system it said something about Root not being installed correctly and asked if i would like to fix it. i said yes to the fix and rebooted perfectly. i'm gonna go back into recovery now to wipe and flash Hyperdrive

EDIT----

actually, now that it "fixed my root" i'm gonna go back to GooManager and install the recovery one more time before i flash a new rom.
[Verizon Samsung Galaxy S 4] CyberZion:
Did you ever see the padlock on reboot?
[Verizon Samsung Galaxy S 4] CCoR87:
Was having the same exact issue as OP, what I ended up doing was starting from scratch and re doing my root method.

Check out this thread for what I did, lmk if you figure it out!

http://xdaforums.com/showthread.php?t=2302560
[Verizon Samsung Galaxy S 4] trbman:
i saw the padlock, but i didn't have a custom rom installed yet. i think the padlock indicates that a custom recovery is installed, so seeing it was normal.

i am currently sideloading hyperdrive on my phone. crossing my fingers that some of this black magic worked.
[Verizon Samsung Galaxy S 4] imablackhat:
I'm hoping you guys figure it out. Lol

---------- Post added at 10:28 PM ---------- Previous post was at 10:27 PM ----------

Give it like ten reboots!
[Verizon Samsung Galaxy S 4] trbman:
****ing a. still doesn't work. i don't know how our 2 devices are not cooperating and everyone else's is. i'm gonna try using the other recovery instead of TWRP.
[Verizon Samsung Galaxy S 4] CyberZion:
Did you install the rom from the SDcard of the phone... I was doing it from the SD card.. Maybe that is the problem. Load the rom from the phone instead.
[Verizon Samsung Galaxy S 4] CyberZion:
Yea, the last two time I rerooted, I used this method. Did you by chance load the rom from the sd card or the phone?
[Verizon Samsung Galaxy S 4] trbman:
i did an ADB sideload using TWRP the first few times, than the last time i used an SD Card with the OUDHS CWM recovery. i'm ODIN-ing back to stock and trying the automated way. if this doesn't work than we're just gonna have to wait for an update that fixes this strange bug. kinda sucks.
[Verizon Samsung Galaxy S 4] imablackhat:
It's only you two guys. I wonder what's going on.
[Verizon Samsung Galaxy S 4] trbman:
yeah. its super frustrating. the phone is still new so maybe we'll see others with the same issue. maybe there is a difference in hardware? although i doubt it. just want some custom ROMs! hahah i cant take stock CrapWiz.
[Verizon Samsung Galaxy S 4] imablackhat:
Okay now that I'm home. I restarted my phone and it worked fine. I had an uptime of like 18 hours? Have no issues. I followed the regular root process through Odin then flashed twrp and backed up and wiped and installed hyper no problem.
[Verizon Samsung Galaxy S 4] CyberZion:
Whenever you reboot, do you see the padlock or does your boot bypass it?
[Verizon Samsung Galaxy S 4] imablackhat:
I see the padlock for like 15 seconds with the led notification solid. Then it moves forward..
[Verizon Samsung Galaxy S 4] CCoR87:
Good question, I attempted to see if i could load the ROM via phone memory but apparently when you wipe before installing you're supposed to not only do a factory reset but also wipe system too. That removed the file from the phone and i was forced to use SD card. I than rebooted w/o any issues but could not reboot afterwards (Padlock scrren hang).

That was as far as I would get previously but after redoing my root (method shown earlier) and recovery (TWRP), I was able to install and than reboot w/o any issues. Do keep in mind that the padlock screen remained on my phone but this time around it did not hang. I tried rebooting multiple times and I'm still golden.

Note, on first boot you should not have any user data, thus requiring you to log back in. Keep it to minimum with just google and than reboot after 5-10 minutes.

LMK>>>..
[Verizon Samsung Galaxy S 4] imablackhat:
Yeah are you guys formatting system too? I did advanced wipe and made sure cache dalvik data and system. Twice. Then flashed rom
[Verizon Samsung Galaxy S 4] CCoR87:
Per devs release notes I'm factory resetting 3x (which in TWRP includes dalvik cahce and cache) and then in advance I perform only system wipe once. From there I install ROM and reboot.
[Verizon Samsung Galaxy S 4] imablackhat:
I always just manually wipe everything. Does the same thing. Except I know I physically checked it in. Never had issues on any device. I always format those 4 before flashing any rom ever. Unless I intend on dirty flashing.
[Verizon Samsung Galaxy S 4] CyberZion:
Trpman, have you had any luck yet?
[Verizon Samsung Galaxy S 4] imablackhat:
Anyone any luck yet?!
[Verizon Samsung Galaxy S 4] shabbypenguin:
twrp 2.5.0.2 wasnt auto loki guys, is the padlock you are reffering to the unauthorized software screen?

or is it just the generic modded kernel screen?

edit: i know thats teh sgs2 but it was teh best image i could find atm
[Verizon Samsung Galaxy S 4] CyberZion:
The Samsung Padlock with custom under it.
[Verizon Samsung Galaxy S 4] imablackhat:
Newest twrp is auto loki. At least it says everywhere and a lot of people use it. Including me.

---------- Post added at 02:19 AM ---------- Previous post was at 02:18 AM ----------

http://www.teamw.in/project/twrp2/181

Says loki.
[Verizon Samsung Galaxy S 4] CyberZion:
I have noticed tha the s3 had this problem at one time, but have not found how they fixed it. Something with the bootloader.
[Verizon Samsung Galaxy S 4] shabbypenguin:
yes recovery and kernels need to be patched with loki for them to work on your device. it doesnt auto loki kernels yet
[Verizon Samsung Galaxy S 4] imablackhat:
But the hyper rom is loki patched and good to go. Right? I mean I'm using it with no issues. I'm just trying to figure out other people's issues.
[Verizon Samsung Galaxy S 4] trbman:
no luck. i gave up after my last attempt. i'm gonna wait until some other methods are discovered/developed before i try again. i'm gonna keep an eye on this thread and post back if anything changes with my situation.

---------- Post added at 12:30 AM ---------- Previous post was at 12:19 AM ----------

i also sent a message to djrbliss to see if he could take a look at this thread to figure out what we may be doing wrong.
[Verizon Samsung Galaxy S 4] djrbliss:
This isn't rocket science.

Both your recovery image and any kernels you flash need to have been patched with Loki in order to boot properly. If you're getting the unauthorized software screen when trying to boot a custom kernel, it means that kernel hasn't been patched with Loki.

You're using TWRP, which at this time is itself patched with Loki (in order to allow the recovery itself to boot), but does not automatically Loki-patch incoming custom ROMs. This means you have three options to get your ROM working:

1. Use a recovery that automatically Loki-patches incoming custom ROMs, such as OUDHS (look for the words "auto-Loki").

2. Only flash ROMs that have been Loki-patched for you (look for the word "Loki" in the ROM title).

3. Manually run loki_patch on the boot.img in any custom ROM that hasn't been Loki-patched. You'll have to be able to follow directions I've already posted for this.
[Verizon Samsung Galaxy S 4] Churchryn:
I also get the unlocked Padlock that says "Custom" screen every time I reboot. However, it doesnt get stuck there. It will sit for a few seconds and then proceed to boot.
[Verizon Samsung Galaxy S 4] BladeRunner:
I don't know if this could have anything to do with people have issues booting BUT I have had issues with downloads from androidhostfile, one mirror in particular. I DL's Hyperdrive from the GA mirror twice and it failed to boot (kept looping back into recovery) even though the installation seemed to complete just fine in recovery. DL'd from the IL mirror booted fine. Make sure you are verifying your MD5 sums. Unlike me :silly:
[Verizon Samsung Galaxy S 4] th3drow:
I'm having the exact same issue, I guess I am going to try to get cwm working, after first reboot everything just stops working and i get locked on the cwm screen. I've tried 2 roms and 2 twp versions.

---------- Post added at 06:35 PM ---------- Previous post was at 05:35 PM ----------

Fixed it! had to use CWM found here

http://xdaforums.com/showthread.php?t=2292112

just rebooted after instaling hyperdrive and it finally worked! The cwm in the all in one tool I found is different, need to use the one in that thread.
[Verizon Samsung Galaxy S 4] thinksnow:
Same issue. I did the following:

Root via open1your1eyes0 thread

TWRP Recovery via Dees_Troy's thread [RECOVERY] TWRP 2.5.0.2 touch recovery [2013-05-23]

Clear factory wipe 3 times

Wipe data, system, cache, dalvik 3 times

Boot to TWRP recovery and install ROM - Hyperdrive ROM

Everything appears to go fine, reboot after install looks great and I make sure not to install any apps or change any settings and to let it sit fr 7-8 minutes before rebooting. At reboot, I get the Custom padlock (with no LED activity, like some others have described).

This is the second time I've installed this ROM, having gone back to factory after the last time.

Frustrating as all get out.
[Verizon Samsung Galaxy S 4] ProfEngr:
I might be in this boat too.

Tried flashing CleamROM 1.2 a bit ago. Got a UID mismatch warning from Android to wipe data. Did that.

Did let it settle for several minutes before loading TiBu. It gave an Android ID is different from last install warning. Told it to fix it; done this numerous times on a Note 2. Phone rebooted & I've been stuck at the Samsung logo ever since. Even tried restoring the stock rooted image and no luck.

Trying a triple wipe of everything & another restore now. TWRP 2.5.0.2
[Verizon Samsung Galaxy S 4] ProfEngr:
Yep. Was TWRP causing the hangs. Went with ouhs (?) CWM variant. All is well so far.

Sent from my SGS4 using one opposable thumb.
[Verizon Samsung Galaxy S 4] OMsupp:
im having the same problem where i cant boot into recovery and im stuck on the custom padlock screen . is there anything i can do. i was on cm10.1 before this and it worked fine. i flashed hyperdrive using OUDHS and it installed and everything. i let it sit for 10 minutes like it said to then i continued to reboot... and now its stuck on the custom padlock screen and im cant boot into recovery for some reason... could i have missed something?
[Verizon Samsung Galaxy S 4] DarkMenace:
Can you boot in to Odin mode? If so you probably need to install the Stock image and restart again.
[Verizon Samsung Galaxy S 4] dontcallmejames:
the first time i rooted, i never saw the custom/padlock screen and i installed various roms to try them all out. i unrooted/flashed back to stock. and then i did it all again, this time i get a padlock screen on every reboot. it still boots into whatever rom i have installed though. i'm told that's quite normal, though i'm a little nervous about why it didn't show the first time i rooted.
[Verizon Samsung Galaxy S 4] DarkMenace:
I see the Padlock sometimes and sometimes I don't. It's from being rooted. If you don't like it go back to a stock image. I'll send you a PM how to fix it.
[Verizon Samsung Galaxy S 4] DAANDAV:
thanks
[Verizon Samsung Galaxy S 4] DarkMenace:
It is however quite normal when running a custom rom. I've seen other threads on it.
[About XDA developers] aristobrat:
I've set my preferences here to email me if there are updates to threads I'm subscribed to and am receiving double notification emails.

I'm only subscribed to these threads with one user account and can't figure out why I'm receiving two replies.

Any suggestions would be great!

Jason
[About XDA developers] edsub:
I have this too, maybe an issue caused by the latest breakdown
[About XDA developers] LooxJunior:
The same by my ...
[About XDA developers] aristobrat:
Ok, cool -- just wanted to make sure that there wasn't some user preference that I had enabled somehow... Thanks for the responses! :)
[About XDA developers] xda-rocks:
It's been happening to me since the site came back up after the hack attack.
[About XDA developers] Bonzo:
Someone fix it!!!

PLEASE!
[About XDA developers] taron:
Same problem.

Admins, we need you here :D
[About XDA developers] HPJ:
*God's booming voice* GET ON WITH IT!!
[About XDA developers] j_metselaars:
Yes, I have that too! And it's really annoying! Is there anything that can be done???
[About XDA developers] Bonzo:
Well..

It seems that we have established the fact that many people has this problem.

Now, I've gotten 3 (x2) mails regarding updates on this thread today alone..

Every time, I hope to see a solution posted. But no..

There is just another "Me too" post..

I suggest that we don't post much more in this topic unless there is a solution..

At least not more than one more "Me too" post per day?

Just my two cents..
[About XDA developers] HPJ:
I agree with Bonzo. Everyone stop agreeing with each other!!!!

sorry!! How could I resist an opportunity like that :D :D :D
[Galaxy S I9000 Q&A, Help & Troubleshooting] lg-optimus:
I wiped my system with TWRP and now I am searching for a solution to install an image from an external sd-card or from a pc. I thought I could mount the external sd-card, because there is an option but I can't.
[Galaxy S I9000 Q&A, Help & Troubleshooting] compacity:
try using other sdcard, are u using 16gb microsd? dont know if its work but somehow some sd cannot be recognized by recovery.try different size.
[Galaxy S I9000 Q&A, Help & Troubleshooting] lg-optimus:
I used a 32GB sdcard. I think it is a Patriot. So you mean, it should be possible to mount an external sdcard with TWRP and install from it? In the meantime I could solve it using the advanced options. There was nothing under /sdcard but the install-image under /emmc. So I copied it with TWRP to /sdcard and then thank God the installation worked after a few tries.
[Galaxy S I9000 Q&A, Help & Troubleshooting] compacity:
Well Done! emmc can be recognized by cwm, what i mean before, sometimes (rarely) some external sd cannot be mounted, i m now searching for some info on that, as some of my friends here complaint their cwm cannot detect emmc or externalsd but da card can be access from inside ROM, i try it myself n found several sd (dont know if size n type or class differ) cannot be mounted.

If success then well done
[Galaxy S I9000 Q&A, Help & Troubleshooting] lg-optimus:
I have no idea, if it was important to copy form /emmc to /sdcard. So the img was on an internal partition.
[Galaxy S I9000 Q&A, Help & Troubleshooting] compacity:
most file(any from app or image or etc) will go to internal as system recognized internal as first partition.

if u already solving ur problem then try not to alter anything more as safety.

n sorry if i cant help much
[Galaxy S I9000 Q&A, Help & Troubleshooting] lg-optimus:
Oh yes, I don't touch it again, at least until the next update and things start to fail. I have banned gmail now, it was something with gapps and I had no idea why I got errer messages every few seconds.
[Galaxy S I9000 Q&A, Help & Troubleshooting] compacity:
try clearing cache or dalvik cache
[Galaxy S I9000 Q&A, Help & Troubleshooting] angelori:
me too

for two days now i've been trying to get jellybean 4.1.2 onto my galaxy s plus. i used odin multi-downloader to do the things suggested and when i get to the part involving the zip file on the sd card everything goes south. it gives me a "cannot mount" message and now basically the phone can either be put into downloading or recovery mode. i'm making a last attempt to get something going using the pda button and a zip file. but it's been over an hour now and i don't think i've resolved anything. got this message initially "<1> setup connection..." but the clock just keeps on ticking away.

i'm desperate and feeling stupid. and tired. time for bed. maybe someone can help walk me through this again.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ktulu84:
why are you using odin?:confused:
[Galaxy S I9000 Q&A, Help & Troubleshooting] angelori:
thanks but don't know what to do all the same

being a noob i followed instructions. but i ain't doing anything now. getting the classic phone...!...pc icon. how do i use your advice? if it's advice... thanks for taking the time to write.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ktulu84:
can you go in recovery mode? wich recovery do you have?

EDIT: can you please tell us wich files are you trying to flash through odin?
[Galaxy S I9000 Q&A, Help & Troubleshooting] angelori:
odin

somehow got the phone into download mode again. then WORKED2.rar archive, press the OPS button and select the AriesVE.ops file from the uncompressed archive;

Mark the One Package option, press the One Package button on the bottom of the window and select the recovery-clockwork-6.0.1.0-ariesve.tar.md5 file; got a PASS; but now all i get is the samsung galaxy s plus gt-i90001 on the black background.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ktulu84:
and you cannot go in recovery mode or download mode again?