I've just rooted my G1 on RC9 and have a rather annoying bug.. the market keeps auto downloading and installing all the apps i've uninstalled.. any ideas
that is wierd, never had that before
all i can suggest really is just to apply the update again, you shouldn't need to wipe either. and if that doesn't work, wipe and reflash it. and if THAT doesn't work D) try a different firmware like ADP, RC33 or the new Magic firmware when it's released
All sorted... took it back to store and they replaced it... rooted my new one and no repeat
Related
My wife and I both have a G1. I have had mine rooted for a week or so, updated to RC33 yesterday, and I rooted my wife's phone and updated last night...
Well, my wife's G1, after a reboot, gets to the Android screen (after 'T-Mobile G1' screen), and the android flashes. So I put her back to RC29 till I can get it figured out.
Just now, mine suddenly rebooted and is doing the same. There are no corrupt files, all were fresh. Install and root were followed step by step......HELP!
rc33
I would recommend wiping then go back to rc29 and then update from their to rc33 hope that helps
Did you have themes installed??
If yes, are they for RC-33?
You can not use any theme you like with RC-33.
An idea.
Hello there.
i have a nexus one from vodaphone and im sure you all know (ive only just found out) that the ROM on these devices has a problem installing updates to android and does not recieve OTA updates. i believe this is to do with vodaphone actually releasing these?
any who, i used the superoneclick Root application, worked like a charm.
so then i procede to download gingerbread rom but it does teh whole E: verification error.
so i search the internet a little and come across a post with a person with teh same problem, Fantastic i thought! i follow the steops but am cut at my first hurdle as it says i need to revert from teh Vodaphoen Rom to teh original google shipping rom, the problem is that i cant seem to download it, it never works and i dont know why the D/l is incredibly slow and sometimes never connects. this is from Shipped-roms.com
if any1 could assist me in reverting to the original shipping rom i can do teh rest and update to 2.3.3
Thanks for reading.
Horizon.
Root your phone, then install rom manager recovery. With this, you will be able to flash any rom you want.
SalsaForte said:
Root your phone, then install rom manager recovery. With this, you will be able to flash any rom you want.
Click to expand...
Click to collapse
ive installed the rom manager and installed the cyanogen room, how ever im still on 2.2.1 and the OTA wont update it just downloads then nothing happens. any idea?
Horizonspace said:
ive installed the rom manager and installed the cyanogen room, how ever im still on 2.2.1 and the OTA wont update it just downloads then nothing happens. any idea?
Click to expand...
Click to collapse
The OTA won't update automatically, you have to manually flash it. OTA will auto-update only from official version and authorized version. Anyway, why don't you flash CM7 RC4?
A few months ago, I loaded 2.3.6 firmware on phone. It is stock gingerbread with root from oden file all_in_one_odin_ep4d. Last week I received an OTA update. The update fails to load and leaves me at the screen with the white triangle with yellow exclamation point. I pulled the battery and rebooted. Today, the update came back. Still no go. I think the update is incompatible with the software on the phone.
Can someone tell me:
1. What is in the update? Is it going to remove root and allow Verizon to see that I 3rd party tether? Are they suddenly going to slap a tether package on my bill? Is it even worth installing?
2. If it’s not worth installing, can I tell my phone that I don’t want it by making it think that the update is already installed?
3. If the update is worth installing, should I wait for an oden install that contains the update or do I do something to the phone to allow it to receive the OTA update? If I do opt for the OTA what must I do to allow it to load?
Being somewhat novice when it comes to loading software on phones, is there a good FAQ out there that lists all the different loads, with what they contain and explanations of those components. Right now, voodoo, Peanut butter and jelly… buzzwords.
beavermjr said:
A few months ago, I loaded 2.3.6 firmware on phone. It is stock gingerbread with root from oden file all_in_one_odin_ep4d. Last week I received an OTA update. The update fails to load and leaves me at the screen with the white triangle with yellow exclamation point. I pulled the battery and rebooted. Today, the update came back. Still no go. I think the update is incompatible with the software on the phone.
Can someone tell me:
1. What is in the update? Is it going to remove root and allow Verizon to see that I 3rd party tether? Are they suddenly going to slap a tether package on my bill? Is it even worth installing?
2. If it’s not worth installing, can I tell my phone that I don’t want it by making it think that the update is already installed?
3. If the update is worth installing, should I wait for an oden install that contains the update or do I do something to the phone to allow it to receive the OTA update? If I do opt for the OTA what must I do to allow it to load?
Being somewhat novice when it comes to loading software on phones, is there a good FAQ out there that lists all the different loads, with what they contain and explanations of those components. Right now, voodoo, Peanut butter and jelly… buzzwords.
Click to expand...
Click to collapse
All in one package that you installed came with custom kernel. You need to flash a FP1 debloated/bloated/rooted rom and the FP1 kernel. Since you have the custom rom+kernel you can not use OTA update. Some people (like me) prefer to do it clean by go back to stock EP4d rom, then do the full update to FP1, then flash what ever custom rom out there, like Eclipse or debloated etc...More on how to do it here:
http://forum.xda-developers.com/showthread.php?t=1560117
Sooner or later you should be on the latest version any way specially for support from XDA.
Thanks for setting me straight. Let’s see if I understand your info.
1. I have a custom ROM and need to use the stock one to be able to get the update to install.
2. Once I install the stock ROM and get the update, I could reinstall the same custom ROM I have now.
3. Returning my phone to stock will remove root access so I can get the update
How do I get back to stock everything, update the phone and then add only root access. I don’t know enough about stock ROMs to know why I’d want or need one.
beavermjr said:
Thanks for setting me straight. Let’s see if I understand your info.
1. I have a custom ROM and need to use the stock one to be able to get the update to install.
2. Once I install the stock ROM and get the update, I could reinstall the same custom ROM I have now.
3. Returning my phone to stock will remove root access so I can get the update
How do I get back to stock everything, update the phone and then add only root access. I don’t know enough about stock ROMs to know why I’d want or need one.
Click to expand...
Click to collapse
1. Yes, you need EP4D stock rom to get OTA update.
2. Yes, once you on stock FP1, you can use flash eclipse 2.0 (which build from FP1 rom). Once done you will have FP1 eclipse with FP1 stock kernel.
3. If you have pure stock EP4D and rooted, you can take the OTA, but yours is not.
You have 2 Options to upgrade:
1. Flash back to pure stock EP4D, OTA upgrade to FP1 then flash pre-rooted FP1 eclipse 2.0 rom. Then flash cwm.
2. Flash FP1 pre-rooted eclipse 2.0 rom, flash cwm, flash FP1 kernel, flash FP1 radio.
Hope this help, don't hesitate to ask if you have more questions.
Ok. That makes sense, sort of…
I’m going to give #1 a try since I found the stock EP4D load on the page you recommended. I will then be able to get the OTA update and have a stock phone with FP1.
I will then follow #5 on that page to root my pure stock FP1 and make CWM stick after reboot. Do you know if there is a free program that will let me change the file permissions of “install-recovery.sh” like root explorer?
beavermjr said:
Ok. That makes sense, sort of…
I’m going to give #1 a try since I found the stock EP4D load on the page you recommended. I will then be able to get the OTA update and have a stock phone with FP1.
I will then follow #5 on that page to root my pure stock FP1 and make CWM stick after reboot. Do you know if there is a free program that will let me change the file permissions of “install-recovery.sh” like root explorer?
Click to expand...
Click to collapse
root browser lite or ES file explorer. Both you can get from the Market (google play).
Thanks for the help. I got the phone updated successfully. I ended up having to load eclipse ROM on the phone after the OTA update as the other method with superuser update and superuser fixer failed to deliver root access.
couple of questions:
1. I can no longer set multi-screen wallpaper. How do I restore this functionality?
2. I can't answer my phone using the puzzle pieces. what am I missing?
Mike
PS thanks again for all the help. Sometimes I just need a push in the right direction.
Now that i've had a chance to play with the phone... The market keeps crashing. Anyone know what to do?
Sent from my SCH-I510 using XDA
FIX: settings/applications/market/clear data Reboot
I am on stock 4.1.2, VRBMB1. I am rooted, unlocked and with TWRP recovery. I have used Titanium to freeze SDM 1.0.
I am considering going to VRBMF1. I don't know how to safely get there. I also don't know what improvements might come with the OTA to MF1. Should I just hang out with VRBMB1 until the rumored update to 4.3 arrives? I would like to be in the position to return to what I have now (just in case), or be able to move to 4.3 if, and when, it come out. How do I proceed? Thanks
I have the same question... subscribed!
Is there a rooted/unlocked update file, or do I just run the VZ update and use Voodoo rootkeeper to restore root (or Casual unlock again, if needed)? Or dirty-flash one of the rooted/unlocked stock ROMs (and then the firmwares)?
So many ways to get there, just looking for the safest... I figure the VZ update might be best.
So, I finally bit the bullet. I backed up all kinds of things before running, but it seems I didn't need to. I unfroze SDM, and then checked for updates. It downloaded and then rebooted to install. Since CWM was installed, it tried to perform the update, gave a few errors, but I let it go anyway. After the main install was done, CWM asked me if I want to let the updater install a new (stock) recovery - I said no. Then it said that I may have lost root, so do I want CWM to fix it - I said yes. Then I cleared the cache (just in case) and rebooted. The phone booted up, said it completed the upgrade, and then dropped me back into the rooted OS. Pretty cool.
SDM did complain to say that the updated "didn't happen" but the phone shows the new MF1 version, and a few new apps as well. So, obviously, the update happened... and I didn't lose root or recovery. Damn nice...
I wonder if TWRP does the same things (disable the stock recovery and restoring root)...?
EDIT: Reading the TWRP page says that they don't support nor recommend applying a stock ROM update.
Secondly, I found that while my phone was working fine, when I tried to get into recovery, it popped up the unauthorized software error. Meh. I used the Casual rooting tool to reroot, apply the insecure aboot, and then reapply CWM... and I'm back to normal now. Not a big deal, but still more steps than I thought I needed above!
Hi everyone, new guy here.
I'm rooted and currently running 9.18.79 with Verizon. I'm trying to install the 9.18.94 OTA update, but it fails everytime. After I select "Install Now" it reboots and starts to install, but then I get the Android robot on its back with the red triangle. The phone then reboots again and I get a message that says the software update failed. What's the secret to updating when rooted (while also making sure to still have root access afterward)?
Thanks...
filmfanatic09 said:
Hi everyone, new guy here.
I'm rooted and currently running 9.18.79 with Verizon. I'm trying to install the 9.18.94 OTA update, but it fails everytime. After I select "Install Now" it reboots and starts to install, but then I get the Android robot on its back with the red triangle. The phone then reboots again and I get a message that says the software update failed. What's the secret to updating when rooted (while also making sure to still have root access afterward)?
Thanks...
Click to expand...
Click to collapse
You cannot be rooted or you must hide root w/ voodoo or super su. Also you must use stock recovery.
the update will not actually fail if you are rooted, although it may report failing.
if it actually fails, you can obviously see it doesnt go through the process, then there is some other factor causing it to fail.
some things that would cause it to fail all together are: non stock recovery, freezing any bloat, removing any bloat, pretty much any modifications to the stock software other than rooting will cause it to fail.
once you have any system deficiencies fixed, use voodoo from the market to protect root and temp unroot before taking the update.
if you cant figure out what you did to the system to fix it, you may want to re-flash using the proper utility for your current system, re-root, protect and temp unroot through voodoo, then try the update again.
Thanks for the replies.
The primary reason I rooted in the first place was to remove a ton of unwanted bloatware, so at this point it's not even close to resembling the stock software. What are my options? Do I really have to re-install everything I deleted, or is it possible to flash the whole system back to stock?
filmfanatic09 said:
Thanks for the replies.
The primary reason I rooted in the first place was to remove a ton of unwanted bloatware, so at this point it's not even close to resembling the stock software. What are my options? Do I really have to re-install everything I deleted, or is it possible to flash the whole system back to stock?
Click to expand...
Click to collapse
you can flash the hole system using this http://forum.xda-developers.com/showthread.php?t=2474393 get the 1.33 version to match what you are on or the 1.34 to go right to the version you are trying to upgrade to. either is fine.