Database Users

S=off 1.49.2 Hboot in update.zip format

Link removed until i can test again sorry...
Disclaimer: While tested, and working on ECLIPS3's test device, this is a risky flash. Flashing this is at your own risk. If data or property loss occurs, its you fault, not mine.
The s-off spl allows you to use fastboot, and can make recovery of a "softbricked" device much easier.
Flash this like any other flashable file through recovery.

Nice way better than doing a battery pull when flashing the original root zip.

sickbox said:
Nice way better than doing a battery pull when flashing the original root zip.
Click to expand...
Click to collapse
The battery pull method won't even work on phones with a newer mainversion, so yeah way better.

jcase said:
http://www.multiupload.com/SGKRIJBQ6Q
Disclaimer: While tested, and working on ECLIPS3's test device, this is a risky flash. Flashing this is at your own risk. If data or property loss occurs, its you fault, not mine.
The s-off spl allows you to use fastboot, and can make recovery of a "softbricked" device much easier.
Flash this like any other flashable file through recovery.
Click to expand...
Click to collapse
Sweet thanks
Sent from my FroyoEris using XDA App

Awesome work thx man

Speechless...take that back, your a dev god! Haha thanks jcase and eclipse.
Sent from my ERIS using XDA App

this unlocks the hboot and pushes a new amons ra recovery?
basically one flash and you have s-off?
this is a good day!!

Wow great work! thanks

"Syntax error in update script
Installation aborted"
????

ThorSkaagi said:
"Syntax error in update script
Installation aborted"
????
Click to expand...
Click to collapse
I'm getting the same error when flashing in recovery.

ThorSkaagi said:
"Syntax error in update script
Installation aborted"
????
Click to expand...
Click to collapse
I had the same issue. The file you downloaded is corrupted. Try downloading again. If it still persists, maybe the upload got corrupted and jcase should try posting it again.

cloudedice said:
I had the same issue. The file you downloaded is corrupted. Try downloading again. If it still persists, maybe the upload got corrupted and jcase should try posting it again.
Click to expand...
Click to collapse
I re-downloaded it twice - same error. Just to be clear, we just flash it like we would any ROM, right?

I tried all of the downloads and they all gave me the same error as seen above.

ThorSkaagi said:
I re-downloaded it twice - same error. Just to be clear, we just flash it like we would any ROM, right?
Click to expand...
Click to collapse
If you try to open the zip with Winzip or something, it'll error out saying the file is corrupted. I suspect the upload didn't complete successfully.

cloudedice said:
If you try to open the zip with Winzip or something, it'll error out saying the file is corrupted. I suspect the upload didn't complete successfully.
Click to expand...
Click to collapse
If that's the case, its good it didn't mess anyone's Eris up :/

I got the same error.
Sent from my Eris using XDA App

so in theory when this does work it will flash the eng. rooted 2.1 or just the bootloader? im not trying to go through everything again but if it only replaces the bootloader then im game. Other wise im just waiting till i get my replacement tomorrow.

Can you post the md5 sum

Dc_striker said:
Can you post the md5 sum
Click to expand...
Click to collapse
he pulled the link until he can further test this bugger, but im excited, this will take away some of the hassle of rerooting 5 refurbs. although it would have been nice 4 refurbs ago lol great work man keep it up.

I got the same error.

[Q] ROM Not Installing Correctly on HTC Aria

I have rooted my HTC Aria which is currently running 2.1. I also have ClockWorkMod Recovery v2.5.0.1 and the liberated_aria_FR008_signed.zip ROM for attn1. But when I try to install the ROM is looks as if it is starting to install but then when it says installing or something like that it jumps back to the Recovery menu screen and does not seem as if it has installed it completely. So I have tried this couple times and have rebooted through recovery and it just starts up as a restored version of 2.1 that was originally on my phone. Not sure what I am doing wrong. It seems as if everyone does this with such ease. Please help.

