yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] previse:
i dont mind helping out as im all for getting this to work, but i do have a question regarding "brick". Do you mean wipeing of everything, or just bootlooping into download mode?
[Verizon Samsung Galaxy S 4] sokrboot:
Brick...as in hey everyone look at my new beer coaster!

««I used to be a Serial Flasher...now I'm just a Cereal Flasher.»»
[Verizon Samsung Galaxy S 4] krazy_smokezalot:
obviously he is new so he dont know cuz he is asking. so i would suggest not to even try to test if were him... Brick = your phone is DEAD R.I.P. nothing can be done to revive it lol:p:D
[Verizon Samsung Galaxy S 4] hexitnow:
Screwing up the software by flashing a recovery on me7 and being put in download mode isnt really a soft brick because you can still get the phone to boot, you just dont have any kind of recovery.

Soft brick = software related, phone wont boot and can be fixed

Brick/hard brick = can be software and hardware related, no fixing it.
[Verizon Samsung Galaxy S 4] previse:
Thank you for being kind enough to answer logically.
[Verizon Samsung Galaxy S 4] jlee85:
Lol
[Verizon Samsung Galaxy S 4] r_hippy:
7L7419319H312702U didn't have a sec to send u anything for your hard work, then the phone issue :( have lunch on me. By the way how did the phone come out? they are 30 minutes from me, I need a screen for my daughters s4.have a good one.

I also sent u a message on hangouts not sure if it was u?
[Verizon Samsung Galaxy S 4] Surge1223:
In addition, I also tend to think of it as a hard brick only after I have attempted every solution I can think of, and ran out of google results that would be helpful. But today, I couldn't get my mdk to boot into recovery, android os, or download mode. However, I still managed to eventually get it in odin mode and after flashing the stock mdk kernel im completely back in business. I think a hard-brick depends at least to some extent, on the owner's own knowledge and willingness.
[Verizon Samsung Galaxy S 4] Alxoom33:
Let's be very clear about this:

BRICK=VERY BAD!!!

You don't want to brick:mad:
[Verizon Samsung Galaxy S 4] mrro82:
How in the world are we bantering over what a brick means to our phones? Seriously guys. We all know what it really means to brick and if you don't, you have no business messing with anything besides the power and home button.

Sent from the other side of the Milky Way with my S4.
[Verizon Samsung Galaxy S 4] Alxoom33:
Geez, some people lack all evidence of a sense o humor! LOL:D
[Verizon Samsung Galaxy S 4] klick37:
I want Hash to work on this so he can get the bounty almost as much as I want him to work on it so I can have it. Think of what magical android things a talented developer like him could do with a few thousand bucks in spending money. Hookers, blow and safestrap. Hell yeah.
[Verizon Samsung Galaxy S 4] hexitnow:
At one point you didnt know what it was either. Everyone has to learn somewhere and sometime. Cut him/them some slack.

Enough of the off topic chatter for me though.
[Verizon Samsung Galaxy S 4] littlebigarm:
That's what I'm all about
[Verizon Samsung Galaxy S 4] DeadlySin9:
He actually said he doesn't dev for a bounty, and said to leave the bounty open for a full bootloader unlock actually. He did say he'd accept donations as a thanks after he gets SS working. Nice as that bounty would be to anyone, lol.
[Verizon Samsung Galaxy S 4] sob372:
Hey so I know we can flash roms that have stock kernels but I know that a lot of me7 roms use the mdk kernel bc of loki and me7 kernel not being compatible with it so can someone tell me if mdk kernels are safestrap friendly.

Edit: and what about flashing mods I havent seen any posts about that
[Verizon Samsung Galaxy S 4] DeadlySin9:
As far as I know, the kernel should not be an issue, and if it is then we'll have kexec at some point (read through the thread for what that is).

As for flashing mods, they will work fine in custom slots. As for flashing mods to the stock system, that will be enabled later.
[Verizon Samsung Galaxy S 4] sob372:
thanks. i saw the custom slots and stock slot and have no idea what it is so ill have to do some more reading. i attempted to flash bonestock 1.1.4 vruame7 and vruame7 stock root deodex and both attempts failed multiple times pretty much immediately. the first attempt of each was about 2 minutes then after that each attempt was about 2 seconds. am i doing something wrong? i just hit install and it says stock slot or rom at the top in red letters. im using odin to return to stock right now
[Verizon Samsung Galaxy S 4] bfmetcalf:
SafeStrap isn't fully functional yet and the ROMs will have to be built for SafeStrap. You can't flash anything in it yet.......

Edit: this is from the second post in this thread...

