yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] earthsound:
black screen after Samsung logo

I have a Verizon Samsung Galaxy S4 that was running 4.2.2 MDK stock & rooted. I had TWRP 2.5.0.2 installed and downloaded Stock_4_3_kernel_MJ5_v1.3_loki_d.zip. Booted into TWRP, wiped, installed the zip, wiped again and rebooted.

After showing the Samsung boot image, it goes to a black screen > the blue LED lights up for a bit > it makes the sound that it used to make when showing the Verizon boot animation and that's it. I know the phone has booted up, b/c I can press the power button to cause the software buttons/lights at the bottom to come on, but the screen stays black. I can long press the power button and get a vibrate like when the power options show. I can touch the areas on the screen (as well as the bottom software buttons) and it makes a little noise with each touch...almost like it's on a setup screen or something.

Can I use Odin to flash back to stock MDK or should I try something else?
[Verizon Samsung Galaxy S 4] r_hippy:
Your rom is mdk dase?

And you fished 4.3 kernel?

That kernel is for MJ7 4.3 rom in the op.

Flash this rom in recovery from your SD card.
[Verizon Samsung Galaxy S 4] gunnermike:
I'd try booting back to recovery flashing the rom and pick one of the kernels included in the aroma installer. don't flash anything else until you boot the first time.
[Verizon Samsung Galaxy S 4] earthsound:
Like an idiot, apparently I completely skipped both downloading & installing VZW_ROM_XXUEMJ7_11-23-13.zip. :eek:

I'm going to grab it and try flashing it in recovery & see if that fixes my mess up.

Thanks!
[Verizon Samsung Galaxy S 4] earthsound:
Stepped through the Aroma installer and rebooted when finished. The phone sits on the Samsung custom boot image and goes no further. I guess this phone had been updated at some point to stock/rooted ME7(?). I was certain that I'd left it at a rooted MDK when I flashed the pre-release MD2 and then used motochopper to root it and then flashed the MDK kernel. That was the first week in August.

How can I determine which boot loader is on the phone? Assuming it's MDK bootloader, what's the best way for me to get this back to stock, rooted MDK? :|

Sorry for polluting this thread...
[Verizon Samsung Galaxy S 4] gadget!:
Are you using safestrap?

If not and you were able to boot into a custom recovery to flash the rom, you are on mdk.

Did you check the md5 on your download?

Sent from a Galaxy S4... Far far away
[Verizon Samsung Galaxy S 4] r_hippy:
Before anything did you check md5?

With the latest release I read to install it complete stock. Don't change anything in aroma.

I never flashed anything but the first release so I can't be sure.

That also may of been with the testing of mk8
[Verizon Samsung Galaxy S 4] earthsound:
I'm not using safestrap, I'm using TWRP 2.5.0.2. It looked like everything in the Aroma installer installed OK, but it just sits at the "Samsung Custom" boot logo. I'm at a loss.

The md5 checksum matched what is in the OP.

I edited my last post while you were replying. Is there a way to determine what version of the bootloader is installed and, therefore, what steps I can take to get this phone back in working condition?

---------- Post added at 07:33 PM ---------- Previous post was at 07:31 PM ----------

The md5 matched what's in the OP.

I will try going through the aroma installer again and not changing any of the settings to see if that clears this up. Thanks for the suggestion.
[Verizon Samsung Galaxy S 4] mochamoo:
Download deviceinfo app from play store. You sound end up with something like this :
[Verizon Samsung Galaxy S 4] earthsound:
Thanks for the suggestion, but I'm not getting the phone to boot past the "Samsung Custom" boot screen. Is there another way to determine the bootloader version? I have TWRP 2.5.0.2 installed.

I ran the Aroma installer from OP again with all default settings and upon reboot, the phone still sits at the "Samsung Custom" screen. I'm not certain which method is best for getting this back to how it was before. :(
[Verizon Samsung Galaxy S 4] r_hippy:
Grab and flash the one in legacy builds and see if it boots
[Verizon Samsung Galaxy S 4] Surge1223:
You're on mdk. You can confirm this a lot of ways like looking at the kernel version and the fact that you can boot to twrp recovery means your on mdk. I havent read what exactly your issue is but I just wanted to quicky say that before you did anything drastic like flashing an update that locks your phone down.
[Verizon Samsung Galaxy S 4] tkacer:
I've had this happen to me a number of times - your options:

