Signing a ROM - Nexus One Q&A, Help & Troubleshooting

I need a bit of help... I have been trying to move from the last CM6 release to a nightly build. The problem I have is the update script STILL does not support the newest HBOOT (which came stock on my Nexus One). I KNOW it is compatible because the last CM6 works fine. There are a few bugs I was hoping might be fixed in a nightly release... hence I want to flash a nightly build to test/compare a bit.
In order to get the old CM6 build to work... I had to find a version someone had corrected the script to be compatible with HBOOT (Deleting a few lines in the updater-script file) and they resigned it and uploaded it. I am trying to complete the same procedure. I think it would be just as easy to add to the line that checks for the HBOOT version to make it compatible. Then I and others I have seen run into this issue... wouldn't have this problem. Anyways... the problem I am having is with resigning. I extract the contents of the ROM... delete META-INF/CERT.RSA, META-INF/CERT.SF, META-INF/MANIFEST.MF. Then I change the updater-script file (I have tried adding a check for my HBOOT version... as well as just removing the lines with the check). I then recreate the zip file with the same structure as before... and then use an "autosign" script to sign the zip file. In the end, I end up with a zip file containing the exact same file set as the original except with the 3 signature files changed and the update-script file modified. When I attempt to flash the ROM I get Error (status 6).
Am I signing properly? Is there any other file that needs to be deleted/modified when I sign the zip? Anyone know why the hell this hasn't been fixed in the update-script to since this has been a known issue for quite some time?

If you cant finish it, have you considered the reverting bootloader thread? Its fairly simple really. Personally Im stuck at the end of the procedure and Ive given up, but it has worked for most everyone else and the instructions are simple to follow. Unless you want to keep your spl id consider reverting, almost every custom rom uses the old one so having the new one could be a bit of a hassle going forward...

DMaverick50 said:
If you cant finish it, have you considered the reverting bootloader thread? Its fairly simple really. Personally Im stuck at the end of the procedure and Ive given up, but it has worked for most everyone else and the instructions are simple to follow. Unless you want to keep your spl id consider reverting, almost every custom rom uses the old one so having the new one could be a bit of a hassle going forward...
Click to expand...
Click to collapse
I would rather just keep my HBOOT the same... the reason being... I know it works with it. I would rather have a newer version than to revert. Also, I know it IS possible to modify the script and resign it. This is because I found one of the old CM6 ROM which someone had already fixed and resigned. I want to know how to sign it properly so that I also know how to do it later if I ever need. I was also thinking of adding some of my own stuff to the script to install a few things when I flash (Korean stock keyboard for example) to reduce my hassle after flashing a new ROM. My point being... I would really just like to know how to do this properly... whether it is easier to revert to an older HBOOT or not... I am not concerned with. Thanks though ^^.

Siging is easy: http://www.robmcghee.com/android/creating-an-android-update-zip-package/
Or you could use Amon RA 1.8 recovery with has no sig checks and will flash anything.

hmmm... forgot that sig checks were removed in Amon_Ra... I have to use 1.8.0.1 anyways because I have an SLCD N1. I removed the sig entirely... and still getting a status 6 error when I flash.
Code:
E:Error in /sdcard/CM6_Nightly.zip
(Status 6)
Installation aborted.
The strange thing is I don't get this error if I just zip it with the original updater-script. I don't know if it is erroring after it would have gotten the assert error... or before.
Anyway to figure out why exactly it is erroring out? I am not sure how to figure out what the status code means.
EDIT: HBOOT 0.35.0017 was just added to CM Nightlies... though... this still doesn't really help me on how to manually modify it... it does fix my immediate issue.