I suggest reading very thoroughly if you are going to be flashing ROM's or you WILL end up with a brick...
[Verizon Samsung Galaxy S 4] mmw68666:
It's not complete yet
[Verizon Samsung Galaxy S 4] rebel1699:
If you are talking about flashing roms in this ss for S4, than the reason it is not flashing is because SS is not yet complete. That is why it is still a wip. Read the op, so you dont brick your device. The download in the op is a "proof of concept" only, as clearly stated.
[Verizon Samsung Galaxy S 4] mmw68666:
Amen read read and read again
[Verizon Samsung Galaxy S 4] HORiZUN:
Sob372, read the first two posts. Twice.
[Verizon Samsung Galaxy S 4] sob372:
i read multiple posts that said its ready to flash custom roms as long as they have stock kernel
[Verizon Samsung Galaxy S 4] mmw68666:
What did you read
[Verizon Samsung Galaxy S 4] sob372:
i just told you what i read. that you can use ss to flash roms that have stock kernel
[Verizon Samsung Galaxy S 4] mmw68666:
Where did you read that
[Verizon Samsung Galaxy S 4] sob372:
i think i started at 48
[Verizon Samsung Galaxy S 4] bfmetcalf:
Always...ALWAYS read the first posts by the person doing the work. They will give you a much better idea of things than starting reading in the middle of a huge thread... start at the beginning

Edit: people almost always update the first few posts with relevant info...
[Verizon Samsung Galaxy S 4] mmw68666:
I agree 100%
[Verizon Samsung Galaxy S 4] sob372:
yes yees indeed ok thanks for replies
[Verizon Samsung Galaxy S 4] hexitnow:
If youre flashing an me7 rom with an mdk kernel why would you use SS since you already have a custom recovery.

If I helped you hit that thanks button please. Doing a little bit of reading goes a long way. Sent via tapatalk.
[Verizon Samsung Galaxy S 4] sob372:
never said i had custom recovery
[Verizon Samsung Galaxy S 4] krazy_smokezalot:
Ditto:what:

S4 on a SAD ME7 Build
[Verizon Samsung Galaxy S 4] hexitnow:
One would assume you did because of what you posted prior. If you tried it with safestrap well then you make me lol

Quoted from hashcode

YOU CAN AND WILL BRICK YOUR DEVICE IF YOU DO ANY OF THE FOLLOWING:

Attempt to install any ROMs -- there are no ROMs which will work with this yet. That comes in phase 2.

Backup -- The /data/media store is being counted as part of /data and you'll create a humongous useless backup.

Restore -- This needs to be tested once the other bugs are fixed on an unlocked device where ODIN restore isn't a big deal.

If I helped you hit that thanks button please. Doing a little bit of reading goes a long way. Sent via tapatalk.
[Verizon Samsung Galaxy S 4] sob372:
I make you lol? Whatever bro
[Verizon Samsung Galaxy S 4] rebel1699:
Just get past it. If you are going to do something like not read the big bold warning in the op, and risk bricking your phone, then ask why it wont work, you should expect a little teasing. Just take it as a learning experience and proceed on. Honestly, if someone sticks thier pen above thier ear, then look all over because they cant remember where they put it, its always funny. Personally, im still trying to live down the time I went into panic because i could not find my phone.......while talking to my wife on it. She still laughs at me. I laugh at me too. :)
[Verizon Samsung Galaxy S 4] sob372:
First I dont get why your telling me to get over something when I was totally done until your post. And second, I read the op, and I misread what a few others posted and thought maybe the op just wasnt updated so id give it a try. I made a mistake big ****ing deal. I disagree with what youre saying. people I dont even know have nothing better to do then worry about the mistakes im making. You think thats alright? That is def not what this thread is for. Someone responded respectfully and thats fine. Wtf need is there for anyone else to say something and be disrespectful about it at that? Get a life.

Mods please clean this useless **** up
[Verizon Samsung Galaxy S 4] rebel1699:
People you dont know are worried about the mistakes your making, because you asked them to, when asking for help as to why installing roms didnt work, openly in the thread. My previous post was actually lighthearted. There are some on here that would have crucified you. If you look back, I was one of the ones that "nicely" responded to you in the first place. :)
[Verizon Samsung Galaxy S 4] Addiso:
Whoa, ladies. Can't we all have a drink and wait patiently for SS and not have this thread locked just like the bootloader one?
[Verizon Samsung Galaxy S 4] sob372:
No you responded after 20 other people did. Your missing the point. Ehats the need for 20 diff people to say the same thing and take up 3 pages? I told you, someone responded and I was informed. Explain to me why you think its necessary for 10 people to do so afterwards.
[Verizon Samsung Galaxy S 4] osukef:
Just stop. Please.
[Verizon Samsung Galaxy S 4] Hashcode:
Please keep it civil.

