Database Users

Question About Software Error Message

Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.

chokem said:
Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.
Click to expand...
Click to collapse
So, to sum up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573

Furies said:
So, to some up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Click to expand...
Click to collapse
OK, thanks very much. So I was indeed on the right track. I'll try your ROM recommendation as well as the modified CWM recovery.

[Guide]ATT KitKat leak working with root

I have been trying to get the KitKat leak working in a safestrap rom slot for days. Each time it failed, and I concluded that it was currently incompatible with the hijack Hashcode was using. So, I tried flashing my KK rom to the stock slot, and then I immediately flashed supersu. Voila, KitKat with root on my locked at&t moto x!
The interesting thing is that this method should work for any rom that is compatible with the stock kernels (because locked bootloader wont allow any other kernel). Hopefully this will 'open the floodgates' to flashing AOSP roms on locked devices that can run safestrap.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE. With that said, this doesn't touch your bootloader, and you should be able to restore back to stock if there is a problem.
Here are the steps I followed on my locked ATT moto x starting with the at&t stock .51 rom:
1) extract ext4 filesystem image from leak's system.img
2) used android kitchen (thanks dsixda) to cook a flashable rom and fixed some symlinks with help from the updater-script found in dhacker29's 4.4 rom
3) root (pwnmymoto - thanks jcase)
4) install safestrap (thanks Hashcode)
5) copied the rom I cooked to sdcard
6) copied supersu flashable zip to sdcard (thanks chainfire)
7) booted to SS TWRP recovery
8) switched to stock rom slot
9) flashed my cooked rom
10) immediately flashed supersu
11) rebooted into bootloader
12) flashed kitkat kernel: fastboot flash boot boot.img
13) cleared cache and userdata
(I left the modem from the 4.2.2 .54 update)
Rebooted to kitkat with root!
I haven't tested bluetooth, but wifi and gps work. Strangely, the safestrap 'recovery or continue' screen is still there, but the /ss directory is empty. (I would like to know how to manually remove ss, as it is almost certainly not working now.)
I would be happy to share my flashable 4.4 rom, but I noticed that the original leak was taken down. What/where is the smart place to get this up?

I found a place to upload the rom: http://forum.xda-developers.com/showthread.php?p=47451659#post47451659
Hopefully the instructions there are clear...

Can I ask how you extracted from the system.img? I tried to follow the guide that uses ext4_unpacker, but it won't open it. It just says unknown file format. Guessing you did it on a Linux machine?

Ctrl-Freak said:
I have been trying to get the KitKat leak working in a safestrap rom slot for days. Each time it failed, and I concluded that it was currently incompatible with the hijack Hashcode was using. So, I tried flashing my KK rom to the stock slot, and then I immediately flashed supersu. Voila, KitKat with root on my locked at&t moto x!
The interesting thing is that this method should work for any rom that is compatible with the stock kernels (because locked bootloader wont allow any other kernel). Hopefully this will 'open the floodgates' to flashing AOSP roms on locked devices that can run safestrap.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE. With that said, this doesn't touch your bootloader, and you should be able to restore back to stock if there is a problem.
Here are the steps I followed on my locked ATT moto x starting with the at&t stock .51 rom:
1) extract ext4 filesystem image from leak's system.img
2) used android kitchen (thanks dsixda) to cook a flashable rom and fixed some symlinks with help from the updater-script found in dhacker29's 4.4 rom
3) root (pwnmymoto - thanks jcase)
4) install safestrap (thanks Hashcode)
5) copied the rom I cooked to sdcard
6) copied supersu flashable zip to sdcard (thanks chainfire)
7) booted to SS TWRP recovery
8) switched to stock rom slot
9) flashed my cooked rom
10) immediately flashed supersu
11) rebooted into bootloader
12) flashed kitkat kernel: fastboot flash boot boot.img
13) cleared cache and userdata
(I left the modem from the 4.2.2 .54 update)
Rebooted to kitkat with root!
I haven't tested bluetooth, but wifi and gps work. Strangely, the safestrap 'recovery or continue' screen is still there, but the /ss directory is empty. (I would like to know how to manually remove ss, as it is almost certainly not working now.)
I would be happy to share my flashable 4.4 rom, but I noticed that the original leak was taken down. What/where is the smart place to get this up?
Click to expand...
Click to collapse
Glad to see locked BLs getting some love. Any chance of KK screenshots? No one seems to have uploaded them on any thread. How has your experience been with it so far?

