Develop Bugs

Rooting the Captivate Glide (SGH-I927)

Note - Sorry everyone; I've been so busy with work the past few days, and it doesn't seem to be letting up any time soon. I'll try to check in as much as possible.
This thread is mainly for rooting development / techniques and updates on the SGH-I927[R]; If you're looking for the latest (detailed) instructions, please see CarpeNoctem's guide here:
http://forum.xda-developers.com/showthread.php?t=1378082
If you want to participate in ongoing rooting/dev work, keep reading!
----
Success! The SGH-I927R was rooted on Dec 5, after a great team effort. We finally have the powerful device the Captivate Glide was meant to be! Special thanks to:
ardatdat, boog, CarpeNoctem, and everyone that helped keep this thread alive.
You've now got a couple options. If you don't mind the annoying little yellow triangle on boot-up (I think it looks kinda hackerish ), you can simply flash my insecure STOCK Rogers boot image (ro.secure = 0), attached to this message. I've never tested this against an AT&T ROM, so if you do, please report back how it goes!
Simply load this .tar up in the PDA section (same as procedure below), flash, and you should be able to adb in as root. Then, install your mode 6755 su binary into /system/xbin, and superuser.apk.
Note that you can always flash back to the stock kernel (also attached), when you're done rooting your device. This will restore the normal boot logo.
Alternatively, here are two pre-rooted ROMs:
Rogers Canada (SGH-I927R): https://rapidshare.com/files/1741701072/SGH-I927RUXKJ5_STOCK_ROOTED.tar.bz2
AT&T (SGH-I927): https://rapidshare.com/files/3058304268/I927UCKI3_STOCK_ROOTED.tar.bz2
1. Unpack the tarball, which will dump out a single tar file.
2. Put phone into download mode.
3. Launch ODIN, and select the file from the PDA flash option.
4. Don't touch anything else!
5. Flash the image.
Now, this goes without saying, but:
This is highly experimental! It could permanently brick your device! It worked for me, but I cannot accept any responsibility if something goes wrong!
At this point, it seems kernels and roms are interchangeable. I highly recommend the Rogers kernel, as it's not infected with CarrierIQ.
PS - Thank you Rogers, for doing the right thing!

The CL652095 is part of their build number, and modules from a different build won't work if that 'version magic' doesn't match.
So, if you try to build a kernel from other source (and the initramfs from your kernel) you will need to
Code:
export LOCALVERSION="-I927RUXKJ5-CL652095"
that way it will load the prebuilt modules properly.
But, if you can pull the zimage from the phone, it might be easier to just unpack, add su (or cwm, then you could flash root from cwm) and repack.

boog said:
The CL652095 is part of their build number, and modules from a different build won't work if that 'version magic' doesn't match.
So, if you try to build a kernel from other source (and the initramfs from your kernel) you will need to
Code:
export LOCALVERSION="-I927RUXKJ5-CL652095"
that way it will load the prebuilt modules properly.
But, if you can pull the zimage from the phone, it might be easier to just unpack, add su (or cwm, then you could flash root from cwm) and repack.
Click to expand...
Click to collapse
Yeah, assuming they're only using that to stamp the kernel and not to reflect their own (critical) patchset they've applied to the stock source.
I sent yet another request to Samsung support, and they're playing dumb. Their support guys claim to "not have the source" and be "not affiliated with the Samsung open source release center" (no joke).
I also filled out a request on their web form on the OSRC; I'll see what they say.
Honestly if there were a way to extract the kernel, we'd be golden. Unfortunately all mmcblk* devices are 007 masked or worse. Wonder if these devices have some undocumented "upload" mode.
Does anyone know if kies is able to force-recover a device with the emergency firmware recovery utility? Does the recovery mode use the main kernel that gets flashed by ODIN, or some separate kernel? ie. if I flash a bad kernel, is it lights out, or will recovery mode still work?

I know adam has been able to use UART to root devices and pull software.
Im pretty sure you need some hardware. But if anyone can find a way its adam.

Well, I'll be damned!
I made a request to the Samsung Open Source Release Center for the source, and they delivered!
I'm downloading right now and will report back shortly!
If anyone else is interested in checking it out, here's the link they gave me:
https://opensource.samsung.com/reception/receptionSub.do?method=downLoad&attach_id=1842
Go Samsung!

I'm not trying to make too much of a tangent but with an upgrade due in a few months I've been considering this device. would you recommend it? If the hardware is worthy I will definitely root& rom and contribute to the community when I have the time.
How would you compare it to to original captivate?

