Develop Bugs

[Q] Did I brick my SGH T889?

I am flashing this for my cousin. She woke me up out my sleep because she wanted her phone upgraded from 4.1.2 to 4.3 or kitkat. I downloaded a 4.3 ROM and didnt flash it correctly because Wifi nor data was working. It could be because I didnt flash the OTA first and/or didnt install the devil kernel.
Anyways I was walking her through how to restore the backup I made but she went into Download mode and here is when the problems started. i told her to battery pull and to go into recovery. There was already a backup ROM on her SD card, she flashed and it failed. Had her wipe twice and it failed again. Had her wipe again and restore and it failed. After 10 minutes of it failing I had her send me the phone.
I was unable to flash any ROM so i factory reset through recovery and still nothing. I then started flashing through ODIN the latest stock, deoxed stock, the MD4, I even flashed LJ1. Some of the ROMs will fail to flash and if a ROM does flash successfully I get no further than the Galaxy Note 2 screen.
So is this an indication that the phone is bricked or am I missing a step or two to finally get this phone to finally boot all the way up?

Bump
Sent from my SM-N900V using Tapatalk

Most likely the phone is on 4.3 bootloader which is why flashing 4.1.2 ROM via pc odin does not work.
You can either flash 4.1.x stock ROM via mobile odin pro or flash 4.3 stock ROM via pc odin.
Sent from my SGH-T889 using xda app-developers app

ciphercodes said:
Most likely the phone is on 4.3 bootloader which is why flashing 4.1.2 ROM via pc odin does not work.
You can either flash 4.1.x stock ROM via mobile odin pro or flash 4.3 stock ROM via pc odin.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Ok thanks didn't even think of that. I'm going to give that a shot
Sent from my SM-N900V using Tapatalk

Unable to flash stock ROM via PC odin
Hello
I am in almost the same situation as mo2002. I had original ROM that came with my note2 running android 4.3 then decided to try jedi master x2 also 4.3. After trying it out for a while I noticed poor battery performance and when phone was locked I had to press the menu button several times to see the screen. That was getting on my nerves. Yesterday my phone was booting up by itself. It did a couple times then got stuck with the samsung logo. Reboot again and again and the same stuff happened that's when I decided to flash stock rom from samsung.updates/device site using odin3 v3.09 however, I have not been successful. After it checks the md5 OK, it fails on the NAND write. Is it the case that the NAND memory is not unlocked? I am still able to boot into recovery though.
Thanks
G

gferreri said:
Hello
I am in almost the same situation as mo2002. I had original ROM that came with my note2 running android 4.3 then decided to try jedi master x2 also 4.3. After trying it out for a while I noticed poor battery performance and when phone was locked I had to press the menu button several times to see the screen. That was getting on my nerves. Yesterday my phone was booting up by itself. It did a couple times then got stuck with the samsung logo. Reboot again and again and the same stuff happened that's when I decided to flash stock rom from samsung.updates/device site using odin3 v3.09 however, I have not been successful. After it checks the md5 OK, it fails on the NAND write. Is it the case that the NAND memory is not unlocked? I am still able to boot into recovery though.
Thanks
G
Click to expand...
Click to collapse
Mines corrected itself so I can't give the exact instructions but I just kept flashing stock ROMS via odin but I used 3.07 I believe. Idk if that makes a difference but after X amount of attempts I power cycled (after it being stuck at the same galaxy note 3 screen) it booted successfully
Sent from my SM-N900V using Tapatalk

[Q] Softbricked my Tab 3 7

Hello there, I was trying to update my Tab's firmware to 4.2.2 following the instructions listed on a website I can't link to because I'm a new member. I found it by googling "update sm-t210 to 2.4.4". It's on a website called techbeasts.
I was using CWM recovery 6.0.4.7. I installed the first file, listed at the bottom of the page, the "Kernel.zip file". It installed using CWM just fine, it's a small file only about 6MB. The second file I tried to install, the "T110 on T210/210R.zip" file failed. It gave me something about 5 out 4 expected args and didn't work.
After this my tablet would not boot, it would show the Samsung Galaxy Tab 3 (not the animation) and then go black.
Next I tried to reflash using the 4.1.2 firmware from SamMobile using ODIN. This failed on the modem.bin. After this I couldn't boot in in recovery mode or ODIN mode. All I get is the, "Firmware upgrade encountered an issue...". ODIN still recognizes my tablet.
So I'm stuck. I've spent all night googling to no avail. Any help would be appreciated.

