yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] superblox02:
Hey all!

I recently dug my old Galaxy S3 Verizon out of my drawer to install a custom ROM on it and use as a music player.

Tell me if there's something I'm doing wrong in this process to install SlimKat (my favorite rom type, it has a unified build for all d2 phones)

Towelroot -> Check root -> Download Busybox & other requirements -> Install Safestrap -> In Safestrap, do factory reset -> Patch ROM, GApps & BMS Kernel (the rom auto-formats /system) -> Reboot

And then it just bootloops. It has a green light in the top right, staying on while the logo for SlimKat just stays there, flashing in & out forever and ever.

Either I'm doing something wrong during the install or I'm just too impatient to wait for first boot, but I'm pretty sure it's the former.
[Verizon Samsung Galaxy S III] ShapesBlue:
If its on the official OTA of either 4.3 or 4.4.2 it's on a locked bootloader. Custom roms can no longer be installed. So for it to run a custom rom other than the bootloader locked roms of 4.4.2 it won't work. There were several to choose from on the 4.3 locked bootloader that were TW(touchwiz) based

Sent from my Nexus 5
[Verizon Samsung Galaxy S III] superblox02:
Aww. Looks like I'm stuck on stock. :(
[Verizon Samsung Galaxy S III] ShapesBlue:
Correct. The only true option to go back to a previous version is a jtag service

Sent from my Nexus 5
[Verizon Samsung Galaxy S III] superblox02:
Well I finally got mine running through a bootstrap, currently running SlimKat 9.0 Stable w/ Quantum Kernel. WiFi won't turn on. I'm sitting on "Select Wifi" in setup wizard, and it's just stuck at "Turning WiFi on..." I know MTP won't work but I can transfer another kernel through ADB if I need to. Anyone have any advice?
[Verizon Samsung Galaxy S III] afaneh92:
No you cant flash or adb custom kernel to a locked bootloader
[Verizon Samsung Galaxy S III] superblox02:
Oh, so I have to use the stock kernel included with my ROM? Or will I not get it to work at all?

Edit: Well, I just did that, and I still have the issue :/

Maybe it's because my ROM already includes a built in kernel.

I'll look into the file infrastructure some more.

Edit 2: There is indeed a boot.img in there, presumably a bootloader. Does SafeStrap use the same bootloader & kernel as stock?
[Verizon Samsung Galaxy S III] afaneh92:
safestrap recovery didnt flash boot.img it skip it during rom flashing.

as I said before we cant get WI-FI or any kernel driver working on aosp rom until somone built this rom with hacked driver with modify device tree.
[Verizon Samsung Galaxy S III] superblox02:
Hmm. I'll see if I can find a SafeStrap-compatible version of the ROM, if not I'll use some other ROM. Thanks for the help!
[Verizon Samsung Galaxy S III] rcwaszak:
Galaxy S III Mini G730V and Unofficial Safestrap

Hi Mohammad, I've tried a few different versions of Safestrap including the Unofficial 3.75. My question is whether or not there is a Safestrap version that works on the Galaxy S III Mini (Verizon). The best I can do is get 3.75 installed but no splash screen (holding the menu button while booting does take me into Safestrap though). However, once in Safestrap the screen objects are very large and do not fit on the screen and I can't swipe, squeeze, or otherwise scroll the screen to see all the options. The options that I can see and click on seem to work ok.

Device SM-G730V

Version 4.4.2

Baseband G730VVRUBNE2

Kernel 3.4.0

Build KOT49H.G730VVRUBNE2

Hardware G730V.05

thanks, richard
[Verizon Samsung Galaxy S III] afaneh92:
Ok I will build it for you but I need more info and if there a working device tree.

I will try on week end.
[Verizon Samsung Galaxy S III] rcwaszak:
Some Screen Shots

