Database Develop

!SOLVED! Vibrant Internal Memory application storage 0b, please help!

!PROBLEM SOLVED!
Hi there,
I hope I am posting in the right place, I hate clutter. I also hope there is something that can be done about this:
I was trying to install a ROM and as usual I used ODIN to go back to stock (JFD) and from there on I would use the One Click Root and then via ClockWork flash the ROM I wanted to try.
This time the ROM said (yes, it was talking) that some partition had not enough space. So, when I went back to ClockWork I saw an option to Partition the drive.. so I did that, and from then on only nightmares...
Nothing would flash properly, even via ODIN. I would get error message about MBR not being able to mount and such. After countless hours of black screen after the Galaxy S logo I finally managed to get a Eugene ROM flashed via ODIN, but now I have a new issue - I cannot install anything, no Titanium, no ClockWork, because my Application Storage is 0B. My external SD is its normal size (a 16GB card, shows 14.83 I think), but the internal storage is 14GB or so and there is virtually NO Application Storage..
* I tried re-flashing things - nothing works other than the Eugene ROM. No JFD, no JI6, nada..
* Would not manage to use an update.zip from the manual recovery (I get the stock Samsung Recovery, it sucks!)
* Cannot install ClockWork and try to fix it from there (or flash another rom via CWR)
* I tried to re-partition via ODIN - no dice.
* I tried to re-partition with Partition Magic (I know... that was my desperate attempt at 1 am after 14 hours of struggle) and it doesn't seem to work (duh).
I am out of ideas and I could really use some help. Did anyone have this issue and what was the solution?

I had this issue, I don't remember the exact steps but I do remember I used "parted" to repartition.
http://forum.xda-developers.com/showthread.php?t=1046220
edit: I remembered: delete the smaller partition, then ODIN to stock w/ repartition checked, and you should get you app storage back.

Thank you, I will give it a try and let you know how it goes! Much appreciated!
german103 said:
I had this issue, I don't remember the exact steps but I do remember I used "parted" to repartition.
http://forum.xda-developers.com/showthread.php?t=1046220
edit: I remembered: delete the smaller partition, then ODIN to stock w/ repartition checked, and you should get you app storage back.
Click to expand...
Click to collapse

german103 said:
I had this issue, I don't remember the exact steps but I do remember I used "parted" to repartition.
http://forum.xda-developers.com/showthread.php?t=1046220
edit: I remembered: delete the smaller partition, then ODIN to stock w/ repartition checked, and you should get you app storage back.
Click to expand...
Click to collapse
Okay, no idea to use "parted". I did download the zip file with the six little guys, but now what? Android SDK? Oh my... no clue...
Any chance for a step by step?

So I download the Android SDK and got the 6 files into the "tools" directory, but now I have no idea what to do...
UPDATE: Okay, I managed to get the ADB going, but when I try to push them files with the command it says failed to copy (the path) "Permission denied"

