Related
I am running Windows 7 x64 I have no idea if following this guide on another operating system will work, this is just a step by step of EXACTLY how I did this, Not to say this is the only way. I have tested other methods and I have put in different variables and I have successfully gotten it to work several times in a row doing it this way while following jp4756's guide. I am sure this is not the only way to accomplish root, however this worked for me perfectly. PLEASE don't skimp out on any step. There is no shortcut here just follow the steps and jp4756's guide to the TEE!!!
Step 1.
Uninstall pdanet/htc sync/ any other thing you installed to get all this to work before
Unplug phone from computer usb cables and have phone powered on and in settings menu
Step 2.
download USBDeview(install it) easy to google it
download HTC SYNC(do NOT install it yet) for mytouch slide easy to google it
Step 3.
While in settings menu go to Application
go to Development
and check the box USB debugging
Step 4.
In settings go to Connect to PC
touch Default connection type and choose Sync
At this point you have the phone not plugged in, you have the setting on the phone changed, you have dowloaded usbdeview and installed it, and have htc sync dowloaded
Step 5.
Start USBDeview(some may have to right click the exe and run as administrator) and delete all android drivers and mytouch drivers, anything relating to android
Install HTC SYNC and let it completely install
Step 6.
Plug phone into computer and let the computer auto install drivers etc...
Step 7.
turn the phone off. Power on the Slide into the bootloader by Holding Down ( Volume Down + Power Button ) After it does its little thing your computer will beep and start auto installing drivers and stuff
Step 8.
If everything has gone according to plan in Device Manager it will show Android 1.0 or w/e with a exclamation point. Right click on that and choose Update Driver Software
2 options pop up choose Browse my Computer
then choose Let me Pick from list...
a list will appear giving lots of choices
choose Android Phone should be the first choice that says android....
then 3 options will appear, choose the 3rd one that has Composite in it and choose okay.
Step 9.
Now select Recovery from the bootloader menu
after it is done doing its thing completely 2 things will happen
1) In device manager you will now have something under disk drives
2) USBDeview a new driver will pop up at the end of the list, something like this:
Port_#0004.Hub_#0004 T-Mobile myTouch 3G Slide USB Device Mass Storage Yes No No No E: HT05RPS05696 6/16/2010 4:00:58 PM 6/16/2010 4:07:35 PM 0bb4 0ff9 08 06 50 USBSTOR USB Mass Storage Driver USBSTOR.SYS USB @usbstor.inf,%generic.mfg%;Compatible USB storage device
Step 10.
This new driver to appear shows Yes under the Connection column. This needs to be disabled. Right click on it and choose Disable Selected Device
after about 10 seconds it should no longer say Yes under connection column, if this does not happen then you are not running it under Admin.
Okay so now you are literally almost freaking there.
Step 11.
Now basically all you have to do is follow jp4756's guide starting with step 5. Im going to assume you already understand steps 1-4 in his guide. And you already have the package listed in his guide as well. You have already put those files where they belong
Step 12.
Okay so we are basically following his guide now. first things first
5. run the update.zip it will fail(MUST DO)
6. now in cmd type adb reboot recovery (don’t press enter)
7. in the recovery hit reboot system now( once it starts rebooting run that command rapidly untill back into recovery) <--- Basically while the phone is rebooting you are just hitting up arrow enter up arrow enter up arrow enter up arrow enter in CMD. You will know when you can stop when the CMD freezes for a sex, computer makes beeping noises and the phone reboots basically. It is headed for recovery and we must switch our command now
8.type adb devices(if it says nothing repeat the steps, if it says offline unplug it and then plug it back in, if it says recovery your fine) <---- Basically after you know its headed for recovery you change command to adb devices and you repeat previous procedure, up arrow enter up arrow enter up arrow enter etc.... I did not use loop, i did this all manually.
This may take a few tries, if it does not show offline then go back to step 6 rinse and repeat. You go back and forth just a few times and you will have it. Literally within about 3 tries you should accomplish the annoying goal of having offline stay there.
My job is done, follow guide and continue on your quest for root
There is no guarantee this will work for everyone. I am not claiming that this is 100% Im just giving an explanation as to how i got it and what might have been causing everyones trouble. Results may vary
Thank you to all the devs who made this possible and jp4756 for his wonderful guide
Wow that is just way to much stuff there...
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
1st: XP sp3 32bit w/ PDANet Drivers <--- Only ones that I could get to load, Forcing drivers wouldn't work in XP... also like I said before, make sure to close the PDANet Program in the Toolbar.. Also make sure to read the directions when installing PDANet...
2nd: Windows 7 64bit w/ Htc Drivers <---PDANet Drivers also work... You have to force the HTC Drivers in Devices Manager..
I think most people are having this problem because they aren't doing the USB Debug thing. But could be Wrong.
Also a side note my phone is running the USB Drive and not SYNC works just fine...
Also It just might be your computer so I would try and use a different one if you can.
jnight666 said:
Wow that is just way to much stuff there... I don't see how anyone has a problem with loop.
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
Also It just might be your computer so I would try and use a different one if you can.
Click to expand...
Click to collapse
Sorry that we all can't be as cool as you jnight666, but some of us are having real problems with no apparent explanation. I am an IT professional with access to every kind of computer used in the modern world, and trust me, I've tried all the ones that apply. Rubbing it in our faces that it was just so easy for you is just rude.
THE DRIVER MAKES NO DIFFERENCE FOLKS. IF YOU CHANGES DRIVERS AND THEN IT WORKED, IT'S PURELY A COINCIDENCE. PEOPLE HAVE GOTTEN THIS TO WORK ON MANY DIFFERENT DRIVERS.
THE CONNECT TO PC SETTING ON THE PHONE DOES NOT MAKE A DIFFERENCE IN FASTBOOT/RECOVRY FOLKS. IF YOU CHANGED THIS SETTING AND IT WORKED, IT'S PURELY A COINCIDENCE. PEOPLE HAVE GOTTEN THIS TO WORK ON VARIOUS DIFFERENT SETTINGS.
That being said, this didn't solve mine. I still cannot root.
And Yes, my cap locks was on purpose.
Okay, please dont come in here and start telling me how my method is wrong. I already stated there are other ways to accomplish it. I had already stated that this isnt 100%. I am merely offering an exact procedure that i duplicated SEVERAL times, with it working for me every time. If this isnt how you accomplished it then pls, theres no reason for you to be in this thread posting negative comments.
With that said fermunky, did you follow the procedure to the tee? - btw im not assuming anything so please dont take it personal. Im just trying to help ppl : )
My caps wasn't to be negative. There are too many people claiming the drivers were a key. And I am not saying yours said this, but it also doesn't clearly say it doesn't. That is all.
Completely understandable, and definitely no disrespect to you or anyone here
When I disable the Mass Storage I see other items in USBDeview that reference the Slide. I end up in a loop after rebooting and rapidly entering adb reboot recovery. I was seeing everything as your instructions explained.
Do you think it is worth a shot to disable all but one item for the Slide? Any suggestions would be greatly appreciated. I work in an IT Escalation Group and this has to be one of the toughest nuts I have tried to crack! LOL
Thanks,
jnight666 said:
Wow that is just way to much stuff there... I don't see how anyone has a problem with loop.
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
1st: XP sp3 32bit w/ PDANet Drivers <--- Only ones that I could get to load, Forcing drivers wouldn't work in XP... also like I said before, make sure to close the PDANet Program in the Toolbar.. Also make sure to read the directions when installing PDANet...
2nd: Windows 7 64bit w/ Htc Drivers <---PDANet Drivers also work... You have to force the HTC Drivers in Devices Manager..
I think most people are having this problem because they aren't doing the USB Debug thing. But could be Wrong.
Also a side note my phone is running the USB Drive and not SYNC works just fine...
And if anyone want to say anything about this I'll go load up my Pentium III machine and see if it works on that...
Also It just might be your computer so I would try and use a different one if you can.
Click to expand...
Click to collapse
3 different computers 3 different op systems installed uninstalled drivers different programs etc...some phones are hard to root its a ambiguous situation
Yeah sorry I wasn't trying to be rude.
I was just trying to be helpful, sorry if it came out that way...
I also have the loop not working issue but i usually only happens once or twice..
I feel your pain I had trouble with the push Update.zip part of this thing and I was trying it for hours...
I was just trying to tell you what worked for me...
If you tried different computer and still no luck then im guessing its the Phone that is the issue or the USB Cable...
gofizzle said:
When I disable the Mass Storage I see other items in USBDeview that reference the Slide. I end up in a loop after rebooting and rapidly entering adb reboot recovery. I was seeing everything as your instructions explained.
Do you think it is worth a shot to disable all but one item for the Slide? Any suggestions would be greatly appreciated. I work in an IT Escalation Group and this has to be one of the toughest nuts I have tried to crack! LOL
Thanks,
Click to expand...
Click to collapse
You definitely don't want to do that, as one of them is one that you need to be connected once you finally get to see offline stay. Are you rebooting using the method described in jp4756's guide? meaning your rebooting using the recovery option reboot, then in command doing the adb reboot recovery, then once you no the phone is gonna boot into recovery you switch to spamming adb devices? When you say your in a loop it sounds to me maybe your not doing the adb devices after the phone listened to your adb reboot recovery command
Followed your instructions...
No ! next to anything in device manager. Right clicked on Android Phone > Android ADB Device and went to properties to update the driver. Nothing in the HTC folder would work, they both said that they weren't applicable for the device...(this was in C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64)
before plugging your phone into your computer a single time, can you confirm that you started up USBDeview and uninstalled every single driver related to android, or mytouch or htc etc... Also before ever plugging your phone in a single time did you install htc completely?
Code3VW said:
Followed your instructions...
No ! next to anything in device manager. Right clicked on Android Phone > Android ADB Device and went to properties to update the driver. Nothing in the HTC folder would work, they both said that they weren't applicable for the device...(this was in C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64)
Click to expand...
Click to collapse
Right Click Android Phone - Properties - Driver - Update Driver - Browse My Computer - Let me pick from a list of device drivers (click this, don't give it the path in the upper box) - Have Disk - Browse to yours C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 - click androidusb.inf and select Open - OK - Unclick Show compatible hardware - Select "T-Mobile myTouch 3G Slide" - Next - All Done.
after getting some sleep and starting fresh, i tried this method again this morning. on the fourth or fifth try i got my slide to stick in offline mode. so then i unplugged it and plugged it back in to get into recovery. lost it, and now im on my 50th or so try to get it back to offline mode.
i need a stiff drink lol
it seems partially a driver issue and also an adb issue i thinks. it connects 'when it feels like it'
i'll report back if i make any progress.
btw im doing this on XP Pro SP3 fully updated
edit: I also noticed when adb does catch the slide, 2 instances of adb are running, then one closes and loses the phone. maybe this will help solve some of the problems
You've misunderstood that post. Only one instance of ADB will show when the loop is not running. Once you start the loop, another instance of ADB will show up and disappear many times. This is normal. As long as only one instance is showing before loop, you are fine.
fermunky said:
My caps wasn't to be negative. There are too many people claiming the drivers were a key. And I am not saying yours said this, but it also doesn't clearly say it doesn't. That is all.
Click to expand...
Click to collapse
I would just like to say that I have followed every method listed in these forums, achieved root the first try (using the updated update.zip). My problem occured when flashing the eng rom, I lost clockwork,root and now the phone runs like sh!t. Yes, superuser was installed and yes my pc no longer recognizes the phone when searching for adb devices after pushing the first 2 files from the eng flash walkthrough.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
mtjnkee said:
I would just like to say that I have followed every method listed in these forums, achieved root the first try (using the updated update.zip). My problem occured when flashing the eng rom, I lost clockwork,root and now the phone runs like sh!t. Yes, superuser was installed and yes my pc no longer recognizes the phone when searching for adb devices after pushing the first 2 files from the eng flash walkthrough.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Click to expand...
Click to collapse
maybe your downloads were corrupted. that's really strange...
man, that really sucks! I am truely sorry...
after spending 20 hours or so on rooting, I really feel your pain.
After I reboot into recovery mode and then use adb to check for my device I never get it to show up. Just so I am clear when you say 'spamming your device' you mean after reboot and rapidly entering the reboot recovery command, then looking for device with adb devices command. I never get it to show.
Thanks for the reply!
No devices in adb?
So I had this same problem with my MT3G. Type in "adb devices" kills the last device and it lists connected devices and NONE were listed. Not sure exactly what I did, but did eventually get it working. (I was trying to use the emulator)
Now though I'm having the same problem with my wife's MTS. Any ideas?
Ok, so I know this will eventually get buried in the forums but I thought I would attempt to give a little basic info here. Right now the QA section is flooded with people that have flashed and are now soft bricked (have problems but can recover) or hard bricked (have problems and cannot recover). I'm hoping that I can help some people prevent these issues to an extent.
Terminology, the differences in my opinion.
Soft brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your hardware buttons work or ADB works and you are able to boot into DOWNLOAD mode.
Hard brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your unlucky and hardware buttons do not allow access to DOWNLOAD mode or ADB is not downloading.
Also, after a new flash or flash to stock, it's a good idea to immediately enable USB debugging. Menu, Settings, Applications, Developement, check the box for USB debugging. It will make things easier later on.
1. First. BEFORE you flash, can you access download mode with your buttons??? Test it.
3 Methods.
Method 1: (ADB - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold Volume Up + Volume Down + Power
Method 3: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons (from i9000 just down, don't touch the power button)
Plug in the USB cable and continue holding both Volume buttons
If not, use designgears fix. http://forum.xda-developers.com/showthread.php?t=812434
2. Second. Download the SDK, drivers for your PC, and learn some basic ADB commands, ie, adb reboot download, adb reboot recovery, adb shell. Here's my quick guide. ADB can be used when the OS is running, when in recovery, and when stuck on ATT boot screen.
Here's what I do. After you download the sdk and unzip. There is a folder called tools. I copy that to c:
Then open a command prompt and type,
C:
CD tools
Then issue adb commands.
adb reboot, adb reboot download or whatever command you need.
Of course make sure your phone is connected via USB and debugging is enabled.
Here's another method for using adb.
1) start-> run-> sysdm.cpl
this will start the system properties. you can reach this from right clicking "My Computer" and hitting properties. Windows 7 though is different. The above method is most universal.
2) Move to Advanced Tab that pops up. From there click the "Environment Variables" button.
http://wtfokc.com/sef****/sysdm-1.gif
3) In the window that pops up, find the "PATH" area in the "System Variables" listbox at the bottom:
http://wtfokc.com/sef****/sysdm-2.gif
4) Click edit again, put in path to the AndroidSDK tools folder. Do it like shown otherwise you can biff something up. DO NOT REMOVE ANYTHING. Just add a SEMICOLON ( ; ) to the last of the line that's already there, then the path to the folder.
http://wtfokc.com/sef****/sysdm-3.gif
5) If on Win7 you shouldnt have to reboot. XP however will. Then you are set. You can now just load a CMD prompt and do ADB without having to CD TOOLS.
3. Third. Install Clockwork Recovery! Root your phone and download ROM Manager from market. Install Clockwork recovery from ROM Manager. BOOT into recovery to make sure it works. You will have to choose reinstall packages from stock recovery. What ROM Manager does, it put an update.zip on the root of your SDcard, then when you choose reinstall packages from stock recovery it install update.zip. I personally leave the update.zip file on my sdcard at all times, just in case.
Once you have clockwork installed, make a Nandroid backup of a good running rom. In case something happens, if you can boot into recovery, then you can possibly restore your nandroid to at least get you up and running quickly, and without the need of a pc.
NEW Info!!! You can recover from a hard brick, maybe. Here's how to create a USB Jig to reproduce the button download mode for you folks who don't have it.
http://forum.xda-developers.com/showthread.php?t=841512
Here's another thread about the USB Jig method.
http://forum.xda-developers.com/showthread.php?t=819551&highlight=USB+jig
If my captivate was one that had the missing button recovery/download out of the box, I would probably know how to make a USB jig or have one already before flashing. Even with the 3 button fixes that are out, it looks like some people are still bricking.
****Disclaimer****
This is just from personal exprience. I have flashed most roms available, and I have experienced every variation of soft brick mentioned above and have recovered.
I find that being able to get your phone into download mode and knowing how to use Odin will be your 2 biggest life savers after something bad happens.
This will not keep you from getting a bad flash or something else, but having this knowledge ahead of time may help you recover from issues more quickly and without asking a question on the forums that have been asked dozens of times.
Also, personally, if I cannot perform step 1, access download mode with buttons, I personally would be VERY cautious about flashing! ADB reboot download is nice, but if you are stuck at ATT logo or phone--!--PC mode then ADB doesn't work, YOU HAVE TO USE BUTTONS.
Just my 2 cents, take it or leave it.
Edit. Added some new info to post. Thanks for extra info guys. I'll mirror the links to the images later when not at work.
+sticky
excellent write up. a must-read for anyone even thinking about flashing
Original Post updated to add my information
bobbylx said:
ADB reboot download is nice, but if you are stuck at ATT logo
Click to expand...
Click to collapse
Ok first off something that should be added to this is always may sure you have usb debug mode Settings>Applications>Development>USB Debugging enabled on your phone. Don't take it out of debug mode. This will allow you to issue adb commands if you have.
If you are getting to the att logo screen and not beyond that and you have debug mode enabled then you can use adb to reboot into either recovery or download mode.
Steps
1: Get the command prompt up and que up the adb command you want to issue either reboot download or reboot recovery. Don't press enter yet.
2: When the att screen comes on your pc should make a notification sound that the device is connected.
3: On the second notification sound issue your adb command and the phone will reboot into the mode you selected.
Mileage may vary but should work.
This has saved me a few times.
STICKY
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks for the extra info. Malfuncion, awesome write up with pics, I'll add to first post later. I always forget about adding a system variable.
Sparker366, thanks, I always thought that at the ATT screen adb didn't, but you know what, I never tried.
I figured since I'm not a dev and don't have that knowledge I would try to help start this up to contribute a bit. And honestly, if you hop over to the QA sections there are so many threads that could be solved by knowing this info ahead of time. I doubt everyone will read it, but I hope it helps the ones that do.
bulletproof1013 said:
STICKY
Click to expand...
Click to collapse
+1
This is my first smart phone and first experience with Android. I also don't have any experience with linux. Fortunately, I was able to avoid problems when I first started by reading, reading, reading. This type of information would have been invaluable. In fact, the tip on keeping debug mode on all the time is great to know, and I never saw that before.
Sent from my SAMSUNG-SGH-I897 using XDA App
This thing is getting buried in the BS posts....BACK TO THE TOP!
definitely sticky
Bump Bump Bump
Great Info
Updated original post with extra info.
Shameless bump here. New version of Cog uploaded, so that means there will be questions soon.
Thanks, great info.
FWIW........
I feel like I am of average intelligence, and would think I could nail download mode everytime by the 3 button method, but damn if it is hit and miss for me every other time.
One way I found (I didnt discover it, but read it somewhere) to nail it EVERYTIME is to remove sd and sim. Plug the usb to the phone AND THE PC, while odin is sitting and waiting. Then while holding both up and down volume buttons, insert the battery. It works every time with no fuss.
Thanks for the post, my vote for sticky as well.
+1 sticky
Sent from my SAMSUNG-SGH-I897 using XDA App
Moving this to the top. More questions in QA that can be helped by reading these tips first.
I would also suggest that anyone who wants to flash actually test their phone's USB transfer ability before flashing.
The best way is to find a large file, perhaps one just under 2G in size and transfer it to the internal SD storage.
Test md5 checksums on the source and this file and make sure these match.
(you can use the 'md5sum <filename>' command from the terminal app, from Windows you can use a md5sum port for the source file win32 md5sum).
This will ensure your USB connection is stable enough for long, error free transfers to the phone.
Also important: it's useful to disable any powersave actions on your PC while using an app like ODIN.
Sorry all, moving this to the top. There are about 6 or 7 bricked phone Questions in Q & A now.
Awesome, clear and concise. Been trying to figure out how to make nandroid backups and this explained it very simply Thank you!
thanks for the reminder
there's so many steps to install a rom...
specially with download mode keycomb, i tend to not to remove sim and memory card cuz i dont want to lose or damaged my mcard. now i will remove each time!
another good reason flashing stock with odin before flashing new rom
I would also say its a good idea to back up your efs folder. Mine got all borked up when that jpc rom came out a while ago and it is a ton of work to fix. Sgs tools copies your nvdata.bin and. /nvdata.bak files to your sd card if you do a product code check. Or you can use root explorer.
I have bootloader 30.04 after using liberty 1.5 I wanted to try out Rubix Focused. Everything was going well till my I tried to flash the watermarkd theme. Went through all the steps rebooted using Koush bootstrapper rocovery and when it restarted stuck at splash screen. After searching around I found out I could get into bootloader menu and reflash. My phone said low batteery cannot program. After cutting a USB in half and jump starting my battery I was able to get it into bootloader and it said battery ok, okay to program. Connect data cable. Make a long story short RSD lite will not recognize my phone I was using 4.9 and was later recommended to use 4.8 as a lot of people had trouble with 4.9 Any advice on this and how I can bring my phone back to life? I can get into boostrap recovery on the Android Recovery system which we all know is kinda useless for the purpose. Am I going to have to SBF Flash my phone? What if it wont recognize the phone after using 4.8 What are my options?! I need to get my phone up and running asap and i've been working on this for like 3 days now. Can anyone give me detailed instructions that could help me restore my phone? I did make a nandroid backup too, I just cant get to the bootstrap recovery for some reason. Only bootloader or Android Recovery. Please Help!!
Make sure you have the latest drivers installed. What OS are you using? If using Windows 7 you have to run as administrator(by holding shift + right click then click run as administrator . Also I had to rename my sbf file to C:/abc.sbf my computer would only recognize the sbf on the root of my C drive.
Hi guys
Let me start off by saying..I should have never attempted this myself.
I'm hoping somebody could please help me with my somewhat-bricked device..bricked in the sense that I don't know what to do with it. (i'm a noob to this). I've tried installing a custom rom and completely screwed up my dell streak 5.
So the phone doesn't boot anymore and just takes me to the option to install update.pkg off the sd card. I added the file along with recovery.img to the sd card.
360 17397 00 May 31, 2011 PKG Recovery Hash Latest Retail rom
My problem is that I cannot for whatever reason get Flashboot to work in order to flash the recovery.img first. under device manager you see android phone/android adb interface but still can't manage the connection to use cmd prompt/fastboot.
Is there any other way of getting the recovery.img to work without fastboot..maybe thru the sd card. I have no idea what i'm doing anymore. I've tried installing the update.pkg but after installation it just stays on the dell logo loading screen forever.
PLEASE help if you can.
Well lets start off to get you back on a stock rom, as it sounds like that would be the easiest at this point. We can move on to a custom rom from there.
The pkg file you downloaded....did you rename it update.pkg ?
If not, rename it update.pkg and make sure it is on the root of your sd card. Get to the recovery menu where you have the option of upgrading from update.pkg and choose it. In about 5 minutes, you'll have a clean stock rom.
I tried installing the 360 rom listed on http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
I did name it update.pkg
It went through the installation phase but on reboot it doesn't get past the Dell Logo loading screen. Any suggestions?
On the screen where you choose upgrade from update.pkg, choose factory reset and see if that helps
Tried both..unfortunately, same end.
Is flashing recovery a required step prior to doing this..because I was unable to do that.
Also, Thank you for taking an interest. I really appreciate it.
yes, you need to have the recovery for the rom you are flashing (at least when it comes to stock roms). My understanding is that the pkg file is encrypted and the recovery decrypts it.
I'm going to try to start from scratch here. I am also assuming you are using a Windows PC.
Download the drivers from Dell. Here's the link:
http://support.euro.dell.com/suppor...dateid=-1&formatid=-1&source=-1&fileid=433681
Install them and reboot your pc.
Download MultiRecoveryFlasher from here:
http://forum.xda-developers.com/showthread.php?t=1000455
Extract it to somewhere on you pc where you can find it.
Now this hasn't been updated to include 360's recovery, but that's ok. We don't have to run the utility. It's the support files that are included that we are going to use.
Download the recovery.img for 360 (which I think you have already done)
Put the recovery.img in the root folder of MultiRecoveryFlasher. There should be other files in there such as fastboot.exe, adb.exe, etc.
Power down your phone and restart it in fastboot mode (hold down camera and power button together until you get a white screen. When fastboot appears in upper right, select it and plug your phone into your pc)
Verify the phone displays fastboot ready
Open a command prompt on your PC
Type in the following command: fastboot.exe -i 0x413c flash recovery recovery.img
Once that is done type in the following command: fastboot.exe reboot
Get ready to hold down the Volume + and - as soon as the screen goes black.
Now choose Upgrade from update.pkg
It should work now. If not, someone else may have to help you with another method such as QDL tool. I've never had to use that.
This is a screenshot of the problem i keep running into. i installed the drivers just as you said and am at the step with fastboot.
imgur [dot] com/gw2A0
Any advice? Thanks again
im an idiot.
i got fastboot to run and send over the recovery.img
currently installing the update.pkg but its still stuck at the Dell Logo screen upon reboot. No idea what is going on.
FIXED. You're a miracle worker. Thank you so much.
Only problem I have now is an irritating sequence of flashing buttons every now and then. Have you had a similar issue in the past?
THANK YOU so much again!
Are you on a stock rom still? Or have you moved on to a custom rom? Typically the flashing led's happen when you are running a rom with an "incompatible" baseband, but that should be pretty near impossible if you are running a rom installed from an update.pkg rather than an update.zip.
running the update pkg off the wiki site.
Only other problem I've noticed is that I can't get it to root. I've tried gingerbreak and superoneclick..both of which worked flawlessly in the past.
Baseband GAUSB1A134700-US
KERNEL 2.6.32.9-PERF
BUILD 17397
I really want another crack at getting streakdroid, but the phone just isn't budging. Tempted to flash/install another rom but worried as heck that this same incident is going to come up. (the flashing lights started after i updated the AMSS and DSP last night--my first attempt at installing streakdroid 2.3).
Installing the stock rom via the update.pkg file will overwrite the amss and dsp1. That's the biggest difference to the end user on update.pkg vs update.zip. It's the actual recommended way to install a baseband. There are several firmwares, besides amss and dsp1, that get installed with a pkg.
Now that you have MultiRecoveryFlasher on your pc, installed StreakMod (custom recovery) should be a breeze for you. The only thing to watch out for is since you have a stock rom now, the first time it boots it will rewrite the recovery back to stock. Here is how to get around this:
Download the custom rom of your choice.
Place the zip file on the root of your sd card.
Get your phone back in fastboot mode
Using MultiRecoveryFlasher, flash StreakMod
As soon as the screen goes black for the reboot, hold the volume +/- keys.
Choose option 2 again, this time it should take you into StreakMod
Choose flash from update.zip
On the next screen, choose search for zip file (similar wording)
Choose the custom rom from earlier
Let it do it's thing.
Choose reboot system now
Again, as soon as the screen goes dark, hold Volume +/-
Now choose option 1 - Factory Rest
Let it do it's thing.
It should boot up now and your custom recovery will stay intact.
Let me give you some friendly advice: Streakdroid 2.3 is too much of a work in progress. Install one of the other Streakdroids, Longhorn, Simple Streak, or even my Streakin' 354. Play with it for a while and learn a little more before jumping into one that may not be as stable.
As far as rooting a stock rom, the preferred method is via superuser.zip. I'm not at home, so I don't have the file to upload for you, but its on these Dell Streak forums somewhere. You have to have a custom recovery to use it though. The custom roms are all rooted already.
Thank you for everything
No problem. Did you get it working?
Sent from my Dell Streak using xda premium
Absolutely and I couldn't have done it without you. If you had written out just one of the x number of tutorials out there, I don't think anyone would have run into the problems I did at first.
Streakdroid 191 runs like a charm---snappy and more responsive than stock ever was.
Glad to hear it...I was lost when I first started too. Someone helped me out and I just like to pay it forward. It's what makes this forum my favorite.
lordmorphous said:
Glad to hear it...I was lost when I first started too. Someone helped me out and I just like to pay it forward. It's what makes this forum my favorite.
Click to expand...
Click to collapse
Hi guys.. Hi Mr Lordmorphous.. im a super noobie in dell streak 5.. i got my dell streak a month ago.. today my phone doesnt work.. im stuck on Dell logo when i am going to switch it to on.. i really dont know where to start and how to type the codes like you are talking about like .pkg ing. etc. .. when im pressing the factory reset nothing happens.. i also tried to click software upgrade via update.pkg on SD card and nothing happens .. i clicked also the screen calibration it says *successful calibration done*.. im totally lost.. can u help me how to start from beginning (like for super noobie like me)? also the codes that im going to type in pc.. thanks in advance!
dwadetiu said:
Hi guys.. Hi Mr Lordmorphous.. im a super noobie in dell streak 5.. i got my dell streak a month ago.. today my phone doesnt work.. im stuck on Dell logo when i am going to switch it to on.. i really dont know where to start and how to type the codes like you are talking about like .pkg ing. etc. .. when im pressing the factory reset nothing happens.. i also tried to click software upgrade via update.pkg on SD card and nothing happens .. i clicked also the screen calibration it says *successful calibration done*.. im totally lost.. can u help me how to start from beginning (like for super noobie like me)? also the codes that im going to type in pc.. thanks in advance!
Click to expand...
Click to collapse
RTFM
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
Hi again guys.. and mr lordmorphous!
im following what you told him (aaivazi)..
I'm going to try to start from scratch here. I am also assuming you are using a Windows PC.
Download the drivers from Dell. Here's the link:
http://support.euro.dell.com/support...&fileid=433681
Install them and reboot your pc.
Download MultiRecoveryFlasher from here:
http://forum.xda-developers.com/show....php?t=1000455
Extract it to somewhere on you pc where you can find it.
Now this hasn't been updated to include 360's recovery, but that's ok. We don't have to run the utility. It's the support files that are included that we are going to use.
Download the recovery.img for 360 (which I think you have already done)
Put the recovery.img in the root folder of MultiRecoveryFlasher. There should be other files in there such as fastboot.exe, adb.exe, etc.
Power down your phone and restart it in fastboot mode (hold down camera and power button together until you get a white screen. When fastboot appears in upper right, select it and plug your phone into your pc)
Verify the phone displays fastboot ready
Open a command prompt on your PC
Type in the following command: fastboot.exe -i 0x413c flash recovery recovery.img
(im already here but this is what the command prompt says:
'fastboot.exe' is not recognized as an internal or external command, operable program or batch file.)
what should i do ?
Streak4ever said:
RTFM
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
Click to expand...
Click to collapse
hi streak4ever thanks for reply.. what does RTFM means? thanks
Hi Guys,
I am a noob to xda so please bear with me...
Hoping someone can help me out here.. I will try and explain in as much detail as possible and provide you with as much Info from my phone as I can.
Firstly my phones details
Motorola Atrix 4g (UK version) Second phone as busted the last one. Bought outright as a retail sale.
Orange UK
System Version: 45.31.0.MB860.Retail.en.GB
Android Version: 2.3.4 (After UK released update)
Baseband Version: N_01.100.00R
Webtop Version: WT-1.2.0.133_38
Kernel Version: 2.66.32.9 [email protected]#2
Ok so, decided to root my phone. To do so I used petesMotorolaRootTools_V1.07 found on the website psouza4.com/bionic/
This worked fine and an app installed from the App Market confirmed that the phone was Rooted and had Superuser permissions.
Next I downloaded ClockWorkMod Rom Manager from the Market Inc Premium, SetCPU, Rom Toolbox & Titanium Backup Free. I had a quick look at these apps once downloaded but didnt really do a lot,
However, when Rom Manager opened it promted me to Flash ClockWorkMod Recovery, Which I did and then selected Back up current Rom. I also did this, (bear with me it gets a little vague here as to what I remember seeing)
Now I'm sure it said something like Nandroid Backup, which I selected. It proceeded to say something along the lines of, Backing up or phone will now reboot??
Anyhow, what ever it said, it started to reboot. The Motorola Red Circle logo came up but then at the top it said reboot failed and something ilse that didnt make sense then froze. I pulled the battery and rebooted. Seemed to work fine. Maybe a touch laggy but nothing to bad.
Next did my research into what ROM I'm likely to want to try. Found a few but seemed from what I have read on various forums that they dont work well for uk phones. Then decided perhaps then flashing should be left alone and went back to PetesMotorolaTools and unrooted. before I unrooted however i removed all apps that required root access first. Possibly a mistake?
I noticed that a few preinstalled apps werent working, nothing important or anything I use but there icons were like Blue settings icons all the same.
Did a factory reset through the handset also, in an attempt to return to factory settings.. not much changed really. Also tried to update software though the Motorola website but it said I was all up to date.
I thought maybe that something went wrong so I rooted again. This time the unroot failed. I then dowloaded all the rooted apps that I had before and then unrooted. This worked. Not sure if coincedence or not but it worked and when unrooting it said unfreezing apps about 6 times, before the complete message. Then uninstalled the root apps again.
Most, not all but most of those preinstalled apps were then working ok.
I read a little bit more bout Roms and decided to have another bash. Found and downloaded a few to comp. Then I place an SD card into phone and Flashed it. then tranferred a copy to its root.
Rooted the phone in the same way as before. Downloaded all the apps again opened CWM RM, Flashed CWM Recovery again as was unsure that the time I did it before would work. Then selected back up Current ROM. Without any message this time the phone started to reboot.
It came up with the recovery screen (Android man and !) From what I have read the next step is to tap the bottom right of the screen to bring up the menu.
This did not work nor did anything else happen. After waiting about 25mins with nothing more happening I pulled the batt again.
Decided I'd boot into recovery mode manually and see if the bottom right of screen would work that way. turned off then held On and down Vol. Fastboot showed at top, Scrolled and selected Android recovery. Same Android Man and ! came up, tried tapping the bottom right of screen again.... It didnt work.
Read more on the forums where someone said that pushing up and down on the Vol buttons works. Tried this and hey presto.. a new menu appears. Shown as follows.
Android system recovery <3e>
Android system recovery utility
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
No back up options so rebooted....
Anyway thought I'd try a few times to use CWM RM to flash a rom to device. Each time it took me throught this same process.
Eventually I though what the hec just try and flash it...
So I selected the apply update from sdcard option.
Then selected the ROM I saved to SD Card.
Then the following text appears on screen in yellow.
--Install /sdcard...
finding update package...
Openeing update package...
Verifying update package...
E:signature verification failed
Installation abborted
I tried this a few times to no avail. even tried downloading the roms from CWM RM with no change.
Read some more on the forums and somewhere read to rename the ROM update.zip
Did this and tried again.... No Joy!!!
Selected Fix permissions in an attempt to clean up and thats as far as I have got...
I'm at the end of my tether and dont know what to do...
Please, please, please someone help me get to the bottom of my dilemma..
Thanks for reading and any help in advance.
Just a little more info to help diagnose
CWM RM Details
Rom Manager Premium v4.8.1.3
Current Recovery: ClockworkMod 5.0.2.0
Latest Recover;ClockworkMod 5.0.2.0
Thanks again peoples for taking the time to at least read this..
No where in there did I see "I unlocked my bootloader"
That's fine that you're rooted, but to use CWM Recovery, install ROMs, make Nandroid Backups, etc. you need to unlock your bootloader first! See the international part of the Pudding thread (since your in UK) in the dev section.
Sent from my CM7 Atrix 4G
Ah Hah! You are correct at no point did I unlock my Booty, Thank you I shall give that a go and report back...
Ok so, I have trawled the forum and many others this avo on my research quest to unlock the bootloader as advised above but have been unsucessful so far.
I used the Pudding thread as you said.
when downloading the files advised I noticed that some were downloading as unrecognised files. I still proceeded to follow instructions as written.
Some of them like the RSD Lite I managed to unzip and extract with a programme I have however the next one needed said it was Undefined File type.
Anyway I deleted those files and tried following the other method listed underneath the driver via the link at "Guide for beginners provided by..."
This was unsucessfull as the "fastboot oem unlock" command was not recognised.
Pulled the batt and rebooted into normal mode and I'm back at SQ1
Bit stuck if anyone has any ideas..
Ok, here goes...
1) Make sure you have the drivers installed on your computer. (Available in Pudding Thread)
2) Go to pudding thread, and grab the Unlock Only IHOP sbf file (assuming your not on AT&T).
http://forum.xda-developers.com/showthread.php?t=1136261
"Unlock:
Unlocker only SBFs - These small 1mb SBF files will get your phone ready to fasboot oem unlock. They are the files most people should use.
ATT ONLY - Unlocker for 1.8.3 and 4.5.91 ATT firmwares
Orange/Bell/Telestra/Latin America/International users ONLY - Download IHOP"
3) Download & install RSD Lite. (Available in Pudding Thread)
4) Put phone in RSD Protocol Mode.
a) Power off phone
b) Upon Powering ON, hold Power Button + Volume UP
5) Connect Phone to computer via USB
6) unzip the IHOP sbf file to root of your C:\, open RSD Lite program, and drag sbf file onto File Name Box. Make sure RSD Lite sees your device connected to it, and then flash away.
7) After the sbf has flashed (hopefully without any errors), reboot your phone into fastboot mode (Power Button + Volume Down; when you see fastboot, press volume up to enter fastboot mode).
8) Re-connect phone to computer if you disconnected it.
9) In the folder where your fastboot files are located (if you don't have fastboot files, go download them from sticky in General Section), press Shift + Right Click, select Open Command Window Here.
10) With phone in fastboot mode, connected to PC and command window open in fastboot file location, type:
fastboot oem unlock
*This will give you your device #
Then type:
fastboot oem unlock [insert your # here]
10) Bootloader should unlock, then type fastboot reboot to reboot the phone. Should say Unlocked on boot screen now, if all went well.
11) Install Rom Racer's Recovery or Rom Manager, and you're good to go.
Think that about cover it... if you have any problems, give details of what is happening and at what step. Also, check the Pudding thread for possible solutions, as most problems have already been solved there.
Thank you for your explanation... I will give it a go when I get back from work tomorrow...
I appreciate you taking the time to help..
Sent from my MB860 using XDA App
Dcskeete said:
Thank you for your explanation... I will give it a go when I get back from work tomorrow...
I appreciate you taking the time to help..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
You should definatly also install busybox
Swiftks said:
Ok, here goes...
1) Make sure you have the drivers installed on your computer. (Available in Pudding Thread)
2) Go to pudding thread, and grab the Unlock Only IHOP sbf file (assuming your not on AT&T).
http://forum.xda-developers.com/showthread.php?t=1136261
"Unlock:
Unlocker only SBFs - These small 1mb SBF files will get your phone ready to fasboot oem unlock. They are the files most people should use.
ATT ONLY - Unlocker for 1.8.3 and 4.5.91 ATT firmwares
Orange/Bell/Telestra/Latin America/International users ONLY - Download IHOP"
3) Download & install RSD Lite. (Available in Pudding Thread)
4) Put phone in RSD Protocol Mode.
a) Power off phone
b) Upon Powering ON, hold Power Button + Volume UP
5) Connect Phone to computer via USB
6) unzip the IHOP sbf file to root of your C:\, open RSD Lite program, and drag sbf file onto File Name Box. Make sure RSD Lite sees your device connected to it, and then flash away.
7) After the sbf has flashed (hopefully without any errors), reboot your phone into fastboot mode (Power Button + Volume Down; when you see fastboot, press volume up to enter fastboot mode).
8) Re-connect phone to computer if you disconnected it.
9) In the folder where your fastboot files are located (if you don't have fastboot files, go download them from sticky in General Section), press Shift + Right Click, select Open Command Window Here.
10) With phone in fastboot mode, connected to PC and command window open in fastboot file location, type:
fastboot oem unlock
*This will give you your device #
Then type:
fastboot oem unlock [insert your # here]
10) Bootloader should unlock, then type fastboot reboot to reboot the phone. Should say Unlocked on boot screen now, if all went well.
11) Install Rom Racer's Recovery or Rom Manager, and you're good to go.
Think that about cover it... if you have any problems, give details of what is happening and at what step. Also, check the Pudding thread for possible solutions, as most problems have already been solved there.
Click to expand...
Click to collapse
A BIG THANKS!!!
Thanks so much for the advice and instructions... Unlocked beautifully... Now to find the ideal ROM....
Dont suppose there are any suggestions for International (UK) Atrix users??
Really appriciate the help..
Regards
Danny
I would recommend that you flashed TWRP 2.0 through CWM direct link. It lets you have touch screen in recovery; much easier! Then if you like CM7 you could try this or if you like the MIUI style (like me!) you would want to try this! It hasn't in-game audio yet but it's much cooler in my opinion. But Neutrino CM7 is really great!
Im not sure, maybe someone else can confirm. You should be using moto-fastboot to unlock & not regular fastboot, right?
Sent from my MB860 using xda premium
draken_1337 said:
I would recommend that you flashed TWRP 2.0 through CWM direct link. It lets you have touch screen in recovery; much easier! Then if you like CM7 you could try this or if you like the MIUI style (like me!) you would want to try this! It hasn't in-game audio yet but it's much cooler in my opinion. But Neutrino CM7 is really great!
Click to expand...
Click to collapse
People have had problems with TWRP.............stick with Romracers CWM, it's tried and trusted. If the touch screen in CWM gets you off, so be it, but I'd rather have a recovery that works with all ROM's, and not just some.