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!)

[Q] Rooting Questions; Effects and Consequences...

Sorry for the wall of text and for being a total noob and thank you for all your help !
So I've been researching all night (read the wiki to no avail too; so please don't simply direct me there) and I have some unanswered noob rooting questions questions and need general reassurance...
Basically I want is full and lasting root permissions on FRG83D 2.2.1 so I can remove system apps (twitter, amazon, etc...) through terminal commands and MAYBE a unlocked boot loader to flash a custom recovery image (Amon_RA) so I can make full nandroid backups.
1) It seems to me that unlocking the bootloader is a more flexible and permanent way to achieve root, as opposed to other '1-click' type methods in the face of firmware updates (2.3...), which would just disable root and it might not be re-achievable till another exploit is found whereas with an unlocked bootloader I can flash w/e I want?
2) Is it possible to enable root and use terminal on my n1 without some "superuser.apk" program? In order to do this would I use an insecure superboot and manually deploy SU?
3) How can I make a backup before rooting if I'm not rooted? I've been using my device for 8 months so there's a lot of stuff on there...
3a) If I can't make a full backup where can I find signed stock recovery images and boot images or updates zips so I can reflash them if I need to?
4) I believe if I superboot.img and leave everything (ROM and Recovery) stock will I still be able to receive and install OTA updates...?
4a) Can someone explain the difference between himem with updated wifi driver and not? I think himem removes permanent virtual address mapping so memory can be used for running applications. Asides from having more memory what are the tangible benefits or downsides to this? Would it make the system faster?Would I be able to multitask more apps before the system quits some because of lacking resources? Would the use of this extra memory inhibit system processes because there is no longer its own personal memory map?
4b) Will installing OTA updates remove root permission? If so, would simply flashing superboot.img re-grant me those permissions? But it would seem I need an updated superboot.img for the appropriate newer build(?). Is the development of superboot images still active and timely?
5) How important are OTAs and the stock recovery image? It would seem if I'm going to do any system moding (even just removing twitter/amazon) I should have a full and function Nandroid backup and would therefor need a custom recovery image- at the sake of missing OTAs (not important mainly because applying them would disable root etc anyway?)?
6) With root permissions and stock everything do I have to worry about manual baseband and radio updates? What about with a custom recovery image?
7) Apps2SD+ doesn't work with stock roms period and I would need a compatible custom rom?
Thanks again.

actually you can flash a recovery image without unlocking boot loader
1. Unlocking bootloader voids warranty and it is the official way to offer you the ability to install third-party roms.
You may get root without unlocking bootloader if you're using an old build. I think there are ways to root frg91 and frg83 without unlocking boot loader), then after you get root, you flash a recovery image, and then install whichever Rom you like. Don't bother with those official release, there will always be someone to release a rooted 2.3 rom.
2. not sure but from security's point of view it's better to have super user GUI program, because not all applications should get root
3. don't know sorry
4. Yes, there are lots of people revert back to stock ROM just for getting next OTA.
4a. I personally have never ran out of memory on my Nexus One, I do want to multi task as much as possible, however no matter how I set low mem killer, Android still automatically kills apps according to oom value (or something like that)
4b. If you get a successful OTA then definitely root is removed, and probably your recovery will revert to stock recovery too, thus you have to re-root..
5. I'd suggest to wait for someone to mod OTA 2.3 to make it rooted, then you flash the rom through recovery.
6. You can freely upgrade baseband (it's radio, the same thing) when you have a custom recovery.
7. There are mainly two ways to App2SD, one is Froyo implementation which works with stock Froyo rom, another way is to use App2Ext which requires root.

houzuoguo pretty much summed it up. I'll add what I can.
3) There is backup software in the market that can backup data without root, although it is not as powerful or thorough as the apps that require root.
3a) You can go back to a stock ROM. I believe there is a sticky round here of ROMs that has some stock ROMs in it. I know someone with a N1 that flashed a CM ROM, didn't like it, flashed a stock ROM, and got the OTA afterwards.
5) Even before an OTA is pushed there are ROMs floating around with the latest and greatest. After the OTAs are pushed you see a lot of very good, stable ROMs based off of them with all features working properly. You can do more with the custom ROMs and recovery images than you could ever do with the stock stuff.
7) DarkTremor's Apps2SD script will not only give you better A2SD than what is built into Froyo but it will give you a few more very useful terminal commands that I can't live without. Good stuff.