freak4dell said:
Can I ask how you extracted from the system.img? I tried to follow the guide that uses ext4_unpacker, but it won't open it. It just says unknown file format. Guessing you did it on a Linux machine?
Click to expand...
Click to collapse
This took me a day to figure out. I used simg2img in ubuntu.

anirudh412 said:
... How has your experience been with it so far?
Click to expand...
Click to collapse
The only material problem I am having is battery life - it seems noticeably worse that the att .54 ota version.

Installation Aborted - Status 7 (expected 5 arguments, got 4)

I've been trying to flash TheAxman 's [ROMS][ViSiON-X STOCK SHOP][i9505/i337][ViS-STOCK][STABLE BASES][03-18] but i keep getting a status 7, installation aborted error which claims that the the expected number of arguments is 5, got 4.
the steps i did to get this error message were:
wipe data/ factory reset --> wipe cache --> format system --> wipe dalvik --> install VisionX's rom
My device is the i337m, its unlocked im with telus
i attached a screenshot of the about phone info for reference.
The device is rooted using cf-auto, and has cwm 6.0.4.7 installed, running on 4.2.2 stock ROM
Now from what i understood in the installation instructions, I should be flashing my carrier's kernel after installing the new ROM, but i cant even get past the rom installation.. I read around the forums that this might be due to a broken updater script, I 'm also iffy as to where/ how I could get a hold of my carriers kernel file to use after (hopefully) i get Vision-X installed on the device..
according to ktoonsez, I should use [KERNEL][TMO][AOSP/TW/GE - 4.4/4.3/4.2][03/12/2014] KT-SGS4 - MJ5 - KTweaker
lastly, i dont know if this is relevant, but in the CWM log i have a message that shows up saying the following
"can't partition non mmcblk device: /devices/platform/msm_sdcc . 2/mmc_host/mmc2"
thank you in advance for your time and assistance

Anyone?
happiness is a warm mug

The French Tickl3r said:
I've been trying to flash TheAxman 's [ROMS][ViSiON-X STOCK SHOP][i9505/i337][ViS-STOCK][STABLE BASES][03-18] but i keep getting a status 7, installation aborted error which claims that the the expected number of arguments is 5, got 4.
the steps i did to get this error message were:
wipe data/ factory reset --> wipe cache --> format system --> wipe dalvik --> install VisionX's rom
My device is the i337m, its unlocked im with telus
i attached a screenshot of the about phone info for reference.
The device is rooted using cf-auto, and has cwm 6.0.4.7 installed, running on 4.2.2 stock ROM
Now from what i understood in the installation instructions, I should be flashing my carrier's kernel after installing the new ROM, but i cant even get past the rom installation.. I read around the forums that this might be due to a broken updater script, I 'm also iffy as to where/ how I could get a hold of my carriers kernel file to use after (hopefully) i get Vision-X installed on the device..
according to ktoonsez, I should use [KERNEL][TMO][AOSP/TW/GE - 4.4/4.3/4.2][03/12/2014] KT-SGS4 - MJ5 - KTweaker
lastly, i dont know if this is relevant, but in the CWM log i have a message that shows up saying the following
"can't partition non mmcblk device: /devices/platform/msm_sdcc . 2/mmc_host/mmc2"
thank you in advance for your time and assistance
Click to expand...
Click to collapse
Check if your download is good first. However, I don't believe you can use that kernel as it says I337 and not I337m.

Installation Aborted - Status 7 (expected 5 arguments, got 4) > Reply to Thread
DeadlySin9 said:
Check if your download is good first. However, I don't believe you can use that kernel as it says I337 and not I337m.
Click to expand...
Click to collapse
thank you for your input, I will redownload the file to cross that out. as for the kernel, how/where might I be able to find it? Can I simply use the stock kernel on 4.2.2 from telus ?

The French Tickl3r said:
thank you for your input, I will redownload the file to cross that out. as for the kernel, how/where might I be able to find it? Can I simply use the stock kernel on 4.2.2 from telus ?
Click to expand...
Click to collapse
Stock kernel will work as long as you're only using other 4.2.2 Touchwiz ROMs. Otherwise, you can check the development section for any kernel thread that lists I337m