On a side note, the DevDB thread is now up:

xdaforums.com/showthread.php?t=2441441
[Verizon Samsung Galaxy S 4] black_label:
How can we donate to hash? he should make a donate version on the play store.
[Verizon Samsung Galaxy S 4] hexitnow:
I think he said he was going to with a .99 cent price tag. Im pretty sure that was posted in the thread at one time. His paypal donation link can be found on his user profile.

If I helped you hit that thanks button please. Doing a little bit of reading goes a long way. Sent via tapatalk.
[Verizon Samsung Galaxy S 4] Hashcode:
I need a couple of things confirmed by ME7 users on the new B07 build of Safestrap here (since my device has a MDK kernel on it):

http://xdaforums.com/devdb/project/?id=550#downloads

Make sure you download the APK, click on it to install, and then once inside the APK use the "Install Recovery" button.

1. Can you see the splashscreen during the reboot

2. Can you tap the soft home key next to the center button to enter recovery

3. Is the UI now rendering properly (for the most part) while in recovery?

As I get time, I'm going to loki the stock ME7 kernel and apply it to my device for better testing.

Also, I'm testing some ROM candidates for flashing in SS and debugging the ROM boot process.
[Verizon Samsung Galaxy S 4] my-blue-snog-box:
I know this isn't what you requested, but I tried it on my SGH-I537 with MF1 and the UI is MUCH more responsive. Also, I can confirm that I got the splashscreen upon reboot!
[Verizon Samsung Galaxy S 4] DeadlySin9:
Not ME7, but can confirm working on MF3 (AT&T). However, the continue button on the splash screen seems to do nothing, and my phone is actually no longer booting right after testing ADB (push and pull on build.prop) and backing up stock. The screen stays black afterwards and the LED comes on blue and pulsing. It did reboot fine before trying that.
[Verizon Samsung Galaxy S 4] black_label:
just updated to latest safe strap.

1. yes

2. yes

3. yes

I'm so excited for this hash! Can't wait for finished product. BTW Im on ME7 / Verizon S4
[Verizon Samsung Galaxy S 4] Hashcode:
You'll need to make sure that the build.prop has 644 permissions.

Reboot into recovery.

Mount system from the "Mount" menu

adb shell

chmod 644 /system/build.prop

exit

and try rebooting again.
[Verizon Samsung Galaxy S 4] rebel1699:
At&t Mf3

Reboot to recovery working correctly.

Splashscreen visible. Recovery soft button works. Continue soft button does nothing.

Ui much clearer and responsive.
[Verizon Samsung Galaxy S 4] DeadlySin9:
Figured that out right before i came back to say i got it, did it all through SS instead of terminal though. Thanks!
[Verizon Samsung Galaxy S 4] my-blue-snog-box:
Video of SS on I537 confirming splashscreen:

https://www.youtube.com/watch?v=Q50oTMnkkjg&feature=youtube_gdata_player
[Verizon Samsung Galaxy S 4] msterwolf:
I am running ME7, and have the B07 build install.

1. YES

2. YES

3. YES

:good:

EDIT: Something I might add is that the soft key for "continue" in the splashscreen seems to be somewhat unresponsive.
[Verizon Samsung Galaxy S 4] twizzlejr:
Ran thru it but for some reason I get to the splash screen and it won't let me press either button and it says safestrap is enabled am I doing something wrong
[Verizon Samsung Galaxy S 4] rebel1699:
Are you tapping right on the word "recovery" or the soft button below it (normally the menu button)? Just in case, it is the soft button you need to press.
[Verizon Samsung Galaxy S 4] twizzlejr:
That might have been my issue ha thanks should I be cocerned at all that it says safestrap is disabled
[Verizon Samsung Galaxy S 4] rebel1699:
I dont think its suppose to be saying enable yet. Mine says disabled too.
[Verizon Samsung Galaxy S 4] thunderbls:
Yes on 1, 2 and 3 here on ME7
[Verizon Samsung Galaxy S 4] killajoe:
Can't wait to rom!!
[Verizon Samsung Galaxy S 4] thunderbls:
Me either but I will : ) I think I saw a posting earlier about going through flashing withrawals, thats me lol
[Verizon Samsung Galaxy S 4] Surge1223:
Well im on MDK so I don't know how much this helps but I dont get the splash screen but i can tap the the area you speak of to enter recovery.

The UI is a lot better. Interestingly I did finally get test 4 to pass. Also adbd was able to connect to connect to 5037 and so my pc was able to find it when i ran the adb devices command. So adb access from recovery and adbd are working but I didn't try to push or pull anything.

