Database Develop

Re-flashed Stock and now unable to root

Just a quick background, I purchased my DS7 at staples and rooted it and installed CWM using the info found on the forums so I could connect to my ad-hoc tether. Last week I attempted to install the HC upgrade and got the mis-match message. I booted into CWM and started looping. In an effort to correct this I mistakenly wiped the memory (big mistake!). I found the instructions on flashing the stock ROM (turned out that it was TMO) and got the unit running again. I called Dell (I have posted in another thread on this) and they are to send a pickup. In the meantime I have found instructions on flashing the OEM stock wfi ROM and have done so. I, like many others, noticed that the service tag was wrong and edited PG23/line220 to reflect my correct tag ( note to posters of ROMs and those who would flash: before doing so write down all the information about your unit so you can make changes later if needed). I now have most everything back to pre-upgrade status, but Gingerbreak v1.2 will not root. When I attempt it the program runs but I get a message “Not sure what happened her. Either the exploit failed or the reboot failed. Please reboot manually and see if you have Superuser!” I reboot and nothing, no Superuser and no root access. Also, before I attempt the “unroot’ option is greyed out so I take it that the unit is not rooted nor can I see root files in file manager One thing I have not tried is the CWM un-install that was included in the stock ROM flash thread. Since I don’t see it and I boot into fastboot I am guessing that it is gone. Any suggestions or has anyone had this issue as well?
Another note, I too have the 338 version and no auto update yet. I am not real sure I want to update now. To those that have updated, can you connect to ad-hoc networks with out changing the WPA?

Big wall of text, if you're on 2.2.x reflash CWM 3.0 and flash Superuser.zip as a update.zip though it.
If you're on HC, flash CWM 4.0 and flash Superuser7.zip on it.
Superuser.zip will always work on 2.x roms.
Superuser7.zip will always work on 3.x roms.
If you try and run the wrong one it will just 'run' and give no error, it will simply not do anything, but it wont damage anything.

Thanks, you think cwm is still lurking and giving problems? So I need to reinstall cwm and use it to install the zip? Won't CWM interfere with the HC update?

alchrisr01 said:
Thanks, you think cwm is still lurking and giving problems? So I need to reinstall cwm and use it to install the zip? Won't CWM interfere with the HC update?
Click to expand...
Click to collapse
If you have CWM installed you won't get the update automatically no matter if you have a matching ROM or not... you must be FULLY stock... but I see no sense in waiting, TheManii has already posted the releases that are coming out... why not just flash the zip

[Q] Liberty Rom w/ 5.7.xxx

Hey guys,
This is my first post and first rom on my D3. I have, however flashed my D1 multiple times. So I have an idea about what i'm doing, but i'm not 100%. Anyhow, I was running 5.7 since it got released OTA. Was extremely happy with the fixes that came out in that ver. Started searching around and ended up flashing Liberty3 2.0 a few weeks ago. I noticed the battery drained somewhat fast when idling. So I did some searching and installed the speedy v7 script. Even got the "it works!" file when i looked in root browser. I also made sure to wipe data, reboot multiple times, wipe battery states and click my heels 3 times.
Battery life probably improved a bit, I still dont think its as good as stock 5.7. It is probably acceptable, but I am used to charging my phone before I go to sleep. Having around 90% battery life when i wake up, and being able to run on that one charge for almost 24 hours. This may be attributed to the surprisingly good sleep policies in the stock blur battery manager. I would love to have those built in to liberty. But I think that some of it also has to do that when I flashed liberty, my version dropped to 5.6.890.
Now after reading the entire thread for Liberty3 2.0, I see that people say to "apply hascode's patch" for 5.7. The thing is, no one links it. Did some poking around and are they talking about the second link from the bottom of this page:
hash-of-codes.blogspot.com/p/android-downloads (please add .html, i am new)
If so, do i just drop it on the SD card, boot in to safestrap and apply the zip?
Sorry this is long-winded. I just wanted to explain the extent that I have gone through before asking a question.

dtr3030 said:
If so, do i just drop it on the SD card, boot in to safestrap and apply the zip?
Sorry this is long-winded. I just wanted to explain the extent that I have gone through before asking a question.
Click to expand...
Click to collapse
Yeah, just install the rom and patch, both from clockwork recovery (cwr/safestrap). That patch is for his cm7 build I believe but I would still give it a shot if I was you, worst that happens is you have to restore a backup w/cwr and it might be what you need.

