3711 replies to this topic

[symbiontsoul]

Yea, send me the actual error and I'll see if I have any ideas.  First idea...recopy the update zip to that phone and make sure it didn't get corrupted.

I did recopy as well as redownload the zip.

[symbiontsoul]

I even used the same sd card that worked in my other phone.

[johnlgalt]

Looks like I get to do some serious playing around tonight.  Maybe.

 

Same, I'll give all methods that I know about a shot on this puppy and see if any are worthy - Like you said, the original method you linked to looks the most promising, but I wouldn't bet on it.

[SamuriHL]

I'm not betting on much, no.  I'm prepping my phone with a fresh coat of system paint and re-root just in case I decide to get adventurous.  You know enough to keep root protected when you do the update and just try the exploits.  if they fail, restore root.

[smileythom]

So Sam, I hosed my phone by updating build.prop, sideloading the update and then it boot looped.  I tried wiping cache and then data, still no luck.  What do I have to do now, or am I stuck until we get the  FXZ in a few days.  

[SamuriHL]

Well you've definitely lost root unless an exploit happens.  Shit.  I'm not prepared to update yet so I can't really fix this for you yet.  Try applying the update in recovery again and then doing a factory reset before you reboot.

[johnlgalt]

GLWT - the few days part lol.

 

I think that a modified HoB with replaced CDT.bin, kernel, and a few other choice files (have to go back and look at the utility that Matt built for me when I proved that ICS could not revert to GB so folks would know for sure) might be a fix so that you can reinstall the ICS /system files with a JB kernel and then let the update run again - I *think* that is how it was done before, but I have to dig up the file / instructions to make sure.  And verify in hte updater-script that there is not more to it.

 

I won't have time to look, though, for at least a couple of hours.

[johnlgalt]

Well you've definitely lost root unless an exploit happens.  $#!+.  I'm not prepared to update yet so I can't really fix this for you yet.  Try applying the update in recovery again and then doing a factory reset before you reboot.

Will the update try to apply if the file hashes don't match what it is looking for?

[SamuriHL]

GLWT - the few days part lol.

 

I think that a modified HoB with replaced CDT.bin, kernel, and a few other choice files (have to go back and look at the utility that Matt built for me when I proved that ICS could not revert to GB so folks would know for sure) might be a fix so that you can reinstall the ICS /system files with a JB kernel and then let the update run again - I *think* that is how it was done before, but I have to dig up the file / instructions to make sure.  And verify in hte updater-script that there is not more to it.

 

I won't have time to look, though, for at least a couple of hours.

 

The HoB has this ability built in.  LOL.  No need to build shit.    However, I don't have recovery extracted yet.  One of you updated, rooted minions....run the recovery extract option in HoB and dropbox it to me.  

[SamuriHL]

Will the update try to apply if the file hashes don't match what it is looking for?

 

It might.  If not, we can force the issue.

[johnlgalt]

Yeah, that is what I was thinking - forcing it like we did with my phone to get it un-soft-bricked.

[SamuriHL]

Yeah, that is what I was thinking - forcing it like we did with my phone to get it un-soft-bricked.

 

That functionality is built into the HoB.  

[GeneralSpecific]

To anyone who may be interested, I followed Sam's instructions precisely.  I opened up TiBu to restore all of my apps, and wasn't able to gain root access.  Obviously, I was pretty upset and decided to put the phone down for a while so as to not get frustrated.  I check about 30 - 35 minutes later, and was granted root access!  So, for anyone who is having the same experience as me, you may just need to give the system time to configure itself.

[karthakon]

Well that didn't work either. I got the smb shares created and mounted and adb could see the phone, but it didn't give me root. I got read-only file system errors.

 

But once again Voodoo was able to restore root. 

[smileythom]

Well you've definitely lost root unless an exploit happens.  $#!+.  I'm not prepared to update yet so I can't really fix this for you yet.  Try applying the update in recovery again and then doing a factory reset before you reboot.

 

Thanks I'll try that.  

[smileythom]

Will the update try to apply if the file hashes don't match what it is looking for?

It actually got passed the verifying current system part.

 

I'll post after it's done.

[smileythom]

wiped data and rebooting now!  :-)  Here's hoping!  

[smileythom]

No luck, black screen!  :-(

[SamuriHL]

Well that didn't work either. I got the smb shares created and mounted and adb could see the phone, but it didn't give me root. I got read-only file system errors.

 

But once again Voodoo was able to restore root. 

 

Yea, that was what Kaos saw, as well.  Well boys and girls, we do NOT have a working root exploit for the Bionic JB release.  Those who took the plunge, don't ever flash system or f up your phone cause you will perma-lose root.  sigh.

[SamuriHL]

No luck, black screen!  :-(

 

SIGH. You may have to hang out for a bit then.