BigArea said:
I'm not trying to make too much of a tangent but with an upgrade due in a few months I've been considering this device. would you recommend it? If the hardware is worthy I will definitely root& rom and contribute to the community when I have the time.
How would you compare it to to original captivate?
Click to expand...
Click to collapse
Honestly, my only issue is the lack of rootability (which hopefully will be solved soon).
Now, I'm coming from a 2+ year old n900, so take my opinion with a grain of salt, but I have to say that the phone itself is spectacular. If it wasn't, I'd have returned it the day I realized it couldn't be easily rooted. It was good enough to make me hold out.
The display is gorgeous, form factor perfect, keyboard is decent enough (not as good as the n900's, but it was way above average), and the performance is, for me, mind blowing.

BigArea said:
I'm not trying to make too much of a tangent but with an upgrade due in a few months I've been considering this device. would you recommend it? If the hardware is worthy I will definitely root& rom and contribute to the community when I have the time.
How would you compare it to to original captivate?
Click to expand...
Click to collapse
slide-out keyboard, stock gingerbread, front-facing camera... in line for an official ICS upgrade (maybe????)... dual core CPU... faster HSPA+ downloads...

Ok, I successfully built a kernel for our device! Time to roll the dice.
...fires up ODIN...
Wish me luck!
Does anyone know offhand how to make a kernel insecure?

Try telling it that it needs to lose some weight. That should make it really insecure.

lol rof ! +10
I am going to request from the moderator to create a captivate glide dev subforum and Q&A.

Well, that got ugly.
ODIN failed to flash the new kernel, giving this error:
Code:
...
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> zImage
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now it's complaining I need to do a firmware recovery. Ugh.
I hope this is reversible.
Any ODIN experts monitoring this thread?
Also, does anyone know how to use KIES to perform an emergency recovery? The device isn't showing up in the list.
EDIT
Ok, this is bizarre. Out of desperation, I booted into 3e recovery mode, rebooted, and suddenly my device came back to life. Running fine. As if nothing happened. I checked the kernel timestamp (from /proc/version) and it's still the stock kernel, so the NAND update failed. I guess it must have flagged a failure, and that flag was reset by recovery mode!

lambgx02 said:
Ok, I successfully built a kernel for our device! Time to roll the dice.
...fires up ODIN...
Wish me luck!
Does anyone know offhand how to make a kernel insecure?
Click to expand...
Click to collapse
How did you build a kernel without the source being released??

jmtheiss said:
Try telling it that it needs to lose some weight. That should make it really insecure.
Click to expand...
Click to collapse
LMAO....+1

CarpeNoctem said:
How did you build a kernel without the source being released??
Click to expand...
Click to collapse
see post #5

lambgx02 said:
Well, that got ugly.
ODIN failed to flash the new kernel, giving this error:
Code:
...
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> zImage
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now it's complaining I need to do a firmware recovery. Ugh.
I hope this is reversible.
Any ODIN experts monitoring this thread?
Also, does anyone know how to use KIES to perform an emergency recovery? The device isn't showing up in the list.
EDIT
Ok, this is bizarre. Out of desperation, I booted into 3e recovery mode, rebooted, and suddenly my device came back to life. Running fine. As if nothing happened. I checked the kernel timestamp (from /proc/version) and it's still the stock kernel, so the NAND update failed. I guess it must have flagged a failure, and that flag was reset by recovery mode!
Click to expand...
Click to collapse
I have had issues with samsung's source. We have been playing with their kh2 source, and I get builds that seem to build successfully, but never boot. Had a few that wouldn't flash (using heimdall), for some mysterious reason that seem similar to what you got.
I would say you still need a backup zimage before trying to flash an unknown kernel. You could be stuck with a non booting phone without it.

Did anybody tried this kernel, same tegra2 same os and version: http://forum.xda-developers.com/showthread.php?t=1348857
when I compare the source from samsung there are some difference (ATT reference in the i927 one) but they are 99.99% similar

hi .. everyone here. I am the kernel developer for i9103.
Firstly, I do not get the Captivate Glide. But, could I do anything for the GLIDE? If I try to compile a kernel, I could not test in using my machine.
And I think you all know how to use Odin3 thru PDA to flash ROM & kernels?

ardatdat said:
hi .. everyone here. I am the kernel developer for i9103.
Firstly, I do not get the Captivate Glide. But, could I do anything for the GLIDE? If I try to compile a kernel, I could not test in using my machine.
And I think you all know how to use Odin3 thru PDA to flash ROM & kernels?
Click to expand...
Click to collapse
Honestly if you can compile the kernel with root and CWM that would be HEAVEN!!
I install your other kernel (curiosity I had to try) and bricked my phone

Also, do anyone get the original kernel (boot.img) for that phone? It will help me and be the most important part to have the compiled kernel working on the phone.
So, please, if anyone get the boot.img, please keep it, upload it and tell me. Thanks.

Not able to go back to stock ROM - Samsung Galaxy S2

Phone: Samsung Galaxy S II Epic 4G Touch - SPH-D710
Carrier: Sprint
Odin version: Odin3-v1.85
Stock image name: HOME_SPH-D710_EK02_CL704398_user.tar
I've tried to use the instructions & stock image posted here and encountered a problem.
When I run Oden, it just sits there at the point where it tries to establish a connection.
I've seen it get a few steps further, and then stall at trying to push an image to the phone.
This is as far as it gets:
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> Sbl.bin
<ID:0/004> zImage
<ID:0/004> factoryfs.img
Then it just sits there. I'm now currently in a bricked state, so I'm extremely open to suggestions

Just realized that this probably should have been posted in the Q&A. Sorry!

Take the battery out, the external SD card (if you have one insert), get a different micro USB cord, then try odin again.
Its usually just the new/different USB cord that does the trick.
If not, try re-downloading the tar, you might have got a bad download.

Close Odin from the red box in the corner then disconnect and pull battery. Put it back and try to go back into download mode. If your phone has any signs of life, it can be saved. I also always Odin with at least 60% battery just to be safe. Also, what Broded said may be the case. It could be a bad download of the tar. It seems like its hanging at the beginning which is much better than hanging in the middle or end
Sent from my Nexus S 4G using xda premium

That one doesn't use an md5 checksum to protect against file corruption. It does have one, but for some reason the file got renamed so it doesn't get used.
If you use the one from my signature, it will not start flashing unless the file contents are verified to be in the proper condition.

Take their advice and redownload the tar file. Get The one that has the .md5 at the end. This will make sure the file is nit corrupted
Sent from my Nexus S 4G using xda premium

Thanks everyone for the replies. I was kind of worried that I'd come back to a bunch of links to the you are a noob video
So I followed the suggestions in this thread including:
I pulled the SD card
The EK02 ROM listed on sfhub's sig w/ MD5.
Switched USB cables & ports on the computer.
Odin still seems to get stuck in the same "SetupConnection.." spot.
From the logs:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EK02_CL704398_ROM_PDA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
I think next I will try this on another PC. Maybe a fresh slate will help. Does anyone have any other suggestions? How long should it sit at the SetupConnection.. part?
I had a pretty full battery when I started this, but have been tinkering for a while and I'm getting a bit nervious that it's running low. Is there any way to try charge given stock equipment?

Good news! The phone is un-bricked.
Swapping out the PC that was running Odin seemed to to the trick. Funny thing is.. I used pretty much all the same things.
Odin 1.85
Original USB Cable
MD5 checked ROM
Anyway, thanks again for everyone's help. Now that I know I can get back from a bricked state, I can with confidence go try out some new ROMs.

Great news.
BTW earlier you were using ODIN to flash the EK02 Modem, Kernel, and ROM.
In your most recent log, you were flashing the EK02 ROM only.
Mentioning it in case that wasn't intentional.

sfhub said:
BTW earlier you were using ODIN to flash the EK02 Modem, Kernel, and ROM.
Click to expand...
Click to collapse
It actually was not intentional. Thanks for bringing that up.
And actually since I've restored back to factory, it seems as if I'm have a lot of problems with reception. Think that may be the cause?
Does order matter about what goes on first?

The order doesn't really matter as much as whether the combination you are ending up with will work well with each other.

Here's where things got a bit more interesting for me. I used odin to re-flash the rom, kernal, and modem. Still had crappy signal. I can basically only roam. That's not normal for me.
I figured I'd try the oneclick method in sfhub's sig. This time I'll let it wipe my user data. Fresh start to the phone. No custom apps, not rooted.. But still the same problem.
I called Sprint to check out what's the deal with roaming on my plan.
I dial *2 and get the following message:
"We're sorry, use of this feature is not currently available. Please call cricket customer support at 611"
Cricket? Why is this configured to call cricket? Isn't this supposed to be a sprint ROM?

schlapppy said:
Here's where things got a bit more interesting for me. I used odin to re-flash the rom, kernal, and modem. Still had crappy signal. I can basically only roam. That's not normal for me.
I figured I'd try the oneclick method in sfhub's sig. This time I'll let it wipe my user data. Fresh start to the phone. No custom apps, not rooted.. But still the same problem.
I called Sprint to check out what's the deal with roaming on my plan.
I dial *2 and get the following message:
"We're sorry, use of this feature is not currently available. Please call cricket customer support at 611"
Cricket? Why is this configured to call cricket? Isn't this supposed to be a sprint ROM?
Click to expand...
Click to collapse
*2 doesn't always work when you are roaming.
*If* you can get on a Sprint native network, the first thing I would try is "Update Profile" and "Update PRL" from menu->settings->about phone->system updates
If that doesn't work, I would try a ##786# reset from the dialer. I figure you don't have that much user data to save right now and probably stuff is backed up. You'll need your MSL, so in adb shell type "getprop ril.MSL" It *IS* case sensitive. If you try to do it in android terminal, the swype keyboard may auto-capitalize "I" in "rIl" and it isn't ovious it did so on the small screen.
##786# will reset your NVRAM and Sprint login info and cause the phone to reprovision.
Now be forewarned, that if you actually have a tower down and that is why you are on cricket, then your phone will *NOT* be able to reprovision. It needs to be on a Sprint native network to reprovision using the automated OTA method. Provisioning voice by hand is ok, but data is a little more annoying.
Anyway, I wouldn't spend too much time trying to figure out if this is a ROM issue. If it was, there would likely be far more complaints. It could easily be Sprint doing maintenance work on some towers near you.
If you are not getting on the Sprint network it is some sort of tower, signal, or provisioning issue. Now if you couldn't get on any cell network, even cricket, then that might be something on your phone.

sfhub, you a rock star. Thanks for your help. All is good now, and I'm back up with full signal.

Does anyone know of a way to revert back to stock using a Mac? I've searched the forums and google but have not found anything helpful. thanks

Use heimdall.

Let me try again since im kind of new. Does anyone know of a step by step to revert back to stock on a mac computer? Thanks everyone.

So I restarted my phone today and it wont go past the "android" logo before shutting off. If anyone is interested in helping me out on a mac, I would be willing to donate to you via paypal. I've just decided I would rather get my phone back to stock. I originally rooted via heimdall and I can currently get into CWM. Thanks guys

fredygonz said:
Let me try again since im kind of new. Does anyone know of a step by step to revert back to stock on a mac computer? Thanks everyone.
Click to expand...
Click to collapse
Do what sfhub said...get Heimdall. I haven't used it myself but those with Macs have had much success with it
Sent from my SPH-D710 using Tapatalk

Thanks John. I have heimdall. But I can't figure out how to root it back to stock using heimdall.

Samsung Galaxy S3 SGH-T999N Stuck on BootScreen

I posted my problem on androidcentral earlier today, I'm not progressing anywhere with my situation, I've copied my original posts with some edits here. If you need more information for helping me to resolve this dilemma, ask right away.
I'm in deep****. It started when i tried changing the fonts on my galaxy s3, simple install and reboot. Now when it rebooted it got stuck on the Metro PCS logo screen, I turned it off and turned it on again, and same problem. Then I tried flashing my g3 with odin it said pass, but now my model number has disappeared from the samsung boot screen and it still has the same problem prior; before it said Samsung Galaxy S3 SGH-T999N, but now it just shows Samsung Galaxy S3. Prior to all this my phone was already rooted. I'm a noob and I need help. All the details I remember about my phone is that the carrier is Metro PCS, the model is SGH-T999N (a t-mobile variant) and the OS was Jellybean 4.1.2.
Thankyou for reading, please reply soon its urgent.
*Extra notes, I tried booting it up into recovery mode it shows splash screen for a brief moment and then completely turns off. It is still able to go in to download mode, also when the phone is completely off and charged in, the battery charging animation is still normal/unchanged before all this happened.
-I've also tried using GS3 Toolkit, but I really don't know which build to use for my predicament, I've tried using the t-mobile SGH-T999 builds but theyre not working at all, just adding to my flashcount.
*Additional notes, when in download mode the information at the top left corner reads as:
ODIN MODE
PRODUCT NAME: SGH-T999N
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CUSTOM BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
tookutz said:
It failed to flash, I tried 3 times, here is the log of the 3rd/last attempt with that .tar file.
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDLJA_T999TMBDLJA_T999UVDLJA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
What else can I try? I doubt I'll be able to replace it with the warranty by now.
Click to expand...
Click to collapse
tookutz said:
Isn't that only on verizon's variants? I don't remember anything having to do with the bootloader, but I did successfully root my phone, so maybe I did, I'm not completely sure.
*Edit, Could you also give me a detailed guide as to how I could reset it with Kies? I'm not sure if it will work or not, because in my first postt, if it wasn't clear, I think I used the wrong .tar which made the model number under the samsung boot screen, disappear.
Click to expand...
Click to collapse
tookutz said:
I'm still stuck on the KIES method, I removed my sd card and found that my titaniumbackup update.zip, also I found the folder where my KIES backup files are that I made on kies a few days ago. Please continue helping me.
*Edit, okay I found my IMEI through the google dashboard, it was also the same number on the sticker under the battery. FML. Okay so when doing the Kies method it asks me for the model name, I enter SGH-T999N, now it prompts to ask me for the s/n, I copy and paste in the IMEI, but it says that it is incorrect. PLEASE HELP
Click to expand...
Click to collapse

If you are still able to get into Download mode, flash back to stock using @DocHoliday77 guide here: http://forum.xda-developers.com/showthread.php?t=2308514

No, sorry man but I'm pretty sure you bricked it. There us no firmware available for the T999N yet. You flashed T999 firmware.
In the future, if you get stuck during boot, factory reset will almost always fix it.
I have an image that I've got to pass to KAsp3rd that he can hopefully use to create a debrick method for the T999N. I'll send it to him in a few min. But once he's got it ready, it should fix you up....hopefully! I've also just received the files I need to create a stock Rom and Odin firmware for it. I'll try to get it all together and will let you know.
In the meantime check his thread, it's stickied in development.
Sent from my SGH-T999L using Tapatalk 4

Actually, @KAsp3rd already has the T999N image. Mustve forgot or missed it or something! Anyway, he may already have the other partitions that were flashed, and if so he should already have everything you need to get working again. If not, I'll have to look, but I might have a copy of all the ones you will need.

@tookutz if you can jump over http://forum.xda-developers.com/showthread.php?t=2439367 and see if we can give you a hand. There is a link to the irc channel that I'm usually in as well in the OP of that thread..

KAsp3rd said:
@tookutz if you can jump over http://forum.xda-developers.com/showthread.php?t=2439367 and see if we can give you a hand. There is a link to the irc channel that I'm usually in as well in the OP of that thread..
Click to expand...
Click to collapse
I feel like this this morning is christmas lol, I wake up and find such helpful replies, I'll give it a look thankyou so much everyone
*Edit, for the list of requirements do I need both the Linux Live Disc and the Linux Virtual Machine? Or is it either or? Also I have an 8gb Micro SD would that suffice? or does it absolutely have to be 16gb+?

tookutz said:
I feel like this this morning is christmas lol, I wake up and find such helpful replies, I'll give it a look thankyou so much everyone
*Edit, for the list of requirements do I need both the Linux Live Disc and the Linux Virtual Machine? Or is it either or? Also I have an 8gb Micro SD would that suffice? or does it absolutely have to be 16gb+?
Click to expand...
Click to collapse
It is either or on the Linux and it has to be 16G or greater. We have tested on 4 and 8gb and they both failed

KAsp3rd said:
It is either or on the Linux and it has to be 16G or greater. We have tested on 4 and 8gb and they both failed
Click to expand...
Click to collapse
Okay so just to be clear, cause I always jump to conclusions and get confused x.x, I can run a Linux Virtual Machine on my Windows 7 laptop? And I'll stop by staples later today and get a new micro sd.

tookutz said:
Okay so just to be clear, cause I always jump to conclusions and get confused x.x, I can run a Linux Virtual Machine on my Windows 7 laptop? And I'll stop by staples later today and get a new micro sd.
Click to expand...
Click to collapse
You can run a VM or boot to a "Live" version that has a Persistence mode on a USB Stick. UNETBootin or LiLi (LinuxLive USB) both work great for this making the Live USB images of major distros, such as Ubuntu (and variants).

tookutz said:
Okay so just to be clear, cause I always jump to conclusions and get confused x.x, I can run a Linux Virtual Machine on my Windows 7 laptop? And I'll stop by staples later today and get a new micro sd.
Click to expand...
Click to collapse
Yes that is correct. If you watch the video in my thread I did the linux portion in a VM. There apparently are windows tools out there for properly managing .img files however I've not used any so therefore cannot recommend any.

KAsp3rd said:
Yes that is correct. If you watch the video in my thread I did the linux portion in a VM. There apparently are windows tools out there for properly managing .img files however I've not used any so therefore cannot recommend any.
Click to expand...
Click to collapse
I'm in class right now, so all I can do is read and re-read this thread lol, can't wait to give it a try x-x

tookutz said:
I'm in class right now, so all I can do is read and re-read this thread lol, can't wait to give it a try x-x
Click to expand...
Click to collapse
If you need any help with it you can join me in IRC or ask in the thread with the walkthrough (if you have more then 10 posts) and if not me someone else should be able to help you

KAsp3rd said:
If you need any help with it you can join me in IRC or ask in the thread with the walkthrough (if you have more then 10 posts) and if not me someone else should be able to help you
Click to expand...
Click to collapse
KK, this will be my 10th post lol, I joined your IRC I think. Im in the #teambuild

Ok, I guess I might be jumping in between conversations but I guess I need help with almost the same thing that happened with OP.
http://forum.xda-developers.com/showthread.php?t=2467692
I didn't try to root it yet, though i would love to, and I am new to a few jargon here.
Please help me out guys.. @KAsp3rd: you mentioned you had a forum to debrick or unbrick the phone. I am not sure whether I bricked my phone or not, but I would like to give it a read at least. Can you please mention the link here. Thanks.
Also, I trying the recovery mode (Home+volume up+power) but it doesn't come up. It just vibrates and the screen remains blank.
I try the download mode (Home+volume down+power) and it shows up with the option to continue to cancel.
I think I will add this info in my original post as well.
Please see if any of you could help me with it.
Thanks.

shanxthechashmich said:
Ok, I guess I might be jumping in between conversations but I guess I need help with almost the same thing that happened with OP.
http://forum.xda-developers.com/showthread.php?t=2467692
I didn't try to root it yet, though i would love to, and I am new to a few jargon here.
Please help me out guys.. @KAsp3rd: you mentioned you had a forum to debrick or unbrick the phone. I am not sure whether I bricked my phone or not, but I would like to give it a read at least. Can you please mention the link here. Thanks.
Also, I trying the recovery mode (Home+volume up+power) but it doesn't come up. It just vibrates and the screen remains blank.
I try the download mode (Home+volume down+power) and it shows up with the option to continue to cancel.
I think I will add this info in my original post as well.
Please see if any of you could help me with it.
Thanks.
Click to expand...
Click to collapse
Can you post exactly the link that you flashed on your phone? Sounds like you might have done the same thing that the OP did and flashed a bad kernel

t999N
Ive apparently flashed T999L firmware to my gfs T999N I just got her and am reduced to edge, everything else is working great but I've hit a wall here and want to either flash back to stock or fix the issue. Carrier is Metro.
I used root66 method for the T999L described in this thread
http://forum.xda-developers.com/showthread.php?p=43772039&highlight=t999n#post43772039
and flashed this file
http://sourceforge.net/projects/d2ltetmo/files/Use In Odin/MB7system.tar.md5.7z/download
From what I now gather I shouldn't have done this and now cannot find a way to get back to stock.
I found this in my searches but I don't know how / if I can use the files to restore,
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SGH-T999N
Please excuse my noobness. Any help would be uber appreciated.
Thanks.

mrrexsocks said:
Ive apparently flashed T999L firmware to my gfs T999N I just got her and am reduced to edge, everything else is working great but I've hit a wall here and want to either flash back to stock or fix the issue. Carrier is Metro.
I used root66 method for the T999L described in this thread
http://forum.xda-developers.com/showthread.php?p=43772039&highlight=t999n#post43772039
and flashed this file
http://sourceforge.net/projects/d2ltetmo/files/Use In Odin/MB7system.tar.md5.7z/download
From what I now gather I shouldn't have done this and now cannot find a way to get back to stock.
I found this in my searches but I don't know how / if I can use the files to restore,
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SGH-T999N
Please excuse my noobness. Any help would be uber appreciated.
Thanks.
Click to expand...
Click to collapse
Quick bit of advice....only post in one thread. When people repost their issue in multiple threads it makes it difficult to keep up with what's been done, what's been asked/answered, etc.
And The last link you posted is just the kernel source, nothing more. It won't help.
Sent from my SGH-T999V using Tapatalk 4

KAsp3rd said:
Yes that is correct. If you watch the video in my thread I did the linux portion in a VM. There apparently are windows tools out there for properly managing .img files however I've not used any so therefore cannot recommend any.
Click to expand...
Click to collapse
Can you please send me galaxy s3 T999N image

[Q] HELP! Soft Bricked T889 Note 2 missing pit file

here is my situation:
my phone was rooted, i unrooted it then realized i forgot to remove the custom boot animation file i had for the phone so i attempted to reroot (followed a stupid youtube video) but accidentally used the wrong root file for my phone. using odin, it failed and i tried rebooting the phone but it says to connect to kies and try to restore it, but it didn't work. then i had a friend look at it (they rooted the phone for me to begin with) and they said my phone was missing the pit file and nothing she did worked. she said it kept on mapping? i'm not too familiar with it but she says my phone was soft bricked. i was hoping maybe someone has some knowledge on how to help me fix my situation? thanks!
youtube video i followed....
How to Root your Samsung Galaxy Note 2
this is a log from odin below
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T889UVBMD1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

Look up Skips Note 2 Tool Kit, install it, run it and your but will be saved! And all automatically! Definitely the best tool I ever saw. Doesn't matter what you are missing or how you screwed up. It's like Prego. It's in there. Then after you OMG I'm cured, imagine what the pro version can do. Believe me, best 10$ I ever spent. I won't even wish you good luck. Just get it and follow the bouncing ball. Cya
Sent from my SGH-T889 using XDA Premium 4 mobile app

darkmanmd said:
Look up Skips Note 2 Tool Kit, install it, run it and your but will be saved! And all automatically! Definitely the best tool I ever saw. Doesn't matter what you are missing or how you screwed up. It's like Prego. It's in there. Then after you OMG I'm cured, imagine what the pro version can do. Believe me, best 10$ I ever spent. I won't even wish you good luck. Just get it and follow the bouncing ball. Cya
Sent from my SGH-T889 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Guy with 5 posts selling software and promising miraculous results...
Sounds legit.
Hastily spouted for your befuddlement

My Note 2 Has Space Herpes
Coug76 said:
Guy with 5 posts selling software and promising miraculous results...
Sounds legit.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Not selling just suggesting a solution that worked for me..... and crediting where credit is due Mr. Cougar. I was pants down six ways from Sunday and found out that Kies wasn't worth a hoot. Crap, I'm knocked :=/ I just knew I had just crash tested and burned....my very first phone. God bless twrp, I erased and formatted the WHOLE tamale. (Note to self: Maybe smart phones are a bit beyond the parameters of my engineering envelop. :-/ Self, you still have those Hawaiian Punch cans and some cat gut layin around? That concept was right up your alley pal)..but I do digress...
After a good cry, I remembered Skips Magic Note 2 Toolkit.
Heck it was already trashed what else could go wrong. I sucked one in and fired Skips up. Crossed my toes, answered two Q's; had to guess on the third and for gods sakes, Coug... May I call ya Coug? Cool. I pushed the red button. The next thing I know we drop into low. Drivers are loading, the phone squatted down, my computer started smoking and making odd noises. Blink....automatic download factory reset mode happened, three different backups; CWM, TWRP and Philz whipped by and auto installed. The phone started blinking, the room turned black, I stood up so I could stand back.
Then it went Plink, auto reboot, flashed into umm I dunno, maybe fast boot mode..(breathe). Odin popped open and sucked in some file. Things went green after a while, the phone spun around; rebooted again....and then, there it was, Samsung singing that same old Song!!!
Just call me Lazarus dude! It was back and downloading updates by air. And better news yet, I was none the worse for the wear! No Spoof..well perhaps a bit of embellishment here and there..but not that much I swear! The thing's not a toolkit it's AhhhLIVE..and fortunately, so is my phone.....go figure....
Mr. Cougar, that's my story and I'm holding tight to it. There was a bit more. Since it was so neat the first time around, I got cocky and bit it again :=/ However, I regrouped and turned Pro (lmao) But rather than tax you further, I'll save that rubbish for later..
Mr. Cougar, I know that you know how inexperienced I am and how awestruck...nah you can't know but I truly am as I watch and read with great fascination as XDA morphs science fiction into science fact every day. I must tell you Sir, this place really is a treasure!
Plus Bonus! You gave me a grin without knowing...on second thought, you probably did ) Mayhaps I shall return the favor some day....and yes I am still befuddled...but happily so.
Thanks for the shout Mr. Cougar.
dm out~

