Major hang up with VD to VJ via auto root

[zatioichi]

So i was everything ready to run the rooting program and i got everything working after a few hickups. I had install the SDK to get things working but i got VD rooted I think. I got the message that let's you know that the phone was rooted and saw superuser had installed so i ASSUMED I was rooted and went on to do the ZVJ update that was placed on the sd card.

That's where the real problems began. When I ran the program again in stock recovery it said su was.denied and then something about an invalid file on the E:/ drive and not being able to read the cashe and when I went to try the ZVJ root it gives an error like /system/.sh not found invalid file or.path(2)


So after that all happened I tried to downgrade back to VD to try again to see where I messed up at. Only I can't, the foryo downgrade update zip can't be ran. Error.comes back saying the zip is unsigned.

So I'm really at the end of my rope, I really need help, what should I do? Where might I have gone.wrong? Anything to help cause right now I'm stuck on 2.33

 

[sfhub]

Without posting the log file I can't tell you what went wrong specifically, but it sounds like the ZVJ recovery wasn't installed because there was some problem with root.

Do you know if you currently have Xionia recovery or is it stock Recovery?

Stock recovery only has 4 options. Xionia has more.

If Xionia, then you need to turn of signature verification for it to run the ZVD updater.

BTW on the main menu of Auto Root, Option H, will enable the scroll buffer so it is easier to see what is going on.

 

[sfhub]

So i was everything ready to run the rooting program and i got everything working after a few hickups. I had install the SDK to get things working but i got VD rooted I think. I got the message that let's you know that the phone was rooted and saw superuser had installed so i ASSUMED I was rooted and went on to do the ZVJ update that was placed on the sd card.

That's where the real problems began. When I ran the program again in stock recovery it said su was.denied and then something about an invalid file on the E:/ drive and not being able to read the cashe and when I went to try the ZVJ root it gives an error like /system/.sh not found invalid file or.path(2)

Only Step C is supposed to be run in Recovery. Step A and Step B are supposed to be run while the phone is in Android.

I wouldn't worry too much, you aren't really stuck from a technical standpoint, you are just panicking. If you work through things slowly w/o trying random things that might make things worse you can recover from what you have described so far. If you flail a lot, then you might get into a harder to recover situation.

Just answer the questions that are asked and we'll get you fixed up.

 

[zatioichi]

Without posting the log file I can't tell you what went wrong specifically, but it sounds like the ZVJ recovery wasn't installed because there was some problem with root.

Do you know if you currently have Xionia recovery or is it stock Recovery?

Stock recovery only has 4 options. Xionia has more.

If Xionia, then you need to turn of signature verification for it to run the ZVD updater.

BTW on the main menu of Auto Root, Option H, will enable the scroll buffer so it is easier to see what is going on.

Sorry about that, I made the thread right before bed cause I'd been working on it all night :x but no it is Stock recovery. Its like 3e.which might not mean much but I tried this on a friends computer so it might take a bit to get the logs but I did enable them. What do you recommend doing so its easier to id.what's happening for sure?

 

[sfhub]

Sorry about that, I made the thread right before bed cause I'd been working on it all night :x but no it is Stock recovery. Its like 3e.which might not mean much but I tried this on a friends computer so it might take a bit to get the logs but I did enable them. What do you recommend doing so its easier to id.what's happening for sure?

Ok, so you have stock recovery.

Do you have ZVJ/GingerBread installed?

If so, boot to ZVJ, make sure USB debugging is enabled, then continue from Step B.

You need to do everything from Step B to Step C (including the stuff on the phone) in sequence. Step B should copy a new update.zip to your phone, and reboot you to recovery. If it reboots to android instead of recovery, just repeat the step.

When you run the update.zip on your phone (while your phone is in recovery) it will mount /system so you don't get the /system/bin/sh error when you run step C. It WILL say INSTALLATION ABORTED. This is expected, just continue to Step C.

Step C should be run while your phone is still in recovery. It will install persistent root and xionia, but only if you performed the previously mentioned steps. If not, then you will get a /system/bin/sh error.

 

[zatioichi]

Ok, so you have stock recovery.

Do you have ZVJ/GingerBread installed?

If so, boot to ZVJ, make sure USB debugging is enabled, then continue from Step B.

You need to do everything from Step B to Step C (including the stuff on the phone) in sequence. Step B should copy a new update.zip to your phone, and reboot you to recovery. If it reboots to android instead of recovery, just repeat the step.

When you run the update.zip on your phone (while your phone is in recovery) it will mount /system so you don't get the /system/bin/sh error when you run step C. It WILL say INSTALLATION ABORTED. This is expected, just continue to Step C.

Step C should be run while your phone is still in recovery. It will install persistent root and xionia, but only if you performed the previously mentioned steps. If not, then you will get a /system/bin/sh error.

Alright Ill give it another go once I get back to that PC, it'll be today (hopefully) but.most likely tomorrow for sure so ill just have to keep you waiting, which again I'm sorry to have to do that. I'm just a bit worried cause I dont think I rooted right on VD.

EDIT: so I downgraded back to VD after remembering the update.zip wasn't on the top level of the SD card, so im going to just retry the auto root and then post the logs to see if i get the same errors again. Sorry about the mix up.