[Q] - Impossible to flash stock rom - Galaxy S 4 Mini Q&A, Help & Troubleshooting

[Q] - Impossible to flash stock rom - Galaxy S 4 Mini Q&A, Help & Troubleshooting

I have been using CM-based roms since I first got my i9195 in September and left TW stock rom behind. But I now decided to go back to stock and I just can't.
My phone has no Knox.
Each time I try to flash ANY recent stock rom with Odin, I get this:
The phone displays
Code:
ODIN : Invalid ext4 image
Odin 3.07 and 3.09 gives
Code:
<ID:0/013> Added!!
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> SingleDownload.
<ID:0/013> rpm.mbn
<ID:0/013> NAND Write Start!!
<ID:0/013> tz.mbn
<ID:0/013> boot.img
<ID:0/013> recovery.img
<ID:0/013> system.img.ext4
<ID:0/013> NON-HLOS.bin
<ID:0/013> cache.img.ext4
<ID:0/013> hidden.img.ext4
<ID:0/013> FAIL! (Ext4)
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Heimdall
Code:
Downloading device's PIT file...
PIT file download successful.
Uploading HIDDEN
62%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: HIDDEN upload failed!
It ALWAYS happens on hidden.img.ext4.
I tried different stock roms (after removing KNOX) - every time it's the same thing.
I tried removing this hidden partition from the rom - rom flashed, but got stuck on Samsung logo.
I tried converting stick Odin format to flashable CWM zip - rom flashed, but got stuck on Samsung logo.
Non-stock roms flash and work perfectly fine.
I am out of ideas. Do you have any?

Here is Odin guide. It should help.
http://forum.xda-developers.com/showthread.php?t=1372414
Sent from my Hudl HT7S3 using Tapatalk
---------- Post added at 09:47 PM ---------- Previous post was at 09:47 PM ----------
I'd like to know how to do this myself. If you figure it out. Let us know in thread please.
Sent from my Hudl HT7S3 using Tapatalk

