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.
Related
I'm running JF1.41 RC33. I just got a notice on my phone of an update available. How is this possible? I thought I can't get OTA updates (and never did until today) with my rooted phone with JF ROMs.
What should I do? I'm ignoring it for now.
Update: it is an update for DroidSand. First time I got a notification without the app being open.
I have a dev phone with the most recent jf update. My phone is prompting me to update with a holiday update or something like that. Do I need to do that? Or will it screw with jf update?
Thanks
***Update*** Its prompting me like every 15 minutes. Its driving me crazy!
either allow the update or get JF's 1.43
I went ahead and downloaded the OTA update, and I no longer have JFv1.41. Which is fine with me, since I have a dev1. I didnt use the multitouch or the auto-rotate anyway. As long as I have root, and tethering, im a happy man!
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
So after downloading and trying to install the ota ics update my phone is stuck on the moto splash screen. The update was downloaded successfully and the install was going smoothly up until 30% completed i guess. The normal android update screen disappeared and the 'dead' android appeared, the phone then rebooted and was then stuck on the initial moto splash screen. I was running stock 2.3.6 gb before the install. Pretty lost here as to whats going on with my moto paperweight. I have read the 'noob' thread, downloaded rsd lite, moto drivers, and the fxz to go back to 2.3.5. But am hesitant to pull the trigger on anything as I am far from being sure! Any help would be appreciated!
name_the_if said:
So after downloading and trying to install the ota ics update my phone is stuck on the moto splash screen. The update was downloaded successfully and the install was going smoothly up until 30% completed i guess. The normal android update screen disappeared and the 'dead' android appeared, the phone then rebooted and was then stuck on the initial moto splash screen. I was running stock 2.3.6 gb before the install. Pretty lost here as to whats going on with my moto paperweight. I have read the 'noob' thread, downloaded rsd lite, moto drivers, and the fxz to go back to 2.3.5. But am hesitant to pull the trigger on anything as I am far from being sure! Any help would be appreciated!
Click to expand...
Click to collapse
You need to grab the ota files from the post alteredlikeness posted in the general section, and put it on your sdcard.
Here:
http://forum.xda-developers.com/showthread.php?t=1930634
Then boot into stock recovery, and hit both vol + and vol - button, then from the menu select apply update from sdcard.
The dead android you saw updated your recovery binary, give this a try... if you get errors, then keep track of them, so you can post then here. That way we can better help.
Thank you Jim. I will give this a try and report back any results.
So I have been relying on my trusty Nokia e71 for the past few days as I have been very busy with work and have had no time to work on my Atrix 2. Finally found some time tonight and have successfully updated my phone! I tried Jim's method to install from the SD card but it repeatedly failed; the phone gave errors pertaining to the signature or security? I honestly cant remember as I have been drinking for a while now. I then tried installing from cache and found success after a looooong install. I'm now enjoying ICS on my Atrix 2 thanks to Jim!
Need some answers/help...
I was stock, rooted on 8.0....saw a pop-up box yesterday about OTA, didn't think much about since I thought being rooted wouldn't allow the OTA. Have seen the occasional pop-up over maybe the last couple weeks, but I don't normally restart my phone unless it starts to lag or freeze up/run slow. A restart usually fixed that. Was perfectly happy staying on 8.0. I did a shutdown on my phone this evening, and when I restarted it, bam, I'm unrooted on 10 now, specifically, QP1A.190711.020
The phone was bought from Google, unlocked in Oct 2017. I immediately unlocked bootloader and rooted at that time and have been running stock 8.0 since. TWRP and Magisk were used following instructions from the thread here on the forum.
No data was lost after the restart today and 10 seems to be running ok. I did download some data and pictures through my USB-c onto a flashdrive and it did seem to drain my battery FAST while doing it.
What I'd like to know now is how to get root back. I wouldn't mind staying on 10, but if I re-root, will another OTA break my root again? I haven't tried to do a shutdown and a restart again to see what would happen because I'm afraid my phone will brick.
I'm kind of a noob at this, and I don't always understand when you all get technical, but I can follow step-by-step instructions.
First off, how did an OTA actually get through, update and unroot my phone?
And second, can someone point me to step-by-step instructions to re-root my phone on 10, and how do I keep it from happening again?
Thanks for looking and I'd be very appreciative if someone could help me out.
Thank you.
Jim
same here
Same here.
I've got a retail (NON-Verizon) rooted, stock OG Pixel with 8.1 and I've been ignoring the nag to update to 10.
My wife has a retail (NON-Verizon) Pixel 2 that was also stock, rooted 8.1 except she just took the update and asked me about it later.
Both were done with TWRP and Magisk, albeit differing versions.
She's now unrooted at QP1A.191005.007.A1
TWRP v3.2.1-0-walleye is installed.
EDIT: TWRP seems to have been nuked by the OTA upgrade.
I just tried to reboot into TWRP recovery and it's gone.
Magisk Manager app version 5.4.0 (57) + "Latest Magisk Version: v16.0" (I'm pretty sure I rooted via v14.5(1456) though) are present.
"Update Magisk Manager" is nagging about updating /installing MagiskManager-v5.8.2
Root Checker Basic v6.4.6 is also installed.
I'm scared to death to update Magisk or attempt root without some guidance from you fine folks here.
Until then, I'll start having her backup everything she wants to keep in case things go sideways.
I didn't think I was the only one this happened to.
Ok...noticed another issue.
I had Titanium Backup Pro installed. I had several apps frozen before the forced upgrade to 10. Guess what? Those apps are listed as disabled in the app list with no button for re-enabling them. Titanium Backup Pro no longer works because I lost root with the forced update to 10, so I can't unfreeze with Titanium Backup.
Is there any way to unfreeze those apps without re-rooting? Not too sure I even want to attempt to root again.
Also, I haven't shutdown or restarted since the forced update. S3NTYN3L, so you're saying you didn't have any issues restarting/rebooting? Other than TWRP being gone, no other issues?
fjm568 said:
S3NTYN3L, so you're saying you didn't have any issues restarting/rebooting? Other than TWRP being gone, no other issues?
Click to expand...
Click to collapse
Correct.
As for "other issues", none that I, or she, have noticed.
Still breathlessly waiting to hear about how I go about re-rooting without data loss.