• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Verizon] Odin fail after root attempt

Just a thought here, are you using the o.e. usb cord?
And what error do you get when trying to install TWRP?
And are you checking the md5 of the download to make sure it isnt corrupt?
 
JohnnyT said:
Still at the same point. Boot into CWM, choose zip from sd card, choose zip from external sd card, choose SuperSU_Bootloader_FIXED.zip, Yes - Install SuperSU_Bootloader_FIXED.zip, then get the following message:
set_perm: some changes failed
E:Error in /external_sd/SuperSU_Bootloader_FIXED.zip
(Status 7)
Installation aborted.

Can't stand this!!!!
Click to expand...


Do you have a spare sdcard you could try? Or worst case, save/pull the current contents off your sdcard and onto a pc, and then reformat the sdcard using your card reader and windows to do a full reformat (not quick). I've always had good luck using fat32 format for all things android. Then replace the zip, put back in phone and try flashing from cwr again. Just a thought, maybe there's a read issue from the card.
 
Mikestony, I am using the USB cord that came with the phone, but I can try another cable. I just don't think it is the cable since it works fine when using Odin and flashing both VRALEC Boot chain and the CMW. Just doesn't want to work with the TWRP.

Not sure how to check the MD5. Odin didn't have a problem putting both CMW and TWRP into the PDN.

Attaching the TWRP error. Thanks so much for all the help though. I really appreciate it. I've had to resort to going back to my rooted Incredible 2 in the meantime. The difference is NIGHT and DAY, lol.
 

Attachments

  • TWRP_Fail01.png
    TWRP_Fail01.png
    160.2 KB · Views: 102
iowabowtech said:
Do you have a spare sdcard you could try? Or worst case, save/pull the current contents off your sdcard and onto a pc, and then reformat the sdcard using your card reader and windows to do a full reformat (not quick). I've always had good luck using fat32 format for all things android. Then replace the zip, put back in phone and try flashing from cwr again. Just a thought, maybe there's a read issue from the card.
Click to expand...

Are you good with adb shell commands?
 
JohnnyT said:
Mikestony, I am using the USB cord that came with the phone, but I can try another cable. I just don't think it is the cable since it works fine when using Odin and flashing both VRALEC Boot chain and the CMW. Just doesn't want to work with the TWRP.

Not sure how to check the MD5. Odin didn't have a problem putting both CMW and TWRP into the PDN.

Attaching the TWRP error. Thanks so much for all the help though. I really appreciate it. I've had to resort to going back to my rooted Incredible 2 in the meantime. The difference is NIGHT and DAY, lol.
Click to expand...
As you can see, some of my friends have come to help out too as I am getting stumped!
Perhaps try as Iowabowtech suggested or what OutofPhases is suggesting:)
 
JohnnyT said:
Mikestony, I am using the USB cord that came with the phone, but I can try another cable. I just don't think it is the cable since it works fine when using Odin and flashing both VRALEC Boot chain and the CMW. Just doesn't want to work with the TWRP.

Not sure how to check the MD5. Odin didn't have a problem putting both CMW and TWRP into the PDN.

Attaching the TWRP error. Thanks so much for all the help though. I really appreciate it. I've had to resort to going back to my rooted Incredible 2 in the meantime. The difference is NIGHT and DAY, lol.
Click to expand...


we are working on a different way to "push" twrp on to your phone but want to make sure it is right before we pass it along. If you make any head way please let us know.
 
I don't believe the S3 has fastboot support does it? I wish it did cuz then we'd be right in my wheelhouse. I'm a little iffy once I get outside of fastboot and into odin.
 
Unfortunately, I'm a complete tool when it comes to ADB. Don't know a thing about it. I have tried again this morning on my laptop, rather than my desktop, and a different cable. Back to the same situation. Get into CWM and still get the Error 7.

I don't have another microSD either. But I did check that this one is indeed formatted as FAT32. I won't be around my desktop for a couple of days and don't have access to another card reader, so I can't reformat it until I get back.

I really appreciate all the help though. Please keep the suggestions coming.

Oh, and I don't think I have fastboot. I believe my Incredible 2 does when I boot into recovery, but that doesn't help this situation.
 
Hey guys, got a heads-up from IBT re. this thread and just wanted to contribute some observations.

Note: I do not own an SGS3 or have any direct rooting experience with it (or Odin for that matter), but I do have some comments about some stuff mentioned above.

The SuperSU_Bootloader_FIXED.zip file that is trying to be flashed is, as mentioned, failing with a status 7 error. That indicates that one of the edify commands inside the updater-script file has returned a non-true (i.e., false/null) value.

Here's the updater-script file for the SuperSU_Bootloader_FIXED.zip file:
Code: 
ui_print("...Installing SuperSU 0.98");
ui_print("Mounting system...");
run_program("/sbin/busybox", "mount", "/system");
ui_print("Deleting old files...");
delete("/system/bin/su","/system/xbin/su","/system/app/Superuser.apk");
ui_print("Copying files...");
package_extract_dir("system", "/system");
ui_print("Fixing permissions...");
[COLOR="Red"]set_perm(0, 0, 06755, "/system/xbin/su");
set_perm(0, 0, 0644, "/system/app/Superuser.apk");[/COLOR]
ui_print("Unmounting system...");
run_program("/sbin/busybox", "umount", "/system");
ui_print("");
ui_print("");
assert(getprop("ro.product.device") == "d2vzw" || getprop("ro.build.product") == "d2vzw");
ui_print("Installing d2vzw VRLE6 bootloader");
package_extract_dir("files", "/tmp");
[COLOR="red"]set_perm(0, 0, 0777, "/tmp/dd");[/COLOR]
if 
	sha1_check(read_file("/tmp/aboot.mbn")) != "6ddd4045b05e1f955f47445d88b734a9dc62bc49"
then
	ui_print("SHA1 SUM FAILURE! QUITTING!");
endif;
if 
	sha1_check(read_file("/tmp/aboot.mbn")) == "6ddd4045b05e1f955f47445d88b734a9dc62bc49"
then
	ui_print("SHA1 SUM Success! Flashing...!");
	run_program("/tmp/dd", "if=/tmp/aboot.mbn", "of=/dev/block/mmcblk0p5");;
	ui_print("Done!");
endif;
ui_print("Installation complete!");
There are three set_perm commands in the updater-script file that could be failing. The first two attempt to secure the root binaries (/system/xbin/su and /system/app/Superuser.apk). The third attempts to secure a file called /tmp/dd (i.e., which I'm presuming is a stand-alone Unix dd utility which is later used to flash what I'm guessing is the unlocked bootloader (it's name, aboot.mbn and contents do indicate that is true).

So, the flashing issue you're having with this .zip file is never getting to the point where the unlocked bootloader is flashed because all of the set_perm commands that might be failing occur before the installation of the new bootchain. Flashable edify scripts that fail do not continue on any further than the failing command.

I do not believe it will make a difference as to which custom recovery is used to flash this .zip file since there appears to be an issue that is causing it to fail. You'd probably have to re-install a custom recovery and use adb to snoop-around and see if you can figure-out what is going on with things that the updater-script file is doing and how far it might be getting (i.e., are the su and/or Superuser.apk files installed?).

Now, as to why the device is not booting-up / hanging? I can't (and am not qualified to) say (for this device), but I imagine that it's related to the issues you're having flashing...

That's all I've got for now...I'll keep looking around and thinking about this.
 
Okay, just got done reading through all 31 pages of the XDA thread and have just a few additional thought's:

1. Read through the OP to see if you carefully followed all of the directions. I'm mostly concerned about this line in Step 3:

o Uncheck the "Auto Reboot" box in ODIN ***VERY IMPORTANT***
Click to expand...

I don't know why it's important (never used Odin) and the author doesn't say...

2. Try reading through all of the thread, too, to see if there's anything anyone reported there that might help you or strikes a chord with you--you might realize something important that could help.

3. Since these are the only files whose MD5s were not listed, here are the values that I got after downloading them:

232b6ece093601cb70923c89cf0df693 *SuperSU_Bootloader_FIXED.zip
959cf38b9c6dda345529664283f3a4ce *VRLE6.bootloader.zip
e475747a3600137eb78347cae68dfbf1 *CWM-SuperSU-v0.99.zip​

(probably not relevant, but good to have for comparison).

Best of luck :).
 
Thanks for the help everyone, including scary alien. The problem has been resolved. I gave a friend that had rooted his S3 (Sprint) my phone and he said that all he did was flash a version of 4.1.2 on my phone through Odin. All I know is that my Verizon S3 has JellyBean installed and within Settings/About Phone, it states 4.1.2 and I have SuperUser access.
 
You must log in or register to reply here.
Back
Top Bottom