Recommendation for next step - Streak 5

[Guest warez71]

I am currently dead locked between gausb1a131500-us / gausb1a130900, Build 11548 & gausb1a131500-us / gausb1a131500 Build 15609.

My goal is to have the original stock 347 back. I seem to be getting close. I would stay with either of the above if the button lights would stop flashing. I am comfortable with fastboot, streakmod recovery, superuser procedures etc. I seem to be having the problem with combinations. If someone could advise the best course of action step by step I am sure that I will have the "so that's what I missed!!" epiphany.

5 days straight but I am going to get it...... :unsure:

****************************************************

Is it possible to use ROM manager from within Android to achieve this?

Looking into QDL Tool

Edited May 16, 2011 by warez71

[Guest warez71]

I can't believe not one person is willing to add anything to this!

I have spent 6 days and nights searching countless pages for procedures to correct my issue without success. As I am in the IT field I know how important it is to work with peers. That is the reason for this forum, right? Also, if you are a veteran here with an attitude towards me for being inexperienced here go scratch. Remember I am the one willing to learn and not afraid to ask.

[Guest Djp42]

I can't believe not one person is willing to add anything to this!

I have spent 6 days and nights searching countless pages for procedures to correct my issue without success. As I am in the IT field I know how important it is to work with peers. That is the reason for this forum, right? Also, if you are a veteran here with an attitude towards me for being inexperienced here go scratch. Remember I am the one willing to learn and not afraid to ask.

Sounds like an "IDTENT" problem to me. Try looking at the Wiki page on Xda developers.

[Guest warez71]

Sounds like an "IDTENT" problem to me. Try looking at the Wiki page on Xda developers.

How bout you GFY and the next time just come out and say it. Mask "idiot" better next time. You are the typical bottom feeder.

[Guest jmhalder]

How bout you GFY and the next time just come out and say it. Mask "idiot" better next time. You are the typical bottom feeder.

I'm NOT an IT professional, and I don't have any problems doing this stuff. :unsure:

I'm suprised you can't just fastboot flash a factory recovery, throw the most recent WWE build (351) on the SD card as "update.pkg", do the update via the factory recovery, then do a "factory reset" in the "pre"-recovery screen... I guess there are other internal SD partitions that can get jacked up, which QDL apparently will fix... I'd used QDL tool before, its easiest to just find a computer that's running XP, as Win 7 is a pain to TRULY disable driver verification. Steve has a decent video walkthough on how to use QDLTool.

[Guest Crinos512]

I can't believe not one person is willing to add anything to this!

I have spent 6 days and nights searching countless pages for procedures to correct my issue without success. As I am in the IT field I know how important it is to work with peers. That is the reason for this forum, right? Also, if you are a veteran here with an attitude towards me for being inexperienced here go scratch. Remember I am the one willing to learn and not afraid to ask.

Did you try the IRC channel? they got me sorted out pretty quickly.

irc.freenode.net


#dellstreak

...other than that I'd have to point out that going aggressive on the people you are asking for help is a good way to ensure that you work alone.

( I also am in the IT field and know that more important than working with peers, is getting along with them. )

Edited May 17, 2011 by Crinos512

[Guest Djp42]

Did you try the IRC channel? they got me sorted out pretty quickly.

irc.freenode.net


#dellstreak

...other than that I'd have to point out that going aggressive on the people you are asking for help is a good way to ensure that you work alone.

( I also am in the IT field and know that more important than working with peers, is getting along with them. )

Which is why i said the IDTENT problem. Figured if you can work that out then you're obviously not as stupid as you sound. If you continue coming across with the attitude you expressed in your second post then i'm pretty confident that people here and perhaps on other forums, are gonna be reluctant to help. That said, i'm not an IT proff, i'm just a noob and i hope that my pointing you to the Wiki on Xdadevelopers has helped in some way.

[Guest warez71]

