yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] open1your1eyes0:
I think I'm definitely doing this wrong. I was able to get up to the step to create the newsys.img and mount it to temp but after that I am just lost. mkuserimg.sh does not want to work properly no matter what I do. Would you like me to upload newsys.img for you somewhere and maybe you can continue from where I left off?
[Verizon Samsung Galaxy S III] eckzow:
I followed the instructions and repacked without hitting any obvious errors in the process. Flashing got me

<ID:0/005> system.img.ext4

<ID:0/005> FAIL! (Ext4)

<OSM> All threads completed. (succeed 0 / failed 1)

Going to go back and see what step I missed...
[Verizon Samsung Galaxy S III] open1your1eyes0:
How were you doing it? Real linux environment or from Android terminal/ADB? Did you get mkuserimg.sh to work?
[Verizon Samsung Galaxy S III] BungeBash:
I think I'm at the same point you are open. I'm trying to crete a new ext4 image from my temp folder

---------- Post added at 05:06 AM ---------- Previous post was at 04:56 AM ----------

I keep getting

$ ./mkuserimg.sh -s rooting system.img ext4 tempdir 1536M

in mkuserimg.sh PATH=/usr/local/bin:/usr/bin:/cygdri ve/c/Python26/Lib/site-packages/PyQt4/bin:/cygdrive/ c/Program Files/Common Files/Microsoft Shared/Window s Live:/cygdrive/c/windows/system32:/cygdrive/c/wind ows:/cygdrive/c/windows/System32/Wbem:/cygdrive/c/wi ndows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Pr ogram Files/Common Files/DivX Shared:/cygdrive/c/Pro gram Files/Common Files/Teleca Shared:/cygdrive/c/Pr ogram Files/Windows Live/Shared:/cygdrive/c/PROGRA~1 /TIEDUC~1/TI-83P~1/UTILS

./make_ext4fs -s -l 1536M -a tempdir system.img root ing

./mkuserimg.sh: line 52: .
[Verizon Samsung Galaxy S III] Tbenson:
Following the instructions I made it to the point of creating the new tar

tar cvf rooted.tar cache.img hidden.img modem.bin recovery.img system.img

However for some reason when I extracted out the stock md5 provided in the OP it did not have hidden.img and modem.bin that is listed here in this thread http://xdaforums.com/showpost.php?p=27801304&postcount=1 . So the tar command worked just complained about those files missing.

I will have to copy this tar to a windows box and flash from Odin as I still don't know if heimdall is compatible.

All of the above was done within a linux environment btw.
[Verizon Samsung Galaxy S III] open1your1eyes0:
That's correct. I think that guide was very awkwardly taken from another guide that was used on a Galaxy SII which had slightly different firmware. Idea is the same but was not formatted properly for the Galaxy S III. Please let us know your outcome.
[Verizon Samsung Galaxy S III] Tbenson:
BungeBash,

The command needs to have the mounted directory and actual temp directory such as temp.

./mkuserimg.sh -s [path to mounted temp dir] system.img ext4 [temp dir such as /temp ] 1536M

Hope this helps!
[Verizon Samsung Galaxy S III] open1your1eyes0:
I was doing this exact command on my Xoom. I mounted newsys.img to /data/GS3/temp and was in the /data/GS3 directory when running it (it had all the ex4 tools) but I kept getting the "file or directory not found" error when running it. And I confirmed the newsys.img was indeed mounted as I saw all the folders in temp.
[Verizon Samsung Galaxy S III] eckzow:
I've got a legit linux install.

So far I get this:

root@failbox:/media/sf_STORAGE/rooty_tools/take2# tar xvf ../HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5
boot.img
recovery.img
system.img.ext4
NON-HLOS.bin
cache.img.ext4
root@failbox:/media/sf_STORAGE/rooty_tools/take2# ./simg2img system.img.ext4 newsys.img
computed crc32 of 0x67bae0a7, expected 0x00000000
root@failbox:/media/sf_STORAGE/rooty_tools/take2# mkdir temp
root@failbox:/media/sf_STORAGE/rooty_tools/take2# mount -t ext4 -o loop newsys.img temp
root@failbox:/media/sf_STORAGE/rooty_tools/take2# cd temp/
root@failbox:/media/sf_STORAGE/rooty_tools/take2/temp# ls
app bin build.prop cameradata etc fonts framework hdic lib media preloaddata tts usr vendor voicebargeindata vsc wakeupdata xbin
root@failbox:/media/sf_STORAGE/rooty_tools/take2/temp# cd xbin/
root@failbox:/media/sf_STORAGE/rooty_tools/take2/temp/xbin# pushd ../../..
/media/sf_STORAGE/rooty_tools /media/sf_STORAGE/rooty_tools/take2/temp/xbin
root@failbox:/media/sf_STORAGE/rooty_tools# tar xvf RootFiles.tar
Superuser.apk
su
root@failbox:/media/sf_STORAGE/rooty_tools# popd
/media/sf_STORAGE/rooty_tools/take2/temp/xbin
root@failbox:/media/sf_STORAGE/rooty_tools/take2/temp/xbin# mv ../../../su .
root@failbox:/media/sf_STORAGE/rooty_tools/take2/temp/xbin# chmod 06755 su
root@failbox:/media/sf_STORAGE/rooty_tools/take2/temp/xbin# cd ../app/
root@failbox:/media/sf_STORAGE/rooty_tools/take2/temp/app# mv ../../../Superuser.apk .
root@failbox:/media/sf_STORAGE/rooty_tools/take2/temp/app# chmod 06755 Superuser.apk
root@failbox:/media/sf_STORAGE/rooty_tools/take2/temp/app# cd ../..
root@failbox:/media/sf_STORAGE/rooty_tools/take2# rm system.img.ext4
root@failbox:/media/sf_STORAGE/rooty_tools/take2# ./mkuserimg.sh -s temp system.img.ext4 ext4 system 1536M
in mkuserimg.sh PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/failuser/bin
./make_ext4fs -s -l 1536M -a system system.img.ext4 temp
Creating filesystem with parameters:
Size: 1610612736
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 6144
Label:
Blocks: 393216
Block groups: 12
Reserved block group size: 95
Created filesystem with 2129/98304 inodes and 285929/393216 blocks
root@failbox:/media/sf_STORAGE/rooty_tools/take2# mkdir junk
root@failbox:/media/sf_STORAGE/rooty_tools/take2# umount temp/
root@failbox:/media/sf_STORAGE/rooty_tools/take2# mv make_ext4fs junk/
root@failbox:/media/sf_STORAGE/rooty_tools/take2# mv mkuserimg.sh junk/
root@failbox:/media/sf_STORAGE/rooty_tools/take2# mv newsys.img junk/
root@failbox:/media/sf_STORAGE/rooty_tools/take2# mv simg2img junk/
root@failbox:/media/sf_STORAGE/rooty_tools/take2# rmdir temp
root@failbox:/media/sf_STORAGE/rooty_tools/take2# ls
boot.img cache.img.ext4 junk NON-HLOS.bin recovery.img system.img.ext4
root@failbox:/media/sf_STORAGE/rooty_tools/take2# tar cvf rooted.take2.tar boot.img recovery.img system.img.ext4 NON-HLOS.bin cache.img.ext4
boot.img
recovery.img
system.img.ext4
NON-HLOS.bin
cache.img.ext4

Upon flashing ODIN fails and the device screen says "ODIN : Invalid ext4 image"
[Verizon Samsung Galaxy S III] BungeBash:
I have my directory named rooting rather than temp. I have my line written as:

./mkuserimg.sh -s rooting system.img ext4 rootingdir 1536M

but it returns the same error:

./mkuserimg.sh: line 52: ./make_ext4fs: No such file or directo ry

When I look at line 52 it states:

MAKE_EXT4FS_CMD="./make_ext4fs $ENABLE_SPARSE_IMAGE -l $SIZE -a $MOUNT_POINT $OUTPUT_FILE $SRC_DIR"

echo $MAKE_EXT4FS_CMD

$MAKE_EXT4FS_CMD

if [ $? -ne 0 ]; then

exit 4

fi

I do have a file from the utils make_ext4fs but seems to not be found when i run my script

---------- Post added at 05:27 AM ---------- Previous post was at 05:25 AM ----------

Did you then turn that ext4 into a tar file?
[Verizon Samsung Galaxy S III] open1your1eyes0:
Hmm I think I'm getting the same thing. I think someone needs to contact OP of that guide for some help. Perhaps we should work together with him to create this.
[Verizon Samsung Galaxy S III] Tbenson:
Same error here.

Using ubuntu 12.04 to perform all the actions listed in the guide to roll your own.

Also this error

./mkuserimg.sh: line 52: ./make_ext4fs: No such file or directo ry

looks like a PATH error.

Are you executing ./mkuserimg.sh from where you built the tools or did you add it to your PATH?
[Verizon Samsung Galaxy S III] BungeBash:
has anyone on linux been able to successfully dissect the current rooted file to determine what is different from that aspect? I get a header error when trying to extract the ext4 file
[Verizon Samsung Galaxy S III] open1your1eyes0:
Here's a theory guys, try to skip the command "./mkuserimg.sh -s temp system.img ext4 tempdir 1536M". I think it's changing it from ext4 to another format but ODIN actually wants ext4. Do the same guide without that command and only create the tar for newsys.img.
[Verizon Samsung Galaxy S III] eckzow:
I came to (mostly) the same conclusion as the rest of you guys :)

Looking at the 'working' version, it's just a straight up ext4 image. Loopback-mountable straight out of the box (after untaring, of course).

So, I dropped the -s off of the mkuserimage.sh command. Seems to be flashing now.

EDIT:

Ok--yes, it flashed. However, now it hangs at the Galaxy SIII logo.

Getting late here; I'm going back to stock for now and I'll check in tomorrow.
[Verizon Samsung Galaxy S III] mb27:
It said it was optional if you weren't having any problems, and I had zero problems so no I didn't do a factory reset.

I flashed that bug fix and fully charged my phone up. I'll see what happens by the end of the day. If it's still a problem I'll do a factory reset. I was hoping there might be a solution not involving a factory reset :-\
[Verizon Samsung Galaxy S III] Elite49:
Yea I think that step might be needed since it seems some others who didn't reset are having issues. I usually charge to 100% and then some before I flash roms and I'll be doing that when I get the phone. Then calibrate battery as well. Though I think thats not needed since its not really a rom but if someone else does let me know.
[Verizon Samsung Galaxy S III] vudugan:
After getting set back up, I found that. Folders in internal sd were still there. I actually copied a few to ext-sd beforehand thinking all on internal would get wiped. I chose settings/backup and reset/factory data reset. So... Should I had wiped through CWM maybe? I know it re-flashed due to different messaging settings.
[Verizon Samsung Galaxy S III] mb27:
Looks like I'm doing a factory reset tonight.

It's been 2 hours since I unplugged after fully charging and I'm at 80%. At this rate I'll be at 60% after 4 hours (assuming linear drain).

Screen is top user at 66%, but it's only been on for 5 minutes. Device idle 18%, cell standby 16%, bluetooth 2%.

I had fantastic battery life before rooting so something went wrong.. could it be an app I froze?

EDIT: Oh man, it's really bad. 3 hours 35 mins and down to 60%. Screen time on is 18 min 51 seconds and 83%. Device idle 9%, cell standby 8%.
[Verizon Samsung Galaxy S III] breaker911:
Does anyone know if this root method will work for this phone?:confused: I know it's a droid razr forum, but it does say for all ics 4.0.4 builds.

http://www.droidrzr.com/index.php/topic/2651-root-any-404-ics-build/
[Verizon Samsung Galaxy S III] pkd600:
Yeah, something definitely seems wrong. A factory reset should fix that right up though.