DeadlySin9 said:
Stock kernel will work as long as you're only using other 4.2.2 Touchwiz ROMs. Otherwise, you can check the development section for any kernel thread that lists I337m
Click to expand...
Click to collapse
Kernel is right. TMO for the I337M.
I've had status 7 errors before using philz and they were solved using 1 of 2 methods. First, I would check the rom for asserts (txt at the beginning of the updater-script that checks ur device version code against those intended for the roms use). If u find an assert in the script, just delete it and try the install again.
Second thing u could try that worked for me was (idk if standard cwm has this option but philz does) checking the 'allow old update binary' box in the settings. If it's not there, try philz or twrp.
Lastly, like deadly said, don't flash the kernel til u get the ROM to boot. That way troubleshooting is easier

thank you both for your valuable input. I will give it another shot

Recovery..
The French Tickl3r said:
I've been trying to flash TheAxman 's [ROMS][ViSiON-X STOCK SHOP][i9505/i337][ViS-STOCK][STABLE BASES][03-18] but i keep getting a status 7, installation aborted error which claims that the the expected number of arguments is 5, got 4.
the steps i did to get this error message were:
wipe data/ factory reset --> wipe cache --> format system --> wipe dalvik --> install VisionX's rom
My device is the i337m, its unlocked im with telus
i attached a screenshot of the about phone info for reference.
The device is rooted using cf-auto, and has cwm 6.0.4.7 installed, running on 4.2.2 stock ROM
Now from what i understood in the installation instructions, I should be flashing my carrier's kernel after installing the new ROM, but i cant even get past the rom installation.. I read around the forums that this might be due to a broken updater script, I 'm also iffy as to where/ how I could get a hold of my carriers kernel file to use after (hopefully) i get Vision-X installed on the device..
according to ktoonsez, I should use [KERNEL][TMO][AOSP/TW/GE - 4.4/4.3/4.2][03/12/2014] KT-SGS4 - MJ5 - KTweaker
lastly, i dont know if this is relevant, but in the CWM log i have a message that shows up saying the following
"can't partition non mmcblk device: /devices/platform/msm_sdcc . 2/mmc_host/mmc2"
thank you in advance for your time and assistance
Click to expand...
Click to collapse
that recovery using these?

I switched to twrp 2.6.3.0, and im not getting the stat7 error anymore. granted, im also trying to flash a different rom, slimkat.
problem now is that im getting stuck on the splash screen with the sammie logo..

The French Tickl3r said:
I switched to twrp 2.6.3.0, and im not getting the stat7 error anymore. granted, im also trying to flash a different rom, slimkat.
problem now is that im getting stuck on the splash screen with the sammie logo..
Click to expand...
Click to collapse
You flashed the ROM and Gapps and made sure to wipe data right? Also, which one are you flashing (which model)?

DeadlySin9 said:
You flashed the ROM and Gapps and made sure to wipe data right? Also, which one are you flashing (which model)?
Click to expand...
Click to collapse
hi deadlysin9,
thank you for the follow up
steps were:
boot to twrp 2.6.3.0 recovery, wipe data, cache, system and dalvik
then flash rom and gapps
my device is the i337m (telus but unlocked) and im using the jflteatt found here,

The French Tickl3r said:
hi deadlysin9,
thank you for the follow up
steps were:
boot to twrp 2.6.3.0 recovery, wipe data, cache, system and dalvik
then flash rom and gapps
my device is the i337m (telus but unlocked) and im using the jflteatt found here,
Click to expand...
Click to collapse
Try using the jfltetmo build, from what I've read t-mobile ROMs and kernels work on the I337m. If that doesn't work the international build is the next best bet.

hello,
just a quick update on our latest discussion, it seems that the tmo build is indeed the right one to flash, ive finally rid myself of TW, and running on slimkat. many thanks for your valuable input.

[Q] "Unfortunately, the process com.android.phone has stopped."

After flashing the SKYFALL (6.1) my GS 4(AT&T I337, NC1), I am getting an error box as soon as I swipe the locked screen that says "Unfortunately, the process com.android.phone has stopped." each time after reboot. I hit OK twice and continue ( I noticed that the 4G LTE lost a couple seconds and shows up again) and am seeing no other problems, but it is annoying and a bit disturbing. This happened only after reboot the phone.
I search online, and tried:
1.) cache wipe
2.) Settings->applications manager- / Choose reset app preferences / Choose Reset Apps
3.) Settings - date and time setting - turn off automatic time zone.
4.) go to setting >> app manager >> all app >> phone >> clear data ?
and no lucky.
However, I run stock rom or flash GoldenEye (for I9505, without 4G LTE?) there is no such problem.
Could someone please offer some advice? Thanks you.