1) pull battery - power back on - boot normally? If no,

2) pull battery - boot back into recovery - wipe cache, delvik - reboot into system. If no,

3) pull battery - boot back into recovery - either restore known good backup or reflash same/different rom or same/different kernel.

One of these three always works for me :good:
[Verizon Samsung Galaxy S 4] r_hippy:
[MENTION=3074508]old&slow[/MENTION]

in your mod Blue_Toggles_Switches_Batt_no_%

I tried to decompile the framework-res.apk

I was going to change a couple image

it decompiled with out errors

but when I go to compile it

I get this error

W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
aapt: warning: string 'default_audio_route_name_hdmi' has no default translation in C:\AndroidMultitool\Decompiled_apk\framework-res\res; found: es
aapt: warning: string 'default_permission_group' has no default translation in C:\AndroidMultitool\Decompiled_apk\framework-res\res; found: es
aapt: warning: string 'permdesc_sendSmsNoConfirmation' has no default translation in C:\AndroidMultitool\Decompiled_apk\framework-res\res; found: es
aapt: warning: string 'permlab_sendSmsNoConfirmation' has no default translation in C:\AndroidMultitool\Decompiled_apk\framework-res\res; found: es
aapt: warning: string 'perms_hide' has no default translation in C:\AndroidMultitool\Decompiled_apk\framework-res\res; found: es
aapt: warning: string 'perms_show_all' has no default translation in C:\AndroidMultitool\Decompiled_apk\framework-res\res; found: es
aapt: warning: string 'tommorrow' has no default translation in C:\AndroidMultitool\Decompiled_apk\framework-res\res; found: bn_IN
I: Building apk file...

any idea ?

to test if it was the images I added

I deleted everything and started over again, I decompiled it and right after I compiled it (with out touching anything)

same error with out any edited files

[MENTION=2296653]swgamez[/MENTION]

I also pulled the framework-res.apk for your mod

I545 VRUEMJ7 Unlock Tether and no WIFI notification

I get this error decompiling it

