I have acquired a number of these streaks. problem is all are stuck at a lock menu asking for a password which i dont have. or they get stuck at the dell screen and wont boot. im currently running windows 8.1 and seem to have an issue with the devices being reconigezed not sure if its the phone itself or issues with drivers. i have tried multiplue drivers from dell and other various sites with no luck. ive tried factory resets on i have also tried to get it to boot from the extrenal sd card with no luck. can anyone help shed some light on this? the whole purpose of this is have a phone when i go to korea and for a OBD2 reader/tuner.
You're lucky. I occasionally check the Streak forums, but it's a dead device now as virtually everyone has moved on to something more capable.
Regarding the units requiring a password at the lockscreen, assuming this is the standard Android lockscreen, a factory reset should eliminate the password (hold volume+ and volume-, press and hold power). If it doesn't, flashing a stock ROM should definitely fix it. From what I remember, the drivers don't work properly on Windows 8 and later, meaning you'll have to find a machine with XP, Vista, or 7 to flash stock ROMs on any of these units, assuming the units frozen at the boot screen didn't have their storage spaces cleared with the fastboot -erase command. Fastboot -erase is pretty much a death sentence for the Streak, due to a bug. The storage areas get wiped, and then locked into a read-only state, with no way to correct it.
Share that info about an OBDII reader/tuner?
Related
Tried to upgrade the ROM on an M1000 to 2003 SE from a 1.600 version and wound up with the following symptoms.
Only able to see the bootloader (v1.06, but computer recognises the device when in the USB cradle)
HimaUpgradeUT will run as far as the screen saying what ROM it's replacing (though it says that there is nothing on the device itself). Then when I press "next" it just hangs on the erasing ROM 0% screen until I get an Error 112.
Tried using two different computers and still get the same error.
Tried different HimaUpgradeUTs and still get the same error.
Tried hard resets, soft resets, reinstalling ActiveSync, disabling ActiveSync etc.
Going insane and need suggestions. Help!
I think your best bet is to revert to the original ROM. I thought it was on this forum, but I just looked and can't find it, but...
http://www2.orange.co.uk/servlet/Sa...096364420640&product=Feature&t=Product#answer
Should get you to the ROM download page on ORANGE UK, where you have a choice of with and without MMS ROM images.
If you can get your 'phone back - that might be a start.
Richard
Edit - just tried the link and it isn't that good. Go to 'Your phones features'.
Sadly I've already tried that. But it won't accept anything. Thanks for the suggestion though.
I at a loss as to what exactly the problem is. I've checked the log file from the HimaUpdateUT file and it keeps trying to erase the original ROM but can't. Which is weird because there doesn't seem to be anything on the device. I wish there was better logging by the program.
I'm starting to consider exploring Bootloader commands to see what I can find.
did you put your device in BOOTLOADER MODE?
PROCEDURE: PRESS ON/OFF POWER BUTTON-SOFTRESET BUTTON-NAV PAD
Yep. In fact I can't get it out of bootloader mode. Have hard reset it several times.
Hi,
do you have SD card???
buzz
Ironically I just ordered one before I fried the device. I guess using it to transfer the ROM image is a possibility. It looks difficult though.
Hey all,
I did my searching for the last several hours, and am feeling pretty weak. I know there are several other posts with this error - but please let me explain my situation.
Phone was running 2.3.6. I am unsure how it was originally unlocked (carrier unlocked) and bought it used. To my knowledge it did not have root access... (though the advert said it did - running SU in Terminal to show if it had access failed)
I tried doing a factory reset on the phone because it kept acting weird. Just rebooting 10 times a day, and wifi not working either.
Since the reset the phone has not made it past the M Dual Core screen.
Edit as I type: As I type this, I FINALLY got into recovery mode. It took a long time... is that normal? I mean.. loongggg. Now i see other posts state I just need to click the bottom right corner above the search key and I should be on the way to recovering the device...
This however is not working...
I will keep the phone plugged in over night and see if it just needed more time I suppose. Can you guys recommend anything?
I am on win7 - should have the device drivers installed (though, Windows doesn't seem to recognize this with a notification bubble). I know the phone was not on USB Debug Mode when I clicked 'factory reset'.. would it have retained this?
I will update as i have more information.. otherwise if I am missing something please let me know.
Thanks again,
-k
Try booting into recovery mode by holding volume down while turning on. When the menu appears keep pressing volume down until it says android recovery and then press volume up to select it. If an android Guy with a warning sign shows up, press volume down and up. A menu should appear soon. Try to do a data wipe and factory reset from there.
Sent from my MB860 using XDA App
Hi ar31791, thank you for the reply.
That worked to put me into a recovery mode - very nice. Is the button combo different depending on the version of android your'e running, or just phone dependent? I appreciate that.
Couple follow up questions if you guys don't mind and can help
- after the factory reset - my boot time is incredibly slow.... like 30 minutes to boot kinda thing. I tried to factory reset several times since, and its the same issue.
- my data is not working on the phone. I used the apn suggestions from all sites I've found, rebooted (took a while) tried data roaming, etc, but it just doesn't work. I have a decent idea that the apn's are correct because the mms apn worked fine with a test picture message.
My main concern is the incredible lengthy boot time and the data no longer working. The issue with wifi still showing 'error' when enabling it was not resolved by the reset (I didn't think it would - I was reading other posts where it is suspected as a hardware issue).
Thanks again for the reads, and replies. I appreciate the help!
-kenny
You need romracers or cwm. Unless yer going to stay stock.
Sent from my MB860 using xda premium
Is this an att or a rogers/international phone? Best bet would be to flash pudding and than cwm + custom roms
hey again- thank you for the replies.. seriously. much appreciated.
phalanx, i dont mind staying stock but would that not allow the data connection to work correctly? i found a few posts based on the romracer. i lack the hands on experience, but it looks like i just need to follow the steps for an adb push and then install eh?
you mention staying stock, is that an option? info on my setup below
crnkoj, i am running a bell phone on a fido network in canada. bought on ebay pre unlocked. i do not bekieve it is rooted. phone, mms and text work fine, it seems to be a problem finding a data network at this moment.
thanks again guys, ill be taking a look into the tutorials for romracer and cwm, and giver a shot. lemme know if you have any further ideas, questions or anything you think i might need to know.
edit.. also, whats the deal with the crazyyyyy long boot up time?
kenny
(send from a mobile.. please excuse any typos or punctuation errors)
No its just that with an unlocked bootloader you can flash a new.recovery and that makes it easier to flash roms and also kernels and radios. Kernels and radios can affect your ability to connect with data and can even affect the speeds.
Sent from my MB860 using xda premium
I had a similar situation. So, i did a full wipe installed the rom did another full wipe then installed the appropriate kernel and booted it up. I believe you nedd to install the right kernel per the instructions. It will mot boot if the kernel is not correct.
Sent from my MB860 using xda premium
Thanks again guys,
Man it's a funny issue. I am always able to get in and factory wipe the device, but it seems that sometimes that damn M screen will sit forever. I left it over the course of a movie and a half (probably 3 hours) and that screen was still just sitting there.
I get into the fastboot menu easy enough before that screen hangs, and sometimes i can get into the Boot Android (without BP) (I believe it's called) and sometimes it hangs, and sometimes it works.
Other times, like right now, it boots just fine and kinda fast.
I am having an issue with the RSDLite application recognizing my phone. It did once - then hung at 94% flash of the pudding tutorial. I didn't realize the tutorial says to keep the phone plugged in for 10 minutes even after a fail to see if it actually completes. I havent been able to have the software recognize the phone since- I've installed and reinstalled the motorola drivers, set the phone to usb debugging, and was able to try 2 computers, and 2 different cables. I'll giver another shot though.
I am pretty sure my boot loader was unlocked (as I said I had this all done from an ebay purchase) so I think I can just proceed to the flashing, but if there is a way to confirm that it is indeed locked, I'll take the advice.
The more I read though, it looks like I might just need to send this beast in for a service call with Motorola, because of that damn wifi "error" error. I'd hate to go through all this and realize it still will not work.
Thanks for the replies, I'll always take more suggestions, and if you guys think I'm on the wrong path, let me know. I'll keep searchin dem' forums
If your bootloader is unlocked it will say unlocked in white letters on that M boot logo screen. Did you run "fastboot oem unlock" after the rsd flash?
Sent from my MB860 using XDA App
Greetings Ladies and Gents. I have a peculiar problem that it seems no one else has had. My OS is corrupt! Well, it's not really my phone, it's a co-workers. Here's what I know:
He has the Zurg root files on his SD
it is at the stock recovery
I *can* get into the OS
I have to do a factory reset before every boot or else it boot loops
Immediately upon getting into the OS, the android setup process crashes
When I'm in the OS, there is no launcher and the soft keys vibrate, but do nothing
If i plug the phone into my computer, USB connection pops up
It is not in debug mode
I have tried about 4 different roms found in different places online and although some of them report in as *signed* none of them have passed the verification
The power/lock button will lock and unlock. Volume up and down as well as camera hard buttons do not work in OS, but do work in recovery
The lock screen does come up and is not password-ed
Any ideas how I might be able to get a working OS for this co-worker of mine? Thanks in advance for your help
Anyone? Bueller? Bueller? Bueller?
Last bump before I give up
Hello everyone.
I ran into a serious mishap with my brand new work phone. I was handed a HTC radar c110 with Windows phone 7.5 to work with, but the phone had a little issue with calls and I decided to do a factory reset to see if it would sort it out.
So I searched on how to do a factory reset, and took a quick run to the bathroom before I could complete it. But my friend decided to finish it off for me, and somehow mispressed some button I guess, because a screen saying "Omega system loader menu" came up instead, with "FFU method" and 2 options, "MTPz" and "TFTP protocol". She took a blind guess at TFTP protocol, and when I came back the phone wouldn't turn on, it keeps resetting every few seconds and only says "TFTP protocol" on the bottom of the screen. Sometimes an image asking to connect the phone to the pc comes up.
I have tried the factory reset after this a couple of times, but when the phone restarts, this TFTP protocol image still comes up and the phone won't start. My guess is I have effed up the OS. What do I do now? Any guess? I don't want to go to my new job on monday and say that I screwed up the phone they gave me yesterday :S.
Any help is very appreciated. Thank you very much.
EDIT: I can get to USB host mode screen (white screen with "enter usb host mode"), and the white screen where you can "image crc" and "factory reset", not sure if it's called bootloader screen? I'm pretty sure I can get somewhere from one of these screens, but I'm not familiar with rom flashing and bootloaders at all.
EDIT2: I have been investigating further and I can now access the bootloader mode (the factory reset one), update mode (the omega system loader one) and usb host mode. I just need to figure out how to flash a rom (preferably an official one, as it's a company phone) into it now.
EDIT3: I got it fixed, not really sure how, but trying different things ended up booting the phone as normal. I am back to having the same problem as before though, but better than having a bricked phone I guess.
any idea what the solution ended up being?
I think reverting back to my original stock rom might be the answer for me, how did you do it?
I've just managed to do the same..
Any help as to how to sort out this issue? TFTP Protocol appears at the bottom of the screen with all the other symptoms referred above.. PLEASE SOMEONE HELP.
Hey guys, this evening I've been trying to wipe an old T-mobile g2x and get it set up so my parents can use it as a remote in their living room for chromecast and whatnot.
I was doing a factory reset and clearing cache/formatting sd cards in Recovery mode because cyanogenmod wouldn't connect to the wi-fi network to let me login to my accounts (using it without a sim card). As soon as I did the formatting (I only wiped the sd-card contents, I have no clue how this happened)....all of these problems started and I've made zero progress whatsoever ever since.
But it's bricked....really hard. The symptoms as of now:
Persistant boot loop. The only thing that has shown up on the screen since it happened is the LG logo, and a charging battery if it's plugged in & not 'booted on' (which is when the LG logo pops up)
Recovery mode is completely gone. Button combinations do not work at all.
USB won't connect. When plugged into my computer, it only registers as "Unknown device" and no matter what drivers I install nothing changes this. This prevents me from using any sort of utilities that need a pc connection, as far as I've been able to figure.
I tried to find a way to get android to boot 100% from the micro sd-card since it's the only way I can actually get data into my phone it seems, but all the suggestions I've seen still require recovery mode to access. I have no idea what to do anymore. Does it seem like I'm pretty screwed? Should I donate my new brick to house builders?
Thank you so much guys, long time reader first time poster These forums have saved my butt so many times! Cheers :good: