hello, i am looking for this file, as it is no longer available on
http://android.clients.google.com/updates/signed-CRB17-from-TMI-RC9-eu.17667e06.zip
if you have a local copy, please contact me on priv...
thanks a lot!
http://www.flyupload.com/?fid=504814219
there it is
HTC Magic with CRA71C
Hi,
I'm from Germany and I just discovered that my HTC Magic didn't get any OTA-Updates because of dev-build CRA71C. In a german developer forum I was redirected to this post, and I only have one question:
can you please post this zip again?
Or sent it via e-mail?
Many thanks in advance!
Google was my friend : http://android.lucidrem.us/_fd.php?file=files/jesusfreke/EUR/signed/signed-CRB17-from-TMI-RC9-eu.17667e06.zip
Mirror : http://forall.ch/WordPress/download/6/
https://www.digital-bit.ch/g1devel/signed-CRB17-from-TMI-RC9-eu.17667e06.zip
OTA Updates
vache said:
Google was my friend : http://android.lucidrem.us/_fd.php?file=files/jesusfreke/EUR/signed/signed-CRB17-from-TMI-RC9-eu.17667e06.zip
Mirror : http://forall.ch/WordPress/download/6/
https://www.digital-bit.ch/g1devel/signed-CRB17-from-TMI-RC9-eu.17667e06.zip
Click to expand...
Click to collapse
ya beat me to it:
http://android.lucidrem.us/_fd.php?...ned/signed-CRB17-from-TMI-RC9-eu.17667e06.zip
for some reason i also have:
http://android.lucidrem.us/_fd.php?...ned-kila_eu-CRC1-from-CRB43-FIX2.1c36f92b.zip
but not the one in between
Many thanks to both of you.
Unfortunately it didn't work. As far as I know, I have to copy the zip, rename it to "update.zip" and then restart my Magic and "apply sdcard:update.zip"
It starts opening it but then says
E:no signature (337 files)
E:verification failed
Installation aborted
Any idea?
U can try to sign again the zip file.
Pardon, but what exactly do you mean?
(I'm just a stupid Android-User )
I'm doing it for you, i'll post a link soon.
Edit : Ok, try with this update. http://shoobee.eu/android/CRB17-from-TMI-RC9-eu.zip
Thanks a lot.
Now it is verified, but I get a failure. It says something like
"Failure at line 1:
assert file_contains ("SSYSTEM:build.prop".... bla bla bla
So I guess this one didn't work for me, right?
Could you give the complet error log plz ?
E:Failure at line1:
assert file_contains("SYSTEM:build.prop","ro.build.fingerprint=tmeu/kila_eu/dream/trout:1.1/TMI-RC9/128600:user/ota-rel-keys,release-keys") == "true" || file_contains("SYSTEM:build.prop","ro.build.fingerprint=tmeu/kila_eu/dream/trouInstallation aborted.
That's it.
Wrong File?!?
nicorola said:
Many thanks to both of you.
Unfortunately it didn't work. As far as I know, I have to copy the zip, rename it to "update.zip" and then restart my Magic and "apply sdcard:update.zip"
It starts opening it but then says
E:no signature (337 files)
E:verification failed
Installation aborted
Any idea?
Click to expand...
Click to collapse
why does this sound like you are trying to apply an OTA update to a root'd phone?!? first thing .. i don't know that this update will function on the magic .. this is a G1 update file
I don't know if my phone's rooted. I just know that I have a HTC Magic with prerelease version CRA71C, and that I have to get rid of it to get future OTA updates.
HTC Magic
nicorola said:
I don't know if my phone's rooted. I just know that I have a HTC Magic with prerelease version CRA71C, and that I have to get rid of it to get future OTA updates.
Click to expand...
Click to collapse
yea .. you're looking for the wrong thing .. i googled that reference and it says that is the Dev version of HTC Magic .. check the Sapphire branch here on XDA .. the dream build is not going to help you much
http://forum.xda-developers.com/forumdisplay.php?f=493
Yeppp!!!
Now you can see why some are called Juniors and some are called Seniors here! Poor guy was wasting him time until Senior stepped in. We are all learning.
i've just put my phone old HTC G1 back to rc7(UK) as i'm selling it
and as soon as i put rc7 I got the updates OTA and applied that
but on reboot I found that my custom boot splash was still there with my name and stuff so i fixed that by rooting it again and replacing the splash1 and splash2 with UK t-mobile G1 logo
then I re-flashed again with RC7 and I'm not getting any updates
I found this website
http://android-dls.com/wiki/index.p...Mobile_.2A.2AUK.2A.2A_G1_Over_The_Air_Updates
with what looks like all the OTA updates and I've managed to put RC8 on and still not getting any OTA updates still
so I tried the next one on the list CRB17
then i get this error the same as the one mentioned before
Code:
E:Failure at line1:
assert file_contains("SYSTEM:build.prop","ro.build.finger print=tmeu/kila_eu/dream/trout:1.1/TMI-RC9/128600:user/ota-rel-keys,release-keys") == "true" || file_contains("SYSTEM:build.prop","ro.build.finger print=tmeu/kila_eu/dream/trouInstallation aborted
and i just don't know what to do now
encepencewktorejrece said:
hello, i am looking for this file, as it is no longer available on
http://android.clients.google.com/updates/signed-CRB17-from-TMI-RC9-eu.17667e06.zip
if you have a local copy, please contact me on priv...
thanks a lot!
Click to expand...
Click to collapse
What kind of phone do u have
I have a UK HTC/T-mobile G1 . its not a dev version ...afaik
i found the answer
code.google.com/u/jsymon/updates
it has all the updates just download 1 by 1 and rename to update.zip and flash
now rocking 1.6
Related
I realize this information is on the HTC website but I have seen alot of questions lately regarding these errors. I decided that maybe, just maybe it might help someone with an error when flashing a rom, radio or splash and they can't quite figure out what the error is referring to. I also figured that this might lighten the load that GSLEON3 has been seeing lately with all of the "HELP, I think I BRICKED my phone" threads that keep popping up. Maybe it will help and maybe it won't but I thought it might be worth a try. I'd like to say thanks to OLI, Jocky, all of the rom cookers, GSLEON3 and XDA. You people make this fun.
I hope this helps someone.
? ERROR [202, 204] : CONNECTION
? This error message will appear when the device is not connected to ActiveSync correctly. Make sure
you properly connect the device to the PC through ActiveSync before running RUU.
? ERROR [206] : MEMORY ALLOCATION
? ERROR [280] : UPDATE ERROR
? When you see any of these error messages, close other running programs on the computer and run RUU again.
? ERROR [208] : FILE OPEN
? ERROR [210] : FILE READ
? These error messages indicate that RUU lacks certain important files and cannot continue with the update. Please get the complete RUU package again.
? ERROR [212] : FILE CREATE
? ERROR [214] : FILE WRITE
? ERROR [222, 224] : DEVICE NOT RESPONDING
? These error messages will appear when remote access control has failed. Check the ActiveSync connection and try running RUU again.
? ERROR [220] : MAIN BATTERY POWER
? This error message will appear when the device's battery power is not sufficient. Although RUU will instruct you to plug in the AC adapter, it still has to make sure that your device has enough power to upgrade the radio. (Even when you plug in the AC adapter, the device is unable to charge the battery
when it is upgrading the radio).
? ERROR [238] : FILE READ
? This error message may appear when, for some unknown reason, the ROM image on the Mobile Device is corrupt. Download the whole RUU and try again.
? ERROR [240] : FILE OPEN
? When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again. Check that the contents of the folder is a KaiserCustomRUU.exe file and an RUUSigned.nbh file. If you put the os-new.nb file in by mistake instead of the .nbh, this is the error that shows up. Thanks ConfusedSTU.
? ERROR [242] : INVALID LANGUAGE
? ERROR [244] : INVALID MODEL ID
? ERROR [294] : INVALID VENDER ID
? ERROR [296] : UPGRADE ONLY
? One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.
? ERROR [246] : DEVICE NOT RESPONDING
? This error message indicates that RUU cannot start the update process. Please contact your service provider for assistance.
? ERROR [260] : UPDATE ERROR
? This error occurs when there is an "open port error" before upgrading the CE ROM image. Solution: You can reset the device and run RUU again. If you still encounter an "OPEN PORT ERROR" again, reset your computer and try again.
? ERROR [262] : UPDATE ERROR
? This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
? ERROR [300] : INVALID UPDATE TOOL
? This error message will appear when you use the incorrect RUU version to upgrade.
? ERROR [330] : ROM IMAGE ERROR
? This error message will appear when you use the incorrect RUU to upgrade and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version to upgrade.
Nice one mate, at leat this will give people who flash some idea what to do when or if they get errors flashing.
great find thanks for posting this will be useful for everyone.
Obligatory "thank you" post.
haha ok ok mistake now i see the solutions xD!
edit...............
Thanks P1T.
Just to put one in laymans terms from real life experience:
ERROR 240
Check that the contents of the folder is a KaiserCustomRUU.exe file and an RUUSigned.nbh file. If you put the os-new.nb file in by mistake instead of the .nbh, this is the error that shows up!!
I thought everyone knew that these error codes were included in the .doc files that come with shipped ROMs (and removed within custom_ruu.exe).
Guess not Great post P1tater!
Confused Stu said:
Thanks P1T.
Just to put one in laymans terms from real life experience:
ERROR 240
Check that the contents of the folder is a KaiserCustomRUU.exe file and an RUUSigned.nbh file. If you put the os-new.nb file in by mistake instead of the .nbh, this is the error that shows up!!
Click to expand...
Click to collapse
I'll add this to the post. Thanks Stu.
_Alex_ said:
I thought everyone knew that these error codes were included in the .doc files that come with shipped ROMs (and removed within custom_ruu.exe).
Guess not Great post P1tater!
Click to expand...
Click to collapse
I thought so to but I have had to answer a couple of these lately and was hoping that this might help to clear a few things up.
Bump (keeping it on the first page) & +1 for sticky
Oh, i would change the name to start with "Flash error codes" or at least include that in the title.
RPG0 said:
Bump (keeping it on the first page) & +1 for sticky
Oh, i would change the name to start with "Flash error codes" or at least include that in the title.
Click to expand...
Click to collapse
I can make that change.
Thanks for the info pal
helpful! thankx
Wiki
Ported to the Wiki
http://wiki.xda-developers.com/index.php?pagename=RUU_Errors
Ta
Dave
Thanks dude. Great work. You put a lot of effort in this kind of handy things.
Oh, by the way, do you have a social live?
iXiR said:
Thanks dude. Great work. You put a lot of effort in this kind of handy things.
Oh, by the way, do you have a social live?
Click to expand...
Click to collapse
I Can't speak for P1, but nope, I work, go home, play with my Son and either relax in front of the Telly or play on my PC.
Everynow and again on a weekend I'm forced into meeting something called friends by my better half
Dave
DaveShaw said:
I Can't speak for P1, but nope, I work, go home, play with my Son and either relax in front of the Telly or play on my PC.
Everynow and again on a weekend I'm forced into meeting something called friends by my better half
Dave
Click to expand...
Click to collapse
That's similar to my own schedule. P1 got to have a secret in finding time for this kind of things
ERROR 200
I got this error 200 "get newer update utility" I am using windows vista 32 bit.
where can i get a newer update utility? thanks
I-mate JasJam upgrade error
hey guys no matter what i do even if i do a reset on the phone and restart the computer i keep getting the 260 error when doing the rom upgrade. i am using windows 7 and have had no errors with anything ever with it.
Any ideas?
Josh
rumjar86 said:
hey guys no matter what i do even if i do a reset on the phone and restart the computer i keep getting the 260 error when doing the rom upgrade. i am using windows 7 and have had no errors with anything ever with it.
Any ideas?
Josh
Click to expand...
Click to collapse
Try resetting the phone and the computer to make sure that no other processes are running. Then try putting phone into bootloader, and when sync'd try flashing from there.
Hello everybody.
I've scoured these forums for a few days now, in hope that I can resolve this very frustrating problem but, alas, I've failed in my mission and have had to resort to picking your brains. (sorry about that!)
I'm running Cyanogen mod 7 on my T-Mobile G2 GSM and so far the ROM has worked brilliantly. The only reason I'd like to change is because of the poor GPS. I've tried a patch and the command fix but both of them didn't work for me.
Anyway... When I boot into Clockwork mod recovery (and wipe all the necessary files) and try to load my new ROM, I'm presented with an error message similar to this:
------------------------------------
finding update package...
opening update package...
E:error in / [ROM NAME & LOCATION]
Install Aborted
------------------------------------
I've tried downloading the rom several times via different websites, tried different ROMs all together, followed every bit of advice I could muster on here, and even purchased a new memory card... Just in case.
It's really frustrating though because I have to use recovery to get Cyanogen back (I need it to tether or I have no internet at home!) and that takes so long each time.
As you can probably imagine, it's really frustrating .
Any help would be massively appreciated!
Thanks again,
Bacoon.
Bacoon said:
finding update package...
opening update package...
E:error in / [ROM NAME & LOCATION]
Install Aborted
Click to expand...
Click to collapse
on sdcard /mnt/sdcard/clockworkmod folder there is a log take a look at it
I think you have to flash a corresponding CWM by fastboot utility
Thank you for getting back to me!
There are 2 that I can see. Should i go for Recovery.log or Report.log?
It's also giving me lots of options to view it... Should I use html viewer? It seems like the only thing that'd work.
Cheers!
EDIT:
I used the HTML viewer on "Report.log" and it came up with a HUUUGE list. Anything in particular I should be looking for, mate?
Bacoon said:
Thank you for getting back to me!
There are 2 that I can see. Should i go for Recovery.log or Report.log?
It's also giving me lots of options to view it... Should I use html viewer? It seems like the only thing that'd work.
Cheers!
Click to expand...
Click to collapse
report.log is generated from cwm recovery menu to report them errors
It says open ROM Manager to repport the issue
recovery.log in a general log to describe CWM activity
I think easy way is to change to a CWM that will allow you to flash that ROM
(I can't tell you exactly because I don't have links)
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
to see/edit files use notepad or better Notepad++ that's a decent editor/viewer best Notepad replacement
I don't know give me a link to that log or better think to change CWM recovery...
alsnxpl Ancient
try CM 10.1
---------- Post added at 03:34 AM ---------- Previous post was at 03:29 AM ----------
Android_Number17 said:
try CM 10.1
Click to expand...
Click to collapse
By Mardon
"E:Error in /tmp/sideload/package.zip
(status 2)
Installation aborted."
what is that? what to do guys? help me please. im a newbie here.
-Samsung Pocket user.
JKevin02 said:
"E:Error in /tmp/sideload/package.zip
(status 2)
Installation aborted."
what is that? what to do guys? help me please. im a newbie here.
-Samsung Pocket user.
Click to expand...
Click to collapse
Nobody told you that use CWM for flashing ROMs?
nobody boss. this is my first time. how to use that? and where i can get that? please guide me. thanks.
First make sure you have a custom Recovery like ClockWorkMod or TWRP or else you would end up having a soft brick.
You made that zip or is it from a defined rom cook for your phone.?
Anyway the possible reasons of that problem are:-
1)signature missing
2)zip is broken
To get rid of the first problem
Check if the META-INF folder is present in the zip..if not then Sign the zip using zipsigner2 app or anyother zip signer packages you can find in xda.
If META-inf folder is present..go to Recovery and toggle signature verification and set to OFF..then try.
For second problem.
Either create a new zip then sign then flash.
Hopefully thats the problem you are asking about.Hoped i help
-Rik[Rittik]
First of all, wrong place
Secondly, why you posted it three times?
Then, from where did you download this ROM?
Hi, I read lots of posts here in xda on how to install custom ROM on my HTC Salsa, lot of times i felt bad as the posts always required my phone to be S-OFF. I couldn't find a nice and easy solution for this.
However somewhere i read that it is not mandatory to have S-OFF and which is when i just started experimenting on my phone.
I did unlock the bootloader from HTC dev . But i still have S-on.
I downloaded some *i9500 custom ROM and copied it to my downloads folder in sdcard. Tried to install the zip from sdcard from my CWM Recovery and it failed always. But then i thought that it could be the problem with image which i downloaded as it is not supported. So then i found one more post for HTC Salsa and downloaded the image from the link given in there.
Here is the link of that post : http://forum.xda-developers.com/show....php?t=2745185
Here is the link from where i downloaded the zip : http://download.androidarmv6.org/_builds/icong/
Here is the image which i downladed : cm-11-20140719-NIGHTLY-icong.zip
After getting into CWM Recovery i tried to install the same and at first it looked that it is going to install but in some time i get some error like
set_metadata_recursive.... error STATUS 7. INSTALLATION ABORTED.
Then i thought i was doing to wrong and as per some post .. i formatted all the /boot /system /sdcard ....partitions listed in CWM.
Now my sdcard is completely formatted .
After i copy my image there and try to install the same :
I get :
--Installing: /sdcard/cm-11-20140719-NIGHTLY-icong.zip
Finding update package...
Opening update package...
Installing update...
E: Error in .sdcard/cm-11-20140719-NIGHTLY-icong.zip
(Status 0)
Installation aborted.
I can't even reboot to my old ROM. .. Not sure if its lost completely. .. Need help urgently.
Please help me recover or reinstall any ROM just for my phone to come back to life again.
You have posted the issue in the right forum in your initial post. That is the right place for your concern. Please be patient and wait for one of the experts to respond.
Close thread
I missed this, was there an issue?
twizt3d said:
I missed this, was there an issue?
Click to expand...
Click to collapse
If anyone installs it, there is no way back at all AT&T doesn't release Odin files for the phone at all.
Sent from my SM-G955U using Tapatalk
FatalONEM8 said:
If anyone installs it, there is no way back at all AT&T doesn't release Odin files for the phone at all.
Click to expand...
Click to collapse
Ahh so it's the same thing listed in the 892 thread under the s8 (unbranded) forum. Bl2
Bump (sorry mods) new info!
Sent from my SM-G955U using Tapatalk
Downloading bra3 now. Pics and more to come.
Edit. Flashed fine, more to come.
Screenshots attached
twizt3d said:
Screenshots attached
Click to expand...
Click to collapse
That is great that we finally get Oreo for Active S8
norbarb said:
That is great that we finally get Oreo for Active S8
Click to expand...
Click to collapse
Agreed but I think the Odin files were the bigger find
The ARA1 to BRA3 link hangs for me, all others are ok.
Edit: Sorry for being impatient, I waited for the download and have successfully updated to 8.0!
New update available! BRB2! February patch!
Sent from my SM-G955U using Tapatalk
I am redownloading BRB2 now, but my first go around, the update from sd failed, and sideloading failed.
E3005 "/system/HWRDB/data/hwr_en_us.dat" has unexpected contents.
E:Error in /sideload/package.zip
(Status 7)
failed to open driver control: No such file or directory
E:ensure_path_unmounted failed to unmount /efs (device or resource busy)
Successfully verify for dmverity hash tree Installation aborted.#1
Edit, i was unable to complete this update tried several attempt all resulting in the above error
twizt3d said:
I am redownloading BRB2 now, but my first go around, the update from sd failed, and sideloading failed.
E3005 "/system/HWRDB/data/hwr_en_us.dat" has unexpected contents.
E:Error in /sideload/package.zip
(Status 7)
failed to open driver control: No such file or directory
E:ensure_path_unmounted failed to unmount /efs (device or resource busy)
Successfully verify for dmverity hash tree Installation aborted.#1
Edit, i was unable to complete this update tried several attempt all resulting in the above error
Click to expand...
Click to collapse
I was finally able to flash this successfully. The issue I had related to the Odin files when I was returning to ara1. Please see the updated post if you need to restore to ara1. Thanks to norbarb and fatalonem8 for assistance with that.
Okay I am a Newbie at this with a ATT Samsung S8 Active
is there a step bye step guidance for this ?
Thank you
Eric
Ericthepilot said:
Okay I am a Newbie at this with a ATT Samsung S8 Active
is there a step bye step guidance for this ?
Thank you
Eric
Click to expand...
Click to collapse
1. Download the update file. ( https://samsung.firmware.science/download?url=48974/1488/SS-G892AUCS2ARA1-to-U2BRB2-UP )
2. Place file on your SD card.
3. Reboot into recovery (hold bixby+Vol up + power)
4. Wait like 15 sec for recovery to boot, may look like it gives you an error but it boots.
5. Select install update from SD card, and select the file that you copied to the SD card.
6. Let it install, after that enjoy Oreo.
bugity said:
1. Download the update file. ( https://samsung.firmware.science/download?url=48974/1488/SS-G892AUCS2ARA1-to-U2BRB2-UP )
2. Place file on your SD card.
3. Reboot into recovery (hold bixby+Vol up + power)
4. Wait like 15 sec for recovery to boot, may look like it gives you an error but it boots.
5. Select install update from SD card, and select the file that you copied to the SD card.
6. Let it install, after that enjoy Oreo.
Click to expand...
Click to collapse
Hi does this Guide applicable to QL1?
or i should update to ARA first?
and 1 more question if i will update 4 File ARA1 will i loose my personal data?
vazovskiiii said:
Hi does this Guide applicable to QL1?
or i should update to ARA first?
and 1 more question if i will update 4 File ARA1 will i loose my personal data?
Click to expand...
Click to collapse
Yes, yes, and yes.
The last link in the OP will update you from QL1 to ARA1 if you need to. Probably better just to install through Odin tho.
You should be on 2ARA1 to update to BRB3, the latest link tells you what version it updates you from and to.
And installing an update.zip will erase your data usually, but there is a way to get around it by turning your phone off at a certain part during the update.
vazovskiiii said:
Hi does this Guide applicable to QL1?
or i should update to ARA first?
and 1 more question if i will update 4 File ARA1 will i loose my personal data?
Click to expand...
Click to collapse
You should update to ARA1, you won't lose data if you flash HOME_CSC. There's a new bypass method for the wipe that occurs during sideload https://pastebin.com/pNKQrfva
FatalONEM8 said:
Recently, we've been able to find Odin files for the G892A they are ARA1 and very new link is here: https://mega.nz/#!d3xxiZiK!63ekoH4Iif2z6MFZ6TJ-2IRcHSh8reO-xZD80KUVUOU
you will need that for these OTAs
Latest:https://samsung.firmware.science/download?url=48974/1488/SS-G892AUCS2ARA1-to-U2BRB2-UP
https://samsung.firmware.science/download?url=48974/1488/SS-G892AUCS2ARA1-to-U2BRA3-UP
https://samsung.firmware.science/download?url=48974/1488/SS-G892AUCS2AQL1-to-U2BRA3-UP
https://samsung.firmware.science/download?url=48974/1488/SS-G892AUCS2AQL1-to-S2ARA1-UP
These are the OTAs for Oreo, credit goes to @locajm for the Odin files and the OTA links norbarb.
Click to expand...
Click to collapse
Oops, still not used to XDA app ??
vazovskiiii said:
Hi does this Guide applicable to QL1?
or i should update to ARA first?
and 1 more question if i will update 4 File ARA1 will i loose my personal data?
Click to expand...
Click to collapse
You can use the ql1-bra3 ota, to skip ara1, but make sure you follow the guidelines to avoid the wipe.