yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Beakhole:
Failed to Flash!

I tried doing this last night for my brother. I put the Loki'd CWM found in the last section of these instructions on his phone, did a NAND backup, then wiped cache, dalvik cache, factory data wipe/reset, flashed the VZW_NC5_AROMA_4_29_30.zip then wiped cache and dalvik cache again but I didn't wipe data a second time.

After the Aroma installer and reboot, I got the screen saying that "unauthorized software was put on this phone" error message.

So I rebooted to recovery, tried to restore from the NAND backup, which "failed to restore /data", ended up factory wiping the phone and restoring the Titanium Backup.

1. Why did it not flash correctly? I went through the Aroma installer just fine...

2. Why couldn't I restore the NAND backup?

3. How can I successfully flash this on his phone without any errors?

Any/all help would be awesome!
[Verizon Samsung Galaxy S 4] bryantjopplin:
Either A you don't have a mdk bootloader or you flashed a kernel without a loki patch.

Tell us what your bootloader is? What was your base rom?
[Verizon Samsung Galaxy S 4] Beakhole:
We're talking about my brother's phone. Here's the info right out of his "About Phone" section of his phone:

Model number: SCH-I545

Android Version: 4.2.2

Baseband Version: I545VRUAMDK

Kernel Version: 3.4.0-562219 | se.infra@SEP-112 #1 | Mon Apr 29 22:51:22 KST 2013

Build Number: JDQ39.I545VRUAMDK

SELinux status: Permissive

Hardware Version: I545.06
[Verizon Samsung Galaxy S 4] dark_overload:
The aroma installer for this ROM has the loki patch/flash tools within, it should have patched the kernel during install.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Baseband and bootloader are two different things. Either download or use a terminal emulator from the phone and type

getprop|grep bootloader

Your output should be like this

u0_a207@jfltevzw:/ $ getprop|grep bootloader

[ro.boot.bootloader]: [I545VRUAMDK]

[ro.bootloader]: [I545VRUAMDK]

u0_a207@jfltevzw:/ $

Now notice that the

getprop|grep baseband

Is different like this.

u0_a207@jfltevzw:/ $ getprop|grep baseband

[gsm.version.baseband]: [I545VRUFNC5]

[ro.baseband]: [mdm]

[ro.boot.baseband]: [mdm]

u0_a207@jfltevzw:/ $

This is all from my phone.

---------- Post added at 03:16 PM ---------- Previous post was at 03:15 PM ----------

Unless he flashed ael or txopl kernel or whatever that other one is. These aren't patched.
[Verizon Samsung Galaxy S 4] mochamoo:
It that is the case then he should go look at post #482 and be sure to grab loki doki zip to flash RIGHT AFTER flashing the kernel and before exiting recovery.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Well yes of course but he said that he had cwm recovery flashed which could also be causing conflicts if he isn't on mdk bootloader. But I have the loki patch uploaded as well.

https://www.dropbox.com/s/k4add46zqp7mcmx/loki-doki-1.zip
[Verizon Samsung Galaxy S 4] Beakhole:
What is Loki Doki? And when should I flash it?
[Verizon Samsung Galaxy S 4] bryantjopplin:
Mostly when you have a kernel that hasn't been patched to load on the mdk bootloader phone. The roms usually have everything needed unless you switch kernels. You should understand that this applies to mdk bootloaders only.
[Verizon Samsung Galaxy S 4] Beakhole:
Ok... so just to make sure I understand:

If my brother's phone is on the stock MDK bootloader, then I should have him reboot to recovery, wipe cache/dalvik cache, flash Loki Doki, wipe cache/dalvik cache again, then wipe date/reset, flash the Aroma zip, wipe cache/dalvik cache again, wipe data/reset, and then reboot? And that'll make this new ROM work instead of getting the error boot message?
[Verizon Samsung Galaxy S 4] bryantjopplin:
Is he safestrap? If you are just using the aroma rom I would clear everything, flash rom, don't reboot, flash su.zip and reboot.
[Verizon Samsung Galaxy S 4] Beakhole:
Ok, attached is a screenshot of the command you had me have him run. As you can see, he has the MDK bootloader.

And no, he's not on safestrap, he's on CWM per the last section of this page's instructions.

So what do you think he should do next? Does he need to flash Loki Doki? And I didn't know that he'd have to flash supersu zip either. Is that necessary?

EDIT: I FORGOT TO ATTACH THE SCREENSHOT.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Well good, does he want cwm or need it? Imo I would use the latest twrp recovery. Does he have root right this moment?

Use this app here

https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools

Follow the on screen instructions and pick it for jfltevzw (Verizon s4 right?) install the latest twrp, reboot recovery, backup if needed, clean and clear system, data, cache, and if he can clear one or the other sd card where the aroma is not located that helps sometimes as well. Reboot and see. If he gets unauthorized screen again reboot into recovery and flash the loki-doki and reboot, if still unauthorized I would re-download rom.
[Verizon Samsung Galaxy S 4] dark_overload:
Yeah, your zip could have been corrupted in transfer. You can check it's MD5 sum against the sum from my copy below. I had no issues with "Unauthorized Software" messages. If it matches, you need not re-download.

VZW_NC5_AROMA_4_29_30.zip

MD5: 714FA0E7C23BDF44DBC2F725542E194B
[Verizon Samsung Galaxy S 4] Beakhole:
Sorry for asking so many noob questions, but how do I have him check what the MD5 sum is? Does he have to do that from within CWM recovery?
[Verizon Samsung Galaxy S 4] dark_overload:
MD5 is a standard checksum algorithm, and there are many ways to generate/verify them. My personal favorite is HashTab but if you just want a standalone tool you could try MD5 Summer, both are for windows.
[Verizon Samsung Galaxy S 4] heath2805:
I use "easy file explorer" from play store. Just long press the file, click more, then property's, show checksum, check MD5 box , then calculate.

Edit: Sometimes I'll copy the MD5 and paste both of them in messages to compare side by side.
[Verizon Samsung Galaxy S 4] bryantjopplin:
That works and so does root explorer, ef file explorer and a few others.
[Verizon Samsung Galaxy S 4] Beakhole:
Ok I had him check and he has the same MD5 as you.

What do you recommend is our next step?
[Verizon Samsung Galaxy S 4] heath2805:
After reading what you posted, it almost sounds like it's your recovery causing the issues. I've used TWRP v2.5.0.2 since it was released and have never had any issues. I've found it to be the most stable recovery out there. Here's the aroma installer if you want to try it. I've used it on the ROM a couple times with no issues. https://www.dropbox.com/s/nohcco2033k77qp/TWRP_AIO-OctOS_jfltevzw.v4.2.zip
[Verizon Samsung Galaxy S 4] Beakhole:
Is this an Aroma installer for TWRP? Or should i have him flash this in CWM? Sorry for not understanding.
[Verizon Samsung Galaxy S 4] jds3118:
PM sent let me know
[Verizon Samsung Galaxy S 4] heath2805:
Honesty I haven't installed the aroma TWRP in CWM before. I do know you can flash a TWRP over CMW and it will change it, so you should be fine. After installing v2.5.0.2 you'll have to reboot and then reboot back into recovery to use it.
[Verizon Samsung Galaxy S 4] Beakhole:
How do I go about installing TWRP? Where do I get it? With this? And if so, will this install a Loki'd version of TWRP? Sorry, this is for my brother's phone and I don't have any experience with Loki'd devices because I got my phone after he got his, that's why he's still on MDK.
[Verizon Samsung Galaxy S 4] heath2805:
Just did this to see. Made a new folder and moved files in it. No issues after rebooting. Using stock "My files" app. I've heard of kk bugs with SD cards but never had any issues.
[Verizon Samsung Galaxy S 4] ejohn3288:
Can I dirty flash this over your non aroma version? Has anyone tried?
[Verizon Samsung Galaxy S 4] elliwigy:
i used the non aroma zip and i cant send sms.. i also used the matching radio from link in op to no avail.. ive tried hangouts n stock sms apk as well as go sms with no luck.. i wiped, flashed rom, wipe dalvik/cache and flashed the (use this 99% of the time) matching radio.. anyone else having this issue or know what i can try? calls and receiving sms works fine.. everything else is wicked smooth! i also noticed knox on the phone which i froze of course...

Sent from my SGS4 KitKat Killa
[Verizon Samsung Galaxy S 4] old&slow:
Has anyone noticed that Root Explorer will show extSd as mounted writable but TiBu will say that it's not and fail on backups?
[Verizon Samsung Galaxy S 4] ejohn3288:
I am on the non aroma version and I have no issues sending sms or mms or making calls. Everything is functional and smooth. I did a clean install and wiped system and flashed the rom and the latest radio.
[Verizon Samsung Galaxy S 4] r_hippy:
Thanks jrkruse, going to give"r a try. Thanks
[Verizon Samsung Galaxy S 4] old&slow:
They changed the name on that Knox app to something obscure. I keep missing it too.:(
[Verizon Samsung Galaxy S 4] stanfna:
Yes. I think it has something to do with how KitKat restricts how apps can access the SD. I have tried both this app...

https://play.google.com/store/apps/details?id=nextapp.sdfix

And this module...

http://xdaforums.com/xposed/modules/app-handleexternalstorage-t2693521

With no success.
[Verizon Samsung Galaxy S 4] tbcpn:
Just started a TiBu Pro backup to external SD. Seems to be functioning properly.
[Verizon Samsung Galaxy S 4] heath2805:
Strange....did you try clearing data on messaging?
[Verizon Samsung Galaxy S 4] old&slow:
Did you format your external SD while on 4.4.2? This is what I get

View attachment 2695197
[Verizon Samsung Galaxy S 4] tbcpn:
I've not formatted the 64gb SD card for many moons, and certainly not on 4.4.X. I don't recall if it is formatted exFat or Fat32--been too long.
[Verizon Samsung Galaxy S 4] old&slow:
Well I was thinking about trying that but not now. Too much work. [emoji13]

Edit: Found a fix http://xdaforums.com/showthread.php?t=2617921
[Verizon Samsung Galaxy S 4] HoosierDaddy2442:
I'm not sure what's going on? It seems I'm having issues with ALL TW roms and no sound? The vibrate thing only happens on this though. I've been running AOSP for months now without issues..

Considering just ODIN back to stock and start fresh?
[Verizon Samsung Galaxy S 4] radpp16:
Running great so far. I did full wipe/cache/dalvik x3. I never do restore backups. Start from scratch each install.
[Verizon Samsung Galaxy S 4] Capaints:
Running Great with No Problem THANK YOU

Running Great with No Problem that I can see / find

THANK YOU :good:
[Verizon Samsung Galaxy S 4] iwearthebelt:
Fast ,smooth and haven't had any issues. Looking forward to some mods (WifiHotspot toggle, dark dialer with record, ) ect....
[Verizon Samsung Galaxy S 4] Redflea:
It does seem like it's time for extreme measures for you. I am running w/out any issues noticed so far,other than the prompt about sending security reports appearing in notification drop-down ("Tap here to help protect your phone by sending...".

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

Dolphin was refusing to see the SD card to save downloads there recently, I assume this may have been the issue (though it did allow me to save them there a few times). I had to wipe/reinstall the ROM for other reasons (had nagware in the play store) so I've downloaded the app and am waiting to see if the same thing happens again.

I did just copy a ROM download from the internal to external SD card using Root Explorer w/out issue.
[Verizon Samsung Galaxy S 4] HoosierDaddy2442:
Works fine now.
[Verizon Samsung Galaxy S 4] elliwigy:
wow.. not sure y this didnt come to mind to try but it worked instantly! Thanks for the advice.. i havent been a flashaholic for some time now since ive been working and then ps4 in spare time but am gettin back into it a bit.. thanks again!

Sent from my SGS4 AOSP
[Verizon Samsung Galaxy S 4] heath2805:
From what I've read TWRP 2-7 were loki'd . And no I haven't tried that flash tool. Good find though never seen that before.

Edit: To install just flash the aroma installer in CWM and it should give you the option to select v2.5.0.2 .
[Verizon Samsung Galaxy S 4] jds3118:
That's an old version of TWRP
[Verizon Samsung Galaxy S 4] heath2805:
Yes true, but very stable. Never had any luck with newer versions. Mostly because of Boot hanging.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Yes that's very old and hasn't been updated for kitkat. Could cause problems down the road. Seriously install this app and use jfltevzw under twrp and it will flash 2.7 and higher to the s4 with no issues, loki-doki already applied as it is meant for the vzw s4 and twrp knows that the recovery on the s4 needs it. You can flash a different recovery on top of another but them seem to be old. If you feel froggy you can download the IMG file and use the terminal emulator cmd and do it your self.
[Verizon Samsung Galaxy S 4] jds3118:
The main issue is the older recovery won't flash larger files like over 1.7gb so if a rom has aroma in the zip it will error older philz's Cwm had the same issue. That may not be relevant to this rom as Idk the files size.
[Verizon Samsung Galaxy S 4] heath2805:
True, I've read some of your posts. Definitely possible with larger files. I'm not trying to steer anyone in the wrong direction, just haven't encountered any issues with that version even on kk builds.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Exactly, they wouldn't update them and tell you most of the time to have it updated. Lol zero issues with updated recoveries or any rom on the s4 ever. A few hiccups here and there but seriously Damn Good coding throughout the community
[Verizon Samsung Galaxy S 4] jds3118:
It's all good my friend we are all just trying to help this guy out ? I ran that version for a long time then had to update for some of the new roms out especially my port.
[Verizon Samsung Galaxy S 4] dark_overload:
I'm not exactly sure what version of CWM I am on but I know it is old. I still have the recovery.lok if you want. I never updated. I never saw the need. It works with the 1.7 GB zip you want to flash.
[Verizon Samsung Galaxy S 4] jds3118:
I updated to ktoonsez's all in one 2.7.0.1 twrp and it works flawlessly? I haven't tried the f2fs yet I still use the .ext4
[Verizon Samsung Galaxy S 4] mochamoo:
Ditto. Forget what I said about Loki doki. That only applies if you are flashing kernels for the i9505, for example. Kt's twrp worked for me when I had issues with the regular twrp. It's been a while so I don't remember what the issue was any more.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Ktoonz modified to be only ext4 format. From what I read.
[Verizon Samsung Galaxy S 4] jds3118:
Ext4 I believe is default and through recovery you can convert the system to f2fs unless he updated since the last time I checked which is possible. His download page still listed as all in one.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Not sure maybe I read about a separate one. Lol
[Verizon Samsung Galaxy S 4] elliwigy:
Can someone point me in the direction of a stock rooted 4.4.2 vzw s4 rom with knox? would it be the leaked tar or the full install with everything in op? The reason is i want to get into romming and wanted a stock rooted 4.4.2 rom i can extract and check out the updater script and layout with least amount of modifications... (yes i also have a vzw s4 mdk with hyperdrive atm).. im guessin the leaked version might not have root? is the full version in op untouched but rooted? thanks in advance!
[Verizon Samsung Galaxy S 4] dark_overload:
I am still using ext4 as well. I hear F2FS is designed specifically for NAND storage, and I have been thinking about converting at some point. For now though, I like using a widely compatible, community developed file system, as opposed to a Samsung developed one. Lol.
[Verizon Samsung Galaxy S 4] jds3118:
Yeah I haven't researched it enough yet to try it myself lol been a little busy lately.
[Verizon Samsung Galaxy S 4] Beakhole:
So I could have him flash TWRP 2.7+ with this right over top of CWM that is already on there?
[Verizon Samsung Galaxy S 4] bryantjopplin:
No problem at all
[Verizon Samsung Galaxy S 4] Beakhole:
SUCCESS!!

Ok, well I followed your instructions for using Rashr to flash TWRP on my brother's phone which worked. Then we rebooted recover, backed up NAND, wiped cache/dalvik, factory reset, flashed the ROM, flashed SUPERSU2.0.ZIP, wiped cache/dalvik, and factory reset again, and now he's up and running KitKat!

Thanks, everyone, who helped! This is good. I was worried that I royally screwed up his phone but it's all better now. :laugh:
[Verizon Samsung Galaxy S 4] jds3118:
Glad you got it going my friend! ?
[Verizon Samsung Galaxy S 4] dark_overload:
Congradulations. It's a complicated process but MDK is the best way, IMHO. You left the internal and external SD alone though correct?
[Verizon Samsung Galaxy S 4] Beakhole:
Yeah. We didn't format or flash a kernel, just wiped cache and factory reset before and after flashing the ROM and supersu. It worked awesomely (if that's a word).
[Verizon Samsung Galaxy S 4] bryantjopplin:
Told you it wasn't that hard lol that app is pretty Damn good.
[Verizon Samsung Galaxy S 4] dark_overload:
In that case be sure to get ahold of me (or post here) if he has any random reboot and/or battery drain issues. CatLog is also a great app for tracing problems. He can use that to save logs for me to drill down upon if he has the same issue I did. I still haven't figured out a more descriptive cause other than an unknown file with bad mojo. :D
[Verizon Samsung Galaxy S 4] mochamoo:
Or just flash jkruse's latest release.

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

Very stable so far.
[Verizon Samsung Galaxy S 4] dark_overload:
The way I understand it, this ROM and the one you linked to are two distinct builds, one is not a later version of the other.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Yes one is the international ported over to the vzw s4 and one is the stock vzw s4 version.
[Verizon Samsung Galaxy S 4] mochamoo:
Both are stock Samsung versions just for different markets. If you want to wait for the official vzw release feel free. International versions are on a faster track. Up to Nf1 now.
[Verizon Samsung Galaxy S 4] dark_overload:
We just don't want people getting confused and thinking they are the same thing. VZW has always been slower to release updates.

Besides, newer doesn't always mean better, lol. Take the case of OpenSSL and the heartbleed bug for example. :D

Some people (like me) prefer to use carrier sanctioned builds. Jrkruse is the man for doing both!
[Verizon Samsung Galaxy S 4] eiddor:
I've been running this ROM for a couple of months now and suffer from the random reboots (vibrates, then vibrates twice, then reboots). Before this ROM, I was running stock TW that I rooted myself, so this was my first flash. I did do a complete wipe and install, but did not wipe my SD card.

Going back through the thread, I'm seeing that formatting your SD card might have resolved this. Do you still believe this to be the case? The SD card with its existing files was working fine with the previous version.

Let me know what you think.

Thanks!
[Verizon Samsung Galaxy S 4] dark_overload:
Make a backup beforehand of course but yes, that is what I would recommend. Format both the internal (emulated) and the external (physical) SD storage devices. I have a few questions about what exactly you are experiencing as well:

How often does the issue happen?

Does the phone seem to get sluggish in the minutes leading up to the reboot?

Does it seem to stop responding completely before the reboot?

If the screen is off when it happens, does it take a long press or two to the power button to bring it around?

Is there any way you could produce a logcat for the period of time leading up to the crash? That is almost exactly what was happening to me. I'd like to compare, especially if a clean internal and external SD correct the problem.
[Verizon Samsung Galaxy S 4] eiddor:
I've been living with it since I installed the ROM, so I have no problem trying to help narrow it down before I go ahead with a reformat (hopefully there will be a new ROM out by then :) )

How often does the issue happen?

Sometimes a few times a day, sometimes a couple of times a week. It seems to be random, and I can't correlate it with a specific action or app (I have tried). Sometimes it's while I'm listening to Audible and it just happens on its own, other times it's while reading a web page, and still other times when I'm on the phone. It has happened at least twice while the phone was sitting idle.

Does the phone seem to get sluggish in the minutes leading up to the reboot?

I wouldn't say "minutes" -- Seconds, yes.