I: Loading resource table...
I: Loaded.
I: Decoding AndroidManifest.xml with resources...
I: Regular manifest package...
I: Decoding file-resources...
S: Could not decode file, replacing by FALSE value: drawable-xxhdpi/stat_sys_wifi_disabled.png
S: Could not decode file, replacing by FALSE value: drawable-xxhdpi/stat_sys_wifi_not_connected.png
S: Could not decode file, replacing by FALSE value: drawable-xxhdpi/stat_sys_wifi_connected.png
S: Could not decode file, replacing by FALSE value: drawable-xxhdpi/stat_sys_wifi_no_network.png
S: Could not decode file, replacing by FALSE value: drawable-hdpi/stat_sys_wifi_dummy.png
I: Decoding values */* XMLs...
I: Done.
I: Copying assets and libs...

and the same error above when compiling it

I then tested on the stock framework-res.apk from the rom

same error compiling

any idea ??

thanks in advance
[Verizon Samsung Galaxy S 4] swgamez:
The reason is because to kill wifi notification you have to delete these PNG files.

Originally Posted by rwc95 View Post

Just a fyi you don't have to add those lines in the xml. You can just 7 zip open the framework and delete the 5 pngs from the drawable/hdpi folder this how I've done all the jellybean leaks for everyone and causes no issues and you don't have to recompile so it's a little quicker.

so to recompile you will need to need add the files back its just a nice trick by rwc95
[Verizon Samsung Galaxy S 4] r_hippy:
Makes sense on the error for decompiling your file. What's the error when compiling the stock framework-res without missing images?
[Verizon Samsung Galaxy S 4] earthsound:
If I boot into TWRP and flash I545VRUEMJ7-Stock-Deodex-Wifi_fixed.zip, should I immediately flash Root.zip before rebooting? Thanks for your help!
[Verizon Samsung Galaxy S 4] r_hippy:
No need all fixes are in that version.

Good luck

Be sure to wipe etc.
[Verizon Samsung Galaxy S 4] earthsound:
Thanks. The reason I asked is that in the OP, next to I545VRUEMJ7-Stock-Deodex-Wifi_fixed.zip it says "(requires Root.zip)."

I'll give this a shot.
[Verizon Samsung Galaxy S 4] r_hippy:
sorry.. your correct I was wrong you need to flash it right after ..
[Verizon Samsung Galaxy S 4] old&slow:
I get the same aapt errors every time. Looks like built just fine though.
[Verizon Samsung Galaxy S 4] r_hippy:
I searched for the errors and can't find anything on it..

I see it did compile (build the apk)

guess it will remain a ministry
[Verizon Samsung Galaxy S 4] swgamez:
What your getting are just warnings, framework-res.apk will still recompile and be usable , as long you don't have any error.

I have never had any issues even with those warnings.

sometimes we use to get this error

http://xdaforums.com/showthread.php?t=2279024
[Verizon Samsung Galaxy S 4] r_hippy:
thanks

I'm Learning

I just don't want to put something together

that may "BROKE" someones phone

thanks [MENTION=3074508]old&slow[/MENTION] for testing it out
[Verizon Samsung Galaxy S 4] swgamez:
You are doing very well and learning very fast mate :good:
[Verizon Samsung Galaxy S 4] old&slow:
Just going out on a limb here, but we're using aapt out if the stock android sdk and it just doesn't recognize some of the touchwiz junk.
[Verizon Samsung Galaxy S 4] swgamez:
Thanks old&slow I think you right;)
[Verizon Samsung Galaxy S 4] r_hippy:
Sorry "aapt" is new to me

I will seach and read about it

I am assuming it's removing or commenting out ?

within the smali or xml

so when compiling it

it doesn't know what it is ??

I hope I didn't make myself look foolish :fingers-crossed:
[Verizon Samsung Galaxy S 4] old&slow:
Not at all.:) I was going crazy trying to recompile SystemUI until I finally found a thread by (I really wish I could remember who). Had to add about 15 "@style/"s to get it to compile without erroring out.
[Verizon Samsung Galaxy S 4] swgamez:
hope this helps

http://xdaforums.com/showthread.php?t=2279024
[Verizon Samsung Galaxy S 4] old&slow:
Thank you [MENTION=2296653]swgamez[/MENTION]. That's the one.:)
[Verizon Samsung Galaxy S 4] r_hippy:
Thanks for taken the time and hunting that down. Helps tremendously [MENTION=2296653]swgamez[/MENTION]

Now I just need upgrade my brain for more storage

Like a new hd in. My rig :)
[Verizon Samsung Galaxy S 4] swgamez:
Thank you guys. You guys make being here fun:o

Knowledge is power. night mates
[Verizon Samsung Galaxy S 4] old&slow:
See ya....:)
[Verizon Samsung Galaxy S 4] earthsound:
Thanks for the suggestions. I'd tried the first two, didn't have a good backup on the cards on hand, and the only thing left was to try the other kernels inside the aroma installer. Instead, I tried the legacy build and it worked! :)

The I545VRUEMJ7-Stock-Deodex-Wifi_fixed.zip build worked! :victory:

As I was interested in some of the features listed in the Aroma installer, I may give that another go, but I was curious as to the main differences between the Ktoonsez TW4.3 and LOKI'd kernels.

Thanks again for your help!
[Verizon Samsung Galaxy S 4] r_hippy:
Good nite m8 thanks for everything

That's good news, glad it worked out

I'm using talexop kernel. Is in the op as well.
[Verizon Samsung Galaxy S 4] r_hippy:
I played with both dark secmms releases from jrkruse

and I put this together.

I'm still looking for more bubbles that will work better with this as well..
[Verizon Samsung Galaxy S 4] old&slow:
Nice! :D
[Verizon Samsung Galaxy S 4] Capp5050:
Guys,

I clean-flashed the 11/23 build to try to fix some self-created issues. All went well, but for some reason I have no lock screen clock. Very strange as this has never happened on any version of this ROM (or any other for that matter).

I tried toggling most of the lock screen options, even the wallpaper.

Screen grab attached.
[Verizon Samsung Galaxy S 4] old&slow:
You might try wiping cache and dalvik in recovery and see if that doesn't fix it.
[Verizon Samsung Galaxy S 4] gunnermike:
So its been a while since ive been in the themeing game. I was trying mod the keyboard but when I decompile it I get a bunch of apktool dummy lines in the public xml and a few other errors. How are you decompiling the apk's?
[Verizon Samsung Galaxy S 4] old&slow:
I'm using the latest apktool release, 1.5.2 I believe, not in front of my computer right now. I always have a ton of dummies though I haven't themed the keyboard.
[Verizon Samsung Galaxy S 4] r_hippy:
Everything is up to date i'm assuming

All tho apktools is choice

I came across this

[TOOL][WINDOWS] ANDROID MULTITOOL v3.0 [ADB]

give it a shot to see if it still happens..

I had a couple issue the other day

old&slow

and

swgamez

where a big help
[Verizon Samsung Galaxy S 4] Capp5050:
Whadya know? That did it. Thx!
[Verizon Samsung Galaxy S 4] old&slow:
Cool!:cool:
[Verizon Samsung Galaxy S 4] gunnermike:
your link doesn't work.
[Verizon Samsung Galaxy S 4] r_hippy:
http://xdaforums.com/showthread.php?t=2326604

Hum.. Try that
[Verizon Samsung Galaxy S 4] Surge1223:
https://www.dropbox.com/s/ayyy6oqgfvn4vti/apktool_2.0.0b7.jar

I assume you know what to do with that (how to add it to your path, etc) use that instead of the 1.52 apktool.jar. Use the aapt from either the api 18 or 19 after updating android-sdk. Thats how I do it, granted im more of a mod and bootloader person than a modder/themer but I dont ever have issues and ive decompiled framework-res.apk, SystemUI.apk, twframework-res.apk from a lot 4.3 devices successfully. Things changed slightly since 4.2.2
[Verizon Samsung Galaxy S 4] gunnermike:
Looks like I just had to setup APK Manager. But I have a new problem, the stupid app wont show up now.
[Verizon Samsung Galaxy S 4] old&slow:
After compiling are you opening the new apk and deleting AndroidManifest.XML and the dragging over AndroidManifest.XML and META-INF from the original apk?
[Verizon Samsung Galaxy S 4] Badger50:
Has anybody figured out how to fix the reverse GPS issue when using the stock kernal? It works fine with KT's kernal, however, I think the Rom runs much better using the stock kernal. Just curious :)

Sent from my Mobile Beast Device!! :)
[Verizon Samsung Galaxy S 4] gunnermike:
Back in the dark ages you didn't have to if you used apk manager. do you have to do that now?

---------- Post added at 08:12 PM ---------- Previous post was at 08:05 PM ----------

Well that worked. I have never had to do that before with apk manager.
[Verizon Samsung Galaxy S 4] old&slow:
Not sure if it was jb or ics when that nonsense started.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Ics 4.0. Had to update apktools to recompile and use an older version to decompile. Or maybe vice versa.
[Verizon Samsung Galaxy S 4] old&slow:
I'm glad it was pretty much unified by the time I started messing with it.
[Verizon Samsung Galaxy S 4] Surge1223:
Does everyone use apk managers now a days? I still do it manually with just the smali and apktool jars and obviously aapt and test key. I dont know I just am used to doing it the old way I guess.
[Verizon Samsung Galaxy S 4] old&slow:
Hey, I have no shame! I'm all about easy.:D
[Verizon Samsung Galaxy S 4] gunnermike:
seriously, I don't have time for complicated. I stopped doing themes about a year and a half ago when we bought our house. There has just been too much to do. Don't really have much more time now, but I wanted a pretty keyboard.

Here is what I have so far. looks ok but somehow key press sound and vibration got broke. I didn't even mess with xml's yet.
[Verizon Samsung Galaxy S 4] r_hippy:
Looks great gunner!
[Verizon Samsung Galaxy S 4] gunnermike:
Thanks. Now I just have to figure why sound and vibration are broke.

---------- Post added at 09:07 AM ---------- Previous post was at 08:10 AM ----------

Could someone do me a favor and decompile and recompile SamsungIME.apk and push that and tell me if vibration and sound work on the keyboard please.

---------- Post added at 09:07 AM ---------- Previous post was at 09:07 AM ----------

Could someone do me a favor and decompile and recompile SamsungIME.apk and push that and tell me if vibration and sound work on the keyboard please.
[Verizon Samsung Galaxy S 4] r_hippy:
I'll test it 4 ya.

---------- Post added at 10:29 AM ---------- Previous post was at 10:11 AM ----------

@gunnermike works. It did reset the sound and vibration. Tho I had to turn it on again. Also reset SwiftKey settings.

---------- Post added at 10:41 AM ---------- Previous post was at 10:29 AM ----------

Weird I flashed the original one back and nothing reset. I then looked at both files there aren't the same size anymore. Maybe something changes slightly. But it did work (sound & vibration)
[Verizon Samsung Galaxy S 4] r_hippy:
Did anyone see this?

Echoe released this, note 3 my files moded to work with what seems mj7 international based roms. Do a quick search for his roms you'll see his add-ons.

I never use my files but it's a cool lay out. Has a ftp as well integrated into it.
[Verizon Samsung Galaxy S 4] gunnermike:
What process are you using? I can't figure out why it's doing that.
[Verizon Samsung Galaxy S 4] r_hippy:
You pushing it adb? I packed it up and flashed it. I also pulled 2 folders in addition to meta-inf (com org) from the original apk, being it wasn't carried over before signing it. Other wise that's it.

I can send you the decompiled archive, add your edits and test or send it back after and I compile it and test. I'll be home in 10 minutes if you want to try that.
[Verizon Samsung Galaxy S 4] stang5litre:
Got a question anyone still having problems with apps on sd card graying out? Tried 2 different 64gb cards both new same result. Any help is well appreciated as I am getting the insufficient space notification when I have space on both
[Verizon Samsung Galaxy S 4] gunnermike:
We can try that. Ill send my apk, would you mind trying that?
[Verizon Samsung Galaxy S 4] r_hippy:
No issues here but I don't have a 64 gig SD card I read people having issues with many makes of the SD card (that size).
[Verizon Samsung Galaxy S 4] gunnermike:
What kernel are you using?
[Verizon Samsung Galaxy S 4] r_hippy:
*pulled files

Samsung_keyboard_files

in the archive there is a file called

MJ7_SamsungIME_test.zip

this was decompiled then compiled and signed

it's flashable

then there is a folder SamsungIME

thats Just decompiled "stock"

then a flashable file called

MJ7_SamsungIME_stock.zip

default untouched

you can zip up your SamsungIME folder before compiling it and I can compile and sign , and test ..

will report back about your file asap
[Verizon Samsung Galaxy S 4] thekidgio:
Are there any roms that work for MI1 on safestrap recovery??
[Verizon Samsung Galaxy S 4] gunnermike:
No, the are no ROMs what so ever fo MI1......:cyclops:
[Verizon Samsung Galaxy S 4] r_hippy:
[MENTION=3315419]gunnermike[/MENTION] no sound or vibration. I double checked settings.
[Verizon Samsung Galaxy S 4] gunnermike:
dang it. you using apktool? not manager?
[Verizon Samsung Galaxy S 4] r_hippy:
Correct I tested it as well with Android multitool.
[Verizon Samsung Galaxy S 4] gunnermike:
Never mind I figured it out! It was a compression storage issue. I opened it up with WinRAR a deleted the ogg files in the res/raw folder and readded them and set compression to store instead of normal and that fixed it. Thanks for the help though its appreciated.
[Verizon Samsung Galaxy S 4] r_hippy:
if you like I can decompile it and pull your edited files out and compile it

you know the files off hang ?

will same me time

---------- Post added at 01:53 PM ---------- Previous post was at 01:48 PM ----------

I went to decompile yours and I get this

I: Baksmaling...
I: Loading resource table...
I: Loaded.
I: Decoding AndroidManifest.xml with resources...
I: Loading resource table from file: C:\Users\Hippy\apktool\framework\1.apk
I: Loaded.
I: Regular manifest package...
I: Decoding file-resources...
S: Could not decode file, replacing by FALSE value: drawable-sw359dp-xxhdpi/floating_qwerty_vietnam_01.png.png
S: Could not decode file, replacing by FALSE value: drawable-sw359dp-xxhdpi/one_hand_qwerty_vietnam_01.png.png
I: Decoding values */* XMLs...
I: Done.
I: Copying assets and libs...
[Verizon Samsung Galaxy S 4] 1Raiders:
Hey guys,

