Database Develop

Open season on Nexus Noob: Help me please

I'm inviting all you guys shoot me down for the noob i am.
I've search and i have found, I've read but only partially understood.
the background:
-Nexus one on vodafone epf30
-Downgraded to erd79 using fastboot (via Terminal in Mac-osx).
-Rotted and installed Amon recovery with sucess.
-At this stage i tried to install a variety of different pre rooted roms
- upgraded to frf91 OTA after giving up on trying to root froyo
I basically just would Froyo 2.2 rooted on nexus one.
I've found a variety of different methods and techs but haven't had any success i can downgrade again and again but each attempt i reach the update.zip stage and simply get a varification failed message.it's likley ive missed something here?!
I'm on mac and I'm sure I'm not having the update.zip.zip issue. ive checked and double checked, (that same issue caught me out before on symbian).
Does anyone dhave a simple deffinitive soloution or can point me in the right direction/
im aware this post will cause a shower of "search you noob SCUM!" style posts.
cheers in advance

http://forum.xda-developers.com/showthread.php?t=712983
Read from:
"By Popular Demand (Credit to lox):
Update.zip to flash with custom recovery"
Download, update using AmonRa's recovery, reboot to bootloader, flash new radio from any Froyo ROM thread in Development, reboot, enjoy.

hi, thanks for your reply. I'm pretty sure i have tried this method. if i down grade to erd79 can i apply this from there or should i go up to ere27 ? and does this require amons recovery or can it be done from a standard recovery?
Sorry im a symbian migrant :-( this is all new and exciting

ok so i down graded again to erd79 then rooted and installed AMONs recovery
installation of update.zip fails with the verification failed, is there something about AMONs custom recovery that im missing should what could be the cause for the verification to fail. im pretty sad now.
maybe there is a way to flash pre rooted Froyo directly using super boot?
maybe i need to be up

You've already installed a custom recovery. Basically you are done the whole rooting process.
No more need to downgrade or anything of the sort. Now you just go into recovery and flash what you want, no other steps.
Now you should be able to flash any custom rom meant for unlocked users.
You may be trying to flash the official 2.2 rom, try looking for a 2.2 for root users. Or try flashing CyanogenMod 6.

Are you sure you have Amon's Recovery because my buddy though he had it and he didnt which is why he couldnt install a rooted froyo ROM. Try http://forum.xda-developers.com/showthread.php?t=702191

ok ill give that rom a shot though i think my main issue could be the fact im using mac os x the downloader in safari automatically unzips .zip files so maybe recompressing the zip is causing the varification to fail.
ill have a go when im home and at a faster net connection work is like 0.2 up and down makes me feel ill!

Oh ok. I have a MAC aswell but I use google chrome for my browser.

OMG! mods lock this down! no need for anything more to be added!
MAC = FAIL
Windows+win
all you have to do is download using anyother browser DONT USE SAFARI!
and success will be yours! rebooting now to pre rooted custom frf91 WOOP!

Hey OP,
Actually you can still use Safari as it does unzip the file automatically but it also downloads the zip file so you end up with both. At least my MAC does this. MAC's are great, Safari on the other hand is junk so don't blame the whole computer for the browsers fault.

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.

[Q] Do i need to flash the EB1 file after flashing the new ROMs?

ok, this has been bugging me for a long time.
I rooted and flashed my HTC G1 Rogers a while ago from 1.5 to 2.2. Then i decided to try some other roms and i did not flash the EB1 File afterwards and kept getting a ROGERS logo and nothing else, then someone finally told me i need to flash the EB1 file too.
how come NO ONE and in NONE of the XDA Development ROM RELEASES does the instructions say "FLASH EB1" after flashing ROM????
this is just frustration for newbies since all they see is:
1. do a full wipe
2. flash my rom
3. flash gapps if you want
4. enable this, disable that, blah blah
-------> now, i want to flash to the newer 2.2.1 and try some other 2.2 roms, do i need to flash the EB1 file after i flash the ROM??? also, WHERE can i get the EB1 files from? i forgot where to get them, i need the 2.2. and 2.2.1 versions right?

It depends on which ROM you are using.
Some are made for the EB1 (mostly in the magic thread).
The rest you need to see if there is an EB1 port, a lot of them do not have 1 so you can not use it. You need to search the thread of the ROM that you want to use for the EB1 port and you need port that matches the build you are running.
For example the CM6 nightlies BCrook will usually make the port however there will only be a new EB1 port if it is needed - the old port will work work with the latest nightly until there is a kernel change(I think that is when a new port is required) and then BCrook makes a new port.
Using ROM manager for the nightlies is the easiest option.

[Q] can't flash with recovery. Odin OK.

Hi, I haven't find a post with this very same problem in a N7000 phone.
Like 2 years ago I had a problem with my Note, a friend helped me and that ended up in Rooting and ParanoidAndroid 2.x.
A few weeks ago I started feeling my phone quite slow, thought it was time for a fresh start.
I downloaded the latest ParanoidAndroid, 4.x, and tried to flash it using CWM and it failed, error status 7. So I tried with 2 or 3 more roms, same luck. So I started to look for this status 7 error. Found out that I could edit the file rom/meta-inf/com/google/android/updater-script to alter the assert lines. That didn't work either.
After reading a bit more I found out about twrp, lots of users had this very same problem and twrp had solved it for them. Well, that was frustrating, there wasn't any official release for the n7000 phone. I had found a post explaining how to compile it from a linux machine, post creator's posted an .img file but just as an example, it was outdated and I don't have a linux machine here with me nor the knowledge to feel confidence on compiling.
After trying some .tar.md5 flashes with ODIN, I got frustrated 'cause they were all working. But those roms are the least, most of the new ones (P.A. included, the one I got to fall in love with), come in .zip format. So, last try, started looking for some PA ROMs in .zip format. Again, no luck.
So, I'm running out of options. I was peacefuly hoping you could guide me in the right direction. I'm no guru but after reading for 2 straight days I think I'd be able to follow any sort of steps you'd suggest to me. I honestly feel confident enough to solve this issue.
Looking forward to your input people, I'm sure you're all more versed than me in the matter!
Thanks.

The rom you are trying to flash is a kitkat rom. To flash you will need newer version of cwm or twrp recovery. As recovery is merged with kernel in note, it's not possible to update without changing the kernel. So from your current pa recovery, flash raw r4 kernel. After that reboot into recovery. This should update the Cwm recovery to 6.0.4+. Now wipe data and cache and flash the new rom.

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