SOLVED!
Guys, problem solved. Here is how in a nutshell:
So, I saw this post - http://forum.xda-developers.com/showthread.php?t=1081732 and although it is for the I9000 I figured I didn't have much to loose anyways. So I did look for EZbase ROM as one of the users suggested (http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/) and got busy. Finding the files was hard (because of expired links and such), but the link above seemed to work.
Once I collected all the files I performed the process just as described (with the partition checked) and ended up with the Galaxy S I9000 boot (instead of Vibrant) and it was in a boot cycle.
Then I managed to bring the phone to Download Mode (key combo is different now, it is power and Vol Up, not as it used to be) and flashed JFD via Odin (checked the re-partition here as well, although I don't know if that mattered).
And a few minutes later I ended up with a working stock Vibrant. The funny thing is that when you boot the device it first shows the I9000 boot image and then switches it to Vibrant (but I really don't give a damn about that).
So there it is! Hope this helps some poor souls who are in the situation I was.
Cheers!
And it worked!

just put a froyo bootloader on an the 1900 will go away

hachaduryan said:
Guys, problem solved. Here is how in a nutshell:
So, I saw this post - http://forum.xda-developers.com/showthread.php?t=1081732 and although it is for the I9000 I figured I didn't have much to loose anyways. So I did look for EZbase ROM as one of the users suggested (http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/) and got busy. Finding the files was hard (because of expired links and such), but the link above seemed to work.
Once I collected all the files I performed the process just as described (with the partition checked) and ended up with the Galaxy S I9000 boot (instead of Vibrant) and it was in a boot cycle.
Then I managed to bring the phone to Download Mode (key combo is different now, it is power and Vol Up, not as it used to be) and flashed JFD via Odin (checked the re-partition here as well, although I don't know if that mattered).
And a few minutes later I ended up with a working stock Vibrant. The funny thing is that when you boot the device it first shows the I9000 boot image and then switches it to Vibrant (but I really don't give a damn about that).
So there it is! Hope this helps some poor souls who are in the situation I was.
Cheers!
And it worked!
Click to expand...
Click to collapse
No dice. Didnt work for me

hachaduryan said:
Guys, problem solved. Here is how in a nutshell:
So, I saw this post - http://forum.xda-developers.com/showthread.php?t=1081732 and although it is for the I9000 I figured I didn't have much to loose anyways. So I did look for EZbase ROM as one of the users suggested (http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/) and got busy. Finding the files was hard (because of expired links and such), but the link above seemed to work.
Once I collected all the files I performed the process just as described (with the partition checked) and ended up with the Galaxy S I9000 boot (instead of Vibrant) and it was in a boot cycle.
Then I managed to bring the phone to Download Mode (key combo is different now, it is power and Vol Up, not as it used to be) and flashed JFD via Odin (checked the re-partition here as well, although I don't know if that mattered).
And a few minutes later I ended up with a working stock Vibrant. The funny thing is that when you boot the device it first shows the I9000 boot image and then switches it to Vibrant (but I really don't give a damn about that).
So there it is! Hope this helps some poor souls who are in the situation I was.
Cheers!
And it worked!
Click to expand...
Click to collapse
So it seems that there are easier methods to solve this issue now.. glad you worked this out

Need help with internal storage!

Well guys....i think this problem stems from me prematurely removing the usb cord. I Understand that. But here is the other couple of predicaments. lol Ok i'm on ICS Stunna 4.3 ......well after something went wrong i'm unable to "repair" my internal storage. Everything still works smooth....but i can't add things to my internal card. Every time i hook up to the computer it says it needs to scan and fix the card.Well the problem is starts to fix it.....but never does....progress bar never finishes. Tried this on 3 different computers. Nothing.So try to install a different rom....i have some on my internal and external. Always aborts in cmw....never finishes. So on top of all this Stunna has started acting odd. Likely read errors.....but problem is i can't switch roms! lol I have tried everything. I was wondering should i format both cards? But if i do that how can i back everything up if i can't access my card? Any help would be appreciated guys. Hoping i don't have to Odin back to stock.
Cliffs- Internal storage won't repair on any computer-Can't install anything in CMW because of it

I have the exact same problem now, as you do. CWM can't install any .zip files, I can't flash Abyss kernel, so it's just stuck in that end.
I installed ICS Stunner 4.5 coming from GB with full wipe. This happened to me after I tried to copy some files over to external SD Card and it failed, seemed like the phone froze (SOD), so I figured flashing another modem would do the trick (read it in ICS Stunner thread's 1st post). Tried to transfer the file over a cable, but same thing happened. After rebooting I just grabbed it from dropbox and installed the modem successfully. I went ahead to try and fix the mounting problem, so I plug in the cable and it offers me to scan and fix both partitions (internal and external). External card finishes successfully, but not the internal one. And after that I'm in the same situation as OP.
Any ideas anyone?

Enable usb debugging(setting-appl-development)
Connect to pc
Select to copy file to fr computer from notification
You will find separate drive letter for int n ext card
Rt click on int sd card letter n format(you can backup imp data to pc b4 this)
Hope it shud b fixed
Sent from my GT-N7000 using xda premium

Gonna try it now. Have lots of pictures to backup first tho
EDIT: Same thing happens as with scan and fix procedure. It starts and just sits there, nothing happens. When I try to stop "USB Storage in use" it just shows the spinner and hangs in there. Only holding the power button helps solve this. My guess is something in the internal SD card partition is broken... just can't say what or how to fix it.

OrangGeeGee said:
Gonna try it now. Have lots of pictures to backup first tho
EDIT: Same thing happens as with scan and fix procedure. It starts and just sits there, nothing happens. When I try to stop "USB Storage in use" it just shows the spinner and hangs in there. Only holding the power button helps solve this. My guess is something in the internal SD card partition is broken... just can't say what or how to fix it.
Click to expand...
Click to collapse
Same problem^^^^ Not sure what to do about all this

Short story:
Formatting didn't work.
Long story:
Okay, so following the idea to format the internal sd card's partition, I achieved it not through Windows format dialog, but through the half-broken CWM. Both my SD Cards were formated (internal and external) in the process. So since I used the external one for backing up important info I had to use [email protected] UNDELETE to get it back (after booting to ICS). In the process the native SD Card mount service seemed like broken, I had to perform a few hard resets. Hangs seemed to occur whenever I tried writing to one of the cards. I downloaded multi-mount SD card app from Play Store and transfered AbyssKernel's .zip and now when I try to install it from CWM it says
Installing: /sdcard/AbyssNotekernel42RedTouchOriginalLogo.zip
Finding update package...
Opening update package...
Installing update...
Click to expand...
Click to collapse
And that's it... so basically back to the start. Any more ideas?

Please help if you have any ideas on what might work. Us 2 guys are in trouble...lol

I don't know if this will help or not but give it a try.
Enter into the download mode and flash any stock firmware using PC Odin. This way you don't need to access any of the cards. After flashing stock ROM, try fixing the internal SD again and if it still doesn't fix, send in your note to Samsung for repairs.
Sounds too simple to be working though but worth a shot.
Sent from my GT-N7000 using XDA

Well for now the phone works, but it's stuck on ICS Stunner. I was thinking to use PC Odin or Mobile ODIN, but what if it doesn't work because the partition is corrupted in some way (as it is now, because CWM can't flash anything).
I'd like to hear more insight before I go the odin-way

OrangGeeGee said:
Well for now the phone works, but it's stuck on ICS Stunner. I was thinking to use PC Odin or Mobile ODIN, but what if it doesn't work because the partition is corrupted in some way (as it is now, because CWM can't flash anything).
I'd like to hear more insight before I go the odin-way
Click to expand...
Click to collapse
I'm about to go ahead and give in to odin....lol I'll keep you updated

OrangGeeGee said:
Well for now the phone works, but it's stuck on ICS Stunner. I was thinking to use PC Odin or Mobile ODIN, but what if it doesn't work because the partition is corrupted in some way (as it is now, because CWM can't flash anything).
I'd like to hear more insight before I go the odin-way
Click to expand...
Click to collapse
Check out this reply from anti. This is the fix using the pit file option. Try Odin flashing of stock rom....but m doubtful it will work. Fingers crossed!! Hope it gets well for you both
http://forum.xda-developers.com/showpost.php?p=24783218&postcount=3306

Twistedchild420 said:
I'm about to go ahead and give in to odin....lol I'll keep you updated
Click to expand...
Click to collapse
I'm downloading an old GB rom myself..
While I am, I can share a thought: I feel that ICS is not yet ready.. at least not for me. Feels nice and fast but buggy USB transfers is a big no-go for me. Also after trying AOSP derived ROM, I decided to wait for a good Samsung edition ICS because all the little tweaks add a good feeling to the experience, I tend to miss them on AOSP or AOKP or w/e
abhisahara said:
Check out this reply from anti. This is the fix using the pit file option. Try Odin flashing of stock rom....but m doubtful it will work. Fingers crossed!! Hope it gets well for you both
http://forum.xda-developers.com/showpost.php?p=24783218&postcount=3306
Click to expand...
Click to collapse
Oooh thanks! Didn't know this. So now I'm pretty confident because if flashing conventionally fails I'll just repartition and get rid of all the partition errors. What do you know, I feel like I learned something new today

SOB! Just did the whole Odin to stock thing and i am stuck in a bootloop! lol

I think my problem is used a .tar instead of .pit.....where can i get the .pit?

Ye same happened to me. Reboot to recovery (volume up + home + power) and do a data wipe/factory reset. After that it boots. Rooted and flashed CWM just fine after that, copying my old GB nandroid backup to SD card as I write

OrangGeeGee said:
Ye same happened to me. Reboot to recovery (volume up + home + power) and do a data wipe/factory reset. After that it boots. Rooted and flashed CWM just fine after that, copying my old GB nandroid backup to SD card as I write
Click to expand...
Click to collapse
Thanks man! That worked!

Twistedchild420 said:
Thanks man! That worked!
Click to expand...
Click to collapse
Glad it helped!
Too bad for me, since I had recovered the latest nandroid with undelete software (cus external sd was accidentally formatted) and now I'm getting a MD5 mismatch Guess I might as well start fresh now, since the last good backup is like 2 months old... Another lesson for me.. always keep your nandroids safe

So everything fine now??
Sent from my GT-N7000 using XDA

sujal said:
So everything fine now??
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Yeah. After quite a time of failed attempts we succeeded. ODIN > Stock GB ROM > ROOT + CMW > Anything you like. No re-partitioning was needed in the process

i have same problem but more complicated. iam on stock GB and its happened after flash bad kernel
the case in detail's :
i flashed wrong kernel on my device previously and now when iam trying to flash another kernel even use ODIN or CWM everything going well and completed but when check i found the old kernel still. i tried many times with same results and no error .
- system can read/write/mount the internal memory but the new pasted files deleted after restart. external card behave normal and i can preform flash using files pasted on it.
- in CWM wipe/format/flash operations running well but no effect on device even restarted to CWM only.
- device has yellow triangle. is it effected?
- the devil kernel stacked in machine is 2.6.35.7-gb4846d2 [email protected] #2 and the build no. is jpkj4
system running normal but cannot keep any changes i do if restarted.
-system rooted and no problem with root
-can access adb
- ODIN behave same CWM, operation work but no change.
can anyone help me guys?
i did repartition the memory useing PIT for note butno change also
thank you all in advance

[Fixed] odin stuck on system.img.md5

Hi im trying to return galaxy 8.9 tablet back to stock using odin, but it gets stuck at system.img.md5 and wont move...is there any way to fix.. tried switching usb ports and no luck...please need help
alrigh... alrigh... alriiiight got it to work after almost 5 days with out a tablet....which i really missed... I finally fixed the god damn issues with this stupid thing.....
with odin constantly hanging on system.img i had to work around it...
first got odin far enough into system.img to were cwm would work
second i adb into the tablet and pushed rom file into sdcard
third i installed rom and finally got my tablet back
yessss
also learned how to open tablet and pull the battery out....which i didn't need to do at all

What is your recent history in terms of Rom & recoveries installed, other errors encountered... ?
Did you do any formats, wipes, factory resets, and if so, in what environment (android, recovery, adb, ...)
---------- Post added at 09:07 AM ---------- Previous post was at 09:06 AM ----------
Have you tried simple options like restarting the pc, reinstalling tab's drivers, ...

Apologies, not relevant to this post

whisperingforce said:
... reverted back to honeycombe 3.2. The problem i have is that it now will not let me access or set up my google account. I have been unable to go back to stock.
Kies is also not recognising my tablet.
Click to expand...
Click to collapse
This is completely unrelated! Pls create your own thread, or search for a topic that's actually similar to yours, instead of trampling over another...

sonko2k said:
Hi im trying to return galaxy 8.9 tablet back to stock using odin, but it gets stuck at system.img.md5 and wont move...is there any way to fix.. tried switching usb ports and no luck...please need help
Click to expand...
Click to collapse
I had the same issue after upgrade to US stock ICS and attempt to install CWM recovery resulted in a tablet that would not boot. Rebooted into recovery mode, rebooted from there to download mode and tried the Odin flash again using the US stock ICS. Each time I did this it got a bit further (as indicated by the download bar on the tablet screen) and eventually it succeeded. I am no expert so I completely fail to understand why this worked but it did.

fred_be9300 said:
What is your recent history in terms of Rom & recoveries installed, other errors encountered... ?
Did you do any formats, wipes, factory resets, and if so, in what environment (android, recovery, adb, ...)
---------- Post added at 09:07 AM ---------- Previous post was at 09:06 AM ----------
Have you tried simple options like restarting the pc, reinstalling tab's drivers, ...
Click to expand...
Click to collapse
okay so recent..... rom was ics 4.0.4 version 3 uploaded by safariking...had ClockworkMod Recovery v5.5.0.4.... and yes i formatted ,wiped, and factory restarted, all in clockwork recovery... i have restarted the pc and reinstalled drivers and got a little bit further but odin still gets stuck... tried to restore with backup but get E: cant mount /sdcard/

sonko2k said:
okay so recent..... rom was ics 4.0.4 version 3 uploaded by safariking...had ClockworkMod Recovery v5.5.0.4.... and yes i formatted ,wiped, and factory restarted, all in clockwork recovery... i have restarted the pc and reinstalled drivers and got a little bit further but odin still gets stuck... tried to restore with backup but get E: cant mount /sdcard/
Click to expand...
Click to collapse
Just like i said before.. In warning: Do not wipe or anything related to that if youre in ICS..
With stock kernel or stock recovery or One of them but you still in stock ICS boot.img wiping is risky..
if you use a safe recovery but your boot.img is not safe. ..or your boot.img is safe but recovery.img isnt. .
Your still have the emmc bug risk..
Stuck on system.img means odin not recognized your system partition.. Maybe corrupted or faulty..
Please read my warning in general section..

suwandiapr said:
Just like i said before.. In warning: Do not wipe or anything related to that if youre in ICS..
With stock kernel or stock recovery or One of them but you still in stock ICS boot.img wiping is risky..
if you use a safe recovery but your boot.img is not safe. ..or your boot.img is safe but recovery.img isnt. .
Your still have the emmc bug risk..
Stuck on system.img means odin not recognized your system partition.. Maybe corrupted or faulty..
Please read my warning in general section..
Click to expand...
Click to collapse
so is my tab bricked or is there any other way

fixed

sonko2k said:
fixed
Click to expand...
Click to collapse
For others who may have this problem in the future, how did you fix it?

boscorama said:
For others who may have this problem in the future, how did you fix it?
Click to expand...
Click to collapse
First post

How did you get the battery out?

orlandoxpolice said:
How did you get the battery out?
Click to expand...
Click to collapse
i took a thin box cutter blade and ran it around the edge of the screen while gently pushing out and pulling up... the screen easily separates from the back cover.... behind the screen is a white battery with small mutil colored wires...gently pull up the wires from the mainboard..... battery is now disconnected.... to put back just push those wires back down onto its connectors....
to completely remove there are screws running along the battery... and two ribbons...detach ribbons and unscrew battery

same problem
i have the same problem how do u use adb to install rom?
or what do u use to install rom,adb or odin? and what procedure do you do? please reply immediately..thanks

See my signature

This thread saved my ass. I too was stuck at the system.img.
Tried to restore using ADB but no joy. I was still able to access the download mode so kept trying ODIN.
It turned out to be my USB 3.0 ports on my laptop.
As soon as I used my USB 2.0 ports on my docking station ODIN worked fine!:laugh:

gutomlagi said:
i have the same problem how do u use adb to install rom?
or what do u use to install rom,adb or odin? and what procedure do you do? please reply immediately..thanks
Click to expand...
Click to collapse
if odin hangs up halfway through the process, what u have to do is install stock recovery through odin.... then go in to recovery and format data...go back to odin and install clockwork recovery.... go back into recovery and mount system and mount data... next download a app called quick adb pusher on to pc select the rom u want to push... under destination type /data/media/ press send and install ur rom

Failed with Odin 3.09, worked with Odin 3.07
I don't know if this will help.
I needed to re-flash my SM-T310 with the Kitkat 4.4.2 Stock ROM. I found a page suggesting I used Odin 3.09 and the stock ROM pointed to from the Samsung site. I started the load, and saw the same problem, my Odin Log looked just like the one posted earlier. Out of sheer desperation, I started again using the version of Odin (3.07) I had previously used to load TWRP.
And it worked perfectly. Loaded the various components, rebooted, came up with the initial screen ... Phew !!
Maybe I just had some sort of nasty glitch, maybe Odin 3.07 is a bit less picky (!) I have no idea. All I know is it worked for me !!

I had this same problem - got stuck on system.img very near the end, stayed there for hours. Finally fixed it by attaching the usb cable to a different port *d'oh*

same problem stuck in system.img
sonko2k said:
Hi im trying to return galaxy 8.9 tablet back to stock using odin, but it gets stuck at system.img.md5 and wont move...is there any way to fix.. tried switching usb ports and no luck...please need help
alrigh... alrigh... alriiiight got it to work after almost 5 days with out a tablet....which i really missed... I finally fixed the god damn issues with this stupid thing.....
with odin constantly hanging on system.img i had to work around it...
first got odin far enough into system.img to were cwm would work
second i adb into the tablet and pushed rom file into sdcard
third i installed rom and finally got my tablet back
yessss
also learned how to open tablet and pull the battery out....which i didn't need to do at all
Click to expand...
Click to collapse
i dont get it what you are talking about like cwm and adb without any logic my phone is bricked and i need your help my flash just stuck in system.img
did you have any idea then please give a reply
..............

[Q] Flash CWM via SD update in stock recovery problems T679

Hello all and thank you in advance for any help you can provide. I'll try not to post a wall of text.
In a nutshell the problem I'm having is - I cannot see my zip files in the stock recovery console under the sd update section. In fact it's like the sad card isn't seen at all. I've taken a zip of cwm, placed it on an sd card, inserted the card, boot into recovery and no zip file is seen. What I'd like is any and all details (perhaps a short tutorial with links to the right files) on how to do this.
Why? - well here's where it gets funny. Old android phone of mine I thought to be dead suddenly springs to life (sweet). It has a pattern lock which I don't remember (not sweet). Tried using google account, apparently I used a different one than the one I've been using for years... The short of it is I'd like to get my data off it or at least see what's there. I've heard I can flash cwm through the recovery console, then via cwm, flash a pattern lock reset (in theory). So I figured I'd give it a go. I hope I explained this well. Any help you guys can provide will be awesome. Thanks!
More info on the phone - no it's not setup for debugging mode. No I cannot access it via the PC. So adb and Odin are out. Also I know I can factory reset easily - not looking to do that though. Thanks again!

The stock recovery only sees the "Internal" SD card, so anything you put on your actual SD will not be detected by the recovery. Download a file manager from google play store. I don't remember which one I used in particular, but try Root Browser or ES File Manager. Copy the file from your External SD card into the Internal SD and try again. Hope this helps.
But... you say you don't know the password to the phone. I'm not sure what can be done besides factory reset...

hadriel821 said:
More info on the phone - no it's not setup for debugging mode. No I cannot access it via the PC. So adb and Odin are out. Also I know I can factory reset easily - not looking to do that though. Thanks again!
Click to expand...
Click to collapse
I don't think you can flash cwm with stock recovery. If you aren't able to flash via Odin in download mode you are pretty short on options.

meekrawb said:
I don't think you can flash cwm with stock recovery. If you aren't able to flash via Odin in download mode you are pretty short on options.
Click to expand...
Click to collapse
You can actually. That's how I did it. When I got this phone the USB to PC connection never worked, only for charging. I was disappointed that I'd be stuck with stock ROM, but I was able to install CWM via Stock Recovery.

Jorge_007 said:
You can actually. That's how I did it. When I got this phone the USB to PC connection never worked, only for charging. I was disappointed that I'd be stuck with stock ROM, but I was able to install CWM via Stock Recovery.
Click to expand...
Click to collapse
Thanks for confirming. Sucks that the OP can't get it onto the internal, then.

If you google "a creative way to bypass pattern lock on android" the first result will show you where I got the idea from. (sorry, would have put a link here but the site won't let me)
that being said, unless the OP there is pulling our legs, it should be completely possible to access the external SD card from stock recovery as that's how he described he did it. now I don't know if stock recovery is the same on all Samsung android devices, but I would assume it likely is, or is at least close.
I'm almost sure if I had another t679 that I could get into, that I could format the card and have it work on the locked one. not sure if it's worth it to me though since at this point I'm mainly pursuing this for personal knowledge and notoriety lol. BTW thanks to all that provided insight thus far. here's to hoping someone has some additional information for me.

bricked....

Hi so I was trying to use CF to root my phone and ended up screwing it somehow and bricked. I thought I'd followed the instructions well enough but I obviously did something wrong. Now my phone is stuck saying it needs to recover with Kies. This is my first Samsung phone but I'm not new to Android.
I tried installing the stock firmware through ODIN but everytime I flash it gets to installing the system ext4 and fails. I also wasn't able to recover using Kies(not even sure how you use it tbh).
If anyone could help me it would be mucho appreciated. I'm pretty pissed at myself right now.

re: not bricked
cronos1388 said:
Hi so I was trying to use CF to root my phone and ended up screwing it somehow and bricked. I thought I'd followed the instructions well enough but I obviously did something wrong. Now my phone is stuck saying it needs to recover with Kies. This is my first Samsung phone but I'm not new to Android.
I tried installing the stock firmware through ODIN but everytime I flash it gets to installing the system ext4 and fails. I also wasn't able to recover using Kies(not even sure how you use it tbh).
If anyone could help me it would be mucho appreciated. I'm pretty pissed at myself right now.
Click to expand...
Click to collapse
Your phone is NOT bricked. If it was the screen would not even go on.
Have you tried going into recovery mode (VolumeUP/VolDown/PowerButton)
and once in Recovery Mode do a factory reset or Data Reset forgot what the
exact wording is in the stock recovery.
If you flashed twrp recovery it's ok too, just select "factory reset".
After doing that the phone should no longer display anything about Kies.
If you get to the twrp recovery screen you should be able to flash a stock
rooted rom without any issues.
If all you get is the stock recovery screen then you should be able to odin
flash the official Samsung Note 4 kitkat 4.4.4 NJ7 firmware which you may
need to download the firmware from http://SamMobile.com if you don't
already have it. (be sure you have the correct firmware for the Note 4 N910T).
Be 100% sure that the phone is FULLY POWERED DOWN before going
into Download Mode to avoid odin errors and issues.
Good luck!

Thanks man. I had tried Odin at my office and nothing doing.
Got home took my time and was real calm about things and voila. May have been an md5 issue with the firmware file. Just relieved I didn't have to RMA it.

cronos1388 said:
Thanks man. I had tried Odin at my office and nothing doing.
Got home took my time and was real calm about things and voila. May have been an md5 issue with the firmware file. Just relieved I didn't have to RMA it.
Click to expand...
Click to collapse
Can you check for the file with md5 before you flash from your phone? I forgot where to dig for this info.
All I I have done before is on my cook rom file, I just open it with WinRAR and test for error. If no error, then its good.

On my Home PC I have a program that will put a check mark next to a file if it matches the md5. I also have Winrar at home.
I was just using the default Windows zip program and I have had problems with that and installers/roms in the past.
The only other things I did different were I removed the SD card and installed the drivers before plugging my phone in instead of letting Windows download them automatically.
I also removed the battery after I left work so it was out of the phone for a couple of hours.
The final thing I did was calm down lol after the initial shock of seeing a softbricked screen on my brand new phone.
I'm all rooted now with TWRP and running Hyperdrive so it's all smooth sailing from this point forward.

You should check md5 on phone once you done transferred to phone from PC
BAD ASS NOTE 4