hi everyone! i just had my nexus one. i bought it from someone and i don't know if it's already rooted or not. Im already on FRG83D 2.2.1.
1.How do I know that my fone is already rooted?
2.Where can i download the stock ROM just in case the fone crashes and i want to revert?

proteus665 said:
hi everyone! i just had my nexus one. i bought it from someone and i don't know if it's already rooted or not. Im already on FRG83D 2.2.1.
1.How do I know that my fone is already rooted?
2.Where can i download the stock ROM just in case the fone crashes and i want to revert?
Click to expand...
Click to collapse
1. Check if there's application named 'superuser'. Or install any terminal emulator; run it, type 'su'.
**Please make your own thread next time.....

LFact said:
**Please make your own thread next time.....
Click to expand...
Click to collapse
Why?
Sent from my Nexus One using XDA App

Thanks guy!
I think I'm going to superoneclick to get root; back up with titanium and remove the system apps I don't want.
From there I'll be able to flash a custom recovery if I want to get more custom.
I'm probably going to wait till 2.3 comes out cause it's right around the corner; Or did they fix the superoneclick exploit in 2.3...?
Also, doesn't Apps2ext require a custom rom that supports it? i.e. it wouldn't work if I had root and was running a stock rom anyway?

[Q] Rooting Streak 7 WiFi

I'd posted a few questions I have on customizing my Streak 7, but have continued looking for information from other sources as well. I'm finding a number of "How to Root" guides, but I can't tell for sure which would work on my Streak and which wouldn't because the version/build numbers don't seem to be matching.
The unit I have is a WiFi only unit I purchased thru Amazon. It has Android version number 2.2.2, Kernel 2.6.32.9 and Build 15799.
* Most of the instructs I've found appear to apply to units that came with 2.2.1, and are either "Pre-OTA Rooted Stock ROM," "Pre-OTA Unrooted Stock ROM" and "Unrooted OTA Stock ROM." Since my unit came with 2.2.2 already installed, it doesn't sound like it would fit into the "Pre-OTA" categories, but since it didn't get an OTA upgrade, it doesn't look like it would fit in the "Unrooted OTA Stock ROM" option either. Am I misunderstanding the different classifcations? If not, does anyone know where instructions for rooting Streak 7 that came with 2.2.2 already installed?
* The primary reason I want to root the unit is so I can get rid of some unwanted pre-installed programs and so (hopefully) so I can assign default browser and email programs to the buttons on the "email/app list/browser" widget at the bottom centre of the Home screen. Once I have done those things, is it possible to then re-root it? Or will it just stay unrooted until the next time the unit is upgraded? If/when there's another upgrading to the Android version, will the programs I deleted still be deleted, or will I need to do that again?
Thank you for any assistance you can offer!
Kriselda Jarsaxa

You should make a nandroid dump, all the previous roms are modified nandroid dumps.
Also if you somehow delete something important you can recover it without having to contact dell

get fastboot working and flash clockworkmod recovery. Dj_steves rom is based off 2.2.2 and has all the crap removed as well as some kernel goodness. 2.2.2 has yet to be rooted manually. you have too flash one of the pre rooted roms. good luck

[Q] OS upgrade and root questions

