i,
I'm new here, I hope I'm posting this in the right forum. My apologies if not.
I have a rooted Verizon Droid 4 running Gingerbread. I had busybox installed to root it, and I configured it using the Droid utility on OS X some months ago. I used Titanium Backup (with root) to freeze the bloatware.
Fast forward to a couple days ago, when Verizon pushed the ICS update to it's phones. I downloaded it and ran it, and it reported "update failed", then I smacked myself in the head and remembered that I didn't un-root the phone.
So I disabled root via busybox, and then retried the update. It downloaded and ran, and now it gets stuck at the Droid animation screen (the one after the "M" "Dual Core" screen).
I'm thinking it's because I did not unfreeze those apps through Titanium?
In any case, I've tried restoring it to Gingerbread (219) (VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01.xml), and it fails on step 6/18 (cdt.bin).
I understand that you can't flash back to Gingerbread from Ice Cream Sandwich, but I'm not sure if ICS ever went all the way through.
Right now I'm downloading the ICS fastboot files (I've been attempting all these restorations via RSD Lite on a mac pro with bootcamp, and a factory cable that I made from the instructions on here (what a pain in the ass that soldering was)).
Does anyone have any advice on what to do to return my phone to stock? I can't get it to do anything.
Many, many thanks in advance to anyone who might be able to help. I've been tearing my hair out over this for the last 3 days.
lol man thank god us Samsung people have Odin...
Is there a stock ICS image out yet?
Can you get into recovery or just bootloader?
I don't think this would have been hard to find if you had looked, but here's where you should be asking your questions: http://forum.xda-developers.com/forumdisplay.php?f=1503
Actually, you'll likely be able to find a thread detailing how to return to stock anyway. The problem is that, as you guessed, you didn't unfreeze those stock apps and processes before taking the update.
I hope you're able to restore to GB as ICS isn't perfect yet because of VZ's tweaking and I don't think it's worthwhile unless you're going to a custom Rom. At least now you know how to handle things in the future, though I wouldn't recommend taking updates until they've been out for a bit and problems have been dealt with.
Related
So the purpose of this thread is to somehow update my 2.2.19 Droid 2 to 2.2.20.
The problem is as follows:
I rooted my phone and removed a lot of the crapware. But for a couple different reasons I want the 2.2.20 upgrade, though the phone works pretty well as is.
The OTA doesn't want to work. I've un-rooted and tried the OTA, fail. I went to my Titanium and tried to reinstall the deleted crapware and it only got through 4 of them. The other 10 won't reinstall, presumably the ones I need in order for the OTA to succeed.
I tried RSD Lite and it claimed "success" though I saw no real change after the reboot.
I don't know what to do at this point. If there's a way to even re-flash to a 100% stock version of Droid 2.2 with all the original programs and lose all my crap, I'll do it. I just don't know where to go and what to do.
I'm gonna pull my hair out!
I am rooted using the Universal Xoom Root method. I am still running stock, only with SU and apps which require SU. Why can I not accept an OTA update? It seems like the worse that could happen is it overwrite the SU.apk and I need to re-root.
Thanks in advance.
I was wondering about this as well. I am rooted and am running Rogue kernel. I guess I'll just update and see what happens. Worse comes to worse, I will have to re-root.
Seems like the Xoom forums are quiet...did a lot of people abandon the device for the Galaxy Tab 10.1...When previous OTAs happened, the forums were chock full of chatter about to or not to accept the update.
Yeah, I just tried an OTA update and it wouldn't work. Got the Droid with exclamation point. Up + power put me back where I was.
Sent from my Xoom using XDA App
same here. No dice on the update, just stuck at the install screen. On a positive note, the update notifications are gone. Damn those were annoying.
If you root, even without any additional custom ROM/kernel mods, you may receive notification of an OTA update but you should not accept it and try to install it. It will probably put you into a bootloop or worse.
If you wish to root, don't worry. Our wonderful developers are hard at work right now, configuring an update for the device...we'll more then likely get it before the official release comes out OTA.
Anyway, you can always revert back to stock if you really want the OTA update, but stock is boring.
place your unrooted backup on, take update and reroot.
if you don't have one, their are some around.
I keep a backup that isn't rooted with all my apps installed, then when update comes, it is real quick to restore, update and reroot ....
jerrycycle said:
If you root, even without any additional custom ROM/kernel mods, you may receive notification of an OTA update but you should not accept it and try to install it. It will probably put you into a bootloop or worse.
If you wish to root, don't worry. Our wonderful developers are hard at work right now, configuring an update for the device...we'll more then likely get it before the official release comes out OTA.
Anyway, you can always revert back to stock if you really want the OTA update, but stock is boring.
Click to expand...
Click to collapse
Yeah, diddo here with it not bothering me about OTA updates anymore after trying. It didn't put me in a boot loop, just the pretty droid screaming (exclamation point)
I have a backup from before I rooted, but what the heck, it didn't hurt anything, and I was just playing around.
Thanks for everyone's input.
Spoke too soon. The update is back to nagging me again. Errrrrrrr
Why can't they just push out ICS for the Xoom. Hell, they showed ICS on the Verizon Xoom at LeWeb this week.
flippingout said:
Spoke too soon. The update is back to nagging me again. Errrrrrrr
Why can't they just push out ICS for the Xoom. Hell, they showed ICS on the Verizon Xoom at LeWeb this week.
Click to expand...
Click to collapse
Yeah, diddo. Mine started again about three days after I tried to install. I too am looking forward to ICS.
Sent from my Xoom using XDA App
I'm hoping to get some eyes on this plan I've made for hacking my new Droid so I can avoid bricking it at all costs.
I bricked my old Bionic 2 days ago due a combination of problems with Clockword Recovery Mod and the leaked ICS update, as well as my battery frying for some reason. Thankfully Verizon was none the wiser and they are sending me a new phone and battery in a few days. Although I'm cautious about hacking now, I still plan on rooting the new phone so I can recover my apps and data from the old phone's SD card.
Here are my plans for the new phone. If anyone could tell me if it makes sense or if they see any issues that will arise from following these steps, please let me know:
1. Root new Bionic with Motofail.exe root
2. Restore apps and such with Titanium Backup (restoring individual apps so I don't get any old clockwork garbage or other random stuff)
3. Download Voodoo Root OTA Rootkeeper.
4. Wait for official ICS OTA (don't want to mess around with the leaks anymore) and backup root with voodoo
5. Unroot with voodoo, install ICS and re-root after update (I've read on some posts that Voodoo works with the ICS OTA but I'm not 100% sure)
If anyone sees any flaws with this plan or if you think it sounds like there won't be any problems, please respond! I really don't want to brick a second phone so any help would be invaluable.
Hey guys, been a long time lurker here and just encountered my first issue, so made an account to hopefully get some advice.
I received the note 10.1 8010 (UK) as a gift for Christmas. I was disappointed to see it was running 4.0, when devices like the Nexus 7 are already on 4.2. And Germany had the 4.1 update for over a month. Samsung as always refuse to give a solid answer.
I followed a guide to install the German 4.1.1 update. I first installed the German version of ICS via Odin. I then applied the update.zip from here:
HTML:
d-h.st/lLB
Prior to this, I rooted the device, but I believe the above process removed the root anyway.
After my device rebooted, the S Pen isn't working at all. It recognises when I take the pen out, but I cannot use it. It doesn't do a thing. I've read about 1,000 forum threads and cannot find an answer, as to how I can get it working again.
I tried deleting cache and user data, then reapplying the update.zip to no avail.
When I boot up in to recovery mode, it does come up with a message about CSC and then the little drop falls over and I have the usual options.
Any idea what I need to do, to get my S Pen working again? Or what I've done wrong?
Many thanks
This is how I rooted the device.
HTML:
rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/
I have a feeling this is the "root" of the issue. I'm not sure how to remove it.
I know previously I wasn't able to change my CSC via CSC switcher, but I am now.
So I guess installing the German ICS and then update.zip, hasn't completely undone whatever rooting it above did.
Removed the custom recovery and the pen started working again. At this point I was back on ICS, trying to see whether JB was the issue.
Now update.zip will not apply, despite the fact I'm on the German ICS stock. I get an error status 7 in package.zip.
This is the worst experience I've ever had, with any device in my life.
If this wasn't a present I'd have smashed it in to tiny pieces. I will never buy a non Nexus device ever again.
I know this may seem trivial, but when I'm running 4.2 on all other devices, I don't want to be stuck on 4.0 with my brand new tablet.
Samsung have really put me off ever buying their devices in the future.
Tehkseven said:
Removed the custom recovery and the pen started working again. At this point I was back on ICS, trying to see whether JB was the issue.
Now update.zip will not apply, despite the fact I'm on the German ICS stock. I get an error status 7 in package.zip.
This is the worst experience I've ever had, with any device in my life.
If this wasn't a present I'd have smashed it in to tiny pieces. I will never buy a non Nexus device ever again.
I know this may seem trivial, but when I'm running 4.2 on all other devices, I don't want to be stuck on 4.0 with my brand new tablet.
Samsung have really put me off ever buying their devices in the future.
Click to expand...
Click to collapse
This a pretty bummer situation. Sorry you're dealing with it.
I find this interesting, as I followed the exact same procedure to root as you. I haven't experienced any pen issues though.
Could it be the 4.1 you flashed?
This is one of my fears too, so I really hope this can be solved.
I finally managed it.
I downloaded a different German ICS from a different guide and this time it worked no problems.
The one that worked, had a file name: N8010XXALI3_N8010OXAALI3_DBT
Update.zip worked first time after I installed the above ICS.
Hope that helps.
This is my first post on this site, though I have trolled these forums since I got my smartphone. I have learned a lot too!
Currently my phone is a rooted Maxx HD (xt926) running JB 4.1.1. From what I have read on the forums, going to 4.1.2 might break my root and WILL keep me from going back to ICS using a tool I found on this site (Matts tool I think its called). I have decided its not worth the upgrade until someone gets root with a stock JB instead of with ICS then a JB upgrade.
I am glad I caught it in time. The updater started the 4.1.2 download so I turned off wifi and data to stall it. I couldn't cancel the download. I have Titanium Backup and froze Updater 4.1.1. This took my downloading notification away completely. Now if I try to do an update, it says an update is currently downloading, however I have no notification or any sign something is actually downloading, so I think that stopped it.
I am hoping this doesn't mess up future OTA updates should I defrost and try again.
This isn't a question so much as I didn't see a thread that covered stopping OTA notifications with this phone after a search. This procedure seemed to work great so far. This is probably such a simple thing to veteran android users that it probably wasn't posted, or I didn't find the post. I am hoping this will help other noobs. Or if this won't work or breaks something else, hopefully someone will point it out.