Haha again no link. It's a mystery patch!

it's there. i'm a noob and cant post links. thats why i said "someone please add .html"
but here it is again:
hash-of-codes.blogspot.com/p/android-downloads . h t m l
i looked again right now and the bottom two look like rooted stock roms. the one just above that labeled "Users of OTA 5.7.894 apply this patch (after applying main .zip) md5sum 46c140b55469ab557cd053e992142223" might be what i'm after. i'm still on 5.6 tho.

hashcodes patch will work for liberty if youre installing it on 5.7.894. Yes it is for CM7, but it works for CM9/Liberty and probably all AOSP roms. I havent tried it with a blurrred rom. http://hash-of-codes.blogspot.com/p/android-downloads.html is the link (lol)

MrJudylicious said:
hashcodes patch will work for liberty if youre installing it on 5.7.894. Yes it is for CM7, but it works for CM9/Liberty and probably all AOSP roms. I havent tried it with a blurrred rom. http://hash-of-codes.blogspot.com/p/android-downloads.html is the link (lol)
Click to expand...
Click to collapse
What does it do btw?

I'm trying to figure out how to push my system to 5.7 while running liberty. Somehow I went from stock 5.7 to liberty 5.6. I still have the verizon system update on my sd card cuz I had debloated before and needed to manually update. It was 50mb I think. I don't think that will update libery tho, will it?
I assume the hashcode patch is his own system tweaks and fixes.

Thanks for sharing this. BTW, do you know how I would go to 5.7 when I already have Liberty3 2.0 running over 5.6? I have no idea how this whole bootstrap thing works... More complicated than HTC and Samsung where you'd only get bootloader and recovery...
I'm using SafeStrap 1.6 and I'd like to not delete any settings I currently have. If that is possible...

what you should do is return to stock blur 5.6.890 (i prefer to sbf but ive received a lot of flack for it). Once on stock, root, install OTA rootkeeper from market, download the 5.7.894, install via stock recovery. Restore root from OTArootkeeper, install safestrap 1.06, install recovery from within the app, restart, hit menu during boot menu, make a backup, toggle safe system, format /system (under mounts and storage), install liberty, install hashcodes 5.7.894 patch!!!, factory reset clear data/cache, boot it up.
Obviously you would lose every settting you have. the idea behind safestrap is to leave your stock system untouched, and its about as surefire as it gets.

Back to stock via RSD or something?

So I got a Droid 4 and seem to be having problems with Safestrap enabling the safe side, is there a way I can RSD back to complete stock so I can go back and do everything myself? I know when I had a Razr I had the same issue but when I RSD backed to stock I was able to root and go back to everything myself and didn't have any problems after that.
I've looked and couldn't find anything to do it...anyone?
**I had it disabled running the stock rom, installed Safestrap went into recovery and was going to switch to the safe side and it gave me a error. So I went to reboot my phone and now everything is wiped and I lost everything

collins521 said:
So I got a Droid 4 and seem to be having problems with Safestrap enabling the safe side, is there a way I can RSD back to complete stock so I can go back and do everything myself? I know when I had a Razr I had the same issue but when I RSD backed to stock I was able to root and go back to everything myself and didn't have any problems after that.
I've looked and couldn't find anything to do it...anyone?
**I had it disabled running the stock rom, installed Safestrap went into recovery and was going to switch to the safe side and it gave me a error. So I went to reboot my phone and now everything is wiped and I lost everything
Click to expand...
Click to collapse
You are not the first one to have this problem. I had this happen to me a few weeks ago and have seen a few others posting of similar issues since. Not sure what is happening that is causing this. Did you make a backup of you non-safe system? If you did you can try restoring it although that did not work for me. Kept getting stuck restoring system.orig. Reboot just brings you back to a completely wiped stock ROM. Really strange. What I did to fix safestrap was uninstall safestrap recovery, delete the safestrap folder on /sdcard, then re-install safestrap recovery. I think somehow something is getting corrupted when switching between the safe and non-safe system.
I haven't seen a good guide on XDA for using the fastboot files to restore your phone to stock but here is a good guide from DroidForums courtesy of SGMD1.
http://www.droidforums.net/forum/dr...otorola-droid-4-xt894-stock-windows-only.html
I would also highly recommend using Titanium Backup or something similar to backup all you apps and data. That way, if something like this happens again, you can restore all you stuff.

