Related
Thanks for all the info guys from my thread I started about me getting a Droid Bionic. Sorry for just now responding but what I've find is I have CWM installed and I'm on Liberty, I'm wanting to try Eclipse real bad though, so would it be safe to just wipe data/dalvik/cache then flash it? Or I've had thoughts that I should've done the safestrap but also I've thought about trying the .901 update, since I'm new with the bionic I'm really nervous about bricking it or messing something else up. Also when I was on stock I was on .893 and then once I flashed Liberty it now says .886, would this make a difference? Thanks for all your help everyone on the forum, I appreciate it!
My suggestion is to make a nandroid backup. Flash completely to stock using the Moto tool. Root and 4ever root. Update to .901. Then Safestrap.
I recently just started using Safestrap and it is nice to know that if you fubar up an android flash and then need to run somewhere, you can always get back to stock.
Yes! Someone else says fubar!
Back on topic, so make a nandroid while I'm on Liberty?
Going to .901 makes me a little nervous because I don't want to mess anything up and I'm also confused on using safestrap but I feel like it would be really nice to have. Is the Moto tool on the forums here to go back to stock?
Thanks for the info man.
One problem I had when going from liberty to eclipse is that I wasn't getting 4g with eclipse. I used safestrap so I could go back to liberty.
Sent from my DROID BIONIC using XDA App
So would you recommend I go back to stock then go from there? If so how would you think I should go back to stock?
I never updated to. 901 because I've never really had any problems with my bionic so I'm not right person to answer anything about that. I'm trying to wait until Motorola releases ICS before I do anything else major. Sorry I'm not able to help.
Sent from my DROID BIONIC using XDA App
Eclipse does have an. 893 rom if you don't want to make the jump to. 901.
Although most of the newer and future eclipse themes will be for v2.1 which is their. 901 rom.
Sent from my DROID BIONIC using Tapatalk
I know there were 2 leaks of ICS for the phone, but has anyone been able to update the ICS ROMs in the threads to use the new kernel and radios? There's still some data issues and we're using a GB kernel
EDIT: i meant leaks, stupid typo
The kernel is based on GB because of the locked bootloader. At least that's how I am to understand it. In other words I think that the custom ROMs can be improved using the leaked ROMs but they'll still have to remain based on the GB kernel. Unless you update your stock system to ICS that is. I think the biggest thing devs should focus on right now is a way to safely upgrade to ICS where downgrading is possible in order to stay on Verizons official upgrade path.
As it stands, the OTA will look for GB 219 when upgrading so those early adopters won't be able to get future upgrades. Unless devs find a way to downgrade or trick the update that is.
Everything I've said could be wrong however this is how I have come to understand it.
Sent from my DROID4 using XDA
Given that we have the fastboot files can't we just wipe and flash that to downgrade?
Sent from my DROID4 using XDA
azrael293 said:
Given that we have the fastboot files can't we just wipe and flash that to downgrade?
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
No, this results in a brick. Fastboot refuses to flash older partitions over new ones.
Sent from my XT894 using xda premium
flamefangahs said:
The kernel is based on GB because of the locked bootloader. At least that's how I am to understand it. In other words I think that the custom ROMs can be improved using the leaked ROMs but they'll still have to remain based on the GB kernel. Unless you update your stock system to ICS that is. I think the biggest thing devs should focus on right now is a way to safely upgrade to ICS where downgrading is possible in order to stay on Verizons official upgrade path.
Click to expand...
Click to collapse
This is why you need kexec - you can load the ICS kernel dynamically, without corrupting your GB install.
Sent from my DROID4 using Tapatalk
highlandsun said:
This is why you need kexec - you can load the ICS kernel dynamically, without corrupting your GB install.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Actually, upgrading to ICS leak is probably the way to go. We can now upgrade from leak 200 to 206, giving us the ability to stay on the upgrade path. Since the XDA forums are dead for the Droid 4, I suggest everyone keep up at droidforums.
Here are the instructions for upgrading from leak 200 to 206:
http://www.droidforums.net/forum/droid-4-roms/209619-get-unstuck-ics-leak-200-aka-upgrading-200-206-instructions.html
Also, I believe Hashcode is working on bringing Safestrap 2.0 to the new ICS leak based on the new kernel, and will be working on getting our ROMs on the new kernel as well.
rumgool said:
Since the XDA forums are dead for the Droid 4, I suggest everyone keep up at droidforums.
Click to expand...
Click to collapse
droidforums is about as dead for the Droid 4 as is XDA. I am really surprised how little interest people have in this phone. I guess I am one of the few that still loves physical keyboards. Only drawback on this phone is the non-removable battery. Otherwise it is rock solid. Had the original Tilt, then TP and TP2. Had the G2 on T-mobile, but reception on that phone was not good and T-mobile Network in the US sucks.
GermanGuy said:
droidforums is about as dead for the Droid 4 as is XDA.
Click to expand...
Click to collapse
This is true, I was just mentioning since most of the recent information regarding the ICS leak has been on droidforums so checking it out would fill everyone in on whats going on. Because basically development for the GB kernel is probably going to come to a halt and future development will be based on the new ICS kernel, including the existing AOSP ROMs.
wait, the 206 version keeps you on the upgrade path?
dewhashish said:
wait, the 206 version keeps you on the upgrade path?
Click to expand...
Click to collapse
No, but 206 was supposed to require 219 as 200 did and the official one will and people have found ways around it.
Sent from my XT894 using xda premium
I have Hashcode's stuff running on my kindle fire. We will all be in for a treat once he starts focusing on D4. He's done really really good work on the kindle.
dewhashish said:
I know there were 2 leaks of ICS for the phone, but has anyone been able to update the ICS ROMs in the threads to use the new kernel and radios? There's still some data issues and we're using a GB kernel
EDIT: i meant leaks, stupid typo
Click to expand...
Click to collapse
They won't be able to do so. What they will be able to do is make their builds work off/with the new kernel/radios flashed by the leak.
So Hashcode will have two builds.
1) - works on phones running the current stock GB kernel.
2) - works on phones running the leaked ICS kernel.
There is still a locked bootloader so you can't flash unsigned kernels/boot.img. For the leaked "system" files to help you need the ICS kernel. The only way to get the ICS kernel is to flash the leak.
So the leaks are great news for people wanting an AOKP or CM9 build running fully functional....on their leak installed phones. Not much help for those who do not want to flash the leak.
I'll definitely flash the leak once root has been released for 4.0.4 (in case OTA rootkeeper doesn't work) and hashcode releases safestrap 2.0 for the leak.
I'm presently running Hashcode and the rest of the STS Dev Team's CM9 release with modifications for the ICS kernel leak on my D4 that has been flashed to the .206 leak; I just pulled their work from GitHub and compiled it myself with a few little tweaks.
So far it's working great, face unlock and the camera is working perfectly and GSM/WDCMA performance is awesome, I don't seem to have the problem of under-reported GSM signal like in the stock MotoBlur leak.
(Note that I'm in Canada and using Bell Mobility, not in the US on Verizon so I can't say if LTE is functioning properly).
I just flashed it with Safestrap v1.09 for the D4; a little tricky since the bootmenu doesn't accept the Menu/Search softkey input to allow you to enter Safestrap, so I had to boot in BP Tools mode to force loading up the Safestrap Recovery. I made some additional tweaks to the build.prop file as well but am really impressed.
Won't be long before Hashcode puts up an official release, but I definitely recommend trying it out if you're up for it. If Hashcode doesn't mind, I could share a .zip of the build I made if anyone out there is interested.
Sent from my XT894 using xda premium
Rick#2 said:
I'm presently running Hashcode and the rest of the STS Dev Team's CM9 release with modifications for the ICS kernel leak on my D4 that has been flashed to the .206 leak; I just pulled their work from GitHub and compiled it myself with a few little tweaks.
Click to expand...
Click to collapse
Do you think you create a guide or go into more detail how you did this? I'm not quite sure what their git is.
Sent from my XT894 using xda premium
Rick#2 said:
...
I just flashed it with Safestrap v1.09 for the D4; a little tricky since the bootmenu doesn't accept the Menu/Search softkey input to allow you to enter Safestrap, so I had to boot in BP Tools mode to force loading up the Safestrap Recovery. I made some additional tweaks to the build.prop file as well but am really impressed.
...
Click to expand...
Click to collapse
This is what I'm trying to fix right now. Seems like the menu/home/search/back buttons are handled as part of the touchscreen. So the new Safestrap has to handle looking for virtual buttons.
Sent from my Amazon Kindle Fire using Tapatalk 2
Hashcode said:
This is what I'm trying to fix right now. Seems like the menu/home/search/back buttons are handled as part of the touchscreen. So the new Safestrap has to handle looking for virtual buttons.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
If you are making good headway, then disregard this. But you could use a scheme similar to FireFireFire for the er, Kindle Fire
Either use a physical button (a return to the old hold the X from the D1, perhaps?) or a few taps to the screen?
podspi said:
If you are making good headway, then disregard this. But you could use a scheme similar to FireFireFire for the er, Kindle Fire
Either use a physical button (a return to the old hold the X from the D1, perhaps?) or a few taps to the screen?
Click to expand...
Click to collapse
Right now, I'm treating the front buttons like they are a special portion of the touch screen (basically any touch past 960 pixels down is considered the "button row", and then I divided the width up into 4 spots for button presses: menu, home, back and search respectively. (This is in the recovery itself as well as the splashscreen which triggers off of menu)
If that fails, Ill just use hard keys for D4's Safestrap temporarily.
Sent from my DROID4 using Tapatalk 2
..or maybe the volume buttons (I bet it requires less modification than implementing support for the digitizer)
I just put up an updated Droid4 2.00 Safestrap for use w/ the new MotoICS leaks:
http://forum.xda-developers.com/showthread.php?t=1688610
BE SURE TO MAKE AN INITIAL BACKUP OF NON-SAFE SYSTEM BEFORE YOU DO ANYTHING.
You will use the "System" backup to restore back to stock .206 to update later.
I have the D4 CM9 / AOKP builds for the MotoICS leaks almost ready and I'll post those soon.
So who here is on an Android 4.0.4 leak? (official ICS leak)
Who is still on stock gingerbread?
Who is running a custom rom?
Answer in the comments and in the poll.
Im interested to see what is being used!
--Sam
I'm on the 208 leak. Lost root cuz I went from 200 to 206 then 208 but its all good. Only bad thing is all the bloat but besides that its running pretty well so far.
Running ICS leak. 206, kept root from GB .219
I was tempted to keep updating with each new leak, but at the expense of losing root I think I'll wait for the official upgrade to be released.
Sent from my DROID4 using Tapatalk 2
Stock rooted/debloated Gingerbread.
ICS shouldn't be that far off....waiting for the official release version. Since leaks are hitting every 12 to 13 days.....and you lose root going from one to the next.....might as well wait it out.
Running Eclipse ROM via SafeStrap. Sounds like the ICS leaks are running really well for most people. I'd just prefer to make sure I keep root and not have to worry about jumping through a bunch of hoops to update when the OTA finally drops, which can't be too far out.
Running stock. I really like AOKP, but the data issues were killing me, so I switched back. I figure once the OTA drops the ICS ROMs will work a lot better. I'm also hoping we get working 3rd party kernels.
I am running a stock ICS Leak
I am also running the stock .206 leak for the Moto Droid 4 and loving it. I haven't tried going to the new .208 leak as of yet.
I'm on .206, rooted. Very happy with it. I don't plan on upgrading again until Dan Rosenberg releases his ICS root method. As nice as ICS is...I'd rather be on GB with root than ICS without it.
wouldn't VooDoo OTA Root keeper work in all of this? I use it to maintain my root for OTA upgrades. But wouldn't it still work with a firmware push?
Just updated to 208 using Fastboot Upgrade and New ICS Root Method then recovered my files from Safe Strap for the data partition. :-D
gdeeble said:
Just updated to 208 using Fastboot Upgrade and New ICS Root Method then recovered my files from Safe Strap for the data partition. :-D
Click to expand...
Click to collapse
Did you take a nandroid, then restore the data only partition of the nandroid after you did the upgrade? THat's a great idea. I might do the same if it is that easy! Otherwise, I'll wait for a newer leak.
buying Droid soon.
I am eagerly awaiting the official ICS rollouts for Verizon, but it may be a while. The goal is not to update myself. Is ICS really all that...and worth waiting for?
rugo32 said:
I am eagerly awaiting the official ICS rollouts for Verizon, but it may be a while. The goal is not to update myself. Is ICS really all that...and worth waiting for?
Click to expand...
Click to collapse
I was a big Motoblur guy (once you debloat it of course) and even preferred it over CM9. I just liked the theme. I think the Motoblur ICS is worth it, it's ICS with a nice familiar feel to it. Is it worth the wait? Maybe. I have faith we can get back on the official path once it comes out so I didn't take much convincing to flash a leak now.
Sent from my DROID4 using Tapatalk 2
droidian1441 said:
So who here is on an Android 4.0.4 leak? (official ICS leak)
Who is still on stock gingerbread?
Who is running a custom rom?
Answer in the comments and in the poll.
Im interested to see what is being used!
--Sam
Click to expand...
Click to collapse
Not me.
Me.
Not me.
It's a corporate-supplied device... I can't mess around with custom ROMs and deal with bugs that I don't have the time to troubleshoot.
Plus no ROM will improve this awful screen or only-slightly-better camera, right?
Sent from my EVO using Tapatalk 2
I'm running .206. I tried .208 but I'm too much of a noob to even fallow noob proof instructions so I'm staying with .206 till I learn more, and till I can get back on the regular path (if its even possible).
So far I like it, the only thing that doesn't work for me is the facebook (my gallery) from the accounts. It crashes my gallery with an error saying that friendfeed has stopped working, so I just don't use that part of my gallery.
I'm satisfied!
Sent from my DROID4 using XDA
danifunker said:
Did you take a nandroid, then restore the data only partition of the nandroid after you did the upgrade? THat's a great idea. I might do the same if it is that easy! Otherwise, I'll wait for a newer leak.
Click to expand...
Click to collapse
Yes I took a Nandroid before I started the crazy Fastboot recovery process, then once rooted and safe strap installed, I did another nandroid(heaven for bid I'd have to start over again) then flashed over data only.
gdeeble said:
Yes I took a Nandroid before I started the crazy Fastboot recovery process, then once rooted and safe strap installed, I did another nandroid(heaven for bid I'd have to start over again) then flashed over data only.
Click to expand...
Click to collapse
Can't you just use recovery for flashing back data (I assume you are using the advanced restore?) or do you need to have safestrap installed?
I am running the .208 and was able to keep root thanks to Voodoo. I know some people have had issues with keeping root when going to .208 from .206 or .200. I went from GB to to .208 maybe thats why i was able to restore root? Anywho, ive been using the leak for over a week now and i am so glad i did.
Just went from .206 to .208 using the new kernel and following the instructions over at DroidForums. Also got root with the new method. Everything works peachy-keen.
Sent from my DROID4 using Tapatalk 2
I posted these questions earlier in the Q+A section and figure this is a better place for them.....
So I've got my 4th Bionic en route due to pesky data connection issues and no GPS. I'm wondering if I should flash the .232 ICS build. A couple questions arise if I may:
- Is it easily rootable? Running .905 stock root presently on my old Bionic. New one I'm sure will have .905 obviously stock and unmessed with.
- Does installing a leaked version make it any more difficult to install the official version at its release? I'm thinking it would be a good opportunity to work bugs out of pertinent apps and familiarize myself with the new version.
- Should I root the .905 before flashing the ICS? Does that matter? I'm thinking it'd be lost anyways on the flash up. And the root of the external (not sdcard, sdcard-ext) SD I'm assuming is where I place the leaked ICS file?
I love these forums as they minimize the knowledge gap between people like me and experts!
Sent from my DROID BIONIC using xda app-developers app
dmullen1373 said:
I posted these questions earlier in the Q+A section and figure this is a better place for them.....
So I've got my 4th Bionic en route due to pesky data connection issues and no GPS. I'm wondering if I should flash the .232 ICS build. A couple questions arise if I may:
- Is it easily rootable? Running .905 stock root presently on my old Bionic. New one I'm sure will have .905 obviously stock and unmessed with.
- Does installing a leaked version make it any more difficult to install the official version at its release? I'm thinking it would be a good opportunity to work bugs out of pertinent apps and familiarize myself with the new version.
- Should I root the .905 before flashing the ICS? Does that matter? I'm thinking it'd be lost anyways on the flash up. And the root of the external (not sdcard, sdcard-ext) SD I'm assuming is where I place the leaked ICS file?
I love these forums as they minimize the knowledge gap between people like me and experts!
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
From everything I hear, .232 should fix your data connection. It is quite easy to update to it, you just have to put the proper update file onto your external sd card and boot into stock recovery and install it. It is also very easy to root, assuming you have access to a computer running windows. The utility to root it is called razrs_edge and is easy enough to find and download. You will lose root on the upgrade, so it's probably just as easy to wait until after the update to root it. There is also a utility available which will let you downgrade to .905 and apply the new update without losing your data when the time comes for the official update. That can be found here http://www.droidforums.net/forum/motorola-droid-bionic/214902-downgrade-902-no-app-data-loss.html Actually, that utility can probably used to upgrade and root the phone even if you're starting on .905. Also, .232 is probably your best bet right now, as .235 is built so you can't go back to anything before it properly.
Good luck!
What about the update to the official release? Would I just be able to OTA to that, providing I defrost any bloat apps Verizon so kindly includes?
And one more quick one. Can I do that flash to .232 right now on my stock, partially frozen and rooted .905 rom without losing any apps or data? Sounds way too good to be true to me!
Thanks for your time too, dude. Totally got it!
Sent from my DROID BIONIC using xda app-developers app
dmullen1373 said:
What about the update to the official release? Would I just be able to OTA to that, providing I defrost any bloat apps Verizon so kindly includes?
Thanks for your time too, dude. Totally got it!
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
You can't directly update to the OTA, but that's what the utility which I linked in my previous reply is for. It will let you temporarily downgrade to .905 and allow you to apply the OTA. The person who maintains it does a really good job and keeps it up to date with all the new files when they're released.
You're the man dude thanks!
Sent from my DROID BIONIC using xda app-developers app
dmullen1373 said:
You're the man dude thanks!
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
If you've got an account on droidforums, make sure to thank Samuri_HL, he's the one who makes things so easy to use.
OK so I've one more question. If I wanted to install it now on my bionic with the stock rooted .905, can I just download the ICS update and install while preserving apps+data?
Sent from my DROID BIONIC using xda app-developers app
dmullen1373 said:
OK so I've one more question. If I wanted to install it now on my bionic with the stock rooted .905, can I just download the ICS update and install while preserving apps+data?
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
As long as you're stock, the upgrade should work fine and shouldn't affect your apps+data. You will lose root (I believe) and need to re-root afterwards though.
One more question.....
OK, so I've managed to get .232 up and running. I haven't rooted it, and truly don't see the point at least at this point because I can just disable the VZ apps that I don't need (namely, all of them.) So, now that I'm on this build, let's say they release the final version tomorrow...what is going to need to happen to update to the final version? I've truly scoured through all of these forums and can't quite figure it out. Will it just be as simple as the .232 flash? I mean is it worth going to .235 on my en route Bionic and loading all of my apps and investing the hours required in getting it perfect? Or will it all just be one waste of time? I know that the final release will be an OTA, so I'm assuming that .905 will need to be in the mix at some point hence the confusion....
Kudos to all who care to help thee noobs around here!!!
dmullen1373 said:
OK, so I've managed to get .232 up and running. I haven't rooted it, and truly don't see the point at least at this point because I can just disable the VZ apps that I don't need (namely, all of them.) So, now that I'm on this build, let's say they release the final version tomorrow...what is going to need to happen to update to the final version? I've truly scoured through all of these forums and can't quite figure it out. Will it just be as simple as the .232 flash? I mean is it worth going to .235 on my en route Bionic and loading all of my apps and investing the hours required in getting it perfect? Or will it all just be one waste of time? I know that the final release will be an OTA, so I'm assuming that .905 will need to be in the mix at some point hence the confusion....
Kudos to all who care to help thee noobs around here!!!
Click to expand...
Click to collapse
You will need to flash the .905 fxz file in order to receive the OTA. There are a couple ways of doing that. The most failsafe way would be to do it using RSD Lite, however that will wipe all of your data and basically return your phone to a like-new state. The other main way is to use SamuriHL's House of Bionic program/script. It uses a modified version of the fxz file that will not wipe your data. You can use it to return to .905 and install the OTA in the normal way, by checking for updates and letting it install once it is available. You can also use it if you download the OTA when it is released and basically do it the same way you updated to .232. When the OTA is released, I'm sure he'll put together a new version of HoB that includes it, so that the whole process is fairly well automated. There's no saying when exactly the OTA will be ready, but for now just enjoy your ice cream sandwich.
When I mention that it will not wipe your data, that means that all of your apps and whatnot will remain intact. In any case, I don't recommend updating to .235, I have it and can't tell much difference between that and the .232 leak, and the .232 leak has a safe route back to stock, whereas .235 doesn't, so it's definitely not worth the risk. If you're happy with it without rooting, then by all means keep it that way, rooting means it's just easier to mess things up.
Looks like we will be skipping the soak and going straight to General Availability (GA) status:
UPDATE - Friday, April 12: The DROID BIONIC by Motorola will soon be upgraded to Android 4.1, Jelly Bean. The software upgrade will be pushed to customers in phases starting April 15.
Source link in post 68: http://forum.xda-developers.com/showpost.php?p=40223168&postcount=68
" Thanks for joining the Motorola Feedback Network. We are inviting owners of the Droid Bionic on Verizon to participate in an early preview of the new Jelly Bean software release, and provide feedback. If you are not currently using a Droid Bionic, please excuse and ignore this email.
The registration window for this soak could be extremely small -- sorry about that. Please act now to take part."
-- Sent from my DROID BIONIC on the KEXEC() enabled latest Linux kernel compiled for Key Lime Pie, with backwards compatibility.
Really? It's not still April 1st is it?
It is true. See Droid Life. Can't wait for some JB goodness.
Drunkula said:
Really? It's not still April 1st is it?
Click to expand...
Click to collapse
Lol. I wouldn't do that to the bionic community. We've been through enough lol
-- Sent from my DROID BIONIC on the KEXEC() enabled latest Linux kernel compiled for Key Lime Pie, with backwards compatibility.
Well now that I believe, I've already backed up and FXZ'd back to stock - in case I also get the invite.:good:
EDIT:
Always cracks me up, though, because the invites always say "keep it confidential" - but people still talk about it!
Drunkula said:
Well now that I believe, I've already backed up and FXZ'd back to stock - in case I also get the invite.:good:
EDIT:
Always cracks me up, though, because the invites always say "keep it confidential" - but people still talk about it!
Click to expand...
Click to collapse
Like they can stop us!
Sent from my Nexus 10
Groid said:
It is true. See Droid Life. Can't wait for some JB goodness.
Click to expand...
Click to collapse
And you know if you read it on the internet it's true. I've read it on three sites now. Woohoo!
Let's see if we can keep this thread helpful. Does anyone have a current howto on going back to stock?
ETA: In other words, can I just rsdlite back to .246 like we used to? I've heard a lot of folks recommending against using rsdlite. Never quite understood why.
SCFirefighter said:
Let's see if we can keep this thread helpful. Does anyone have a current howto on going back to stock?
ETA: In other words, can I just rsdlite back to .246 like we used to? I've heard a lot of folks recommending against using rsdlite. Never quite understood why.
Click to expand...
Click to collapse
You can fxz to GB update to official ICS from there.
Sent from my XT875 using xda app-developers app
mikemikemikexxx said:
You can fxz to GB update to official ICS from there.
Sent from my XT875 using xda app-developers app
Click to expand...
Click to collapse
What? No, this is horrible advice. Use 246 fxz if you'd like to revert to stock without bricking
Liquid Smooth Bionic
rocketsaucev2 said:
What? No, this is horrible advice. Use 246 fxz if you'd like to revert to stock without bricking
Liquid Smooth Bionic
Click to expand...
Click to collapse
Yeah, I know you cannot downgrade back to GB. I hope nobody else will try that; it will be a rude awakening.
I will fxz back tonight. I can't wait for the soak!
rocketsaucev2 said:
What? No, this is horrible advice. Use 246 fxz if you'd like to revert to stock without bricking
Liquid Smooth Bionic
Click to expand...
Click to collapse
Meant to say go back to GB or fxz ICS before joining soak test.
Don't see much point either way since your rooted. Custom Roms will always be a better choice. Don't see that changing with official JB. They should have just went straight to KLM than ceased development for our phone. Now it will die with JB.
Sent from my XT875 using xda app-developers app
Either way, gb is history for the bionic. No going back. I believe we'll see some klp action with kexec
Sent from my Nexus 10
Newb-ish question
So, i had the stock ICS (work phone, so no "major modding"), but I rooted it. I uninstalled some VZ junk, and ran some apps which required root -- specifically titanium backup -- I've backed up my apps from ICS
To get the JB soak test, do I need to simply unroot? Or do I need to restore to factory?
I "unrooted" using the option in SuperSU. Now, after reboot, my phone shows that it is no longer rooted (checked with one of the rootchecker apps).
Do I qualify for the JB soak when it's pushed? Or since I removed the VZ crapware, is the update for my phone not going to work?
If i need to revert to factory, I'm assuming from reading the sticky, that I need to "use the ics fxz method". I don't see instructions on that, just a thread with links to downloads... Do I download that to an SD, and then boot into recovery, to install it? Or am i missing something...
Sorry for the probably-too-basic-for-most-of-you questions...
You will need to fxz back, or restore every Vz app you removed, and unroot. The update is probably still going to fail for you. It is very particular about system files and Checks all of them before updating them. Try it, but just be aware you may have to fxz after all.
You can always reroot and restore TiB data after JB is done flashing. That's what my plan is.
You will need USB drivers, rsdlite, and the 246 fxz file. Read a generic fxz how to and you will see how it works.
ETA:
Let me rephrase. If you uninstalled the Vz crap using the normal app management interface, which you can do for some of them, you should be in the clear. You can also 'disable' apps in ICS. If you did that you should be ok as well. It's only if you used 'advanced' methods like TiB's freezing or simply uninstalling apk's from the /system partition you will fail the update.
I just finished fxz'ing back to 246. All I did was re-root it, and restore TiB application data. None of this should prevent me from accepting the OTA soak update. I'll keep you posted!
I think folks have the wrong idea of what a soak is. Your phone will get an over the air update when it's ready; a soak is not for the masses, you have to sign up for them. You don't go back to stock to get a soak.
Sent from my Nexus 10
mikemikemikexxx said:
You can fxz to GB update to official ICS from there.
Sent from my XT875 using xda app-developers app
Click to expand...
Click to collapse
I second the person who said don't do this.
Sent from my DROID Project X using Tapatalk 2
smokedkill said:
I second the person who said don't do this.
Sent from my DROID Project X using Tapatalk 2
Click to expand...
Click to collapse
Guess you have SRS (Selective Reading Syndrome). I posted right after with what I meant to say.
Sent from my XT875 using xda app-developers app
rocketsaucev2 said:
I think folks have the wrong idea of what a soak is. Your phone will get an over the air update when it's ready; a soak is not for the masses, you have to sign up for them. You don't go back to stock to get a soak.
Sent from my Nexus 10
Click to expand...
Click to collapse
I'm not sure you understand what a SOAK is....
You have to be almost 100% stock for a SOAK push out to install...just like you do for an OTA. A SOAK push out is the exact same file they will push out to everyone as the OTA if the SOAK goes well. Typically with Motorola, all most every SOAK has been "approved" as successful and pushed out as the OTA. If for some reason this SOAK is not approved....another SOAK goes out and if approved becomes the OTA. In that case they have to create two....one for phones still on the current official OS and one for phones that are on the earlier SOAK OS.
If you've made changes to your phone, from as simple as deleting bloatware from /system/app or installing safestrap, the SOAK install will fail. It's not a ROM being pushed/installed, it's a patch to the current ROM being pushed/installed. If you current ROM doesn't match what the SOAK is trying to patch it fails.
Things that usually don't affect OTA (or SOAK) installs are root and frozen apps/bloatware, the install will succeed and all your frozen apps will be unfrozen and root will be removed.
Things that always affect the OTA (SOAK) installs are alternate recoveries (Safestrap Recovery), deleted/renamed /system/app apks (removing bloatware, replacing system apps with other apps, merging app updates into /system/app and such....
If you've modified your phone, installed safestrap, etc.....going back to stock (via FXZ) is the BEST option to take if you want the SOAK and/or the OTA to install.