Did you wipe cache and data in Safestrap before you ran the Aroma installer?

I did exactly the following
1.) Download the latest ROM, SuperSU, and your modules.
2.) Place them on root of your MicroSD card.
3.) In Safestrap, factory reset twice.
4.) Now wipe all except MicroSD card twice.
5.) Flash the ROM zip.
7.) Now flash the modules zip file.
8.) Now flash SuperSU update.
9.) Reboot and let it sit for 5 minutes.
Also, I flashed Goldeneye (also by iB4STiD) without such problem.

I just noticed the SKYFALL ROM you linked to is on NI1 base. That's your problem.

jdisco1 said:
I just noticed the SKYFALL ROM you linked to is on NI1 base. That's your problem.
Click to expand...
Click to collapse
I took OTA to NI1. Everything's OK when using NI1 stock; after flashing SKYFALL, the same thing happened.
PS:
I tried the SlimSung (UCUFNI1 also) on my base NC1, everything's OK. However, slimsung is a slim version, I don't like it too much. So I took OTA to NI1...

macos6 said:
I took OTA to NI1. Everything's OK when using NI1 stock; after flashing SKYFALL, the same thing happened.
PS:
I tried the SlimSung (UCUFNI1 also) on my base NC1, everything's OK. However, slimsung is a slim version, I don't like it too much. So I took OTA to NI1...
Click to expand...
Click to collapse
Obviously you know what you're doing if you could get other ROMs on there with no trouble. I highly doubt this would cause that, but did you also flash the NI1 kernel modules and NI1 modem?
Only things that could be wrong in my book:
- Corrupted download (Try downloading it again)
- Wong version of Safestrap (NC1 and up use 3.72)
- One of the options you picked in Aroma is breaking it
Also, here's the Safestrap installation instructions for that ROM
http://forum.xda-developers.com/showpost.php?p=53038182&postcount=13961
For those coming from a previous 4.4.2 ROM or rooted NB1, NC1, or NI1...*
1. Reboot into Safestrap 3.72 Recovery
2. Wipe > Advanced Wipe > everything EXCEPT extsdcard*
3. Install latest ROM zip
4. In Aroma, select "Safestrap" version and continue through selections
5. When Aroma finishes, uncheck "reboot" option and then press "reboot" to exit back to safestrap.
6. Install ATT Modules
7. Install SuperSU
8. Reboot

but did you also flash the NI1 kernel modules and NI1 modem?
Click to expand...
Click to collapse
I followed exactly in guut13's thread post #5 under the title "NI1 ROOTED WITH SAFESTRAP" to upgrade to NI1.
I downloaded all the files to my PC folder "NI1" and checked all the MD5, all is OK
My Safestrap version is latest 3.72; also followed the steps in the post.
I saved the install guide to .doc file, and perform each step according to the guide.
I think the problem is weird. I flashed GoldenEye by iB4STiD also, no problem. (however, maybe there is no 4G LTE? or just the network icon problem? I am not quite sure, if this version support 4G LTE then I can use this version-I have backups)
thank you.

Bootloop after successfully rooting and flashing BS free rom

As the title suggests, I am having trouble with a bootloop after successfully rooting a BOK3 stock GS5 5.0, installing SafeStrap and successfully flashing steps 2, 4 and 8 on this guide.
I can exit the bootloop by pulling the battery, booting into download mode, downgrading to the ni2 kernel using Odin and finally making it back to SafeStrap. From here however, I'd like some input on how to proceed.
I think I'd like to try to revert all changes through whatever means, all data has been backed up so I'm not concerned about that.
Thanks in advance

problem was being caused by /data not mounting properly, I assume it got corrupted somewhere along the way. Full wipe of everything but sd card fixed the problem and allowed flawless running of the deodexed stock BOK3 rom generously provided by jrkruse, thanks to CVertigo1 for the pointers.

T3nmoku said:
problem was being caused by /data not mounting properly, I assume it got corrupted somewhere along the way. Full wipe of everything but sd card fixed the problem and allowed flawless running of the deodexed stock BOK3 rom generously provided by jrkruse, thanks to CVertigo1 for the pointers.
Click to expand...
Click to collapse
For future reference, you should post issues in that specific ROM thread instead of the generic troubleshooting forum. You'll get help much quicker in the appropriate thread.