Thanks that's what I was looking for, as far as having a back up...no I don't have one since it came with Safestrap and running eclipse I don't have a backup of the stock that's why I was wanting to start from scratch and get my ducks in a row with everything

There's a Droid 4 SBF out there. I've been able to get it to work with RSD Lite 5.7

[Q] OTA Update and Safestrap Clarification

Hello all,
I've been running Eclipse 2.2 on 902 for some time and I've stubbornly refused to switch away from using bootstrap for all my backup needs, however, after reading enough about it I decided to give safestrap a try. I've had a little trouble with the process however and was looking for a little clarity...
My understanding with safestrap was that in addition to giving me a safe (technically unsafe) 2nd partition/access to recovery in case I messed something up, that it would also pretty easily transfer data, apps, etc from one partition to the next, making flashing roms (and I thought updating) much easier and quicker without needing to backup individual portions of my system, Is this correct or am I mistaken?
Onward to what I did (my goal is to update to 905 and install eclipse 3.0) - Installed safestrap, backed up safe and unsafe side. I then went to unsafe and used bootstrap to restore to IMMEDIATELY after I applied the 902 update (had backed it up previously). This backup was literally a stock Bionic which I had updated from 886 all the way to 902, rooted, then installed bootstrap to backup. I then updated this to 905 with no issue, and of course backed it up... From here, my understanding was that I could simply swap over to safe side, then install the eclipse 3.0 through finding a zip in recovery - Recovery would not do this for me. It gave me an error similar to "cannot apply eclipse3.0.zip (bad)"
I tried to push the ROM both without making any changes (just switching from unsafe to safe and immediately trying to apply the zip) and when that didn't work I wiped data, formatted system, and wiped cache/dalvik and got the same error. (the net result through all of this was making my safe side non-responsive, and me ending up restoring safe side system to the initial backup I had made about 30 minutes prior).
Is this working as intended? Should I look at safestrap as purely an extra failsafe to keep me from bricking my phone and not an easier method to flash/update? If I have to expect that I need to go to safe, follow the same path to apply the update as I did on unsafe, then flash 3.0 and restore with titaniumbackup, sms/call log backup, etc, I will, but I just wanted to make sure I'm not misunderstanding something with safestrap that may allow me to make this whole process easier - I'd be much more interested in trying out a variety of ROMs if the restoring of my data wasn't such a hassle when I did it.
Sorry for the long post - I'm long winded and also wanted to get all of the information out there for anyone who may answer.
Thanks in advance!
-Jamie

Guess I was too wordy and nobody wants to read it (or posted in the wrong spot maybe) -
tldr:
Is there a way to use safestrap as having a way to easily transfer data etc from one rom/update to the next? or should I be using it solely to have an extra backup to prevent me from bricking my phone, and just do the longer more arduous methods of restoring data and settings after a rom swap/update?

I'm no expert but I have successfully used Safestrap, installed eclipse 3.0 as well as tried other roms and themes, and have other Android experience as well. Sounded like you may have used bootstrap and Safestrap at the same time. Am I wrong? If not, from my understanding that is a no no. Uninstall bootstrap completely and use Safestrap only. I also upgraded my "unsafe" system to .905 via OTA before attempting 3.0. My first experience with Safestrap, however, was not entirely positive either. I think my download was corrupt because it stopped working correctly. I downloaded again and haven't had any problems since. I followed this guide http://forum.xda-developers.com/showthread.php?t=1455888 and it worked. He's not really all that clear at times. It's also not necessary to factory reset after flashing a new rom. Always do it, but it can be done before too. I always do it before and have no problems. Also if you decide to apply a theme make sure you boot up the new ROM before flashing the theme. This guide was not entirely clear on that and it got stuck in a wicked boot loop that ended with me on stock and Safestrap gone. Keep trying. Hope some of this helped. I'm wordy too
Sent from my Galaxy Nexus using xda app-developers app

Btw, to answer your first question, the best way I've found to transfer user apps from ROM to ROM is with titanium backup. Other data will still be on your sd cards and accessible to the new ROM. I never use titanium to restore system settings and most system apps though. Things tend to get messed up if you try to do this from one rom to another. System apps can be converted to user apps with titanium which is cool then backed up and restored to new ROM. And never restore Google play app with titanium. Some go so far as to say don't restore apps with data but I haven't had any trouble except with core google apps like play, gmail, voice. Usually flash gapps if I have to and restore other core Google apps directly from play store. Sometimes titanium "hangs" on some apps. Not to much trouble with it lately maybe it's fixed used to be a PIA though.Sorry there's still plenty of setup involved any time you want to "dial in" a new ROM.
Sent from my Galaxy Nexus using xda app-developers app

Thanks G-diddy,
To clarify, I knew bootstrap and safestrap didn't play well together. That being said, I did NOT use safestrap to try and restore to a bootstrap backup. I installed safestrap, then swapped to my UNSAFE side, then restored to a previous bootstrap backup (using bootstrap), then OTAd to .905. I then backed up this fresh near stock but rooted .905 with safestrap (thus should never have to use bootstrap ever again). I then tried to swap over to safe and push eclipse 3.0 but had no success... At present my phone has near stock but rooted .905 on my unsafe side, and the same .902 with 2.2 eclipse on my safe side that I've been running for months...
I guess I have no choice but to restore my present safe side to the old bootstrap backup, then manually ota, then install the rom, I just thought that Safestrap would make all of this process easier - in as much as since my unsafe side is successfully updated, I was hoping my safe side would be too, making the process somewhat simpler. Sounds like I'm wrong in this assumption though, unless someone else can say otherwise?
Thanks for the tip on Titanium Backup too, although I've been using the premium version of that for months now, ever since I decided I was going to turn my phone into a toy

[Q] Hello, new here, messed up my droid 3

yes i have tried many things before posting here....
used to have a droid x and ran liberty on it.
um, lets see i tried to boot my droid 3 with a ROM based on 4.2 (i think it said its compatible with my version, 5.7.906.XT862.en.US.
its like cyanogenmod 10 or something like that.
here is what i did after having rooted of course:
-installed droid 3 bootstrap
-backed everything up using said app
-downloaded the ROM i wanted
-installed ROM manager
-installed the ROM i wanted.
to my surprise when the phone booted back up it was basically stock. it had all the stock apps that come with the phone, except certain things were not working right even then. i could not access google play. i could not access 3g i dont think, it seemed to be running on 1x or something.
tried holding m+power button and i tried a few options in that menu, none of which would properly boot my droid 3 bootstrap.
any idea what the heck happened?

Hello.
The CM10 roms can not work with bootstrap. You need safestrap 3.0x to install them.
I would suggest you go back to stock using SBF:http://forum.xda-developers.com/showthread.php?t=1686911
After that, root, and install safestrap 3.05.
From there you can install any rom you want (GB, ICS, JB).
Do note that only GB roms are fully functional. None of the JB builds have camera and the ICS builds aren't nearly finished

DoubleYouPee said:
Hello.
The CM10 roms can not work with bootstrap. You need safestrap 3.0x to install them.
I would suggest you go back to stock using SBF:http://forum.xda-developers.com/showthread.php?t=1686911
After that, root, and install safestrap 3.05.
From there you can install any rom you want (GB, ICS, JB).
Do note that only GB roms are fully functional. None of the JB builds have camera and the ICS builds aren't nearly finished
Click to expand...
Click to collapse
yea i dont necessarily use the camera on mine, but i did note that before trying to install it. thank you for your help i am installing the SBF right now. hopefully this works.

Don't use rom manager for the D3
Sent from my DROID3 using xda premium

Yeah you need Safestrap 3.0.5 not bootstrap you can grab it here, http://goo.im/devs/hashcode/solana , make sure to uninstall bootstrap before installing safe strap

okay i got steeldroid a gb version of it installed and it works fine
but how do i get ICS and JB versions installed? i tried both in slot 1 and neither would work properly i just got boot loops im assuming i need firmware but i havent seen any downloads or ways to update my phone.