hov215 said:
I have rooted my HTC Aria which is currently running 2.1. I also have ClockWorkMod Recovery v2.5.0.1 and the liberated_aria_FR008_signed.zip ROM for attn1. But when I try to install the ROM is looks as if it is starting to install but then when it says installing or something like that it jumps back to the Recovery menu screen and does not seem as if it has installed it completely. So I have tried this couple times and have rebooted through recovery and it just starts up as a restored version of 2.1 that was originally on my phone. Not sure what I am doing wrong. It seems as if everyone does this with such ease. Please help.
Click to expand...
Click to collapse
Number 1 mistake is booting into ClockworkMod with the USB cable connected. Disconnect the USB cable before you boot into ClockworkMod to flash the new ROM.

tpbklake said:
Number 1 mistake is booting into ClockworkMod with the USB cable connected. Disconnect the USB cable before you boot into ClockworkMod to flash the new ROM.
Click to expand...
Click to collapse
I have done that. USB was not attached to phone when booted into ClockworkMod. I just don't know why the ROM is not installing correctly. Anything else you can tell I may have done wrong?

hov215 said:
I have done that. USB was not attached to phone when booted into ClockworkMod. I just don't know why the ROM is not installing correctly. Anything else you can tell I may have done wrong?
Click to expand...
Click to collapse
You should make sure that you have a good download of the ROM by comparing the MD5 checksum of the zip file on your SD card with the MD5 checksum on the download page.

tpbklake said:
You should make sure that you have a good download of the ROM by comparing the MD5 checksum of the zip file on your SD card with the MD5 checksum on the download page.
Click to expand...
Click to collapse
Not sure how to do that.

hov215 said:
Not sure how to do that.
Click to expand...
Click to collapse
Did you download the ROM file to a PC and then copy it to the SD card? If so then here is a Windows version of md5sum that you can run and generate the MD5 checksum. Then compare that with the MD5 value this is on the download page. If the values don't match, then try downloading the ROM file again.
If you downloaded directly to the SD card, then you can make a "adb shell" connection and run the md5sum program on the phone to check the zip file.

tpbklake said:
Did you download the ROM file to a PC and then copy it to the SD card? If so then here is a Windows version of md5sum that you can run and generate the MD5 checksum. Then compare that with the MD5 value this is on the download page. If the values don't match, then try downloading the ROM file again.
If you downloaded directly to the SD card, then you can make a "adb shell" connection and run the md5sum program on the phone to check the zip file.
Click to expand...
Click to collapse
thanks. i am using a Mac and don't see any link or attachment with the program you are referring to.

hov215 said:
thanks. i am using a Mac and don't see any link or attachment with the program you are referring to.
Click to expand...
Click to collapse
Then it looks like Google will be your friend. I'm sure the Mac can generate MD5 checksums in some manner.
Anyway, so did you download to the Mac first and then copy it to the SD card or did you download it directly to the SD card?

tpbklake said:
Then it looks like Google will be your friend. I'm sure the Mac can generate MD5 checksums in some manner.
Anyway, so did you download to the Mac first and then copy it to the SD card or did you download it directly to the SD card?
Click to expand...
Click to collapse
downloaded to the Mac first and then .zipped it because my downloader auto-unzips files. then i dragged onto my SD card. Then unplugged USB and then booted into ClockWork Recovery. Did the restore and empty cache steps and attempted to install the Liberated ROM. It seems like it is installing but never seems to say complete. so then i reboot and it still goes to 2.1

i boot into recovery mode then i restore to factory settings, then i empty devlk cache which seems to not even run but just shoot back to the menu when i hit "YES". Then I go to install the ROM but it doesn't seem to be installing completely

hov215 said:
i boot into recovery mode then i restore to factory settings, then i empty devlk cache which seems to not even run but just shoot back to the menu when i hit "YES". Then I go to install the ROM but it doesn't seem to be installing completely
Click to expand...
Click to collapse
As it is installing, what is it displaying on the bottom of the screen?

Try downloading from your phone browser. It may be the whole, unzip /rezip process that's fuxing it up.
Sent from my Liberty using XDA App

tpbklake said:
As it is installing, what is it displaying on the bottom of the screen?
Click to expand...
Click to collapse
It says:
"Finding update package"
"Opening update package"
"Installing update..."
But it does all that really fast and then just goes back to the ClockWorkMod menu screen. Then I try and reboot and it is still 2.1

