Database Develop

[Q] OTA update wont work?

Hi
newb here!
i have FRG33 build on my phone, and some time ago an OTA update came out that i couldn't install (i get "failed to verify whole-file signature" "signature verification failed" errors). i'm guessing the update is the 2.2.1 release - so how can i install it? i figure there's something i can drop on the sd card and install from there but i don't know what to search for or why this error happens at all (and google has been exceedingly unhelpful)
any help?
thanks!

Is your phone completely stock? Unrooted, stock recovery, stock rom...?

erm.. how can i tell? <,<
i bought it from a friend
i'm pretty sure it's at least rooted though, whatever that means (sudo-like access to phone i guess?) since i have an app called superuser and i downloaded lamppu (led flash as flashlight) which apparently needs root access to work (and it works)
if you need me to paste certain things from settings/options, i can do that

lavalove said:
erm.. how can i tell? <,<
i bought it from a friend
i'm pretty sure it's at least rooted though, whatever that means (sudo-like access to phone i guess?) since i have an app called superuser and i downloaded lamppu (led flash as flashlight) which apparently needs root access to work (and it works)
if you need me to paste certain things from settings/options, i can do that
Click to expand...
Click to collapse
Your phone has an unlocked bootloader if there is a padlock symbol on the first screen when you boot up (the one with the static x).
You can see what recovery is on the phone if you press and hold the volume down button while powering the phone on. This will take you to the Fastboot screen, and you will use the volume down button again to scroll down and select "Recovery" and then press the power button. That will either get you into the stock Android recovery (which will pretty much just be a /!\ symbol) or a custom recovery (which should have a nice text-based menu with options and such).
You can find out information about your ROM by going to Settings --> About phone, and scrolling down the bottom. If you would, post the various version numbers and settings and such.
If you are running another other than the stock recovery and a stock ROM, no OTA update will install for you.

aha, good stuff
here's what i got:
unlocked padlock symbol on boot
my recovery menu is "clockworkmod recovery 2.5.0.7"
android ver:
2.2
baseband version:
32.36.00.28U_4.04.00.12_7
kernel:
2.6.32.9-27237-gbe746fb
[email protected] #1
build#
FRG33
so presumably no OTA updates
how do i get my updates then? (and stop the "you have an update, update now!" pop-up which pops up even during video playback.. i mean, really?)

If you want to get the automatic updates, you'll have to revert back to a stock ROM and a stock recovery. There should be instructions for that in one of the stickied threads.

well, i assume there's a way to update manually as well?
so i guess my question is
a) how do i know what's this OTA update (i.e. where i can find a link for it)
b) how do i install it manually?
and/or i guess more generally -- is there a general intro tutorial to tinkering with android phones that also explains terminology etc (for instance, you said i need a stock ROM, but from http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Roms, FRG33 is a stock ROM, so am i misunderstanding terminology here? i.e. difference between ROM & build?)
thanks btw, you've been really helpful

Answer: SEARCH.
There must be at least 100 threads on this very topic. To update, you're either going to have to flash a new rom, or revert back to the original shipping rom. Search or read the wiki on how to do either.

Or disable signature checking on CW recovery and OTA updates will install fine.