Hi Mohammad, Thanks. Attached are some screen shots . . .
[Verizon Samsung Galaxy S III] afaneh92:
dont mess up with recovery you will brick your device. and dont ever flash recovery of different device.

copy and paste what in proc/partition from any root file explorer.
[Verizon Samsung Galaxy S III] rcwaszak:
proc/partitions file

Hi Mohammad, sorry for the delay. I used the .doc file extension just to get the file to upload. The file should be a copy of proc/partitions. If you want me to run commands from the terminal emulator and pipe them to a text files I can do that and send them to you.

thanks again.
[Verizon Samsung Galaxy S III] afaneh92:
thats enough will pm you with new build when it ready.

the apk layout is ok? or need to resize!

Edit: a test build is ready ckeck your inbox.
[Verizon Samsung Galaxy S III] LimpRiku:
So if I'm currently running android 4.2.2 on a SCH-i535 can I update to Kitkat, but a ver before they locked the bootloader? Or is my bootloader already locked? I'd really like to flash a new rom. It's been literally years (as per my 4.2.2 android ver) :p
[Verizon Samsung Galaxy S III] ShapesBlue:
The VZW S3 was never updated to 4.2.2 it went from 4.1.2 to 4.3 and then 4.4.2

Sent from my Nexus 5
[Verizon Samsung Galaxy S III] afaneh92:
its seem you are on unlocked bootloader!

your rom is custom if not you are on 4.3 or 4.1 and upgrade to 4.4.2 will lock your booloader.
[Verizon Samsung Galaxy S III] ShapesBlue:
4.2.2 is not a valid android version on the VZW S3. As I previously mentioned there are only versions 4.1.2 followed by 4.3 then 4.4.2. There never was a 4.2.2 version

Sent from my Nexus 5
[Verizon Samsung Galaxy S III] o8o.o0880o.o8o:
I'm pretty sure that was a typo in regards to 4.4.2 which the bl is locked. Sorry guy. Also from what I gathered 4.3 locked to the boot loader, not 4.4.2.

*edit* I meant 4.3 locked first, not that 4.4.2 didn't lol

---------- Post added at 04:06 PM ---------- Previous post was at 04:03 PM ----------

Sadly enough I'm still waiting on any progress with ss 3.75 running cm but any time I bring it up you all act like it never happened. What's up?
[Verizon Samsung Galaxy S III] ShapesBlue:
While true and all about the android version number it's always nice for people to respond when myself or others respond. I grow tired of constantly repeating myself. And both 4.4.2 and 4.3 ML1 are bootloader locked

Sent from my Nexus 5
[Verizon Samsung Galaxy S III] o8o.o0880o.o8o:
I'm not sure why everyone seems to jump to conclusions without reading the whole forum. I've been waiting on answers to this post for a while now but all I hear is Locked BL, you can't do that.
[Verizon Samsung Galaxy S III] ShapesBlue:
I have been following the forum since the beginning and even though I don't have a locked bootloader I know enough about this that you can hard brick your phone trying to install a custom rom.

As I've said before and I will say it again your more than welcome to attempt to flash a custom rom and hard brick your phone. I've seen many people around here attempt to do so and indeed hard brick the phone. Verizon locked the bootloader down thanks to both them and Samsung.

But if you want to believe that there's a small possibility that you will be able to run a rom that will never work more power to you

Sent from my Nexus 5
[Verizon Samsung Galaxy S III] maddstealth:
I remember the ree locked bootloader days... It was four score and seven years ago...

In all seriousness, though, yeah there was definately a time where the bootloader was unlocked, or at least could be unlocked, and from there installing a new ROM was relatively easy. Used the phone to euphoric bliss with Cyanogenmod installed up until around January of this year when the phone's screen died. Got a new copy, tried to install Cyanogenmod again, and ended up locking myself outside of Recovery.