zervic said:
Try downloading from your phone browser. It may be the whole, unzip /rezip process that's fuxing it up.
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
hov215 said:
It says:
"Finding update package"
"Opening update package"
"Installing update..."
But it does all that really fast and then just goes back to the ClockWorkMod menu screen. Then I try and reboot and it is still 2.1
Click to expand...
Click to collapse
You are selecting the "choose zip from sdcard" in ClockworkMod, right?

tpbklake said:
You are selecting the "choose zip from sdcard" in ClockworkMod, right?
Click to expand...
Click to collapse
Yes, I am trying to download directly from browser to the SD Card this time and see if that works.

zervic said:
Try downloading from your phone browser. It may be the whole, unzip /rezip process that's fuxing it up.
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Thank you so much!!! That was it! I downloaded the .zip file straight from my phone's browser to my SD Card and installed via recovery mode and it worked perfectly. Now running 2.2 perfectly.
You are a genius to walk me through that.

hov215 said:
Thank you so much!!! That was it! I downloaded the .zip file straight from my phone's browser to my SD Card and installed via recovery mode and it worked perfectly. Now running 2.2 perfectly.
You are a genius to walk me through that.
Click to expand...
Click to collapse
Make sure tto thank Blake too lol if he didn't ask everything he asked (which I would have asked if he didn't) I wouldn't have been able tto suggest that glad to see you got it workin
Sent from my Liberty using XDA App

Does that ROM have the HTC sense with the active weather??
Sent from my HTC Liberty using XDA App

I have done everything except flash the rom cause I want to make sure its running HTC sense, does anyone know???
Sent from my HTC Liberty using XDA App

hawk8509 said:
I have done everything except flash the rom cause I want to make sure its running HTC sense, does anyone know???
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Yes it does. Its liberated froyo.
Sent from my Liberty using XDA App

sbf failed! bricked phone?

hi i was using the sbf 1.2.6 file from http://bandbinnovations.com/xda/OLYF..._1g_1FF.sbf.g. site, i flashed in rsd mode and it went through ecxeuction 100%, then went through flashing the different files, but then as it was flashing the files at about 86% it said flashing failed "because of switching device to bp pass mode failed". and now iam stuck at the red M screen, what can i do now?. i have tried about 4 different sbf files but they have never done this. . can someone help. what do i do now?

Did you check the MD5 hash? Also did you give the .SBF a shorter file name? This solved all my problems personally.

Moved to general.

bongd said:
Did you check the MD5 hash? Also did you give the .SBF a shorter file name? This solved all my problems personally.
Click to expand...
Click to collapse
what is the MD5 hash, and yes i did renamed the.sbf.gz to atrix.sbf. dont know what to do?

Hi
Rename the file to smtng shorter
Make sure the the battery is full and you might wanna use a PC and not a laptop ( my laptop was part of the problem when I tried to flash an sbf to a soft brick phone)
If it doesn't work for you pm me and ill send you a complete way to do it
Sent from my MB860 using XDA App

See if you can access RDS protocol by holding Vol. Up at boot. Then retry.

RPK925 said:
what is the MD5 hash, and yes i did renamed the.sbf.gz to atrix.sbf. dont know what to do?
Click to expand...
Click to collapse
You have to extract the file, not rename it.

Yeah first need to extract the .Gz file and then rename the long sbf file to smtng shorter
Sent from my MB860 using XDA App

AmitMa said:
You have to extract the file, not rename it.
Click to expand...
Click to collapse
i downloaded it on my sd card then extracted it to the root if my c:\ drive, and renamed it ryan.sbf.

I
RPK925 said:
hi i was using the sbf 1.2.6 file from http://bandbinnovations.com/xda/OLYF..._1g_1FF.sbf.g. site, i flashed in rsd mode and it went through ecxeuction 100%, then went through flashing the different files, but then as it was flashing the files at about 86% it said flashing failed "because of switching device to bp pass mode failed". and now iam stuck at the red M screen, what can i do now?. i have tried about 4 different sbf files but they have never done this. . can someone help. what do i do now?
Click to expand...
Click to collapse
Wow! Today I woke up ready to call.att.warranty, and powered up mt Atrix and I went to the M screen and I thought it would stay there because of the failed SBF flash the night before, and then to my surprise it then popped up the" rethink possible" att logo. And I thought I was dreaming. It started up like normal, and im now rooted on 1.2.6. I have now idea how it happened, but im glad it did. Does anyone have anyidea what happens or have ever heard of this before? It was bricked on the M screen all last night, and now im back to stock. Very strange.
Sent from my MB860 using XDA Premium App