same problem here.
can't flash stock rom..
1.
and this is what odin says
2. St*pid anti spam
I flashed couple of times, and with out any problem.
just to add, no help with Kies. tried to do firmware upgrade, but when i enter model number GT-I9195
and then in next screen s/n number, says 'GT-I9195' dose not support initialising
the only way i was able to bring it back to life was to flash a CWM. (don't know how i think of that)
after that phone booted normally, but still can't flash rom via odin.
and Kies is waste of time because it even won't recognise my phone. no connection what so ever. Win pop's up auto play window, and I'm already browsing internal storage, but Kies is still trying to recognise phone.. after about 15 min it says to reboot my phone, because it can't connect :laugh:
Samsung and their stuff. Pffff...
but to be back with real problem. haven't figure out this problem yet. but will try to re flash same stock rom, to see if it's a rom problem or phone it self. I'm guessing the partition table is changed for this new builds of rom's so it can't be flashed. or some other wired stuff.
if someone has some good advice, or even better, has an answer how to flash this new stock rom..

wizard.no.84 said:
just to add, no help with Kies. tried to do firmware upgrade, but when i enter model number GT-I9195
and then in next screen s/n number, says 'GT-I9195' dose not support initialising
Click to expand...
Click to collapse
Don't use Kies. It will punch you in the face with KNOX. Oh, wait... I see form you screenshots It already did...
Anyway, I also thought it might be changed partition layout, but that would be strange because it would also prevent other people to upgrade form stock to newer stock... Hmm...
In the meantime, I tried CWM-flashing this http://forum.xda-developers.com/showthread.php?t=2552363 and, unlike my modded stock roms based on newer bases, this did work (not on PhilZ though). I am running it now, but as I said - this is a bit outdated and does not solve the main problem.

Knox is a least of my problem.. i can remove it after, but i don't know whats the deal..
I'm downloading free region rom "X.." and the one I already have in the phone and try to flash them.
but knowing server down limit, it will take a while.

wizard.no.84 said:
Knox is a least of my problem.. i can remove it after, but i don't know whats the deal..
Click to expand...
Click to collapse
No, you can't. You can remove apps but Knox is there to stay and your Void Warranty flag is already tripped. Just look at your bootloader screenshot.
But on the bright side - you have nothing more to lose at this point

impactor said:
But on the bright side - you have nothing more to lose at this point
Click to expand...
Click to collapse
:laugh::laugh::laugh::crying: that's true :good:

OK, I see that you are using a PIT file. Was there the "Re-Partition" also enabled?
I never tried the scenario above I always flash new stock FW as a single-file package and browse it via Odin AP button.

ladislav.heller said:
OK, I see that you are using a PIT file. Was there the "Re-Partition" also enabled?
Click to expand...
Click to collapse
I don't think I am using a PIT file. Where do you see it? Re-Partition was always disabled.
ladislav.heller said:
I never tried the scenario above I always flash new stock FW as a single-file package and browse it via Odin AP button.
Click to expand...
Click to collapse
Which is what I am doing in the part describing Odin flashing.

Here's some more specifics:
ladislav.heller said:
Easily:
You did not say nothing about Odin version you used.
Click to expand...
Click to collapse
impactor said:
Odin 3.07 and 3.09 gives
Click to expand...
Click to collapse
ladislav.heller said:
Nothing about Samsung drivers version, Kies presence, etc.
Click to expand...
Click to collapse
As indicated, I did that in Windows and in Linux and the process stops at the same stage, which suggests driver version irrelevant.
In case this assumption is wrong: on Windows it is Kies 2.6.2.14014_7 and driver 2.11.7.
ladislav.heller said:
You did not specify WHAT firmwares you exactly tried, from where you downloaded them.
Click to expand...
Click to collapse
FTM I9195XXUBNB3
EVR I9195XXUBNB3
and one of the old I9195XXUBMJ7
Downloaded from here: http://samsung-updates.com/device/?id=GT-I9195 and samfirmware.com
ladislav.heller said:
Were the downloaded firmwares corrupt or not? Did you try to unpack them manually?
Click to expand...
Click to collapse
Not corrupt, as suggested by several different firmwares tried.
Yes, I unpacked them manually in order to remove knox. Like so: http://forum.xda-developers.com/showthread.php?t=2549357
Also, author of that guide did the whole rom-deknoxing by himself for me, too, and the result was the same.
The rest of your questions relate to CWM flashing method.
ladislav.heller said:
You did not say, how you built your modded ROM in Kitchen.
Click to expand...
Click to collapse
I tried some, and I tried no modifications. Same result.
ladislav.heller said:
You did not send me the update script for you modded ROM.
Click to expand...
Click to collapse
update, or updater? Here is the later one:
Code:
show_progress(0.1, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p21");
mount("ext4", "EMMC", "/dev/block/mmcblk0p21", "/system");
package_extract_dir("system", "/system");
symlink("toolbox", "/system/bin/cat");
symlink("toolbox", "/system/bin/chcon");
symlink("toolbox", "/system/bin/chmod");
symlink("toolbox", "/system/bin/chown");
symlink("toolbox", "/system/bin/cmp");
symlink("toolbox", "/system/bin/cp");
symlink("toolbox", "/system/bin/date");
symlink("toolbox", "/system/bin/dd");
symlink("toolbox", "/system/bin/df");
symlink("toolbox", "/system/bin/dmesg");
symlink("toolbox", "/system/bin/du");
symlink("toolbox", "/system/bin/freshsebool");
symlink("toolbox", "/system/bin/getenforce");
symlink("toolbox", "/system/bin/getevent");
symlink("toolbox", "/system/bin/getprop");
symlink("toolbox", "/system/bin/getsebool");
symlink("toolbox", "/system/bin/grep");
symlink("toolbox", "/system/bin/hd");
symlink("toolbox", "/system/bin/id");
symlink("toolbox", "/system/bin/ifconfig");
symlink("toolbox", "/system/bin/iftop");
symlink("toolbox", "/system/bin/insmod");
symlink("toolbox", "/system/bin/ioctl");
symlink("toolbox", "/system/bin/ionice");
symlink("toolbox", "/system/bin/kill");
symlink("toolbox", "/system/bin/ln");
symlink("toolbox", "/system/bin/load_policy");
symlink("toolbox", "/system/bin/log");
symlink("toolbox", "/system/bin/ls");
symlink("toolbox", "/system/bin/lsmod");
symlink("toolbox", "/system/bin/lsof");
symlink("toolbox", "/system/bin/md5");
symlink("toolbox", "/system/bin/mkdir");
symlink("toolbox", "/system/bin/mount");
symlink("toolbox", "/system/bin/mv");
symlink("toolbox", "/system/bin/nandread");
symlink("toolbox", "/system/bin/netstat");
symlink("toolbox", "/system/bin/newfs_msdos");
symlink("toolbox", "/system/bin/notify");
symlink("toolbox", "/system/bin/printenv");
symlink("toolbox", "/system/bin/ps");
symlink("toolbox", "/system/bin/reboot");
symlink("toolbox", "/system/bin/renice");
symlink("toolbox", "/system/bin/restorecon");
symlink("toolbox", "/system/bin/rm");
symlink("toolbox", "/system/bin/rmdir");
symlink("toolbox", "/system/bin/rmmod");
symlink("toolbox", "/system/bin/route");
symlink("toolbox", "/system/bin/runcon");
symlink("toolbox", "/system/bin/schedtop");
symlink("toolbox", "/system/bin/sendevent");
symlink("toolbox", "/system/bin/setconsole");
symlink("toolbox", "/system/bin/setenforce");
symlink("toolbox", "/system/bin/setprop");
symlink("toolbox", "/system/bin/setsebool");
symlink("mksh", "/system/bin/sh");
symlink("toolbox", "/system/bin/sleep");
symlink("toolbox", "/system/bin/smd");
symlink("toolbox", "/system/bin/start");
symlink("toolbox", "/system/bin/stop");
symlink("toolbox", "/system/bin/sync");
symlink("toolbox", "/system/bin/top");
symlink("toolbox", "/system/bin/touch");
symlink("toolbox", "/system/bin/umount");
symlink("toolbox", "/system/bin/uptime");
symlink("toolbox", "/system/bin/vmstat");
symlink("toolbox", "/system/bin/watchprops");
symlink("toolbox", "/system/bin/wipe");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm(0, 3003, 06755, "/system/bin/ip");
set_perm(0, 3003, 02750, "/system/bin/netcfg");
set_perm(0, 3004, 02755, "/system/bin/ping");
set_perm(0, 2000, 06750, "/system/bin/run-as");
set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluetooth");
set_perm(0, 0, 0755, "/system/etc/bluetooth");
set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pairing.conf");
set_perm(3002, 3002, 0444, "/system/etc/bluetooth/blacklist.conf");
set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pair_devlist.conf");
set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");
set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");
set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
set_perm_recursive(0, 0, 0755, 0644, "/system/vendor/firmware");
set_perm(0, 2000, 0755, "/system/vendor/firmware");
set_perm(0, 2000, 0755, "/system/vendor/lib");
set_perm(0, 2000, 0755, "/system/vendor/lib/hw");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
show_progress(0.1, 10);
show_progress(0.2, 0);
package_extract_file("boot.img", "/dev/block/mmcblk0p13");
show_progress(0.2, 10);
unmount("/system");
ladislav.heller said:
Bootloop maybe caused by kernel. Which kernel you are using?
Click to expand...
Click to collapse
Stock.
Thanks for taking the interest in it.

Odin part:
Did you UNPACKED the original stock FW and removed the Knox bootloader files?
What did you do next? Repacked them into TAR with MD5 checksum? If yes, what commands you used?
Kitchen part:
Have you replaced the kernel (boot.img) + needed modules in the result ZIP package to Arco's one or another modded kernel? Because with the stock kernel it won't work.

X.. rome worked
i just flashed open region rom and got PASS
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
wtf?

ladislav.heller said:
Odin part:
Did you UNPACKED the original stock FW and removed the Knox bootloader files?
What did you do next? Repacked them into TAR with MD5 checksum? If yes, what commands you used?
Click to expand...
Click to collapse
Code:
unzip *.zip
rm -rf SS_DL.dll
tar -xvf *.tar.md5
rm -rf aboot.mbn
rm -rf sbl1.mbn
rm -rf sbl2.mbn
rm -rf sbl3.mbn
rm -rf *.tar.md5
tar -H ustar -c rpm.mbn tz.mbn boot.img recovery.img system.img.ext4 NON-HLOS.bin cache.img.ext4 hidden.img.ext4 > name.tar
And then I flash, because if I add md5, Odin will display some error message in Korean while loading it.
ladislav.heller said:
Kitchen part:
Have you replaced the kernel (boot.img) + needed modules in the result ZIP package to Arco's one or another modded kernel? Because with the stock kernel it won't work.
Click to expand...
Click to collapse
You mean I need to replace the stock kernel, because it will not work if flashing with CWM?
If that's the case, then can I use the JB version from here? http://forum.xda-developers.com/showthread.php?t=2568479

impactor said:
Code:
unzip *.zip
rm -rf SS_DL.dll
tar -xvf *.tar.md5
rm -rf aboot.mbn
rm -rf sbl1.mbn
rm -rf sbl2.mbn
rm -rf sbl3.mbn
rm -rf *.tar.md5
tar -H ustar -c rpm.mbn tz.mbn boot.img recovery.img system.img.ext4 NON-HLOS.bin cache.img.ext4 hidden.img.ext4 > name.tar
And then I flash, because if I add md5, Odin will display some error message in Korean while loading it.
You mean I need to replace the stock kernel, because it will not work if flashing with CWM?
If that's the case, then can I use the JB version from here? http://forum.xda-developers.com/showthread.php?t=2568479
Click to expand...
Click to collapse
Odin part - try these commands:
Code:
tar -H ustar -c rpm.mbn tz.mbn boot.img recovery.img system.img.ext4 NON-HLOS.bin cache.img.ext4 hidden.img.ext4 > name.tar
md5sum -t name.tar >> name.tar
mv name.tar name.tar.md5
And use name.tar.md5 in Odin.
Kitchen part:
Use this kernel.

ladislav.heller said:
Odin part - try these commands:
Code:
tar -H ustar -c rpm.mbn tz.mbn boot.img recovery.img system.img.ext4 NON-HLOS.bin cache.img.ext4 hidden.img.ext4 > name.tar
md5sum -t name.tar >> name.tar
mv name.tar name.tar.md5
And use name.tar.md5 in Odin.
Click to expand...
Click to collapse
As I said, if I do this, Odin won't even open file, just return an error in Korean. Tried it already on several roms.
ladislav.heller said:
Kitchen part:
Use this kernel.
Click to expand...
Click to collapse
Thanks. Do I just replace files form the zip in the kitchen's work folder, or do I need to do it some other way?

impactor said:
As I said, if I do this, Odin won't even open file, just return an error in Korean. Tried it already on several roms.
Thanks. Do I just replace files form the zip in the kitchen's work folder, or do I need to do it some other way?
Click to expand...
Click to collapse
Odin part:
Are you using Odin v3.09 ?
BTW I have no idea
Kitchen part:
Yes, replace in working folder before the build of final ROM.
Replace everything and when there is something extra in f4k kernel, also add those files to the correct directories.

I had this to make sure the Stock one you are flashing with ODIN is for your device as I tried a few here in the UK
And only the BTU ones work on my device for some reason as tried EE (Orange who is my sim card with) and doesnt work
Failing that then use Recovery via Kies
Similar to this as I dont have the right link handy :LINK

If you will face this "hidden.ext.img4" problem again, solution is simple. The complete firmware was correctly written and u just need to boot it for the first time.
When the error happens, dont reboot the phone. Just unplug and replug the usb cable and flash a stock recovery image (just the recovery.img file packed in a *.tar.md5 file) with odin. Flashing will complete and when the phone will reboot, you have to go in recovery mode with the 3 button trick. Your phone will automatically complete the flashing procedure and firmware will be installed and booted.

I dont think that will work. Because when i got that "hiddent.ext" error, and when i flashed the CWM and rebooted, i was back at the beginig. Didn't check build in "settings-about" but im prety sure i was on old rom, (not the new flash) because root was still present.
Only now when i flashed it successfully the root is gone
Sent from iPhone

It work, surely. Tried it several times on my i9195 the file you need to flash is the stock recovery file extracted from the firmware image you are installing.
I've modified my previous post adding more details. I don't know if i can upload and post an example recovery image for copyright issues.

Related

[Q] Creating a Kernel update zip file

Ok I'm a bit confused. After hours upon hours of trying, I have yet to successfully create a WORKING update.zip file for flashing a kernel.
I'm trying to create an update.zip file for the 2.6.35.10 kernel from the leaked T-Mobile US Gingerbread 2.13.531.5 ROM.
I properly unpacked the boot.img from the ROM, and my updater-script file seems correct, then I create the zip, sign it and flash thru CWM. The update completes without errors, however, when I reboot the phone, it still says I have 2.6.32.28. I'm stuck. My updater-script is as follows:
Code:
ui_print("");
ui_print("T-Mobile US - G2 Kernel Update");
ui_print("Kernel Version: 2.6.35.10");
ui_print("Prepared by: spyral");
ui_print("");
ui_print("Using: AnyKernel Updater by Koush.");
ui_print("");
set_progress(1.000000);
ui_print("Clearing dalvik and boot cache ...");
delete_recursive("/data/dalvik-cache");
delete_recursive("/data/boot-cache");
ui_print("Extracting System Files...");
set_progress(2.000000);
mount("yaffs2", "MTD", "system", "/system");
package_extract_dir("system", "/system");
unmount("/system");
set_progress(5.000000);
ui_print("");
ui_print("Extracting Kernel files...");
package_extract_dir("kernel", "/tmp");
ui_print("Installing kernel...");
set_progress(6.000000);
set_perm(0, 0, 0777, "/tmp/dump_image");
set_perm(0, 0, 0777, "/tmp/mkbootimg.sh");
set_perm(0, 0, 0777, "/tmp/mkbootimg");
set_perm(0, 0, 0777, "/tmp/unpackbootimg");
run_program("/tmp/dump_image", "boot", "/tmp/boot.img");
run_program("/tmp/unpackbootimg", "-i", "/tmp/boot.img", "-o", "/tmp/");
run_program("/tmp/mkbootimg.sh");
write_raw_image("/tmp/newboot.img", "boot");
set_progress(10.000000);
ui_print("Done!");
I've tried multiple times, with no luck. Any ideas?

Btw, sorry if I posted this in the wrong forum Mods... feel free to move it if need be. I'm still learning the ropes of this place.
Sent from my HTC Vision using XDA Premium App

Nothin so far, huh?
Sent from my HTC Vision using XDA Premium App

Still nothin on this??
Sent from my HTC Vision using XDA Premium App

Flashable ZIP How To?

How do you make flashable zip?
i have alot of mods on my arc s and i want them all in one and flashable..

http://forum.xda-developers.com/showthread.php?t=1374394
Flashable Zip

In few words:
You make a zip file with the order of how the files go.
You make an updater-script which are the instructions for CWM to flash the correct order.
You sign it and that's it.
Everything is in the tutorial XperienceD posted.

XperienceD said:
http://forum.xda-developers.com/showthread.php?t=1374394
Flashable Zip
Click to expand...
Click to collapse
IM sorry but im kinda slow... in the "Flashable Clockwork Mod (CWM) zip:"
TO UNDERSTAND UR GUIDE I OPEN SOME SCRIPT TO GET AN IDEA BUT I FOUND SOME LINES THAT IS NOT INCLUDED IN YOUR EXAMPLE.
LIKE THESE:
show_progress(1.000000, 0);
set_progress(0.125000);
mount("MTD", "system", "/system");
package_extract_file("fix_permissions", "/tmp/fix_permissions");
set_perm(0, 0, 0777, "/tmp/fix_permissions");
WHAT IS show_progress(1.000000, 0); AND set_progress(0.125000); ??
I GUESS mount("MTD", "system", "/system") IS THE SAME AS run_program("/sbin/mount", "/system"); ??
AND ALSO GUESS THAT package_extract_file("fix_permissions", "/tmp/fix_permissions"); AND set_perm(0, 0, 0777, "/tmp/fix_permissions"); IS FOR THE PERMISSIONS, IF U HAVE IN UR ZIP RIGHT?
I DONT REALLY UNDERSTAND THOSE OR I CAN JUST IGNORE THEM?

[Q] Halp Me! Wiped everything but recovery

So I wiped everything but recovery from my tmobile s3, including internal storage by mistake. As of now all I have is TWRP and SU access with the phone unlocked. I was wiping my phone so that I could use Cyanogenmod rather than Paranoid droid because my data kept dropping. When I wiped the Internal memory my CM.zip went with it. I have been trying to somehow install the zip file or restore any OS on my phone to no avail.
What ive done:
-I have attempted to flash over the stock rom via odin.
-I think this may not have worked because I wiped everything including the os and cannot turn on usb debugging
-I have attempted to push over a zip of CM via adb sideload.
- I made sure system and and sd were unchecked before pushing
- I have the latest files for adb 4.1.3, 4.1.2, 4.1.1
- I modified the google usb driver inf file so that I could use adb sideload
-shows device is attached
- I pushed the file receiving error message on twrp but 100% on command prompt
"assert failed: getprop("ro.bootloader") == "T999
getprop("ro.bootloader") == "T99UVDLJC"
getprop("ro.bootloader") == "T99UVDMD5"
getprop("ro.bootloader") == "T99VVLDLL1"
E: Error executing updater binary in zip ' /data/m '
-Reboot phone into TWRP
-If I ignore the previous error and attempt to flash the renamed sideload.zip I get the same error with a little extra
"assert failed: getprop("ro.bootloader") == "T999
getprop("ro.bootloader") == "T99UVDLJC"
getprop("ro.bootloader") == "T99UVDMD5"
getprop("ro.bootloader") == "T99VVLDLL1"
E: Error executing updater binary in zip ' /sdcard/sideload.zip'
Updating partition details...
Any help would be fantastic. Again Im using the galaxy S3 t999 with tmobile it was bought 5 days ago so it has LTE speeds.
If you can please do. I dont know what to do next.

Un zip the rom.
Delete signatures.
Open the updater-script and delete alk assert lines.
Rezip
Flash.
Or find another rom that doesnt do these checks.
Usb debugging has no affect on recovery or odin.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Un zip the rom.
Delete signatures.
Open the updater-script and delete alk assert lines.
Rezip
Flash.
Or find another rom that doesnt do these checks.
Usb debugging has no affect on recovery or odin.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thank you for the quick reply. How do I delete the signatures. And what do the alk assert lines look like? Any way you can show me a visual or describe it more?

davidmooch said:
Thank you for the quick reply. How do I delete the signatures. And what do the alk assert lines look like? Any way you can show me a visual or describe it more?
Click to expand...
Click to collapse
Ok so I don't have it using signatures and I deleted get prop from the updater script. Now it just says flash rom error with no details. Please help.

The signatures are the 3 files in the meta-inf folder. Also, inthe updater- script, delete the lines beginning with "assert". Should be at the top.
Make sure you have the latest recovery installed.
Sent from my SGH-T999 using xda premium

davidmooch said:
Ok so I don't have it using signatures and I deleted get prop from the updater script. Now it just says flash rom error with no details. Please help.
Click to expand...
Click to collapse
Probably borked the syntax. Let's see it.

Aerowinder said:
Probably borked the syntax. Let's see it.
Click to expand...
Click to collapse
Possibly, but at the beginning the error was in the updater-binary, leading me to think he may have an older recovery.
Agreed though, if you can post the script we can take a look at it for you. (You can post the whole thing as an attachment or just copy paste the top portion where you made the changes)
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Possibly, but at the beginning the error was in the updater-binary, leading me to think he may have an older recovery.
Agreed though, if you can post the script we can take a look at it for you. (You can post the whole thing as an attachment or just copy paste the top portion where you made the changes)
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
updater-script
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p14", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
package_extract_dir("system", "/system");
symlink("/system/xbin/su", "/system/bin/su");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");
symlink("Roboto-Regular.ttf", "/system/fonts/DroidSans.ttf");
symlink("busybox", "/system/xbin/[", "/system/xbin/[[",
"/system/xbin/adjtimex", "/system/xbin/arp", "/system/xbin/ash",
"/system/xbin/awk", "/system/xbin/base64", "/system/xbin/basename",
"/system/xbin/bbconfig", "/system/xbin/blkid", "/system/xbin/blockdev",
"/system/xbin/brctl", "/system/xbin/bunzip2", "/system/xbin/bzcat",
"/system/xbin/bzip2", "/system/xbin/cal", "/system/xbin/cat",
"/system/xbin/catv", "/system/xbin/chattr", "/system/xbin/chgrp",
"/system/xbin/chmod", "/system/xbin/chown", "/system/xbin/chroot",
"/system/xbin/clear", "/system/xbin/cmp", "/system/xbin/comm",
"/system/xbin/cp", "/system/xbin/cpio", "/system/xbin/crond",
"/system/xbin/crontab", "/system/xbin/cut", "/system/xbin/date",
"/system/xbin/dc", "/system/xbin/dd", "/system/xbin/depmod",
"/system/xbin/devmem", "/system/xbin/df", "/system/xbin/diff",
"/system/xbin/dirname", "/system/xbin/dmesg", "/system/xbin/dnsd",
"/system/xbin/dos2unix", "/system/xbin/du", "/system/xbin/echo",
"/system/xbin/ed", "/system/xbin/egrep", "/system/xbin/env",
"/system/xbin/expand", "/system/xbin/expr", "/system/xbin/false",
"/system/xbin/fbsplash", "/system/xbin/fdisk", "/system/xbin/fgrep",
"/system/xbin/find", "/system/xbin/flash_lock",
"/system/xbin/flash_unlock", "/system/xbin/flashcp",
"/system/xbin/flock", "/system/xbin/fold", "/system/xbin/free",
"/system/xbin/freeramdisk", "/system/xbin/fstrim", "/system/xbin/fsync",
"/system/xbin/ftpget", "/system/xbin/ftpput", "/system/xbin/fuser",
"/system/xbin/getopt", "/system/xbin/grep", "/system/xbin/groups",
"/system/xbin/gunzip", "/system/xbin/gzip", "/system/xbin/halt",
"/system/xbin/head", "/system/xbin/hexdump", "/system/xbin/id",
"/system/xbin/ifconfig", "/system/xbin/inetd", "/system/xbin/insmod",
"/system/xbin/install", "/system/xbin/ionice", "/system/xbin/iostat",
"/system/xbin/ip", "/system/xbin/kill", "/system/xbin/killall",
"/system/xbin/killall5", "/system/xbin/less", "/system/xbin/ln",
"/system/xbin/losetup", "/system/xbin/ls", "/system/xbin/lsattr",
"/system/xbin/lsmod", "/system/xbin/lsusb", "/system/xbin/lzcat",
"/system/xbin/lzma", "/system/xbin/lzop", "/system/xbin/lzopcat",
"/system/xbin/man", "/system/xbin/md5sum", "/system/xbin/mesg",
"/system/xbin/mkdir", "/system/xbin/mke2fs", "/system/xbin/mkfifo",
"/system/xbin/mkfs.ext2", "/system/xbin/mkfs.vfat",
"/system/xbin/mknod", "/system/xbin/mkswap", "/system/xbin/mktemp",
"/system/xbin/modinfo", "/system/xbin/modprobe", "/system/xbin/more",
"/system/xbin/mount", "/system/xbin/mountpoint", "/system/xbin/mpstat",
"/system/xbin/mv", "/system/xbin/nanddump", "/system/xbin/nandwrite",
"/system/xbin/nbd-client", "/system/xbin/netstat", "/system/xbin/nice",
"/system/xbin/nohup", "/system/xbin/nslookup", "/system/xbin/ntpd",
"/system/xbin/od", "/system/xbin/patch", "/system/xbin/pgrep",
"/system/xbin/pidof", "/system/xbin/ping", "/system/xbin/pipe_progress",
"/system/xbin/pkill", "/system/xbin/pmap", "/system/xbin/poweroff",
"/system/xbin/printenv", "/system/xbin/printf", "/system/xbin/ps",
"/system/xbin/pstree", "/system/xbin/pwd", "/system/xbin/pwdx",
"/system/xbin/rdev", "/system/xbin/readlink", "/system/xbin/realpath",
"/system/xbin/renice", "/system/xbin/reset", "/system/xbin/resize",
"/system/xbin/rev", "/system/xbin/rm", "/system/xbin/rmdir",
"/system/xbin/rmmod", "/system/xbin/route", "/system/xbin/run-parts",
"/system/xbin/rx", "/system/xbin/sed", "/system/xbin/seq",
"/system/xbin/setconsole", "/system/xbin/setserial",
"/system/xbin/setsid", "/system/xbin/sh", "/system/xbin/sha1sum",
"/system/xbin/sha256sum", "/system/xbin/sha3sum",
"/system/xbin/sha512sum", "/system/xbin/sleep", "/system/xbin/sort",
"/system/xbin/split", "/system/xbin/stat", "/system/xbin/strings",
"/system/xbin/stty", "/system/xbin/sum", "/system/xbin/swapoff",
"/system/xbin/swapon", "/system/xbin/sync", "/system/xbin/sysctl",
"/system/xbin/tac", "/system/xbin/tail", "/system/xbin/tar",
"/system/xbin/taskset", "/system/xbin/tee", "/system/xbin/telnet",
"/system/xbin/telnetd", "/system/xbin/test", "/system/xbin/tftp",
"/system/xbin/tftpd", "/system/xbin/time", "/system/xbin/timeout",
"/system/xbin/top", "/system/xbin/touch", "/system/xbin/tr",
"/system/xbin/traceroute", "/system/xbin/true", "/system/xbin/ttysize",
"/system/xbin/tune2fs", "/system/xbin/umount", "/system/xbin/uname",
"/system/xbin/uncompress", "/system/xbin/unexpand", "/system/xbin/uniq",
"/system/xbin/unix2dos", "/system/xbin/unlzma", "/system/xbin/unlzop",
"/system/xbin/unxz", "/system/xbin/unzip", "/system/xbin/uptime",
"/system/xbin/usleep", "/system/xbin/uudecode", "/system/xbin/uuencode",
"/system/xbin/vi", "/system/xbin/watch", "/system/xbin/wc",
"/system/xbin/wget", "/system/xbin/which", "/system/xbin/whoami",
"/system/xbin/xargs", "/system/xbin/xz", "/system/xbin/xzcat",
"/system/xbin/yes",
"/system/xbin/zcat");
symlink("mksh", "/system/bin/sh");
symlink("toolbox", "/system/bin/cat", "/system/bin/chmod",
"/system/bin/chown", "/system/bin/cmp", "/system/bin/cp",
"/system/bin/date", "/system/bin/dd", "/system/bin/df",
"/system/bin/dmesg", "/system/bin/du", "/system/bin/getevent",
"/system/bin/getprop", "/system/bin/grep", "/system/bin/hd",
"/system/bin/id", "/system/bin/ifconfig", "/system/bin/iftop",
"/system/bin/insmod", "/system/bin/ioctl", "/system/bin/ionice",
"/system/bin/kill", "/system/bin/ln", "/system/bin/log",
"/system/bin/ls", "/system/bin/lsmod", "/system/bin/lsof",
"/system/bin/md5", "/system/bin/mkdir", "/system/bin/mount",
"/system/bin/mv", "/system/bin/nandread", "/system/bin/netstat",
"/system/bin/newfs_msdos", "/system/bin/notify", "/system/bin/printenv",
"/system/bin/ps", "/system/bin/r", "/system/bin/reboot",
"/system/bin/renice", "/system/bin/restart", "/system/bin/rm",
"/system/bin/rmdir", "/system/bin/rmmod", "/system/bin/route",
"/system/bin/schedtop", "/system/bin/sendevent",
"/system/bin/setconsole", "/system/bin/setprop", "/system/bin/sleep",
"/system/bin/smd", "/system/bin/start", "/system/bin/stop",
"/system/bin/sync", "/system/bin/top", "/system/bin/touch",
"/system/bin/umount", "/system/bin/uptime", "/system/bin/vmstat",
"/system/bin/watchprops",
"/system/bin/wipe");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 0, 0755, 0755, "/system/addon.d");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm(0, 3003, 02750, "/system/bin/netcfg");
set_perm(0, 3004, 02755, "/system/bin/ping");
set_perm(0, 2000, 06750, "/system/bin/run-as");
set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");
set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");
set_perm_recursive(0, 2000, 0755, 0755, "/system/etc/init.d");
set_perm(0, 0, 0755, "/system/etc/init.d");
set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
set_perm(0, 0, 0644, "/system/vendor/etc/audio_effects.conf");
set_perm(0, 0, 0644, "/system/vendor/lib/libbt-vendor.so");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
set_perm(0, 0, 06755, "/system/xbin/librank");
set_perm(0, 0, 06755, "/system/xbin/procmem");
set_perm(0, 0, 06755, "/system/xbin/procrank");
set_perm(0, 0, 06755, "/system/xbin/su");
show_progress(0.200000, 0);
show_progress(0.200000, 10);
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "restore");
delete("/system/bin/backuptool.sh");
delete("/system/bin/backuptool.functions");
show_progress(0.200000, 10);
package_extract_file("boot.img", "/dev/block/mmcblk0p7");
show_progress(0.100000, 0);
unmount("/system");