1.No

2.Yes

3.Yes

Edit:Splash screen showed upon second boot

1.Yes

2.Yes

3.Yes

P.S. I havent tried uninstalling it yet but If it was a success, then I would have sucessfully passed Tests 1-5. I don't know how much of that is due to me being on MDK though so sorry if its not helpful.
[Verizon Samsung Galaxy S 4] SamuriHL:
Looks like you're making some fairly steady progress! Great work man!

Carved in blood by a wakizashi...
[Verizon Samsung Galaxy S 4] jlopez1286:
quick question Hash, as you continue to develop SS.. Would it be just Verizon specific or would it continue to work on AT&T?? I know last time you said that eventually it would need two different signatures for it to work, if i remember correctly. Also Thank you for all your hard work!!
[Verizon Samsung Galaxy S 4] chapsizzle71:
Confirmed working.

Rebooted from SS to recovery - yes

Boot to recovery with soft keys - yes

Thanks for your hard work.
[Verizon Samsung Galaxy S 4] sokrboot:
All systems go! Nice work Hash! Thank you for your time and energy.

««I used to be a Serial Flasher...now I'm just a Cereal Flasher.»»
[Verizon Samsung Galaxy S 4] :
If you looked a couple pages before this one, AT&T users were trying it out as well and got similar results as Verizon users...

Sent from the best phone in the world.
[Verizon Samsung Galaxy S 4] rebel1699:
He was talking about how the roms would have to be done a little different than verizons to make them compatible with SS. SS itself, should be primarily universal.
[Verizon Samsung Galaxy S 4] krazy_smokezalot:
Ui works fine hopefully this gives you the green pight to move to the next step!:thumbup::D

S4 on a SAD ME7 Build
[Verizon Samsung Galaxy S 4] thunderhorse:
Thanks!

After reading through 57 pages, I joined the forums just to say thank you to Hashcode; installed SS 3.5 B07 on ME7 and got Yes to all 3. Finally done missing the ease of doctoring WebOS!
[Verizon Samsung Galaxy S 4] Alxoom33:
A little nervous about trying this on an encryopted S4 running ME 7. Has anything been done to potentially prevent the bootlooping issue that I encounters last week? If I am to test this again, it will need to be over the weekend when I could Odin back the System.tar if necessary. Thoughts?
[Verizon Samsung Galaxy S 4] krazy_smokezalot:
Read this page and a few page back since this bo7 update NO ONE HAS HAD ANY BOOTLOOP! GUARENTEED :D:thumbup:

S4 on a SAD ME7 Build
[Verizon Samsung Galaxy S 4] lazer9:
I would heed caution if on an encrypted phone. Hash hasn't changed the big RED warning in the OP yet.
[Verizon Samsung Galaxy S 4] krazy_smokezalot:
Thanks but I work at Verizon so you know :rolleyes::rolleyes::p:D:thumbup: lol but anyways if its a brick oh wellbi for one dont care as long as progress is being made know what I mean... but im juat rooted only on ME7 and tried the B07 update I did exactly what hash said to do and NOTHING ELSE didnt try to flash a rom because obviously its not ready as of yet..:thumbup:

S4 on a SAD ME7 Build
[Verizon Samsung Galaxy S 4] sokrboot:
FYI this is Hash's post from the SS Dev thread he JUST created 8 hours ago...

*** DISCLAIMER ***

...CURRENTLY THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.

CURRENT PROJECT STATUS:

Proof of Concept Build Testing

WHAT IS SAFESTRAP?

Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.6.1.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:

1. Here you can create virtual ROM-slots (2 on the S4 due to partition size and internal space) for flashing ROMs. These ROM-slots allow for 3 different sizes of /data partitions: 1GB, 2GB and 3GB. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.

2. You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.

3. Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.

For more information you can read up here:

http://blog.hash-of-codes.com/how-t...al Flasher...now I'm just a Cereal Flasher.»»
[Verizon Samsung Galaxy S 4] SamuriHL:
Two things....it hasn't been updated and I don't think Hash has encrypted his phone to look at it. However, since test 1 now works, it MIGHT in theory work now. BUT, I would wait until you can quickly fix it like we did last week. It's much safer to know you can just fix it immediately rather than risk it and not be able to.
[Verizon Samsung Galaxy S 4] krazy_smokezalot:
What does encryption mean mean first of all!?!??? :confused: not rooted?

S4 on a SAD ME7 Build
[Verizon Samsung Galaxy S 4] sokrboot:
Usually phones are encrypted or password protected when used for work/business/enterprise. Its a security feature.