nosit1 said:
See if you can access RDS protocol by holding Vol. Up at boot. Then retry.
Click to expand...
Click to collapse
Actually last night for about a hour a could not get to the.RSD protocol screen. Then I tried powering up pushing both the vol up and down button at the same time and that worked, for me. I have no idea why it worked when I pushed both but it did.
Sent from my MB860 using XDA Premium App

[Q] Can you install the 4.1.2 OTA on an unlocked phone with CWM installed?

I got the ota the other day and debated installing it because my M is rooted and the bootloader is unlocked and I have flashed ClockworkMod recovery. I searched for a while to see what others were saying and didn't really find anything of note so I decided to go ahead and run the install. When the phone rebooted into recovery and tried to install the update, it gave me the following Error: E: Failed to verify whole-file signature. Then there was an option to apply unsigned update (or zip, I can't remember the wording exactly). I chose not to do this and went back in the recovery menu and rebooted back into system. The phone booted normally and then immediately rebooted on its own back into recovery to try to install the update again, ending in the same results. This happened 2-3 more times before I finally formatted the Cache Partition through cwm which ended the bootloop (not sure that you can really describe that as a bootloop since it was actually doing what it thought it should be). My question is this, is it safe to go ahead and install the unsigned update via CWM? I have also since seen threads stating that if you had removed some of the bloatware apps, that the update would fail. I have removed many of these unneeded apps, should I reinstall them? I have seen a link or two to the bloat apks...

Having a unlocked bootloader doesn't matter. You just need to be stock 4.1.1 bloatware and all.

what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.

Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app

bobcheeks said:
Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No. You don't have to unroot. You must have modified something else.
Sent from my Nexus 7 using Tapatalk 2

antp121 said:
what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.
Click to expand...
Click to collapse
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!

bwat1009 said:
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!
Click to expand...
Click to collapse
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2

antp121 said:
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...

bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
I RSDed back to 4.1.1 because mine hung on the clock app. I had installed the 4.2 clock.

bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...

sloosecannon said:
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...
Click to expand...
Click to collapse
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...

After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.

bwat1009 said:
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...
Click to expand...
Click to collapse
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.

tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium

Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Alright, thanks for the tip and the link, I will give it a try and let you know...

tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
I'm pretty sure you need an unlocked boot loader to downgrade.

netizenmt said:
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
I did. It fixed an issue where my phone wasn't booting, but it did not revert me to 4.1.1. Just found your comment in the other thread about modifying the xml file.. I'll try that next. Thanks.

patehi nice
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
That worked at getting the system apps that I had removed back into the /syste/app directory and now the update appears to be installing... Will let you know if it works.
*UPDATE*
Well that worked like a charm, update installed successfully, root access maintained, cwm allowed me to prevent reflash of stock recovery so all is right with the world... Thanks you guys!

Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Thank you! I had missing Amazon_IMDb.apk, Facebook.apk, Kindle.apk, PlusOne.apk files. Copied these to my phone and updated successfully!

TWRP not installing ROM

So I've downloaded the CM 10.2 RC1 update, but every time I try to install it, TWRP says "No MD5 file found" acts busy a little bit and then stops as if it was done. But when I check "About this phone" it says I'm on the 11/22 nightly. Um, what's going on?
Thanks in advance for the help.
Sent from my Nexus 4 using Tapatalk

jcicora said:
So I've downloaded the CM 10.2 RC1 update, but every time I try to install it, TWRP says "No MD5 file found" acts busy a little bit and then stops as if it was done. But when I check "About this phone" it says I'm on the 11/22 nightly. Um, what's going on?
Thanks in advance for the help.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
change recovery version and download a different rom from CM