Related
I know, I know, there are loads of threads like this but I must be lacking something in the brains department as I've spent the last 6 days (since I got my orange tytn) reading this forum trying to understand how to unlock the thing without turning it into a brick and then to flash a rom and radio.
Everything I read on here has people contradicting other people and I end up not having a clue what to do in the end.
HEELLLLP!!!
To confuse matters even more I thought I'd got it sussed and then read about roms having/not having a CUBE!!!! WTF???? I then gave up and started typing this thread...
Here's what I think......and PLEASE correct me or agree with me....
Firstly I seem to be stumbling at the first hurdle since I have an orange tytn and that it seems is the worse to have for some reason???
I thought I'd start off simply by using the kaiser simunlocker to unlock the phone (by jocky) but then came across something called hardspl with all its variances, so OK lets go with the flow and dismiss the hardspl step for now assuming I can do it and read on...
Assuming I could ever find a program that makes a backup of the rom I've got I'd carry on with the unlocker until I get to the step (step 10) that says download the original radio..............this of course doesn't exist (1.27.14.32) so I look for a proggy that downloads the radio to use at this point. Here's where I come unstuck again.........no proggy!!
At this point I must assume that this may not be possible on the model I've got if I want to be sure I can make it original again.
Could someone please confirm this so I can accept the fact that I have to use what came with the phone and save myself a few hours a night getting nowhere...
Sorry for my rant but I'm frustrated that my old brain can't figure this out and giving up seems to be the only option. I completely understand that I'll get flamed for this since I'm a noobie and asking again what numerous otheres have asked but I accept that...
I have great respect for all you guys that can actually understand this on first reading and especially the people who produce this stuff....
Thanks again folks
familyguy said:
I know, I know, there are loads of threads like this but I must be lacking something in the brains department as I've spent the last 6 days (since I got my orange tytn) reading this forum trying to understand how to unlock the thing without turning it into a brick and then to flash a rom and radio.
Everything I read on here has people contradicting other people and I end up not having a clue what to do in the end.
HEELLLLP!!!
To confuse matters even more I thought I'd got it sussed and then read about roms having/not having a CUBE!!!! WTF???? I then gave up and started typing this thread...
Here's what I think......and PLEASE correct me or agree with me....
Firstly I seem to be stumbling at the first hurdle since I have an orange tytn and that it seems is the worse to have for some reason???
I thought I'd start off simply by using the kaiser simunlocker to unlock the phone (by jocky) but then came across something called hardspl with all its variances, so OK lets go with the flow and dismiss the hardspl step for now assuming I can do it and read on...
Assuming I could ever find a program that makes a backup of the rom I've got I'd carry on with the unlocker until I get to the step (step 10) that says download the original radio..............this of course doesn't exist (1.27.14.32) so I look for a proggy that downloads the radio to use at this point. Here's where I come unstuck again.........no proggy!!
At this point I must assume that this may not be possible on the model I've got if I want to be sure I can make it original again.
Could someone please confirm this so I can accept the fact that I have to use what came with the phone and save myself a few hours a night getting nowhere...
Sorry for my rant but I'm frustrated that my old brain can't figure this out and giving up seems to be the only option. I completely understand that I'll get flamed for this since I'm a noobie and asking again what numerous otheres have asked but I accept that...
I have great respect for all you guys that can actually understand this on first reading and especially the people who produce this stuff....
Thanks again folks
Click to expand...
Click to collapse
Screw what everyone tells you and start with the link above this thread. Actually the second thread on this page. I think I am one of the oldest around here so its not your "old" brain. _Alex_ has gone to great length to get all of the information you need in one place. Start with his sticky. Good luck.
hello, lots of stuff to learn, first thing, which sounds like you did is read, next hard SPL
see the 2nd sticky in the forum,
go down to kaiser wiki, then rom tools wiki, the 3rd choice, hard SPL cid unlock, read carefully and install, once completed, now your phone is ready to flash roms, (for Kaiser) most come with radio or recommend radios to use and not use. if you have problems with hard spl then use the wiki again to troubleshoot and the first 2 stickys
im out
just sell your kaiser and stick to a razor......lol.....j/k....just listen to p1tater...hes right!!
Hey family guy,
A few months back I got an Orange TYTN II just like you. I read for about a week on here untill I felt confident enough in the steps needed to flash a new ROM. First off I Hard SPL and then went for Dutty V3 ROM which was perfect untill I then felt clever enough to flash a new ROM a few weeks later. Due to not sim unlocking correctly the first time around, upon a new radio being flashed to the phone It locked my SIM.. untill I found out the true way to SIM unlock the phone.
Once you have Hard Spl and SIM unlocked you are well away. I know at this point you are probably feeling pretty confused with all this but believe me it is well worth it in the end.
Oh and FYI.... I can confirm that there is an Orange original Rom on here and a few compatible radios should you ever need to revert back to them for some reason as I had to do this myself at one point when trying to work out where I was having issues with something.
All the best
Chris
P.s are we going to start the "who is the oldest contest yet?"
c.b said:
P.s are we going to start the "who is the oldest contest yet?"
Click to expand...
Click to collapse
There's been one around for a while:
http://forum.xda-developers.com/showthread.php?t=325426
but then they do say that memory's the first thing to go, so I'll forgive you!
Confused Stu said:
There's been one around for a while:
http://forum.xda-developers.com/showthread.php?t=325426
but then they do say that memory's the first thing to go, so I'll forgive you!
Click to expand...
Click to collapse
PMSL....That's where it went, I knew I had left it somewhere. Now where are my damn glasses I can't read a thing.
Unlock your Orange Kaiser
Here's my experience ..
1. Basically HardSPL your Tytn II to facilitate a cooked ROM that can be 'sim unlocked'
2. Install the Cooked Rom
3. Run the Sim unlock generator code
4. Phone is *UNLOCKED !*
5. Install a ROM of your choice
6. Install a Radio of your choice
Here's the stuff I used:
READ ALL THE POSTS - READ ALL THE POSTS !!
** USE WINDOWS XP OS with Activesync!! **
1. HTC Kaiser Hard-SPL v1 - CID Unlock & Flash any ROM to your device
You will know you got it right when it says either 1.0.HardSPL or 1.0.OliPof.
NOTE: I had problems here and had to force it with JumpSPL1.93 because HardSPL would not install.
2+3. I used Jockyw2001 Kaiser Sim Unlocker v0.1
NOTE:
> The file has three steps ... 1, 2 & 3 so you can't go wrong:
> Step 1. Installs the 'patched' Radio
> Step 2. Generates the key code for unlocking (on your PC) which you enter into the Tytn.
> Step 3. Installs a replacement radio
4. My code was a series of numbers that I had to type into the screen.
5+6. Read my signature for what I'm using today (it changes)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
All instructions are on screen with prompts.
I sweated for days before I chanced it and it took me about 15 minutes from start to finish but you end up with a pucka HTC looking Tytn II and not the Orange variant.
A few important pointers from the bit I learned:
1. You cannot do this on a WM6.1 Tytn II, you have to go down to WM6.0 - As mine was WM6.0 it didn't matter.
2. Vista is a ***** for doing this and you have enough things to think about without the PC's OS .. USE XP !!
3. HardSPL once done, the Tytn II is clear for all future ROM + Radio upgrades.
4. Bootloader = Power button + Camera button + Reset with stylus
5. Hard reset is Left softkey + Right softkey + Reset with stylus
6. Always Hard reset after blowing any new ROM before using.
7. Backup all your contacts etc. to your SD card with PIM Backup 2.8 before you do anything.
8. Remove the SD card before you begin.
9. The 'Cube' isn't always included in the ROM's - I use this CUBE
10. Most Roms come with their own 'loader' called 'Kaiser_RUU' so you don't have too much to think about.
11. Stick your Radio and ROM information in your signature, you never know when you may want to go back and forget what you had installed ;-)
12. Installing a new radio on a phone that isn't SIM Unlocked will result in a LOCKED TO ALL NETWORKS phone - So SIM Unlock it !!
Enjoy
PS. Let me know if you can't find the files you need.
SIM Unlocker Software HERE
PPS. Before you unlock your Orange can you pop over to this thread and answer Rabdo's question - Thanks.
ajs007 said:
Here's my experience ..
12. Installing a new radio on a phone that isn't SIM Unlocked will result in a LOCKED TO ALL NETWORKS phone - So SIM Unlock it !!
this thread and answer Rabdo's question - Thanks.
Click to expand...
Click to collapse
Hey I have a question about this point - I've never SIM unlocked my phone and have flashed about 6 ROMS, and various radios and never had a problem. All I did was run hardSpl, then started flashing.
So what I'm asking is are you sure of this point?
Mods Please Close
This is a useless thread. Mods please close this thread.
P1Tater said:
Screw what everyone tells you and start with the link above this thread. Actually the second thread on this page. I think I am one of the oldest around here so its not your "old" brain. _Alex_ has gone to great length to get all of the information you need in one place. Start with his sticky. Good luck.
Click to expand...
Click to collapse
Oldest around here your a Matt Serra fan I swore you were like 25.
-McMex
mattarse said:
Hey I have a question about this point - I've never SIM unlocked my phone and have flashed about 6 ROMS, and various radios and never had a problem. All I did was run hardSpl, then started flashing.
So what I'm asking is are you sure of this point?
Click to expand...
Click to collapse
I have heard before that Orange Kaiser's are a little different to other networks and need to be SIM-unlocked before they can use a different network.
Confused Stu said:
I have heard before that Orange Kaiser's are a little different to other networks and need to be SIM-unlocked before they can use a different network.
Click to expand...
Click to collapse
Ok thanks, that would make sense then.
Cheers!
Hi all and thanks for your comments advice and encouragement..........just quickly looking at the old age thread I am one of the oldest at 47!!
The thing about this thread is that it's happened again and there are only 13 posts!!
There's been contradiction about the orange tytn above. Some peeps say it needs to be unlocked (and that they've done it but don't mention what radio they're using), and some peeps say it doesn't need to be unlocked!?!?!?
There is my confusion and my hesitation to do anything in case I lock the sim out completely. That I can't have as I need the phone at all times to get in toch with my kids (humans or small goats depending on what your state of mind is!).
Here is what I think I should do...
1.) Use hardspl to unlock something (not sure what at the mo) so that I am able to flash
2.) Unlock the SIM lock using kaiser sim unlocker (or not! jury is out, but not sure which radio to use so scared of brickifying it)
3.) Flash my choice of rom (but not sure if I have to then flash a radio or if the radio is included in the rom)
That's about all my poor tired OLD.......VERY OLD brains can figure out and there are enough 'I don't knows' there to stop me in my tracks...
I'll keep reading though but in the meantime I could do with gleaning info from someone who is in the UK on orange and maybe has a recent model...
TTFN
familyguy said:
I'll keep reading though but in the meantime I could do with gleaning info from someone who is in the UK on orange and maybe has a recent model...
TTFN
Click to expand...
Click to collapse
I'll be 48 in August, so it's not just the Youngsters who play with the 'phones.
(Does that make me the oldest ?)
I bought the TytnII from the Orange Shop in Leicester just before Christmas but didn't have the bottle to unlock it for months ... Main reason was the unlocking 4 months ago was £20 !! and i didn't want to brick it either.
I spotted someone selling the unlocking service on ebay about a month ago, so I knew someone had cracked it here (and some cheapskate was selling the service.)
Feel free to private message me, if you need to we can talk it through over the phone.
Alan.
familyguy said:
There's been contradiction about the orange tytn above. Some peeps say it needs to be unlocked (and that they've done it but don't mention what radio they're using), and some peeps say it doesn't need to be unlocked!?!?!?
TTFN
Click to expand...
Click to collapse
I may have added to the confusion - I do not have an Orange phone, adn was questioning whether you need to SIM unlock the phone b/c I hadn't. Later it was pointed out that Orange phones may be different and need to be.
mattarse
Greetings to all...........and a damn good weekend to everyone!!
mattarse you simply added to the confusion in my mind............for other it was probably very clear
ajs007, I will PM you and perhaps a quick chat to get me up and running would be great!
One thing I do know though..........when (yes, I've gone from if to when) I get more knowledable about this I'll be one of the first peeps there to help anyone out if I can!
After a long chat with ajs007 (for which I am very grateful) I felt I had the confidence to go ahead and install hardspl using the jumpspl route.
My tale of woe follows as it was unsuccessful every time...
I followed jockys instructions,
1a. download the 5 attached files
1b. connect your PC to phone with a USB cable
2. REMOVE SIM and SD CARDS !!
3. copy JumpSPL1.56-KAIS.exe to your device and run it (make sure the USB cable is still connected). If you still get a white screen then reset your device and now try JumpSPL1.93-KAIS.exe
4. after a few seconds "USB" appears on the phone display
5. unplug and replug the usb cable
6. deselect "Allow USB connections" in Activesync connection settings
7. now flash hardSPL (run KaiserCustomRUU.exe from flash-hardSPL.zip on your PC)
After step 3 (for both 1.56 & 1.93) I get the tri-colour screen (not mentioned above) shortly followed by 'USB' on the white at the bottom (step 4).
(I guess this makes it a quad colour screen instead of
I then did step 5 and step 6 as above and moved on to step 7 to run kaisercustomruu.exe.
I then get a screen which says verifying phone settings and a further screen which has 'current info about your pda phone:' and lists nothing!!
Another line that says 'image version:' and has nothing listed and yet another line that says 'select from below:' and has nothing next to it!?!?!?!?
There is a button that says update the current ROM version but I dare not press it if it is going to update with nothing!!!??
On top of all that I read contradiction again where the instructions above state that you must deselect 'allow usb connections' yet when you run kaisercustomruu.exe it states that you must have an activesync connection....
I'm now really confused and convinced it just isn't to be. Sorry Alan it did sound so easy when you explained it but there must be something different about my phone.........I'm going to throw myself or the phone or both of us off a tall building.............now Im totally depressed
Exit stage left feeling very sorry for oneself...
Looks like everything was A.O.K. for flashing..
IMPORTANT ** You didn't say if you had SPL xxx PoF on the Tri Screen ?
I didn't have any reference to a ROM on the install screen but it worked, probably because the ROM was in the same directory and it didn't need to look anywhere ....
I think (but I'm not 100%) the activesync USB connection is an XP v. Vista thing, and you do need USB connection in XP.
In summary, if you did have SPL xxx PoF on the Tri Screen you should be good to go.
From totally & utterly confused to successfully running Dutty's 6.1!!
Lots of bonus points and many thanks to AJS007 for allowing me to bother him with all my questions and lack of confidence.
Here's my tale...
Firstly I tried to install hardspl running from my PC and a USB cable but I got the infamous white screen!
I then followed the instructions for using jumpspl version 1.53 (for some reason the instructions I read didn't say remove and re-inset battery therefore I didn't do that bit!).
I got to the bit where 'USB' appears on the screen and pulled out the cable then re-inserted it. I have no idea why you do this but I did it. When I pulled the cable out the screen had 'Serial' on it and when I re-inserted it, it went back to 'USB'
I carried on to the next step and unchecked the 'Allow USB Connections' in Activesync (again I have no idea why you do this) and went on to run 'kaisercustomruu.exe'
Here's where I hesitated and got stuck. The program started on the PC and got to a point where it interrogated the phone, shortly after that I was presented with another screen that waited for my input ready to 'Update' but I hesitated since there was no information listed under 'Image Version:' and 'Select from below:'.
I wasn't sure what to do here and cancelled the whole thing in case I bricked it
After further investigation, more reading and speaking once again to my mentor AJS007, I decided to go ahead and throw what caution I had left to the wind, so I pressed the 'Update' button.
After a few more screens I got to the point of no return and gritted my teeth.........nothing happened........I disconnected and re-connected and tried again..........nothing again............after a third time though (and I don't know why) it burst into life and I got the 'percentage screen'.
At this point I did think I had trashed it but plodded on regardless in the hope that I hadn't and everything would be OK. Thankfully it was and on entering the bootloader screen I saw 'olipof'..............all was well
This gave me the extra bit of confidence I needed to go through the unlock procedure and then on to flash Dutty's latest. I did get to the point where I had to enter the unlock code and it took 2 attempts to accept it for some reason........I can't explain that either!!
It was all in all a stressful time and involved a lot of pacing up and down when the ROM was flashing, taking what seemed to be hours to complete and slowing down to an almost stop at certain points, but in the end it did all work and I am now left with a transformed T2, but with the following little problems,
1.) My bluetooth headset has to be paired every time I want to use it!
2.) When I go to re-calibrate the screen (with the cross hair) it freezes up and I have to do a soft reset.
3.) My screen 'tap' noises have disappeared (except when I press the 'start' button)
I haven't tried to reflash the radio to see if that will take care of the bluetooth issue yet but I intend to do so in the next few days.
For anyone that's interested I'm using the radio ROM that was included in Dutty's latest build (WM6.1_5.2.19209) which is 1.58.16.27.
Finally, once again my thanks to AJS007 who went to the trouble of helping me in my few hours of need.
If anyone new here would like to ask me any questions about my noobie experience please don't hold back!!
I just got the Captivate about a month ago. Had a regular phone for about a year, touch screen went out, bought a replacement digitizer but knew it was a temporary fix anyway and wanted a new phone. Convinced the maternal unit to use her contract extension to get me a new phone, and snagged the Captivate for $30 from RadioShack. My first Android phone, and I have to say I'm horribly disappointed, but I guess I'm doing something wrong here.
First two or three weeks, my mom had the phone and got to play around with it for a while. Wasn't until the 29th that I got the phone, and I just played around with it for a week and got all the apps I deemed useful and worthwhile. Eventually realized I couldn't use Flash in the browser, nor Skype, etc., without upgrading to 2.2.
So, I went through the tutorial Samsung provided, watched videos on Youtube just to be sure, but followed everything Samsung's tutorial said word for word. ... only for my phone to end up completely screwed up. Gallery, Browser, Music Player, Video Player, and many other default applications were missing. Now I'm smart enough with technology to think, okay, something's wrong. I knew about the factory reset, so I went to go to settings to do that, and realized. ... oh wait, the Settings menu is also missing. Wonderful. There was no "Settings" button in the Applications list, and if I tried getting to it from the menu button, it simply did nothing at all.
Found Odin, flashed back to 2.1, and then factory reset and got rid of every application I had and etc., so that absolutely nothing was on it, basically a stock phone. Tried upgrading again fresh, still following the instructions very closely. Same problem occurred, and I was pissed. Gave up on 2.2, tried flashing back to 2.1 /again/ with Odin, only for my phone to decide it didn't want to enter download mode anymore. Forced it using 'adb reboot download', but alas, it locked up in the middle of flashing back to 2.1 and wouldn't do anything. I waited about 30 minutes to see if it'd resume the flashing process at all, but nothing, so I regrettably had to disconnect the USB cable and hard brick the phone (wouldn't turn on or anything).
Still under warranty, so I replaced it from RadioShack, and now have a new Captivate. Went ahead and installed all the applications I needed, used the Sideload Wonder Machine to install a few third-party applications, had no problem doing that for a while. Didn't bother attempting to upgrade. However, my computer got a trojan and deleted the MBR. Repaired using the XP boot disc, but it meant I was back on SP2. After installing every last one of the damn updates all over again, I decided to check up on some new applications to install via sideloading.
Hooked up my phone, it detected all the new hardware again since the drivers seemingly were also lost amongst everything else during the repair, only for it to encounter an error on the "Samsung Android Composite ADB Interface". So, I uninstalled the drivers, tried installing them manually. Hooked up the phone, but it still wanted to try to install that one driver and failed. I've restarted my computer, uninstalled the drivers, attempted manually installing them through device manager, you name it. Still can't get it to work -- it keeps having a fatal error every time. However, it's only when my phone has USB Debugging on. Installs every single driver perfectly fine when it's off, in MTP/Mass Storage/Kies mode. Just has a "fatal error" in USB Debugging on that one driver.
tl;dr, the drivers are broken on my computer and I can't fix them despite actually /not/ being computer illiterate. And, I kind of still want 2.2, but apparently the stock 2.2 update is a pain in the rear end and I no longer have a warranty through RadioShack now, so I can't risk bricking my phone due to a faulty update process. Any suggestions?
err, the only thing you should have needed to do was install the latest version of Kies, plugged the phone in, it would have prompted you to do the update. It's quite painless..
Edit: Sorry irrelevant
sw411 said:
err, the only thing you should have needed to do was install the latest version of Kies, plugged the phone in, it would have prompted you to do the update. It's quite painless..
Click to expand...
Click to collapse
At the time I tried, Kies itself didn't support the Captivate. Only Kies mini. And in order to do that upgrade, I had to install the drivers, then put the phone into download mode to install more drivers for some odd reason, restart the phone (taking out the battery and putting it back in), then hook it up. Kies mini wouldn't detect the phone for several tries at first, finally got it about the 10th time in. Then go to the "Upgrade phone" link, and yeah. I followed the instructions from Samsung's official SGH-i897 Froyo upgrade guide.
I did EXACTLY as the instructions say, down to the wire. Still ended up both times with all those applications missing and the settings panel missing, unable to do a factory reset without flashing back to 2.1 first.
Install z4root and root phone
Install rom manager
Flash clockwordmod recovery from rom manager
Choose a 2.2 rom from the forums
Download and copy to SD card
Install via rom manager
????????
Profit
Hope this helps. Btw I reccomend firefly or serendipity for the rom
Sent from my Captivate running CyanogenMod7 using XDA Premium App
brendanmurphy said:
Install z4root and root phone
Install rom manager
Flash clockwordmod recovery from rom manager
Choose a 2.2 rom from the forums
Download and copy to SD card
Install via rom manager
????????
Profit
Hope this helps. Btw I reccomend firefly or serendipity for the rom
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
Only downside to rooting the phone is the voided warranty. I don't entirely know what I'm doing there when it comes to flashing, and if I manage to do something wrong and brick the phone again, I'm completely wiped. I don't have the money to replace the phone at all. I have no job. ._. Only reason I got the phone was because I managed to get some spare money fixing up a friend's computer, and the maternal unit's contract extension was available. I'm not paying for the phone, still my parents. Damn economy in this state is so broken, and I'm screwed over worse since I have no diploma.
However, I was looking into info on the roms, and while I was tempted to try out CM7 for the fact it was 2.3, I actually considered getting Paragon RC6 from what I had read. Just decided not to because I can't replace the phone if I screwed up. In the slim chance I do opt to risk not having a phone at all if I do something wrong, would you say Paragon's worthwhile or would it be better to go with Serendipity? I do like TouchWiz, and Wifi access is a must (200 MB plan isn't going to cover it with how I use data; I'm frequently using Wifi in as many places as is possible), but I'm pretty sure both of those are fine there. Just not really sure which would be better overall, performance-wise.
I can't do either of them right now anyway until I figure out why the drivers aren't installing. So that's my first issue.
Don't worry about bricking I almost guarantee you will brick your phone once. But that is what Odin is for and it's almost impossible to hard brick a phone these days. Just install paragon with the instructions I gave its really fool proof these days to install rom. You will learn by trying if you mess up so be it that's what xda is here for to help.
Drop me a pm anytime if you need help
Sent from my Captivate running CyanogenMod7 using XDA Premium App
brendanmurphy said:
Don't worry about bricking I almost guarantee you will brick your phone once. But that is what Odin is for and it's almost impossible to hard brick a phone these days. Just install paragon with the instructions I gave its really fool proof these days to install rom. You will learn by trying if you mess up so be it that's what xda is here for to help.
Drop me a pm anytime if you need help
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
Well. Despite it being almost impossible, I've managed it once already within the first month of having one. Kind of why I'm a bit skittish about actually going through with it. I'm definitely all about modding and customizing things to your liking, but not having the funds to fall back on if I /do/ screw up bigtime again, yeeeeah.
After looking at Firefly and Serendipity thoroughly, though, I'm impressed. It's a tough choice between the three (Paragon, Serendipity, and Firefly). I'm leaning towards Serendipity now though after watching a video just to see the interface. Kinda not a huge fan of the GB launcher -- I liked the side-scrolling app launcher more, honestly -- but that's not a big deal.
So, let's see if I've got the details down right before I try anything. Search z4root in Market, install. Subsequently get Rom Manager, install it. Flash ClockworkMod (via Rom Manager). Pick a 2.2 rom (which will be a tough choice), and download it to my microSD card to put in the phone. Install said rom (via Rom Manager). And then, voila, it's done.
Did I miss anything, or am I actually following instructions right here?
Edit: Nope, can't find z4root in the Market anyways. Means I'd have to Sideload it, and until I get this driver issue solved, that's not gonna work either. That's gonna be the first thing necessary to fix since it also means I can't use Odin if I do anything wrong... Downloading Serendipity now though, so if I can get that fixed, I may go ahead and try this out after I get some sleep. But since I'm nocturnal, time for some rest. Hoping for some tips or pointers when I get back on. Definitely looking forward to good experiences with XDA and my Android phone.
Yea those are the exact steps its really simple. http://forum.xda-developers.com/showthread.php?t=944418 try this it will install drivers for you ans sideload apps. This is a useful tool
Sent from my Captivate running CyanogenMod7 using XDA Premium App
The.Se7enth said:
Only downside to rooting the phone is the voided warranty.
Click to expand...
Click to collapse
Quick question. Did you purchase the insurance through AT&T for the phone? If so, you will most likely always be able to get it replaced even if it's been rooted. It's just as simple as calling the help line, and saying that you have no idea what happened, and it won't work now. Of course that is worst case scenario
From my experience, the Captivate is a pretty difficult phone to hard brick compared to some others. For a beginner, all of this can be somewhat overwhelming, we've all been there. But once you get the hang of the whole process, you'll be good to go!
Yeah I've done that once already. Just called in and told them that it seems like a software problem and they replaced it no charge.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Beginner help....
AT&T warranty is for 1 year on new phones, 90 days on phones you purchase as refurbished. (30 day "I just don't like THIS phone" replacement/return in both cases.) If Radio Shack will not replace the phone, AT&T should swap. If neither is willing to help, Samsung will honor their 1 year warranty, but it requires shipping back to Samsung.
Your situation sounds like your Windows PC is the problem. A complete reinstall of Windows & apps (not just a quick MBR repair / install over top of existing stuff) may be your best bet if you can't use a different machine.
Kies Mini should upgrade your phone to 2.2 painlessly - without you having to do anything but plug it in and click the on screen button.
Also if you root and need to return it just flash back to stock which will take away root and at$t is none the wiser, most likely
peypey008 said:
Quick question. Did you purchase the insurance through AT&T for the phone? If so, you will most likely always be able to get it replaced even if it's been rooted. It's just as simple as calling the help line, and saying that you have no idea what happened, and it won't work now. Of course that is worst case scenario
From my experience, the Captivate is a pretty difficult phone to hard brick compared to some others. For a beginner, all of this can be somewhat overwhelming, we've all been there. But once you get the hang of the whole process, you'll be good to go!
Click to expand...
Click to collapse
Nope. Don't feel their insurance policies are worth it. You spend more money on the insurance policy in total, even if it's month-to-month, than you would on a brand new contractless phone. Besides, I had only made $120 from fixing up three ancient computers (so ancient they actually had ISA slots and DIMM SD-RAM memory -- one was even a Pentium II), and only had $50 by the time I bought the phone which was a couple months later. My $50 went towards the phone and a pack of screen protectors, while my mom covered the upgrade fee. Couldn't afford the insurance policy even if we wanted to.
But I do greatly appreciate the encouragement. I'll give it a go in a bit, and try out flashing Serendipity. I'll follow the official instructions from their own website though, because I read this on their FAQ:
"Never use ROM Manager. EVER, EVER, EVER, EVER, EVER!"
pouelle said:
AT&T warranty is for 1 year on new phones, 90 days on phones you purchase as refurbished. (30 day "I just don't like THIS phone" replacement/return in both cases.) If Radio Shack will not replace the phone, AT&T should swap. If neither is willing to help, Samsung will honor their 1 year warranty, but it requires shipping back to Samsung.
Your situation sounds like your Windows PC is the problem. A complete reinstall of Windows & apps (not just a quick MBR repair / install over top of existing stuff) may be your best bet if you can't use a different machine.
Kies Mini should upgrade your phone to 2.2 painlessly - without you having to do anything but plug it in and click the on screen button.
Click to expand...
Click to collapse
RadioShack replaced the phone the first time, but the manager there said after replacing it once, the warranty was thus void. I'm not sure if profanity is allowed here, but you can figure out which word I wanted to reply to him. It's eight letters long, starts with bull.
I've read posts on AT&T forums saying if the phone's bricked or can't be repaired by user methods though, especially if it's rooted, that they won't honor the warranty at all and will consider it user error and that you're out of luck. Even people who tried to upgrade to 2.2 stock had issues with that. But I dunno.
Anyways, my machine works perfectly for everything else. Before the repair, when I tried to upgrade? It was a fresh install. I had just reformatted it because it was performing sluggish before and I decided I wanted a single-boot installation instead of having my old dual-boot of Windows 7 and XP. It's now just XP for the time being, seeing as how the hardware's limited and I want to get the best out of it for gaming (I can run 7 with ease, but it uses more resources than XP, thus games don't run as well).
I realize earlier I may have come off as implying the upgrade to 2.2 process was difficult. I don't mean it was "difficult" by any means necessary. It was simply a plug the phone in, let all the drivers install, unhook and put in download mode, hook up again for more drivers. Restart phone, start up kies, hook up phone, and click "Upgrade phone" button. Accept the terms of service or whatever, and wait. Upgrade starts, phone flips into download mode on it's own, restarts a couple times, and voila, you're on 2.2. I thought it was a piece of cake. My issue is that regardless of how easy it was, it still ended up rather broken because all those applications were missing, on top of the fact the Settings panel was also gone, leaving me unable to perform a factory reset.
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?
The.Se7enth said:
At the time I tried, Kies itself didn't support the Captivate. Only Kies mini. And in order to do that upgrade, I had to install the drivers, then put the phone into download mode to install more drivers for some odd reason, restart the phone (taking out the battery and putting it back in), then hook it up. Kies mini wouldn't detect the phone for several tries at first, finally got it about the 10th time in. Then go to the "Upgrade phone" link, and yeah. I followed the instructions from Samsung's official SGH-i897 Froyo upgrade guide.
I did EXACTLY as the instructions say, down to the wire. Still ended up both times with all those applications missing and the settings panel missing, unable to do a factory reset without flashing back to 2.1 first.
Click to expand...
Click to collapse
Fail, Kies Mini works from Kies mode on the phone. It puts the phone into download mode when you start the upgrade from Kies Mini.
Just saying...
The.Se7enth said:
Nope. Don't feel their insurance policies are worth it. You spend more money on the insurance policy in total, even if it's month-to-month, than you would on a brand new contractless phone. Besides, I had only made $120 from fixing up three ancient computers (so ancient they actually had ISA slots and DIMM SD-RAM memory -- one was even a Pentium II), and only had $50 by the time I bought the phone which was a couple months later. My $50 went towards the phone and a pack of screen protectors, while my mom covered the upgrade fee. Couldn't afford the insurance policy even if we wanted to.
But I do greatly appreciate the encouragement. I'll give it a go in a bit, and try out flashing Serendipity. I'll follow the official instructions from their own website though, because I read this on their FAQ:
"Never use ROM Manager. EVER, EVER, EVER, EVER, EVER!"
RadioShack replaced the phone the first time, but the manager there said after replacing it once, the warranty was thus void. I'm not sure if profanity is allowed here, but you can figure out which word I wanted to reply to him. It's eight letters long, starts with bull.
I've read posts on AT&T forums saying if the phone's bricked or can't be repaired by user methods though, especially if it's rooted, that they won't honor the warranty at all and will consider it user error and that you're out of luck. Even people who tried to upgrade to 2.2 stock had issues with that. But I dunno.
Anyways, my machine works perfectly for everything else. Before the repair, when I tried to upgrade? It was a fresh install. I had just reformatted it because it was performing sluggish before and I decided I wanted a single-boot installation instead of having my old dual-boot of Windows 7 and XP. It's now just XP for the time being, seeing as how the hardware's limited and I want to get the best out of it for gaming (I can run 7 with ease, but it uses more resources than XP, thus games don't run as well).
I realize earlier I may have come off as implying the upgrade to 2.2 process was difficult. I don't mean it was "difficult" by any means necessary. It was simply a plug the phone in, let all the drivers install, unhook and put in download mode, hook up again for more drivers. Restart phone, start up kies, hook up phone, and click "Upgrade phone" button. Accept the terms of service or whatever, and wait. Upgrade starts, phone flips into download mode on it's own, restarts a couple times, and voila, you're on 2.2. I thought it was a piece of cake. My issue is that regardless of how easy it was, it still ended up rather broken because all those applications were missing, on top of the fact the Settings panel was also gone, leaving me unable to perform a factory reset.
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?
Click to expand...
Click to collapse
Yea once you have serendipity installed don't use rom manager but for initial install your fine
Sent from my Captivate running CyanogenMod7 using XDA Premium App
cappysw10 said:
Fail, Kies Mini works from Kies mode on the phone. It puts the phone into download mode when you start the upgrade from Kies Mini.
Just saying...
Click to expand...
Click to collapse
You can "say" all you want, my good sir, but google the instructions. They tell you clearly to put the phone into download mode TO FINISH INSTALLING DRIVERS. You don't start up Kies mini until after all the drivers are installed, at which point you hook up the phone with USB Debugging, not Kies mode. I appreciate your willingness to help, but be sure to read everything I say before you correct me. I'm not that slow. I read instructions thoroughly and I've read quite a lot of posts on these forums. I work with computers regularly -- just not Android. The issue had nothing to do with that anyway, so that doesn't even matter.
brendanmurphy said:
Yea once you have serendipity installed don't use rom manager but for initial install your fine
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
I'm sure it's possible, and I don't mean to come off disrespectful, but I'm just gonna go with the instructions on their website. Just seems a safer route to install a ROM by the creator's instructions, you know? Only thing I'm not sure about is what they mean by "Flash it in 2e recovery (twice)." on ClockworkMod.
The.Se7enth said:
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?
Click to expand...
Click to collapse
These two are still my top questions now. Is it a good idea to have the SIM card out during the upgrade process, and not put it back in until after the update is 100% complete?
Also, I'm really frustrated about this whole driver thing. I know the drivers aren't broken because I used them on this very computer before, and the repair shouldn't have damaged anything because absolutely everything else is working flawlessly. But every time I've uninstalled the drivers completely, and hook up the phone, it keeps getting a fatal error on that. Apparently "S3C6410 Android ADB" is the name of the device that can't install drivers.
Hello, thank you for reading this, to start with.
First off, here are the specs of the phone I am asking about:
Galaxy S 4G exclusive from T-mobile
Model #: SGH-T959V
Firmware: 2.2.1
Kernel:2.6.32.9
Build #: FROYO.VUVKD1
If that's not enough please ask.
Back Story: Phone was given to my ex by his mother. It was for T-mobile, which don't have good plans for pre-paid/pay as you go in my area. So I was asked to make it work for ATT. I rooted using Superoneclick, and then did the hex voodoo and unlocked the phone. It worked for a few months, no problem. There was no data plan so no phone internet was acessed, wifi was but only rarely. It DID work.
Then, the other day, my ex dropped it. It worked just fine for a minute or two, but now is stuck with no service, and such. No imei number. No phone number. Nothing. Searches for the provider. Sim card has been replaced just in case. I've restored and re-rooted, but i couldn't re-unlock the sim # as the hex editor couldn't find the code. AND the sim doesn't ask for an unlock code when inserted.
I have googled and searched my tushie off to figure this out. All my answers are bad flashing of roms and such, and the last anything that was done to it out of ordinary use was me unlocking it, and it worked for months.
Keep in mind that i haven't a clue what flashing a rom means, or what odin is (i read that several times, haven't a clue what it is), and I know how to follow step by step instructions as long as they use reasonably understandable terms to the android nooblett.
I am currently running on an ubuntu laptop, so downloading and running anything means I download, put it on a flash drive, and install it or run it on a windows computer that doesn't have internet access (long story, i'm rambling as it is).
Some extras:
I did not do any backups, because everything worked for the longest time anyways.
I've tried a few things involving nv_data.bin and the like, but it seems they don't exist or are hidden from my silly self.
I have to re-root and such as I've just performed a factory reset to see if that would fix the issue.
I am extremely tired so I'll likely do nothing tonight, including responding, as I have to work tomorrow and lots of other things.
I am a rambling idiot, feel free to mock me for it, but i do try and give out as much information as I can.
Any questions? If not, please, please, please tell me an answer that doesn't involve sending this phone back, because it's long out of warranty and has passed through many hands (the previous people did not like t-mobile either...).
And thank you for reading the ramblings of this idiot.
Are you sure it's not a hardware issue? I dropped my old iPhone 3G and it stopped recognizing my SIM unless it was placed just right. Have you tried any other SIM cards in there? Take a look at my SGS4G carrier unlocker (link is in my signature) and see if it scans through your nv_data.bin file correctly. I never liked that people encourage direct editing of that file. :/
Have you tried seeing if Samsung Kies mini will recognize your phone? Since you still seem to be on factory stock and did a factory reset.... download Kies mini, plug your phone in and see if it will recognize it. Kies mini - in case you are unaware is Samsung's software to update our phone.
If it recognizes your phone - try to do the upgrade to Gingerbread. If it will upgrade to Gingerbread, it might rewrite your efs folder - which is where the IMEI and phone information is stored. If it doesn't rewrite the efs folder... it shouldn't matter if your phone is out of warranty as Kies mini - you will say and not mention the other stuff you have done - messed it up during the upgrade... which is happening to people more than you would think. Take it back to where you purchased the phone and give it a shot. Or try contacting Samsung. Many have done that as well. You need a computer you can download Kies mini to and do the upgrade... in other words - a computer with internet access you can work on.
o You may start with another Factory Reset
o Download Kies mini if you do not already have it. < - - Click link here for Kies mini - When you follow this link you will see two tabs - 'Manuals' and 'Software' - click software and download.
o Make sure your phone is charged.
o Make sure USB Debugging is off.
o Start Kies mini on the computer.
o Make sure phone is not connected to computer yet.
o In USB Settings on phone select ‘Kies (Firmware update)’ if it is not set to ask every time.
o Plugged in phone, let device drivers install on computer. You will see a notification on your computer when complete.
o Then Kies mini will recognize the phone.
o Hit upgrade and wait.
o Phone will eventually reboot. Check your IMEI.
---------- Post added at 05:32 AM ---------- Previous post was at 05:26 AM ----------
FBis251 said:
I dropped my old iPhone 3G and it stopped recognizing my SIM unless it was placed just right. Have you tried any other SIM cards in there?
Click to expand...
Click to collapse
You owned an iPhone FB? Damn!
FB is one of the best on here... however, if you are on stock you should try an upgrade if Kies mini will recognize your phone. I have read flashing stock - in this instance via Kies mini - has many times rewritten the efs folder for people with IMEI problems. Either way - if he is on stock everything he can take it in to T-Mobile and ask for you?
Thoughts on that FB?
lumin30 said:
You owned an iPhone FB? Damn!
FB is one of the best on here... however, if you are on stock you should try an upgrade if Kies mini will recognize your phone. I have read flashing stock - in this instance via Kies mini - has many times rewritten the efs folder for people with IMEI problems. Either way - if he is on stock everything he can take it in to T-Mobile and ask for you?
Thoughts on that FB?
Click to expand...
Click to collapse
I still have it lying around and it's bricked. I wanna try flashing it again with another USB cable but I can't find my spare.
Hmm, haven't ever tried the kies mini approach but it's worth a shot, especially if it'll restore the /efs directory.
If it IS fully stock, then yes take it in to T-Mob and see if they'll give you a replacement and next time don't go editing anything in /efs directly.
Thank you everyone. I will try these things later today. Like I said the only things I've personally done to it are root and unlock. I dunno what happened and its possible it could be hardware, but ill try updating it through kies first. Again thank you, ill keep you updated on what happens.
RamblingIdiot said:
Thank you everyone. I will try these things later today. Like I said the only things I've personally done to it are root and unlock. I dunno what happened and its possible it could be hardware, but ill try updating it through kies first. Again thank you, ill keep you updated on what happens.
Click to expand...
Click to collapse
Hi,
If the problem is solved for you please edit the title in the OP and add [SOLVED] to it
10x
Ok Guys/Gals, I'm stumped...
Followed the instructions. Mini Kies on computer that works with it (windows vista 32 bit), waited til kies told me to plug in the device. I did. Drivers installed. I waited. And waited. And waited. And waited a bit more. Then it pops up for me to enter a pattern. No pattern had been established with that phone before. So I set one up on the phone, and redid all that, thinking that's all I had to do. Asked me for the pattern again, I put it in.
Here are the steps i'm taking.
Mini kies asks me to plug in my phone.
I do it (this is the phone in the thread, not my actual phone).
And I wait. A while, actually. Somewhere in the line of 1-5 minutes.
And now i get a little popup. "Pattern" the header reads. "The mobile phone is locked. To connect, use the mouse to enter the pattern as specified by the mobile phone." Followed by the pattern unlocker.
I place the pattern i created on the phone in to the one on the computer. It must not be right (as there was none to begin with, and i had to create new and redo this whole step) because now it reads:
Firmware version: device cannot be upgraded
Firmware upgrade: (this is a blank nothingness)
Agh, don't get me wrong, i love this stuff, but after dealing with a defaulty U-scan computer all day (i am a cashier...), computers are not on my good list.
Please help ?
Ok, so after hours of crying, moaning, cursing, yelling at the phone, cursing SD cards for being so small, cursing the better phone for being more retarded than it's cheapo brother the Prevail, I fixed it.
I was so frustrated, i reset everything, again. Still wouldn't work with kies. Checked everything. Made sure I was doing everything right. Googled every last letter i could find about my issue.
I wanted to throw the phone, but instead, i took the battery out, the sim card out, and the SD card out, and cursed each and every one of them out. Before I continue, let me say, that I'd done this before, for approximately the same time, if not longer. Then, i threatened their inanimate lives and put them back, and tried to do the kies update. Turned on the phone, not expecting any miracle of any sort. Suddenly the phone's alive with all sorts of missed calls and texts and who knows what else. So while the phone is no longer rooted, it's still unlocked, and works like a dream again.
TL;DR version? Took the battery, sim, and SD card out for a while. Even though I'd done this as the first thing i did when this issue started happening, perhaps yelling at them made the difference.
Thank you all for putting up with me and my rambling idiocy.
Awesome, glad you got it working again. Maybe we need to put "threatening sdcard/SIM card" methods into the wiki...
stephen_w said:
Awesome, glad you got it working again. Maybe we need to put "threatening sdcard/SIM card" methods into the wiki...
Click to expand...
Click to collapse
Stephen
I threaten my phone with a trip to the recycling yard all the time. It works.
And to the OP glad you got it figured out. A few people with the imie issue have used the pull battery wait ten approach and it seems to work.
Glad you fixed it.
I strongly suggest you make a copy of your efs folder in case you have an IMEI issue again. I keep a copy of my efs folder on my external sdcard and my PC.
This started happening last night. Can't figure out how to fix it, and I really don't want to have to hard-reset my phone :crying:
Here's whats happened so far...
1. Metrotube wouldn't launch (insta-crashed) even after a reboot... so i uninstalled the app.
2. When i attempted to re-install metrotube, it went into the queue, but is stuck on "pending"
3. Attempting to cancel or retry the download = nothing happens
4. Feeds in the People hub refuse to update. Instantly fails with an error.
5. messenger refuses to sign in.
6. "Me" tile is stuck on "3 new items" even though Ive already read everything in there.
7. Attempting to install any other app from the marketplace = error message.
8. Rebooting the phone multiple times has done nothing to help the problems above.
What happened, and how do I fix it? Since when does WP7 randomly just fubar itself?
Still having this issue guys. Any help?
Try pulling the battery if you can for 60 seconds and then try. Otherwise, given what your phone is doing, all I can think of is a hard reset as it sounds messed up.
P.S. If you have a recent backup try using Zune to restore to that.
Device? ROM? Version?
Sent from my HD7 using Board Express
pvt_nemesis said:
Device? ROM? Version?
Sent from my HD7 using Board Express
Click to expand...
Click to collapse
Nokia Lumia 900, OS version 7.10.8779.8
Finally went ahead and hard-reset the phone. Everything is working again...going to take ages to get my handset set back up the way I like it again.
What happened and how do I keep it from happening again!?
Tell us everything you did in the past 3 weeks, and we can say what happened after that.
mcosmin222 said:
Tell us everything you did in the past 3 weeks, and we can say what happened after that.
Click to expand...
Click to collapse
Can you narrow that down slightly? I'll gladly list everything I can, but "everything" is a bit broad.
Does the list I gave in the first post give you any clues? Seems weird that the entire OS would just screw up like that, when it was working fine just minutes before hand...
It sounds to me like a potential hardware failure, either in the NAND Flash itself or in the SD card storage (for phones which use that instead of soldered-in storage). That's just a first guess, though.
As for things to tell us about, were you messing with any high-privilege apps? Either apps that use privilege elevation hacks, like WP7 Root Tools or things like Windowbreak for Samsung, or apps which you marked as "Trusted' in Root Tools?
Leapo said:
Can you narrow that down slightly? I'll gladly list everything I can, but "everything" is a bit broad.
Does the list I gave in the first post give you any clues? Seems weird that the entire OS would just screw up like that, when it was working fine just minutes before hand...
Click to expand...
Click to collapse
Well not quite everything. We don't need to know whom you're texting or stuff like that. Nice info would be if you tried rooting, sideloading some unknown app, attempting to charge without your battery, stuff like those...or if you tried some high privileges stuff, like the guy above me asked.
GoodDayToDie said:
As for things to tell us about, were you messing with any high-privilege apps? Either apps that use privilege elevation hacks, like WP7 Root Tools or things like Windowbreak for Samsung, or apps which you marked as "Trusted' in Root Tools?
Click to expand...
Click to collapse
mcosmin222 said:
Nice info would be if you tried rooting, sideloading some unknown app, attempting to charge without your battery, stuff like those...or if you tried some high privileges stuff, like the guy above me asked.
Click to expand...
Click to collapse
Like I said earlier, this is a Lumia 900. This phone can't be rooted by any known method, and mine wasn't even developer unlocked.
No high-privileges, no root tools, nothing. Totally stock and unmodified with only marketplace apps. It just decided to screw up one day and the only way to fix it was a hard reset...
Also can't charge a Lumia 900 without the battery, because it's sealed inside.
Hi guys, I'm having a problem rooting an HTC Aria that I recently acquired, and I'm not sure how to search for my answer. I guess Ill try to explain what happen as best as I know, since some things happened so fast I have no idea exactly what happened. Its also worth mentioning that I have no experience rooting android phones, but I'm not an idiot, so please don't be afraid to help because you think Im gonna be waste of your time.
I used the tool unRevoked with Reflash to inflict the damage. Things seemed to be going great, in fact at one point it even said this was a triumph. Somewhere towards the very end, it looked as if it complained about not finding a file on the sd. It was so fast I couldn't read it because I was looking at the computer at that time. Im not surprised it didn't find the file it was looking for since I had no sd card installed. The tutorial/procedure that I read was very detailed, so detailed that he sometimes took a minute to make sure the reader knew to double click the file to open it, yet there was no mention of absolutely needing an sd card for it to work.
Now when I re-run reflash, when I get to the point where you have to choose HBoot USB, it wont ever let me pick it. It just forces me to pick Fastboot or one of the other ones, spits out several lines of green text that is way too fast to read, then gives you the option to pick HBoot again. It never leaves this menu now, not by way of reflash anyway. I can still unplug and reboot my phone , and operate it like normal, but reflash wont go past that recovery menu. I did a factory reset, that didn't help. I also picked recovery on that menu. I browsed the options, but Im afraid to make another move at this point without some input. If someone could please maybe tell me what happened and how to proceed I would be very grateful.
Thank you