using pathsaver to get from eclipse 2.1 to stock - Motorola Droid Bionic

Hey friends,
I am having a little trouble using pathsaver to stock from eclipse 2.1.
drivers and all are installed.
using the newest version linked in a thread below
in charge mode/usb debug mode
when I run the script it just hangs at phase 1.
Any ideas? or a better way for getting to a rooted 893?

Try using R3l3AS3DRoot and For3v3r Root first, then use Path Saver.

Related

Rooting Captivate that has Cognition 2.2?

I'm trying to get root(superuser) access on my captivate which already has Cognition 2.2. I was trying to update Cognition Rom to the latest beta and having issues because the captivate would not restart in clockwork recovery even when rom manager would tell it too.
I thought by unrooting it using one click root it would work so I did that and now I cant root it back to try the update of the ROM again (I know dumb).
Now its 2.2 and I dunno how to get root access.
Install using an Odin installer.
will that give root access and install cognition 2.2 latest beta? I've never used the Odin installer.
Yes. It's like clockwork, but on your computer.
FerraraZ said:
I'm trying to get root(superuser) access on my captivate which already has Cognition 2.2. I was trying to update Cognition Rom to the latest beta and having issues because the captivate would not restart in clockwork recovery even when rom manager would tell it too.
I thought by unrooting it using one click root it would work so I did that and now I cant root it back to try the update of the ROM again (I know dumb).
Now its 2.2 and I dunno how to get root access.
Click to expand...
Click to collapse
I don't know if you've already tried this or if it will help at all but I was having somewhat similar problems on my phone running stock 2.1 update 1 but after I ran "fix permissions" in ROM Manager it worked. Hope that helps.

[Q] Is there a rooted NVFlashable Stock HoneyComb ROM for DS7 Tmobile 4G?

I have tried upgrading using the method posted here but I keep getting an error: "FOTA Name mismatch". (I used method one).
Also, I was unable to get the stock 2.2 rooted using the super one click method, in order to install the CWM and try the method 2.
I have been working on these for hours and I am at my wits ends.
Here, is my question: Is there an NVFlash method that will get me to a rooted stock honeycomb?
Thanks for your help.
P.S: I have been using Steve's HoneyStreak R7 but the battery life has been terrible. I downgraded to stock 2.2 to get the official HoneyComb upgrade but have not been successful.
to answer your last question, no. To root froyo on ds7 use gingerbreak.
brown14you said:
I have tried upgrading using the method posted here but I keep getting an error: "FOTA Name mismatch". (I used method one).
Also, I was unable to get the stock 2.2 rooted using the super one click method, in order to install the CWM and try the method 2.
I have been working on these for hours and I am at my wits ends.
Here, is my question: Is there an NVFlash method that will get me to a rooted stock honeycomb?
Thanks for your help.
P.S: I have been using Steve's HoneyStreak R7 but the battery life has been terrible. I downgraded to stock 2.2 to get the official HoneyComb upgrade but have not been successful.
Click to expand...
Click to collapse
Method one works, if you get the FOTA mismatch then you flashed the incorrect recovery. I used method one. BUT there is a problem, rooting stock Honeycomb I get some random reboots, if I stay stock unrooted it runs fine
Gingerbreak worked for me after flashing back to 2.2 with NVFlash.
otnos said:
to answer your last question, no. To root froyo on ds7 use gingerbreak.
Click to expand...
Click to collapse
Thanks. Using Gingerbreak worked magic. Thanks.
cdzo72 said:
Method one works, if you get the FOTA mismatch then you flashed the incorrect recovery. I used method one. BUT there is a problem, rooting stock Honeycomb I get some random reboots, if I stay stock unrooted it runs fine
Click to expand...
Click to collapse
Thanks for the heads up!
illdill said:
Gingerbreak worked for me after flashing back to 2.2 with NVFlash.
Click to expand...
Click to collapse
Thanks

VZW Galaxy Tab Root 2.3.5?

I have tried Superoneclick latest version with zergrush. Hangs on step 7. I would like to root my SCH-I800. Anyone shed some some light on this? Even a manual root via adb?
Sent from my SCH-I800 using xda premium
Will CF-Root work? If which file?
same here: no joy with either latest superoneclick or with the pure zergrush.
vzw may have patched that exploit
:/
I mean I can put it back to stock and not update it. Just seems a lot more stable with 2.3.5. More fluid and faster. I originally had 2.2 and rooted manually. Now seeing new update, I reset to stock and downloaded both updates to 2.3.5. No dice on any root method yet. I see CF-Root as method but our device is considered old by latter means? Also my kernel string only gives "2.6.35.7". Hopefully soon...
If you flash the kernel from my Cubed 3 ROM it will allow you to adb push the root files.
D
dsb9938 said:
If you flash the kernel from my Cubed 3 ROM it will allow you to adb push the root files.
D
Click to expand...
Click to collapse
Can/should we flash the recovery as well? Is it possible to flash back to the stock kernel and/or recovery after rooting?
BTW, I really like your ROM, I just prefer to stay a little closer to stock. Thanks a lot for all the help you have provided us VZW Tab owners!
EDIT: I just now saw your rooted stock ROM in the development forum. That is really awesome, thanks! But, if possible, I am still interested in rooting the device without having to reflash the entire ROM and losing data/settings in the process.
Any update on this? Suggestions?
Just need to root, not change the ROM (yet!)

[Q] AT&T Galaxy Tab SGH-i987