Also the 3 files are still the the meta folder. Ill try deleting them and re zipping. Also my TWRP is the latest version.

If you had unzipped, removed the asserts and rezipped, it will fail if it is signed. Even if you just unzip/rezip and do nothing, itll fail. Remove those 3 files and you should be good to go.
Did you do anything other thsn removing the asserts?
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
If you had unzipped, removed the asserts and rezipped, it will fail if it is signed. Even if you just unzip/rezip and do nothing, itll fail. Remove those 3 files and you should be good to go.
Did you do anything other thsn removing the asserts?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
-No I did not remove anything other than the asserts and now the files in the Meta-data folder you said are used for verification.
-When using ADB Sideload to push zip to sd card
It says checking for md5 file... skipping MD5 check: no MD5 file found and at the top it says ADB sideload complete with FAILED under it
When I reboot the recovery I try to install getting an error
Updating partition details...
Installing ' /sdcard/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found:
Error flashing zip '/sdcard/sideload.zip'
Updating partition details...
under this it says "Failed"

davidmooch said:
-When using ADB Sideload to push zip to sd card
It says checking for md5 file... skipping MD5 check: no MD5 file found and at the top it says ADB sideload complete with FAILED under it
When I reboot the recovery I try to install getting an error
Updating partition details...
Installing ' /sdcard/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found:
Error flashing zip '/sdcard/sideload.zip'
Updating partition details...
under this it says "Failed"
Click to expand...
Click to collapse
Did you copy recovery.log to sd so you can see more detail?
Why are you trying to sideload? Have you tried to just flash a rom normally?
Did you delete the signatures?
Have you tried a different rom?
Your best option is to flash stock using odin. Factory reset and start over like it was new. All you said before was you tried it. It would help to know what happened. Use root66 firmware to retain root.
Sent from my SGH-T999 using XDA Premium 4 mobile app