GldRush98 said:
Answer: SEARCH.
There must be at least 100 threads on this very topic. To update, you're either going to have to flash a new rom, or revert back to the original shipping rom. Search or read the wiki on how to do either.
Click to expand...
Click to collapse
i've tried searching but it's a little difficult when i don't know any related terminology (hence the request for an intro guide of sorts). it's not like i'm posting here without doing nothing else, but google queries like site:xda-developers.com nexus one ota error frg33 for example didn't yield much. i did find a how-to-get-back-to-stock tutorial here but i am still looking for a tutorial to understand that tutorial as i have no experience with adb or fastboot, etc. (not to mention its last updated date is a year ago (although last edited date is fairly recent.. but i'm still wary) i'm learning though.
Rusty! said:
Or disable signature checking on CW recovery and OTA updates will install fine.
Click to expand...
Click to collapse
is there any risk to doing this? if not, this seems to be the simplest option so far, but doesn't a failed signature check usually signal an incompatibility/corruption?
thanks again for your help guys!

The reason it failed the check is because custom recoveries use test keys, and OTA updates use release keys. It's quite safe

If you poke around a little bit, you'll find stickies referencing you to the NexusOne wiki. The following are two guides on adb listed there:
[Newbie Guide] adb/fastboot/bootloader/android 101
[GUIDE] ADB For Beginners (Setup, Use, and More!)

Nexus One, go back like from the origin

Dears,
I have a Nexus One that some months back I root follow some steps on this forums. All work perfect. But now, to get more easy updates I think in go back to like when I buy with the official OS and can receive and install directly the OTA updates because now not use too much the rooted advantages.
Exist a method to do this?
In the phone information show Android version 2.3.3 baseband version 32.41.00.32U_5.08.00.04 and Build number GRI40.
Any idea?
I already receive a OTA message to update to 2.3.4 but when say install the phone tell me that go to restart, after restart show me the Android System Recovery and a lot of options ( reboot, USB-ms..., etc, etc) and a error like not found one file (I not remember the name).
Is best unroot? Or exist any easy method to put the 2.3.4 (or latest version in the future) without need backup all the data, wait a lot to update, etc?
The OTA updates are simple and I never need backup the info before update.
Any help are welcome because Im lost :S
THANKS!

If I'm understanding you correctly. You want to go back to stock and receive updates through via google? If thats what you want to do.
Follow the instructions here. It will restore your phone to the original ROM it shipped with. Shortly after setting your phone back up you should receive updates fairly quickly. Last time I did it I was back up to current in a couple hours.

Thanks, but when say:
"Only if downgrading to stock builds older than FRG33, ONLY FOR AMOLED DEVICES - Revert HBOOT to older version.
******* WARNING - DOWNGRADING HBOOT ON SLCD DEVICE WILL BRICK IT !!! ******* EPF30 Attention - Amoled vs SLCD"
How I know what is my version of phone? I can know if is AMOLED?
Thanks!

If you use the FRG33 file it doesn't matter...
Just in-case you still want to know, you can check which screen you have by typing dmesg in a terminal emulator and scanning the results. AMOLED screen will show up as samsung_oled_panel SLCD will show up as something else...

Thanks!
Exist a easy method to get, for example now, the 2.3.4 version of Android without lost information, in simple steps for my Nexus One and without unroot the device?

Third option in this post, but without the first step:
http://forum.xda-developers.com/showpost.php?p=13909618&postcount=2

Thanks guys!, I already downgrade to 2.1.1 and update by OTA to 2.3.4... Now think in root again ajajajaja. But now is more easy using the recovery that I have installed, its OK?

Yes it's a lot easier to root using recovery...

One extra doubt: after start with 2.3.4 the phone not have any information (like new one), but I found on my Market that exist a list of all my already downloaded applications as "installed" but on the phone not found this applications. The sync are active, but these applicaton not are autoinstalled again on the phone automatically and show as installed (that prevent that I can install again...) Any idea?

[SOLVED] How do I root 2.2 to get to Honeycomb?

Upon every reboot, the Galaxy Tab appears to have wiped all data. It prompts me to setup the device. Apps I install are wiped out.
Q. How do I get the device onto Honeycomb Alpha 2?
or
Q. How do I get root on FroYo to get onto Honeycomb Alpha 2.5?
A coworker dumped this device on me. I've been working with Chaos67731, using his instructions to get this Galaxy Tab restored to stock. Here is a video (in 2x and sometime 20x) of that process: http://www.youtube.com/watch?v=5eNLh6wu0ZE. It was on some flavor of Honeycomb, probably a custom ROM, from an outside developer/consultant. From conversations with Chaos67731 it would appear that the recovery on the device is far from stock. After I reboot, the device prompts for setup and flashes "Force close" messages left and right. Chaos67731 mentioned something about "Fix permissions," but I'm not sure where to start with that. Do I need root access?
I attempted to temproot with Visionary+. No dice. (I tried V+ because it's how I temproot my HTC-G2 to run gfree to permroot)
I attempted to root using superoneclick. OS Version Check Failed. Running psneuter... FAILED.
I attempted to root using z4root. "...has stopped unexpectedly. Please try again."
Any and all help would be appreciated! I'm working mostly off adb on OSX at this point. I'm able to hop on Ubuntu 10.04 and WinVista if necessary.
Verizon Galaxy Tab 7-inch
Unsure what version of Android is installed
Hardware version: I800.0.3
Model SCH-I800
Firmware version 2.2 (this sounds discouraging)
Baseband S:I800.0.3V.EB24
Kernel 2.6.32.9 [email protected] #3
Build SCH-I800.DJ11
-- eta June 30, 2011, 3:30pm CT --
It looks like I have root access, but cannot execute root commands. Superuser.apk kicks an "unexpectedly quit" type error.

Use Super One Click. Honeycomb is Android 3.0-3.1 not 2.5. Also the Honeycomb port is still in Alpha and seeing how you don't really know what software version it is I don't know that I would really recommend you switching to it because a lot of stuff doesn't work. It takes some work to move around on it.

alforque said:
Upon every reboot, the Galaxy Tab appears to have wiped all data. It prompts me to setup the device. Apps I install are wiped out.
Q. How do I get the device onto Honeycomb A2?
or
Q. How do I get root on FroYo to get onto Honeycomb A2.5?
A coworker dumped this device on me. I've been working with Chaos67731, using his instructions to get this Galaxy Tab restored to stock. Here is a video (in 2x and sometime 20x) of that process: http://www.youtube.com/watch?v=5eNLh6wu0ZE. It was on some flavor of Honeycomb, probably a custom ROM, from an outside developer/consultant. From conversations with Chaos67731 it would appear that the recovery on the device is far from stock. After I reboot, the device prompts for setup and flashes "Force close" messages left and right. Chaos67731 mentioned something about "Fix permissions," but I'm not sure where to start with that. Do I need root access?
I attempted to temproot with Visionary+. No dice. (I tried V+ because it's how I temproot my HTC-G2 to run gfree to permroot)
I attempted to root using superoneclick. OS Version Check Failed. Running psneuter... FAILED.
I attempted to root using z4root. "...has stopped unexpectedly. Please try again."
Any and all help would be appreciated! I'm working mostly off adb on OSX at this point. I'm able to hop on Ubuntu 10.04 and WinVista if necessary.
Verizon Galaxy Tab 7-inch
Unsure what version of Android is installed
Hardware version: I800.0.3
Model SCH-I800
Firmware version 2.2 (this sounds discouraging)
Baseband S:I800.0.3V.EB24
Kernel 2.6.32.9 [email protected] #3
Build SCH-I800.DJ11
Click to expand...
Click to collapse
it's the verizon tab. so you need to download the samsung sch-i800 drivers, because the tab doesn't install them well, generally. then, run superoneclick, in psneuter mode, with usb debugging enabled. it'll get to a point where it looks like it's hung? it hasn't. leave it be. this takes longer to root for some odd reason. my impatience made me think it was unrootable, but then i had to walk away from the computer during a rooting attempt, and when i came back, it had gotten past the point where it usually 'hung' and was chugging right along. so yeah. be patient. lol.
as far as honeycomb goes, it's only in alpha mode. but once you're rooted, you can flash via the instructions found here: http://forum.xda-developers.com/showpost.php?p=14428575&postcount=718
or, you can run a custom FroYo mod called better than life, which is epic win. find that here: http://forum.xda-developers.com/showthread.php?t=1147277
and if you brick it, you can fix it with instructions found here: http://forum.xda-developers.com/showthread.php?t=1133590
good luck!

Thanks for the tips. I'm 90% there. I'm able to root, but I can't get root access. Perhaps that's for another thread.

i'm not really sure what you mean, that you can't get root access. if you're rooted, then use a root file explorer like root explorer, or es file manager.

New post about my current problem. When I try to run anything as root, I receive an error that Superuser has unexpectedly quit.

[Q] Having problems when trying to ROOT Moto G LTE x1040

Hi, I'm relatively new to this forum and I've been trying almost all day to root my phone...
First, I had problems trying to get a working recovery (they just crashed to random colors/or loaded fine and then rebooted like nothing happened). Tried with CWM Recovery but it seems this model is not supported atm, tried with TWRP v2.8.3.0 and also crashes... ATM the only custom recovery that has started without going haywire is TWRP v2.8.0.0 (at least for my phone).
I prefered using 'fastboot boot recovery.img' before 'flash' since it's the first time I'm trying to root a phone. The recovery mode starts okay and I also placed the UPDATE-SuperSU-v2.46.zip in the internal storage before hand. I try to install the .zip file and all goes well, no errors and a blue 'Successful' message. This is where the 'root' procedure fails. Since you can reboot or go home to check other stuff I just tried rebooting the first time and it asked me that I had a SuperSU in the device and that if I wanted to install it to have root. I obviously swiped to install it and it displayed for a split of a second the window from before and just shut down and rebooted...
I tried several other methods to try and root my phone after this failure, but none worked. I checked again if trying this procedure would serve a purpose but I got the same thing always. But since I saw the process so many times I could see for a moment a red line saying something like 'E: failed to copy su binary to /system/bin (...)' but couldn't read more because it was a split of a second there xD. I googled this weird error and I found that my /system is in read only state and not writtable... But to change it to writtable I need root too it seems <_<)
So, any help? I'm sorry if this long text makes someone just look away but I don't really know how to explain my problem in more simple words xD. Any help will be appreciated .
EDIT: Forgot to say that my phone has its bootloader unlocked already and it has USB Debugging enabled.
Moto G LTE x1040
System version (as my phone says) 21.31.1.peregrine.retla.retla.en.01 entcl
Build: KXB21.14-L1.56-1
OS: KitKat 4.4.4

Any help ?
Bump.

Bump. Tried with CF Root by Chainfire but no root gained =/ .

Wait you are in the wrong forum, this is for the second generation search for moto g 2013 all recoveries here are for different device

fburgos said:
Wait you are in the wrong forum, this is for the second generation search for moto g 2013 all recoveries here are for different device
Click to expand...
Click to collapse
I suppose that would be this one then? http://forum.xda-developers.com/moto-g
Thank you for the response, I'm going to repost this in that section, sorry for the mistake >.<

ERROR mount failed to mount /dev/block/mmcblk Op35 at /system: file exisst

mount failed to mount /dev/block/mmcblk Op35 at /system: file exists
The above is a error message i keep getting when i try to flash a system update zip file within TWRP.
PHONE HTC ONE
M7_UL PVT SHIP S-ON RH
HBOOT -1.61.0000
RADIO-4T 35.3218.16
OS 7.19.401.22
CID HTC---001 UK UNLOCKED
HISTORY
I factory reset my phone and then went on to try and root it and followed a couple of different methods using youtube vids after doing days of reading threads and instructions online here and on other forum sites.
:good: **Thanx to QBKING77 & MAX LEE for their complete step by step guides**:good:
Yet each time i used the root checker it kept saying i wasnt rooted.
It seemed to be the superuser binary being outdated and no solutions i found seemed to work.
So following instructions i wiped my Cache & Davik and unfortunately i accidentally formatted my phone. :crying:
This left me able to get into TWRP recovery but was stuck on HTC logo on white background.
After 2 days of trying to find the solution i was able to flash a signed RUU using "fastboot"
M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed
The above is the RUU i used which seems to work fine. it certainly got my phone back from what i believe was a bricked state or semi at least.
When i got my phone back to normal i was finally able to root my phone and all seemed fine.
Then the other day i received a notification saying that there was a new system update which i tried to install yet when i clicked "ok" I was taken to TWRP recovery. Now though i can find the new OTA update i get the above thread title message appear each time i try to flash the zip file.
I know i can leave my phone as it is but i really would like to know what the problem is so i wont have any problems
I know i can install the OTA file but would have to revert back to the stock recovery option to do so which i have read is possible which im loathe to do as i dont know if i can get back to the TWRP recovery and if i will loose the backup which is stored under it.
Im also concerned that i may end up back where i started if i try it.
So can anyone help me with a solution to how i can use TWRP to flash the update and solve this "MOUNT" problem.
Im not a real techy guy but i am fairly inteligent enough to use CMD and FASTBOOT etc...
so if you can help id really appreciate it.
Cheers
JJ