Database Develop

Trouble Flashing New CM N1 6.0 RC2 ROM

I have been trying to flash my Nexus one with a the new cyanogenmod 6.0 RC 2 ROM but for some reason doesn't work, and I have updated my Nexus one with the newest radio img, wipe the phone before loading the ROM and everything else but it still will not boot up. The boot animation always freezes up and get stuck in a loop. I have never had trouble flashing ROMs on my Nexus one until this one so i don't know what the problem could be so I was hoping some one here could, help me figure out what the problem could be.

Check the MD5 sum of your download file.

I'm sorry I'm still new to a lot of this stuff, what does MD5 mean.

Devyne_one said:
I'm sorry I'm still new to a lot of this stuff, what does MD5 mean.
Click to expand...
Click to collapse
Google it, you'd need the files necessary to check anyways.

I've heard somewhere that Cyanogen's ROMs don't like new HBOOT 0.35.0017. And i think you got it (new HBOOT) after you updated radio. Here is the instruction how to revert HBOOT to previous version http://forum.xda-developers.com/showthread.php?t=726258

Signing a ROM

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.

How to install Slim ICS properly?

I want to use slim ics. The last time I tried it it showed me no service. How do I properly install it? Any help appreciated.

If you are not on an ICS build then follow this guide http://forum.xda-developers.com/showthread.php?t=1494493
And when you are finished with this guide:
Put the slim ics 3.6 base and essentials on to your sdcard
format data
clear cache
clear dalvik cache
then flash the slim ics base
then flash the essentials
If the base flashed too quickly ie. under 5 seconds then flash it again before flashing essentials.
This is what I have done and its fine.
Hope this helps.

Hi, I exaclty did like shizz22 suggest and it works great for me.
Hope you'll be able to do it and have fun with it

Thanks guys. I will use that later. Now i'm very happy with ICSSGS. I will use your info later.

domdomrys said:
Thanks guys. I will use that later. Now i'm very happy with ICSSGS. I will use your info later.
Click to expand...
Click to collapse
Yeah I quite like ICSSGS. I'll probably go back when their new one is out.

No luck
I've been happy Slim ICS 3.4 user for about 2 months. Then checked that there is a 3.7 version and decided to upgrade. After download of base and I9000 essentials I've made an md5 check, which failed for both files. Considering that in the Android development topic people reported successful update to 3.7, I decided that the md5 published on the site must be wrong. To make sure it is not a download error, downloaded them several times but the md5 check failed everytime. Still decided to go and update and now I have softbricked my SGS. I'm a new user and don't have 10 posts to warn other users in the Slim ICS thread, so if someone here could do that, it would be great for the community. Now through the painful unbrick of my phone ..

The slim installer does not contain any modem
So upgrading from gb to slim requires you to flash a modem after the base+essential to get service

firenxe said:
The slim installer does not contain any modem
So upgrading from gb to slim requires you to flash a modem after the base+essential to get service
Click to expand...
Click to collapse
Is this advise for me or original poster? Also how does it help? Coming from gb rom you inevitably have a modem, so what gives?