««I used to be a Serial Flasher...now I'm just a Cereal Flasher.»»
[Verizon Samsung Galaxy S 4] SamuriHL:
Um, NO. It means the data partition is encrypted and you have to enter a pwd every time you boot. The warning is in there due to the issue he encountered last week. Considering he's the only one that's tried it, him asking is probably not a bad thing. It was a pain to fix his phone the first time. Fortunately he's in a better condition to do so this time if it still doesn't work.
[Verizon Samsung Galaxy S 4] krazy_smokezalot:
Oooh like the option encrypt sd card I think thats what it is called if thats the case... IT DOES NOT APPLY TO ME:p:D:thumbup:

Basically if your encrypted and you dont read and you install this then thats not one fault but yours

S4 on a SAD ME7 Build
[Verizon Samsung Galaxy S 4] sokrboot:
Yes I agree.

««I used to be a Serial Flasher...now I'm just a Cereal Flasher.»»
[Verizon Samsung Galaxy S 4] jzmax22:
Quick question where do find the link for b07 ? I looked in the OP, but the link there is for b02. Thanks in advance.
[Verizon Samsung Galaxy S 4] thunderhorse:
B07 here ya go
[Verizon Samsung Galaxy S 4] jzmax22:
Thank you sir! Much appreciated. And a big thanks to Hashcode.
[Verizon Samsung Galaxy S 4] thunderhorse:
He is a godsend for those of us who got a phone with ME7 already installed!
[Verizon Samsung Galaxy S 4] Jayrod76:
It's nice to know that if my MDK craps the bed that I will hopefully be able to continue to ROM on ME7. I am grateful for those smarter than I to do things like Loki and other B/L alternatives such as SS. This is the last time I do this. I knew Loki would be patched eventually and am treating my phone well..but stuff happens! Dev or GPE from now on.

Sent from my Platyraptor extreme ultra maxxxx 4gLTE/GSM/ABC/123 Nick Knack Pattywack Ermegherd GED, MD,RNA,DNA,YMCA Edition S4! Via the 4th dimension....NOW RUNNING ECLIPSE
[Verizon Samsung Galaxy S 4] deadenz:
Will this work for the at&t galaxy s4 with mf3 update?
[Verizon Samsung Galaxy S 4] hexitnow:
Wheres the request?

Ok thanks.
[Verizon Samsung Galaxy S 4] Alxoom33:
I think that it may have to be customized, but not sure...I know the 3.11 version worked for both the Bionic and Razor.
[Verizon Samsung Galaxy S 4] snarlytaz:
MDK Possibilities?

This might be slightly off topic but I am curious of MDK possibilities, maybe some others would be curious too.

I have my own slim debloated ME7 rom running on my MDK/Loki with Kloontz TW Kernel. If that were my safe stock setup, could in theory SS be installed to run roms in slots so long as the rom was Kloontz TW compatable? Or aosp roms using aosp kernel installed first via Loki, etc...

Would the true TWRP/Loki recovery stay in tact and/or ODIN flashabe back to MDK on soft brick?

On D3 I always did a base custom rom first then would SS to other roms but that was on locked bootloader with no custom kernel.

Just curious as others may be too.
[Verizon Samsung Galaxy S 4] Pepsistopheles:
So if I install Safestrap then my ROM of choice, I could delete the stock TouchWiz ROM once it was set as inactive? I'd love to free up that space if it's possible.
[Verizon Samsung Galaxy S 4] Alxoom33:
On the Bionic, HC and D Hacker were developing kexec custom kernels to be able to develop CM10.1, AOKP, Liquid and other AOSP roms that run on SS. Simply put, as I understand it, the kexec kernal loads side by side with the origonel kernel and takes over. I believe it is called a hijack.:p

---------- Post added at 01:14 PM ---------- Previous post was at 01:12 PM ----------

No, Lol! The OS and the custom recovery have to be SS compatible. :cowboy:

---------- Post added at 01:27 PM ---------- Previous post was at 01:14 PM ----------

No, no no no no! No, you keep the Stock Rooted rom in the "Safe" partition, put your custom roms in the unsafe slots to play with....Reason, if one of the test roms craps out you don't brick, you go back to your "safe" rom and then fix the problem, or go back to the unsafe side to a rom that works. It's the best of all worlds... no softbricks, unless you do something really stupid to kill your safe rom and/or Safe Strap at the same time.:cool:

---------- Post added at 01:31 PM ---------- Previous post was at 01:27 PM ----------

Too bad Developer or GPE was not offered by Verizon. Still verizoning us to this day...:D

Hope you are enjoying your knick nack patty whack etc...S4. Keep up your theams....:cool: