Related
Hello, i am currently trying to root my sisters galaxy s 4g... Her Baseband is T949VUVKI1. Firmware is 2.3.5, Build Number is GINGERBREAD.VUVKI1. i remember flashing her phone to 2.3.5 and download mode working perfectly fine, and for some reason it wont go into download mode at all... the computer is not recognizing her phone either. YES, i do have usb drivers installed otherwise my galaxy s 4g wouldnt be recognized on my computer(odin specifically, not turning yellow). Please help, i have searched everywhere in the internet and tried almost everything... Volume up and down and plug charger, batter out volume up and down usb and battery in etc. PLEASE HELP!! Thank You in Advance.
Nvm
10c
1. Try reinstalling to drivers. Also make sure you're using the same USB port as Windows can be funny about it it sometimes.
2. if download mode is being difficult, go download the Android SDK from www.android.com. Install it, run it, and only download the platform tools. When that's done, open a command promt, CD to where the plaform tools installed (either c:\program files\Android\Android-sdk\platform-tools or c:\program files (x86)\Android\Android-sdk\platform-tools ), then issue the command: adb reboot download.
3. I suggest you check the dev section for bhundven's one-click collection. Uses Java and Heimdall vs. ODIN and works easily.
Sent from my SGH-T959V using XDA App
i have this issue 2.3.5 messed me up. Odin sees my phone in debug mode but not in download mode...using odin 1.85 sinse it is the only version that responds to my phone at all. help please!
Tytan0007 said:
i have this issue 2.3.5 messed me up. Odin sees my phone in debug mode but not in download mode...using odin 1.85 sinse it is the only version that responds to my phone at all. help please!
Click to expand...
Click to collapse
Get it back into download mode, go grab a bhundven's one-click. The one-clicks utilize Heimdall vs. ODIN, which means they use open-source USB drivers instead of the proprietary Samsung drivers. See if that enables the computer to see the phone. If so, flash the one-click
Should I uninstall the samsung drivers prior to using Heimdall's One-Click?
Tytan0007 said:
Should I uninstall the samsung drivers prior to using Heimdall's One-Click?
Click to expand...
Click to collapse
That's a good idea. Some people have reported conflicts between the drivers.
Why would only Odin 1.85 see my phone in USB Debugging and not in download mode? And all other Odin verisions never see my phone, no matter what state it is in... I am at work so I will give the one click another try when I get home. I never thought of uninstalling the Samsung drivers prior to install; however, I did use the one click method to no avail. However, Heimdall's one-click was able to see my device it just kept giving me a driver error. This is so crazy it might just work.
Tytan0007 said:
Why would only Odin 1.85 see my phone in USB Debugging and not in download mode? And all other Odin verisions never see my phone, no matter what state it is in... I am at work so I will give the one click another try when I get home. I never thought of uninstalling the Samsung drivers prior to install; however, I did use the one click method to no avail. However, Heimdall's one-click was able to see my device it just kept giving me a driver error. This is so crazy it might just work.
Click to expand...
Click to collapse
I wish I had a good answer. ODIN's a funny animal. I've been fortunate and not had any problems with it. I am hoping you are correct - maybe it was just a driver conflict. Let me know how it goes.
didn't work...
You could try downloading a terminal app from the market. Open the terminal and type:
reboot download
See if that does it.
***Update***
Okay, so Oneclick was not working at all no matter what I did with the drivers. However, in all my tinkering with it I installed the Samsung Driver, the Open Source one, and some gadget driver as well from oneclick.
Doing this put all these drivers in my computer. Then I went into my Device manager (Win 7) and looked at my USB driver and I uninstalled everything and went to the stock win 7 usb driver. Then I plugged my phone in and my computer began searching for drivers for this device when it decided that it would be a good idea to load all three drivers at once and voila my phone was then showing up on ODIN 1.85.
I then proceeded to flash my phone with a rom, probably the wrong one considering I was coming from 2.3.5 and my phone boot looped and then soft bricked(sorry if I used these term incorrectly, noobin it).
After, some nervous moment of scouring XDA I found the god-send of a post on getting in to download mode, using odin, and flashing stock 2.3.6 - thank you Raver(I believe). When I did this, my phone magically started obeying ODIN like a devout viking and is now running 2.3.6 superbly.
Keeping with my phones newly found viking heritage, I intend to figure out how to properly root it, update the kernal and modem(not sure which one is best), get CWM, and subsequesntly put in Valhalla Black.
Seeing as though this last rendevous with flashing caused me a little scare I may hold off and wait to see what the next big update is (maybe a port ICS variant) and then go with that.
Anyway, thank you Stephen for helping me out with this and to everyone in this post.
Here's some reading for you Tytan,
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G#FAQ_.28with_answers.29
PS: Unless you wanna brick your phone, do not flash anything that isn't intended for the SGH-T959V Samsung Galaxy S 4G. You're saying you wanna flash a Vibrant ROM. You can, if you want an expensive paperweight. Happy flashing!
2.3.5 may have been for vibrant...yeah I think I got lucky. I did it prior to knowing about xda.
Sent from my SGH-T959V using XDA App
Tytan0007 said:
didn't work...
Click to expand...
Click to collapse
How are you getting into download mode?
There was a post in another thread where the person apparently was using the power menu to get into download mode or maybe the adb command.
Have you tried both the old fashion volume +/- and plug in usb cable? Or the adb command?
Do you have access to another computer? Believe it or not sometimes just changing computers will make the difference.
Weird when I replied there was no posts other than the ones on the first page...oh well glad its working now.
Hi, I tried reflashing zeus on my infuse after getting tired of AEON, but instead I ended up flashing cm7 onto my phone, now i cant get it past the samsung screen. Its not like the infinite boot loops where it flashes on and then resets, it just sits at the samsung screen. I have already tried deleting all caches reflashing to ZEUS, AEON, and CM7, nothing works, i cannot get past the samsung screen. Luckily i can still get to the recovery menu which means something still is working.
My question is, what do I have to do? I dont mind going back to stock but I dont know how to go about doing it. Another problem I have is that my phone cannot ( from my point of view) connect to a computer. Ever since I rooted my phone I cannot connect my phone or sd card to my computer.
Someone Please Help.
There is a whole section on how to return to stock (Factory / Return to Stock at the beginning of the following:
http://forum.xda-developers.com/showthread.php?t=1610374
Do a little reading. I find Heimdall the easiest, others prefer Odin.
Yeah, what he said. Me, I use Odin, with unbrick root 1.1 then flash again with a cwm root extras, getting me out of that stock recovery 3e I think it's called.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
psal217050 said:
There is a whole section on how to return to stock (Factory / Return to Stock at the beginning of the following:
http://forum.xda-developers.com/showthread.php?t=1610374
Do a little reading. I find Heimdall the easiest, others prefer Odin.
Click to expand...
Click to collapse
Heimdall Odin and computer in general doesnt acknoweldge that my phone is plugged into the computer no matter what usb port I plug into, I can give them a shot again but I tried odin yesterday and It didnt do anything...
Edit: Just tried Heimdall and odin again to no avail, the computer does not nor has ever recognized that the phone was plugged in, and just to make sure I used my laptop and my desktop and neither of them could connect to my phone.... looks like im screwed......
Javelin177 said:
looks like im screwed......
Click to expand...
Click to collapse
Not by a longshot.
For Heimdall, a lot of people have reported problems but the suggestion is perserverence.
First make sure you read and follow the instructions very carefully.
Try with different ports on your computer (ok, you did this one).
Try with different computers.
Try with different cords.
Perhaps unload and re-install the drivers.
Post back here what kind of things you are seeing.. which step looks like it isn't responding as expected.
If you really can't connect using Heimdall (and I can understand how hopeless that can seem... been there myself), you still have a lot of options because you said in your first post you can boot into recovery. .
That means there is a lot of stuff you can flash.
Ethereal, Aeon are good stable GB custom roms and easier to flash than the stock one.
For stock, you might try to flash dman's stock UCLB3:
http://forum.xda-developers.com/showthread.php?t=1508619
The complicated part of dman's stock UCLB3 is the stuff in there about video I don't quite understand (*)
To get video back, you have to put the stock kernel back in (disable lagfix first!). The stock kernel will make you lose CWM but not root.
Then you can flash a custom GB kernel (Entropy's DD or Zen's Infusion) to get back CWM.
(*) Here's the part I don't understand: When we go back to custom kernel, do we still have the video or does it get lost because we no longer have the stock kernel ?
If anyone can clarify that one point, I'd be grateful.
electricpete1 said:
Not by a longshot.
For Heimdall, a lot of people have reported problems but the suggestion is perserverence.
First make sure you read and follow the instructions very carefully.
Try with different ports on your computer (ok, you did this one).
Try with different computers.
Try with different cords.
Perhaps unload and re-install the drivers.
Post back here what kind of things you are seeing.. which step looks like it isn't responding as expected.
If you really can't connect using Heimdall (and I can understand how hopeless that can seem... been there myself), you still have a lot of options because you said in your first post you can boot into recovery. .
That means there is a lot of stuff you can flash.
Ethereal, Aeon are good stable GB custom roms and easier to flash than the stock one.
For stock, you might try to flash dman's stock UCLB3:
http://forum.xda-developers.com/showthread.php?t=1508619
The complicated part of dman's stock UCLB3 is the stuff in there about video I don't quite understand (*)
To get video back, you have to put the stock kernel back in (disable lagfix first!). The stock kernel will make you lose CWM but not root.
Then you can flash a custom GB kernel (Entropy's DD or Zen's Infusion) to get back CWM.
(*) Here's the part I don't understand: When we go back to custom kernel, do we still have the video or does it get lost because we no longer have the stock kernel ?
If anyone can clarify that one point, I'd be grateful.
Click to expand...
Click to collapse
Well heres the thing, when i first screwed up I tried flashing back to Zeus or AEon, problem was it would go through all fine and dandy and I would get happy thinking I have a phone again, but then when I rebooted it sat at the samsung screen, which i figured it would do, so I left it over night so it could set itself up like it usually does after flashing to a new rom. It sat over night and didnt move off the samsung screen, both with Aeon and Zeus.
Another thing too is that I thought if I partitioned the sd card and then worked off a fresh partition, I could get past the screen and then upartitiion and reflash the whole thing... Now my phone won't mount the sdcard, it doesnt recognize the sd or the sd-ext, tried mounting, manual mounts and everything. I even tried reformatting the external sd, to see if that would help. It didnt....
So the question is now... am I now screwed???
tl;dr... Phone cannot connect to computer to use heimdall or odin, wouldnt boot into new rom after flashing three or four times, and now the sd card wont mount... screwd :crying:
edit: It might not even be worth fixing because I think im going to get the nexus 4 on wednesday.... but I still would like to fix it if I can. Thanks guys for helping me so far through these tough times hahaha
(*) Here's the part I don't understand: When we go back to custom kernel, do
we still have the video or does it get lost because we no longer have the stock
kernel ?
If anyone can clarify that one point, I'd be grateful.
Click to expand...
Click to collapse
The post from Dman predates the video and MHL-HDMI out fixes that Entropy512 provided. The current Entropy DD and Zen Infusion kernels have the same video and MHL support found in the stock UCLB3 kernel.
Note that if you are coming from a JB ROM, you need to flash an Odin or Heimdall package with a PIT file to get the stock partition config back. They can be found here:
ODIN - http://forum.xda-developers.com/showthread.php?t=1705260
Heimdall - http://forum.xda-developers.com/showthread.php?t=1524081
Either will return your phone to stock after which you can ODIN or Heimdall a custom kernel and flash a custom ROM. If you flash the ODIN package with root you can also use SGS Kernel Flasher to flash a new kernel zImage file.
Zen Arcade said:
Either will return your phone to stock after which you can ODIN or Heimdall a custom kernel and flash a custom ROM. If you flash the ODIN package with root you can also use SGS Kernel Flasher to flash a new kernel zImage file.
Click to expand...
Click to collapse
But like I said just a few minutes ago, I can't even get heimdall or odin to recognize the phone. Even before All of this started happening, my computer would not recognize my phone, or my sd card.
You said you used a different PC or laptop. Did you try a new cable? I had a cable that didn't read correctly, switched to another and was able to flash.
Sent from my SGH-I997 using xda premium
psal217050 said:
You said you used a different PC or laptop. Did you try a new cable? I had a cable that didn't read correctly, switched to another and was able to flash.
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Yup. I have used three different usb cables: Two OEM's, and one After market.
You may have an issue with your Infuse drivers on your PC.. to fix this:
1 - uninstall all existing Samsung Infuse drivers using control panel/programs and features - this would include "kies", "kies mini" and/or "SAMSUNG USB Driver for Mobile Phones"
2 - remove any remaining devices from control panel/device manager
2a - as part of this you may need to look at hidden devices. To do this you will need to add a system environment variable (from control panel/system/advanced) called "DEVMGR_SHOW_NONPRESENT_DEVICES" and set its value to "1". Then from device manager "view" menu select "show hidden devices"
2b - Look for devices under "Universal Serial Bus devices" and "Universal Serial Bus controllers" that are named "SAMSUNG USB Composite Device" or "SAMSUNG Android USB Composite Device" and remove
3 - you might need to reboot after removing drivers and associated devices (recommended)
4 - reinstall Samsung Infuse drivers... (do not use the link in the ODIN thread)
4a - kies mini is available here:
http://org.downloadcenter.samsung.c...ATT_I997_Infuse_4G_Kiesmini_1.0.0.11084_3.exe
or from here (downloads/software):
http://www.samsung.com/us/support/owners/product/SEG-I997ZKAATT
(you may have better results using the "driver only" option at the second link - the smaller of the two files. Kies can sometimes cause problems of its own).
5 - once installed and rebooted, connect your phone (booted into phone OS with USB Mass Storage mode enabled and then USB Debugging enabled) and validate connectivity using ADB or by mounting to PC as a USB storage device. Test by copying a decent sized file to/from the phone.
6 - if this works, boot into download mode and retry Odin or Heimdall packages. If you don't have Java Runtime Environment installed make sure you install that first. For Heimdall (and maybe Odin) make sure to right click the file name and run as administrator.
---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------
Or... If you are still in the middle of a CM7 install, you may just need to complete the install by booting recovery, wiping system and flashing a second time as shown in the install instructions here:
http://forum.xda-developers.com/showthread.php?t=1311960&highlight=cm7
Either way, good luck!
I thought cm7 required a double flash...just like ICS does if coming from GB...
So flash
Get stuck at Samsung screen
Boot to recovery
Re flash
reboot
Enjoy?
Could be wrong though as I never used cm7...but I remember reading that our idea to double flash for ICS came from cm7
Sent from my SGH-I997 using Tapatalk 2
Zen Arcade said:
You may have an issue with your Infuse drivers on your PC.. to fix this:
1 - uninstall all existing Samsung Infuse drivers using control panel/programs and features - this would include "kies", "kies mini" and/or "SAMSUNG USB Driver for Mobile Phones"
2 - remove any remaining devices from control panel/device manager
2a - as part of this you may need to look at hidden devices. To do this you will need to add a system environment variable (from control panel/system/advanced) called "DEVMGR_SHOW_NONPRESENT_DEVICES" and set its value to "1". Then from device manager "view" menu select "show hidden devices"
2b - Look for devices under "Universal Serial Bus devices" and "Universal Serial Bus controllers" that are named "SAMSUNG USB Composite Device" or "SAMSUNG Android USB Composite Device" and remove
3 - you might need to reboot after removing drivers and associated devices (recommended)
4 - reinstall Samsung Infuse drivers... (do not use the link in the ODIN thread)
4a - kies mini is available here:
http://org.downloadcenter.samsung.c...ATT_I997_Infuse_4G_Kiesmini_1.0.0.11084_3.exe
or from here (downloads/software):
http://www.samsung.com/us/support/owners/product/SEG-I997ZKAATT
5 - once installed and rebooted, connect your phone (booted into phone OS with USB Mass Storage mode enabled and then USB Debugging enabled) and validate connectivity using ADB or by mounting to PC as a USB storage device. Test by copying a decent sized file to/from the phone.
6 - if this works, boot into download mode and retry Odin or Heimdall packages. If you don't have Java Runtime Environment installed make sure you install that first. For Heimdall (and maybe Odin) make sure to right click the file name and run as administrator.
---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------
Or... If you are still in the middle of a CM7 install, you may just need to complete the install by booting recovery, wiping system and flashing a second time as shown in the install instructions here:
http://forum.xda-developers.com/showthread.php?t=1311960&highlight=cm7
Either way, good luck!
Click to expand...
Click to collapse
You should get a triple thanks for writing this up.
Here is where I noted many users get stuck. Completely uninstalling and reinstalling drivers is the key.
mg2195 said:
I thought cm7 required a double flash...just like ICS does if coming from GB...
So flash
Get stuck at Samsung screen
Boot to recovery
Re flash
reboot
Enjoy?
Could be wrong though as I never used cm7...but I remember reading that our idea to double flash for ICS came from cm7
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Yeah..I think CM7 require a double flash if you are coming from froyo or gb. Something about the double flash for the recovery
same thing for gb to jb double flash works on mine flash once sticks at kernel, pull bat,three finger again to blue recovery the reflash rom again and bingo
Sent from my SAMSUNG-SGH-I997 using xda premium
Hi All,
I was using Samsung Galaxy SL (I9003) with Android Gingerbread 2.3.6. I wanted to install CM10. Here what I did.
-> Rooted the phone using Odin (Windows)
-> Installed CM10 through SD Card
-> Installed gapps through SD Card
So far went well and I was able to install the ROM. But my key board was not working. So I wanted (I got scared on rooting) to recover my stock ROM (which I took backup through CWM)
Now my phone got soft bricked. It goes into boot loop (Samsung logo). Doesn't open up recovery. It goes into Download mode. But none of the computer recognizes it. Odin (Windows) doesn't, Heimdall doesn't, ADB doesn't. Fastbood Doesn't.
I am desperate for a solution to bring my phone alive.
It does turn on and it goes into download mode. But not able to find option to flash the Rom.
I am new to the forum and this area. So sorry for my ignorence
If you've flashed "[ALPHA][ROM][4.1.2] CyanogenMod 10 for Samsung Galaxy SL - Alpha 4 - Farewell Release" and re-flashed other roms other than Alpha 4 without repartition(going back to Odin-Pit-XXKPE/XXKPQ-DDLF2/or any-root) I think you've hard bricked your phone...http://forum.xda-developers.com/showthread.php?t=2048672
wee2wee said:
If you've flashed "[ALPHA][ROM][4.1.2] CyanogenMod 10 for Samsung Galaxy SL - Alpha 4 - Farewell Release" and re-flashed other roms other than Alpha 4 without repartition(going back to Odin-Pit-XXKPE/XXKPQ-DDLF2/or any-root) I think you've hard bricked your phone...http://forum.xda-developers.com/showthread.php?t=2048672
Click to expand...
Click to collapse
Thanks.. I also think so. if I give it to Samsung service center.. can they recover it (it's out of warranty) - if it is less costlier than a new phone ?
Thanks,
Achir
as far as i know, if you can go into download mode then your phone is not bricked.
just flash back to CM10A4 and follow the step to go back to stock.
sianghung said:
as far as i know, if you can go into download mode then your phone is not bricked.
just flash back to CM10A4 and follow the step to go back to stock.
Click to expand...
Click to collapse
How can I flash ? No computer is detecting my device. What alternate option I have ? Can a Jig help ? I think jig is just to put the phone in download mode.
Thanks,
Achir
achir said:
How can I flash ? No computer is detecting my device. What alternate option I have ? Can a Jig help ? I think jig is just to put the phone in download mode.
Thanks,
Achir
Click to expand...
Click to collapse
try reinstalling ur phone driver? restart ur pc and try again??
wee2wee said:
If you've flashed "[ALPHA][ROM][4.1.2] CyanogenMod 10 for Samsung Galaxy SL - Alpha 4 - Farewell Release" and re-flashed other roms other than Alpha 4 without repartition(going back to Odin-Pit-XXKPE/XXKPQ-DDLF2/or any-root) I think you've hard bricked your phone...http://forum.xda-developers.com/showthread.php?t=2048672
Click to expand...
Click to collapse
Lola's i9003 was dead because it does not start... but my friend in this case achir SL is still recoverable...
@achir:dont panic and dont flash unnecessary things...You have soft bricked your SL.. too much of flashing and a small mistake can brick your phone.
and since you said your phone is not detected by ODIN but you can still go in download mode... so here are the steps which can help you..
1.Install samsung USB drivers for I9003
2.Install net framework on your PC
3.Disable your computers Antivirus and Firewall(it may interupt with ODIN process)
4.Restart your PC.
5.Connect your phone in download mode.
6.If its detected by system but not by ODIN then unplug and then replug the phone, repeat this process untill your phone is recognised by ODIN(rebooting of PC should also be done if necessary).
7.Once connected/recognised by ODIN flash a stock firmware.
8.Be patient because the first boot will take a long time.
let me know if it worked well?
You need not worry. I too had a bricked my phone exactly on Jan 1 (and missed wishing my friends as my phone was off).
See my forum where i faced the same issue. http://forum.xda-developers.com/showthread.php?t=2076250
As our members have mentioned you can reinstall the Samsung drivers in the PC which will make ODIN detect your phone. :good:
Okay. I re-installed the driver but still my PC doesn't recognize it (unknown device). My Mac and my friend's Linux can not recognize it.
I have my personal Mac (Windows is in office laptop which doesn't have full admin). But I tried with Heimdall and ADB in my Mac (I assume doesn't need driver) but they can not list my device.
Now my critical problem is making my Mac detect the device so that I can proceed with some recovery (if at all possible).
You case is very similar with lolation. From cm10a4 with mtd fs direct flash rfs fs. Lolation go to service center.
Sent from my Galaxy Nexus using Tapatalk 2
I tried a lot but it seems no computer can recognize the phone. It seems service center is the only option
Have you try using another usb cable?(maybe the usb cable you're using now is defect)..According to Dhiru, either Alpha 3 or 4 won't result in a hardbrick...read here... http://forum.xda-developers.com/showthread.php?p=35505300#post35505300
Can't Recover ! Need Help
Can't Recover ! Need Help
Hi All,
I was using Samsung Galaxy SL (I9003) 4GB Indian with Android Gingerbread 2.3.6.7 I wanted to install CM10. Here what I did.
-> Rooted the phone using Odin (Windows)
-> Installed CM10 through SD Card
-> Installed gapps through SD Card
So far went well and I was able to install the ROM. But my key board was not working. So I wanted (I got scared on rooting) to recover my stock ROM (which I took backup through CWM)
Now my phone got bricked. I can open up recovery either goes into Download mode. Odin (Windows) which doesn't help me. i tried to install rom but got error now my phone can get into recovery or download mode only.
I tried to flash it gives me pass but position is same please help someone.
After reinstalling ur kies,connect ur phone to odin...it will be detected..if it is not detected also , just frst flash latona.pit file...once... if not flashed try to flash again....then flash complete package of xxkpe...ur phone will boot up..bcz one time i too faced same prblm...my phone was not detected by Odin..but i flashed latona.pit file,by luck it worked for me...then i flashed xxkpe...phonegot bootedup...
---------- Post added at 01:01 AM ---------- Previous post was at 12:58 AM ----------
caashmon said:
Can't Recover ! Need Help
Hi All,
I was using Samsung Galaxy SL (I9003) 4GB Indian with Android Gingerbread 2.3.6.7 I wanted to install CM10. Here what I did.
-> Rooted the phone using Odin (Windows)
-> Installed CM10 through SD Card
-> Installed gapps through SD Card
So far went well and I was able to install the ROM. But my key board was not working. So I wanted (I got scared on rooting) to recover my stock ROM (which I took backup through CWM)
Now my phone got bricked. I can open up recovery either goes into Download mode. Odin (Windows) which doesn't help me. i tried to install rom but got error now my phone can get into recovery or download mode only.
I tried to flash it gives me pass but position is same please help someone.
Click to expand...
Click to collapse
Go to download mode...flash latona.pit file...then ur phone will be in black color screen..then remove battery again go to download mode and flash full xxkpe package...ur phone will boot up...
I tried to upgrade to Android on the phone as written here
http://forum.xda-developers.com/showthread.php?t=1601844
After first step when installed the firmware from zip and going back into recovery mode I can only see this (picture attached).
Tried to reboot in CVM or regular, it won't go any further.
If I place it in download mode the Odin won't see it. (Installed Kies 3 to have the drivers).
What else can I do and make it work?
Thx
http://forum.xda-developers.com/showthread.php?t=1524081&page=33
qkster said:
http://forum.xda-developers.com/showthread.php?t=1524081&page=33
Click to expand...
Click to collapse
Actually I could fixed it, the point Odin didn't see it was because the drivers for USB samsung weren't installed properly by Kies under Win 8 x64, so I went into Device Manager and installed by hand.
After that Odin saw the phone, and from there it was a piece of cake to solve it.
I had some other couple of issues with the correct JB installation for it, after a couple of rounds of restoring everything via Odin I finally had success with this build http://forum.xda-developers.com/showthread.php?t=2130816 which for some reason was the last on my list to try. But it works pretty well.
Previously, I've talked about how I bricked my G920T by using an apk to try to root my phone.
Then I tried to do a factory reset with the stock recovery but it wouldn't even go into the stock recovery. So I flashed TWRP and wiped the whole phone including the system partition.
Then I tried to flash a stock 6.0.1 firmware to the phone but doing so did not improve the situation as my phone still won't boot. Even worse, when I power my phone, all I see is the blue LED indicator, no Samsung logo, nothing.
Then I tried to flash a custom ROM like XtreStoLite but that didn't fix anything either.
When I use TWRP or the stock recovery, the error "failed to mount /efs (invalid argument)" comes up on the log. I tried using the ADB method to fix it but my phone would not get recognized by ADB probably because USB debugging isn't on by default.
I cannot shut down the phone without having it charged to a power source then holding down PWR+DOWN VOLUME+HOME until the screen shuts off.
When I enter download mode, I don't see the warning screen, I enter the download mode directly.
It will warm you when you enter download. Or use TWRP and reboot into Download.Once in download flash the ROM using Odin. Get the latest one from SamFirm.
P.S. Next time root using CF Auto Root
yasteellutch said:
It will warm you when you enter download. Or use TWRP and reboot into Download.Once in download flash the ROM using Odin. Get the latest one from SamFirm.
P.S. Next time root using CF Auto Root
Click to expand...
Click to collapse
It doesn't warn me when I enter download mode, that's one of the problems.
I tried flashing the official ROM using ODIN, it still won't boot because of the efs error.
1) Download the latest SmartSwitch
2) Click on more -> Emergency software recovery and initialization
3) Go into Device initialization, enter your model name, search for it and proceed as advised by the assistant
That should fix everything, otherwise:
1) Download the latest official firmware for your model, the 4-File (or 3-File) Version
2) Use latest ODIN, check repartition in options
3) Select all the files and flash it
If EFS or DRK is corrupted, flashing roms, custom or not won`t help, it can be fixed via repair box maybe (Octoplus/Z3X)
Try to flash CF auto root for your model, if it still won`t boot, then find someone with a box to try to help you remotely or not.
But Smart Switch emergency initialization with phone sn would be the first thing I would try.
Orginator said:
1) Download the latest SmartSwitch
2) Click on more -> Emergency software recovery and initialization
3) Go into Device initialization, enter your model name, search for it and proceed as advised by the assistant
That should fix everything, otherwise:
1) Download the latest official firmware for your model, the 4-File (or 3-File) Version
2) Use latest ODIN, check repartition in options
3) Select all the files and flash it
Click to expand...
Click to collapse
Which mode should I be in when using SmartSwitch? No devices are shown when I have it plugged in during the bootup, and is so too in download mode but shows a not supported message.
brenner650 said:
If EFS or DRK is corrupted, flashing roms, custom or not won`t help, it can be fixed via repair box maybe (Octoplus/Z3X)
Try to flash CF auto root for your model, if it still won`t boot, then find someone with a box to try to help you remotely or not.
But Smart Switch emergency initialization with phone sn would be the first thing I would try.
Click to expand...
Click to collapse
How can someone with a box help me remotely?
zheyizhu said:
Which mode should I be in when using SmartSwitch? No devices are shown when I have it plugged in during the bootup, and is so too in download mode but shows a not supported message.
Click to expand...
Click to collapse
Download mode offcourse. Nevermind the not supported message.
Follow instructions from link below, I made it for such occasions:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
zheyizhu said:
How can someone with a box help me remotely?
Click to expand...
Click to collapse
Well if you know someone who have a box, it doesn`t have to be remotely.
If not, it is possible to fix it remotely, with help of usb hub (FlexiHub or similar), tunneling (TeamViewer or similar) and box software (you connect phone to your computer, the other guy connects box to his computer, both of you are connected through a gateway to a wonderfull thing called internet, and everybody is happy ) .
Same as on site, just with few more things in between the phone, and the box.
brenner650 said:
Download mode offcourse. Nevermind the not supported message.
Follow instructions from link below, I made it for such occasions:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
Well if you know someone who have a box, it doesn`t have to be remotely.
If not, it is possible to fix it remotely, with help of usb hub (FlexiHub or similar), tunneling (TeamViewer or similar) and box software (you connect phone to your computer, the other guy connects box to his computer, both of you are connected through a gateway to a wonderfull thing called internet, and everybody is happy ) .
Same as on site, just with few more things in between the phone, and the box.
Click to expand...
Click to collapse
The S/N sticker on the back of the phone is long gone, is there any other way I can find it besides from going into settings because I can't do that?
EDIT: I am able to borrow a friend's serial and got the firmware installed.
The Samsung boot logo is back now, however, the device still won't boot. The efs error is still there but the download mode warning sign came back.
EDIT #2: Okay, I flashed TWRP now and ADB is working once again. Can I utilize this to fix the efs error?