Develop Bugs

Tried to Root - Now my phone stuck on Splash Screen :-(

Tried to install a rooted Kernal using Odin, The first Kernal did not install (froze), so I pulled the battery, and succesfully installed a different one. Now the phone freezes at the Galaxy SII screen with the Yellow Triangle. Tried re-installing several other Kernals, but to no avail.
Was able to boot into CWM 5, clear the phone, and then install Starbright ROM, but phone still freezes at the splashscreen.
I have tried everything I know to do.
Anyone got any recommendations, or am I bricked?

You are no where near bricked. I don't have a link but search the development section for a complete Rom but in .tar format and flash it to your phone via odin. Or find a complete stock Rom in .zip form and flash it via cwm.
Sent from my SPH-D710 using XDA Premium App

http://forum.xda-developers.com/showthread.php?t=1282415 follow directions here..

Thanks....I tried that method before, and odin kept freezing up when trying map the pit file.
Tried several others also.
I switched to a different windows machine and usb cable and it worked.
Guess Odin is just finicky like that!
Thank you for both of your help.....Tremendously.

dont need a pit file just check the reboot option

Basic Odin questions

Hi,
I have been rooting for a while with my evo 4g which is basically just recoveries & zip files.
Currently I have updated to Calk's ICS Beta 3 rom with modem FC05. I have read some stuff here & there that talk about having issues going from a ICS rom back to a GB nandroid.
I have installed Kies opened Odin, looked at the Wiki here:
http://forum.xda-developers.com/showthread.php?t=1274337
I just dont quite get in terms of flashing zips through odin. I keep reading people say to odin back to stock & then flash from there.
How do I do that? I looked at QB777's video on youtube, but it seems like PIT files arent used much at this point.
Any advice would be great.
Thanks,
Rich

Ok, basically when you Odin back to stock, it involves flashing a .tar ROM from the pda slot in desktop Odin and not zip file like you would in CWM. Once you restore back to stock, you can find a .tar recovery, I personally use rogue which will allow you to have cwm-based recovery for flashing zips. All the links should be in development. Let me know if you still need help
Edit-what Odin does is it allows you to flash Roms, kernels, moderns, etc even if you don't have a custom recovery, provided that they are in the correct format, like .tar extension
Sent from my SPH-D710 using xda premium

so when i flash a tar, I go into download mode, open odin, point it to a stock rooted tar file that has CWR & I am back to stock ready to flash to something else?
Can you help me find those files? A stock rooted, CWR should do the trick.

RichTJ99 said:
so when i flash a tar, I go into download mode, open odin, point it to a stock rooted tar file that has CWR & I am back to stock ready to flash to something else?
Can you help me find those files? A stock rooted, CWR should do the trick.
Click to expand...
Click to collapse
Ok, so you go into a download mode on your phone, open Odin, plug in your USB cord, ODIN should recognize your phone provided you installed the right drivers. You're good if you get the yellow box that says 0 com, something something. The only box that should be checked is Auto Reboot in Odin.
The easiest way that I've been going back and forth between GB and ICS is to install the rooted EL29 .tar version here
http://little-melon.com/sfhub/SPH-D710.EL29_CL852097_ROOTED-sfx.exe
You would need to extract the file until you get a folder with tar.md5 name. Example of the file I provided would be SPH-D710.EL29_CL852097_ROOTED_PDA.tar.md5 once you unzip it. This is the file you would put on the PDA slot of your desktop Odin.
Once you do this, Odin will start flashing and be done in like 1-2 minutes and auto reboot. Do not do anything to shut down, unplug, or mess with the device while Odin is flashing or you may end up bricking it. Once your phone reboots you will be rooted and stock based with EL 29 modem and kernel, which is the latest official Sprint OTA. If you want to get a recovery after this,you would need to go back into Odin and flash a kernel that has a recovery baked in. Like I said I use Rogue and the link would be here for Rogue Stock EL29-
http://goo-inside.me/kernels/TeamRo.../rogue_ET-recoveryonly-1.1.4-rc0-odin.tar.md5
Flashing this in Odin you will get CWM-based recovery and can start backing up, flashing different ROMS.
Hope this helps.

This is very helpful. I am stuck at the SGS2 boot screen after flashing MIJJs Goodness 1.8, can't boot in to recovery, only download mode. How do I fix this?

thefoss said:
This is very helpful. I am stuck at the SGS2 boot screen after flashing MIJJs Goodness 1.8, can't boot in to recovery, only download mode. How do I fix this?
Click to expand...
Click to collapse
Flash a recovery in download mode that I linked. It's rogue recovery
Sent from my SPH-D710 using xda premium

Just to confirm, using the files you had here, I open odin in download mode, choose PDA (check the check box) point it to the tar.md5 file, hit start & wait a few minutes until it auto reboots?
How do I flash the recovery? Is it also the PDA?
I have been flashing modems in CWR, not odin & I just want to make sure that recovery or rom itself, just PDA & nothing else checked (but PDA)?
stargaterules said:
Ok, so you go into a download mode on your phone, open Odin, plug in your USB cord, ODIN should recognize your phone provided you installed the right drivers. You're good if you get the yellow box that says 0 com, something something. The only box that should be checked is Auto Reboot in Odin.
The easiest way that I've been going back and forth between GB and ICS is to install the rooted EL29 .tar version here
http://little-melon.com/sfhub/SPH-D710.EL29_CL852097_ROOTED-sfx.exe
You would need to extract the file until you get a folder with tar.md5 name. Example of the file I provided would be SPH-D710.EL29_CL852097_ROOTED_PDA.tar.md5 once you unzip it. This is the file you would put on the PDA slot of your desktop Odin.
Once you do this, Odin will start flashing and be done in like 1-2 minutes and auto reboot. Do not do anything to shut down, unplug, or mess with the device while Odin is flashing or you may end up bricking it. Once your phone reboots you will be rooted and stock based with EL 29 modem and kernel, which is the latest official Sprint OTA. If you want to get a recovery after this,you would need to go back into Odin and flash a kernel that has a recovery baked in. Like I said I use Rogue and the link would be here for Rogue Stock EL29-
http://goo-inside.me/kernels/TeamRo.../rogue_ET-recoveryonly-1.1.4-rc0-odin.tar.md5
Flashing this in Odin you will get CWM-based recovery and can start backing up, flashing different ROMS.
Hope this helps.
Click to expand...
Click to collapse

Reverting back to GB ROM
I recently switched back from ICS to GB and did not have any problems with the change back. I simply went into my SD card manually took everything off except my chaulkins format all and my wifi tether hack. I then went into recovery mode and did a wipe all. Then went to zip files, ran the format all, then did an install of the new ROM and it works great!

[Q] Mobile Odin and FC07 modem

Hey all,
I just loaded up FC07 TAR from Calk's thread into Mobile Odin and hit flash firmware. It seems to be stuck on "Flashing.... Rebooting into recovery" for about 3-4 minutes now. (seems frozen)
Is this supposed to happen right away? I'm rather new using Mobile Odin and don't want to prematurely battery pull/screw something up.
Thanks in advance.

Maybe a bad download? I've been using CWM to flash modems, no problems here.
Sent from my Galaxy S II, AOKP style.

Still stuck on this screen. I'm tempted to pull the battery but am not sure

So,
I ended up pulling the battery and booted into recovery manually. The process seemed to have finished but I'm still on my old modem according to "About phone."
Sigh

Does anyone have any advice with flashing modems in Mobile Odin?

b0ricua said:
Does anyone have any advice with flashing modems in Mobile Odin?
Click to expand...
Click to collapse
Yeah I have advice ... it doesn't work on our phone.
I've tried flashing both modem.bin files (pulled from a ZIP) and modem.tar files, and I haven't been able to get any of them to flash. Mobile Odin goes through the process that seems successful, but upon reboot the baseband doesn't change. Also, the modem flash happens way too fast, which indicates that it didn't do anything.
Chainfire knows about it. For now, you'll need to use CWM or PC Odin to flash your modem.

Thanks man! That's the answer I was looking for!
PC Odin'd the modem successfully.

Dchibro said:
Yeah I have advice ... it doesn't work on our phone.
I've tried flashing both modem.bin files (pulled from a ZIP) and modem.tar files, and I haven't been able to get any of them to flash. Mobile Odin goes through the process that seems successful, but upon reboot the baseband doesn't change. Also, the modem flash happens way too fast, which indicates that it didn't do anything.
Chainfire knows about it. For now, you'll need to use CWM or PC Odin to flash your modem.
Click to expand...
Click to collapse
sir u r wrong i always flash the modem through mobile odin and i never had a problem seems like u either have the wrong file or its corrupted or u do not have root access.

[Q] AT&T bricked my S3 - Help please.

Ok the backround. about 5 days ago the software update started. All seemed ok but then I was getting reboots 4-5 times a day. Brought it to AT&T and they tried to reflash. After backing up info I signed the release form holding them not liable for bricking the phone. Asked the tech how many have bricked on him and he said none. Sorry I was his first...maybe. Screen asking for Kies program to repair. AT&T tech not allowed to use Kies. I downloaded Kies but no luck.
Got the bugger to go to the Boot screen of "Warning...a custom OS....". Then the "Downloading, do not turn of target" screen. It is stuck there or I should say I have left it there. Top of screen says Odin Mode (in red), Produce Name: SGH-I747, Current Binary: Samsung Official, Qualcomm SecureBoot: Enabled, Warranty Bit: 0, Bootloader Ap SWREV: 3.
I have downloaded Odin 3.09. I have the USB drivers installed. I want to restore last known version of AT&T android 4.2.2 or the upgrade 4.3 that didn't seem to take. I am not sure which version it was running before the crash. My wife's S3 is running 4.3.
What Next? Where do I get the file to upload to the phone? Thanks.

So your s3 was trying to upgrade from 4.1.2 or 4.3?

thenexusgeneration said:
So your s3 was trying to upgrade from 4.1.2 or 4.3?
Click to expand...
Click to collapse
Not sure. I think I checked the build version after the install and it read 4.2.2. Can't be absolutely certain when i saw that build number. Would make sense to check it after the install assuming the install happened at all. But again the wife and I bought the two S3's at the same time and hers is running 4.3.

If you got the ota a few days ago, and judging from the SWREV (Software Revision), you are currently on 4.4.2 firmware (NE4). This means you cannot flash older firmware on Odin (or any other way, OT it'll really brick). From now on you can only flash NE4 firmware.
You can, however, flash older roms.
If you haven't already, try factory resetting from recovery. (This will wipe all your data including the internal sdcard)
If that doesnt work, my only other suggestion is to flash TWRP via Odin, then boot TWRP recovery and flash the stock NE4 rom from enewman17.

DocHoliday77 said:
If you got the ota a few days ago, and judging from the SWREV (Software Revision), you are currently on 4.4.2 firmware (NE4). This means you cannot flash older firmware on Odin (or any other way, OT it'll really brick). From now on you can only flash NE4 firmware.
You can, however, flash older roms.
If you haven't already, try factory resetting from recovery. (This will wipe all your data including the internal sdcard)
If that doesnt work, my only other suggestion is to flash TWRP via Odin, then boot TWRP recovery and flash the stock NE4 rom from enewman17.
Click to expand...
Click to collapse
I can't get to the factory reset screen, only the warning screen before pressing volume up to load a custom OS. I'm confused....well on may levels but I digress. I thought ROM and firmware were the same thing.
Also the TWRP site has two files, same file I Assume, in different formats, md5 and tar. Are they the same file? Do I use one over the other? To flash TWRP using Odin what screen should I start with on the S3? thanks.

To boot recovery hold volume up, home and power. When it vibrates release power only.
A rom (as we use it here) is just the O/S on the /system partition and is usually flashed in recovery. They also include kernels most of the time. The firmware is this, and more. It includes images for multiple partitions. (aboot, sbl2, sbl3, tz, rpm, modem, recovery, boot, system, cache)
Around here you'll see a lot of folks refer to this as just the bootloaders, but they are talking about the base firmware. Sorry if I confuse anyone with that btw, I try to remember to call it the bootloaders, but am just used to using the term firmware.
As for flashing twrp from odin, it must be a .tar or .tar.md5. Both are used by odin. The .md5 extension just tells odin a hash value is included. It will then run an md5 checksum to verify the file about to be flashed is valid, or not corrupted. Either one will work, but the .tar.md5 is safer. If the download gets corrupted somehow, odin will catch it and refuse to flash.
When flashing anything in odin you need to be in Download mode.

DocHoliday77 said:
To boot recovery hold volume up, home and power. When it vibrates release power only.
A rom (as we use it here) is just the O/S on the /system partition and is usually flashed in recovery. They also include kernels most of the time. The firmware is this, and more. It includes images for multiple partitions. (aboot, sbl2, sbl3, tz, rpm, modem, recovery, boot, system, cache)
Around here you'll see a lot of folks refer to this as just the bootloaders, but they are talking about the base firmware. Sorry if I confuse anyone with that btw, I try to remember to call it the bootloaders, but am just used to using the term firmware.
As for flashing twrp from odin, it must be a .tar or .tar.md5. Both are used by odin. The .md5 extension just tells odin a hash value is included. It will then run an md5 checksum to verify the file about to be flashed is valid, or not corrupted. Either one will work, but the .tar.md5 is safer. If the download gets corrupted somehow, odin will catch it and refuse to flash.
When flashing anything in odin you need to be in Download mode.
Click to expand...
Click to collapse
Thanks Doc, when I try the boot recovery hold volume up, home and power I get the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." message. If I use the hold volume down, home and power combo I get to the "Warning!! A custom Os can cause....." screen. If I press volume up it goes to the "Downloading...Do not turn off target!!" screen. If I press volume down it reboots to the "Kies" screen. Which screen mode should I be in when attempting to flash the TWRP file with Odin? thanks.
OK I tried to flash the TWRP file. Put S3 in download mode, Opened Odin, plugged in S3, Odin showed "added", tried to load the TWRP file into Odin but it freezes Odin. Non responsive Odin. Tried 4 times with and without plugging in phone. any clues?

Try downloading the file again. Could be a corrupted download. Also, what version of Odin are you using?
Oh, and kies interferes with Odin. Uninstall it and try odin again.

DocHoliday77 said:
Try downloading the file again. Could be a corrupted download. Also, what version of Odin are you using?
Oh, and kies interferes with Odin. Uninstall it and try odin again.[/QUOTE
Thanks I tried 3.09 first then 3.07. 3.09 hangs right away. 3.07 doesn't say "not responding" but nothing happens. Looks like it will but no. I wait for about 45 min. I will try everything from scratch. I did uninstall Kies with no help. Kies can't find the device - generic code 43.
Is it the Bootloader ap SWREV: 3 that indicates I need 4.4.2?
If its an older version such as 4.3 can i/should I still install 4.4.2?
Where do I find 4.4.2. Thanks for all your help because this is like finding a specific needle in a stack of needles without even fulling understanding what a needle is! God I miss DOS.
I've been doing all the above without sim or sd card installed. Does that make any difference.
Click to expand...
Click to collapse

IT's BACK ALIVE! Now what?
What happened? None of the .MD5 files would load and would just lock the Odin. Since I had nothing to loose I used a 2.6 version of the .tar file without the .MD5 check. It loaded fine, rebooted and there is my phone screen with all my apps and info. I'm afraid to even unplug it from the cable (silly I know). Checked the version and it reads 4.4.2., baseband version I747UCUFNE4, Kernel version 3.4.0-1514807, build number KOT49H.I171UCUFNE4, SE for Android status Enforcing SEPF_SAMSUNG-SGH-I747_4.4.2_0016.
Am I done? Is it safe to put back in service or should I do something else? thanks

Weird! Sounds like something on your system didn't like the md5sum. Never seen that before!
But if it appeared to flash ok, rebooted and it says PASS in Odin, you should be good to go.
First though, what exactly did you flash? Can you link to it? To my knowledge there is no NE4 firmware package available. Ive been trying to make one but it hasn't worked yet....

DocHoliday77 said:
Weird! Sounds like something on your system didn't like the md5sum. Never seen that before!
But if it appeared to flash ok, rebooted and it says PASS in Odin, you should be good to go.
First though, what exactly did you flash? Can you link to it? To my knowledge there is no NE4 firmware package available. Ive been trying to make one but it hasn't worked yet....
Click to expand...
Click to collapse
Just flashed the TWRP http://true-android.blogspot.com/2014/01/install-twrp-recovery-2631-on-at-galaxy.html. It passed it and phone rebooted to the normal reboot and my old screen. Weird? I do weird all the time. I used Odin 3.09. I have run it through some of its apps. I will wait 24 hours to see if it reboots by itself.

Cool, sounds like it should be ok then. Hopefully it'll make it through your testing period!

DocHoliday77 said:
Cool, sounds like it should be ok then. Hopefully it'll make it through your testing period!
Click to expand...
Click to collapse
Well it's functioning but we are back to the reboots 4-5 x a day. I can get to the recovery screen now. Anyone have a guess of my best next option?

Not sure, could be a faulty power switch though. Lots of these have been going bad in recent months, but it usually happens all the time, not just a few times a day.
Sent from my SGH-T999 using Tapatalk

Just a F/U. The reboot was getting to be a problem. Also had a problem with back up and restore apps. Found one that worked so I did a factory reset. All is good again. Love my S3 again. Still not happy with how AT&T handled the problem though.

Bricked L900. Doesn't boot. Odin fails 100% of the time. Stock recovery gives errors.

Hi there. A friend of mine gave me a bricked L900 stuck in the black "Galaxy Note II" screen. The first thing I did was to enter stock recovery, but a bunch of red error messages appeared (as pictured). Wiping data/factory reset didn't do anything. Entered Download mode without a problem and then tried to flash every single Odin firmware for the L900 found on the whole internet, but no matter what I flash, Odin ALWAYS fails. Also noticed that after an unsuccessful flash, still in download mode you can read in red: "sw rev check fail device 3 binary 2". Also, it is not recognized by Kies.
The previous owner said the phone bricked while receiving an OTA update. I have spent a whole week trying to fix this thing! I decided to ask for some help here before smashing it with a hammer.
Any help is much appreciated!

domenicostorino said:
Hi there. A friend of mine gave me a bricked L900 stuck in the black "Galaxy Note II" screen. The first thing I did was to enter stock recovery, but a bunch of red error messages appeared (as pictured). Wiping data/factory reset didn't do anything. Entered Download mode without a problem and then tried to flash every single Odin firmware for the L900 found on the whole internet, but no matter what I flash, Odin ALWAYS fails. Also noticed that after an unsuccessful flash, still in download mode you can read in red: "sw rev check fail device 3 binary 2". Also, it is not recognized by Kies.
The previous owner said the phone bricked while receiving an OTA update. I have spent a whole week trying to fix this thing! I decided to ask for some help here before smashing it with a hammer.
Any help is much appreciated!
Click to expand...
Click to collapse
I have something that should fix you right up. I have to find the file so it may take a while to get back to you. I am headed to bed now.
Sent from my XT1045 using XDA Premium 4 mobile app

I forgot to mention I already tried flashing a file named "fix.tar" that I found in one of these L900 unbrick threads, but sadly it didn't work (Failed to flash, like anything else). I hope you have different file. Thank you!

domenicostorino said:
I forgot to mention I already tried flashing a file named "fix.tar" that I found in one of these L900 unbrick threads, but sadly it didn't work (Failed to flash, like anything else). I hope you have different file. Thank you!
Click to expand...
Click to collapse
Yes I do. A quick question. Have you tried flashing just a custom recovery to start with?
Sent from my XT1045 using XDA Premium 4 mobile app

heres what you can do you can flash philz recovery in odin and download a custom rom (will take a while but worth) and flash the rom and shouldnt be bricked trust me i bricked the note 2 before but got a rom to fix it up

Yes I did. Tried flashing every custom recovery and they all fail.

domenicostorino said:
Yes I did. Tried flashing every custom recovery and they all fail.
Click to expand...
Click to collapse
Have you tried this http://forum.xda-developers.com/showthread.php?p=55712636
Sent from my XT1045 using XDA Premium 4 mobile app

I tried, but remember the phone doesn't let me flash anything via Odin. TWRP simply doesn't flash, it instantly fails.

domenicostorino said:
I tried, but remember the phone doesn't let me flash anything via Odin. TWRP simply doesn't flash, it instantly fails.
Click to expand...
Click to collapse
Have you tried using heimdall to flash? It is an odin link software that can be used on window, mac, and Linux.
Sent from my XT1045 using XDA Premium 4 mobile app

Trying now. I have downloaded Heimdall Suite 1.4. After installing the included drivers and opening the program, I'm not sure what to do. When I go to "load package" I am unable to pick any of the firmwares I have downloaded. They are not displayed in the window that opens to pick the file (and I am in the right folder). Heimdall is new territory for me! Any suggestion?

domenicostorino said:
Trying now. I have downloaded Heimdall Suite 1.4. After installing the included drivers and opening the program, I'm not sure what to do. When I go to "load package" I am unable to pick any of the firmwares I have downloaded. They are not displayed in the window that opens to pick the file (and I am in the right folder). Heimdall is new territory for me! Any suggestion?
Click to expand...
Click to collapse
You will need to extract the files and use the flash tab. Don't remember if a pit files is included in the tar.md5 package (fyi you might have to remove the .md5 to extract the files) bit if you need one let me know.
On the flash tab select your pit file then add a partition, then select the corresponding file. You will need to do this for every partition you want to flash. Once setup click on the start button.
Sent from my XT1045 using XDA Premium 4 mobile app

Thank you. I have extracted the files but Heimdall doesn't recognize them. It doesn't recognize any .tar or .md5 file. I am very familiar with file extensions, extracting, flashing software, etc... but this is the first time using Heimdall and I am very frustrated because I can't make it work. Any suggestion? Thanks again.

You give up on this yet domenicostorino? Looks like according to your images, you just need to odin with an included pit file. Lemme know, I have a pit that works for this device, had to fix one last week. Your images are showing no such directory, so that should fix you.
Edit: Grab the pit from here Use it with stock tar and flash via odin. That is the one I grabbed.

Hey! My Note has been collecting dust on the corner of my desk but I haven't given up on it yet! I would really apprecite if you can share that pit file and some steps. So far, EVERYTHING I've flashed with Odin just fails. Maybe that pit file is all I'm missing! Please help me bring that phone back to life!!

domenicostorino said:
Hey! My Note has been collecting dust on the corner of my desk but I haven't given up on it yet! I would really apprecite if you can share that pit file and some steps. So far, EVERYTHING I've flashed with Odin just fails. Maybe that pit file is all I'm missing! Please help me bring that phone back to life!!
Click to expand...
Click to collapse
Just grab that pit file I edited with, select it in the pit section of odin, it should check mark the repartion as well. At the same time grab the stock firmware tar. You are going to be doing everything just like you have been, just using a pit file and repartitioning at the same time. Good luck, just holler, I will be around most of today. I used this firmware with that pit. Firmware
If it doesn't boot, don't worry, enter recovery and see if it fixed the can not mount, I don't know which baseband you currenlty have, so that could keep it from booting. If that happens and mounts are fixed, then just grab the last firmware and flash it without the pit file. Here is the latest FIRMWARE.
Remember you flashing tar files, all three of them need to be extracted.

Thank you. I did everything exactly as you said but the pit file didn't do the trick. It failed right away again. Of couse when I enter recovery the same can't mount messages in red appear again.

domenicostorino said:
Thank you. I did everything exactly as you said but the pit file didn't do the trick. It failed right away again. Of couse when I enter recovery the same can't mount messages in red appear again.
Click to expand...
Click to collapse
Assuming you extracted the t0lte.zip to read t0lte.pit and placed in pit section of Odin with repartition checked, and extracted the rom to a .tar and place in the AP section then hit start. Should have worked or did for me anyway. Have you tried different usb cable as well as a different port on pc? <that can cause odin to fail. Also which Odin version are you using? I use 3.09 Odin. Wife's phone went on the blink last week because of a battery failure, nothing would mount after replacing battery. What I described is all I did, she is back up and running with latest stock and rooted now.

After looking at this again, according to the images on first post, you have the latest stock build NE2. I extracted the pit file from the wife's phone and compared to the other. They are the same. At this point I would just try one more time with the pit and the latest stock firmware. If that doesn't work then maybe it is just a bad eMMC.
Here is the extracted pit from wife's phone if you want to try it. View attachment L900_NE2.7z

I did try again many times using the pit file and latest NE2 firmware. I guess the eMMC is faulty. Thanks for your help anyway!

mattsm said:
Assuming you extracted the t0lte.zip to read t0lte.pit and placed in pit section of Odin with repartition checked, and extracted the rom to a .tar and place in the AP section then hit start. Should have worked or did for me anyway. Have you tried different usb cable as well as a different port on pc? <that can cause odin to fail. Also which Odin version are you using? I use 3.09 Odin. Wife's phone went on the blink last week because of a battery failure, nothing would mount after replacing battery. What I described is all I did, she is back up and running with latest stock and rooted now.
Click to expand...
Click to collapse
I'm having a similar issue. Phone was charging in the truck, came out to the Galaxy Note 2 boot screen with the green light on, once I unplugged it though, it just died, Any attempts after that and the screen goes fuzzy on me. I can only boot into downloader mode, but everything I've tried to flash via two different ODIN's so far fails almost immediately. http://forum.xda-developers.com/note-2-sprint/help/odd-semi-brick-t3082102 I'd really love some help sorting this out.
---------- Post added at 11:44 PM ---------- Previous post was at 11:40 PM ----------
domenicostorino said:
I did try again many times using the pit file and latest NE2 firmware. I guess the eMMC is faulty. Thanks for your help anyway!
Click to expand...
Click to collapse
I found this, but I can't even get into recovery - http://forum.xda-developers.com/showthread.php?t=1823918