Goblinlord said:
hmmm... forgot that sig checks were removed in Amon_Ra... I have to use 1.8.0.1 anyways because I have an SLCD N1. I removed the sig entirely... and still getting a status 6 error when I flash.
Code:
E:Error in /sdcard/CM6_Nightly.zip
(Status 6)
Installation aborted.
The strange thing is I don't get this error if I just zip it with the original updater-script. I don't know if it is erroring after it would have gotten the assert error... or before.
Anyway to figure out why exactly it is erroring out? I am not sure how to figure out what the status code means.
EDIT: HBOOT 0.35.0017 was just added to CM Nightlies... though... this still doesn't really help me on how to manually modify it... it does fix my immediate issue.
Click to expand...
Click to collapse
Yeah... Status 6 is a certificate failure IIRC...
Does Kang-o-rama install on your phone? (I've taken the assert out).
Post me a link to your signed rom and I can have a look at it for you and resign it for you to test if you like?

djmcnz said:
Yeah... Status 6 is a certificate failure IIRC...
Does Kang-o-rama install on your phone? (I've taken the assert out).
Post me a link to your signed rom and I can have a look at it for you and resign it for you to test if you like?
Click to expand...
Click to collapse
I believe you about the certificate failure... I had a feeling I might not be signing it right. I did think that Amon_Ra 1.8.0.1 didn't check though.
Unless you have updated Kang-o-Rama then it won't install. I tried it about a week or 2 ago. I don't think the kernel was compatible with the SLCD screen. Booted up fine... just screen shuts off when it should go to boot splash. This is the same issue that other recoveries and older ROMs have had on my device. I can tell it boots fine though (buttons lighting up, logcat, adb shell, etc.). Yours does flash fine though.
I don't really need it resigned at the moment since they added HBOOT 0.35.0017 into the nightly device-info. I will upload it tonight just so I can see if you can help me figure out where I am going wrong (at work right now). Thanks. I was actually thinking it might be better if I made a separate package that installs the stock Korean IME as well as a few other things and removes a few of the google apps after initial flashing. This way I could easily apply it to any ROM package. The Korean IME is the big one for me as it I need it and I am actually quite fond of the stock Korean keyboard.

Related

Non-public froyo build updating issues

My phone is running build FRF33B (googling this build number returned no results at all). It was a non public build. I got the phone from Adobe as part of a (kongregate) promotion to get flash developers to edit some games so they could run on froyo, and hence I really don't know what was done to the phone before I got it (there's an unlocked symbol when it boots, and even though it's a t-mobile nexus I'm using it on AT&T's network).
FRF33B is nice and usable (but full of minor bugs which get irritating after a while), and I'd really like to update to the latest stable build, but it's not receiving any of the OTA updates, and trying to install any manually gives me a package signing verification failure.
Does anyone here know how I can update the phone? Do I need to downgrade it somehow? Do I need to root it? Any help would be appreciated.
Downgrade to erd79 would be my best suggestion and it will update to frf91 I hope that helps and if u need a update zip let me know and I can email it to u
Sent from my Nexus One using XDA App
Or just unlock your phone, put a custom recovery, and install whatever ROM you want. Look at the sticky in the development section for details.
Option 3: Search around for the FRF91 Universal update.zip, copy it to your SD card, and flash it via stock recovery.
rohandhruva said:
Or just unlock your phone, put a custom recovery, and install whatever ROM you want. Look at the sticky in the development section for details.
Click to expand...
Click to collapse
ok I've done this, and flashed the universal FRF91, now the phone is stuck on the animated X, is this normal? Do I just have to wait or did I do something wrong?
edit: it looks like it just rebooted itself.... still not getting past the animated x part though
edit: wiped the phone and tried again, now it works... got to set up everything on the phone again though and download my apps again... oh well. thanks for the help

[Q] A question to rom developers

Hi guys. I would like to adress a seroise issue that some of the nexus owners have.
I am one of them.
Most of the roms on the forum are not flashable due to a status 7 error. I got the same error using amon ra and clockwork recovery.
I underatand that the issu happend because i have some bad blocks or that the immages are bigger and could not be flashed. I can asure you that this is how i got my phone from google and i bought it on the first day it was availble online.
At this mpment i am seeking a solution that can solve my problem so i will be able to flash any rom ( rodriguez, enomether, cm6 , or evil nexus).
I was able to fflash some of the roms but i would really wanna be on the cutting edge.
probally a solution is to split the roms into 2 updates.zip.
i do not expect the prnogrammers to do it only for a small number of people but if you will be able to help me out and explain how to i will really appriciate this.
I am really desperate and need your help.
Thank you
Hay... Any one?
Are you bootloader-unlocked? try re-flashing a new recovery. That's all I can really think of. Splitting the update won't do anything, to the best of my knowledge.
Of course.
I flashes AMON RA 1.08 and clockworks.
Same deal. Nothing helps. I cannot install CM6 but I can install kang-o-rama that is based on CM6.
I am also able to flash emonther official but not the micromod that is based on that rom.
The rom just need to be smaller.
Extracted file "/system/xbin/tune2fs"
minzip: Extracted file "/system/xbin/upgrade_fs"
minzip: Extracted file "/system/xbin/vfp-crasher"
minzip: Extracted file "/system/xbin/wlan_cu"
failed to write boot partition from /tmp/boot.img
E:Error in /sdcard/MM-720p-WM950-MusEQ-v2.2.zip
(Status 7)
Installation aborted.
Failure at line 7:
install_zip SDCARD:/MM-720p-WM950-MusEQ-v2.2.zip
OK. This is what I have found out.
I cant flash the boot.img separately .
It has to be lower than 2.5. Thats why I am able to flash KANG O RAMA> couse its image is 2.35
I need a method in which the images will be lower.
How come some of the developers are unknown to this and some do?
Some of the Nexuses came out with bad blocks in the boot partition. It limits their ability to use custom ROMs, since custom ROMs usually include more options, newer kernels etc, which in turn makes the boot.img grow in size. Nothing much to do. Some of the ROM developers account for these devices and try to make boot.img smaller, some don't - or can't.
Micromod changes the original TheOfficial kernel to another one, with another boot.img - that's why you're unable to flash it.
OK, What can I do then?
What I wrote in the other thread, in General section - change the kernels of the customized ROMs based on Enomther or CM6 sources back to their original ones.

[Q] Update.zip doesn't apply when attempting to mod battery

I wanted to apply one of the battery mods to my captivate i896 (running the stock rogers rom), specifically version E.
I tried using the UOT Kitchen website at first but that failed. So then I tried to do it myself, but that also fails. Something seems to be going wrong when I try to apply the update.zip I have and I see no error output to help me trace it. Here's what I've been doing (when I tried it from scratch):
So I downloaded the related zip file from the second post, "scbm_E_grey_number.zip".
I then used "Android Theming and Tweaking" to get the framework file from my phone, and decompile it. I replaced the corresponding .png and .xml files from "scbm_E_grey_number.zip" to the appropriate folders in the decompiled folder from the ATT software. Then using the same software, I compile the framework apk again.
I then use the update.zip creator. I create a "framework" folder in the "placehere" folder for the update creator. Inside the framework folder I placed my new APK. I then ran the update creator to generate a new script, which copies from "framework" to "framework" on SYSTEM. Finally, I have it create the update.zip for me.
Everything is fine up to this point. I place the update.zip on my SD card, boot my phone into recovery, try to flash it...I get the following:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried this a few times with no luck
I'd like to figure this out in the hopes that I can do some mods of my own in the future, so any help would be great Thanks!
If you ever figuered this out please let me know too, i am having the same issue. I am using a Captive that I just restored with Odin. I unroot it and remove the applock on it. I get the same installation aborted issue. I then tried to install it with ClockWork recovery... that just crashed my phone and I had to reinstall again. So if anyone know what the problem is please chime in.
Can't theme the stock rom. It has to be a deodexed rom, which is essentially all of the custom ones. Also, don't flash mods through the stock 2e recovery, you want to do it through CWM.
TheEscapist said:
Can't theme the stock rom. It has to be a deodexed rom, which is essentially all of the custom ones. Also, don't flash mods through the stock 2e recovery, you want to do it through CWM.
Click to expand...
Click to collapse
Hmm I see, thanks for the info... there was no odex file for that particular file, so I thought I'd be lucky and it was possible :/
And, why should you use CWM to flash instead of the stock recovery?
ootz0rz said:
Hmm I see, thanks for the info... there was no odex file for that particular file, so I thought I'd be lucky and it was possible :/
And, why should you use CWM to flash instead of the stock recovery?
Click to expand...
Click to collapse
No problem. While on the topic, is that thanks button new, or am i just blind, and missed it all this time?
It's something about signatures, if I remember correctly, though, that may be 3e. I think part of it is that it's just typically done with CWM.
ootz0rz said:
I wanted to apply one of the battery mods to my captivate i896 (running the stock rogers rom), specifically version E.
I tried using the UOT Kitchen website at first but that failed. So then I tried to do it myself, but that also fails. Something seems to be going wrong when I try to apply the update.zip I have and I see no error output to help me trace it. Here's what I've been doing (when I tried it from scratch):
So I downloaded the related zip file from the second post, "scbm_E_grey_number.zip".
I then used "Android Theming and Tweaking" to get the framework file from my phone, and decompile it. I replaced the corresponding .png and .xml files from "scbm_E_grey_number.zip" to the appropriate folders in the decompiled folder from the ATT software. Then using the same software, I compile the framework apk again.
I then use the update.zip creator. I create a "framework" folder in the "placehere" folder for the update creator. Inside the framework folder I placed my new APK. I then ran the update creator to generate a new script, which copies from "framework" to "framework" on SYSTEM. Finally, I have it create the update.zip for me.
Everything is fine up to this point. I place the update.zip on my SD card, boot my phone into recovery, try to flash it...I get the following:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried this a few times with no luck
I'd like to figure this out in the hopes that I can do some mods of my own in the future, so any help would be great Thanks![/QUO
Flash perception
Click to expand...
Click to collapse
dfuse06 said:
Flash perception
Click to expand...
Click to collapse
Eh, I'm hesitant to flash a custom rom. I have a rogers captivate and don't want to be stuck with an at&t boot screen (in case I need for repair or whatever) and I don't want to be stuck with poor GPS performance (as mine works VERY VERY well right now).
ootz0rz said:
Eh, I'm hesitant to flash a custom rom. I have a rogers captivate and don't want to be stuck with an at&t boot screen (in case I need for repair or whatever) and I don't want to be stuck with poor GPS performance (as mine works VERY VERY well right now).
Click to expand...
Click to collapse
AT&T boot screen can be replaced, but you have to do a whole bunch of Odin stuff to get there. Also, that's because we(I'm on rogers as well) have a tweaked modem.bin. You can flash that, or one of the jupiter/JM9 fixes to get similar gps performance. But obviously, it's your choice. You are messing with a quite expensive piece of hardware. However, if you want to apply mods, you need to get a custom rom.
TheEscapist said:
AT&T boot screen can be replaced, but you have to do a whole bunch of Odin stuff to get there. Also, that's because we(I'm on rogers as well) have a tweaked modem.bin. You can flash that, or one of the jupiter/JM9 fixes to get similar gps performance. But obviously, it's your choice. You are messing with a quite expensive piece of hardware. However, if you want to apply mods, you need to get a custom rom.
Click to expand...
Click to collapse
I'd love to have a set of concise instructions detailing all that...but everything is all over the place and difficult to find :/ Right now I'm just mostly reading up on things and trying to learn
There's instructions in the dev forum. If I wasn't on my phone, I'd grab the link for you. As far as learning, you just have to spend hours and hours on here.
TheEscapist said:
There's instructions in the dev forum. If I wasn't on my phone, I'd grab the link for you. As far as learning, you just have to spend hours and hours on here.
Click to expand...
Click to collapse
Heh I've been trying. It's certainly a bit of a learning curve