I've tried the Safestrap method, every version of v3.75 from B01 to B04, and while the application installs properly and apparently installs the recovery properly, given the fact that it shows the option to reboot to recovery, when I try to do so, it just reboots in the standard fashion. What's more, I've read in the thread that one should be able to spot the splash screen during boot (only lasts a second IIRC), but I've tried watching for it through a full 30 minutes of rebooting, and haven't seen it even once.

Has anyone else dealt with this or am I the only one doing something wrong?
[Verizon Samsung Galaxy S III] afaneh92:
SPLASH_RECOVERY_KEY := KEY_MENU

SPLASH_CONTINUE_KEY := KEY_BACK

SPLASH_DISABLE_KEY := KEY_HOMEPAGE

these are function keys of splashscreen so homepage key will disable it.

maybe it hardware issue.
[Verizon Samsung Galaxy S III] maddstealth:
And whaddaya know, that worked like a charm! xD

I swear, I've been reading up on this all over the place, but never say anything about those hotkeys, but thanks regardless! I'm about to back up the system and give installing the cyanogenmod rom a shot. I'll check in if I run into any obstacles. :)

EDIT: Soooooo... Does Safestrap support the installation of Lolipop ROMs?

EDIT_DOS: NVM, I reviewed the OP; stuck with the Superlite ROM. Welp, that and NovaLauncher will be plenty usable. :)

EDIT_TRES: Okay, serious issue. Ever since Safestrap has been enabled and I figured out how to create custom rom slots, the WIFI will not toggle. Whether I'm using the PaulRizz ROM or the stock ROM, I cannot get the wifi to toggle out of gray. I've tried restoring my backup copy of the stock, I've tried clearing all the caches, and I've even done the factory restore on the Stock ROM but nothing works. Help?
[Verizon Samsung Galaxy S III] smithmal:
Confused....

I had Safe Strap v3.71 official and I was unable to activate any ROM slots. I've now installed this patched v3.71 (I had to install twice by the way as the first time, I got a black screen after going into recovery; the only way to get my phone back up was to pull the battery) and still, I can't activate any of the ROM slots.

Wasn't this version suppossed to allow my to activate a ROM slot so I could install a Safe Strap friendly ROM?

Thanks,

smithmal
[Verizon Samsung Galaxy S III] maddstealth:
Have you adjusted the space allowance for data? I had this same issue, but found you have to make sure there's enough to accommodate the current disk space being used by the Stock Rom.
[Verizon Samsung Galaxy S III] LinuxHippy:
ok, it's been a couple of months since I checked in here and I see now that the unofficial bootstrap has gone through some revisions. I have a Verizon S3 running 4.4.2 which is of course a locked bootloader. I rooted it and then following this thread installed bootstrap B02 I went back to the first post and downloaded the upgraded apk file for B03,4,5 checked the md5sums and then pushed them to my micro SD. After making sure Busy Box was up to date and rebooting I then went to update bootstrap. Following that first post I uninstalled bootstrap inside it's app and then state said uninstalled. Then I went to a file browser to where all the bootstrap apks were and pushed on each one from B05 back to B02 and B02 is the only one that would install. The others stopped after the first install screen with "app not installed".

So what did I do wrong here?

Marty

