Related
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?
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've been trying to flash back to factory, and I got RSD Lite and the SBF file, and the program and everything recognizes the phone in bootloader.
However, when I go to run the process, it goes through 'creating disk image' really fast, then says 'phone is not compatible with multi-interface super-file'.
What do I do? I didn't brick it, but It won't boot, all I get is the boot image till it runs out of battery.
HELP??
thatkidoptimus said:
So I've been trying to flash back to factory, and I got RSD Lite and the SBF file, and the program and everything recognizes the phone in bootloader.
However, when I go to run the process, it goes through 'creating disk image' really fast, then says 'phone is not compatible with multi-interface super-file'.
What do I do? I didn't brick it, but It won't boot, all I get is the boot image till it runs out of battery.
HELP??
Click to expand...
Click to collapse
Make sure to plug the phone in to the wall charger and let it charge to a full charge. Then unplug the wall charger, pull the battery. Then plug the wall charger back in with the battery still out. Put the battery back in and power up the phone. It should boot to bootstrap recovery. From there, you can restore a backup.
As for SBF: Are you on 2.3.340? If so, flash this file via bootstrap recovery:
http://www.megaupload.com/?d=4AO672L1
This is maderstcok .340. It is basically a clean system flashable zip that is pre-rooted. Will get you back to a clean slate.
ONLY USE THIS if you are 2.3.32 leak or 2.3.34 already. Here is the original page about it on droidxforums:
http://www.droidxforums.com/forum/droid-x-hacks/15666-maderstcok-ota-2-3-340-update-zip.html
SysAdmin-X said:
Make sure to plug the phone in to the wall charger and let it charge to a full charge. Then unplug the wall charger, pull the battery. Then plug the wall charger back in with the battery still out. Put the battery back in and power up the phone. It should boot to bootstrap recovery. From there, you can restore a backup.
As for SBF: Are you on 2.3.340? If so, flash this file via bootstrap recovery:
This is maderstcok .340. It is basically a clean system flashable zip that is pre-rooted. Will get you back to a clean slate.
ONLY USE THIS if you are 2.3.32 leak or 2.3.34 already. Here is the original page about it on droidxforums:
Click to expand...
Click to collapse
Ok, charging now. What if I don't have a backup? It's not my phone, and I can't guarantee this guy was smart enough to do one...
Then download the maderstcok file on your pc, move to your sd, manually boot into clockwork and install the zip from sd. It will work on any system version from 2.3.15 and up. If that doesn't work and there's no backup. Try wiping data/cache and reboot.
And if you're SBFing what is the bootloader?
For 30.04 you need the full SBF for 2.3.320 or system only 2.3.340 along with rsdlite 4.8+
For 30.03 you need the full SBF for 2.3.15 or 2.3.320 along with rsdlite 4.6+
So do I have this right? If I am on 2.3.340 there is no need to sbf? Simply use the maderstock image and restore it to be back to stock and that will accept OTA updates?
rocko73 said:
So do I have this right? If I am on 2.3.340 there is no need to sbf? Simply use the maderstock image and restore it to be back to stock and that will accept OTA updates?
Click to expand...
Click to collapse
Yes, you could use Maderstcok if you feel more comfortable flashing files. Just an FYI in case you didnt know, there is now a full 2.3.340 sbf... You can find it at mydroidworld
I also have a link in my guide in the Droid X general forum
SysAdmin-X said:
Yes, you could use Maderstcok if you feel more comfortable flashing files. Just an FYI in case you didnt know, there is now a full 2.3.340 sbf... You can find it at mydroidworld
I also have a link in my guide in the Droid X general forum
Click to expand...
Click to collapse
Nice info. One quick question. I have never had to reactivate my phone after installing any of these roms. Is using the sbf file or maderstock different than doing a factory wipe/reset is I were already bone stock?
rocko73 said:
Nice info. One quick question. I have never had to reactivate my phone after installing any of these roms. Is using the sbf file or maderstock different than doing a factory wipe/reset is I were already bone stock?
Click to expand...
Click to collapse
I'm not quite sure what you mean by these ROMs.... The files being suggested are SBF files, which are used to return your phone to an "out of the box" state depending on which Verizon update you are running off of.
for your second question, yes the SBF of maderstcok file is different that a factory reset/data wipe. All that the factory reset/data wipe does is erase your downloaded apps, and personal data such as accounts (gmail, etc).
SysAdmin-X said:
I'm not quite sure what you mean by these ROMs.... The files being suggested are SBF files, which are used to return your phone to an "out of the box" state depending on which Verizon update you are running off of.
for your second question, yes the SBF of maderstcok file is different that a factory reset/data wipe. All that the factory reset/data wipe does is erase your downloaded apps, and personal data such as accounts (gmail, etc).
Click to expand...
Click to collapse
Sorry, I meant Roms as in Rubix, Apex, etc. I understand now though. Thanks again.
rocko73 said:
Sorry, I meant Roms as in Rubix, Apex, etc. I understand now though. Thanks again.
Click to expand...
Click to collapse
No problem. If you have issues or questions, check out my guide
http://forum.xda-developers.com/showthread.php?t=940986
If you sbf,or flash madertstock you will have to reactivate your phone. Its painless dial *228, press 1, provide last 4 of ssn if prompted, wait for process to finish it may take while do not pull battery.
Sent from my DROIDX using XDA App
I think I may have messed up...
Got Droid X Bootstrapper loaded, made a back up. Forgot to wipe, and installed Liberty 1.5, rebooted... Liberty Installed. Now on reboot all I get is Liberty and the wings going around in circles over and over again.
Ugh! Anyone got any ideas?
I think I might have fixed it. Got into Bootstrap recovery mode and was able to reload my back up.
This time, back up THEN WIPE! Grrrrrr
Segfalt said:
I think I might have fixed it. Got into Bootstrap recovery mode and was able to reload my back up.
This time, back up THEN WIPE! Grrrrrr
Click to expand...
Click to collapse
yes, first rule of thumb should always be to make a backup before changing anything such as theme/ROM... unless you feel you have nothing to lose =)
Now to run a back up again and then WIPE... forgot to wipe last time. So I'm sure it was trying to load both boot files. Looked like Liberty was going to work. But, it wound up in an endless loading screen with the wings spinning.
**solved**
Have you tried Eugene's Froyo that doesn't brick? I once have a problem installing the first versions of voodoo lagfix do to my NAND (or something like that) being of a different size than the majority of the vibrants. The phone soft-bricked but I brought it back with Eugene's froyo and flashed back to stock 2.1. I noticed that all my stuff inside the internal SD Card was deleted (or reformatted...i really don't know). Maybe this can help you get rid of the ghosts of past roms. Good luck.
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
No, I hadn't thought of that. I wasn't sure if flashing any more ROMs would be a good idea. I'll try it though and see what it does. Thank you.
Let me know if it worked for you.
Hi,
I tried this and no luck - still the same. I wasn't able to get rid of any of the aforementioned problems.
I'm getting desperate at this point. If anyone knows of anything that could easily fix the problem, even if it carries a risk of making things worse, I'm willing to try anything and not hold anyone responsible for the actions I take...
Surely there are adb commands that can format or delete these ghost files & folders, or if someone could tell me where to go and manually delete files & folders through something like DROIDEXPLORER or ROOT EXPLORER, I'd be willing to try anything.
Again, thanks in advance!
Have you tried checking the "Re-Partition" box when you Odin back to 2.1?
tnimoruen said:
Have you tried checking the "Re-Partition" box when you Odin back to 2.1?
Click to expand...
Click to collapse
Yes, I have. I've tried two different versions of ODIN, the re-partition option, I've formatted the internal and external SD, etc. This is all what leads me to believe that there are files/directories used during the flashing process that are *not* cleared/wiped by ODIN or other flashing methods. There are ghost files, I just don't know how to get to them and get rid of them. Maybe I need a Vibrant Exorcist, LOL.
Wipe dalvik cache had been broken for quite some time, actually there's been some threads about it. If you can't odin the only other option is just wipe data/ factory reset in clockwork recovery.
I've seen those Dalvik cache posts, but I must have misunderstood the issue. As far as the others, I can ODIN - It's just not wiping everything. I can also wipe/reset in CWR, but again, it's not wiping everything. Stuff is getting left behind (I can only assume) which is preventing me from doing certain things. The phone works, but certain things will no longer work - such as not being able to use mini-Kies to go to 2.2, format BOOT in CWR, can't root via SOC due to mount path error, etc.
WIPE WIPE WIPE!!!!!!
Use the Eugene's Froyo...etc. Keep doing it--it might take a few tries. Hell, try re-partition and NOT re-partitioning. Sometimes this phone can get finicky. Just be patient and persevere and it will pop into place. ODIN re-creates all software--but is pretty un-reliable for obtuse issues like yours. Just keep at it.
Get to 2.1 stock NO MATTER WHAT...then flash your choice of rom. It can iron itself out with a little sweat and rage.