wondering if someone else could reproduce this...

I set all 3 animation scales to zero (in dev options).

They stick perfectly until i open camera. After I close camera, trans animation goes to 1x.

Just curious. Other than that this rom is absolutely amazing!!!

Thanks ALL

E
[Verizon Samsung Galaxy S 4] gunnermike:
So here is a Samsung Keyboard with my old epic blue theme. Old&Slow you can offer it as an option in the aroma installer on the next version if you want. I don't have much time for playing like I used to but I will probably do the dialer and maybe the status bar, maybe a few others depending on time.
[Verizon Samsung Galaxy S 4] 1Raiders:
Looks great bud!

Thanks!
[Verizon Samsung Galaxy S 4] gunnermike:
That's really weird. I don't get that error when I decompile it. I use APK Manager, that might have something to do with it.
[Verizon Samsung Galaxy S 4] r_hippy:
So what did you change?

Assuming is all working now?
[Verizon Samsung Galaxy S 4] Surge1223:
It doesn't matter during the decompile. When you recompile it, delete the resources.arsc file and it will rebuild the resources and it will be referenced in the classes and manifest for the next time you decompile it. When you opened the apk with an archiver and manually fixed your mistake, no instructions/data in the manifest or classes was added or removed to reflect the changes you made.
[Verizon Samsung Galaxy S 4] r_hippy:
[MENTION=3315419]gunnermike[/MENTION]

