Related
Hi guys
I was wondering if there is a way to update my phone with out rooting..
I am not to keen on rooting and trying to flush a cooked rom..
i am looking for the latest vision of android as i am running 1.1 at the moment and it has no market
thanx for all the help
if you're doing an official rom, then yes, you can. search the interwebs for an official 1.5 link, and also grab the market activator program from google's code base. once you download the official 1.5 rom, rename it update.zip, put it on your sd card and reboot into recovery mode (home+power when the phone is off). when the triangle and disk screen comes up, push alt+s on the keyboard to apply the update. after its done, your phone will reboot. you will then be running "cupcake", which is 1.5.
after that, if your market still isnt working, install the activator and run it. your phone will reboot when its done and the market will be working.
kusotare said:
if you're doing an official rom, then yes, you can. search the interwebs for an official 1.5 link, and also grab the market activator program from google's code base. once you download the official 1.5 rom, rename it update.zip, put it on your sd card and reboot into recovery mode (home+power when the phone is off). when the triangle and disk screen comes up, push alt+s on the keyboard to apply the update. after its done, your phone will reboot. you will then be running "cupcake", which is 1.5.
after that, if your market still isnt working, install the activator and run it. your phone will reboot when its done and the market will be working.
Click to expand...
Click to collapse
thank you so much i was just about to get rid of this phone
kusotare said:
if you're doing an official rom, then yes, you can. search the interwebs for an official 1.5 link, and also grab the market activator program from google's code base. once you download the official 1.5 rom, rename it update.zip, put it on your sd card and reboot into recovery mode (home+power when the phone is off). when the triangle and disk screen comes up, push alt+s on the keyboard to apply the update. after its done, your phone will reboot. you will then be running "cupcake", which is 1.5.
after that, if your market still isnt working, install the activator and run it. your phone will reboot when its done and the market will be working.
Click to expand...
Click to collapse
could not update
when i get to the screen with the triangle and phone i push alt+s like you said then the screen comes up with a box and phone and progress bar and then goes back to triangle and phone
Mr wyngaard said:
could not update
when i get to the screen with the triangle and phone i push alt+s like you said then the screen comes up with a box and phone and progress bar and then goes back to triangle and phone
Click to expand...
Click to collapse
You saw a progress bar. Did it act like it was loading? Did it give you any message afterwards? Did it reboot a couple times or anything?
supremeteam256 said:
You saw a progress bar. Did it act like it was loading? Did it give you any message afterwards? Did it reboot a couple times or anything?
Click to expand...
Click to collapse
no reboot nothing. the progress bar was there for 1 or 2 seconds then just went back to the triangle with the ! in it and the phone under neath there was no massage and it just sat there doing nothing
Mr wyngaard said:
no reboot nothing. the progress bar was there for 1 or 2 seconds then just went back to the triangle with the ! in it and the phone under neath there was no massage and it just sat there doing nothing
Click to expand...
Click to collapse
Is your card formated to fat32?
no i will try that now
thanks
no luck still
I pressed alt+L and it came up with a screen with righting thats says
installing from sdcard...
finding update package...
opening update package...
verifying update package...
E:No signature(413 files)
E:verification aborted
what does this mean please help me
you probably downloaded an "unsigned" update somewhere, hence the no signature. make sure your update is signed.
You are trying to install the official cupcake rom from t mobile right? Are you sure you grabbed the official one.
i had the same trouble when i did mine. for me tho it was that i named the file update zip. but then i saw if i just named it update the ".zip" was put there automatically. i just named it update and put it in the 1st postion in my sd card and it worked. good luck.
^^^Yea thats why its good to have your computer show file extensions.
HI guys
yip it was named correctly.
i live in south Africa and my service provider is MTN do you think that could be the problem
where would i get the right update for my phone!!!!1
i found this link but i cant open it
it gives me a error can some one try it plz
https://android.clients.google.com/updates/partner/signed-kila-ota-148830.de6a94ca.zip
ok so i found a cupcake file downloaded is and it was not signed so would not up date
busy downloading a new one now says it is signed only time will tell here is the link to the signed one
http://code.google.com/p/android-ro...=signed-kila-ota-148830.de6a94ca.zip&can=2&q=
this should be the us cupcake update
So I did a "checkin" tonight to see if I could get a OTA and I got one! I am running a rooted phone with 2.2 on it and FRF50.
I clicked "restart and install" on my phone and it took me to a bootloader-type menu and it said failed.
Any ideas? Now the update doesn't show up anymore either...
download the full update and install that "insert link here"
I have the same problem... I downloaded the update, then I chose to install it and the update hanged to a screen with a android and an exclamation mark.
I have a rooted nexus 1 that runs 2.1-update1 (ERE27).
What do you mean by "download the full update"?
Can you post a link?
i'm having same issue.. its because we are rooted w/ custom recovery.
I don't think it's the boot loader...
At the screen with the android and the exclamation mark, I pressed the power and up buttons at the same time and I found these messages:
Code:
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/lib/modules/bcm4329.ko", [some really long string], [another really long string])
E:Error in /cache/signed-passion-FRF91-from-ERE27.e410116a.zip
(Status 7)
Installation aborted.
This is because I changed the wifi firmware to enable tethering.
I will try to restore the default bcm4329.ko and try again.
If anybody has anything to suggest, he is more than welcome
If you're running a custom recovery, you need the repackaged zip. Check the dev forum.
I don't know what a custom recovery is!
I have only rooted my phone without paying much attention (I was just typing some commands back then).
I restored my N1 to its original shipping state using this guide: (I can't post links, so just search in google for "Restore your Nexus One to its Original Shipping Image" and the first result is the one I used).
Then my nexus redownloaded the update, and it was applied successfully.
Perhaps it was an overkill to wipe everything to apply the update but it wasn't neccessary for me to keep everything I had in my phone!
Cheers!
So I purchased a used G1 and I knew it has some software issues. I have no idea what version OS or anything is on this phone. Issue is it will not boot up into the OS. After researching (I am new to android) I have found what it can and what I cant get it to do. I can get into recovery mode no problem and after an ALT-L I see "Android System Recovery <2e>". The phone usually boots into this mode straight away, or I can hold home+power and it will enter the mode. Tried doing a "wipe data/factory reset" but nothing changes. If I reboot the phone and hold "back" I would expect it to enter Fastboot mode where I could do stuff. Instead I see the "rainbow screen" very briefly and then a message saying that if I want to restore factory setttings press send, otherwise hit any other key to cancel. No matter what I press nothing happens and I have to pull battery. I can only get into this mode every now and then. It seems pretty finicky about getting into it, and again no options when I do. Finally the camera+power to get into the bootloader does nothing. I can get the PC to see the phone when in recovery mode. It showed up as a mass storage device and i got that changed over to "Android Phone" by installing the SDK drivers.
Is there anything I can do on the recovery screen? That is the only thing that consistently works. I have tried a few update.zip files (various OTA updates I downloaded) but I either get a "No signature" error or it starts installing and then immediately get an "Installation aborted".
Any help to get this up and running would be appreciated. Hopefully its not just useless. For now an OEM 1.5 build is really all a i need. I can worry about updating/rooting later.
Download dream.nbh and format your sd card then place the dream onto ur sd card reboot holding home+cam button and let it do its magic that's how I fixed mine I'm sure if you go to the htc site you will find all the files u need just do a bit more research before trying this
Sent from my HTC Magic/Dream using XDA App
I mentioned in my original post that the camera+power button to enter bootloader mode does not do anything. I have already researched solutions, but it only seems I have access to the recovery mode screen. What can be done from there to assist with this issue (if anything)?
Download and flash the files from here http://developer.htc.com/adp.html (ota radio and system image) rename them update and flash them one at a time
Sent from my HTC Magic/Dream using XDA App
As for the no sig error just do some reasarch on adb shell and flash clockworkmod recovery from there its easy once u do some searching.....dw a couple of weeks ago I was you lol it'll pan out ok the people round here are really helpful
Sent from my HTC Magic/Dream using XDA App
Does this require adb? I have not been successful in making my pc get an adb connection. When in recovery mode the phones shows up on my pc and I got it to show up as android, but "adb devices" does not show anything listed. Everything referencing adb says it needs USB Debugging enabled, but I cant do that I cant get into the OS to enable. I dont seem to be able to enter fastboot mode either (see original post).
Download the radio and recovery image format sd card rename the ota radio update.zip boot into recovery and select apply update from sd card one you have that done delete the update.zip and then place the recovery image on sd card but rename update.zip and do the same....should work for ya
Sent from my HTC Magic/Dream using XDA App
When trying to update the radio files (tried all 3 versions on the download page) I get the "E: No signature (5 files)" error. Can I generate a valid signature for the files?
its worth a try lol if that dont work then i really dont know whats wrong lol
So far I have tried the following files:
The following pass verification and I get to the "Installing update..." but I then instantly get an "Installation Aborted". No other error message as to why:
signed-kila-CRC1-from-CRB43-FIX.7ca4a1d7.zip
signed-kila-DRC83-from-CRC1.c41b93c1.zip
signed-kila-ota-148830.de6a94ca.zip
signed-PLAT-RC33-from-RC30.zip
signed-RC30-from-RC29-fat.1582cace.zip
The following I get a "No Signature" error:
signed-dream_gfh-ota-147201.6d1386de.zip
ota-radio-2_22_19_26I.zip
ota-radio-1_22_12_29.zip
ota-radio-1_22_14_11.zip
I did a Wipe data and Cache before each update.zip attempt and this was using the "Android system recovery <2e>" screen.
Ideas? I will look and see if I can add a signature to the radio files.
dont spose u flashed the recovery with clockworkmod recovery 2.5.0.7
too short
I have not been successful flashing anything to the phone so far. All this was done via the "Android system recovery <2e>".
I signed the radio files myself, but they came out identical and same issues occurred. No idea what the "No signature" error is. Seems like a bunch of people get it on the forums, but no solutions. No idea why the good updates suddenly abort.
forum.xda-developers.com/showpost.php?p=4647751&postcount=1
Unfortunatly that seems to require fastboot, adp, or a rooted phone. I tried installing another SPL and I keep getting the "No Signature" error.
wow man your having a tough ass time lol ill keep researching for ya
i think your home button maybe stuck lol
far to short
You know thats not a bad idea. It does actually boot into recovery mode without holding the home button like you are meant to. Would holding home when powering on prevent the boot loader from starting if I hold the camera button?
on my g1 if i hold home power and cam buttons i get the bootloader/fastboot menu
So I ordered a new battery for it today too. The phone does not seem to work too long without being plugged in. Maybe that will help.
I also managed to capture some pictures of the screens I have, so maybe that will assist people with diagnosing the issue.
The first is the rainbow screen I get when holding back on a reboot. It flashes for 1 second or so and then displays the white screen with blue text. The last pic is the recovery menu I have access to.
It looks like this is a fully stock phone, no flashes. I am going to keep trying to get into that bootloader screen. Getting into the rainbow screen works once every 20 tries or so. Maybe the bootloader is similar. Hitting send on the white screen does nothing and requires a battery pull to reset phone.
how long can you stay in the coloured menu for ?????? also what happens if you stay there like what options do you get???
Hi everyone,
I seem to have nothing but trouble when it comes to installing OTA updates for my Gear Live, and am wondering if anyone can help me.
It all started when the Android 5.1.1 update notification arrived on my Gear Live some time ago. I eagerly installed it, and expected it to install without any problems. Unfortunately, the update reached around 30%, before displaying the Android mascot with a red exclamation mark. I managed to restart the watch, and re-downloaded and installed the update. The same thing happened, except, it was stuck in a boot loop :crying:
I contacted Samsung Australia who took the watch in for repairs (it took them 4 weeks). I was pretty happy to see the watch working again, and running the 5.1.1 update.
Just yesterday, I received a notification that an update is ready to be installed. I swiped and hit install. The watch rebooted, and began the installation. Again, reaching 30% before failing and displaying the Android mascot with the red exclamation mark. I am yet again stuck in a boot loop. I managed to tap the Android mascot, which brought up the Android System Recovery. It said
"Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!"
I have cleared the cache, and have wiped the data through recovery. This seems to allow the watch to boot up, however, the process repeats itself when I try to update it again.
Does anyone know why the update would be failing, especially after it has already been repaired by Samsung, and how I can fix it myself (I don't really want to be without a watch again for 4 weeks)?
Thanks,
Tim
Did you try the live restore tool? (read the whole thread)
Brendo said:
Did you try the live restore tool? (read the whole thread)
Click to expand...
Click to collapse
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Verifying current system...
"/system/priv-app/ClockworkHomeGoogle/ClockworkHomeGoogle.apk" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
Click to expand...
Click to collapse
tims1710 said:
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Click to expand...
Click to collapse
Try a different usb cable? (ie official, not a cheap one)
My watch always took a few goes to get detected by adb
tims1710 said:
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Click to expand...
Click to collapse
I had that exact error yesterday when I was trying to install new OTA update. I flashed back to KMV78Y(from live restore tool v2) Don't use v3 it has corrupted file and breaks bluetooth.
Try to manually flash using fastboot. I wouldn't recommend trying to flash recovery partition from live restore tool since you can end up with a broken OTA and broken adb sideload. Also, don't try to flash TWRP into recovery partition. Loading it into ram memory is fine though.
Anyways, to manually flash using fastboot, you need to open console and go to directory of Gear live restore tool. Make sure your watch is in bootloader mode, not recovery. Type fastboot flash boot 78Yboot.img and then fastboot flash system 78Ysystem.img Do factory reset just in-case and upgrade your way up to latest firmware.
Just craked open a new CCGTV (?) that shipped with qts1.200625.002.
It's been trying to update to qts1.210311.005, downloads and verifies fine, but then errors out during reboot and recovery (Android robot exclaimation mark). It then goes on to boot the existing FW fine.
Is there any way to check what the issue is? A log or something that I can access via a computer or file browser?
I'm experiencing the same issue, except I don't get the Android robot screen.
The Update downloads, device reboots, installation progress bar completes, device reboots, home screen, screen with update error "Can't install update. Oops, something went wrong".
Could someone help? Any suggestions?
Fwiw I got to my recovery logs by pressing the reset button on the dead robot screen. That indicated a hardware issue (cannot verify vendor partition or something), and so an RMA later and I have a working dongle.