So I managed to use ODIN to get CWM reworking. But I've hit another brick wall. Now that I've got something to work with anyone have any ideas?

jstephens89 said:
So I managed to use ODIN to get CWM reworking. But I've hit another brick wall. Now that I've got something to work with anyone have any ideas?
Click to expand...
Click to collapse
Install the latest CWM (6.0.4.8) and it you should be able to flash the rom correctly.

Thanks gr8note,
So I did what you suggested, I installed 6.0.4.9 and then lo and behold, the error went away! The ROM installed with no errors. One issue is the device no longer registers with adb, but fortunately the ROM was already on my device. The device is still discoverable with ODIN on my PC.
My new problem is now I can't get it to boot in to anything but recovery or ODIN. Even if I just use the power button it boots to recovery. I just got home from work and will be searching for a solution, but any more help would be appreciated!
Thanks again.

jstephens89 said:
Thanks gr8note,
So I did what you suggested, I installed 6.0.4.9 and then lo and behold, the error went away! The ROM installed with no errors. One issue is the device no longer registers with adb, but fortunately the ROM was already on my device. The device is still discoverable with ODIN on my PC.
My new problem is now I can't get it to boot in to anything but recovery or ODIN. Even if I just use the power button it boots to recovery. I just got home from work and will be searching for a solution, but any more help would be appreciated!
Thanks again.
Click to expand...
Click to collapse
Flash the kernel again.
Sent from my SCH-I605

Hi gr8nole, thank you for getting back to me. I've seen your name all over these forums searching for a solution.
So I have reflashed the kernel I had originally downloaded, and also tried the blackhawk kernel I found on these forums for the sm-t210. It still will only boot to recovery. I have flashed several different recoveries to my tablet. I have tried two different ROMs - one from the website I mentioned above and the stock ROM from SamMobile - and it still will only boot to recovery or ODIN.
If you had a different kernel in mind a link would be greatly appreciated. Beyond that, any other advice you can give me?

hey hey hey
jstephens89 said:
Hi gr8nole, thank you for getting back to me. I've seen your name all over these forums searching for a solution.
So I have reflashed the kernel I had originally downloaded, and also tried the blackhawk kernel I found on these forums for the sm-t210. It still will only boot to recovery. I have flashed several different recoveries to my tablet. I have tried two different ROMs - one from the website I mentioned above and the stock ROM from SamMobile - and it still will only boot to recovery or ODIN.
If you had a different kernel in mind a link would be greatly appreciated. Beyond that, any other advice you can give me?
Click to expand...
Click to collapse
j,
a while back i read a warning about sammobile images being screwy and to avoid them.
this was the image i used when i first got my tab http://d-h.st/users/Jamison904?fld_id=21912 the 1.13 gb img not the dump
hope this helps
m

Hey thanks for replying.
I ended up doing a huge facepalm when I figured out my problem. I was attempting to install the stock ROM like the other ROMs...through a recovery. You can imagine my frustration when I finally realized it was not a normal ZIP but instead had to be extracted and ODIN'D.
Duh.

[Q] Note 2 bricked after 4.4 update, can't get into recovery

After trying to update to kit kat my note 2 will not get past the "note 2" splash screen. What sucks even worse is that I can't get into recovery to install a new rom. I've been searching tons of threads and whatnot across XDA and other websites but nothing has worked.
What I've tried:
-Flashing TWRP, CWM, Philz recoveries. Odin says they succeeded but I still can't get to any of them.
-Flashing srock roms downloaded from multiple sources. When I try this I get an error in odin, usually fails right after sboot.bin
-Using other versions of Odin, different usb's, etc. Same stuff happens no matter what.
-Kies, but it won't connect and says device is unsupported.
-Android toolkit, but i couldn't really do much with it in this state
-I even tried re-partitioning with some t0lte pit file. This really didn't change anything.
-I found an "mk4_recovery.tar" file in a thread on here. That finished and succeeded, but I still can't get anywhere, However I did notice that this changed the "current binary" on my phone from "custom" to "official samsung binary." I'm not sure if that is important or not.
I feel like I am running out of options and my phone is hard-bricked. You guys are my last hope and I'm hoping there's something you guys can help me with!! If you have anything I can try please let me know!!!

