Obviously this guide owes a huge bunch of thanks to "TheManii", "Giveen" and other folks who can't be named on this forum. I have tested this on both a Streak 7 WiFi and a Streak 7 4G. In both cases they had the Stock Honeycomb already on them. So if you are coming from some other version of Android you may wish to reconsider
1) Download the Fastboot+ADB.zip file for Clockwork Mod 5.0.2.7 from the XDA Developers thread (http://forum.xda-developers.com/showthread.php?t=1334487)
2) Download the Clockwork mod 5.0.2.7 file from the XDA Developers thread (http://forum.xda-developers.com/showthread.php?t=1334487)
3) Go into Settings->Applications and turn on "Run Applications from Unknown Sources"
4) Go to Development Settings and select "USB Debugging"
5) Unpack the Fastboot+ADB file into a directory on your computer where you can find it again
6) Attach the Streak to your PC, and copy the "Drivers.zip" file from the root directory of the Streak (/sdcard) to the same directory where you unpacked the Fastboot file
7) Turn off your Streak after you have copied this file, and disconnect it from the PC
8) Unpack the drivers.zip file and find the "Setup.MSI" file. Execute this file to install the drivers you will need
9) Put your Streak into Fastboot mode - i.e. turn it off, then turn it on by pressing the Power button while holding the Vol DOWN (-) at the same time. This can take up to 20 seconds
10) You will get some red text followed by a white line saying something about Fastboot USB downloading is active
11) Connect the streak to the PC now, and it should install an Android ADB driver. Depending on what you have already setup you may get some drivers installed successfully, and some not. In general if you've been following this guide, you'll be ok
12) Open a command line for the folder where you have fastboot and your recovery image (ClockWorkMod) - in windows navigate to the folder, and hold the shift key while right clicking
13) On the command line type the following:
fastboot -i 0x413C flash recovery recovery.img (where recovery.img is the ClockworkMod or other recovery file)
14) On the command line type the following:
fastboot -i 0x413C reboot
15) Your device should now reboot
16) To get it to reboot into CWM, turn the Streak off, and then turn it on again while holding the Power Button and Volume UP (+) at the same time. This may take up to 30 seconds
From here you would follow the normal CWM options to install just the root files (Superuser7 for one example) or install a custom ROM.
It turns out steps 9 - 15 are also a great way to fix the problem when your Streak comes up and starts asking for a Password when you never setup a password. For some reason installing one of the custom ROMS also installs a version of CWM that is not as recent as the 5 series, which can lead to issues with the signature verification (i.e. when things go "boom", Android sees the partition as encrypted rather than just "locked"). So steps 9 - 15 allow you to put in a later CWM which does a proper wipe, and you're back in business. Have to reinstall apps, but the data is left alone.
Just in case I'm not the only one who has run into this
Ok, I used this guide to modify my Dell Streak 7 wifi. After I was done my screen kept flickering and I put it back to stock thanks to AndroidOVERALL putting together a post on how to complete the restore.
I have searched about the screen flickering but didn't find a resolution. Maybe I missed it, but it seemed that others had the same issue and it was either a hardware problem, the brightness was adjusted, or auto rotate was disabled. I tried adjusting the brightness settings and many other settings but the issue was not resolved until I returned everything to stock.
I have a Dell streak 7 wifi, US version with Honeycomb.
Please point me in the right direction if this issue has been resolved and I missed it. If not any suggestions?
Did you load a custom ROM after following these steps, or did you just reboot aft getting CWM installed. Usually the flickering comes from an issue with the video driver (so can be software if a bad driver, or hardware if it's only marginally in spec).
For any one who gets to the end of the steps and now can boot in go CWM but doesn't know what to do about getting rooted.
Very very Simple.
Download Superuser7.zip
http://www.tablet-cables.com/streak/tools/root/Superuser7.zip
Have your Streak booted normally and USB cable hooked up.
Move to the internal Memory Superuser7.zip
power off device
Power back on using Vol UP & Power Button
Select 2. Software upgrade via update.pkg on SD card and press power
CWM will load.
Select install zip from sd card and power to enter.
select Choose zip from internal sd card and power.
use Vol UP to go backwards to your files and select Superuser7.zip and hit power
move down to YES - Install Superuser7.zip and hit power
thats it. its rooted.
goto ++++++++ Go Back+++++++
and reboot system now
and let it reboot.
Not necessary, but I'd suggest running Superuser and hitting the Knob icon top right (settings) and scrolling down and updating Super User.
Hope this helps someone who may not know where to get Superuser7 and what to do after following the great guide above.
thanks!
nothing sucks worse than a bad download -- happend TWICE! (dayum!)
got rewt?
Help?
I am trying to Flash superuser.zip after installing the clockwork.
But I keep getting the following screen. I do not have exterior sd card installed.
What can I do?
blastedmax said:
I am trying to Flash superuser.zip after installing the clockwork.
But I keep getting the following screen. I do not have exterior sd card installed.
What can I do?
Click to expand...
Click to collapse
It's saying that it is looking for an SD Card and not finding it, so that certainly makes sense. However, it sounds like it is looking for "update.pkg" rather than "superuser.zip", so is it possible you accidentally selected the "Update" option in CWM rather than the option to select a file?
He doesnt have clockwork mod installed, you must have CWM installed to flash zips
OK, I have a new Streak 7 t-mobile with HC 3.2. I plug it to the pc running xp sp3, and it needs drivers for MTP and Streak7. I pointed to the Fastboot+ADB folder I extracted for the Streak7 driver and it installed Android ADB Interface. Pointing there for MTP fails to find a driver. I can't get to the internal SD to get the drivers.zip because my computer won't recognize the Streak until the MTP driver is installed. After installing an MTP driver from the net, I can see the internal and external SD. I copied everything to a single folder labelled STREAK in c:\ and unplug the Streak from the pc. I put the Streak into fastboot mode (Volume - & Power), wait about 10 seconds, then plug it into the usb port. The computer see the Fastboot device and needs a driver. I point it to the STREAK folder (former Fastboot+ADB) but it didn't find a driver it liked. I tried to install manually, but there is no Android 1.0 or Android ABD Interface devices in my list. I do see Android USB Devices, but it is empty when I click on it. ANYBODY else get this, and how do I move forward? I followed the guide to the letter, and appreciate all the work & effort you guys put into making these root methods available. The Streak7 is a cool little device, but I think it will be cooler once I root it. I have rooted my Epic 4g and the wife's Evo 4g on this same computer, and I do have the Android SDK installed (even though I don't know how to use it).
OK, so I used all the same files I have here and was able to successfully get Clockwork flashed & gain root. I dunno why the xp machines don't like these files. I tried 3 other xp laptops before getting to my wife's Windows 7 laptop, which worked just as described in the very well-written guides. #MindBottling!
I cannot even find the drivers.zip in step6. WIN7x64 and a brand new tmobile streak 7. where is this thing? I looked through all the folders and subfolders.
Drivers.zip is in the main directory of the Streak. Open up ES File Manager or a similar program and you should see it. To get it to your PC, attach the Streak via USB and let it mount as external storage (default behavior I believe).
In my main directory on on my streak, using ES file explorer, i cant seem to find that file. I see acct, cache, config, d, ....etc folders, i scroll down, i see default.prop, init, init_recovery.rc, ...... var files, but i dont see drivers.zip. help I need to get honeycomb so I can use skype front facing camera, cause I understand froyo 2.2 can only use the back camera w skype.
Since this should be a common file for all SD7 units, can someone please email that file to me so i can get past step 6. [email protected]
cidand1 said:
In my main directory on on my streak, using ES file explorer, i cant seem to find that file. I see acct, cache, config, d, ....etc folders, i scroll down, i see default.prop, init, init_recovery.rc, ...... var files, but i dont see drivers.zip. help I need to get honeycomb so I can use skype front facing camera, cause I understand froyo 2.2 can only use the back camera w skype.
Click to expand...
Click to collapse
From this I gather your Streak did not ship with Honeycomb. That would explain why you didn't find the file as that is something that I gather Dell added when they changed how they shipped it later on. I am not sure what the redistribution rules are for the file, which is why I haven't posted it myself.
That said, I also can't guarantee this process will work for someone starting with Froyo. I do know there may be an issue with which version of CWM you can use in that case. As such, you may want to check one of the other guides to be sure.
EwanG said:
From this I gather your Streak did not ship with Honeycomb. That would explain why you didn't find the file as that is something that I gather Dell added when they changed how they shipped it later on. I am not sure what the redistribution rules are for the file, which is why I haven't posted it myself.
Click to expand...
Click to collapse
Explain please? Shouldn't drivers be present no matter how it's shipped? Mine came with Froyo with drivers, I OTA'd to HC and I still have them.
Ya I bought this from dell directly about 3 weeks ago. From what I have been reading on XDA, mine is definitely different. Its a tmobile streak 7.
Android 2.2.2
Kernel : 2.6.32.9
OEM ver: GLUNB1A133633
Build : 15420
Another thing I noticed is that even trying to load CWmod through fastboot, my computer does not recognize the DS7 in fastboot mode. The drivers in the fastboot+ADB zip file dont work on my computer as fastboot drivers (or maybe I should try another CPU). My cpu is an AMD 64; running win7 pro 64; i need some serious help.
I think I bricked!
Ok I followed the directions from here to root my tablet.
http://www.cesgeekbook.com/2011/12/root-dell-streak-7-with-honeycomb-32.html
All went well! Everything worked and I was rooted! did the Superuser7. Clockwork came up and installed. All went right! So I was pleased. I figured I would later than put on a ROM cause it was late. Well was going to do so and tried to go into clockwork via ROM manager. Didn't work! Kept rebooting! So I figured I would try the pother way "Press Power and +" then click to Install from SD Card to go into Clockwork. That didn't work either! Then Now it won't reboot at all! I can get into fastboot and I can get into the bootloader. But that's it! I tried to do a Factory Reset and nothing! it just stays on the Dell boot screen. Anyway to fix the problem? If so, please give me step by step directions on how to do it.
Use of ROM Manager is generally discouraged due to unknowns about how the package will work with other ROMs. It also isn't clear to me which version of CWM you were using.
If you can get into fastboot, then you should still be able to use ADB, and I would suggest trying to reinstall CWM as indicated in the first message of this thread. That way at least you should be at a known good spot for us to try and help you get a custom ROM installed.
EwanG said:
Use of ROM Manager is generally discouraged due to unknowns about how the package will work with other ROMs. It also isn't clear to me which version of CWM you were using.
If you can get into fastboot, then you should still be able to use ADB, and I would suggest trying to reinstall CWM as indicated in the first message of this thread. That way at least you should be at a known good spot for us to try and help you get a custom ROM installed.
Click to expand...
Click to collapse
Didn't know about the Rom Manager issue. I guess it's only good to use on cell phones? Anyway, I am trying again, but the problem is my laptop is now not reading the tablet when in fastboot mode. I have followed all the step again. Including reinstalling the drivers. But since it's not reading the tablet. I can not reinstall CWM. The version I installed was the one from the 1st page. It's a fairly simple thing to do. But just need to get the device to be read by my laptop.
I have contacted Dell and explained to them the problem. They did say that I can return it to get it fixed. but still kind of hoping I can do it from home.
Marvelous0ne said:
Anyway, I am trying again, but the problem is my laptop is now not reading the tablet when in fastboot mode. I have followed all the step again. Including reinstalling the drivers.
Click to expand...
Click to collapse
Not sure what you mean when you say the laptop is not reading the tablet in fastboot mode. When in fastboot it should NOT show up as attached storage. The best way to tell if it is "really" seeing the Streak 7 is in step 13 - which uses an id rather than a device name so that it should work even if the tablet isn't fully identified. If you try to perform step 13 while in fastboot, what message are you getting?
Related
Okay I don't know if this will help anyone, but I figured out how to stop Windows from detecting the phone as two USB drives when the phone goes into Recovery mode, and to make it show up as Android Composite ADB device.
I do NOT have HTC installed, rather, I'm using the USB 3 drivers that come down through the SDK, so I'm not sure how to do this if you are using the HTC Sync drivers intead.
At any rate, start with the phone off and disconnected. Open the Device Manager. Boot with your prefered method into Recovery mode, then connect the phone. It should detect as USB Mass Storage Device under Universal Serial Bus Controllers. Right click on USB Mass Storage Device and click Uninstall and then OK. Once this is done, disconnect the phone (you can leave it running in Recovery).
Open My Computer and navigate to C:\Windows\inf. Copy the files usbstor.inf and usbstor.pnf to your desktop or wherever, it doesn't matter, just make sure you put them somewhere you can get them later. Then delete them from the C:\Windows\inf folder. These are the drivers that Windows automatically uses for USB storage devices.
Ok, now bring Device Manager back to the foreground and plug the phone back in in Recovery. It should show up as Android Phone with an exclamation mark. If Device Wizard pops up cancel out of it. Now right click on the Android Phone and click update driver. Click Browse my computer for driver software. Click Let me pick from a list... Click Android Phone and Next. Click Have Disk. Browse to your SDK folder into the USB Drivers folder and you should see android_winusb.inf, select that then click OK. You should now have a list of three items to select, this part I am not sure if there is a 'right' or a 'wrong' but I go with Android Composite ADB Interface.
Select that or whichever one you think and this is what it will install as. Bingo, now whenever you connect the phone into Recovery or boot into Recovery with it already connect it correctly detects as the Composite ADB Interface or whichever you selected, but does NOT show up as any USB drives.
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
At any rate, to get everything back to normal as far as your computer being able to use USB storage devices just copy those two files back to the inf folder before you connect them and you should be fine.
bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
.
Click to expand...
Click to collapse
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Or you could try what I've done 7 times and achieved ADB Shell 7 times...
1. Turn the phone off.
2. Start running Loop.bat
3. Unplug USB cable.
4. Turn device on in Fastboot by holding in the optical joystick and power.
5. Plug USB in.
6. Hit power button once to get to HBOOT.
7. Wait two seconds for it to do it's thing.
8. Pull off the back of the phone.
9. Hit Vol - to Recovery then hit power.
10. Immediately after doing this continuously push the sd card in and out (about every .5 - .75 seconds)
11. ?????
12. Profit
@DigitalDementia--
How is what you said relevant in this thread?
bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
Click to expand...
Click to collapse
drtrmiller said:
@DigitalDementia--
How is what you said relevant in this thread?
Click to expand...
Click to collapse
Pretty positive it had everything to do with that section of the first post, he said he still couldn't achieve root I attempted to help him. Why don't you explain to me exactly what it doesn't have to do with this thread?
rynosaur said:
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Click to expand...
Click to collapse
The real bummer here - and I should have known better, really - is that this wipes your phone.
I suppose it should be obvious, but take it from someone who's pretty new to Android phones and just wiped their entire phone after following your steps: Please add a warning to your original post.
It's late, I'm tired and irritated, but I'm sort of bummed to know I went from hero to zero in trying to enter shell (again) during recovery all in an effort to get proper perm. root. Sort of ****ty to know that I just lost everything.
still no root
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
USB drives are ok in recovery
When I am in recovery with adb and working correctly it still shows the 2 USB drives so this is normal and ok, what you have done is fool yourself into thinking that your phone is in correct mode but it really is not, this is why it still does not work, sorry.
rynosaur said:
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Now that I've scorched the earth, I'm hitting this thing hard with every trick I can think of to get the shell in recovery again.
Thankfully, I at least have my app list on appbrain.
After researching around the different forums, I think this maybe my issue. I will have to make this attempt when I get home.
This is what I posted on a different forum. I am not sure if this is a similar experience you were having:
So, for a little a bit I was having issues with finding and modding the usb.inf file. I got that finally resolved... Now as I go to one of the first parts of the procedure, executing the adb shell command. Well at first it said the 2 lines, about the daemon and whatever the second line was. Anyways, the third line did not say "no device found" it went straight to a shell prompt "$" . The instructions made a point in the instructions for it to say " no device found" .
I went ahead with the rest of the instructions. No Luck. And I did both methods. A co-worker of mine told to run adb devices to see if my phone is recognized. I will also make that attempt tonight.
I wanted to know if any of you had some insight. I made sure I was in the right directory.
I will make another attempt on a different machine tonight.
Thanks. Oh yeah, I do have some UNIX experience if that makes a difference.
I had the same problem, used this method here
addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
Click to expand...
Click to collapse
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
kentoe said:
I had the same problem, used this method here
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
Click to expand...
Click to collapse
I rooted in Windows, rather than linux, simply because I like the look of MejDam's procedure better than the linux script posted here on XDA--and his windows procedure is accompanied by his YouTube video
Long story short: I had ADB Composite Device AND the two storage volumes mounted together, as I got shell, and did the other steps in recovery. NB: they were mounted as Generic Storage Volumes, not writeable partitions. The stock recovery on DI does not allow host to mount either partions, although I'd like to see if
Code:
mount /dev/block/mmcblk0p1
worked for the SDcard on the sdcard, cuz then it would be a cinch to mount sdcard/emnc partition into host OS--windows, linux, Atari 2600, etc Worth a try.
Anyhow, my conclusion: a bad driver setup could be a barrier to catching adb shell, but it is certain not the prevailing problem for most, IMHO.
Was wondering if bast525(the creator of the thread) was ever able to adb shell while in recovery, and if so what did you do thanks.
Heh, I wish.... I've tried just about every method posted on these forums, and five different SD cards from Sandisk, PNY, and Kingston. The only thing I haven't tried is rolling back to the pre OTA update, because I don't want to wipe the phone at this point.
Here is my experience with all this and why I need help ..
(Yes, I am new to all this, maybe that's why I get confused but alright..)
Okay, I want to root my phone with the design of DocRambone. Right, I follow your guide here:
http://forum.xda-developers.com/showthread.php?p=7329960#post7329960
And go to HOWTO#1 which says I need to flash my firmware. And so I start.
I first download Odin, get the 512.pit file and then try to find the desired firmware package(which according to the Doc guide is I9000XWJM8). Okay, I search the link and get to this: (I pick original firmwares -> Europe)
https://www.wuala.com/Samsung Galax...n/Original Firmwares/Europe/?key=AfzUZSU4SpKU
Which leads to my first confusion. I can't find anything named "I9000XWJM8". The closest I find is the one called "GT-I9000_I9000XWJM8_I9000XXJM4_CODE-MODEM.7z". Can I use this one or where is the "I9000XWJM8" ? :S
Right, I then assume it's the right one and continue only to find out that I don't know how to start my phone in "download mode". Or maybe I just can't because I got one of the phones without the 3 button combination. I'm not sure which one it is, and yes I did try all the combinations you state here:
http://forum.xda-developers.com/showthread.php?t=746814&page=2
None works. But how does the screen look like when you are in recorvery mode? Maybe you should add this to the guide, so people know if they can or cannot start in recorvery mode.
Anyway, I assume I have one of the phones without the combination and so I continue to the guide "Release: 3-button combo fix for any firmware version":
http://forum.xda-developers.com/showthread.php?t=785201
I follow the guide and get to step 6 which says "Start a new command prompt and type "adb reboot recovery"". Right, what's this now?
I go back to the big tutorial:
http://forum.xda-developers.com/showthread.php?p=7329960#post7329960
And finds the ADB tutorial to find out that I need Android Software Development Kit .. AND a rooted phone. Right, so I wanted to root my phone in the first place and now I need to root the phone in order to get the 3 button combination so I can root the phone. "Wait what?" was my 1st thought. But then I remembered that I found this guide earlier "[REF] Howto (un)root your SGS I9000 the easy way (keep all your data) (Eclair 2.1)":
http://forum.xda-developers.com/showthread.php?t=728754
Why did I got here? Because it said "the easy way". I thought that maybe it doesn't need the 3 buttom combination and so I found out it doesn't!! YAY finally a breakthrough, I thought. And so I started with this tutorial.
I was then met with this
"ROOT includes:
- Superuser 2.3.6.1
- Busybox 1.16.0 (for use with Titanium Backup)"
which brings me to another question: Does this mean that you get these apps when you use this root method? or do I need to install the apps first?
I thought it was the first one, since it says "includes". And so I start with the "Automated Method!". I dowload the .bat file and start. Follow what it says and reaches to the part where I plug in my phone. Here I get the error message: "Driver installation unsuccessfull" (Or something like it. I Don't recall since when I plug the phone in now I don't get the error. I don't even get a "ready to use removable disk" now. It doesn't even recognize the phone now when it's plugged in). Now I have tryed to connect it to the pc before (although WITHOUT the USB-debugging checked) and it worked fine. And this is as far as I can get. I am now officially stuck!
I have read comments and all but it doesn't help.
I'm realy tired from trolling these forums after being led through like 4-6 guides + the ones I havn't mentioned here (havn't counted, but something like that)..
So can anyone please, for the love of god, tell me which guide I should start with, list the guides so I know which one to go to next and answer the questions above.. My head hurts now :S ..
But in general, please write the guides more "noob friendly" or whatever .. I think alot of them are written by admins for admins(or atleast people who know their way around these phones). Atleast that's the impression I get.
I know it was a long read but I hope you'll help anyway
Thank you in advance!
/JohnTheOne
Sorry if I sound mad or offencive btw.. it's not my itention. I'm just mad and annoyed at myself because I can't make it work
Sent from my GT-I9000 using XDA App
hello there, I can appreciate if you're new to smartphones it can seem a lot to take in.
If you want an easy/simple way to root then there are 2 or 3 methods available on this fantastic forum but try this one:
http://forum.xda-developers.com/showthread.php?t=742403
just go to youtube and search for rooting videos and watch someone do it first, then you do it. very easy once you see how it is done. youtube or theunlockr.com also has great videos
Yea but my problem is now that I can't get access to it when it's in USB debugging mode.
As I posted earlier, the first time I put my phone in USB debugging mode and connected it to my computer it said "Drivers where not successfully installed" (or something like it).. And now, when I connect my phone to my computer in USB debugging mode, it won't even show as an USB. It doesn't pop up and say "USB connected" and I can't find it under My Computer.
Someone who can help me with this?
And when I plug it in, in USB debugging mode, should I press the USB connected button on my phone, like I usually do when I connect the phone to my computer without it being in USB debugging mode?
Okay, I found the device now on my computer, but I can't find any drivers for the phone to be connected in USB-debugging mode. Anyone knows where I can find drivers for this?
JohnTheOne said:
Okay, I found the device now on my computer, but I can't find any drivers for the phone to be connected in USB-debugging mode. Anyone knows where I can find drivers for this?
Click to expand...
Click to collapse
when used as USB Debugging mode, you need no driver if you plan to use it as a mass storage drive
you just pull down the tab and select mount the drive
then you can copy your Update.zip to the phone Internal SD
after it is done select Unmount the mass storage drive from the pull down tab in the phone
and now you can boot into the Recovery Mode, select update.zip
and you are rooted.
reboot back to normal, and enjoy the freedom to install any App you want to play with
The easiest way I found is to go on to Android market, install One Click Lag Fix. Then open the app and select root 2.1. Restart into recovery and select apply update.zip. Your phone reboots and its rooted. Simples!
simplest way to root is
1)go to market search for RyanZA's OCLF 2.0.
or here is link http://www.appbrain.com/app/com.rc.QuickFixLagFix
2)open the app
3) click root.
4)then boot into recovery
5)use volume button to select update.zip and click home button
6)your phone is rooted.
Hi everyone... Can anyone here let me know if these "lagfix" rooting methods work and are SAFE for a LOCKED (I have not unlocked the sim) Bell Galaxy S with stock JH2 rom? I am also a bit of a noob and would like to see what this phone can really do.
Also... Do I have to unroot it if I want to upgrade to froyo when it is released?
Please advise...
Thx.
yiannisthegreek
PS... Once this is rooted, HOW do you unroot with these "lagfix" methods if I ever need to?
i would advice againts installing the LAG FIXes as they can kill your Internal SD
there are over a dozen forum topics with people unable to repair the damage, and end up having to ship the phone back to samsung to have it repaired.
Allgamer...
Thank You for the heads up on this but now I am still confused on how to do it. I have to move the update.zip file to my internal sd card but I too have some issues that I cant figure out.
I learded how to do it on youtube watching someone called tech0stickyasglue and it seems very simple but firstly I am not sure exactly where I have to place the file and if I have to unzip it and then place the 2 folders inside it into the sd card, etc... I also have an issue with the whole "mount" and "unmount" thing.
I can mount the card while in usb debugging but when I go back to the dropdown menu it does not give me an option to "unmount" it only gives me an option to quit usb debugging and when I pick this option I get a warning message saying that I should "make sure I have unmounted form the host" or something to that effect.
Can you give any advice or step by step instructions to me on what and where I need to place these files to make this work?
I would greatly appreciate it...
Yea but the thing is that I can't go into recorvery mode.. The 3 button combination doesn't work (Talking to the people from page 1)
AllGamer said:
when used as USB Debugging mode, you need no driver if you plan to use it as a mass storage drive
you just pull down the tab and select mount the drive
then you can copy your Update.zip to the phone Internal SD
after it is done select Unmount the mass storage drive from the pull down tab in the phone
and now you can boot into the Recovery Mode, select update.zip
and you are rooted.
reboot back to normal, and enjoy the freedom to install any App you want to play with
Click to expand...
Click to collapse
When I put down the tap and select mount the drive(when in USB debugging mode that is) I can't acces the phones folders. I can't even see the extra icons you usually get, under My Computer, when you connect an USB to the computer. I can only find the SAMSUNG_Android under Control Panel -> Hardware and Sound ->Devices and Printers where it lies under the "Unspecified" section and not under the "Devices" section. And when I right click on it, press proporties and go to the Hardware tap, I can see under "Device status:" it says "The drivers for this device are not installed. (Code 28)" ..
So can anyone tell me what's wrong? (I havn't installed Kies btw, dunno if that has got anything to do with it)
JohnTheOne said:
When I put down the tap and select mount the drive(when in USB debugging mode that is) I can't acces the phones folders. I can't even see the extra icons you usually get, under My Computer, when you connect an USB to the computer. I can only find the SAMSUNG_Android under Control Panel -> Hardware and Sound ->Devices and Printers where it lies under the "Unspecified" section and not under the "Devices" section. And when I right click on it, press proporties and go to the Hardware tap, I can see under "Device status:" it says "The drivers for this device are not installed. (Code 28)" ..
So can anyone tell me what's wrong? (I havn't installed Kies btw, dunno if that has got anything to do with it)
Click to expand...
Click to collapse
Ahh... the joy of Android & Kies....
you don't really need to install Kies, I only installed Kies to check for official ROMs, but i was using the phone on the PC even without Kies installed
You can install the Android SDK drivers, inside the Android package that you download from google, there is a sub folder with both 32bit and 64bit drivers, unplug your phone and install them, then plug back the phone, it should be detected now.
in my Work PC, i never installed any driver, and i select mount, and it gets detected as a USB key by Win XP
AllGamer said:
Ahh... the joy of Android & Kies....
you don't really need to install Kies, I only installed Kies to check for official ROMs, but i was using the phone on the PC even without Kies installed
You can install the Android SDK drivers, inside the Android package that you download from google, there is a sub folder with both 32bit and 64bit drivers, unplug your phone and install them, then plug back the phone, it should be detected now.
in my Work PC, i never installed any driver, and i select mount, and it gets detected as a USB key by Win XP
Click to expand...
Click to collapse
Alright, thanks alot But where can I find this Android package then? I'm not sure what you are talking about exactly
Why wont anyone explain WHAT file(s) you put WHERE exactly for this update.zip root method? Is is some sort of "spy secret" or something?
Seriously... I CAN get to see my phone folders on my computer so I am good there but what I dont know is if I am supposed to move the entire .zip file to the root of my sd card or if I need to extract the .zip file to the root of my sd card.
At any rate... I have tried BOTH methods and I always get the same error message when I reboot in 3 button mode... Something to the effect of E: cannot open / install update.zip... Invalid or not found... (I am guessing on this as I am at work but you get the idea)...
Please... ANY help and "step by step" instruction would be GREATLY appreciated!!!
Hi,
One Click Lag Fix (OCLG) downloadable from Android Market will give u an option to root ur phone. And also it gives u an option to fix the lag in galaxy s. I have more than 80 applicatons and widgets installed in my phone. I insist that OCLF is the most useful, powerful and demanded application ever. It is so easy to use and follow. It even offers an option to unroot. So don't be afraid to download and install.
For ur reference, the bench mark speed has been increased from 800 to 2150. Comparable to nexus 1 with 2.2 was 1200. Hope this helps.
Sent from my G-I9000M Ver. UGJH2 using XDA App on Bell Mobility Network
JohnTheOne said:
Alright, thanks alot But where can I find this Android package then? I'm not sure what you are talking about exactly
Click to expand...
Click to collapse
you download it from google
just google up Android SDK download
keep getting this message even though I have installed drivers..pc says they work..phone registers that usb is connected..debugging is selected...what am I doing wrong here...thanks
Update Failed
Please check the PC side and devise side status.
1. Power on your devise and select USB debugging on your phone
-Press Menu and then tap Settings>Applications>Development
-Tap the USB debugging check box if it's not selected
-The USB cable must be connected to your devise and PC
2. Check your driver is installed correctly.
3. Close all other applications in the device and PC.
is your antivirus/internet security shut off?
Have you removed all instances of the drivers (confirmed through device mgr&ctl panel), rebooted an installed the drivers again (making sure phone is not connected until post-install)?
What OS are you running?
running windows7..will check on the antivirus...try reloading USB drives...back in minute with update...lol
32bit or 64bit?
nt sure...wife's laptop..window 7 home premium? Edit...64 bit..sorry
topherdownfrown said:
nt sure...wife's laptop..window 7 home premium? Edit...64 bit..sorry
Click to expand...
Click to collapse
There have been multiple people that have been having odd results with updating through win7 x64.
I would suggest running the update on a 32bit machine.
will try after work..thank you..post result later.
Spz0 said:
There have been multiple people that have been having odd results with updating through win7 x64.
I would suggest running the update on a 32bit machine.
Click to expand...
Click to collapse
Exactly. I tried for 4 hours on my Windows 7 Home Premium 64 bit machine with no luck. Drivers were installing properly from the CD included with the phone, but the update would always fail at 98%. First try on my older Vista 32 bit machine the update went right through the first time with absolutely no issues.
Don't give up
Spz0 said:
There have been multiple people that have been having odd results with updating through win7 x64.
I would suggest running the update on a 32bit machine.
Click to expand...
Click to collapse
I agree. However, I got the "failed to update" message even when I tried to install using my desktop computer that's running Vista32. BUT, then I installed the drivers (the ones that came with the update) to my Toshiba netbook (running Windows 7 Starter). The first update failed, same as before. So I disconnected my Zio, and rebooted it. I plugged it back into the netbook, ran the update installer, and it installed in like 7 minutes. Works great too. So far none of the issues that have been brought up on other threads.
edit: froyo 2.2.1 installed successfully on the Zio in less than 10 mins. i forgot to unmount the damn sd card and this was the really why my phone froze on the "modem download mode" and why the install GUI on pc dissapeared.
piece of cake! thanks a lot guys for posting this update and for creating the Zio forum.
installed the zio m6000 drivers directly from retail cd and ran the kyocera updater. i'm running Win XP on an old-school Dell optiplex.
anyway the update has been taking up at least 20 mins now. the screen on my Zio is black and the message "modem download mode" (i figure that its the tethering part) appears.
why is this update taking so long?
I've heard of varying times. Myself, it only took 6 mins or so, others had to wait more like 20-30.
What does the update program say?
OMG!!!! Its happening to me too! HELP!!! I get error code [0x50015001]. SDcard is out, uninstalled modem driver and installed the one that came with the upate, and still 98% then failed. Any help PLEASE?????
itrustno1 said:
OMG!!!! Its happening to me too! HELP!!! I get error code [0x50015001]. SDcard is out, uninstalled modem driver and installed the one that came with the upate, and still 98% then failed. Any help PLEASE?????
Click to expand...
Click to collapse
don't panic!
you have to follow the directions straight to the teeth on the install instructions.
1. make sure that you have the correct Zio usb drivers installed on your PC.
2. when the installer window (GUI) pops up, read the instructions. make sure that USB debugging is 'checked.' usb debugging option is the settings.
3. make sure that you unmount your sd card (not pulled out).
4. i reset my Zio to factory default right before i updated 2.2
5. if the update installer didn't appear at first then run it again and watch the progress.
Turn your phone off, Hold the volume + (up) and - (down) and the power button to place your phone into Modem Download Mode.
Make sure you have the Kyocera M6000 Drivers installed on your machine properly first. Once you are sure the drivers are installed correctly you can plug your phone in... wait a minute or so before you launch the update file.
I have installed the update to my phone 3 times with no problems other than when I extracted the file from the zip, I found it worked best running it without extracting the file. I have Win 7 32bit and it takes about 5 - 6 minutes to update.
If all else fails. You might have to download the sdk manager and use fastboot and flash the boot image then do the update and it will put the phone into recovery.
Spz0 said:
I've heard of varying times. Myself, it only took 6 mins or so, others had to wait more like 20-30.
What does the update program say?
Click to expand...
Click to collapse
By the way, The updater says 5 - 10 minutes.
Success!!!! ok...I dont know if it mattered but I also installed the future dial suite on the zio disk...I went through first and erased all other zio usb drivers before reinstalling the disk versions...plugged in phone..drivers got the OK..then ran the installer..took 5 minutes plus 2 for reboot..lol..
Also...fyi..I did this to my wifes phone but forgot to factory reset...all of her programs and contacts including adw ex remained intact after update (smoke from ears) oh well..thank god for titanium backup..
So does that confirm my thoughts of when I updated the other day to fix a goof after my original update. My apps and everything were still there after the update. So that must mean that the update from 1.6 to 2.2 does not format the phone unless go into the phone settings and do a factory reset.
Im at the end of my chain, please help me. My zio is stuck on the black screen "modem download mode" ever since the 98% thing happened. Try after try i keep getting error code. Im using windows vista 32-bit, i got the disc that came with my zio, i think i may have opened/extracted the zips wrong or didnt install in order or something. I think i uninstalled everything to do with this from my cpu even the zips so i can start fresh with ANY help i can get.
Uninstall the drivers for your zio that you have currently installed. Install the drivers that are on the site for the update download. Turn the phone off, unplug your battery for about 10 seconds if you need to. Hold + up and - down on the volume and the power button to put your phone into Modem Download Mode manually. Give the computer a minute to recognize the device. Run the updater again and if it fails or gives you an error message I would reccomend downloading the updater again. I have been able to run the updater several times already with no issues.
If you are still having problems, you may need to download sdk-manager if you do not have it already. You can always just use fastboot to erase the system and then run the update. The update will then set up the system partition and update the phone.
I had to do this just a few hours ago after I semi-bricked my phone while messing around with the cpu. What I did to get it working again after "bricking" it was...
1. you will need to have the android folder for the sdk-manager in the root of your hard drive to make it easier, unless you know where it is located.
2. Open command prompt and change to the tools directory within the sdk-manager folder. Mine was located in C:\Android\SDK-Manager\Tools
3. You may need to find the AdbWinApi.dll file, mine was located in the platform-tools directory so I just copied it to the main Android folder then copied fastboot from the tools directory and also placed that into the main Android folder.
4. Put your phone into fastboot. Hold Volume + up and the send and power keys. You can do "fastboot -w" and it will wipe user data and cache. You will need to type "fastboot erase system" and it will erase the system partition. Now type "fastboot reboot" and your phone will restart.
5. Put your phone in Modem Download Mode and run the updater.
Mattix724 said:
Uninstall the drivers for your zio that you have currently installed. Install the drivers that are on the site for the update download. Turn the phone off, unplug your battery for about 10 seconds if you need to. Hold + up and - down on the volume and the power button to put your phone into Modem Download Mode manually. Give the computer a minute to recognize the device. Run the updater again and if it fails or gives you an error message I would reccomend downloading the updater again. I have been able to run the updater several times already with no issues.
If you are still having problems, you may need to download sdk-manager if you do not have it already. You can always just use fastboot to erase the system and then run the update. The update will then set up the system partition and update the phone.
I had to do this just a few hours ago after I semi-bricked my phone while messing around with the cpu. What I did to get it working again after "bricking" it was...
1. you will need to have the android folder for the sdk-manager in the root of your hard drive to make it easier, unless you know where it is located.
2. Open command prompt and change to the tools directory within the sdk-manager folder. Mine was located in C:\Android\SDK-Manager\Tools
3. You may need to find the AdbWinApi.dll file, mine was located in the platform-tools directory so I just copied it to the main Android folder then copied fastboot from the tools directory and also placed that into the main Android folder.
4. Put your phone into fastboot. Hold Volume + up and the send and power keys. You can do "fastboot -w" and it will wipe user data and cache. You will need to type "fastboot erase system" and it will erase the system partition. Now type "fastboot reboot" and your phone will restart.
5. Put your phone in Modem Download Mode and run the updater.
Click to expand...
Click to collapse
okay, let me give that a shot, stay with me please!!!!!!
Hi
How to flash Dell Sreak 7 T-Mobile to 3.2 Honeycomb?
I tried everyting and searched everywhere
I tried this http://forum.xda-developers.com/showthread.php?p=23833836#post23833836
but the link didn't work: update.pkg for US 4G
I decided to get this link from wiki http://forum.xda-developers.com/wiki/Dell_Streak_7 (the latest one) but got this massage: "FOTA mismatch"
514 21700 11.810.09.06.00 30 Dec 19, 2011 Latest US 4G rom - this file didn't matched
I even found and tried this method but it didn't work too.
l
Every failed time backed to the original 2.2.2 android (I didn't know if it nessesary to do, but I did)
Is someone knows what to do?
What do you mean that the link didn't work? I'm downloading it right now, although I don't need it and will delete it.
I encountered the "FOTA name mismatch" doing the official Dell 514 update. I found an old post at some forum that said to rename it to "Update.pkg" instead of "update.pkg" and that worked for me.
The download just finished with no problem at all.
alex04210 said:
Hi
How to flash Dell Sreak 7 T-Mobile to 3.2 Honeycomb?
I tried everyting and searched everywhere
I tried this http://forum.xda-developers.com/showthread.php?p=23833836#post23833836
but the link didn't work: update.pkg for US 4G
I decided to get this link from wiki http://forum.xda-developers.com/wiki/Dell_Streak_7 (the latest one) but got this massage: "FOTA mismatch"
514 21700 11.810.09.06.00 30 Dec 19, 2011 Latest US 4G rom - this file didn't matched
I even found and tried this method but it didn't work too.
l
Every failed time backed to the original 2.2.2 android (I didn't know if it nessesary to do, but I did)
Is someone knows what to do?
Click to expand...
Click to collapse
There is nothing wrong with ANY of the links you posted. Just like wptski said, they are all downloading and opening fine.
If you get a FOTA mismatch then you haven't flashed the correct factory recovery to decrypt the update.pkg, simple as that...
Recheck your procedure, you're doing something wrong but you have looked in all the right places
i´m in the same situation.. "FOTA mismatch"
are there a "step by step" tutorial to do this??
langoreta said:
i´m in the same situation.. "FOTA mismatch"
are there a "step by step" tutorial to do this??
Click to expand...
Click to collapse
there are several step by step hold your hand because you're too lazy to read methods here on the forum.. if they don't work you're doing something wrong
Sent from my HP Droid
if you go through some of my posts -I only have a few- you will figure out your problem.... I had the same issue there is a particular set of steps that must be done in a particular order to get the DS7 into the correct mode to be flashed...
Its been awhile since I flashed mine to HC but I agree with you..! The info is somewhat scattered & one step isnt even mentioned but is implied & I explain it in one of my posts...
Upgrade to HC 3.2 from TM 4G DS7
Dear friends;
To upgrade to HC 3.2 you should go to DS7 General tab. Look for upgrade TM-4G. http://forum.xda-developers.com/showthread.php?t=1286295
I luckily upgraded to HC with lots of searching and lost time.
The key is to follow The Manii instruction and install USB driver. Without the USB driver you can not enter Fastboot.
I have described my luck to successful upgrade as follows:
I finally upgraded my TMO 4G DS7 to HC 3.2. It is by some luck that I had downloaded a USB driver awhile ago. I tried it and it installed and I could fastboot from my XP (I don't have W7 driver) computer. Please do not ask where I found the driver because I don't remember. I downloaded it back in September from somewhere in XDA forum.
I do have the driver for XP but don't know how to upload here to share with everyone. For those who want the driver please send me your email.
I followed The Manii instruction and XDA Flashing Guide with the following details:
1. Save the recovery-Froyo-us.img in the same folder as fastboot (exe) file in XP computer, say C:\Android. And save update.pkg in the root of external SD card
2. Fastboot DS7 (vol- plus power button). Will see fastboot.... on the DS7 screen
3. Connect USB cable from DS7 to XP computer. Your computer may ask to install 'USB driver'. This was where I got stuck for hours until I found the driver on my computer. Thanks to post # 165, 166. Read posts on page 17. There are good hints there.
4. In Windows XP after driver has been installed, Click Start then Run 'fastboot flash recovery recovery-froyo-US.img' (use Browse to go to the folder where fastboot.exe is located). You will see something 'recovery...'. It seems stuck as if nothing happens there for awhile (just be patient for few minutes)
5. Reset DS7 by pressing the PIN hole near SD card
6. Enter recovery mode on DS7 by pressing Vol+ plus power button
7. Navigate to Software update via Update.pkg on SD card
Few minutes later, reboot and Bingo Honeycomb 3.2.
So far everything seems to work fine but I'm not very impressed with the screen. The characters are rather small and not as easy to read as on Froyo 2.2.2. It uses far more memory (RAM) than Froyo. Video chat works on Gtalk and Skype. GrooveIP works (phone app using Gvoice number).
Good luck.
Our friend Clickslick also posted links to USB driver and others. Goto page 20 or so of the thread post #196
To get fastboot to work I had to download this file:
http://www.fileserve.com/file/5bgRBX5
from this thread:
http://forum.xda-developers.com/showthread.php?t=878786
and used this video:
http://www.youtube.com/watch?v=XHDAtiaYEM8
to setup the "fastboot driver"
How to do the Driver setup:
Download the above file and unzip it this folder contains the driver needed to get past the initial plug-in of the DS7 to the PC while the DS7 is in "Fastboot Mode" select the folder of the DLed above driver and it will fail but now you leave the DS7 plugged in and go into your device manager and do as the above video shows...
now the DS7 will show as something useful...
now you will go to a dos promt by typing CMD in the run bar and following the steps on page 11 of this thread and running the command line there in post #103 it will then finish that... you will need a staple to turn off the unit in the sd card area on the left small hole...
then you will proceed with the right update.pkg file on the root of the sim card boot the unit using the + and power and select the update from sim and it works
There are a variety of threads on how to downgrade a DS7 back to froyo 2.2, so it always takes me a while to pierce things back together. For anybody in the same boat, here's a simple guide, with links. Many many thanks to all those that have come before me: TheManii, Giveen, DJ_Steve, and all the others on the DS7 community that refuse to let the thing die.
Download the complete restore file from here: http://d-h.st/iXc. Unzip the files somewhere, but the caveat here is that if the path is too long, the process will fail. Unzip it to c:\Streak, or something of the sort.
Download the ADB+Fastboot package from here: http://d-h.st/NMu, and unzip it somewhere, like c:\ADB
As detailed in this page (http://forum.xda-developers.com/showthread.php?t=1018809),
Plug the usb cable *on the streak only* (for now)
Hold down both volume buttons
While holding down the volume buttons, plug the other end of the usb cable on your PC. Keep holding the buttons until the lights on the side of the streak come on (the screen will *not* turn on)
Once the streak is lit up, you'll need to install the APX drivers. Go to the windows device manager, and you'll see a device with a yellow question mark (I believe it was called APX, sorry, writing mostly from memory here). Right click that device and update the driver, windows will ask you where the drivers are, navigate to C:\ADB (or wherever you unzipped the ADB files). On windows 7, you'll be prompted to install unsigned drivers. On windows 8, you'll have to boot with signed driver protection disabled. After you install the driver, the icon will change and the yellow question mark will disappear.
Now that all the prep-work is complete, navigate to the c:\Streak folder (or wherever it was you unzipped the files to), and execute the batch file "run this to restore to froyo.bat". This will start flashing the files into the Streak. The whole process will take about 5-10 mins, and it will actually fail at the very end. It'll say it cannot locate P23.img. That's OK! P23 and P24 are for non-wifi models, so we're good. Reboot the Streak using a pin, and voila! It should be good as new.
If the batch file fails to start, or closes very quickly after launching, you probably do not have the APX driver installed, or there's a connectivity issue between the PC and the Streak. Let me know what you run into and I'll try to help.
marciolsf said:
There are a variety of threads on how to downgrade a DS7 back to froyo 2.2, so it always takes me a while to pierce things back together. For anybody in the same boat, here's a simple guide, with links. Many many thanks to all those that have come before me: TheManii, Giveen, DJ_Steve, and all the others on the DS7 community that refuse to let the thing die.
Download the complete restore file from here: http://d-h.st/iXc. Unzip the files somewhere, but the caveat here is that if the path is too long, the process will fail. Unzip it to c:\Streak, or something of the sort.
Download the ADB+Fastboot package from here: http://d-h.st/NMu, and unzip it somewhere, like c:\ADB
As detailed in this page (http://forum.xda-developers.com/showthread.php?t=1018809),
Plug the usb cable *on the streak only* (for now)
Hold down both volume buttons
While holding down the volume buttons, plug the other end of the usb cable on your PC. Keep holding the buttons until the lights on the side of the streak come on (the screen will *not* turn on)
Once the streak is lit up, you'll need to install the APX drivers. Go to the windows device manager, and you'll see a device with a yellow question mark (I believe it was called APX, sorry, writing mostly from memory here). Right click that device and update the driver, windows will ask you where the drivers are, navigate to C:\ADB (or wherever you unzipped the ADB files). On windows 7, you'll be prompted to install unsigned drivers. On windows 8, you'll have to boot with signed driver protection disabled. After you install the driver, the icon will change and the yellow question mark will disappear.
Now that all the prep-work is complete, navigate to the c:\Streak folder (or wherever it was you unzipped the files to), and execute the batch file "run this to restore to froyo.bat". This will start flashing the files into the Streak. The whole process will take about 5-10 mins, and it will actually fail at the very end. It'll say it cannot locate P23.img. That's OK! P23 and P24 are for non-wifi models, so we're good. Reboot the Streak using a pin, and voila! It should be good as new.
If the batch file fails to start, or closes very quickly after launching, you probably do not have the APX driver installed, or there's a connectivity issue between the PC and the Streak. Let me know what you run into and I'll try to help.
Click to expand...
Click to collapse
Thanks for the details. I just used it to get my Streak 7 back to Froyo.
Do you know how I can install CWM or TWRP recovery. Tried both but when I try to start it factory reset (data only) option, it simply reset the data partition which tells me CWM/TWRP did not install correctly. When I install it streak screen says stormgr recovery installed.
Appreciate the help.
TWRP is not available for Froyo. And CWM ....I'm not even sure.
giveen said:
TWRP is not available for Froyo. And CWM ....I'm not even sure.
Click to expand...
Click to collapse
Really! If that's the case, how were pleople flashing streakdroid by djsteve and rooting?
Sent from my SGH-i747 using Tapatalk
Rooting is done via other ways
Like I said there might be a CWM for Froyo, I just dont know.
All TWRP were done by me, so I absolutely know there is none for Froyo.
marciolsf said:
There are a variety of threads on how to downgrade a DS7 back to froyo 2.2, so it always takes me a while to pierce things back together. For anybody in the same boat, here's a simple guide, with links. Many many thanks to all those that have come before me: TheManii, Giveen, DJ_Steve, and all the others on the DS7 community that refuse to let the thing die.
Download the complete restore file from here: http://d-h.st/iXc. Unzip the files somewhere, but the caveat here is that if the path is too long, the process will fail. Unzip it to c:\Streak, or something of the sort.
Download the ADB+Fastboot package from here: http://d-h.st/NMu, and unzip it somewhere, like c:\ADB
As detailed in this page (http://forum.xda-developers.com/showthread.php?t=1018809),
Plug the usb cable *on the streak only* (for now)
Hold down both volume buttons
While holding down the volume buttons, plug the other end of the usb cable on your PC. Keep holding the buttons until the lights on the side of the streak come on (the screen will *not* turn on)
Once the streak is lit up, you'll need to install the APX drivers. Go to the windows device manager, and you'll see a device with a yellow question mark (I believe it was called APX, sorry, writing mostly from memory here). Right click that device and update the driver, windows will ask you where the drivers are, navigate to C:\ADB (or wherever you unzipped the ADB files). On windows 7, you'll be prompted to install unsigned drivers. On windows 8, you'll have to boot with signed driver protection disabled. After you install the driver, the icon will change and the yellow question mark will disappear.
Now that all the prep-work is complete, navigate to the c:\Streak folder (or wherever it was you unzipped the files to), and execute the batch file "run this to restore to froyo.bat". This will start flashing the files into the Streak. The whole process will take about 5-10 mins, and it will actually fail at the very end. It'll say it cannot locate P23.img. That's OK! P23 and P24 are for non-wifi models, so we're good. Reboot the Streak using a pin, and voila! It should be good as new.
If the batch file fails to start, or closes very quickly after launching, you probably do not have the APX driver installed, or there's a connectivity issue between the PC and the Streak. Let me know what you run into and I'll try to help.
Click to expand...
Click to collapse
WOW!!! Thank you so much for posting this!! I was able to take my bricked Streak and bring it back to life! (Even though I will never use it probably, but i feel much better knowing i have a working streak than having a paperweight because I was being dumb with it)
Thank you Thank you Thank you!!!!