silverchairbg said:
Is this advise for me or original poster? Also how does it help? Coming from gb rom you inevitably have a modem, so what gives?
Click to expand...
Click to collapse
Just follow this guide to get back to GB and onto and ICS rom http://forum.xda-developers.com/showthread.php?t=1494493 (I'm assuming you can't apologies if you can)
Then just download the .zip files and transfer it to your phone and flash accordingly. http://code.google.com/p/slimics37/downloads/list
I downloaded the base via my phone and got the Md5 error but I flashed it anyway (wasn't planning to but forgot about the error) and it worked fine. I downloaded the essentials through my computer though so that may have been the problem?

back in the game
shizz22 said:
Just follow this guide to get back to GB and onto and ICS rom http://forum.xda-developers.com/showthread.php?t=1494493 (I'm assuming you can't apologies if you can)
Then just download the .zip files and transfer it to your phone and flash accordingly. http://code.google.com/p/slimics37/downloads/list
I downloaded the base via my phone and got the Md5 error but I flashed it anyway (wasn't planning to but forgot about the error) and it worked fine. I downloaded the essentials through my computer though so that may have been the problem?
Click to expand...
Click to collapse
I know how to unbrick the SGS, at least from softbrick, thanks for your advise anyways. I just wanted to warn anybody else that might be absend-minded and does not check the md5s. But after all it seems you are right, although they did not match, after my unbrick I used the same files and this time it worked. Here's what I did: flashed essentials first, rebooted to recovery, formated system in mounts and storage, flashed base + essentials, rebooted. All fine and dandy, except, there is no modem as the original poster stated. Flashed one modem from the respective section here in XDA and I'm back in the game.

silverchairbg said:
I've been happy Slim ICS 3.4 user for about 2 months. Then checked that there is a 3.7 version and decided to upgrade. After download of base and I9000 essentials I've made an md5 check, which failed for both files. Considering that in the Android development topic people reported successful update to 3.7, I decided that the md5 published on the site must be wrong. To make sure it is not a download error, downloaded them several times but the md5 check failed everytime. Still decided to go and update and now I have softbricked my SGS. I'm a new user and don't have 10 posts to warn other users in the Slim ICS thread, so if someone here could do that, it would be great for the community. Now through the painful unbrick of my phone ..
Click to expand...
Click to collapse
I don't know what you did, but for me it worked the first time and I didn't have any md5 error. I downloaded it from the website, not via OTA.

OTA gave me the error. Still worked with the Base. Used the essentials from the website.

silverchairbg said:
I've been happy Slim ICS 3.4 user for about 2 months. Then checked that there is a 3.7 version and decided to upgrade. After download of base and I9000 essentials I've made an md5 check, which failed for both files. Considering that in the Android development topic people reported successful update to 3.7, I decided that the md5 published on the site must be wrong. To make sure it is not a download error, downloaded them several times but the md5 check failed everytime. Still decided to go and update and now I have softbricked my SGS. I'm a new user and don't have 10 posts to warn other users in the Slim ICS thread, so if someone here could do that, it would be great for the community. Now through the painful unbrick of my phone ..
Click to expand...
Click to collapse
i upgraded from 3.6 to 3.7 without problem. As it was recommended, I cleared my data and upgraded to 3.7 and restored some files from TB
Sent from ICS333

BlueFlame4 said:
I don't know what you did, but for me it worked the first time and I didn't have any md5 error. I downloaded it from the website, not via OTA.
Click to expand...
Click to collapse
hmmm... i got a md5 error in Update me app, but cwm gave no error and flashed it right away. base3., no errors were there in essentialsI9000
Sent from ICS333

[Q] Can't install some ROMs [Solved]

Hi all,
For the longest time I've been sporting a CM11 4.4.2 ROM and have wanted to change things up... problem is I can't! I tried updating my TWRP (it was quite a few versions behind before), I've tried installing 4.4.4 roms and 5.0 roms and I can't get about 80% of them to flash. The message that pops up in TWRP when I do have this problem is:
"This package is for devices: m7wls, m7spr; this devices is m7."
Click to expand...
Click to collapse
What I don't understand is that I am on sprint, and I do have the HTC One m7 and I am downloading ROMs from the HTC One Sprint section.... so what gives? I've been trying to find more information about this and I did find a post on another forum suggesting to unzip the rom file and change the updater-script to include m7 then rezip so I tried that and the above quoted message does go away but TWRP still doesn't let me flash the ROM.
Any help would be a appreciated.

Jaeryl said:
Hi all,
For the longest time I've been sporting a CM11 4.4.2 ROM and have wanted to change things up... problem is I can't! I tried updating my TWRP (it was quite a few versions behind before), I've tried installing 4.4.4 roms and 5.0 roms and I can't get about 80% of them to flash. The message that pops up in TWRP when I do have this problem is:
What I don't understand is that I am on sprint, and I do have the HTC One m7 and I am downloading ROMs from the HTC One Sprint section.... so what gives? I've been trying to find more information about this and I did find a post on another forum suggesting to unzip the rom file and change the updater-script to include m7 then rezip so I tried that and the above quoted message does go away but TWRP still doesn't let me flash the ROM.
Any help would be a appreciated.
Click to expand...
Click to collapse
You've probably flashed wrong TWRP. Make sure to flash the TWRP for m7wls.

I must have been installing the m7 specific version of twrp, I google'd twrp m7wls and installed that version and it worked without a hitch. Thanks lerenturk!

Happy to help you, Jaeryl.

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