SCAND1UM said:
After trying to update to kit kat my note 2 will not get past the "note 2" splash screen. What sucks even worse is that I can't get into recovery to install a new rom. I've been searching tons of threads and whatnot across XDA and other websites but nothing has worked.
What I've tried:
-Flashing TWRP, CWM, Philz recoveries. Odin says they succeeded but I still can't get to any of them.
-Flashing srock roms downloaded from multiple sources. When I try this I get an error in odin, usually fails right after sboot.bin
-Using other versions of Odin, different usb's, etc. Same stuff happens no matter what.
-Kies, but it won't connect and says device is unsupported.
-Android toolkit, but i couldn't really do much with it in this state
-I even tried re-partitioning with some t0lte pit file. This really didn't change anything.
-I found an "mk4_recovery.tar" file in a thread on here. That finished and succeeded, but I still can't get anywhere, However I did notice that this changed the "current binary" on my phone from "custom" to "official samsung binary." I'm not sure if that is important or not.
I feel like I am running out of options and my phone is hard-bricked. You guys are my last hope and I'm hoping there's something you guys can help me with!! If you have anything I can try please let me know!!!
Click to expand...
Click to collapse
This happened to me today too. I didn't like the OTA 4.4 so I was trying to get a custom rom again. Thanks to jlmancuso he made the best solution here:
http://forum.xda-developers.com/showpost.php?p=53035491&postcount=287&nocache=1&z=4473536636214703
Simply download the attached file. It is BRICKED heaven! (worked for me.) and have your recovery (twrp, philz, cwm) file. And have Odin.
1) Extract all files fix / recovery (if haven't already) / and odin (again if haven't already)
2) Open Odin in PDA put in the "fix" file. BEFORE continuing, UNCHECK Auto Reboot. (HAS TO BE UNCHECKED)
3) Connect phone to computer
4) Once the file has finished (Odin will say pass) disconnect the phone.
DO NOT TAKE THE BATTERY OUT
5) Put it back in Recovery Mode (home / volume up / power )
Give it a minute and it will load a custom recovery.
If you were stuck at a bootloop you probably don't have a rom on your phone (cleaned and empty).
If so try flashing this in Odin as well (https://drive.google.com/file/d/0B0CWousOd0ntTHl2RmxPbHJWODQ/edit?usp=sharing}
When the custom recovery loads you can flash what you want.
Odin will not let you downgrade from NE2 to anything below (bootloader). I suggest flash over Philz and flash that way.
http://forum.xda-developers.com/showthread.php?t=2768847
Has a NE2 rooted already. Flash this and save a backup. YOU WILL NEED IT.
Once in the custom recovery that comes up I suggest to flash the M2 Stock with Count Reset. (back to complete stock) then can do what you want from there.
**If the custom recovery does not show up**
Repeat the steps above (Odin / add fix to PDA / Uncheck Auto Reboot / Connect Phone / start flash)
Then again DO NOT PULL BATTERY ... (once it shows pass) disconnect and reboot back in download mode ( home / volume down / power )
Flash over your recovery ... (do not pull battery) and try the Recovery Mode ... my first time I thought it was still stuck in bootloop so give it a second.

michael85tx said:
Once in the custom recovery that comes up I suggest to flash the M2 Stock with Count Reset. (back to complete stock) then can do what you want from there.
Click to expand...
Click to collapse
What a nightmare!
I odined back to stock MK4, did the 4.4.2 OTA last night. Then did the CF Auto Root via odin, installed custom recovery. The phone is currently on pageplus network. I started messing around, did the GSM Mod, then tried the international and domestic sim unlock procedures. The result was not satisfying, so I tried flashing different modems. Eventually CDMA works, but GSM not. So I made a huge mistake by attempting to downgrade from NE2. And of course failed. Now the phone can't register on either CDMA or GSM.
So once I flash M2 Stock with Count Reset, I can play with the 4.4.2 OTA zip again to get a 100% 4.4.2 system?

michael85tx said:
This happened to me today too. I didn't like the OTA 4.4 so I was trying to get a custom rom again. Thanks to jlmancuso he made the best solution here:
http://forum.xda-developers.com/showpost.php?p=53035491&postcount=287&nocache=1&z=4473536636214703
Simply download the attached file. It is BRICKED heaven! (worked for me.) and have your recovery (twrp, philz, cwm) file. And have Odin.
1) Extract all files fix / recovery (if haven't already) / and odin (again if haven't already)
2) Open Odin in PDA put in the "fix" file. BEFORE continuing, UNCHECK Auto Reboot. (HAS TO BE UNCHECKED)
3) Connect phone to computer
4) Once the file has finished (Odin will say pass) disconnect the phone.
DO NOT TAKE THE BATTERY OUT
5) Put it back in Recovery Mode (home / volume up / power )
Give it a minute and it will load a custom recovery.
If you were stuck at a bootloop you probably don't have a rom on your phone (cleaned and empty).
If so try flashing this in Odin as well (https://drive.google.com/file/d/0B0CWousOd0ntTHl2RmxPbHJWODQ/edit?usp=sharing}
When the custom recovery loads you can flash what you want.
Odin will not let you downgrade from NE2 to anything below (bootloader). I suggest flash over Philz and flash that way.
http://forum.xda-developers.com/showthread.php?t=2768847
Has a NE2 rooted already. Flash this and save a backup. YOU WILL NEED IT.
Once in the custom recovery that comes up I suggest to flash the M2 Stock with Count Reset. (back to complete stock) then can do what you want from there.
**If the custom recovery does not show up**
Repeat the steps above (Odin / add fix to PDA / Uncheck Auto Reboot / Connect Phone / start flash)
Then again DO NOT PULL BATTERY ... (once it shows pass) disconnect and reboot back in download mode ( home / volume down / power )
Flash over your recovery ... (do not pull battery) and try the Recovery Mode ... my first time I thought it was still stuck in bootloop so give it a second.
Click to expand...
Click to collapse
You, sir, helped the hell out of me! I thought my phone was screwed and I've already tried everything. Thank you soo much!
Just curious, did you ever get kitkat to work? I've tried going to MC2 stock then upgrading a couple more times but it ends up doing the bootloop again every time :/ did you ever get that to update?
I'm so glad to have a working phone now though! Thanks!

SCAND1UM said:
You, sir, helped the hell out of me! I thought my phone was screwed and I've already tried everything. Thank you soo much!
Just curious, did you ever get kitkat to work? I've tried going to MC2 stock then upgrading a couple more times but it ends up doing the bootloop again every time :/ did you ever get that to update?
I'm so glad to have a working phone now though! Thanks!
Click to expand...
Click to collapse
I did the procedure everything went well but is there any way to update lastest firmware kitkat as i tried to and keep having to do the same procedure to unbrick it? thanks

brooklynman2020 said:
I did the procedure everything went well but is there any way to update lastest firmware kitkat as i tried to and keep having to do the same procedure to unbrick it? thanks
Click to expand...
Click to collapse
The best way to do the upgrade (since you know how to get your phone back if it happens again) is to just simply use Odin now to flash the 4.4.2 tar file thanks to "garwynn" for taking the time in making it.
http://forum.xda-developers.com/showthread.php?t=2780984
since most of my links don't work after I post lol I'm giving the download too. I tried uploading it but the file size is too big to post. So I hope this link works let me know and I'll re-upload it and post another link if the link stops working. 4.4.2 stock rom .tar
---------- Post added at 03:05 AM ---------- Previous post was at 02:55 AM ----------
lilila said:
What a nightmare!
I odined back to stock MK4, did the 4.4.2 OTA last night. Then did the CF Auto Root via odin, installed custom recovery. The phone is currently on pageplus network. I started messing around, did the GSM Mod, then tried the international and domestic sim unlock procedures. The result was not satisfying, so I tried flashing different modems. Eventually CDMA works, but GSM not. So I made a huge mistake by attempting to downgrade from NE2. And of course failed. Now the phone can't register on either CDMA or GSM.
So once I flash M2 Stock with Count Reset, I can play with the 4.4.2 OTA zip again to get a 100% 4.4.2 system?
Click to expand...
Click to collapse
sorry for the late reply but yes you can. I have gone back and forth trying to decide which 4.4.2 works best for service and style. lol right now I'm on 4.4.2 stock rooted (took FOREVER to get rooted I think it just finally clicked in I had given up). but there's already a .tar file for 4.4.2 you can just flash the .tar file and you have a OTA STOCK (unrooted) version of 4.4.2 for SPRINT only. It's the easiest way to get your phone back to working if it' soft bricked or just won't load recovery.
...NOTE... you can UPGRADE flash your bootloader (i.e. ... M2 .. MK4 ...N2) from Odin. You just CAN NOT downgrade firmware via Odin if you're going to go back to 4.1/4.2/4.3 versions. You will 99% of the time get "failed" at write to sboot .. for recovery I recommend Philz as it clears your cache and such when you flash roms and gapps and such for you.
---------- Post added at 03:10 AM ---------- Previous post was at 03:05 AM ----------
SCAND1UM said:
You, sir, helped the hell out of me! I thought my phone was screwed and I've already tried everything. Thank you soo much!
Just curious, did you ever get kitkat to work? I've tried going to MC2 stock then upgrading a couple more times but it ends up doing the bootloop again every time :/ did you ever get that to update?
I'm so glad to have a working phone now though! Thanks!
Click to expand...
Click to collapse
You're welcome lol when it happened to me I wanted to punch a wall or something because I couldn't make a call to help me and there was no way Sprint would have helped me. It took me 8 hours to find it that day lol I had almost started giving up hope

You may already know this, but you also want to read up and see what versions of odin people are having success with. As well as what custom recoverys (and versions) seem to be working.
I used Odin v3.09 with no problems. Heard that others had success with v3.07
Flashed and running Philz custom recovery v6.0.4.5
I flashed update-supersu-v1.94.zip (originally flashed cwm-supersu-v0.94.zip, which DID NOT work). Supersu is a little buggy. On both the note2 and s3, after install apk would fc. Went to play store and updated supersu, supersu will then work (even "partially" disables knox for you)
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2

g_money said:
You may already know this, but you also want to read up and see what versions of odin people are having success with. As well as what custom recoverys (and versions) seem to be working.
I used Odin v3.09 with no problems. Heard that others had success with v3.07
Flashed and running Philz custom recovery v6.0.4.5
I flashed update-supersu-v1.94.zip (originally flashed cwm-supersu-v0.94.zip, which DID NOT work). Supersu is a little buggy. On both the note2 and s3, after install apk would fc. Went to play store and updated supersu, supersu will then work (even "partially" disables knox for you)
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Yeah that's true I use Odin 3.09 Philz Recovery (latest version if that doesn't work the 6.07.09 has had some good success) and SU v1.93 is the one I have.