Thanks for the laugh. I needed that this morning.
Hastily spouted for your befuddlement

I can only go on download mode on my note 2 and i've tried to use the toolkit but it only works through ADB.Do you have any other suggestions? Also i've tried to use odin but i get the missing pit errror message.

I'm interested in knowing how to use the toolkit also
Androidfan253 said:
I can only go on download mode on my note 2 and i've tried to use the toolkit but it only works through ADB.Do you have any other suggestions? Also i've tried to use odin but i get the missing pit errror message.
Click to expand...
Click to collapse
I've tried the full version on my softbricked t889 and it did not work. Neither does Odin. Everything I've read says my phone is a softbrick because it can go into download mode but that's all it does. My phone doesn't loop and stuff like others it has these white noise and colored lines all across it when i boot it regular. Please someone help mmy phone has been broke since the beginning of this year.

This looks like a hardware issue(possibly emmc) but you can always try different versions of ODIN's, a different USB cable or verify USB drivers on your system.

Can't Flash to Stock. Memory Error.

Hi again guys. Been a while. As everyone always says on here, I apologize if this has already been covered, but I looked around and couldn't find a resolution.
T-Mobile Samsung Galaxy s4 (obviously). SGH-M919
Android version 4.2.2 I believe. It wasn't updated to kit-kat or anything current bc I rooted it the day I bought it 2 years ago.
The problem was created when I was attempting to move apps from internal memory to my sdcard.
The best method I found online used an app called FolderMount.
When I opened the app it stated that a patch was necessary in order for it to work...which "succeeded"....to brick my phone.
Once I exited the app, my phone didn't recognize any files that were saved or have the ability to open any Samsung or Google apps whatsoever. They all criticaled. Even Gallery wouldn't load. Also, Swiftkey no longer found language packs/had the ability to download new packs.
My Computer recognized the device still, but it only showed a few MB of storage and an empty SD card.
I tried restoring to factory conditions 3x. It removed everything, but still failed to recognized the internal memory and still wouldn't run the google/samsung apps.
At that point I tried to flash back to stock with Odin. Which I had done initially 2 years ago when I was rooting phone.
Now I'm stuck at an error screen that reads : Firmware upgrade encountered and issue. Please select recovery mode in Kies & try again.
I tried Kies. The Kies 3.0 doesn't support the Galaxy S4 and the old version won't connect with my device. I was going to attempt their emergency firmware recovery wizard.
Please keep in mind that I have googled/youtubed every option I could find and have had no success. I'm not just a person who put 30 seconds of research into this and then decided to complain on a forum without putting some time into fixing this issue.
I'm stuck and have no idea what to do at this point. It's hard to find a solution for a phone that is virtually considered old tech/obsolete.
Any help is appreciated. I have spent the entire day on this and am pretty depressed about it. My only optimism is that I know some people on this forum know what they are talking about The workweek is approaching and I need to have my phone operational.
Thanks!
-Garrett

Have you tried contacting the Foldermount developers for any help or feedback?
What folders where you moving?
Can you get to settings and try a factory reset?
Pp.

I have not contacted the developers (as the problem happened this morning) and I couldn't use my phone to even find them. I guess I could look them up on my PC. And no I can't go to settings. I can't get to any different screen other than the error message that I have. I turn my phone on and it immediately goes to this: http://postimg.org/image/8he6jagx3/
That's literally the ONLY screen I can access. I can't get to the download boot screen or safe mode with the button shortcuts. No idea what to do, bc the phone isn't broken...It's not a hardware issue. It's a firmware problem that a lot of ppl have had, but I can't find a solution that actually works. If anyone has any ideas, I'm open to try anything
Here is a link to the app: https://play.google.com/store/apps/details?id=com.devasque.fmount&hl=en
(Obvious....but I would recommend that no one try it out, or you might end up where I am.)
EDIT: I posted a review to the developers. Several people had the exact same problem. I will post their reviews below:
Athanasios Mamarelis March 24, 2015
Fail After patching and reboot my phone stopped woking...is there any way to unpatch?
Tomasz A. Kawecki
Serious problem with in-app purchase. I bought it a few version ago. Now, it says it cannot connect to G.Play so no premium features are available. Asked dev to repair it. No answer.
idris oulmane January 3, 2015
Horrible Application I'll give it -00 I setup this horrible application on my S4 and when I reboot it it stuck on the Samsung splash screen logo, My galaxy S4 won't start, I tried all the solutions I found on the web but nothing work, even factory reset!, Thank you for this ****ing application.
Akram Hossain Rana February 10, 2015
Its change my internal storage path After installing this **** its remove all of my data under internal storage , and change my internal storage path now my internal storage show 0kb size. realy sucks.
Tanvir Shahriar February 21, 2015
bricked my sd card I don't why I lost my all file from sd..
Faizan Zafar
DO NOT DOWNLOAD!!! It deleted some important files in sdcard and did not do what it was made for.
Does this shed any light on a potential solution?
By the way, here is a post about FolderMount from this site: http://forum.xda-developers.com/showthread.php?t=2192122
That's actually how I found it initially.

Suspect that some important system ui files got moved from folders that should not had been messed with.
While on firmware update screen try connecting with Odin running, it should show up in Odin, flash stock firmware.
Make sure you have a current Odin like 3.07 or higher.
Pp.

PanchoPlanet said:
Suspect that some important system ui files got moved from folders that should not had been messed with.
While on firmware update screen try connecting with Odin running, it should show up in Odin, flash stock firmware.
Make sure you have a current Odin like 3.07 or higher.
Pp.
Click to expand...
Click to collapse
That is what I've been trying to do since that error screen popped up.
I'm using Odin 3.07. If I can't get the phone into Download Mode it won't work.
It fails every time I've tried. I don't even have an idea as for what to try next.

InsomniacoreDSPS said:
That is what I've been trying to do since that error screen popped up.
I'm using Odin 3.07. If I can't get the phone into Download Mode it won't work.
It fails every time I've tried. I don't even have an idea as for what to try next.[/QUOTE
May sound stupid but did you try to power the device off completly then hold vol down then plug into computer. With Odin running of course. Also try Odin 3.09, prolly won't make a differnece but its the one ive been using and it can't hurt at this point. Good luck.
Click to expand...
Click to collapse

lordodin912 said:
InsomniacoreDSPS said:
That is what I've been trying to do since that error screen popped up.
I'm using Odin 3.07. If I can't get the phone into Download Mode it won't work.
It fails every time I've tried. I don't even have an idea as for what to try next.[/QUOTE
May sound stupid but did you try to power the device off completly then hold vol down then plug into computer. With Odin running of course. Also try Odin 3.09, prolly won't make a differnece but its the one ive been using and it can't hurt at this point. Good luck.
Click to expand...
Click to collapse
I cannot believe it. Thank you so much...I'm not out of the woods yet, but that successfully got me into download mode. Odin still fails to flash...hmmm. Are there some settings to tweak or something? Any chance at a solution?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
Click to expand...
Click to collapse
Click to expand...
Click to collapse

InsomniacoreDSPS said:
lordodin912 said:
I cannot believe it. Thank you so much...I'm not out of the woods yet, but that successfully got me into download mode. Odin still fails to flash...hmmm. Are there some settings to tweak or something? Any chance at a solution?
Click to expand...
Click to collapse
Mabey since your computer recognizes the device in download you could (google) manually "ADB/fastboot?" push system boot bootloader etc. Or try to Odin/adb a custom recovery then DL a 4.4.2 or newer custom/modded stock ROM and flash away. Just make sure you have proper modem etc.
Click to expand...
Click to collapse