I absolutely apologize for my attitude to all who took offense and specifically Djp42. This is frustration. I am no better than anyone here (information tecnology is my trade). What I SHOULD have conveyed is that with all the cumulative knowledge contained in all the postings if you are not familiar it is overwhelming (especially when your new device is two hours old and you FUBAR'd it). My experiance previously with other forums is to be jumped on for not knowing and being apprehensive to ask anything else. Yes, these guides and posts are informative and helpful. *POINT* Was using WIN 7 x64 and it was the first problem brought up by a member. QDL tutorial, amazing but hung on me and I have an unlocked 00 not a locked AT&T 02. Fastbboot issue - .BAT file was configured to run FASTBOOT-WINDOWS, instructions stated rename to FASTBOOT keeping the ".exe" (also said to choose OS).

Regardless of this and that I was looking for a to the point. That's not always the best. I'm not well off enough to just buy another one without saving and since it's an Android I figured no problem as opposed to my iPhone hacking. I am hardware to he core, not software and code. Again, I apologize. I am a tell you what you need to know guy from start to finish, since I need that.

If someone has the time to go over a few things I would love to work at it and guarenteed to pay it forward.

Crinos512 - per your post bottom (lol)

If your phone is having problems auto-rotating, or does not rotate at all in any app (like mine did). These steps should get you working again. This will be overkill in some cases but I like to cover all my bases when something is not working to begin with.

Note: This assumes you are running Android 2.2 (if you are not, you will not be able to perform the last step, but your phone should still work properly without it). Your phone will need to be rooted with busybox and you will need a terminal emulator app installed. I have attached the "Android Terminal Emulator" apk just in case you don't have or know what that is.

open your terminal type su press enter

type cd /data/system press enter

type rm ms3c_yamaha.cfg press enter

type cd /system/bin press enter

type ./sensorcalibutil_yamaha press enter

secure your phone on a flat level surface and gently press the enter key on your keyboard

type exit press enter

type exit press enter

Close your terminal and go to menu -> Display -> Horizantal calibration

turn your phone upside down with the bottom edge over hanging the table you used as a flat surface so that you can just barely see the calibration button when you are looking under the phone. Gently press the calibration button.

All done, you should be in working order!

***credit from copy - juise15th February 2011, 06:22 PM***

[Guest Crinos512]

Crinos512 - per your post bottom (lol)

If your phone is having problems auto-rotating, or does not rotate at all in any app (like mine did). These steps should get you working again. This will be overkill in some cases but I like to cover all my bases when something is not working to begin with.

...

You'll note that the upside down text in my sig is a link... :unsure:

Seriously though, go onto IRC to the #dellstreak channel.... that's where the experts hang out.

( Showing my age here: have you ever used IRC before? )

[Guest fards]

if I understood what your problem was then I'd stand a better chance of helping. I've read the first post several times and it doesn't make any sense.

you're deadlocked between several builds?

flashing LEDS mean you have the wrong boot.img for the baseband you have.

from what I understand there isn't a 347 .pkg file, just a nandroid backup, so you need to flash that if you want to get to 347.

but the leds will still flash if you don't have the 347 baseband with it.

why not do as suggested and flash the 351 pkg? it works

easiest way to get rid of flashing leds is to use a custom boot img, so flash streakdroid... 190 is based on 347 anyway.

Edited May 18, 2011 by fards

[Guest warez71]

if I understood what your problem was then I'd stand a better chance of helping. I've read the first post several times and it doesn't make any sense.

you're deadlocked between several builds?

flashing LEDS mean you have the wrong boot.img for the baseband you have.

from what I understand there isn't a 347 .pkg file, just a nandroid backup, so you need to flash that if you want to get to 347.

but the leds will still flash if you don't have the 347 baseband with it.

why not do as suggested and flash the 351 pkg? it works

easiest way to get rid of flashing leds is to use a custom boot img, so flash streakdroid... 190 is based on 347 anyway.

Instead of waiting and researching I installed different packages without understanding how it works for the device. What you pointed out is what I finally did last night with Streakdroid 190. Bang! Perfect flash with CR. I was hesitant to implement anything more than a Root for fear of ruining the device based on the posts that I had read. So looking to recover to stock was my blind quest. Having to piece together the puzzle without (immediate) support or with someone to bounce off of lead to my less than appealing candor. I work best with straight to the point direction. Much to learn and I appreciate the recommendation as that is exactly what I would have done when I read it with your O-10 grade. Thank you for taking the time.