Related
Current phone information should be attached. Short form is, I'm using the Gummi 1.2.0 rom, put onto my phone after using safestrap (and following the instructions to make a backup before doing so). Safesystem is enabled.
Two backups: located on my external SD card
nonsafe-2012-05-26.07.52.54/
safe-2012-05-27.08.06.28/
Safestrap recovery v1.09 (afraid to update to 2.0 without breaking more stuff)
What I'm looking to do is return my phone to working stock, which I believe was Gingerbread 2.3.6. That said, every time I've touched this thing trying to go back, I've black screened it. I don't live in an area with 4g (screw the mountains, and their 1x service), so any attempts to connect to the 4g network for any part of the process will require me driving into Pennsylvania, 30 minutes away. I've heard before that you can't return from the ICS leak to the Stock for the Droid 4, for various reasons (but i believe the important one was it was a later firmware and it isn't a process designed to go backwards)
I'd like to know if thats still the case currently, or if something has changed. I'm getting shaky wifi/data/cell reception up here, and its flawless back on stock. Hell, I've got an old razor as an emergency phone that's flawless up here. Next time I'll do more research for this stuff I was a proud OG droid owner, and ran cyanogenmod on it before the vid card fried one evening. Thought the droid 4 would be a good deal, but I've had nothing but trouble with the roms on it.
All that said, I can simply smash and return this droid if its the only way to get a stock one back, but I don't like destroying useful and good technology when I can help it. Besides, I like fixing the problems I create.
Thanks for the help XDA, either way.
-- TheChaoticDoctor
Did you flash the leak ICS from Motorola or did you use Safestrap and flash Gummy ICS?
If you flashed the leaked ICS, there is no going back. You will need to find get the files to flash the partial .219 system back so you can run the .206 leak update again.
If you just used safestrap to flash Gummy 1.2.0 then you can use the .219 flash files to completely re-do your phone.
Currently there are no ROMs to flash if you are on the leak, Hashcode just released his Safestrap 2.0 to do so but still nothing to flash. All the current ICS ROM builds are for the stock phone running the Gingerbread Kernel.
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
TheChaoticDoctor said:
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
Click to expand...
Click to collapse
You should probably go up to .208, that's the latest leak. Make sure to use rootkeeper, and follow all the instructions. So far I haven't lost root, but be aware I'm stuck on .206 because I don't want to lose root....
Look here for more info:
http://forum.xda-developers.com/showthread.php?p=26311439
Sent from my XT894 running ICS
First of all, it sounds to me like you've just flashed a ROM, not flashed the leak. If that is the case, you can just toggle the safe mode in safestrap to get back to stock. Safestrap lets you toggle between stock and the ROM. It is pretty awesome because you can play with the ROM and then go back to stock whenever you need to.
If you HAVE flashed the Motorola leak (as opposed to just a ROM) you are SOL.
If you haven't flashed the Motorola leak and just want to get back to factory conditions, you'll have to flash via RSDLite. That info you should be able to find here:
http://forum.xda-developers.com/showthread.php?t=1622256
Honestly I WOULD NOT flash the leak at this time. IMHO, it doesn't really offer enough to risk getting off the upgrade path forever, and losing the ability to flash back via RSDLite.
Hey guys.. My System Version is listed as being 6.13.215.XT894.Verizon.en.us. (This phone is about a week or 2 old for me) I have installed safetsrap recovery just to see how it works etc and have successfully installed the Eclipse port on the non-safe system. Now that I am done having fun with that, I would like to upgrade my system to newer leaked versions. My question is this: Should I uninstall safestrap before attempting to flash any of the leaked updates? How should I go about removing safestrap the "best" way? Also could someone please enlighten me with the correct "order" of these releases? EG: 6.11.200, 6.11.202, 206 etc. I guess I'm confused bc my system version starts with 6.13 instead of 6.11. Any help much appreciated!
I'm in the same boat as you, safestrap w/eclipse setup and I think I want to just switch to ICS 211
Pretty sure there are 2 methods, one with fastboot, and one with safestrap.
Fastboot method (droidforums.net/forum/droid-4-roms/212634-simplified-211-update-guide.html) definitely requires you to uninstall safestrap, but I think that automatically happens when you flash w/stock 219.
Safestrap method (droidforums.net/forum/search.php?searchid=4780372) allows you to just use a 211 ICS rom. But, I'm not sure if you already have to have done the fastboot ICS, I think you may have to fastboot ICS then install safestrap and safestrap into 211 ICS from 206 or 208 ICS.... Anyways, that's about where I am right now, trying to figure out if I safestrap to a 211 ICS rom from my current stock 219 GB, will it brick my phone. :/
---------- Post added at 12:46 PM ---------- Previous post was at 12:38 PM ----------
Oh also (droidforums.net/forum/droid-news/212864-another-ics-leak-here-droid-4-maybe-closer-ota.html) says that "212 ICS should be leaked soon". You may want to just hold tight, lots of new leaks means that something big (and easy to install for noobs like me ) may be coming soon .
The adventure continues...
Thanks for the quick response man... I'm glad to see I'm not the only one in this situation! I've been "creeping" on this board for 2 years now, (which I can't believe how fast that time went by) and thought it was about time that I start posting etc... you know what I mean, I see that was your 4th post so, that makes 2 situations where we are in the same boat! Thanks for the links brother I have actually read those, but need to checkup on them again... ALSO, my system downloaded an update the other day, (OTA) and was automatically going to install it (I clicked on download, thinking it would just download and wait for me to do the install manually like i have been used to in the past...) So, I tried to interrupt the download by throwing my phone into airplane mode really quick and then forcing a shutdown. Next time I turned on my phone I end up seeing the "Green Android with a triangle" screen, and a progress meter.. and I KNOW what that means. Something was flashed automatically by the phone. I got nervous, but my phone booted up perfectly, and I still had root, along with safestrap intact. I'm still a bit confused by what might've happened, but am relieved that my phone is still working perfectly... strangeness. I'll update this thread w any more info I can find. Thanks again!
Time out guys! First off, you cannot flash the ICS leaks in safestrap. The leaks are updates, not full ROMs. Second, you cannot flash a ROM based off the ICS leaks in safestrap unless you update you stock system to an ICS leak first. Well, you probably could, but it wouldn't boot. If you are on GB .215 you will need to update to .219 first. If you are on GB .219, and have not installed safestrap, you should be able to flash the an ICS leak via stock recovery without fastbooting. If you have installed safestrap, I believe you have to fastboot using the .219 file since safestrap changes something in the build.prop that will cause the leak update to fail.
The Optimizer said:
Thanks for the quick response man... I'm glad to see I'm not the only one in this situation! I've been "creeping" on this board for 2 years now, (which I can't believe how fast that time went by) and thought it was about time that I start posting etc... you know what I mean, I see that was your 4th post so, that makes 2 situations where we are in the same boat! Thanks for the links brother I have actually read those, but need to checkup on them again... ALSO, my system downloaded an update the other day, (OTA) and was automatically going to install it (I clicked on download, thinking it would just download and wait for me to do the install manually like i have been used to in the past...) So, I tried to interrupt the download by throwing my phone into airplane mode really quick and then forcing a shutdown. Next time I turned on my phone I end up seeing the "Green Android with a triangle" screen, and a progress meter.. and I KNOW what that means. Something was flashed automatically by the phone. I got nervous, but my phone booted up perfectly, and I still had root, along with safestrap intact. I'm still a bit confused by what might've happened, but am relieved that my phone is still working perfectly... strangeness. I'll update this thread w any more info I can find. Thanks again!
Click to expand...
Click to collapse
Yup, same here, I'm just taking as much info in right now as possible. I think our options are eclipse, stock 219 with frozen apps, or ICS. Oh if you use stock at all, I'd recommend upgrading to 219, I think that was a major update, my battery life has just about doubled... then again I only had my phone for about a week before upgrading, and about 3 weeks total now.
kwyrt said:
Time out guys! First off, you cannot flash the ICS leaks in safestrap. The leaks are updates, not full ROMs. Second, you cannot flash a ROM based off the ICS leaks in safestrap unless you update you stock system to an ICS leak first. Well, you probably could, but it wouldn't boot. If you are on GB .215 you will need to update to .219 first. If you are on GB .219, and have not installed safestrap, you should be able to flash the an ICS leak via stock recovery without fastbooting. If you have installed safestrap, I believe you have to fastboot using the .219 file since safestrap changes something in the build.prop that will cause the leak update to fail.
Click to expand...
Click to collapse
Thanks for clarifying that ^^, kwyrt, I've read some of your other posts they are always quite informative!
Glad I could help! There are a LOT of nice, helpful people in these forums. Just keep asking questions! Doing some of this stuff can be nerve wracking even if you know what your doing. I actually, finally, got up the nerve to jump on the ICS leak train last night. If you decide to take the leap, I highly recommend using jsnweitzel's Droid 4 Utility located here: http://forum.xda-developers.com/showthread.php?t=1714596. Made the process much easier than it has any right to be.
Android 4.0.4 flash Success! =)
So I decided to take the leap last night... first thing I did was every way of factory resetting I know how to do hehe. (Privacy, factory reset under settings, then a data and dalvik clear in recovery) Downloaded the GB219 file, put it on my SD, fired up the Droid 4 Utility (thanks to everyone who contributed!) and had no problems at all upgrading. I wasn't worried about root so I skipped the OTA rootkeeper process. Next I needed to get to an ICS build. Again, I used the Droid 4 utility.... only difference being that we had to flash the boot.img file first.. (ICSFIX.img). On my first go, I successfully flashed the new boot.img (ICSFIX), but then got a sig verification error when trying to flash the OTA zip. ****. Soft brick at 2AM... heh. at least I still had plenty of time. Re-DL the OTA file, copied it over again and repeated the entire procedure, this time with success. Really Glad I decided to upgrade! Thanks guys!
Yesterday i flashed if i remember the 223 leak. I flashed from 905, rooted with razor ics root. I went in to sqlite and changed the setting to get the free hotspot and than rebooted. Now on my top banner the wifi icon and my signal icon stay gray! They never got to blue! I have data service but the are always gray. Also later my signal strength went noticeably lower than before i flashed! Any help would be great! ...... also i just noticed that my browser is talking! Had chrome installed, couldn't find anything in the settings so i uninstalled and went to reinstall. Play store says that NOW its not compatible with my device! And now my stock browser is talking to me! PLEASE HELP!!!!!!
Sent from my DROID BIONIC using xda app-developers app
One thing at a tine.
Browser talking - check you're accessibility settings, see if Talkback is enabled.
For the GNow, that does not come with the ICS leaks. Either you installed an unofficial leak, or you installed GNow before the leak, or you installed it after the leak. There is a thread in XDA that details how to get GNow working in ICS.
For the sqlite mod, change the string back. Foxfi is free, doesn't require root, and works.
Sent from my rooted BIONIC running ICS 6.7.235 via Tapatalk 2
Thanks, I FXZed back and reloaded everything no sqlite no root and everything seems good! Still lost data for a while last night but l don't have great service at home! Might root later today, we'll see!
Sent from my DROID BIONIC using xda app-developers app
I do have one more question! If i go from .233 can i just flash .235 or do i need to FXZ again?
Sent from my DROID BIONIC using xda app-developers app
Each time you try to flash a new ics leak you HAVE TO FLASH BACK TO 902/905
if you flash to 235 YOU CAN NOT FLASH BACK TO 902/905 but you can only move foward
I recommend you stay on 232 unless you dont care about flashing back to gb
bhp117 said:
Each time you try to flash a new ics leak you HAVE TO FLASH BACK TO 902/905
if you flash to 235 YOU CAN NOT FLASH BACK TO 902/905 but you can only move foward
I recommend you stay on 232 unless you dont care about flashing back to gb
Click to expand...
Click to collapse
If people are going to keep stating this, then they need to qualify it with the fact that you can still install GB roms on the safe side. You can even put .905 stock back on safe or unsafe using the backup restore within Safestrap (if you have the stock .905 backup file that is). There's a lot of scare about .235, but all you have to do is change how you flash and you don't "lose" anything. **Wonder if I will have to make another tutorial for people on .235...goodness**
What? We have a locked boot loader... can't run .235 on one side and .905 on the other lol
What he said was correct.. you cannot use RSD lite to fxz back to .902/.905 with .235 so unless you're a fool don't make the move... 232 is great
Finally Iced Out Legitimately... Bionic is back
You cannot go back to fully stock Gingerbread anything once you flash .235 so for the sake of newer users being thrown off the upgrade path and not being able to FXZ back to .905 we all should just leave it at that.
cnorman76 said:
I do have one more question! If i go from .233 can i just flash .235 or do i need to FXZ again?
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
I think you've gotten the gist of the info, but I'll reiterate.
You have to be on .905 to flash any of the current ICS leaks (and there is a 99% chance of that being true with any future leaks / soak tests / final OTA b/c .905 is the current official OS version for the BIONIC.
You can flash .235 off of .905, but once you are in .235, you cannot restore your phone to .905 via FXZ, and you cannot try to fool the system with a simple Nandroid backup of .905 that you restore over .235. The reason is that the update script also looks to patch several things.
First of all, no update script ever includes the boot.img of the version that is being installed. It includes a patch file that requires you to have either the boot.img of the system that you are coming from, or the system that you are going to. Any other version and it throws up an error and does not allow the update to continue. IOW, if, say, leak .241 comes out, and you're on .235, you have no way to getting .241 without using a method to make the .241 kernel. You cannot flash the .905 kernel onto a .235 system - it trips eFuse and bricks the phone. You have no .241 kernel to install b/c, as I said, the update only includes a patch file, not the full kernel.
Second, even provide that you pass that (which in theory you might as you are on a .235 leak with only .905 /system restored from a Nandroid backup, and if the new leak uses the exact same kernel you'll pass), it also verifies every file in /system that it is going to patch, along with every file in /preinstall that you are going to patch. Restoring that Nandroid backup does wonders for having the .905 /system on your phone, but the current leak you are on has already patched several files in /preinstall, so those signatures will not match, and you'll fail the verification step, and ultimately the update will fail.
For the record, a typical FXZ flashes 17 different partitions on our phones. Nandroid backups on the BIONIC typically can only make backups of 3-4 of those partitions. We have figured out ways to grab a few more of them, but we are still stuck at grabbing a couple of them, and there are 4-5 that we cannot grab from our phones at all.
Since the folks with RAZRs went through something very similar in May and June, mattlgroff figured out a way to fool the update into thinking you have all the components correct in place that need to be there, and the update proceeds. Thus far, after bricking my phone trying to FXZ back to .905 / .902, I used a script to get back on .235, then verified that the move to reinstall the .235 leak works. If another leak is found, then I can test the second part of the script, that which allows new leaks to be installed. The script does not allow any older ICS leak to be installed, and currently there is no way to go back to a previous leak nor a previous GB stock FXZ at all. Even if we had a .223X ICS FXZ or a .22X ICS FXZ or a .230/.232 FXZ, they would not work on a phone that has been updated to .235.
That is why we're saying hold off unless you're 100% positive you're willing to accept the risk - this is way beyond the risk associated with rooting your phone. If Motorola makes the next leak force the phone to have components from .905 that we cannot flash into a .235 upgraded phone, I (and several others that have taken the plunge) might be permanently stuck on .235 until an FXZ for a version of ICS higher than or equal to .235 is released. And that typically takes 6-8 weeks.
HTH
crobs808 said:
If people are going to keep stating this, then they need to qualify it with the fact that you can still install GB roms on the safe side. You can even put .905 stock back on safe or unsafe using the backup restore within Safestrap (if you have the stock .905 backup file that is). There's a lot of scare about .235, but all you have to do is change how you flash and you don't "lose" anything. **Wonder if I will have to make another tutorial for people on .235...goodness**
Click to expand...
Click to collapse
Make a guide if you will and state the proper steps to do so
I had one issue with. 232. I noticed the lock screen is useless. My home button unlicked the screen plus the notification bar scrolled down to unlock also lol. Other that that it amazing
Sent from my DROID BIONIC using xda app-developers app
dblkspecial said:
I had one issue with. 232. I noticed the lock screen is useless. My home button unlicked the screen plus the notification bar scrolled down to unlock also lol. Other that that it amazing
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
i noticed that the other day when I got a text while my screen was locked. I naturally pulled the notification bar down and noticed that I didn't unlock my phone at first. Tried it just now and it's unlocking without swiping to unlock. My home button doesn't do anything howerver.
Hi guys, my mom has the Droid 4. I initially put her on the ICS leak 6.16.208 when it first came out. When the official ICS release (I think it was .219 or something) came out in August, since the .208 leak was working fine for her, I just left her phone alone. Now I see that there's finally a JB update for the Droid 4, and I'm wondering what would be a safe way to get from the ICS leak to the JB OTA.
Would I have to get from the ICS leak to the final version of ICS first, and then update to JB? Or is there another way to go about this? I apologize for asking; I've tried to research this on my own and I just find a clutter of threads that never really seem to talk about how to get off a leaked build.
I have Safestrap Recovery v2.0.0 installed. The unsafe system is the .208 leak, and the safe system is a custom ROM she didn't end up liking (a rather buggy AOKP port), so she just runs the .208 leak all the time.
Would anyone have any insight as to how I could proceed to ultimately get onto the JB OTA? If someone could just point me in the right direction, I'd really appreciate it. Thanks in advance.
I'd probably use the Fastboot/RSD Lite method to flash the release version of ICS, and then update to JB from there. My Droid 4 on GSM thread includes a section on how to flash ICS via Fastboot.
Hopefully we'll eventually get Fastboot files to go straight to JB, but I haven't seen them yet.
Lum_UK said:
I'd probably use the Fastboot/RSD Lite method to flash the release version of ICS, and then update to JB from there. My Droid 4 on GSM thread includes a section on how to flash ICS via Fastboot.
Hopefully we'll eventually get Fastboot files to go straight to JB, but I haven't seen them yet.
Click to expand...
Click to collapse
Thank you so much for your fast response and for writing this guide.
So from what I understand, just fastboot to the OTA ICS and then I can get to the JB OTA from there with the update.zip, right? Will fastboot wipe my data?
Also, is that "Upgrading to Jelly Bean" going to take me to the actual official JB OTA (not a leak)? Because it looks like the link lets you download 6.16.217 which I believe is the finalized JB OTA, correct? If so, that's very exciting. I was anticipating that I would have to wait for Verizon to actually push the JB OTA to me.
Once again, thanks a lot!
This is currently a "soak test". There is a chance that problems could be found with it, though with all the previous soak tests, the official version has followed a few days later and been exactly the same.
If you want to be really sure, you should wait until someone confirms that the two are the same.
Unfortunately I cannot remember if fastboot wipes your data as I tend to wipe my data after an upgrade anyway. If you're rooted I'd suggest you run Titanium Backup to be sure.
I'll use TiBu just to be sure. I actually just read an article that the JB OTA is currently rolling out, so I guess this should be the final version. Thanks for the help!
So its been awhile since I flashed a ROM to my BIONIC. That was back before ICS was even released for the BIONIC. So I started looking at updating to one of the more stable ROMS that has way better performance that this stock one. Currently I have 6.7.232 on my phone and I would like advice on which ROMs are best for this device. I have looked into some such as Gameblur, Raging Bionic, and Icarus HD. Thus far I havent really decided on one but I have noticed that some of them are on Jelly Bean. I am not sure if I have to return to the OTA path to update to any of these. I also have Safestrap 3.11 installed. Any advice would be appreciated. thanks.
Any help out there?? Thanks.
HarielA4 said:
I have looked into some such as Gameblur, Raging Bionic, and Icarus HD. Thus far I havent really decided on one but I have noticed that some of them are on Jelly Bean. I am not sure if I have to return to the OTA path to update to any of these. I also have Safestrap 3.11 installed. Any advice would be appreciated. thanks.
Click to expand...
Click to collapse
Well Gameblur and Raging Bionic both require one to be on the 98.72.22 Moto 4.1.2 Jellybean update. Incarus HD however is ICS base and can be flashed with your current setup.
If you are destine to update your stock side I would first prep what you currently have on there right now. See this HERE for getting stuff ready.
I would backup anything on the internal storage before hand and make sure that you have a full battery.
You will find the proper FXZ files HERE. If you are on 6.7.2-223 update then use the one for 4.0.4. It would be easier to root again through the update process. After you have completed the restore processes and root through the HOB. Make sure you have VooDoo Root Keeper installed on your phone to back up Root and to disable Root. Then with a good Data connection you are going to take the update Via OTA. Once the update is complete and you are fully booted up. Use VooDoo to restore your Root and test using root explore or NoFrills CPU.
nobe1976 said:
See this HERE for getting stuff ready.
Click to expand...
Click to collapse
The link provided there has a post from the OP that states House of Bionic is discontinued and to use House of Moto. Should I do that?
Secondly I havent for sure decided which Rom I will be moving to. I feel that the interface I have been using is kinda laggy. I installed Next launcher to see if that made a difference and it was more responsive but still my system memory usage skyrockets after a couple hours and sometimes the only way to resolve it is to restart the device. Any recommendations as to which Rom I should move to?
HarielA4 said:
The link provided there has a post from the OP that states House of Bionic is discontinued and to use House of Moto. Should I do that?
Click to expand...
Click to collapse
You can try using the House of Moto stuff also depending on what you feel more comfortable on using. The HOM was desighned to have one interface for all Moto devices instead of each having its own individual setup. I would still use HOB for your purpose only because I don't know if he added in the script to root the device, which was made for ICS versions not JB hence the discontinued portion of it.
HarielA4 said:
Secondly I havent for sure decided which Rom I will be moving to. I feel that the interface I have been using is kinda laggy. I installed Next launcher to see if that made a difference and it was more responsive but still my system memory usage skyrockets after a couple hours and sometimes the only way to resolve it is to restart the device. Any recommendations as to which Rom I should move to?
Click to expand...
Click to collapse
I have tested and played around with a lot of different ROMs and tweaks to find the one that I am ultimately satisfied with. Flying Jelly, well the name speaks for itself, Rage, and GameBlur (which I had minor help in) all work fine for there purpose.. One must pick and choose which one suits there purpose. So my suggestion would be to install SafeStrap 3.60, which is the latest updated one, and create a few slots and run each the same as you would Stock or any other firmware to measure which one suits your needs.....
In a previous post you wrote "If you are on 6.7.2-223 update then use the one for 4.0.4.". I went to the FXZ site and it shows that the 4.04 rom has version 6.7.223 on it already. I already have root. Why would I need to install the same version again and reinstall root to get on the OTA. I just want to make sure I understand this to avoid making mistakes. Thanks.
Then if you feel confedent that all will go well then just install Voodoo to backup and disable root. Take the OTA update and see if it will install. The most that will happen is that if it detects that something is missing from the current firmware you have the installation process will fail and reboot back into what you currently have. At that point you will have to FXZ your stock back to the way it was installed originally, root, then backup root and disable, then take the OTA. ICS is way easier to root then JB. I have kept Root before via OTA when I got it, so I know it Voodoo will keep the backup and install it..
nobe1976 said:
Then if you feel confedent that all will go well then just install Voodoo to backup and disable root. Take the OTA update and see if it will install. The most that will happen is that if it detects that something is missing from the current firmware you have the installation process will fail and reboot back into what you currently have. At that point you will have to FXZ your stock back to the way it was installed originally, root, then backup root and disable, then take the OTA. ICS is way easier to root then JB. I have kept Root before via OTA when I got it, so I know it Voodoo will keep the backup and install it..
Click to expand...
Click to collapse
I think I miscommunicated what my question was. The instructions say to install the FXZ for the 4.0.4 that has the same version of Android OS that is currently installed. the further instructions say to install the OTA from verizon but everytime I check for an update nothing shows up on my phone. Where else can I get the OTA?
In addition I want to know what I should do about safestrap. Should I remove it before installing the OTA or is it fine to leave as is when I go to install the OTA?
OK... If you cannot even get Big Red to send you the update. You can fxz the update, but at that point you will loose root, but have the option to keep your current data. Go see House of Moto or House of Bionic over at droidrazr.com
As far as Safestrap I would just uninstall recovery through the app the reboot so it clears out before the fxz process.
$3π+ £®m€ ×X× BiOπI¢ oπ $ø|/|£ťhïñğ ¢ű$ț¤|/|
fyi I think he took House of Bionic down, didn't see a link. I can however attest that House of Moto worked perfectly fine. Flashed fresh .232 and VZW sent me the OTA (I tried voodoo rootkeeper before updating). I did lose root despite following all of the steps. To get it back your best bet is to boot up a live Ubuntu disc. I tried the VM that someone compiled but it kept failing.
PS: nobe1976, how the hell did you fit 3 ROMS on your phone? I can only fit one ROM (besides obviously stock). Wish we could install ROMs through safestrap to SD (internal or external).
mikemikemikexxx said:
fyi I think he took House of Bionic down, didn't see a link. I can however attest that House of Moto worked perfectly fine. Flashed fresh .232 and VZW sent me the OTA (I tried voodoo rootkeeper before updating). I did lose root despite following all of the steps. To get it back your best bet is to boot up a live Ubuntu disc. I tried the VM that someone compiled but it kept failing.
PS: nobe1976, how the hell did you fit 3 ROMS on your phone? I can only fit one ROM (besides obviously stock). Wish we could install ROMs through safestrap to SD (internal or external).
Click to expand...
Click to collapse
This is the Exploit I have been using the past few days.. HERE.
However Samuri didn't remove the HOB site, He just doesn't maintain it as much since HOM. Here is the LINK to that f needed.