Database Develop

Updating with out rooting????????

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

Droid 1 stuck in bootloader and won't flash

Summary: Phone won't get past the bootloader, I've tried flashing .sbf's, update.zip's and updating the baseband with no luck.
Full Story: A couple weeks ago my 100% stock unrooted Droid 1 stopped getting a signal. It over 24 hours so I took it in to Verizon. They tried a factory reset, said it's out of warranty and told me to buy a new phone. How convenient for them, my contract ended in a week.
I decided to squeeze some more life out of it and started using it WiFi only. That lasted about a week until I restarted it and it hasn't been able to get past the bootloader since.
In it's current state it cannot boot Android at all, I only have access to the bootloader and recovery.
The first thing I tried was the Cyanogen Motorola Droid: Full Update Guide, but when I was ADB'ing it became apparent I had bigger issues. Commands like "su", "cp", and "chmod" were returning "not found".
Next I tried to flash a stock .sbf using RSDlite. It hangs at 99% with an error "Phone[0000] BP Pass Through Mode". The only info I could find about that was to try it on 32 bit WinXP, which I did, and it also failed.
So then I tried flashing older and rooted .sbf's since nothing else was working. It had the same "BP pass through mode" errors. One changed my boot animation from the white M logo to a blue skateboarding Android, but that's it.
The only .sbf's that are completing are recovery only. So far I've flashed SPRecovery, ClockworkRecovery and RZRecovery with no issues.
My next step was trying update.zips. signed-voles-FRG22D-Master_OTA.zip came back with the error:
Code:
assert failed: sholes.update_cdma_bp("/tmp/1rdl.bin", "/tmp/1bp.img")
E:Error in /sdcard/update.zip
(Status 7)
Google couldn't find anything useful about that error.
That error message made me think it had something to do with the baseband, so then I tried updating that with C_01.43.01P.zip and another .zip I found of the same version but a different file size. Both returned the same error listed above.
So now I don't know what else I can do. Did my Droid 1 really irreversibly brick itself for no reason?

Its very important you have the latest version of RSDlite when flashing an SBF. I struggled for about 3 hours to try and fix my phone when i thought I bricked it. I went from RSDlite 4.8, to 4.9 and suddenly the flash was successful. It was very much a head slap moment. See if that helps you.

I am using RSDlite 4.9, which I'm pretty sure is the latest version.

Troubleshooting "Installation aborted"

I have seen a lot of issues with installing the OTA and seeing installations that are aborted and having this message :
Assert failed apply_patch_check
To help troubleshoot the issue you need to post the full error message so someone can figure out what it is failing on.
But if you get that "Assert failed apply_patch_check" and in the parentheses it says "boot" and then letters and numbers, it means your kernel is different than .886. "But I am stock .886". No you are not, you installed a leaked update, your kernel is different than .886 and you cannot update with the OTA.
Hopefully 5.7.893 will follow and put most of us back on track and then 8.894 will put the rest except for some that installed some other strange versions floating out there.

Hi! Yea I'm having massive troubles here. I've downloaded around 10 different ROMs, and all but the Cyanogenmod 7.1.0.2 aborts the installation process. Even worse, I've removed the original ROM and cannot use anything computer-based (like flashtool, fastboot) because of this.
can I update/repair my kernel? (when I reboot I see the icon of the "freexperia" logo from a leftover installation).
So the only things I have are my boot-unlocked SE Xperia Arc S, and Clockworkmod (CWM-based recovery v5.0.2.6) and a possibility to transfer files to my sd card via usb cable.
I just bought my Arc S, but since the #"%"¤# SE bloatware I got massive slowdowns and mermory-related issues very fast, so I wanted to uninstall some stuff. Of course it led me down a path of insane troubles so now I just want back to stock ROM. I've already wasted 10 hours of my life on this so soon a new phone will be cheaper
Any help is HUGELY appreciated.

you cant boot into the bootloader? hold down the volume buttons and the power button. once you do that you can flash the stock fxz files and get your phone back.

[Q] Failed to verify whole-file signature

Hey everyone, I've had this problem for a while now and have no idea how to fix it.
I've tried to flash some ROMs on my tab since it's gotten laggy as of late.
I've gone to Clockwork and hit "Flash Clockwork recovery" but every time I do so it gives me the option of "Epic 4G" or "Galaxy S i9000"
This obviously doesn't seem right since the tab is neither of those.
Whenever I hit "reboot into recovery mode" I get taken to the Android System recovery screen and in red I get the message
"E: failed to verify whole-file signature.
E: signature verification failed.
Installation aborted."
Anyone know what I can do to fix this?

Not a single person here can help me?

First Step,
http://forum.xda-developers.com/showthread.php?t=812367
Prolly incompatible cwm/kernel/rommanager/root installed.

same problem
i am also getting the same Error message on my samsung galaxy s 4g t-mobile, i used superoneclick to root my phone. i have the superuser app on my phone so my phone is rooted. im trying to apply the audiophile framework update.zip file and i get this message can you help please thank you

There is a difference between rooting and having an alternate recovery installed.
Root gives you the ability to modify system files when running the ROM.
Custom recovery such as clockworkmod allow you to install unsigned files.
Should be easy to search out how to install a custom recovery.
Sent from my GT-I9000 using XDA App

Resolution
Use this foruma and re root the phone
100 % fix
I found this after umpteen failures..
http://forum.xda-developers.com/showthread.php?p=22555425
Ar318307 said:
Hey everyone, I've had this problem for a while now and have no idea how to fix it.
I've tried to flash some ROMs on my tab since it's gotten laggy as of late.
I've gone to Clockwork and hit "Flash Clockwork recovery" but every time I do so it gives me the option of "Epic 4G" or "Galaxy S i9000"
This obviously doesn't seem right since the tab is neither of those.
Whenever I hit "reboot into recovery mode" I get taken to the Android System recovery screen and in red I get the message
"E: failed to verify whole-file signature.
E: signature verification failed.
Installation aborted."
Anyone know what I can do to fix this?
Click to expand...
Click to collapse

how to accept bluetooth xfer
I have 13 of these tablets and cannot confirm bluetooth xfers on them. A popup comes on screen to do so, but disappears quickly with no button to confirm. I attempted to update with gapps on the recovery screen, and got a Failed to verify whole-file signature error. I know these have good RK3188 cpu's, I would like to get the up and running. suggestions?

Update bricked watch

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.