With no OS I am using adb sideload because I cannot mount my sd card even with TWRP to transfer files. I havent copied any recovery log over to my sd card or internal memory. My TWRP is on internal memory because its a S3 and didnt come with an sd card will this affect anything? Also I have already tried to flash stock using odin and root66 and all Odin said was failed.

davidmooch said:
With no OS I am using adb sideload because I cannot mount my sd card even with TWRP to transfer files. I havent copied any recovery log over to my sd card or internal memory. My TWRP is on internal memory because its a S3 and didnt come with an sd card will this affect anything? Also I have already tried to flash stock using odin and root66 and all Odin said was failed.
Click to expand...
Click to collapse
Oh, so you dont have an external sd card at all then? Thatll make this more difficult.
When you use Odin it gives a readout of what its doing in the lower left frame. Does it fail immediately after you start? Does it pass the md5sim check? Does it successfully get pit for mapping? Where does it fail exactly? Does it flash through several partitions and fail on the same one every time? Does it seem to flash everything and then fail at the very end?
When you boot into download mode and then plug it in, does Odin show Com## in the top left?
Easiest thing woukd be to redownload root66 firmware and try again. If it fails, copy/paste the output from odin into a post here so we can see it.
Without a physical sdcard, Odin is probably your best chance of getting it working again.
Sent from my SGH-T999 using XDA Premium 4 mobile app

