Develop Bugs

[Q] Samsung EPIC 4g BRICKED - won't boot!!!

Hello Everyone,
I tried flashing Cyanogen7 onto my rooted EPIC 4G using ClockworkMod Recovery v3.0.2.4 and this immediately bricked my phone and kept it from booting up.
When I try to boot up my phone it gets stuck at the SAMSUNG boot up screen and the four capacitive buttons (menu,home,back,search) say lit up. When I try to boot into Recovery Mode I get the following screen:​
ClockworkMod Recovery v3.0.2.4
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
- Install zip from sdcard
- Backup and Restore
- Mounts and Storage
- Advaned
- Power Off
- *****Go Back*****
------------------------------------------------------------------
E:Missing bitmap icon_clockwork (Code -1)
ClockworkMod Recovery v3.0.2.4
E:failed to open /etc/recovery.fstab (No such file or directory)
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]​
When, for example, choose Wipe data/factory reset from the menu above it simply shows:​
-- Wiping data...
Formatting /data...
E:unknown volume "/data"
Formatting /cache...
E:unknown volume "/cache"
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
E:unknown volume "/sdcard/.android_secure"
Data wipe complete.
E:unknown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:unknown volume for path [cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]​
I'm really not sure what to do here. Any help would be appreciated.​
Thanks guys...

Have to tried to Odin back to stock and then retrying it? Your phone isn't bricked. It's not even close to being bricked. In fact, it's just fine. A simple couple clicks in Odin and your right back to stock let me know if ya need anything else

Ur not bricked go into download mode by holding 1 on the keyboard while powering on and Odin back to stock I am truly bricked where as my phone won't get into anything or even charge

tried looking into Odin...seems to only work on Windows...don't suppose there's an alternative that I could use on my Mac is there?

Heimdall. Read the directions twice.

And in the future, don't touch ROM Manager or any of the CWM versions it offers. Ever.
EDIT: This thread title gets more annoying every time I see it...

Failed to Detect Compatible Device
Hey all,
So I was able to get Heimdall up and running (thanks a bunch for that) but for some reason my phone doesn't seem to be able to connect to my computer when it's in downloading mode (screen where the yellow android with a shovel pops up). When I click 'Start' on Heimdall it just tells me that it cannot detect a compatible device. But I'm sure that my Epic is plugged in correctly.
The only thing I can think of is that my cord is messed up for some reason. Going to give it a try with a different one. Is there anything else it could be?

I don't know mac but the same thing happens on windows if after you installed samsung drivers you did not re boot pc. Maybe a problem you might run into is that when the phone is running and you connect it will install the drivers. Hopefully it installs what you need without a running connect.
Sent from my SPH-D700 using XDA App

ldartez said:
Hey all,
So I was able to get Heimdall up and running (thanks a bunch for that) but for some reason my phone doesn't seem to be able to connect to my computer when it's in downloading mode (screen where the yellow android with a shovel pops up). When I click 'Start' on Heimdall it just tells me that it cannot detect a compatible device. But I'm sure that my Epic is plugged in correctly.
The only thing I can think of is that my cord is messed up for some reason. Going to give it a try with a different one. Is there anything else it could be?
Click to expand...
Click to collapse
I doubt it's your cord. Unfortunately Samsung have released a lot of dodgy secondary bootloaders that don't work on OS X. Samsung fixed this for certain bootloaders running on certain devices however I'm unsure about the Epic 4G. I recommend starting a thread asking about it. If no one knows then unfortunately you'll have to use Windows or linux.

