Related
Hey everyone, I'm quite the lurker on these forums and don't post very often at all. I just want to first and foremost say that everyone here has been amazing and the work that has gone on for this phone is truly astonishing.
Now, with that being said... I'm bricked.
I was running CM7 today and decided (don't ask why) to try that ICS for the i9003. Dumb move. Hopefully someone is getting a laugh out of this as well.
I expected the results to be bad, but not disastrous. In the process of trying to do this I bricked the phone. When I had the ICS ROM on it, it got stuck on the AT&T screen. No worries, I made a back up this morning... I figured just pop back into recovery and restore myself back to normal and everything's fine.
Well, here's where it gets bad. I cannot get into recovery. After multiple attempts of trying to get into recovery. ADB nor Odin even see my phone in download mode. I do have a USB JTAG jig, which has saved me quite a few times.
I started downloading stock ROM's like crazy today. The only one that I could get to install was stock 2.3.5 with Boog's kernel with CWM. I booted into the OS and all seemed well at the time... except there's no modem! I have no internet, service, or anything. This is the only time ADB can see my phone, is when it's booted up. As soon as it's in download mode, ADB can no longer see my phone. The same with ODIN.
ODIN sees my phone when it's booted up, but doesn't actually make the handshake for an install of another version. I've tried to root it, in hopes of being able to push ROM Manager, Super User, and restore my back up in CWM. This didn't work either. During the rooting, using a one-click, it hangs up trying to run the psneuter exploit.
If I'm booted into this 2.3.5 stock of android with no modem, I tried to reboot into recovery using ADB running reboot recovery. This just boots the phone back into Android as if there's no recovery on the device at all.
Soon as I'm back in download mode I cannot push any files with ODIN or ADB. Neither one of them see my device at this point. Even using the JTAG jig.
This is where I'm now at. I'm not sure what else to try at this point. Is there a reason that my device is no longer being recognized in ADB when in download mode?
Any insight would be greatly appreciated. I've been trying to scour forums and search engines with no luck so far. This is my only phone, so it's a little depressing to be without any means of communication on the go, but that's the chance you take...right?
p.s. I do have all the Samsung USB drivers as I normally push files with ADB and have just done so earlier this week. Had the same luck on my computer at work today. So, I know it's not a PC related issue.
Thank you to everyone in advance.
I've also tried to push a modem to the phone with no luck.
I installed 2.3.5 with the Executable JAR of Heimdall AndroidOS 2.3.5 to push the files and that JAR version is the only device that will install to my phone and makes the handshake. Just no modem
You may want to give Heimdall a try - it installs its own USB drivers, so it's possible it might be able to see your phone that way. Nevermind - just saw your post. Which Heimdall did you grab?
Also try switching USB ports - sometimes a different port makes a difference.
There's a one-click in my signature if you need it.
I believe it was the one in your signature to be honest. Which is the only one that recognizes my phone in download mode.
I get it to boot to Android, but that's where I'm stuck. Can't get into CWM from that stock ROM. I'm assuming it would have to be rooted to even use CWM, and I was unable to one-click root it.
edit: Just to be sure I did try the one in your sig. It installs no problem, but ROM manager crashes and the screen distorts right before home screen loads. Once it's loaded it seems OK. Might be a boot loader issue.. but not sure. Once in download moad Odin3 doesn't recognize the device. The one click app does, but not Odin3 v. 1.3 to flash rooted kernel. It just doesn't recognize the device for some reason, but java installer still recognizes it.
I cannot get into CWM as it just crashes. Doesn't reinstall correctly, gets stuck on running privileged commands. Cannot boot into it since it's a privileged command as well. Only version of odin that recognizes my phone is the one in your link and it's a JAR Exe lol. This is the strange part.. no modem. Just got the wifi to work to at least make it to the market place. Still no modem, broadband is 'unknown'.
When I go back into download mode to flash a kernel in Odin v1.3 it doesn't recognize my device. ADB does not recognize my device. The java installer for the stock rom I just used in your sig still recognizes the device. Only the java installer recognizes it. Tried using Heimdall 1.1 for the kernel flash and it also does not recognize my phone.
I do have an HP TouchPad running CM7 alpha 2.1 as well. Not sure if this will help, unless someone can think of something clever by having an extra Android device. Just throwing it out there.
sunfirex said:
I believe it was the one in your signature to be honest. Which is the only one that recognizes my phone in download mode.
I get it to boot to Android, but that's where I'm stuck. Can't get into CWM from that stock ROM. I'm assuming it would have to be rooted to even use CWM, and I was unable to one-click root it.
Click to expand...
Click to collapse
As far as I know, that should have CWM installed in the file. Depending on which bootloaders you have, either holding V+ and Power from a powered-off state, or V+/V-/Power should put you straight into CWM.
If that isn't working for you, but you're at least on a Gingerbread rom, try this. It appears Heimdall is ok with your phone, and this kernel I'm certain has CWM baked in. You might bootloop, but you should definitely get to CWM from this.
That's exactly what it was. That version of Heimdall in the link you provided solved my issue.
Thank you so much!
Glad to hear it.
Hello everyone, before I start, I want to let everyone know I have searched endlessly for a fix, etc.
I have a SideKick 4G that I purchased maybe a month ago, and yesterday I went ahead and tried to flash a custom ROM on it. Now my issue is, I was hap-hazardly strolling through the menus and doing the procedure so I didn't back anything up or check the mounts etc.
My issue is, I have Odin and the sk4g.pit file, but I can't find the KD1OdinSTOCK.tar or KG2OdinSTOCK.tar files, because the file hosts are down... permanently.
I also do not know if I have the KD1 or KG2 firmware, what the difference is, and if any problems could be caused by flashing one or the other onto my device. I'm pretty new to the whole process and I was only looking to make my phone faster and less clunky.
If I get the files, a quick walk-through for my specific situation would be very highly appreciated.
Thanks in advance!
EDIT: I found a newer firmware for the SideKick 4G, called KH1, Not KD1, KG2, or KJ1.
To get the file:
1) Go to SamFirmWare.com and make an account
2) Search T839UVKH1
3) Make sure you find the firmware for this model. "SGH-T839"
4) Download it
5) Make sure to look for what password you'll need to open the file (This one is marked with "##")
6) Input password when extracting the file to wherever you want to put it (The password for this one is samfirmware.com)
That should be it.
My issue now is that Odin isn't recognizing my device. It's in download mode and I have the factory cable but I must be doing something wrong as I can set the PIT file and the PDA file, tick boxes etc. but I can not for the life of me get my device detected.
Alright, later update.
I got Odin to recognize my phone, and now I'm trying to flash it.
I don't seem to be having any negative impact with my firmware (KH1) and sk4g.pit, however it always fails at write boot.sbl OR, it gets stuck at Set PIT file.
My phone changed from the Downloading... mode to the Phone - ! - PC picture, however, I was told I can still flash from this mode. I've been continuing to flash with different settings in hopes of reaching recovery, and so far what has NOT worked:
Auto Reboot
Auto Reboot + Re-Partition
Auto Reboot + Re-Partition + F. Reset Time
I don't believe I've tried Auto Reboot + F. Reset Time without Re-Partition, or Re-Partition with F. Reset Time.
Any advice or comments?
Update #2.
http://forum.xda-developers.com/showthread.php?t=1350060&page=6
This thread seems to have a link to a oneclick stock recovery as well as KG2 firmware, judging by the 254 MB download (THAT WORKS BY THE WAY.)
Hopefully after I download this, I can get the phone running. Will post later to inform a yay or nay.
Edit: I almost successfully flashed to stock KG2 Firmware. All went well (Kernal, Recovery, etc) Except it failed at the modem.
It rebooted after failing modem and now I'm stuck at sidekick boot logo. It's better than having Phone - ! - PC though.
EDIT 2: Seems that it keeps failing at Modem, part 3 of 6. along with that, it does restore the phone to Download mode rather then the broken sync picture. Odin now does not recognize the phone, but I think that's due to the other drivers the oneclick method prompted me to install. I'm going to try to disable those drivers temporarily and see what odin thinks about it.
Update #3.
I discovered the drivers downloaded to run the oneclick as provided by the link in the previous update did infact block connection to odin with the same device.
Uninstalling the driver got the connection going again. Every time in Odin, I fail at writing either boot.sbl or cache.rfs.
I took the files from the KG2 firmware and compiled my own .tar out of them and when I flashed using my compiled tar, that's when I got the cache.rfs write error. Phone has shown no signs of improving or deteriorating. I can go back to oneclick recovery and get the phone out of broken sync picture mode, and back into Download mode. However, here are my 2 issues flashing.
In Odin:
I either have no connection, or
I can't write boot.sbl or cache.rfs and fail.
In Heimdall One-Click KG2:
I need the driver Odin doesn't like, and
I flash almost all the way through, but fail halfway through uploading MODEM.bin.
It's giving me the opportunity to flash Boot Loaders along with KG2 kernal, recovery, modem, etc. It's the only thing I haven't tried yet.
Update #4.
I'm about to flash bootloaders. Wish me luck
EDIT: I'm about to cry :') I THINK IT WORKED. I'm loading boot screen.. got animation and now got samsung screen, waiting for the phone to boot. got a fully successful oneclick and it's looking well at the moment
YEAH!!!!!!!!!!!!!!!!!!!! HOME SCREEN!!!!!
Nice monologue.
Thank you sir. What do you think of the things I did to get my phone working again? Anything you think I shouldn't have done? o_o''
I got in a SK4g for my wife intent on upgrading her current phone. I own a 4g myself, and have Rooted/ROM'd it with no issues, we we thought it best to get her the same phone for ease of use/manipulation.
I got the phone in and used superoneclick to root it, then went through the process of putting CWM in place and installing GenericGinger_2.0_SK4G. The process ran smooth as glass (as expected) until it got to reboot. On reboot it hung up on the sidekick screen. After about an hour of waiting I pulled the battery and restarted the machine.
It came back up in recovery mode with the stock recovery (blue) text. Since then I haven't been able to get it to do anything but restart into that recovery screen. Odin doesn't see the phone in download mode and t839-Sidekick4G-UVKG2-One-Click does nothing. It shows it uploading, reboots the phone, and I'm back at the blue text. flashing the bootloaders with One-Click shows success on everything *except* uploading the bootloaders. If I tell it to re-install packages I get a 'cannot validate signature' response. I've tried using android commander to push CWM's recovery file to the phone and get 'permission' denied.
I've done a lot of searching on this site, trying most suggested fixes I've come across with no luck.
what can be done with this phone to get it back in operating condition?
Thanks in advance!
try installing kies odin wouldnt see my phone until i installed it
Kies installed and Odin saw the phone. excellent, thanks!
now, the next issue... lol
I used Odin to push KD1OdinSTOCK onto the phone. it's doing more than it was (going to the initial sidekick screen then dumping to recovery). Now it'll load through the sidekick and samsung splash screens, then reset and do it again. The same thing happens when I tried StockKG2ODIN. I'm using the sk4g.pit that I pulled from this site, could that have anything to do with it/is there another one around that I could try? Anybody have thoughts or ideas on what to do next? I've tried using t839-Sidekick4G-UVKG2-One-Click again, but it nuked the drivers kies put into place and dropped the phone back to what it was doing before.
okay, I did some light reading of this thread here
and followed the directions closely. I also went through sduvick's list of things to do with the following results:
Black screen, no logo.
1. Get into download mode by using VolDown+Touchpad+Power
2. flash full sk4g.tar.md5 as posted.
device will boot through the logo and splash screens, then repeat. note: if I leave the USB cable plugged in on reboot it will go to the battery screen, otherwise it just boot loops.
_________________________________
logo only
1. Download mode
2. Flash full package
device boot loops
_________________________________
Can't flash recovery/boot/sbl
1. Download mode
2. use PIT only, run with repartition checked
3. reboot/reDownload mode
4. run the full image in Odin.
PIT only returns a black screen on the device. running the full image in afterward returns to the boot loop.
_________________________________
Anything else
1. Download mode
2. Full tar.md5 flash in Odin
3. Ask if it doesn't work
okay, so I'm asking...
I'm still able to boot into recovery mode (blue text).
I've noted a bit of strange behavior when trying to boot into download mode. holding vol down + trackball + power does nothing. however, if I plug the phone in while powered down while holding down the trackball it'll boot into download mode, no power or vol down required.
If you can't flash with Odin, you may have a hardware problem.
Judging from your issue with installing Kies, you had a driver problem previously.
Seems that you are bumbling in the dark here. Once again, people need to be better prepared to Odin their devices before they start modding them.
In fact, getting Odin working should be the first thing a person should do with their phone after rooting and installing CWM.
Anyhow, try a different version of Odin. If that doesn't clear up your problem, I suspect some bad blocks in your flash memory are responsible here. It's a dorment issue that would really only be a problem when you flashed the device. If that's the case, you have a new paperweight.
Good luck.
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
I don't think the problem is that I can't flash with Odin, but that the device isn't loading the ROM that's flashed. poking around in the filestructure with android commander after a fresh load shows that the system makes it onto the phone.
Speaking of poking around with Android Commander, I've noted that the device is software rooted, but not hardware rooted. the default.class file shows ro.debuggable set at 0 where it should be 1. this is keeping me from just pushing the CWM recovery onto the system and restoring the backup I made before getting into this mess. Anybody want to help me pull/edit/flash the image to change that?
As for a driver issue, that's a good possibility given that the one-click uses a driver set, kies mini uses another, kies has a different one yet and we (as a community) started screwing with the t839's using vibrant drivers. I've got them all. thusfar the only drivers I've found that work with both flavors of Odin I have (1.61 and 1.85) would be those that came with the Kies (thanks for the tip pmp326).
On bumbling in the dark, yes, yes I am. There isn't much of an instruction manual for Odin past what's written here, and 90% of that is 'put your phone in download mode, connect Odin, plug the pit in pit and the tar in PDA make sure only auto-reboot is checked and hit start'. to be honest I haven't had to use the program previously as the stock one-click actually worked on my T839. This new device is being ... difficult.
the dormant bad blocks issue you spoke about, was this something found in new-out-the-box phones? I haven't seen a lot about that in the threads, can you point in at more info, please?
at any rate, it doesn't matter which version of Odin I use, I got the same result from both. I tried using a different cable/different USB port as well. I haven't tried using a different system (yet), but don't want to go through all the trouble of setting up everything on another box. Win7 is finicky enough, trying to get everything operating on Server2k3 would most likely end up a challenge. *lol*
I'll try repartitioning with KG1 when I get back to the house.
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
I've gotta pop the debug lock in the default.class to be able to push anything into the system folders with Android Commander. I've found a nice walk-thru to do this, it just requires a little knowledge of c++ and some patience. with any luck I should be able to pull default.class out of its img, edit it and flash that back (most likely with Heimdall since it can do itemized flashing).
pmp326 said:
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
Click to expand...
Click to collapse
tried it, no joy.
pmp326 said:
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
Click to expand...
Click to collapse
tried this, brings me back to the boot loop.
orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
currently I'm running into issues with getting ADB to push onto the system as the system is claiming it isn't rooted. Is there a way I haven't read about or found to root the phone without getting into the actual O/S (i.e. from the blue recovery screen)?
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
rpmccormick said:
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
Click to expand...
Click to collapse
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
I like turtles.
Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
Even the end... I mean, your not trying to odin a "tar.md5" are you?
rpmccormick said:
Even the end... I mean, your not trying to odin a "tar.md5" are you?
Click to expand...
Click to collapse
No....
Sorry man. I've never had to ODIN (this phone). I say check the md5 to make sure you downloaded a good copy, and maybe try a different USB cable. The ADB method seems nutz... if it doesn't boot after a successful ODIN, the phone is probably a paperweight.
Good luck!
Let's see, where shall I begin?
Got my phone back from my girlfriend since she bought the Nexus 4. Battery was extremely swollen and because of that, the phone basically didn't work. Constantly restarting, couldn't use data, etc... Bought a new battery and decided that I would get a nice fresh ROM installed to get this thing running nice again. It has been on Valhalla for about a year now, and I tried to jump straight to the ICS milestone ROM that I saw in Development. Unfortunately, I didn't know of the new CWM that I was supposed to have, which results in a nice little brick. Frozen at the Boot screen. I was able to get it back into download mode with the volume buttons+cable method and luckily Odin recognized it. I installed a really old KD1 Rom that I had which appears to be all the way back to Froyo.
Now that you are up to speed, the phone boots up fine and seems to be working, but nothing in CWM works at all. Everything fails to mount, which means I can't flash any zips to get off this ROM. To top that off, Odin stopped recognizing it in download mode after I installed that other ROM.
It's been too long since I have been on this phone, and within a couple hours of messing with it again, I can see that I have obviously fallen behind on the development. Any suggestions as to what I should do next? My goal is the get it up to the newest ROMs and see how well it runs. I have the Basic with a twist kernel and ICS milestone ROM ready to go, but no way to flash them.
Thank you to anyone who took the time to read this.
Follow this to the tee
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Don't forget to flash bootloader's since you got into Froyo!
Unless you need to, don't flash back to Froyo. Always flash back to stock Gingerbread.
Once you do that flash a another one-click package to get a CWM recovery.
th3controller said:
Follow this to the tee
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Don't forget to flash bootloader's since you got into Froyo!
Unless you need to, don't flash back to Froyo. Always flash back to stock Gingerbread.
Once you do that flash a another one-click package to get a CWM recovery.
Click to expand...
Click to collapse
I didn't even realize it was a Froyo rom, to be honest. I would go and search for a Gingerbread Rom, but the "All roms/rooting/FAQS....." sticky in the development section has been updated in such a long time. I decided to take my chances on that one instead of looking through tons of threads. Froyo was the only one I had for Odin at the moment unfortunately, and Odin was all that I could use.
Thank you so much for the help! This phone should be up and running again in no time!
Don't forget to delete drivers! Odin and Heimdall don't play too well together!
th3controller said:
Don't forget to delete drivers! Odin and Heimdall don't play too well together!
Click to expand...
Click to collapse
Just the Samsung Drivers? I'll try to find them all.
Well, looks like the guide isn't going to work very well for me. I got all the way up to installing drivers with zadig. Heimdall opened automatically like I installed it before ( I may have, it has been forever), but zadig never did. I had to trick it into opening. Once it did open, my phone never shows up in the list of devices as a Samsung device. It only shows up as "Unknown device" and there are no drivers for it to install.
With the phone plugged in download mode, go into device manager delete all USB drivers, reboot pc. Next time you plug in the phone windows should prompt you to install drivers, don't. Use zadig.
TwitchyEye said:
With the phone plugged in download mode, go into device manager delete all USB drivers, reboot pc. Next time you plug in the phone windows should prompt you to install drivers, don't. Use zadig.
Click to expand...
Click to collapse
Finally got around to working on my phone again. Unfortunately, I am unable to follow the guide how I was supposed to. Fortunately, on the other hand, it appears that I successfully got it to flash gingerbread.
Here were my steps to get it work if you want a laugh. My computer didn't like the procedure that the guide had.
1. Update Java, download file, place file into C drive, etc... Everything up to this point worked fine.
2. Open command prompt and execute command. (This is where it all went crazy)
3. Command says false. (instead of opening Zadig, my computer immediately opened Heimdall. So how do I install drivers?)
4. Went to Heimdall help menu and selected install, which froze heimdall completely. Upon Heimdall crashing, Zadig opens.
5. Open Zadig. All drivers are uninstalled, but my device can't be found in the list. (Right after here is where to told me to reboot.)
6. Reboot. Windows keeps automatically installing drivers and I can't do anything about it, so I just uninstall them and try again.
7. Same process. Command prompt, heimdall opens early, crash heimdall, open Zadig, SUCCESSFULLY install drivers.
8. Command prompt again, because that is my only way of getting heimdall open
9. Heimdall finds device, try to flash, but it fails.
10. Unplug phone, and plug in again. Heimdall finds it again.
11. Try to flash again, and success.
It was kind of a nightmare getting it to work, but it looks like it will fix it finally. Thanks for the help everyone!
Double-flashing with Heimdall seems fairly standard. When that happens, sometimes you don't actually have to unplug the phone again, just repeat the same flash-command and it should work the second time. If that doesn't work, reboot the phone, it should go to panic-download mode where it doesn't boot to launcher anymore, just shows the yellow exclamation mark screen, and there the flash should work.
Both my SGS4G and my wife's have done this since we first got them. Sometimes.
So, I know I made lots of mistake and all of it is my fault, but now I need a solution for the huge amount of problems I am facing.
So, I had a stock Froyo on my phone and I tried following the steps of this thread : http://forum.xda-developers.com/showthread.php?t=1894737
The first mistake I did, was I flashed XXKPQ directly by mistake instead of XXKPE, which I noticed while I was in the middle of doing it.
The phone was working properly on the GB rom. After that I rooted it, following the guide using a cf root of XXKPQ.
Now, I didn't know if there was prerequisite for it or not, but I flashed the custom rom of http://forum.xda-developers.com/showthread.php?t=2300693
The first problem I saw was that while installing it from the sdcard, for a long time, the screen was blank. I left it thinking that it was part of it, but since it persisted, I rebooted it. The phone opened properly and after that I installed the gapps later through recovery mode.
The first major problem I saw was that the phone after screen locking, it used to shut down automatically. After looking through solutions, where none were working, I tried flashing to stock rom via odin (stock rom : http://forum.xda-developers.com/showthread.php?p=16107097)
After that though, whenever I open the phone, it just stucks at the samsung logo screen and doesn't go further.
Also, when in download mode, I tried it attaching to Odin but "USB device not recognized" comes all the time.
I don't know what to do.. I know I must have made loads of huge mistakes and I should have done everything, being properly informed, but now I really need a solution..
It's good ur phone is alive after going these many mistakes.
Flash KPE with .pit file then flash DDLF2 firmware. It's the best firmware till date.
Good luck!
Sent from my GT-I9003.
How do I flash it, when the device is not being recognized by my laptop?
tyson123g said:
How do I flash it, when the device is not being recognized by my laptop?
Click to expand...
Click to collapse
Download & install this USB driver for our phone from this thread's 1st post & then try connecting ur phone to ur laptop.
http://forum.xda-developers.com/showthread.php?t=1879783
Good luck!
Sent from my GT-I9003.
Thanks for the advice, but actually after writing that post only, after some time, it started recognizing my device, so I was able to do it..
Though, actually I wanted to install CM10.1, but doing the XXKPE + XXKPQ thing properly and then rooting it again, I tried doing CM10.1. But for some reason after just installing the alpha2 file from zip and the gapps file for it, it always goes back to CWM recovery mode.. It also sometimes used to display that the device has no root access, so while rebooting it asked if I wanted to root it.. I always selected yes, but after booting it always comes back to the recovery screen.
Any idea, what to do to solve this?
tyson123g said:
Thanks for the advice, but actually after writing that post only, after some time, it started recognizing my device, so I was able to do it..
Though, actually I wanted to install CM10.1, but doing the XXKPE + XXKPQ thing properly and then rooting it again, I tried doing CM10.1. But for some reason after just installing the alpha2 file from zip and the gapps file for it, it always goes back to CWM recovery mode.. It also sometimes used to display that the device has no root access, so while rebooting it asked if I wanted to root it.. I always selected yes, but after booting it always comes back to the recovery screen.
Any idea, what to do to solve this?
Click to expand...
Click to collapse
Umm..ur doing something wrong.
Follow correct steps. U will get correct steps in all the rom thread's 1st or in 2nd post.
Good luck.
Sent from my GT-I9003.