For what its worth, I did not do a factory reset before I flashed and I haven't any battery problems. I am at 88% right now with 3 hours and 45 minutes, screen is the biggest user with 39% and 25 minutes on.

---------- Post added at 03:01 PM ---------- Previous post was at 02:59 PM ----------

No, that's a root method for a different phone. When they say all ics 4.0.4 builds, they mean all ics 4.0.4 builds for that phone.
[Verizon Samsung Galaxy S III] mb27:
Do I need to flash the stock ROM first? Or can I just do a factory reset and then flash the root66 ROM again?

My phone is also getting extremely hot! Battery temps are just over 100 degrees. They usually peak in the 90s when I play a game..
[Verizon Samsung Galaxy S III] aigochamaloh:
Something is definitely not right. I'm at 6 hours and 88%. I don't have the cell idle fix, so it's taking ~52% though.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Excellent battery life on mine (same build, tons of apps added too):
[Verizon Samsung Galaxy S III] Hypnosis4U2NV:
I flashed the ROM in this thread, did a factory reset anyway, and restored with TiBu.. Any apps that didn't work after restore, I uninstalled and reinstalled manually.. No issues during 2 weeks of use.. Also got TWRP recovery installed but would love to see an 4EXT recovery for this phone, now that's a bad ass recovery..

On another note, add me to the list of folks who would like to see THIS ROM deodexed and zipaligned also..

Sent from my Commodore 64..

READY.

load"*", 8,1
[Verizon Samsung Galaxy S III] vudugan:
Alright, i'm getting really frustrated over this and i'm hoping this will be my last "help me" comment.

I rooted with the original "Sprint" image, started seeing comments and new threads bout the new correct VZW root66, downloaded files and followed directions in the top of this thread. (Factory data reset, installed root66). Found out that in my sdcard (phone) all folders/ files were still there from other apps like Liteflow, pictures and all custom ringtones, alarms and notifications.

Wifi has been connecting all day as it should and staying connected, so there is some change. Phone took a hard hit today at work with taking pics, emails loaded with pics, texting and back and forth on Tap a talk, not to mention setting up TB and letting it do its thing (rooted this morning before work). Got 8.5hrs of battery leaving me now with 16%, I'm guessing thats fair.

What bugs me is why didnt the phone sd wipe totally clean after factory reset?

As far as the Sprint image to this image goes...

If i have the Sprint image and want this image, What about flashing from Sprint to Original Stock(released by Sammy) then root66?

I have flashed alot of ROMS on other phones so lets just say I follow directions pretty good. Some of us will always be noobs or/and very cautious.

Anyone care to shed some light?
[Verizon Samsung Galaxy S III] Hypnosis4U2NV:
Why would factory reset wipe your internal memory? I would think that's what you would want NOT to happen if you didn't have an external card attached..

As far as flashing back to stock and then the root66 ROM, it can't hurt and it might be a better way to get rid of everything "Sprint" from your previous flash..

Sent from my Commodore 64..

READY.

load"*", 8,1
[Verizon Samsung Galaxy S III] fbm111:
Samsung newb.... Can you use mobile Odin to flash this?

My serial number is gone will this fix it?

Thanks!
[Verizon Samsung Galaxy S III] mb27:
Alright I think everything is working properly now.

I restored factory defaults. Flashed stock rom. Wiped data from recovery. Flashed rooted rom.

Been unplugged for 40 minutes and still at 100%. Before I would be down nearly 10%.

Battery is also staying nice and cool at 84 degrees instead of 100+ (at idle!).

I think it was a CPU bug. Something was hogging it. My widgetsoid has a cpu % widget and I don't think I saw it under 50% earlier today. Now when I'm not doing anything it hovers around 10-20%.

Hopefully everything stays running smoothly. I don't want to post another reply saying it's draining fast again :eek:
[Verizon Samsung Galaxy S III] gordo80:
any if you guys missing music effects under setting>sound>music effect with this build?
[Verizon Samsung Galaxy S III] XooLoo:
Didn't know such thing should be there... mine doesn't have a music effects option. Now I want to see how I can get it added. :eek:
[Verizon Samsung Galaxy S III] Elite49:
Sorry for newb question but what stock rom did you flash. I thought you'd just have to factory reset, flash rooted and wipe.
[Verizon Samsung Galaxy S III] mb27:
I used the one from this thread.

It may not have been needed, but I thought it might be worth the extra step.
[Verizon Samsung Galaxy S III] Elite49:
Better safe then sorry. Let us know how the battery is after a couple charges again.
[Verizon Samsung Galaxy S III] Noxious Ninja:
Could you tap the graph and take another screenshot? I'm interested in what it shows your cell signal strength as being. Also, did you have wifi turned completely off?

This is pretty normal for me, but I leave Wifi on all the time. Might have to make a Llama/Tasker task to keep it off unless I'm at home...

Stock, used it for about a day, then flashed root66. I was at home and actually connected to Wifi maybe 4 hours of this time. BetterBatteryStats shows Screen On 1h28m and Awake 2h15m, Deep Sleep 3h1m.
[Verizon Samsung Galaxy S III] aigochamaloh:
Here's mine. Like I said earlier, I don't have the cell signal fix, but it doesn't bother me really. This phone really has fantastic battery life. If I wasn't playing with it more than I usually use my phone, it could go 1.5-2 days easily.
[Verizon Samsung Galaxy S III] aburgthing:
Just dropping by to say thank you. Followed directions, no problems to report. New to Samsung but this was pretty easy.
[Verizon Samsung Galaxy S III] trott33:
^+1
[Verizon Samsung Galaxy S III] mb27:
I dunno why I'm having such a big battery problem with this... my phone had 75% battery remaining when I went to bed. When I woke up 7 hours later it was dead :confused:

I think I'm going to flash the stock rom tonight and see if my battery life returns to normal. If it does I'll flash root66 again and just leave it plain (no widgets, no different launcher, no frozen apps, etc) to see how that goes.
[Verizon Samsung Galaxy S III] Elite49:
Might be your battery.
[Verizon Samsung Galaxy S III] mb27:
Think it could happen so soon? I mean, I was getting wonderful battery life right up until I rooted..

After losing 15% battery life in the last hour without even touching my phone, I downloaded this app called Watchdog and it said Facebook is using 50% of the CPU in the background. It doesn't show up as a factor in the battery info screen, but I wonder if maybe the FB app is my problem?

I went one step ahead of force closing it and uninstalled Facebook for now. I'm interested to see how the next hour goes.
[Verizon Samsung Galaxy S III] blueb0x:
That used to be a major issue on my droid x. There were a few replacement apps - the only one I can remember is Friendcaster.
[Verizon Samsung Galaxy S III] mb27:
Alright, I'm back to 100% stock. Fully charged my phone, unplugged 90 minutes ago, and it's still at 100% just like it should be. So I am confident there is no hardware issues.

I'm going to try one more time to flash the root66 rom. This time I won't install any other apps or widgets after I flash and see how it does. Then the painful process of installing things one at a time to find out what the problem app is.

Ahh, the joys of rooting..

UPDATE: Phone is rooted again and I've done nothing but setup gmail. Fully charged up and unplugged 1hour 4 mins ago. Still at 100%! Before I was losing 10-20% an hour, doing nothing! Clearly it must be an app I downloaded or froze causing the massive drain. Hopefully I can figure it out quickly and this won't take up my weekend, because I will work on it until I figure it out!
[Verizon Samsung Galaxy S III] Elite49:
Should compare your apps to someone who has a rooted phone with good battery life. Though it doesn't surprise me if rooting does mess up the battery since others have reported this. Before I get my phone I want see what the real issue is.
[Verizon Samsung Galaxy S III] DROID3R:
HEY I JUST GOT MY GALAXY S 3 TODAY.

ok so i set up the phone to my liking with apps and settings. but i would like to be rooted. im coming from a droidchage.

so just to comfirmed after i flash this rooted rom my settings and apps will remain intact right? only change is gaining root?

thanks in advance.
[Verizon Samsung Galaxy S III] mb27:
That is correct.

You'll only lose settings/apps if you do a factory reset from the settings menu or wipe data from recovery. At least, with this ROM anyway.
[Verizon Samsung Galaxy S III] Elite49:
Would love to know what it was, as it could help many out. Not reading that far back in topic did you try that betterbatterystats app? Just downloaded it for my current phone in prep for GS3 and went from a 5% change in awake/screen on to 3% change. Seems like I did pretty damn good with keeping apps asleep. :silly:
[Verizon Samsung Galaxy S III] mb27:
Morning update: Battery drained 3% in the 6.5 hours I slept last night. No problems with the handful of apps I've installed so far (google voice, lux free, SvZ, Sentinel3, updated maps, youtube, and gmail). I just installed the Amazon App store and Fancy Widgets Pro. I also own Beautiful Widgets but a lot of reviews in the play store are reporting issues.

So far I've yet to figure out what the issue was. I thought it may have been the Facebook app (look at the recent reviews in Play store, they are awful) but after I uninstalled it nothing changed.

I have not tried betterbatterystats but I'll look into it.
[Verizon Samsung Galaxy S III] Elite49:
http://xdaforums.com/showthread.php?t=1179809

Free for XDA users
[Verizon Samsung Galaxy S III] guyd:
Thanks for the updates. I've never had Facebook installed on my S3, and have had strange battery behavior on occasion. It doesn't happen often, just once in a while. Like you, I haven't been able to pinpoint what rouge app is causing it. It happens so random, that I think it may be a Samsung bug. And the battery monitor (gsam) didn't log what kept the phone awake and burned up the battery. Strangest problem I've ever seen on any of my Android phones!
[Verizon Samsung Galaxy S III] JoeyBert:
Does anyone know why the email color scheme changes from Black on White to White on Black after root? Is there anyway to change it? I rooted/unrooted/rooted to test this.
[Verizon Samsung Galaxy S III] mb27:
Thanks! I saw it on the market for a couple bucks and thought I didn't really need it that bad. But for the price of free I might as well try it!

No problem. I've installed a couple more apps (AdAway, Dolphin HD, and XDA), still no Facebook yet, and I'm still getting great battery life, especially considering at work I get a horrible signal.

Before I go to bed tonight I plan on installing facebook.
[Verizon Samsung Galaxy S III] stang6790:
If you are talking about the background color of the individual emails that may be the "Background color" setting in "power saving". If it is turned on the background on the emails will be black.
[Verizon Samsung Galaxy S III] pjamv5:
I haven't figured this out yet, either. I swear when I originally set everything up on stock there was a dark or light "theme" option in the email app. I remember because it was originally black background, but I prefer white so I changed it. I haven't been able to find that option on root66 or more recently on NoSympathy. Interestingly, I didn't do a factory reset when I flashed root66 or NoSympathy so my white background has persisted.
[Verizon Samsung Galaxy S III] nosympathy:
I could be an absolute idiot, wouldn't be the first time, but I swear there is a setting I saw somewhere that allows you to have the mail app show a black background to save battery life.

I think it was in the power saver in settings? If you enable it, it changes the background of email to save power?

My phone is in the middle of flashing so I cannot look.
[Verizon Samsung Galaxy S III] pjamv5:
No you're right, there is, but all that seems to do is change the background of an actual email. The main inbox list background color remains unaffected. I'm baffled as to how I did this unless stock truly is different somehow. I did a factory reset and temporarily flashed beans rom, and my email background was black with no option (at least that I could find) of changing it. Restored my backup of root66, and obviously I got the white background back but still couldn't find the option to change it. Then when I flashed your rom I didn't do the factory set, and my white background is still there.
[Verizon Samsung Galaxy S III] open1your1eyes0:
RE (last couple of posts) - Settings > Power saving > Background color (Enable this)