Does it seem to stop responding completely before the reboot?

Yes.

If the screen is off when it happens, does it take a long press or two to the power button to bring it around?

Yes, that has happened.

So, it's been a number of years since I've worked with logcat (Droid2!) -- if you could give me the steps, I can go ahead and set that up. The problem is that I have no way of predicting when it's going to happen.

Thanks!
[Verizon Samsung Galaxy S 4] dark_overload:
Look in a post I made a page or two back for a link to CatLog. Once installed, start recording (from the menu) and it will continue to save a log until a reboot. The logs should show up in the CatLog folder on the internal SD.
[Verizon Samsung Galaxy S 4] eiddor:
Got it -- I'll have it start logging soon. Hopefully there's size limitation and it will automatically roll-over the logs :)
[Verizon Samsung Galaxy S 4] xander45:
I just have to give major props to this dude for helping a brother out......many, many thanks!!!
[Verizon Samsung Galaxy S 4] dark_overload:
I don't think there is a size limitation, but I highly doubt you'll fill up the storage in the time it takes to log a crash. It's also likely that it does not rotate. It would be nice if Android worked more like its *nix big brothers, that's for sure.

Thanks again for going out of your way to catch the logs for me. :)
[Verizon Samsung Galaxy S 4] alexsahka:
Just got I545 with 4.2.2 official ROM is it good idea to install this ROM(I want newer ROM)?

And any guide (link to guide) where I can get what is requirements for such move.

Thank you.
[Verizon Samsung Galaxy S 4] dark_overload:
I love it! As long as you don't have any haunted files left on your SD it works great!

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

Look here for information on rooting (required) and recovery.

Also please note that this ROM is geared toward those of us who are fortunate enough to have held on to their MDK bootloader. It may or may not work on SS. See a few posts back for a link to Jrkruse's international build which is SafeStrap compatible.

Make sure you also make backups beforehand, just in case. I would also recommend the "shotgun wipe" at least for now.
[Verizon Samsung Galaxy S 4] alexsahka:
Thank you.
[Verizon Samsung Galaxy S 4] dark_overload:
Don't mention it. Happy to help.

If you discover that you have an MDK bootloader and you decide to flash this specific build, then subsequently have the battery drain and/or random reboot issue (which can be avoided by performing the shotgun wipe), please let us know here.
[Verizon Samsung Galaxy S 4] alexsahka:
How to check bootloader version? I got 3e in recovery.
[Verizon Samsung Galaxy S 4] dark_overload:
That link I sent you to has the instructions for checking the bootloader version, it's pretty easy to do from a terminal.

u0_a232@jflitevzw:/ $ getprop ro.bootloader
I545VRUAMDK
u0_a232@jflitevzw:/ $
[Verizon Samsung Galaxy S 4] mochamoo:
There's also this little utility in the play store that will give you all kinds of info about your device, including bootloader version if you aren't comfortable with using a terminal server.

https://play.google.com/store/apps/details?id=com.jphilli85.deviceinfo
[Verizon Samsung Galaxy S 4] bryantjopplin:
IMO if they are romming, they need to learn.
[Verizon Samsung Galaxy S 4] jds3118:
I agree if romming you it's good to know how to use terminal emulator but he is just trying to get his boobloader info ? that app gives you everything see pics