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.
./simg2img system.img.ext4 newsys.img.ext4
computed crc32 of 0x67bae0a7, expected 0x00000000
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.
One of the things that stands out from the output of running the below
Code:./simg2img system.img.ext4 newsys.img.ext4 computed crc32 of 0x67bae0a7, expected 0x00000000
The checksum after is not meeting what's expected. Not sure if this was the reason I couldn't flash the file. (invalid ext4 file)
I too have to head to bed. We see what tomorrow brings.
I flashed the stripped version, but couldn't get ADB to install any of the removed apps. Root Browser also couldn't install any apps either.
I installed the non-stripped with root and now messaging FC. That's a pretty much needed app IMHO.
Could someone list all issues with the other rooted romantic so I can compare to my phone.
Thanks
Sent from my SCH-I535 using xda premium
I think the key issue is that we actually have to "workaround" things. If that rooted system.img is really just stock + Superuser/su there is no reason why we should be experiencing anything different from stock.
my messaging is working fine but swype i can confirm is not working.
Watch if you do a factory reset things will start breaking even more.
I just used the stripped version that invisiblek posted. Then pushed Then apks that i want. Keyboard works and have no issues so far.
Sent from my SCH-I535 using xda app-developers app
Are you willing to do a factory reset on the device and confirm that it stays working? I'm still waiting to get off work before I can dive back into the roms.
Here's a theory I'm interested in trying.
1. Flash full stock image
2. Flash the "supposedly broken" rooted system.img that is in that thread
3. Flash CWM recovery
4. Take the full stock image, untar it, then
- Delete recovery.img (stock recovery), retar it again OR
- Delete everything besides system.img.ext4, retar it again OR
- Delete everything besides system.img.ext4, convert it with simg2img.sh, retar it again
5. Flash the new modified full stock image (now it doesn't reflash recovery to stock)
6. Boot and confirming everything is working
7. Boot in CWM recovery (which still stayed from before) and just flash Superuser.zip to root
Please do sir!i made root injected images for att in this thread.
you guys want me to try a vzw one?
Here's a theory I'm interested in trying.
1. Flash full stock image
2. Flash the "supposedly broken" rooted system.img that is in that thread
3. Flash CWM recovery
4. Take the full stock image, untar it, then
- Delete recovery.img (stock recovery), retar it again OR
- Delete everything besides system.img.ext4, retar it again OR
- Delete everything besides system.img.ext4, convert it with simg2img.sh, retar it again
5. Flash the new modified full stock image (now it doesn't reflash recovery to stock)
6. Boot and confirming everything is working
7. Boot in CWM recovery (which still stayed from before) and just flash Superuser.zip to root
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
Just formatted back to stock until issues can be resolved. The stock image (which I'm told this root is + su) lost all Sprint instances and any strange extra options. Also the Keyboards are back to functioning. Not to be a conspiracy theorist, but I feel that the root image has more going on with it than what we are told.
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Here's a theory I'm interested in trying.
1. Flash full stock image
2. Flash the "supposedly broken" rooted system.img that is in that thread
3. Flash CWM recovery
4. Take the full stock image, untar it, then
- Delete recovery.img (stock recovery), retar it again OR
- Delete everything besides system.img.ext4, retar it again OR
- Delete everything besides system.img.ext4, convert it with simg2img.sh, retar it again
5. Flash the new modified full stock image (now it doesn't reflash recovery to stock)
6. Boot and confirming everything is working
7. Boot in CWM recovery (which still stayed from before) and just flash Superuser.zip to root