Any help is appreciated, I'm still fairly new with Android, but trying to learn my way around.
When the OTA update for 2.2.1 came out, I decided to do a factory reset because I'm just picky like that, and I like to be fresh coming out of OTA updates. Prior to the factory reset, I was running stock 2.2, though I was rooted using the manual (D2) method through adb, I had bloat frozen with Titanium Backup, and I had Droid X Bootstrap installed.
I unfroze the bloat and did the 2.2.1 update prior to factory reset. I did not unroot prior to the OTA. After the OTA I did a factory reset. I expected the bootstrap to go as well. It didn't, and I noticed immediately because I was booting into its recovery every other reboot because I was no longer rooted.
I still had the superuser icon (ninja) in the app drawer, however was no longer rooted of course, so I loaded z4root and let it "unroot" me, and then let it root again, which fixed the Bootstrap recovery issue.
Here's my problem. Obviously the factory reset did not wipe everything because bootstrap was still trying to load. My phone is definitely more sluggish than it was prior to the factory reset. Different types of screen lag are very noticeable and the phone really lags later in the day if I don't reboot. I loaded less apps after the reset than I had prior to, but otherwise did nothing different. I want to try to remove the bootstrap too, as well as anything residual to try to figure this out, even if I do have to factory reset again, because it's definitely not stable the way it is. Is it possible to remove it, and how so?
I'm aware that this may not fix the problem, and to me it doesn't even make sense that it would, but I definitely feel something "off" here and for my own peace of mind I'd like to remove it at least for now just to see. I've done factory resets before and the phone always feels much snappier once it's back up and running. This time it's worse than when I started.
Any assistance would be greatly appreciated.
You would have to flash a stock sbf. Correct me if I am wrong but I think that stands for system boot file. That should take care of everything. I am sure u can find the thread on the forum on how to do it. Just to mention I think that all the boot strap does is hijack your normal boot process by interrupting it allowing u access. It doesn't actually replace the boot process.
Sent from my DROIDX using XDA App
Info on the bootstrapper can be found here:
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
Basically it replaces the logwrapper.bin file which gets executed very early in the boot process. This allows bootstrapper to control the rest of the boot sequence.
To *just* remove bootstrapper, I think there is a backup of the original logwrapper executable stored in /system, so you could just replace the exploited version with the original.
However, if you are having issues, I would suggest you just go ahead and flash back to complete stock:
http://rootzwiki.com/index.php/Main-Page/Droid-X-Full-2.2-SBF.html
Make sure you are still on the 2.3.15 version before using this. Once you take the OTA (to 2.3.340) I don't think this SBF will work any longer.
So the sbf flash method wont work if u took the update?
Sent from my DROIDX using XDA App
sorry to hijack this thread. But I am having major issues with bootsrap. I accidently moved it from my sd card to internal storage. How do I move it back. It wont allow me.
crxin said:
So the sbf flash method wont work if u took the update?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
The .340 update "upgrades" your bootloader to 30.04. I've read that the 2.3.15 SBF will not work with this bootloader.
There are some SBF files produced by Team Black Hat (at Leaked 2.3.320 and patch files to put you to 2.3.340), but I've not used them.
I think you can find more info on those at mydroidworld (or you can support TBH by buying their app in the marketplace and downloading direct from there)
jaynyc22 said:
sorry to hijack this thread. But I am having major issues with bootsrap. I accidently moved it from my sd card to internal storage. How do I move it back. It wont allow me.
Click to expand...
Click to collapse
I'm not sure what you mean?
Try uninstalling from Manage Applications and re-install?
Do you mean the DroidXBootstrapper UI or the logwrapper exploit?
Related
Ok so this morning my alarm wakes me up and I noticed I had to unlock my phone to make it snooze, something didnt seem right as my alarm app usually comes up to the front and I can snooze without unlocking my screen. So what do I decide to do half asleep? I decide to reinstall the rom. Here are my steps, and I suggest you dont follow them.
1. Format system
2. Format data
3. Format cache
4. Mount system
5. Reboot phone (Swear this was an accident, as I was trying to navigate to the "install zip from sd card" option)
So my question is ,whats the quickest way to unbrick my phone. It just stays on the "M" boot logo. I found a couple of threads on different sites but want to make sure I"m using the latest method and for the Droid X. Thanks in advance
SysAdmNj said:
Ok so this morning my alarm wakes me up and I noticed I had to unlock my phone to make it snooze, something didnt seem right as my alarm app usually comes up to the front and I can snooze without unlocking my screen. So what do I decide to do half asleep? I decide to reinstall the rom. Here are my steps, and I suggest you dont follow them.
1. Format system
2. Format data
3. Format cache
4. Mount system
5. Reboot phone (Swear this was an accident, as I was trying to navigate to the "install zip from sd card" option)
So my question is ,whats the quickest way to unbrick my phone. It just stays on the "M" boot logo. I found a couple of threads on different sites but want to make sure I"m using the latest method and for the Droid X. Thanks in advance
Click to expand...
Click to collapse
Looks like an SBF is in your very near future.
Go to the Development subforum and search there.
If you have not applied the OTA 2.2 update, you will need the instructions to SBF back to 2.1 and then apply the 2.2 leak, and load your ROM from there.
If you have already done OTA 2.2, there is also an SBF that will restore /system only. It Might save you.
BE ABSOLUTELY SURE YOU DO NOT FLASH the 2.1SBF if you were on OTA 2.2. If you do, it will be game over.
Let us know how you fair.
One of the first things I did was the 2.2 ota when I got my phone.
Thanks, I will search there and report back.
SysAdmNj said:
One of the first things I did was the 2.2 ota when I got my phone.
Thanks, I will search there and report back.
Click to expand...
Click to collapse
Can you not get back into Clockwork if you pull your battery?? And they do have a 2.2 sbf that restores your system files.
MrDanger said:
Can you not get back into Clockwork if you pull your battery?? And they do have a 2.2 sbf that restores your system files.
Click to expand...
Click to collapse
if you hose /system you won't be able to get back into recovery. Recovery depends on the logwrapper in /system/bin. If it's gone, no recovery boot.
I'm guessing Format System pretty much took care of that
MrDanger said:
Can you not get back into Clockwork if you pull your battery?? And they do have a 2.2 sbf that restores your system files.
Click to expand...
Click to collapse
Zaphod-Beeblebrox said:
if you hose /system you won't be able to get back into recovery. Recovery depends on the logwrapper in /system/bin. If it's gone, no recovery boot.
I'm guessing Format System pretty much took care of that
Click to expand...
Click to collapse
Correct, I cannot get back into clockwork recovery.
I can get into android recovery but I cant do much from there.
Guys, is the ota 2.2 sbf I need SHADO_X6_2.3.13_SYSTEM-ONLY.zip
found here?
http://rootzwiki.com/index.php/Main-Page/Team-Black-Hat-does-it-again.html
SysAdmNj said:
Guys, is the ota 2.2 sbf I need SHADO_X6_2.3.13_SYSTEM-ONLY.zip
found here?
http://rootzwiki.com/index.php/Main-Page/Team-Black-Hat-does-it-again.html
Click to expand...
Click to collapse
Yes. I think that is your only hope at this point. If it doesn't work, I think you are SOL.
I did something very similar to this, flashing the 2.2 System SBF fixed it
I'm back up and running. Thanks people.
good for you man. seriously. just read a couple threads like this. makes me real nervous about flashing roms.
Not nervous since I have insurance
Seriously I caused my issue with a silly mistake. Usually its smooth sailing.
I downloaded the new update and installed it. Took me forever to get my root back but I finally got the phone where I want it. Unfortunately, the droid x is still trying to download the update which keeps failing. I contacted Motorola and they told me to do a factory rest and that might resolve the problem but they were unsure. How do I tell the phone it is up to date without having to reset everything?
If you do a factory reset, and the OS version is not .340, then the update did not work.
*DISCLAIMER - This Can Be Dangerous*
I would suggest using RSD Lite and the. 340 SBF to update the DX to the latest software version.
-----
Sent from my Droid X. Powered by Big Red, customized by NATF.
I did the update already and the system shows 2.3.340. All I am trying to change is the phone trying to download the update and continually failing.
I don't want to do a factory reset unless it is the last resort. I do have RSD Lite but I am a little leery of flashing the phone. Is there a full SBF file available for the 2.3.340 or can I just run the update again?
Sorry for all the questions I just don't want to brick the phone and I am new to all of this.
Olson-clan said:
I did the update already and the system shows 2.3.340. All I am trying to change is the phone trying to download the update and continually failing.
I don't want to do a factory reset unless it is the last resort. I do have RSD Lite but I am a little leery of flashing the phone. Is there a full SBF file available for the 2.3.340 or can I just run the update again?
Sorry for all the questions I just don't want to brick the phone and I am new to all of this.
Click to expand...
Click to collapse
If the phone keeps trying to update, then something is likely corrupt with the software. Try this as a test:
Reboot into Clockwork Recovery
Make a Nandroid backup
Do a factory reset and also wipe cache and data
Reboot and see if you still have .340 and get prompted for the update
If you still have .340 and get prompted, then you will most likely have to SBF and start over. You can always restore the Nandroid backup to go back to your original settings and data.
OK, I will try that. Noob question though, do I need to unroot before factory reset? If so, will I also need to delete superuser.apk or will the reset delete all of that?
Thanks for all your help.
There is no need to remove root first. If you lose it in the restore just run z4root again.
Also, just to clarify my last post, the Nandroid backup would only be used if a reset doesn't fix the problem. You would then be able to restore everything back and use a program like Titanium Backup to save your data in a format that could be restored over top of a new ROM.
-----
Sent from my Droid X. Powered by Big Red, customized by NATF.
Thanks for all your help and patience. Just one more bank of questions before I start this. Do I need to rename the bloatware I changed after rooting or will the reset take care of that? Once I reset, I will need to reroot to install the backup with Droid X bootstrap, correct? Lastly, worse case scenario I have to SBF to start over, is there a full 2.3.340 SBF out there?
There is a version of .340 that has most of the components of an SBF, but it is not the actual full release. I have .320 Full and .340 System-Only on my machine, and I used them both when first updating. After the .320 update is successful, you will only need the .340 System-Only until a newer one is leaked.
Once done with both SBF files, you will use Motorola's recovery to do a Format Cache and also a Factory Reset. This will put everything back to the day you opened the phone, without root and Clockwork.
When ready to root again, install z4root (available here on XDA), reboot, then run z4root and finally, install DX Bootstrapper. You will be all set to use Root Explorer and remove the bloat all over again. Before removing the bloat, I strongly suggest creating a Nandroid backup so that you can easily get it all back in the event you need to do a warranty exchange and the USB port stops working.
So here's the latest. Did a Nandroid back up and then cleared the cache followed by a factory reset. I didn't unroot or even flash the SBF files just to see what happened. The root was still there. I had to download root explorer again along with launcherpro but otherwise the phone was good to go. Checked system updates and low and behold, it was up to date!! So far it is working just fine, had to reinstall the apps I had before that I liked but all in all it's right where it needs to be. Thank you NotATreoFan for all your help.
On a side note, I had rooted the phone via the terminal emulator so I don't know if that made a difference in keeping the root. z4root may give different results.
Glad to hear it worked for you.
Hey guys, just sharing this with everyone. Maderschramm over at droidforums and droidxforums has packaged an update zip for 2.3.340. It can be used as an alternative to SBFing or to update you if you haven't already.
Install- Make a backup first
1. Download zip
2. Boot into clockwork recovery
3. Install zip from sd
4. Reboot
5. Activate phone
IMPORTANT
BE SURE TO REBOOT AFTER INSTALLING ZIP. DO NOT DO ANYTHING ELSE IN CLOCKWORK RECOVERY PRIOR TO REBOOT. YOU WILL BRICK.
You will lose root, but you will also still have all apps and contacts.
Read this thread prior to doing the install. There's some helpful tips from Maderschramm.
http://www.droidxforums.com/forum/droid-x-hacks/15666-maderstcok-ota-2-3-340-update-zip.html
Mirror 1
http://ubuntuone.com/p/XAk/
Mirror 2
http://www.megaupload.com/?d=4AO672L1
good find. I am going to download and store away for a rainy day ota update. I hate sbf and rsdlite. And although I appreciate all that the black hat does - having to do like 20 (exaggeration) installs in clock work makes me a little nervous.
so good on ya mate.
that's why after i SBF 2.3.320 i always go straight into Android recovery before booting up and Factory Reset there, then boot up. But i guess everybody has there own way of doing things.
Ya, this is an easy alternative to get everyone to a clean 2.3.340. If you're on 2.3.15, 2.3.320, or 2.3.340 this will definetly come in handy.
Wonderful. I just left a stock rom literally today and realized I lost corporate email access with Gummy. That is a deal-breaker and obviously I didn't research it well enough before doing it. I NEED to get back to stock regardless of how painful it is. So this will unroot me, just Z4 again afterwards I take it?
Correct it will unroot and remove bootstrap. So after rebooting then use z4 and grab bootstrap again.
Very nice, thank you! Hopefully I never need to use it!
Sent from my DROIDX using XDA App
Hopefully we wont need to use it, but at least we will feel better about doing this rather than an SBF.
Droid-Xer said:
Ya, this is an easy alternative to get everyone to a clean 2.3.340. If you're on 2.3.15, 2.3.320, or 2.3.340 this will definetly come in handy.
Click to expand...
Click to collapse
I don't know about 2.3.15 When I did it on that, I bricked and ended up having
to SBF to .320 and using the patches to get to .340
forever29 said:
I don't know about 2.3.15 When I did it on that, I bricked and ended up having
to SBF to .320 and using the patches to get to .340
Click to expand...
Click to collapse
Reasons for bricking:
Installing zip as an update.zip
Doing anything else in bootstrap after installing zip
Soft brick (factory reset will bring it back)
Thanks This has saved me more than once while working on cracking the bootloader
Hrmm I ran this directly from having Apex and it didnt like it. Seemed to not fully wipe the phone at all. Im guessing I didnt read something all the way. I simply went to clockwork and loaded the file and rebooted. When it came back my system was still intact, but everything was force closing.
r3dlined said:
Hrmm I ran this directly from having Apex and it didnt like it. Seemed to not fully wipe the phone at all. Im guessing I didnt read something all the way. I simply went to clockwork and loaded the file and rebooted. When it came back my system was still intact, but everything was force closing.
Click to expand...
Click to collapse
Doing a factory reset seemed to put it back to normal
It will update or bring you back to clean 2.3.340. You will lose root and bootstrap, but you will keep all apps and setup.
does anyone have any alternate DL links? it keeps hanging no matter which link I use.
Got it going. Honestly though, who uses Megaupload anymore?
Sent from my DROIDX using XDA App
i won't try to install until file size matches
r3dlined said:
Hrmm I ran this directly from having Apex and it didnt like it. Seemed to not fully wipe the phone at all. Im guessing I didnt read something all the way. I simply went to clockwork and loaded the file and rebooted. When it came back my system was still intact, but everything was force closing.
Click to expand...
Click to collapse
You didn't wipe cache and factory reset before install
Sent from my DROIDX using XDA App
If you don't wipe data/cache prior to install then you will have the same setup and apps, only you will have lost root and bootstrap. If you want a clean start then wipe data/cache then install zip.
WOW Droid X saver
Man this saved my Droid X from sure bricking, thankyou very much uploader
So I originally rooted using SuperOneClick, then I got an OTA that broke root. I then found gingerbreak and rooted using that method. I have done a few cool things, like change the boot animation and lock/unlock sounds, enabled sideloading, etc.
Anyway...
With rumors and speculation about Gingerbread coming out in the coming months (hopefully), I am wondering if the boot animations, lock sounds, and/or SuperUser access will deny the OTA from installing. Is it a good idea to return the ROM to stock to avoid any bugs?
Second,
Specifically on the Atrix, if I performed a factory reset, I assume I won't lose root access, but would I lose the boot animations, and lock/unlock sounds? Let's say I wanted to return it to a 100% stock ROM (un-root, stock boot animation, EVERYTHING) before the 2.3 update comes, how would I do it? I feel as though if I perform an OTA with the mods I've done to it, some unknown bugs/issues would appear (I've seen PLENTY of bugs as is). Can anyone shed some light on this? Call me paranoid, but I've seen too many software issues with this phone, and I'm hoping 2.3 will address them, and I hope I don't introduce any new bugs by updating a modded phone.
You should definitely go back to stock. I doubt that you'll even be prompted if you're rooted, so you won't get the update to Gingerbread. Instructions to return to stock can be found on Motorola's website, by Googling, or from Android Central.
If I do a hard reset using Android Recovery, will that effectively unroot and restore EVERYTHING to the factory image? I know if I do a soft reset through the OS, I will still have root access. I realize I can just unroot using SOC, but there have been issues where busybox is still installed along with the superuser icon, even though the phone doesn't have root access. I just want a clean slate.
rytymu said:
If I do a hard reset using Android Recovery, will that effectively unroot and restore EVERYTHING to the factory image? I know if I do a soft reset through the OS, I will still have root access. I realize I can just unroot using SOC, but there have been issues where busybox is still installed along with the superuser icon, even though the phone doesn't have root access. I just want a clean slate.
Click to expand...
Click to collapse
Try this.
Motorola
brewstermax said:
Try this.
Motorola
Click to expand...
Click to collapse
I have 4.1.83, and this will not work for it.
I would be interested in learning more about this too
Sent from my MB860 using XDA Premium App
This is a thread I commented on over at the Motorola forums. I actually got the forum manager to comment on the issue:
"rytymu
What do I do if I'm on 4.1.83 and want to return to stock (rooted)? The software given just says my device is up to date...
Mark (Forums Manager)
With next update/upgrade you will go up to next stock version. You have to
wait til then.
rytymu
So if I understand right:
I most likely will not get an OTA notification because of the root access, so when I run the Motorola Software Update program after the next update comes out, it will then flash a 100% stock image as if I just pulled it out of the box? This includes removing/wiping busybox, root access, boot animations, and EVERYTHING else?
Mark (Forums Manager)
If you are on 4.1.83 but modded you will get ota notification but will
likely fail on install. If MSU is made available you can update /upgrade to
that version. Root and other sideloaded things will be removed. Stock ATRIX
Att software. Not AOSP Android."
I guess this is what I'm looking for, unless someone interprets otherwise...
brewstermax said:
You should definitely go back to stock. I doubt that you'll even be prompted if you're rooted, so you won't get the update to Gingerbread. Instructions to return to stock can be found on Motorola's website, by Googling, or from Android Central.
Click to expand...
Click to collapse
OTA update should be fine if you have not deleted any of the original Moto files/bloatware, or leave any of the original Moto bloatware frozen. The updates only throw up at you when there are missing or frozen Moto apps and/or files.
If you are on 4.1.83, (or any firmware), and rooted only, you will get the update fine, but will lose root.
If you have flashed for example GladiAtrix, you will more than likely have to flash back to stock first.
If you have rooted on any version and then frozen any apps, thaw those apps and you will update fine, but again lose root.
Every time you update you lose root.
So I have frozen all bloat, but I did uninstall swype and reinstall a newer version. Is this going to be a problem for the next ota? Am I going to have to do a fresh sbf flash or is there a way to reinstall the stock version of swype? I'm not sure I still even have that file...
Sent from my MB860
beazie0885 said:
So I have frozen all bloat, but I did uninstall swype and reinstall a newer version. Is this going to be a problem for the next ota? Am I going to have to do a fresh sbf flash or is there a way to reinstall the stock version of swype? I'm not sure I still even have that file...
Sent from my MB860
Click to expand...
Click to collapse
If you installed a newer version of the same Swype, this should I imagine be the same as updating Swype. I'm thinking this would allow you to just unfreeze all the bloatware and update OTA. Only thing I can think of is that you try the OTA when it's available, and if it balks at you, flash back to stock.
I just followed another thread on XDA, and flashed to 1.26. After about 40 minutes, I had a fresh install. I then did a factory reset, as I was told that some user data and caches aren't touched by flashing (?). I did it just for good measure. I then went into the menu and updated to 4.1.57. I was tipped off (in an above post, actually) about some Motorola Softare Update program that will flash you from 4.1.57 to 4.1.83. The forum manager at Motorola instructed to do this to basiclly restore your phone if you had modified it (to clear the OTA check). Again, just for good measure, I used this to flash from 4.1.57 to 4.1.83 to be 100% sure I had a bone-stock phone.
Sent from my MB860 using XDA App
rytymu said:
I just followed another thread on XDA, and flashed to 1.26. After about 40 minutes, I had a fresh install. I then did a factory reset, as I was told that some user data and caches aren't touched by flashing (?). I did it just for good measure. I then went into the menu and updated to 4.1.57. Now, I'm actually in the "soak" beta feedback over at the motorola forums, and I was tipped off (in an above post, actually) about some Motorola Softare Update program that will flash you from 4.1.57 to 4.1.83. The forum manager instructed to do this to basiclly restore your phone if you had modified it (to clear the OTA check). Again, just for good measure, I used this to flash from 4.1.57 to 4.1.83 to be 100% sure I had a bone-stock phone.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
The Moto Software Update is not needed, and Mark, or whoever over on the Moto forums did not "tip" you off to this. This is no secret, and is well known. (BTW, you are breaking the NDA just by saying you are in beta, (soak feedback forums are down in any event as they are always taken down between betas), but that's another story, and being in beta doesn't make you more knowledgeable either).
You have made this sound more complex than it is.
To go back to stock (and the instructions are all over the forums BTW) --->
Flash 4.1.26, OTA to 4.1.57, OTA to 4.1.83!..............Done!
Or ------------>
Flash 4.1.57 sbf, OTA to 4.1.83!..................Done!
People who were having the OTA notification issues, (continually popping up), were those who flashed the 4.1.83 sbf which is floating around, and that's why they were told to flash 4.1.83 through the Moto Update portal.
(Edited above statement)
Sent from my MB860 using XDA App
I know I have to clear cache and data but do I have to manually mount system? Also do I need to unfreeze any frozen apps? I am currently on. 340. Thanks.
Sent from my DROIDX using XDA App
Personally, all of the AIO installs have been nothing but problematic for me.
What I recommend is this:
Download the .602 sbf boot disk from HERE
There should be no need to delete any of your data so you should not loose anything.
From there, manually check for an update from verizon and it will install the .605 update.
Then, run Pete's Motorola Root Tools from HERE and you are done.
I know it seems like a bit, but I seriously tried the AIO in 3 different versions and each time it totally screwed my phone up (but I always keep a backup so I just had to sbf then restore.. but still wasted a lot of time)
Good luck
D.