I can't flash any 4.4 KitKat ROM's

Hey Guys,
I feel really stupid that I can't figure this out. I have a T-Mobile HTC One that I've tried 3 different 4.4 ROM's now (OMNI, CM11, and TripKat) and all of them fail. I perform a full factory reset and wipe before each. I've received several errors about a build.prop and something else but heres the most common and the latest:
"Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard *screen is cut off and can't read rest of line*
Error flashing zip '/sdcard/Download/m7ul_signed *screen is cut off and can't read rest of line*
Updating partition details...
Failed"
I'm currently running GPE 4.3 with Kernel version 3.4.10-ge22f38b which is the only stable restore I currently have. I have no idea what happen to the stock ROM I ALWAYS backup as soon as I get a new device. I was running the PAC Man ROM (sorry, I can't remember the name of it at the moment) before I ran into this issue. I'm still S-ON but I've never had a single issue flashing ROM's before 4.4. I've looked around but can't find anybody with this specific issue. I've seen some people that can't update to 4.4 from GPE 4.3 but thats not what I'm trying to do here. Any and all help would be GREATLY appreciated! Please let me know if theres any other pertinent information I left out. Thank you for your time!
-Greg
greg.dassing said:
Hey Guys,
I feel really stupid that I can't figure this out. I have a T-Mobile HTC One that I've tried 3 different 4.4 ROM's now (OMNI, CM11, and TripKat) and all of them fail. I perform a full factory reset and wipe before each. I've received several errors about a build.prop and something else but heres the most common and the latest:
"Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard *screen is cut off and can't read rest of line*
Error flashing zip '/sdcard/Download/m7ul_signed *screen is cut off and can't read rest of line*
Updating partition details...
Failed"
I'm currently running GPE 4.3 with Kernel version 3.4.10-ge22f38b which is the only stable restore I currently have. I have no idea what happen to the stock ROM I ALWAYS backup as soon as I get a new device. I was running the PAC Man ROM (sorry, I can't remember the name of it at the moment) before I ran into this issue. I'm still S-ON but I've never had a single issue flashing ROM's before 4.4. I've looked around but can't find anybody with this specific issue. I've seen some people that can't update to 4.4 from GPE 4.3 but thats not what I'm trying to do here. Any and all help would be GREATLY appreciated! Please let me know if theres any other pertinent information I left out. Thank you for your time!
-Greg
Click to expand...
Click to collapse
TWRP or CWM? Whichever it is, you have made sure you are running the latest version of the recovery?
There are also reports of needing to be S-OFF for some 4.4 roms to work. Still, I dont think that is your issue right now as they are able to flash the roms at least. (The issue with S-ON is crashing/rebooting once they get into the initial setup of the phone after first boot.)
Ken4G said:
TWRP or CWM? Whichever it is, you have made sure you are running the latest version of the recovery?
There are also reports of needing to be S-OFF for some 4.4 roms to work. Still, I dont think that is your issue right now as they are able to flash the roms at least. (The issue with S-ON is crashing/rebooting once they get into the initial setup of the phone after first boot.)
Click to expand...
Click to collapse
I was on the PAC-Man ROM and it would reboot like every third screen unlock! So that helps explain why that was happening at least! Hahaha!
I'm using TWRP...I haven't updated it in while so that could be the issue. I'm currently running v2.6.0.1. I'll have to check to see what the latest version is. I'll attempt to S-OFF (still laugh at that!) and update to the latest TWRP version and try again...thanks for the info!
greg.dassing said:
I was on the PAC-Man ROM and it would reboot like every third screen unlock! So that helps explain why that was happening at least! Hahaha!
I'm using TWRP...I haven't updated it in while so that could be the issue. I'm currently running v2.6.0.1. I'll have to check to see what the latest version is. I'll attempt to S-OFF (still laugh at that!) and update to the latest TWRP version and try again...thanks for the info!
Click to expand...
Click to collapse
2.6.3.3 is the latest. If you read the thread in most of these kitkat ROMs you'll need that version.
PcFish said:
2.6.3.3 is the latest. If you read the thread in most of these kitkat ROMs you'll need that version.
Click to expand...
Click to collapse
Thank you, sir!