I am N1 newbie but not Android newbie - have been using rooted Droid Incredible as my "main" phone for several months.
I just purchased officially unlocked N1 that is currently activated on prepaid T-Mobile account in USA and in future it will be used on my vacation in Europe.
Phone came with OS v. 2.2
I read a lot and things are sure different for N1 comparing to DInc. For DInc there was just one OS update and just one way to root it. For N1 its almost too much of a good thing for someone who hasn't followed it until now - 3 or 4 official OS updates and gazillion ways to root .
At this time I would like to root the phone (definitely, so that I can use third-party apps that require root access) and upgrade OS (possibly). I am not planning to use custom ROMs at this time but would like to try them in the future if rollback to stock ROM is possible.
As I already mentioned - my phone currently uses OS 2.2 and when I checked for an update via phone menu no updates were found. I was connected to internet at the time.
Questions:
1) From what I read some of the official ROMs between 2.2 and 2.3.4 (latest version) had problems. Are these versions even worth considering now that 2.3.4 is out?
2) Are there any known issues in 2.3.4 that are not present in 2.2?
3) What are advantages of going from 2.2 to 2.3.4?
4) Can I upgrade from 2.2 to 2.3.4 directly? All guides I found usually describe 2.2->2.2.1 etc - that is ROMs are updated consequently as they were released.
5) Should I a) update ROM to the latest and then root or b) first root 2.2 and then update ROM?
6) What are advantages of rooting with unlocking bootloader as opposed to rooting without unlocking bootloader?

Read the wiki. It is there to answer most of your ?s. Or use the search function.
If anything is still unclear ask about it and you will get help.
Sent from my Nexus One using XDA App

albundy2010 said:
Read the wiki. It is there to answer most of your ?s. Or use the search function.
If anything is still unclear ask about it and you will get help.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I read the WIKI and searched and it is still unclear.

1. 2.3.4 is the only version that currently has a fix for the recently found security hole that affects every version of Android other than 2.3.4. But this only affects non-https logins over an open wifi network, and people have to be scanning it.
2. I think the only major issue (depending on who you talk to) is the 2-3 second delay when you first answer a call before your microphone works. It has never really been a bother to me, and doesn't seem to affect everyone (maybe some just take longer to talk after they swipe, IDK).
3. There are a lot. Bugfixes, better UI, faster, support for video calling with GTalk (although obviously, only the back camera works, but you can still receive fine).
4. Almost, you can upgrade directly to 2.3.3. I don't think I have enough posts to add links, but a quick google search of "nexus one full gingerbread update" (without quotes) showed some results and the second one for me is how to manually update to Gingerbread. From there, you have to root the phone, because there are no hacks known to root 2.3.4 yet. This is where it gets a bit tricky because flashing a new update will kill your root. There are a number of guides on xda which can walk you through this part, because it is pretty detailed.
5. Kinda touched on with the above. Don't wait until you get to 2.3.4 until you root.
6. An unlocked bootloader makes things a lot easier. You can actually root your phone if it is running 2.3.4, because this allows you to load a custom recovery, which will give you access to the system partition of your phone. From there, you can add the files needed for root and remove the ones that will replace the recovery. The only benefit to keeping your bootloader unlocked is that it will keep its warranty through HTC, although HTC has been really good about replacing defective phones even if the bootloader is unlocked.

[Q] First Time Rooter, Gs6 SM-G920T, need help intresting problem cant find fix.

#1-"com.tmobile.pr.adapt (10001) has been granted superuser permissions for an interactive shell" pops up on my screen every 30 seconds on the bottom of my screen in a grey box.
#2- i also noticed that i can accept and recieve calls but i can not hear, nor can the other person hear me. if i use hangouts video call, skype, etc it works fine.
#3-i also tried to get rom manager to make a recovery and it says it needs to get CWD recovery to install a new software, the first thing we need to do is install a up to date version, we will begin that process now... etc.. then it says to get started you must first sset up a custom recovery, it gives two options a samsung galaxy s3 on metro pcs or a samsung previal 2 on boost mobile, or device not listed, when i click that it says "SM-G920T does not have an officially supported CWDR yet. Have you installed a CWD based recovery manually?" so im not sure what to do from there, or if i even need that. i have been a iphone user since day one went to android after reading up a lot on it, although rooting is quite different than jailbreaking it seems, i am incredibly excited to get started if i can get past these little problems and get started and figure everything out. ANY advice, or anwsers to these problems would be Greatly appreciated! thanks!
Also i went to dev options in settings and noticed the "OEM unlocking- allow the bootloader to be unlocker" was turned off, i dont know if this is necessary to root if i did something wrong by not turning it on or what, or if it may fix any problems above if i turn it on now. thanks!
I have a samsung Galaxy S6 (SM_G920T) . i Rooted and did not trip Knox, Although i did just remember that my fingerprint sensor is not working either.
Thank you guys so much this si a incredible forum i have spent hours and hours reading and researching before making this post i appreciate it so much!