Stuck with 4.4.2 OTA
michael85tx said:
This happened to me today too. I didn't like the OTA 4.4 so I was trying to get a custom rom again. Thanks to jlmancuso he made the best solution here:
http://forum.xda-developers.com/showpost.php?p=53035491&postcount=287&nocache=1&z=4473536636214703
Simply download the attached file. It is BRICKED heaven! (worked for me.) and have your recovery (twrp, philz, cwm) file. And have Odin.
1) Extract all files fix / recovery (if haven't already) / and odin (again if haven't already)
2) Open Odin in PDA put in the "fix" file. BEFORE continuing, UNCHECK Auto Reboot. (HAS TO BE UNCHECKED)
3) Connect phone to computer
4) Once the file has finished (Odin will say pass) disconnect the phone.
DO NOT TAKE THE BATTERY OUT
5) Put it back in Recovery Mode (home / volume up / power )
Give it a minute and it will load a custom recovery.
If you were stuck at a bootloop you probably don't have a rom on your phone (cleaned and empty).
If so try flashing this in Odin as well (https://drive.google.com/file/d/0B0CWousOd0ntTHl2RmxPbHJWODQ/edit?usp=sharing}
When the custom recovery loads you can flash what you want.
Odin will not let you downgrade from NE2 to anything below (bootloader). I suggest flash over Philz and flash that way.
http://forum.xda-developers.com/showthread.php?t=2768847
Has a NE2 rooted already. Flash this and save a backup. YOU WILL NEED IT.
Once in the custom recovery that comes up I suggest to flash the M2 Stock with Count Reset. (back to complete stock) then can do what you want from there.
**If the custom recovery does not show up**
Repeat the steps above (Odin / add fix to PDA / Uncheck Auto Reboot / Connect Phone / start flash)
Then again DO NOT PULL BATTERY ... (once it shows pass) disconnect and reboot back in download mode ( home / volume down / power )
Flash over your recovery ... (do not pull battery) and try the Recovery Mode ... my first time I thought it was still stuck in bootloop so give it a second.
Click to expand...
Click to collapse
Followed this procedure after accepting OTA and couldn't get chainfire autoroot to work. This worked flawlessly for me and I'm flashing again !!!!

lewisyiv said:
Followed this procedure after accepting OTA and couldn't get chainfire autoroot to work. This worked flawlessly for me and I'm flashing again !!!!
Click to expand...
Click to collapse
Where is the fix file for download? I cant flash the tar file, all time show fail in odin, I was try with firmware 4.4.2, 4.2, 4.1.2 and nothing my note 2 enter in download mode but not in recovery mode, alwais is in bootloop in logo... maybe I have brick?

vegitamaster66 said:
Where is the fix file for download? I cant flash the tar file, all time show fail in odin, I was try with firmware 4.4.2, 4.2, 4.1.2 and nothing my note 2 enter in download mode but not in recovery mode, alwais is in bootloop in logo... maybe I have brick?
Click to expand...
Click to collapse
Two post above you or in the quote above you has the link for fix. You need to follow the first link (xda thread link) and it will take you to my post that has the upload.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Second post in this thread helped me immensely. Thank you!
I broke my note 2 that I had rooted and was running rwilco's mostly stock rom on.
Got another note 2 off craigslist and decided I should root it too for speed and for tethering. Tried the liquid smooth rom and it failed leaving me with no ROM.
Every ROM I tried failed until I found this thread and used Odin to flash "ALL_SPT_L900VPUCNE2_L900SPTCNE2_1561791_REV04_user_low_ship.tar.md5" that was linked.
So phone is now running 4.4.2 can I safely try again to load a custom ROM?
What do I need to do to make sure I don't have the same problem?
I'm not really savvy with this stuff but I can follow destructions

does any of the above steps wipe internal data?

[Q] Phone really seems to be bricked

Hi all, I'm hoping someone can help, but I'm not too optimistic. I have a SGH-M919 (T-Mobile Galaxy S4) that had a tripped KNOX bootloader and I had been installing custom ROMs on it. I wanted to ODIN back to stock, but it has caused all kinds of problems.
I was using ODIN v3.09 to ODIN the NB4 complete .tar file from Sammobile under the "AP" section with only Auto Reboot and F. Reset Time checked. It got what looked like about 95% complete and then showed FAILED. It gets to a point where it will say:
"Complete(Write) operation failed"
Upon rebooting, the phone says "Firmware upgrade ecountered an issue. Please select recovery mode in Kies & try again."
The phone will go into Download mode still but it will not go into Recovery mode.
After the above combination failed, I've tried using ODIN v.3.07 and v1.85, different official and unofficial firmwares (NB4, MK2, Fenny's NB4), tried various USB ports on my computer, and even tried another computer. Each time ODIN fails, and sometimes much earlier in the process.
I also tried installing using Kies after all of the above failed, but Kies will not recognize the phone at all.
Is it dead, or does anyone know of something else I can try? Upon my searching, most recommendations to "brick" problems seems to just be to ODIN like I did above =/.
Thank you for any help!