Issues with OTA Update

Hi,
I am sorry if this has already been addressed, but I can't seem to find it anywhere. Anyway I am trying to get the OTA update and my main goal is to do it without losing all my data (yes I have a backup, yes I'd rather stay as far away from wiping my device as possible). My device is on the stock sense ROM, I have S-OFF and I am rooted with TWRP recovery. I've been following this guide, ( http://www.theandroidsoul.com/t-mob...mware-and-recovery-version-1-32-531-33-82340/ ) and I've gotten to the part where I need to flash the system file, this is where I get stuck I continuously get an error that reads "target reported max download size of 536870912 bytes
Invalid sparse file format at header magi". If anyone has any idea how to fix this it would be greatly appreciated. Thanks!
Maddog0057 said:
Hi,
I am sorry if this has already been addressed, but I can't seem to find it anywhere. Anyway I am trying to get the OTA update and my main goal is to do it without losing all my data (yes I have a backup, yes I'd rather stay as far away from wiping my device as possible). My device is on the stock sense ROM, I have S-OFF and I am rooted with TWRP recovery. I've been following this guide, ( http://www.theandroidsoul.com/t-mob...mware-and-recovery-version-1-32-531-33-82340/ ) and I've gotten to the part where I need to flash the system file, this is where I get stuck I continuously get an error that reads "target reported max download size of 536870912 bytes
Invalid sparse file format at header magi". If anyone has any idea how to fix this it would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
You must be new to S-OFF. Well let me tell you... you're S-OFF!!! you don't need to do all that. What you're really looking for is to update your firmware without wiping. Follows instruction here in the OP: http://forum.xda-developers.com/one-m9/development/firmware-t3068243
It's pretty direct. Download the NOWIPE zip and fastboot flash it. Done. Firmware will be updated. You then can just download an updated stock rom and install that with TWRP.
Teo032 said:
You must be new to S-OFF. Well let me tell you... you're S-OFF!!! you don't need to do all that. What you're really looking for is to update your firmware without wiping. Follows instruction here in the OP: http://forum.xda-developers.com/one-m9/development/firmware-t3068243
It's pretty direct. Download the NOWIPE zip and fastboot flash it. Done. Firmware will be updated. You then can just download an updated stock rom and install that with TWRP.
Click to expand...
Click to collapse
Yes, I am new to S-OFF, I've had an S4 for the last two years and never needed it, I understand the basic idea behind it but I didn't fully understand what I could so with it. Anyway, I have followed the instruction from your link and flashed the no wipe firmware, but I am still unable to flash a stock ROM, I am now getting this error:
Code:
script aborted: Package expects build fingerprint of htc/himaul_tmous/htc_himaul:5.0.2/LRX22G/505029.33:user/release-keys or htc/himaul_tmous/htc_himaul:5.1/LMY47O/560065.6:user/release-keys; this device has .
E:unknown command [set_err_msg]
Package expects build fingerprint of htc/himaul_tmous/htc_himaul:5.0.2/LRX22G/505029.33:user/release-keys or htc/himaul_tmous/htc_himaul:5.1/LMY47O/560065.6:user/release-keys; this device has .
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/OTA_HIMA_UL_L51_SENSE70_TMUS_MR_TMOUS_2.7.531.6_R4-1.32.531.33_release_445026.zip'
Error flashing zip '/external_sd/OTA_HIMA_UL_L51_SENSE70_TMUS_MR_TMOUS_2.7.531.6_R4-1.32.531.33_release_445026.zip'
Updating partition details...
Any Ideas? I feel like its something really stupid that I am missing but I've reall just hit a wall here.
Maddog0057 said:
Yes, I am new to S-OFF, I've had an S4 for the last two years and never needed it, I understand the basic idea behind it but I didn't fully understand what I could so with it. Anyway, I have followed the instruction from your link and flashed the no wipe firmware, but I am still unable to flash a stock ROM, I am now getting this error:
Code:
script aborted: Package expects build fingerprint of htc/himaul_tmous/htc_himaul:5.0.2/LRX22G/505029.33:user/release-keys or htc/himaul_tmous/htc_himaul:5.1/LMY47O/560065.6:user/release-keys; this device has .
E:unknown command [set_err_msg]
Package expects build fingerprint of htc/himaul_tmous/htc_himaul:5.0.2/LRX22G/505029.33:user/release-keys or htc/himaul_tmous/htc_himaul:5.1/LMY47O/560065.6:user/release-keys; this device has .
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/OTA_HIMA_UL_L51_SENSE70_TMUS_MR_TMOUS_2.7.531.6_R4-1.32.531.33_release_445026.zip'
Error flashing zip '/external_sd/OTA_HIMA_UL_L51_SENSE70_TMUS_MR_TMOUS_2.7.531.6_R4-1.32.531.33_release_445026.zip'
Updating partition details...
Any Ideas? I feel like its something really stupid that I am missing but I've reall just hit a wall here.
Click to expand...
Click to collapse
Looks like you're trying to flash an OTA. What I meant was to flash a stock ROM... but I looked in our dev section and noticed nobody has created one lol.
I'm a bit rusty on flashing stock stuff, but you should really ask the guys in this thread: http://forum.xda-developers.com/tmo...lease-read-rooting-using-twrp-t3069022/page34
My guess is that you just want to update your system too. I think i saw someone dumped the system and boot img and you can flash those, but I don't recall the exact method.
Basically S-OFF allows you to access different.. uuhh "partitions" (sorry bad terminology) because it bypasses any security checks. Partitions such as your firmware and radio. That's pretty much what S-OFF does. It allows you to flash any of the firmware and radios across all the different versions.
I would suggest to take a dip into custom roms and choose T-mobile as the carrier lol. I personally like Leedroid's rom, he keeps it pretty stock and is an awesome responsive dev.
Teo032 said:
Looks like you're trying to flash an OTA. What I meant was to flash a stock ROM... but I looked in our dev section and noticed nobody has created one lol.
I'm a bit rusty on flashing stock stuff, but you should really ask the guys in this thread: http://forum.xda-developers.com/tmo...lease-read-rooting-using-twrp-t3069022/page34
My guess is that you just want to update your system too. I think i saw someone dumped the system and boot img and you can flash those, but I don't recall the exact method.
Basically S-OFF allows you to access different.. uuhh "partitions" (sorry bad terminology) because it bypasses any security checks. Partitions such as your firmware and radio. That's pretty much what S-OFF does. It allows you to flash any of the firmware and radios across all the different versions.
I would suggest to take a dip into custom roms and choose T-mobile as the carrier lol. I personally like Leedroid's rom, he keeps it pretty stock and is an awesome responsive dev.
Click to expand...
Click to collapse
Alright, Ill look into that thread. I've read about S-OFF in the past and I'm very familiar with rooting and ROMs from my last few phones but OTAs were never something I worried about (since I always used a custom ROM). In all honesty I like sense 7, and I need WiFi calling for work (I spend a lot of time in places without service, like data centers), so I think I am going to try to stick with stock. Anyway, thanks for all your help!
Maddog0057 said:
Alright, Ill look into that thread. I've read about S-OFF in the past and I'm very familiar with rooting and ROMs from my last few phones but OTAs were never something I worried about (since I always used a custom ROM). In all honesty I like sense 7, and I need WiFi calling for work (I spend a lot of time in places without service, like data centers), so I think I am going to try to stick with stock. Anyway, thanks for all your help!
Click to expand...
Click to collapse
Yeah I can tell by how long you've been a member here. But the thing with HTC ONE is that a lot of the custom roms are based off stock and they even compile it so that the aroma installer allows you to choose your carrier so that it will install it based off of your carrier's stock base. I work in a similar environment and also need wifi calling and these custom roms have that feature.
LeeDroid, insertcoin, viperrom (off the top of my head) should have working wifi calling.
Basically you install their rom and they ask you which carrier you want to install it for... choose T-mobile. And you should be set. Now I know that the new fw was just released for T-mobile, so I'm not sure if insertcoin and Viper have updated theirs yet, but i know for sure that LeeDroid has updated his. Give it a shot and come back to the custom flashing world lol
OOPS looks like LeeDroid hasn't pushed the T-mobile update yet he's planning to, so probably tomorrow.
Teo032 said:
Yeah I can tell by how long you've been a member here. But the thing with HTC ONE is that a lot of the custom roms are based off stock and they even compile it so that the aroma installer allows you to choose your carrier so that it will install it based off of your carrier's stock base. I work in a similar environment and also need wifi calling and these custom roms have that feature.
LeeDroid, insertcoin, viperrom (off the top of my head) should have working wifi calling.
Basically you install their rom and they ask you which carrier you want to install it for... choose T-mobile. And you should be set. Now I know that the new fw was just released for T-mobile, so I'm not sure if insertcoin and Viper have updated theirs yet, but i know for sure that LeeDroid has updated his. Give it a shot and come back to the custom flashing world lol
OOPS looks like LeeDroid hasn't pushed the T-mobile update yet he's planning to, so probably tomorrow.
Click to expand...
Click to collapse
Just installed this one https://mega.nz/#!7JImgSKD!UHs07fG8IiN5FJ6YhPncf8tIZdjjQFeUeRZUN3diVuo and it gave me the "T-Mobile US" option so maybe he just updated it?
Maddog0057 said:
Just installed this one https://mega.nz/#!7JImgSKD!UHs07fG8IiN5FJ6YhPncf8tIZdjjQFeUeRZUN3diVuo and it gave me the "T-Mobile US" option so maybe he just updated it?
Click to expand...
Click to collapse
Oh no that option is always there. We should be expecting a r16 soon. With the new base for T-Mobile. You can always install that rc2 now an update to r16 when he releases it tomorrow. Unless you're working tomorrow.
@Maddog0057 Viper ROM has working Wi-Fi calling. InsertCoin (ICE now) and LeeDroid Wi-Fi calling didn't work for me
Nilsonf said:
@Maddog0057 Viper ROM has working Wi-Fi calling. InsertCoin (ICE now) and LeeDroid Wi-Fi calling didn't work for me
Click to expand...
Click to collapse
Yep exactly the same with me. Currently on Viper at the moment until wifi calling is fixed

Categories

Resources