Hi all. I'm not a beginner but I've kept my AT&T Galaxy Tab SGH-i987 running the stock Froyo in hopes that an official Gingerbread release would ever come from Samsung or AT&T. Although it did come out for most of the other US variants, it doesn't look like it will ever materialize for the AT&T-variant.
At the same time, it appears that no one has a way to restore the stock AT&T ROM.
Anyway, I plan to use a custom Gingerbread or Ice Cream Sandwich ROM soon. (Sooner if there is a way to restore the stock AT&T ROM, if I choose.)
So, for the AT&T stock ROM, what are the correct steps to update to GB or ICS?
Get the chainfire bootloader app.
Get the JQ1 rom.
Get helroz galaxy unlock
Get the super one click root app
Get the chainfire CF Root v3.3 kernel.
Get odin3 1.7 app.
Get windows 7 pc or get correct usb drivers.
1. In applications select usb debugging
2. Optional--unlock tab using helroz app if you're planning to use other carrier sim cards.
3. Connect tab to pc, Root stock froyo with super one click.
4. Put bootloader app on internal sd card. Run app and patch bootloader if needed.
5. Put tab in download mode and connect to pc. Start odin3. Install JQ1 rom, carefully following that thread.
6. Use odin3 to flash CF Root kernel to root JQ1.
Tab is now stock gb 2.3.3, rooted, unlocked.
Check out this thread http://forum.xda-developers.com/showthread.php?t=1342365
In it we're discussing the stock Rogers rom, however the method to capture the stock state and restore will work for you.
Happy to try and help if you need more pointers.
Sent from my GT-I9000 using XDA App
Good info... just what I was looking for.
I have no problem resetting my Galaxy Tab back to stock and trying to capture a stock firmware since there doesn't seem to be one out there for AT&T. But it sounds like it has to be rooted to capture?
That was the dilemma I had when looking at the stock Rogers ROM. However, there is a fine distinction between needing root and being rooted. Some call this 'local root'.
First is make sure you've got the Android SDK installed on your PC.
What we're trying to accomplish is to be able to run a version of the script from the roto backup thread.
The dd utility should be on the device already, but you won't have permission to execute the commands to copy the volume if you're not running with root permissions.
I think using zergRush you can achieve a 'local root' (non permanent). I haven't tried this myself yet.
Since ADB will be running 'as root' you won't need the 'su' commands in the roto backup script, you will be effectively root already. You'll also need to track down a busybox to install on the device, since that will provide you with the 'tar' command that won't be part of the stock system.
There you go - my best guess on how to capture a stock ROM in a non-rooted state.
---------- Post added at 09:14 PM ---------- Previous post was at 08:38 PM ----------
Just ran zergRush against my Gingerbread (stock) firmware - appears to be a temporary root. I assume it'll work fine against Froyo since that's the exploit that SuperOneClick 2.2 used.

[Q] sideload apps for official gingerbread?

Hi all,
I have a notification from AT&T that I can now update my Froyo Captivate to Gingerbread.
I am currently rooted (Even if rooted, I am not using any custom roms.. and I don't seem to need any.. I am happy with what has come with Cappy. I rooted it just to sideload the apps as it comes disabled in Froyo by default)
My question is: If I use the Kies and update my Cappy to gingerbread, will I be able to sideload the apps as I do it now?
As I am rooted, will it create any problem updating it to gingerbread using Kies?
I just updated to gingerbread yesterday using kies mini, and after I did the "Allow Installation from non-Market Sources" was visible. I think thats all you need for sideloading. You will lose the Root, but like you said you don't need it.
I'm not sure if beeing rooted will affect kies, I was on a custom rom so I used a oneclick back to stock and then kies
thanks t-roth for the response. How is your experience with new stock GB?
Does anyone knows if I am rooted, I can directly go to the Stock Captivate GB using the Kies Mini
22andy2 said:
Does anyone knows if I am rooted, I can directly go to the Stock Captivate GB using the Kies Mini
Click to expand...
Click to collapse
If your rooted phone can connect to Kies, you can install the update.
Thanks Bruce. I will try that out..
Probably the last question. Am I going to see huge performance change moving from Froyo to GB?
I was rooted and Kies had no issue with my phone being so. It left me root-less after the fact, and I felt naked. The number one reason you SHOULD want to be rooted is to get rid of the freaking still-born garbage AT&T thinks we should endorse and like. As far as actual side-loading...I was unable to get the Sideload Wonder Machine to work. But I didn't sweat it because I quickly sought Root. Some of the more powerful utilities require root, but for the casual user, you probably won't want to be messing about in system folders anyway.
You say you "quickly sought root", but did you find it. I tried the 2.3.5 upgrade and as noted it left me able to load non-market apps ok but I was root-less. I haven't been able to root the KK4 upgrade and since I live and die with my Root Explorer and TI Backup I NEED the root. Z4 Root wouldn't work and neither would any of the 3 versions of Super 1-Click that I have (1.6.5, 2.1.1 & 2.3.1). If you were successful, what did you use?
I think it depends on how you enabled the side loading of apps. I'm not on the official gingerbread but that's what I think.
Sent from my slSamsung Captivate on CM7!
use the newest version of super 1 click root.. duh.
or look up the fugu mod root method. odin flash fugu root kernel, let it bootloop once, then odin flash your stock kernel again... or a cwm based kernel for your android version (kk4)
TRusselo said:
use the newest version of super 1 click root.. duh.
or look up the fugu mod root method. odin flash fugu root kernel, let it bootloop once, then odin flash your stock kernel again... or a cwm based kernel for your android version (kk4)
Click to expand...
Click to collapse
I used SQLite editor when I was first rooted.
Sent from my slSamsung Captivate on CM7!

Categories

Resources