#1 Freeze that ****. Use some root tool to freeze that T-mobile apk, seems u gave it root permissions at some point. I believe there are a lot of apps that you will want to do the same.
#2 ? No idea. Stock rom/kernel?
#3 What is this I don't even. Don't do that. Go to TWRP's official web, get your zeroflte (SM-GT920T) twrp and flash it via ODIN, or else get the recovery.img and use flashify. All that assuming you want a custom recovery.
You will need to unlock the bootloader if you are on 5.1.1. I believe locked will prevent changes or wiping anything on the OS partitions, even recovery (can someone confirm?)
I believe jailbraking and rooting should be pretty much similar, if not the same, as both target to grant the user root access to do whatever he pleases on the OS.
Welcome to android btw.

How did you root? Sounds like you used the modified sboot which causes no sounds in calls and nonfunctional fingerprint scanner. If so, flash back to stock and use a different rooting method. The rest, pretty much what the above poster stated

Root
I rooted using the version that I found the only one that works it seemed like, went to Odin put my phone In download mode and then put the boot loader download in BL and the. Put a something unikernel.sbin I believe, whatever the guide said also then it was done. I thought you couldn't use the twrp or custom recovery etc on tmobile one yet but I just read a thing about xtrestolite odex pure v2 which says it's for 5.1.1 and my model of phone but in the guide it says to root using CF auto root and a link there to it but the link doesn't have my phone on the list that the guide that clearly is my phone says to use I don't know if I'm missing something but I want to use it I understand most of it but I don't know if I need to unropt first and re root then use Odin and flash twrp that's supported on my phone then use that to recover the rom. Etc. The kernel that says is used in the guide is the same one I downloaded so do I need to remove it all then let it do that or?
Sorry if this didn't make sense I'm halfway there between confused and understood I have spent the last 10 hours reading and trying to figure this out though lol. Thanks guys!

Also
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?

Just flash the 5.1.1 firmware to return to stock. To root, flash unikernel with Odin. The other method you used was to not trip knox, but as you experienced has side effects. I had to Odin back to 5.1.1 myself. Can't have those issues

thanks!
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?

CjetOKC said:
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
Click to expand...
Click to collapse
Yes, flashing to 5.1.1 works exactly like that. You need to get the version for your model (very important on this one) and then simply place that file in the AP field of ODIN while the device is in recovery mode. It is normal for ODIN to freeze for 2 minutes while verifying. Make sure to use a MD5 checker tool on the firmware before flashing.

Rooting has historically required more technical savvy and balls than jailbreaking, but PingPong made rooting the S6 brain-dead simple. CF-Auto root is still pretty painless, but you must make sure you have the right zip for your device.
Anyhoo, the quickest & easiest way to restore phone calls & fingerprint scan is to use Odin to get back to bone stock.
Next, use PingPong to root. After rooting, "com.tmobile.pr.adapt" will ask for root access. That is T-Mobile's "phone home" app and sends info about your device (probably including root status). Deny it root access and make sure you check "Remember my choice", and it won't bother you again. You will not lose any functionality by denying it root, so terminate that crap.
Don't bother with rom manager. CWM is archaic. If you want a custom recovery, use TWRP. You can install TWRP either using Odin or TWRP Manager app (it's free).
Good luck and have fun with your S6

CjetOKC said:
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Click to expand...
Click to collapse
Are you still rooted? If so, and if you are experiencing the call audio issue, go flash AOU's kernel. He has made a kernel for the tmo s6. that should eliminate your call audio issue. The finger print scanner is the only issue with flashing his kernel. Also, I rooted with the modded sboot, his TWRP and kernel, and I didn't trip knox
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002