Have you tried flashing recovery and then booting right away to it?

serio22 said:
Have you tried flashing recovery and then booting right away to it?
Click to expand...
Click to collapse
I was able to flash a recovery, which is good news. The one I had on hand was Philz, which I could go straight into. Now I have a problem with /data not being able to mount, and no ROM I install from recovery seems to boot, even a full nandroid backup... Any ideas from there?
UPDATE: I flashed TWRP 2.5.0.2 and was able to format /Data, reinstalled a ROM, and it booted!! Thanks so much!!

Mralexander006 said:
UPDATE: I flashed TWRP 2.5.0.2 and was able to format /Data, reinstalled a ROM, and it booted!! Thanks so much!!
Click to expand...
Click to collapse
Good! That's what I was gonna suggest

Mralexander006 said:
I was able to flash a recovery, which is good news. The one I had on hand was Philz, which I could go straight into. Now I have a problem with /data not being able to mount, and no ROM I install from recovery seems to boot, even a full nandroid backup... Any ideas from there?
UPDATE: I flashed TWRP 2.5.0.2 and was able to format /Data, reinstalled a ROM, and it booted!! Thanks so much!!
Click to expand...
Click to collapse
Hi. I'm having the same issue here. Can you please elaborate on what you did exactly? Thanks

hyperenigma said:
Hi. I'm having the same issue here. Can you please elaborate on what you did exactly? Thanks
Click to expand...
Click to collapse
ive read forums and trying different things for 6+ hours and was having no luck.
i read that someone took it to a best buy where they have a samsung kiosk because they can reflash the firmware.
i took it there but they were unable to reflash it.
they had the same problems i was having.
i literally just tried odin again and it worked.
i think mayb them hooking it up to their computer did something to it which then allowed me to get it to work.
if that doesnt work you can also send it back to samsung to have it reflashed,
both are FREE of charge. ( most people dont know that.
best of luck to you.

Hey sorry, have been swamped with work. Did you ever get it working or still need help?

Using ODIN to flash a complete ROM would always fail, bit have you tried flashing just TWRP recovery? For me that worked, and from there I could reformat the /data folder, and flash a new ROM in recovery. Never was able to use Odin for a full ROM but that method was good enough.

[q] phone wont boot help

HEY GUYS,
So I am upgrading to the note 4 next week. Sending my sister my note 2 and decided to leave the wonderful Community Rom and restore it back to stock for her to receive updates and not worry about root issues. I rebooted into my philz recovery. Flashed my old MC2_STOCK_with_COUNT_RESET-20130511 zip I had on my SD card which had always worked in the past, and succeeded. Then it rebooted to the Samsung Galaxy Note 2 splash screen and sat there for over 15 minutes never booting up.
Went to PC, opened Odin 1.85, and flashed several L900 Kies firmware and they failed. Finally, found one that flashed successfully, KIES_HOME_L900VPALJ1_L900SPTALJ1_265523_REV04_user_low_ship.tar. After successful flash, it auto reboots from download mode and has been stuck on the splash screen again for over 15 minutes. What do I do now? I have never had it hang up like this for this long, and had issues like these reverting to stock when I have wanted to in the past. Only thing that is different, is I have been on the 4.4.2 rom and these are probably 4.1.2 or 4.3 versions I am flashing.
Please help, I only have a limited time to fix this before I have to ship it off. Thanks guys

Dedline said:
HEY GUYS,
So I am upgrading to the note 4 next week. Sending my sister my note 2 and decided to leave the wonderful Community Rom and restore it back to stock for her to receive updates and not worry about root issues. I rebooted into my philz recovery. Flashed my old MC2_STOCK_with_COUNT_RESET-20130511 zip I had on my SD card which had always worked in the past, and succeeded. Then it rebooted to the Samsung Galaxy Note 2 splash screen and sat there for over 15 minutes never booting up.
Went to PC, opened Odin 1.85, and flashed several L900 Kies firmware and they failed. Finally, found one that flashed successfully, KIES_HOME_L900VPALJ1_L900SPTALJ1_265523_REV04_user_low_ship.tar. After successful flash, it auto reboots from download mode and has been stuck on the splash screen again for over 15 minutes. What do I do now? I have never had it hang up like this for this long, and had issues like these reverting to stock when I have wanted to in the past. Only thing that is different, is I have been on the 4.4.2 rom and these are probably 4.1.2 or 4.3 versions I am flashing.
Please help, I only have a limited time to fix this before I have to ship it off. Thanks guys
Click to expand...
Click to collapse
Have you tried to boot into recovery and wipe data and cache?

mr_wrong_0 said:
Have you tried to boot into recovery and wipe data and cache?
Click to expand...
Click to collapse
It does not boot into recovery. Only a splash screen of Samsung. Recovery does not seem to exist at this point.

I'd say start there.
Flash a custom recovery with Odin and then flash a stock rooted rom like Rwilco's mostly stock

Working after this flash
Thanks for your help, I went to this link - http://forum.xda-developers.com/showthread.php?t=2780984
Downloaded [LINK][ROM][ODIN][TAR]SPH-L900 NE2 (NE2 Modem/Kernel/ROM - Stock) and flashed it in Odin 1.85 and it booted and is updated and everything. Finally! Thanks