I compiled yours after decompiling it and replacing

those 2 images and flashed it

all works
[Verizon Samsung Galaxy S 4] gunnermike:
Sorry meant to quote you in that post.

It was a compression storage issue. I opened it up with WinRAR a deleted the .ogg files in the res/raw folder and re-added them and set compression to store instead of normal and that fixed it. Thanks for the help though its appreciated.

---------- Post added at 01:17 PM ---------- Previous post was at 01:15 PM ----------

Not sure I'm following you. I manually added ogg files back, the error he was getting was for a png file in a different folder.
[Verizon Samsung Galaxy S 4] r_hippy:
Missed this

ur welcome

glad its sorted

---------- Post added at 02:19 PM ---------- Previous post was at 02:17 PM ----------

thats weird I replace those images and it all worked

never looked at ogg files :D

go figure
[Verizon Samsung Galaxy S 4] DroidForLife33:
How did you get the dark theme?
[Verizon Samsung Galaxy S 4] Surge1223:
Okay I see where the confusion is. I feel like I have to explain in case someone accidently stumbles here in the future with the same issue. Gunners issue compression storage issue would not have affected r_hippy because they both used different apktool manager/multitool implementations. So gunner solved his issue of by deleting then readding the conflicting files with the proper compression (which is no compression). r_hippy however saw errors during decompiling..which is normal because when you rebuild the apk it regenerates the resources and classes reflecting any modifcations you make. This is all a consequence of how apktool was originally made, you used to have to decompile/recompile twice to generate a signed apk.

And why im in this thread discussing this..I have no idea lol. What can I say you guys keep it interesting over here. My bad for the confusion and clutter. Carry on.