DocHoliday77 said:
Oh, so you dont have an external sd card at all then? Thatll make this more difficult.
When you use Odin it gives a readout of what its doing in the lower left frame. Does it fail immediately after you start? Does it pass the md5sim check? Does it successfully get pit for mapping? Where does it fail exactly? Does it flash through several partitions and fail on the same one every time? Does it seem to flash everything and then fail at the very end?
When you boot into download mode and then plug it in, does Odin show Com## in the top left?
Easiest thing woukd be to redownload root66 firmware and try again. If it fails, copy/paste the output from odin into a post here so we can see it.
Without a physical sdcard, Odin is probably your best chance of getting it working again.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
*Note in download when using odin it says qualcom secure boot enabled
K so when im in download mode it says I have 2 counts of custom binary downloaded... Idk how but is that a problem? Then it says binary and system is custom. I go into Odin and it shows Com#. Passes Md5 check then fails.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDMD5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

So I used a different version of Odin and tried flashing the pit file with it and got this
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDMD5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!

Wow so I got it to flash both the pit file and the root66 rom successfully. However when I boot up the phone it still shows the the paranoiddroid guy under galaxy s3 when booting up, then after the screen goes black and no OS loads.... I am so lost on whats going on here

davidmooch said:
Wow so I got it to flash both the pit file and the root66 rom successfully. However when I boot up the phone it still shows the the paranoiddroid guy under galaxy s3 when booting up, then after the screen goes black and no OS loads.... I am so lost on whats going on here
Click to expand...
Click to collapse
How, exactly, did you flash? What options were checked? Which fields did you use for flashing? (Pda, phone, pit, etc)
I could very easily be wrong, but I was under the impression you may have to select nand erase with a pit flash. (Do not do this! I'm really not sure if it!)
I kinda doubt it wouldve been a partition issue...
Sent from my SGH-T999L using XDA Premium 4 mobile app

AT&T I747 UCUEMJB 4.3 Stock Restore

AT&T I747 UCUEMJB Stock Restore
This is Abandoned. I recommend you do not use this to restore you phone as to a fear of bricking your device.
This is a last ditch effort for restoring the AT&T I747 to factory stock. This zip will wipe all data, clear the binary flash count, restore the system, flash the latest KNOX firmware and stock recovery. There is absolutely no possible way to clear the warranty bit back to 0 IT IS IMPOSSIBLE TO REVERT ONCE TRIPED!! Not even Samsung can undo this.! Its the price we pay for rooting our phones. Also once tripped KNOX is rendered useless and will no longer be available as an app in your drawer.
This is meant for restoring your phone to as near stock as possible in hopes to capture any future OTA updates. Can't guarantee that will work either...
As always I don't take any responsibility for what you do with your phone. Please do not flash this if you don't understand the consequences. This thread will have limited support. Use with caution!
Directions are really simple.
Downloads:
TWRP and CWM 6.0.4.5 http://www.mediafire.com/download/30idxwhg2hidxx2/ATT_I747_UCUEMJB_StockRestore_2282014.zip
MD5: 739f9cf2d0eb570ec7d18146d5e4a45f
CWM 6.0.4.7: http://www.mediafire.com/download/h7mw94pfj5qssty/ATT_I747_UCUEMJB_StockRestore_CWM_2282014.zip
MD5: 487b55449ecf7b0c273d5df86f51c170
Odin: http://forum.xda-developers.com/showpost.php?p=52341560&postcount=227
Verify the MD5
Flash via custom recovery (CWM or TWRP).
When flash is done
Allow phone to fully boot up.
Boot into download mode and verify the count has been reset. (Hold Volume Down, Home and Power till you see D/L mode appear. Quickly release button combo, then Volume Up to continue)
Boot into recovery and verify that it is now stock. (Hold Volume Up, Home and Power till you see "Recovery Booting..." in the upper left hand corner then immediately release button combo)
If your selling your phone or returning for warranty now would be a good time to give one last factory data reset before boxing.
XDA:DevDB Information
MJB Stock Restore, ROM for the AT&T Samsung Galaxy S III
Contributors
enewman17
ROM OS Version: 4.3.x Jellybean
Version Information
Status: Beta
Created 2014-02-23
Last Updated 2014-05-26

First!!! Thank you. Takes out a worry (no warranty but resale potential is nice). Does this work with Knox and efuse?
Sent from my awesome phone.

Second. Will keep this is my arsenal.

Great job on this. Hoping I won't ever need this but it sure is a relief to know someone put hard work into making this for those of us that have no choice

I love you! Thank you so much for this!
Quick noob question... Is it possible to Flash this via Odin?

imcol said:
I love you! Thank you so much for this!
Quick noob question... Is it possible to Flash this via Odin?
Click to expand...
Click to collapse
Custom recovery as mentioned in instructions.
Sent from my awesome phone.

aybarrap1 said:
First!!! Thank you. Takes out a worry (no warranty but resale potential is nice). Does this work with Knox and efuse?
Sent from my awesome phone.
Click to expand...
Click to collapse
Not sure what you mean. Yes this is completely stock so it has knox.
The qfuse or efuse.... are one-time-programmable (OTP) elements that are used to enable and disable security and debug features of the MSM7xxx device. The Qfuses are implemented as an array of one-bit fuse blocks. The Qfuse banks are used for two purposes — providing non-volatile, immutable storage of data, and configuration of hardware features. For immutable data storage, the Qfuses are read via a shadow register which contains the actual value stored and includes error correction. For configuration, each Qfuse is associated with a one-time write register. The value of each Qfuse is sensed at power up and stored in a register. Blowing Qfuses is done by placing a value to a register and applying current to the fuse. The fuse registers are accessible through JTAG and software readable address locations.
So long as your not trying to downgrade there is no fear of erasing this register. Previous versions did not use this feature to secure the bootloader. So in download mode you will see "Warranty Bit 1" if we get an update and they update the firmware it will jump to 2. Does this help? :good:

Sorry about that but thank you. I had a dumb moment. Knew what it was but didn't think first before posting the question
Sent from my awesome phone.

Awesome...Thanks so so much :highfive:

If I flash this can I still root my S3 again after?

Thanks enewman17!
This lil' bugger is hard to get and hard to find. Plus, Samsung and AT&T only made 4.3 OTA only, therefore wasn't released as a ROM. <grrrrr>
No worries though, thanks to you for digging this up. I'm keeping this, in case my phone starts acting crazy or wanted the "stock feel" back.
Big ups, enewman17!
enewman17 said:
AT&T I747 UCUEMJB Stock Restore
Here is what we got. This zip will wipe all data, clear the flash count, restore the system, flash MJB firmware and stock recovery.
I've flashed this many many times and seems to be working just fine. I can not guarantee this will work for any future OTA's (as there is no way to verify)
but should work just fine for any service or warranty work. As always I don't take any responsibility for what you do with your phone.
Directions are really simple.
Download http://www.mediafire.com/download/2j5pf893spm3zpy/ATT_I747_UCUEMJB_StockRestore.zip
Verify the MD5: bb4a69d922030327c97c3a8775476fce
Flash via custom recovery (CWM or TWRP).
When flash is done
Allow phone to fully boot up.
Boot into download mode and verify the count has been reset. (Hold Volume Down, Home and Power till you see D/L mode appear. Quickly release button combo, then Volume Up to continue)
Boot into recovery and verify that it is now stock. (Hold Volume Up, Home and Power till you see "Recovery Booting..." in the upper left hand corner then immediately release button combo)
If your selling your phone or returning for warranty now would be a good time to give one last factory data reset before boxing.
XDA:DevDB Information
MJB Stock Restore, a ROM for the AT&T Samsung Galaxy S III
Contributors
enewman17
ROM OS Version: 4.3.x Jellybean
Version Information
Status: Testing
Created 2014-02-23
Last Updated 2014-02-22
Click to expand...
Click to collapse

TheStart said:
If I flash this can I still root my S3 again after?
Click to expand...
Click to collapse
Absolutely, there are a couple of ways. First you can flash cf auto root via odin or flash cwm or twrp with one of there Odin flashable.tars then flash the latest recovery flashable super user
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Downloaded and saved for later use. Thanks for your hard work and for your unrelentless giving to the community. I hope to one day learn half of what you know about building stuff for phones so I too can give to the community. Thanks again.
Sent from my SAMSUNG-SGH-I747 running S3Rx MJ2 bootloader MJB modem and it is smooth

This was needed badly around here. You're a genius.
However, we still need more to testers to verify this around here as with anything new. I cannot use this yet because I'm still on 4.1.2.

Thanks for this update..
Sent from my SGH-I747 using Tapatalk

I keep getting the "Status 7 Installation Aborted" error. And it says "format () expects 5 args, got 3
I checked the MD5 Checksum and was flashing it through CWM 6.** (currently on 4.3.1 / CM 10.2.1 -d2att)

This is only for AT&T versions correct?
Sent from my SGH-I747 using Tapatalk

ParryB said:
I keep getting the "Status 7 Installation Aborted" error. And it says "format () expects 5 args, got 3
I checked the MD5 Checksum and was flashing it through CWM 6.** (currently on 4.3.1 / CM 10.2.1 -d2att)
Click to expand...
Click to collapse
I'm getting the same error

pwned101 said:
I'm getting the same error
Click to expand...
Click to collapse
ParryB said:
I keep getting the "Status 7 Installation Aborted" error. And it says "format () expects 5 args, got 3
I checked the MD5 Checksum and was flashing it through CWM 6.** (currently on 4.3.1 / CM 10.2.1 -d2att)
Click to expand...
Click to collapse
Alright here is my install script. I only tested on the latest twrp and with the binary I'm using it only wanted 3 arguments.
assert(getprop("ro.bootloader") == "I747UCALEM" || getprop("ro.bootloader") == "I747UCALG1" || getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == "I747UCDMG2" || getprop("ro.bootloader") == "I747UCUEMJ2" || getprop("ro.bootloader") == "I747UCUEMJB");
ui_print("*********************************");
ui_print("* TouchWiz 4.3 I747UCUEMJB *");
ui_print("* Stock Restore *");
ui_print("*********************************");
ui_print("");
run_program("/sbin/busybox", "mkdir", "/tmp");
ui_print("[*] Resetting flash counter");
package_extract_dir("tools", "/tmp");
set_perm(0, 0, 0777, "/tmp/clearcount.sh");
set_perm(0, 0, 0777, "/tmp/bl");
run_program("/tmp/clearcount.sh");
delete("/tmp/clearcount.sh", "/tmp/bl");
unmount("/cache");
unmount("/system");
unmount("/data");
ui_print("[*] Formatting cache");
format("ext4", "EMMC", "/dev/block/mmcblk0p17");
ui_print("[*] Formatting system");
format("ext4", "EMMC", "/dev/block/mmcblk0p14");
mount("ext4", "EMMC", "/dev/block/mmcblk0p17", "/cache");
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p15", "/data");
ui_print("[*] Formatting dalvik");
delete_recursive("/data/dalvik-cache");
delete_recursive("/data/local");
ui_print("[*] Formatting data");
run_program("/sbin/sh", "-c", "find /data/* -maxdepth 0 -type d ! -name 'media' -exec rm -rf {} +");
ui_print("[*] Restoring system");
package_extract_dir("system", "/system");
ui_print("[*] Symlinking");
symlink("dumpstate", "/system/bin/dumpcrash");
symlink("toolbox", "/system/bin/cat");
symlink("toolbox", "/system/bin/chmod");
symlink("toolbox", "/system/bin/chown");
symlink("toolbox", "/system/bin/cmp");
symlink("debuggerd", "/system/bin/csview");
symlink("toolbox", "/system/bin/date");
symlink("toolbox", "/system/bin/dd");
symlink("toolbox", "/system/bin/df");
symlink("toolbox", "/system/bin/dmesg");
symlink("toolbox", "/system/bin/getevent");
symlink("toolbox", "/system/bin/getprop");
symlink("toolbox", "/system/bin/hd");
symlink("toolbox", "/system/bin/id");
symlink("toolbox", "/system/bin/ifconfig");
symlink("toolbox", "/system/bin/iftop");
symlink("toolbox", "/system/bin/insmod");
symlink("toolbox", "/system/bin/ioctl");
symlink("toolbox", "/system/bin/ionice");
symlink("toolbox", "/system/bin/kill");
symlink("toolbox", "/system/bin/ln");
symlink("toolbox", "/system/bin/log");
symlink("toolbox", "/system/bin/ls");
symlink("toolbox", "/system/bin/lsmod");
symlink("toolbox", "/system/bin/lsof");
symlink("toolbox", "/system/bin/mkdir");
symlink("toolbox", "/system/bin/mount");
symlink("toolbox", "/system/bin/mv");
symlink("toolbox", "/system/bin/nandread");
symlink("toolbox", "/system/bin/netstat");
symlink("toolbox", "/system/bin/newfs_msdos");
symlink("toolbox", "/system/bin/notify");
symlink("toolbox", "/system/bin/printenv");
symlink("toolbox", "/system/bin/ps");
symlink("toolbox", "/system/bin/reboot");
symlink("toolbox", "/system/bin/renice");
symlink("toolbox", "/system/bin/rm");
symlink("toolbox", "/system/bin/rmdir");
symlink("toolbox", "/system/bin/rmmod");
symlink("toolbox", "/system/bin/route");
symlink("toolbox", "/system/bin/schedtop");
symlink("toolbox", "/system/bin/sendevent");
symlink("toolbox", "/system/bin/setconsole");
symlink("toolbox", "/system/bin/setprop");
symlink("mksh", "/system/bin/sh");
symlink("toolbox", "/system/bin/sleep");
symlink("toolbox", "/system/bin/smd");
symlink("toolbox", "/system/bin/start");
symlink("toolbox", "/system/bin/stop");
symlink("toolbox", "/system/bin/sync");
symlink("toolbox", "/system/bin/top");
symlink("toolbox", "/system/bin/touch");
symlink("toolbox", "/system/bin/umount");
symlink("toolbox", "/system/bin/uptime");
symlink("toolbox", "/system/bin/vmstat");
symlink("toolbox", "/system/bin/watchprops");
symlink("toolbox", "/system/bin/wipe");
symlink("toolbox", "/system/bin/chcon");
symlink("toolbox", "/system/bin/setenforce");
symlink("toolbox", "/system/bin/grep");
symlink("toolbox", "/system/bin/runcon");
symlink("toolbox", "/system/bin/touchinput");
symlink("toolbox", "/system/bin/md5");
symlink("toolbox", "/system/bin/getsebool");
symlink("toolbox", "/system/bin/setsebool");
symlink("toolbox", "/system/bin/restorecon");
symlink("toolbox", "/system/bin/getenforce");
symlink("toolbox", "/system/bin/load_policy");
symlink("toolbox", "/system/bin/cp");
symlink("toolbox", "/system/bin/playback");
symlink("toolbox", "/system/bin/du");
symlink("wiperiface_v02", "/system/bin/wiperiface");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 0, 0777, 0777, "/system/etc/init.d");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm(0, 3003, 06755, "/system/bin/ip");
set_perm(0, 3003, 02750, "/system/bin/netcfg");
set_perm(0, 3004, 02755, "/system/bin/ping");
set_perm(0, 2000, 06750, "/system/bin/run-as");
set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluetooth");
set_perm(0, 0, 0755, "/system/etc/bluetooth");
set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pairing.conf");
set_perm(3002, 3002, 0444, "/system/etc/bluetooth/blacklist.conf");
set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pair_devlist.conf");
set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");
set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");
set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
set_perm_recursive(0, 0, 0755, 0644, "/system/vendor/firmware");
set_perm(0, 2000, 0755, "/system/vendor/firmware");
set_perm(0, 2000, 0755, "/system/vendor/lib");
set_perm(0, 2000, 0755, "/system/vendor/lib/hw");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
ui_print("[*] Extracting Kernel");
package_extract_file("boot.img", "/dev/block/mmcblk0p7");
ui_print("[*] Restoring stock firmware");
package_extract_dir("firmware", "/tmp");
set_perm(0, 0, 0777, "/tmp/dd");
run_program("/tmp/dd", "if=/tmp/NON-HLOS.bin", "of=/dev/block/mmcblk0p1");
run_program("/tmp/dd", "if=/tmp/sbl1.mbn", "of=/dev/block/mmcblk0p2");
run_program("/tmp/dd", "if=/tmp/sbl2.mbn", "of=/dev/block/mmcblk0p3");
run_program("/tmp/dd", "if=/tmp/sbl3.mbn", "of=/dev/block/mmcblk0p4");
run_program("/tmp/dd", "if=/tmp/aboot.mbn", "of=/dev/block/mmcblk0p5");
run_program("/tmp/dd", "if=/tmp/rpm.mbn", "of=/dev/block/mmcblk0p6");
run_program("/tmp/dd", "if=/tmp/tz.mbn", "of=/dev/block/mmcblk0p8");
run_program("/tmp/dd", "if=/tmp/recovery.img", "of=/dev/block/mmcblk0p18");
delete_recursive("/tmp");
unmount("/system");
This is what I have: format with 3 argument
ui_print("[*] Formatting cache");
format("ext4", "EMMC", "/dev/block/mmcblk0p17");
ui_print("[*] Formatting system");
format("ext4", "EMMC", "/dev/block/mmcblk0p14");
This is what CWM wants: format with 5 argument.
ui_print("[*] Formatting cache");
format("ext4", "EMMC", "/dev/block/mmcblk0p17", "0", "/cache");
ui_print("[*] Formatting system");
format("ext4", "EMMC", "/dev/block/mmcblk0p14", "0", /system");
It's an easy fix, just open the zip archive pull updater-script form the meta-inf/com/google/android folder. Make the changes then just drag the updater-script back into the zip. I'll upload another one with the changes though.

shiniyoyo said:
This is only for AT&T versions correct?
Sent from my SGH-I747 using Tapatalk
Click to expand...
Click to collapse
That is correct

error 6 while trying to use set_perm in updater-script

Heloo, i have hard times finding a solution to my problem, here my script :
Code:
ui_print("Starting...");
mount("ext4", "EMMC", "/dev/block/mmcblk0p41", "/system");
ui_print("...system mounted");
package_extract_dir("modifiedframework", "/system/framework");
ui_print("...framework-res.apk transfered");
set_perm(0, 0, 0644, "/system/framework/framework-res.apk");
ui_print("...permissions set");
unmount("/system");
ui_print("...system unmounted");
it return : Updater process ended with ERROR: 6
and the script is working fine if i remove the line
Code:
set_perm(0, 0, 0644, "/system/framework/framework-res.apk");
any help is welcome, thanks you

thanks for help... i have found the solution, https://github.com/mission-impossible-android/mission-impossible-android/issues/50. i'm using this update-binary and now it is working.

@linpinpin
I'm facing exactly the same issue with TWRP on Xiaomi. set_perm(...); causing error: 6 regardless it's syntactically fine.
Which updater binary can I use for my device?

i use this one https://github.com/mikeperry-tor/mi...ult/META-INF/com/google/android/update-binary click on download
i'm using a xiaomi also

Develop Bugs

welcome