Benjamin Dobell said:
I doubt it's your cord. Unfortunately Samsung have released a lot of dodgy secondary bootloaders that don't work on OS X
Click to expand...
Click to collapse
This may be, but the stock Samsung cord is a notorious piece of horse ****. (Yes, it's that bad.)

Benjamin Dobell said:
I doubt it's your cord. Unfortunately Samsung have released a lot of dodgy secondary bootloaders that don't work on OS X. Samsung fixed this for certain bootloaders running on certain devices however I'm unsure about the Epic 4G. I recommend starting a thread asking about it. If no one knows then unfortunately you'll have to use Windows or linux.
Click to expand...
Click to collapse
I've tried starting a thread b4 on this and no one responded to it
Sent from my SPH-D700 using XDA Premium App

Honest suggestion? Just find a friend with a Windows computer and use Odin on his. Also, I've never had any problems with my Samsung data cable, but I also bought a blackberry micro cable for like $1.50 on amazon and free prime shipping, and it works great too.

Phone fixed!!
I ended up being able to fix my phone. The problem ended up being that Mac, for some reason, is not able to detect samsung phones (or at least mine..Epic 4g) while they are in Download Mode. I loaded the .msi drivers that I needed, Odin ( as opposed to heimdall for the sole reason that Heimdall requires Visual studio files to be installed on Windows) and the stock android image onto a flash drive.
I plugged these into a windows machine and everything worked perfectly.

k0nane said:
And in the future, don't touch ROM Manager or any of the CWM versions it offers. Ever.
EDIT: This thread title gets more annoying every time I see it...
Click to expand...
Click to collapse
if not rom manager or CWM then what do you usually use for flashing roms?

He's just saying don't use Rom Manager or the versions of CWM it specifically installs. Just use the CWM versions found here on the Epic 4G forums. Yes, CWM is how we flash roms.
ldartez said:
if not rom manager or CWM then what do you usually use for flashing roms?
Click to expand...
Click to collapse

well i just ran into this problem, with rooted stock froyo (think its EC05) and the customized purple cwm for the epic... so clearly using the recovery image found on these forums is NOT foulproof... and all i wanted to do was perform a back up so i could try out a eg22 rom... sigh... anyway thanks to odin im back up but now i have to re do everything and i was not able to back up my STOCK!!! image. is there a different recovery available or perhaps one that works?

duplissi said:
well i just ran into this problem, with rooted stock froyo (think its EC05) and the customized purple cwm for the epic... so clearly using the recovery image found on these forums is NOT foulproof... and all i wanted to do was perform a back up so i could try out a eg22 rom... sigh... anyway thanks to odin im back up but now i have to re do everything and i was not able to back up my STOCK!!! image. is there a different recovery available or perhaps one that works?
Click to expand...
Click to collapse
Did you go into recovery with the 3 finger method or did you use quck boot or ROM manager? Never use any of those when doing a backup or restore. The purple recovery worked well for me when I needed it but now am using Bonsai's recovery rooting with Masterkey Unlocker. You can find Bonsai's site by googling Bonsai Android.
Sent from my SPH-D700 using XDA App

kennyglass123 said:
Did you go into recovery with the 3 finger method or did you use quck boot or ROM manager? Never use any of those when doing a backup or restore. The purple recovery worked well for me when I needed it but now am using Bonsai's recovery rooting with Masterkey Unlocker. You can find Bonsai's site by googling Bonsai Android.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
yeah, i used the three finger method...
bonsai eh? ill have to look it up. edit: or i could just click the link in your sig... lol
off topic: im new to the epic (finally retired my weary hero), so anything you would recommend?

duplissi said:
yeah, i used the three finger method...
bonsai eh? ill have to look it up. edit: or i could just click the link in your sig... lol
off topic: im new to the epic (finally retired my weary hero), so anything you would recommend?
Click to expand...
Click to collapse
I try not to advertise the link in the sig (shhh). I do recommend trying the Masterkey Unlocker if you are unhappy with CWM 3.1.0.1. It is a nice graphical interface and works well. You can Odin to either EB13 or EC05 stock, root with the MK and then 3 finger to nand backup your phone or use Titanium Backup.
Sent from my SPH-D700 using XDA App

[Q] CWM Troubles (E: Can't open /cache/recovery etc. etc.)

I would love your guy's opinions on this issue. I was planning to do a fresh install of Cyanogenmod due to wifi issues when I ran into some trouble. I just updated my Clockworkmod recovery from 3.0.0.8 to 5.0.2.0 this morning, and it has been bringing up errors along the lines of:
Code:
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/log
E: Error in /cache/recovery/log
(Read-only file system)
I read up on these errors, and it seems that attempting to flash ROMs and whatnot with these errors often lead to bricked devices. So far, my device still works fine (minus the WiFi, obviously), and I've successfully flashed the recovery several times, performed a nandroid backup, and reflashed my kernel without error, as far as I can tell. However, given the nature of these errors, I am much too nervous to try reflashing Cyanogenmod. So far I have attempted downgrading CWM, checking my emmc and checked the cache partition for the files CWM supposedly can't open. last_log is present, but log is not. From the results of the emmc test, I think it's working fine, but I'd like you guys to verify that for me. Below is about as detailed a log as I can give of what has happened today. Any assistance in fixing this problem and making sure it is safe to reflash Cyanogenmod would be extermely appereciated.
Phone Info
HTC Droid Incredible (ADR6300)
Cyanogenmod 7.1.0 RC1
Android 2.3.4
Clockworkmod Recovery 3.0.0.8
Incredikernel 2.6.38.8 (8/15/11)
HBOOT 0.92.0000
Radio 2.15.00.07.28
S-OFF
Code:
Events leading up to this:
Flashed CWM 5.0.2.0 through ROM Manager-flash failed
Rebooted into recovery-still running 3.0.0.8
Rebooted phone
Tried again through ROM Manager with "erase recovery" option checked
Rebooted into recovery-still running 3.0.0.8
Rebooted phone
Flashed CWM 5.0.2.0 through Terminal Emulator
Rebooted into recovery-flash was successful
Rebooted phone
Discovered WiFi error issue
Rebooted into CWM 5.0.2.0
Performed a nandroid backup, which appeared to be successful
Errors appeared at some point, can't remember when.
"E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_log"
Rebooted phone
Rebooted into CWM 5.0.2.0
Wiped Dalvik cache and reflashed incredikernel, thinking it would fix the WiFi issue
Flash seemed successful, same errors popped up again, can't remember exactly when
Rebooted phone
Researched errors, came to notice that navigating menus and backing out now caused:
"E: Error in /cache/recovery/log
(Read-only file system)
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_log"
Further navigation would always produce:
"E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_log"
Code:
Steps taken to fix the problem (so far)
Tried flashing CWM 3.0.0.8 through ROM Mangager
Rebooted into recovery-still running 5.0.2.0
Tried flashing CWM 3.0.0.8 through adb
Rebooted into recovery-flash was successful
Errors still persisted
Found a thread suggesting the problem may be with a faulty emmc
Ran "cat /proc/kmsg | grep mmc0" through adb to test the emmc
Results of test
Checked to see if log and last_log files exist
Found last_log, not log
Images of the problem
Results of the emmc test
Errors in CWM 5.0.2.0
Errors in CWM 3.0.0.8
last_log is present in /cache/recovery

Have you wiped the cache partition from recovery and then flash cwm recovery from hboot as a PB31IMG.zip?

How exactly do I go about doing that? I know how to wipe the cache, but do I just rename the CWM zip to PB31IMG.zip and flash it?

Rixanu said:
How exactly do I go about doing that? I know how to wipe the cache, but do I just rename the CWM zip to PB31IMG.zip and flash it?
Click to expand...
Click to collapse
Um not sure what file you have but here is one for you http://dinc.does-it.net/PB31IMG.zip, just place it on the root of your sdcard and boot into hboot. It will find the file after a couple secs and prompt to press vol up to install. This is version 5.0.1.0
Also you may want to run fix permisions from the advanced menu in recovery.

You are quite the lifesaver, it worked like a charm! One more question, though. I would like to upgrade CWM to 5.0.2.0 if possible. Would it be safe to flash it through terminal emulator/adb, or should I just update through hboot from now on? Thanks so much for your help!

Rixanu said:
You are quite the lifesaver, it worked like a charm! One more question, though. I would like to upgrade CWM to 5.0.2.0 if possible. Would it be safe to flash it through terminal emulator/adb, or should I just update through hboot from now on? Thanks so much for your help!
Click to expand...
Click to collapse
No problem. Hboot is the best way to do it. I dont have a 5.0.2.0 file at the moment but if you need one i can get it for you.
Edit: you could also update it thru rom manager and if for some reason it messes something up just flash the one from earlier post again.

That's alright, I found one a few minutes ago, just in case. This also seems to have fixed my wifi issue, so this is about the best case scenario I can picture. Thanks again!

Your welcome.

I guess all is not as it seems. The problem in CWM started popping up again just a few minutes ago. On top of that, when I rebooted, I got caught in a bootloop. I managed to boot up fine after a battery pull, but this is really starting to scare me. Does anyone have any advice?
PS. I'm posting here because I feel this doesn't need a whole new topic. If that would be better, just let me know.

Rixanu said:
I guess all is not as it seems. The problem in CWM started popping up again just a few minutes ago. On top of that, when I rebooted, I got caught in a bootloop. I managed to boot up fine after a battery pull, but this is really starting to scare me. Does anyone have any advice?
PS. I'm posting here because I feel this doesn't need a whole new topic. If that would be better, just let me know.
Click to expand...
Click to collapse
I would revert back to CWM 3.0.0.8 thru rom manager for awile and see if the problem still persists. However once you do make sure to make a new nandroid as i dont believe cwm 5 backups are compatible with version 3.

Rom manager didn't work (again), so I flashed through hboot and it worked fine. Errors are gone, and no more bootloops since last night. I'm gonna wipe and reflash Cyanogen later today because my wifi is all buggy again and I feel as if a clean install may hopefully kill any latent symptoms. Feel free to let me know it that's a bad idea, haha. Thanks again.

Can no longer flash a rom

So I have an issue. After I was formatted system and wiped my data to install 1.9 I accidentally reboot the phone before I installed the rom, now when I'm in clockwork mod I get a
E:unknown volume for path [/sdcard]
E:Can't mount /sdcard/
error whenever I try to select the zip to install. How do I fix this?
The phone won't load past the boot screen either because there is no rom installed. I even tried to reset it to stock and it won't load past the startup screen

This happened to mine too. Looking for answers

There's always a usb jig to force it into download mode. Then just reflash a tar. Look for the thread "the jig is up"
Sent from my SPH-D710 using xda premium

This happened to me. I odin'd an older version of cwm, and installed a rom from the internal storage. For some reason the older one worked for me.
Sent from my SPH-D710 using XDA App

Or you can try to mount USB in mounts and storage, transfer rom to internal storage, and flash from there.
Sent from my SPH-D710 using XDA App

Happened to me tons of times. Just Odin the recovery again and it'll work fine.

OP, much like others have suggested, boot into odin mode and reflash recovery

Having major issues here please help and thanks!
My phone-Samsung Galaxy S2 Epic 4G Touch (Sprint) SPH-D710
RUNNING AOKP ICS ROM DOWNLOADED FROM EPIC4GTOUCHROOT DOT COM
From my understanding i should have flashed this rom through odin instead of my rouge recovery.I enjoyed the rom for a day or two than decided to flash back to a different rom and rouge recovery no longer showed up. Anroid system recovery <3e> shows up instead. i went to try to flash a rom here and it started than the android guy came up laying down with the chest area open and an exclamation mark above him than said
E: failed to verify whole-file signature
E: signature verification failed
installation aborted.
My computer no longer recognizes my phone iv tried re-installing the drivers and no luck. I've tried installing from sd card and still no luck. Ive tried mobile odin and it doesnt pick up anything in my sd card.
SOMEONE PLEASE HELP WHAT DO I DO???
-THANKS

[CWM][Samsung Galaxy GT-I5510] CWM Touch Recovery

That's it, I present you CWM Based Recovery On-Screen Touch Navigation Controls by Team UtterChaos for our Galaxy 551 :laugh:
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE BY FLASHING THIS ROM
DOWNLOAD
Code:
You can find it [URL="http://goo.gl/WFr5Q"]HERE[/URL]
Code:
OFFICIAL THREAD [URL="http://forum.xda-developers.com/showthread.php?t=1485829"]HERE[/URL]
Installation
Code:
1. Make sure you have got GingerBread bootloader.
2. Download Odin Multidownloader v4.34 for GT-I5510, Callisto_v1.ops and latest Clockwork Mod Recovery if you do not have them already.
3. Run Odin Multi downloader v4.34 and select the Callisto_v1.ops by clicking OPS button.
4. Select One Package Option and Click One Package button and select the recovery file name (CWM_5.0.2.7_touch_bebek15.tar.md5) file you downloaded.
5. Leave other settings to default (i.e. don’t change any other options/settings)
6. When you are done reboot your phone in download mode (Press Q + Power button to go to download mode)
7. Connect your phone in download mode to your computer via USB Cable.
8. When Odin detects your phone (If you see a com port number written in yellow background at the top left, then your phone is detected. View image.), click Start button.
9. Wait till Odin finishes the job (approx. 5-10 seconds:cool:) and when it reports ‘PASS’, you can disconnect your phone.
Credits
Code:
[B]Team UtterChaos
squadzone
willingmagic
didhiy
yagya
me[/B]
hint: you can't restore nandroid backup from other version of cwm with this.

thanks priyesh103 for this video​

Screenshot of CWM touch recovery
look at here,

Just asking, do we need an "Power Off" option on the recoveries?

sometimes a poweroff option is needed....
Sent from my GT-I5510 using xda premium

odin doesn't detect my phone !!
pls share the drivers for win 7 64 bit

help me !!!
can u provide drivers for win7 64 bit
i need to install cwm but odin doesnt detect my phone
pls give me the exact procedure to insall cwm
edit :successfully installed cwm

please help, wrong flashing this cmw cause my phone firmware is froyo, now I can not get to the download mode, try using a usb jig (with resistor 330k ohm) also can not help...

nasyiinhd said:
please help, wrong flashing this cmw cause my phone firmware is froyo, now I can not get to the download mode, try using a usb jig (with resistor 330k ohm) also can not help...
Click to expand...
Click to collapse
same problem here :crying:, any luck in resurrecting it

CWM errors
Hi,
Thanks for the great instructions! I followed them precisely but as I boot to the recovery mode (power+T) I get the following errors nor any commands work in CWM. I even tried to flash the CWM with ODIN again.
CWM-based recovery v.5.0.2.7
E: Can't mount /cache/recovery/Command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Please note that I had a stock Samsung Galaxy GT-I5510 with Android 2.3.6. So I have not rooted my phone in any way. Should I? How can I do it? Thank you for your support!
P.S. As I will get the CWM Recovery to work I will flash CyanogenMod 10.2.
http://forum.xda-developers.com/showthread.php?t=2438393

qrk said:
Hi,
Thanks for the great instructions! I followed them precisely but as I boot to the recovery mode (power+T) I get the following errors nor any commands work in CWM. I even tried to flash the CWM with ODIN again.
CWM-based recovery v.5.0.2.7
E: Can't mount /cache/recovery/Command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Please note that I had a stock Samsung Galaxy GT-I5510 with Android 2.3.6. So I have not rooted my phone in any way. Should I? How can I do it? Thank you for your support!
P.S. As I will get the CWM Recovery to work I will flash CyanogenMod 10.2.
http://forum.xda-developers.com/showthread.php?t=2438393
Click to expand...
Click to collapse
You want to put SD card with CyanogenMod 10.2 and gapps to your phone, then choose option install wipe data/factory reset, install zip from SD card and choose .zip file containing CyanogenMod 10.2, and then install gapps and restart the phone.

Phone doesn't reboot
Hi,
I hope anybody reads this.
I downloaded the .tar.md5 files and proceeded with the instructions.
Though Odin tells me that it's flashing the telephone this is the last message of the log "<1> Close serial port and wait until rebooting."
And nothing happens afterwards. I can only see that the phone switches on again, but the screen stays dark.
Can you help me with anything? I already spent hours because i just tried to get a custom recovery on the phone because I couldn't install CyanogenMod from the SD card.

H4NNE5 said:
Hi,
I hope anybody reads this.
I downloaded the .tar.md5 files and proceeded with the instructions.
Though Odin tells me that it's flashing the telephone this is the last message of the log "<1> Close serial port and wait until rebooting."
And nothing happens afterwards. I can only see that the phone switches on again, but the screen stays dark.
Can you help me with anything? I already spent hours because i just tried to get a custom recovery on the phone because I couldn't install CyanogenMod from the SD card.
Click to expand...
Click to collapse
Which version of odin are you using?

Hi,
It's 4.43
I also started it as administrator and tried different USB-Ports.
What does the .ops file contain? Some register adresses?

H4NNE5 said:
Hi,
It's 4.43
I also started it as administrator and tried different USB-Ports.
What does the .ops file contain? Some register adresses?
Click to expand...
Click to collapse
Try odin 4.34.
.ops file contains partition table of your phone.

So first I flashed the stock firmware back again to be safe that at least it's still working. That was successful.
Ok I forgot to install the GB bootloader, I didn't mention this. But from the links of the first page none is working anymore.
Can you provide me one?
Also now I can't get into the stock recovery anymore with "T + Power".

H4NNE5 said:
So first I flashed the stock firmware back again to be safe that at least it's still working. That was successful.
Ok I forgot to install the GB bootloader, I didn't mention this. But from the links of the first page none is working anymore.
Can you provide me one?
Also now I can't get into the stock recovery anymore with "T + Power".
Click to expand...
Click to collapse
Cwm and stock

Bootloader

Hi kac321,
Thanks but I need the bootloader. I already have the recovery.

H4NNE5 said:
Hi kac321,
Thanks but I need the bootloader. I already have the recovery.
Click to expand...
Click to collapse
Check post #18

[Q] Stuck On Boot Screen Even After Flash With Odin

I drop my phone one day and this nightmare started. When I power on my phone it then stuck on bootloop. I then start the phone in recovery mode and I got the error messages as below.
Code:
# MANUAL MODE #
-- Appling Multi-CSC...
E:failed to mount /system (No such file or directory)
can't mount '/system' (No such file or directory)
E:failed to mount /data (No such file or directory)
can't mount '/data' (No such file or directory)
E:failed to mount /data (No such file or directory)
E:failed to mount /system (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (No such file or directory)
Then I go on and try to flash with stock ROM using Odin. I am pretty sure I did the steps right as I follow online instruction and I flash my phone before. At the end my phone just stuck at bootup screen and when I try in recovery mode it shows the same error message as above.
Is anyone have any idea how to get this fix? I am suspected that my internal storage is corrupted but that's just my guess. Thanks in advanced!
*****I notice that when I start Odin it get through the "Get PIT for Mapping" step very quickly unlike what I saw on any other youtube video. Is it possible that my phone PIT is corrupted and need a new PIT file?

try downloading this and flashing via odin
http://forum.xda-developers.com/showthread.php?t=1975560
i just had a problem with trying to restore a stock rom using twrp and got stuck in a boot loop, even after wiping and installing another stock rom... then i flashed this one via odin and for some reason it worked and i'm back into my stock rom w/ root.
really hope this works for you & good luck.

NovaxxBite said:
try downloading this and flashing via odin
http://forum.xda-developers.com/showthread.php?t=1975560
i just had a problem with trying to restore a stock rom using twrp and got stuck in a boot loop, even after wiping and installing another stock rom... then i flashed this one via odin and for some reason it worked and i'm back into my stock rom w/ root.
really hope this works for you & good luck.
Click to expand...
Click to collapse
I did try flashing with Odin but it end up in a bootloop. I will look into the thread you provided and see if I miss something. At the meantime, I hope there will be another way to work around.

I search online and found someone having the similar issue to their phone but it is on HTC device.
http://forum.cyanogenmod.org/topic/6433-solved-messed-up-partitions-on-internal-storage/
Therefore, I believe my internal storage partition is mess up or corrupted and need to repartition. In order to do that I believe I need the PIT file for my T-Mobile Note 2 is that right? If so can anyone provide me the PIT file for T-Mobile note 2? Or is there something I am missing still?

Anyone have any idea about this? Please I really need help on this.

jackgan said:
Anyone have any idea about this? Please I really need help on this.
Click to expand...
Click to collapse
What was the last official T-Mobile firmware that you had on your phone?

EdKeys said:
What was the last official T-Mobile firmware that you had on your phone?
Click to expand...
Click to collapse
I believe it is this version. I get the version detail from SamMobile.
Model SGH-T889
Model name GALAXY Note II
Country USA (T-Mobile)
Version Android 4.1.2
Changelist 935627
Build date Thu, 18 Apr 2013 14:07:55 +0000
Product code TMB
PDA T889UVBMD1
CSC T889TMBBMD1
I didn't update to Android 4.3 as some user said having battery problem with this version.

jackgan said:
I believe it is this version. I get the version detail from SamMobile.
Model SGH-T889
Model name GALAXY Note II
Country USA (T-Mobile)
Version Android 4.1.2
Changelist 935627
Build date Thu, 18 Apr 2013 14:07:55 +0000
Product code TMB
PDA T889UVBMD1
CSC T889TMBBMD1
I didn't update to Android 4.3 as some user said having battery problem with this version.
Click to expand...
Click to collapse
Try this with ODIN. If that doesn't work I have one more idea you can try.
http://www.mediafire.com/download/3aaao482ha133oq/root66_TMO_T889UVBMD1.tar.md5

EdKeys said:
Try this with ODIN. If that doesn't work I have one more idea you can try.
http://www.mediafire.com/download/3aaao482ha133oq/root66_TMO_T889UVBMD1.tar.md5
Click to expand...
Click to collapse
I tried with ODIN v3.07 and my phone went into boot loop. What's the other option you have?

EdKeys said:
Try this with ODIN. If that doesn't work I have one more idea you can try.
http://www.mediafire.com/download/3aaao482ha133oq/root66_TMO_T889UVBMD1.tar.md5
Click to expand...
Click to collapse
I haven't heard back from you for a while. I did tried your suggestion with ODIN but that doesn't work. Do you have any other option for me yet?

jackgan said:
I haven't heard back from you for a while. I did tried your suggestion with ODIN but that doesn't work. Do you have any other option for me yet?
Click to expand...
Click to collapse
Really sorry I missed your previous post. Have you tried to ODIN a custom recovery? Download this and flash with ODIN, then try to boot to recovery.
http://www.mediafire.com/download/05sczh30v7f96q8/Note2-CWM-6.0.4.3-SGH-T889.tar
If you can get to recovery, follow the instructions in my ROM thread for wiping. If you want to give my ROM a try, download the D edition. The wifi will work no matter what bootloader you currently have installed. You'll have to take out your sd card and get the ROM file on there with another device before you proceed.
http://forum.xda-developers.com/showthread.php?t=2631278
This is a T-mobile stock, rooted and debloated ROM. There is a link in the thread for the stock 4.3 modem to flash too in case you need that. Put that on your sd card too.

EdKeys said:
Really sorry I missed your previous post. Have you tried to ODIN a custom recovery? Download this and flash with ODIN, then try to boot to recovery.
http://www.mediafire.com/download/05sczh30v7f96q8/Note2-CWM-6.0.4.3-SGH-T889.tar
If you can get to recovery, follow the instructions in my ROM thread for wiping. If you want to give my ROM a try, download the D edition. The wifi will work no matter what bootloader you currently have installed. You'll have to take out your sd card and get the ROM file on there with another device before you proceed.
http://forum.xda-developers.com/showthread.php?t=2631278
This is a T-mobile stock, rooted and debloated ROM. There is a link in the thread for the stock 4.3 modem to flash too in case you need that. Put that on your sd card too.
Click to expand...
Click to collapse
I tried flash the CWM recovery with ODIN but my phone start bootlooping and cannot get into original recovery again. I believe my phone's motherboards is damage in some way that cause the internal storage fail to be detected. Do you think putting in a new motherboard will work? I search on ebay and it's like $80 for a new working motherboard.