:(
[Verizon Samsung Galaxy S III] afaneh92:
Did you tryied flash the modules in superlightrom download area.

does busybox installed correctly.

try uninstall the apk too then reinstall the new one, upgrade will fail.
[Verizon Samsung Galaxy S III] LinuxHippy:
That worked. Sorry to have wasted your time with such an obvious answer. I should have seen it... embarrassing!

Once I did the uninstall in safestrap, I went outside safestrap and uninstalled it's apk.

Thanks for your help again mohammad.afaneh! I did a reboot into recovery and that works.
[Verizon Samsung Galaxy S III] smithmal:
Ahhh.... this is probably it.

Looks like there are three partitions that you can adjust per ROM slot:

System size

Data size

Cache size

From what I can see, the minimum partition size allowed by Safestrap allows for data and chache is 1GB and 300MB respectively. The system size is 1.5GB and cannot be adjusted (at least pressing "+/-" does nothing to adjust the size of the system partition.

Safestrap reports my current "Free Space" @ 525 MB so even if ROM Slot 1 is dialed back to its minimum size (which would equate to 2.8GB), I still don't have enough room to add a new slot. I believe the S3 has an internal storage size of 32GB. How much storage are most people taking up with their Stock ROM? Is the most efficient way to reduce the Stock ROM size to remove apps or are their other "tricks" people are using?

smithmal
[Verizon Samsung Galaxy S III] afaneh92:
I will reduce minimum system size to 1G in next build.

Most d2vzw devices are 16GB.

I will fix my device soon.
[Verizon Samsung Galaxy S III] wiab:
Viper4

Can Viper4 be installed with the SuperliteROM?
[Verizon Samsung Galaxy S III] ShapesBlue:
Good question. If you can do a backup first I would, then attempt to install it

Sent from my Nexus 5
[Verizon Samsung Galaxy S III] Sohaib-alm:
Yes it can be installed:) I've tested it in SUPERLIGHTROM but that will make ur battery drain :(

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Sea23.vn:
Help me. I need Rom for Safestrap

Thank!
[Verizon Samsung Galaxy S III] Bbakes2012:
Please read the entire frist two posts from the OP before you ask a question. The second post contains links to SUPERLIGHT rom and PaulPizz. As far as completely functional roms those are the only two.

Here is a link to the second post:

http://xdaforums.com/showthread.php?p=53731742
[Verizon Samsung Galaxy S III] ShapesBlue:
If people read things xda would be useless lol

Sent from my Nexus 5
[Verizon Samsung Galaxy S III] maddstealth:
Another Satisfied Customer

Hello! I've recently installed the SUPERLIGHT! rom and just wanted to say OH MY GAwD, this feels so gooooooood! Granted there are a few things I still have to deal with using the Touchwiz interface, mostly that "Recommended Shortcuts" portion of the pulldown menu and that annoyingly pesky habit of the OS to force me to change the input device method to from the Thumb Keyboard that I use to Samsung's crappy keyboard when I connect my Bluetooth keyboard, but overall, this phone is much faster, more responsive, and bareable now, especially w/ the Nova Launcher. I'm figuring out how to handle the second issue, but does anyone know how to get rid of the first?

Also, and far more importantly, I have the Stock Rom saved on an Micro SDHC card, and would like to scrap it from the stock rom so I can use the SUPERSTOCKED ROM exclusively, if possible (AH WANT DAT SPACE!) So...is it possible? At least, is it possible without softbricking the phone and erasing the Safestrap Recovery?
[Verizon Samsung Galaxy S III] LinuxHippy:
I wiped stock from the device after making a backup and testing it in slot 1. I then copied the backup to my computer and checked the md5sum in both places to make sure they copied ok. SS didn't disappear when I wiped stock.

I posted this here:

http://xdaforums.com/galaxy-s3-verizon/development/rom-superliterom-v1-0-i535vrudne1-t2805797/page18

It's on page 18 if it doesn't take u there post 172.

Marty
[Verizon Samsung Galaxy S III] fdigl:
After I tap install, the status remains not installed. I'm on stock rooted NE1, is there anything I can do?
[Verizon Samsung Galaxy S III] LinuxHippy:
Did u install busy box software after the busy box app installed?
[Verizon Samsung Galaxy S III] fdigl:
Yes, busybox is installed.

EDIT: After starting fresh via ODIN the status is installed once I tried again, but I am unable to get to the safestrap pre boot screen nor the safestrap recovery. It just boots straight to system.
[Verizon Samsung Galaxy S III] LinuxHippy:
I had problems at first with build 5. Try an older build.

Marty

---------- Post added at 08:29 PM ---------- Previous post was at 08:10 PM ----------

Is your security setting changed to allow installation of apps from unknown sources? Also after app installs the software will want to download added software like busy box did.

Marty
[Verizon Samsung Galaxy S III] fdigl:
I'm on build 5, but I'll try an older one. And yes, I enable Unknown Source application installations as soon as I get a phone or flash a ROM since I tend to sideload some apps.

EDIT: I can safely report back that build 4 is functional and working.
[Verizon Samsung Galaxy S III] LinuxHippy:
Cool! I had no problems on build 2 but did with build 5. I couldn't get build 5 to install the super lite ROM 3 at first but after rebooting a number of times it took. Not sure why, but it seems buggy.

Marty
[Verizon Samsung Galaxy S III] Sea23.vn:
Can i flash SUPERLITEROM on Stock ROM slot?

(Samsung Galaxy S3 Verizon 4.4.2 Stock install Unofficial Safestrap Recovery v3.75 B05)
[Verizon Samsung Galaxy S III] LinuxHippy:
Yes, see post 295 on last page.

Marty
[Verizon Samsung Galaxy S III] dwh2o13:
New to the thread and have read about half of it. Also new to modifying the galaxy s3. Here is where I am.

Rooted via towel root, installed busy box, and have the safestrap apk on the phone. Just want to confirm I'm on the correct build. Screen shot below.

Also can exposed be used?
[Verizon Samsung Galaxy S III] LinuxHippy:
That screenshot looks like you're good. I'm not sure what exposed is. If it's a ROM, I've not heard of it from reading threads that have to do with a locked boot loader.

Marty
[Verizon Samsung Galaxy S III] dwh2o13:
Exposed Framework. When this apk is installed, you can then install various modules to customize your phone. Early in the thread I thought I read that it didn't play well with this version of safestrap
[Verizon Samsung Galaxy S III] dawgdoc:
I just picked up an i535 this week in the same condition as yours. I found it cheap and grabbed it a a backup device before learning that the verizon locked bootloader was more restrictive than simply not being able to be downgrade as on my i747.

Anyhow, xPosed is working for me. So fa I have only installed two modules; xPrivacy and PlayStorePermissions, No issues so far.

I rooted with Towelroot, installed BsyBox, installed Safestrap, flashed SuperLiteRom on the stock Slot, and lastly loaded xPosed and the modules.
[Verizon Samsung Galaxy S III] LinuxHippy:
Are u using safe strap too?

Marty
[Verizon Samsung Galaxy S III] dawgdoc:
Yes, sorry I didn't get the edit to/,y post in fast enough. :angel:
[Verizon Samsung Galaxy S III] LinuxHippy:
Do u also have a ROM 1 slot with the xposed app installed there? I don't think safe strap is active on the stock ROM slot.

Marty
[Verizon Samsung Galaxy S III] dawgdoc:
After installing Safestrap and making a nandroid backup, I placed the SuperLiteRom/in the stock slot. I then sideloaded the xPosed installer, because I had the apk on my laptop from a tablet pull. I installed and opened the xPosed-installer.apk. From within the installer app I selected to install xPosed. After a rebootxPosed was working. I then installed the two module apks I mentioned above. Next, using the xPosed installer I activated them. Following a reboot the modules were ready for use.
[Verizon Samsung Galaxy S III] bigp951:
That is exactly what I did.... If you plan on being bold using xposed I suggest making nandroids regularily.. I got so bold as to installing around 10 modules a day and frequently had to flash back to a previous state. some of the modules are pretty sweet though. :good:
[Verizon Samsung Galaxy S III] dawgdoc:
Since this device is intended as a backup/loaner it is not connected to a carrier yet. I am spending some time each evening learning how tight I can lock it down with xPrivacy without causing reboots/bootloops. The only things I have added other than the xposed modules are Better Battery Stats. and Terminal Emulator. I will soon begin adding other apps.
[Verizon Samsung Galaxy S III] LinuxHippy:
Xposed Framework features do look like what I have enjoyed in CyanogenMod ROMS, but it can be problematic with SS. I searched through the entire long thread and found a couple postings of this. The clearest is from the OP on post 45 here:

http://xdaforums.com/showthread.php?t=2797314&page=5

This was from last year, so maybe he updated builds of SS so that this is not a problem now since people are getting everything installed OK.

Marty
[Verizon Samsung Galaxy S III] dawgdoc:
I checked the post you linked to and I see why some of us have had success.

We installed Safestrap first and then installed xPosed. In the post they mention problems when xPosed is instgalled before Safestrap. That being said, from what I have read not every module will work using an i535 on 4,4,2, Safestrap, and one of the two alternate ROMs (Paul Pizz or SuperLite). But, that is true for my Acer tab, i747, and other devices where people install xPosed.
[Verizon Samsung Galaxy S III] LinuxHippy:
Yeah I saw that. You may have trouble updating SS with xPosed but then again that post is before build 4 & 5.

Marty
[Verizon Samsung Galaxy S III] dwh2o13:
This was my suspicion as well....SS first and then exposed. Has anyone noticed if the phone isn't as quick and /or battery drain with the addition of exposed modules?
[Verizon Samsung Galaxy S III] LinuxHippy:
I was having trouble all day installing a ROM with the unofficial SS B5 today. I checked the MD5 and it was good. After hours of getting the same failed message (picture attached), I tried re-downloading the ROM from another mirror and it worked. I have no idea how 2 files that produce the same MD5 checksum could not be identical...but they were.

So, if u happen to get a failed message from SS just try the obvious: re-download from another mirror.

Marty
[Verizon Samsung Galaxy S III] arosboro:
Is it possible to install cm-11 nightly for d2lte? I saw AOSP was supported now, but it softbricked my phone.

What are the steps to get an AOSP rom installed? It looked like it worked but my phone went into a boot loop and I couldn't enter recovery mode after activating rom slot 1.
[Verizon Samsung Galaxy S III] ShapesBlue:
If your running safestrap you can't install custom roms other than the few safestrap roms. Trying to install custom roms will brick your device

Sent from my N5
[Verizon Samsung Galaxy S III] arosboro:
Thanks for the advice. I found the Superlite ROM from the same author of this thread. It installed and for once did not brick my phone. I am very pleased, at least that I can remove that VZW bloat. Too bad no custom roms. I thought AOSP included CM roms, and did see reference to CM in some of the posts.
[Verizon Samsung Galaxy S III] dawgdoc:
I think SafeStrap supports custom ROMs for those still on unlocked bootloaders.
[Verizon Samsung Galaxy S III] ShapesBlue:
True but why would you even need safestrap if your on an unlocked bootloader?

Sent from my Nexus 5
[Verizon Samsung Galaxy S III] dawgdoc:
I don't know, but I have seen people posting about errors trying to flash ROMs other than SuperLiteROM and PaulPizz using SafeStrap. They seem to realize that they must use SafeStrap if they are on the locked bootloader but are missing the fact that only SuperLiteROM, PaulPizz, and stock are available to them.

It could be because one of the SafeStrap threads mentions the other ROMs supported for those on the unlocked bootloader. I guess this is so they can have different ROMs on the various slots. I guess this would work like on of the multi-boot mods.
[Verizon Samsung Galaxy S III] Bbakes2012:
Actually if you scan through the posts, you'll see me and a few others let you know that AOSP can be installed. I don't know about cm but I know I've gotten slim on here before. The only issue is, even though the rom works, the radios don't. So no Wi-Fi or mobile anything lol. The only working, fully functional, roms are the couple in the OP posts
[Verizon Samsung Galaxy S III] LinuxHippy:
Is there a way to install SlimKat without changing the kernel? I think that's why the radios work in the other 2 ROMs.

Marty