Related
Hello!
First of all I've searched all the posts about this problem.. and personally I can't fix it.
So here is what I've done to brick my Galaxy Note GT-N7000 (I think that's called a non-usable device).
Installed few ROMs and finally after taking some decisions I've returned back on ICS 4.0.3 (Flashed with ODIN 1.85).
Restored EFS with kTool (because ClearNotev5 did something wrong with my phone.. and discovered after few hours that I can restore EFS).
Updated ICS 4.0.3 to 4.0.4 using WIFI (OTA I think it's called) and BANG after restart phone stucked at Bootscreen.
So from yesterday untill now I've restored my phone to factory settings few times(GB 2.3.5 & 2.3.6/ICS 4.0.4),repartitioned with .pit files for N7000 16GB,installed different custom/stock ROMs and nothing.
I've discovered few minutes ago while triyng to make a factory restore (GB 2.3.5) that my phone stucked at data.img... I've read about this and it is said that I must change my N7000 motherboard.. I have no warranty so please help.. and sorry for my bad english
Read many times about ota harbrick, i think its not advisable to use ota for upgrade. Sorry for your loss.
Flash gb in pc odin, if sucessfull and still stuck in logo go to CWMR and perform 3 wipes. This is all advise i can give you.
And try different gb rom.
allexsava said:
So from yesterday untill now I've restored my phone to factory settings few times(GB 2.3.5 & 2.3.6/ICS 4.0.4),repartitioned with .pit files for N7000 16GB,installed different custom/stock ROMs and nothing.
I've discovered few minutes ago while triyng to make a factory restore (GB 2.3.5) that my phone stucked at data.img...
Click to expand...
Click to collapse
^^
I think you had already tried the recovery method from a bricked device. So if you still facing problems you have to change the MB.
OTA Brick or Soft Brick?
I still haven't fix it but here is what I want:
Can someone give me different versions of GB (I've tried only one with CSC,MODEM but this now stops at data.img..) :crying:
I have to make a repartition to my phone? Will that help?
And can someone guide me through a tutorial step by step on how to revive my phone from EMMC Bug..?
PS: When I try to wipe data in CWM (using Hydracore Kernel v2.0b STD) with ICS 4.0.4 (Stock) my N7000 stucks,same for installing CleaNotev5.0 (stucks at Extracting\System).. But what is curios is that, I can clear Dalvik Cache and Cache, I can install Kernels and run N7000 in DOWNLOAD/CWM or stock Restore mode.
Any solutions?Please help..
allexsava said:
I still haven't fix it but here is what I want:
Can someone give me different versions of GB (I've tried only one with CSC,MODEM but this now stops at data.img..) :crying:
I have to make a repartition to my phone? Will that help?
And can someone guide me through a tutorial step by step on how to revive my phone from EMMC Bug..?
PS: When I try to wipe data in CWM (using Hydracore Kernel v2.0b STD) with ICS 4.0.4 (Stock) my N7000 stucks,same for installing CleaNotev5.0 (stucks at Extracting\System).. But what is curios is that, I can clear Dalvik Cache and Cache, I can install Kernels and run N7000 in DOWNLOAD/CWM or stock Restore mode.
Any solutions?Please help..
Click to expand...
Click to collapse
You can try the post here :
http://forum.xda-developers.com/showthread.php?t=1667886&highlight=emmc
Just follow the step there.
I've experienced before, and revive it using this method. So far mine still work well, and no further error ever since.
You will loose certain GB on your internal storage. Which for me it's not a big deal. I'm kinda lazy to go to samsung repair center, unless my phone is totally dead.
Here is my step (follow at your own risk) :
1. You have to know first your N7000 is the 16GB or 32GB, and then you download the correct pit for your phone.
2. After you download, extract the zip file.
3. Since mine is the 16GB, I've picked this pit file to use (inside the zip) : Q1_20110914_16GB-patched-regain-0102400-kB.pit (the pit file will be vary depending on which sector your phone brick)
4. Put your phone on to download mode.
5. Open ODIN PC and connect your phone, and wait till ODIN say "Added" and you see that your phone has connected.
6. Put the patch pit file I choose, then put the samsung stock rom as the PDA (if you downloaded 1 file only for the stock ROM, if not, put properly for the PDA, Phone, and CSC).
7. Check ON the "repartition", "Auto-reboot", "F-reset time"
8. Click Start, and wait till the process has finished. Your phone should auto reboot by then.
9. My phone has recovered, and I lost 1GB internal storage.
One last thing, try not to do wipe on ICS, unless you are on a safe kernel like speedmod / GLNotecore.
For Hydracore (You may check with the developer), I haven't tested it yet for wiping. But for those speedmod and GLNotecore, is confirm safe kernel. I've tried these 2 for wiping.
PS : if you are not sure with my step on reviving with the pit file, I suggest you to read the link above from the OP for the pit revive method.
Good Luck !
antique_sonic said:
You can try the post here :
http://forum.xda-developers.com/showthread.php?t=1667886&highlight=emmc
Just follow the step there.
I've experienced before, and revive it using this method. So far mine still work well, and no further error ever since.
You will loose certain GB on your internal storage. Which for me it's not a big deal. I'm kinda lazy to go to samsung repair center, unless my phone is totally dead.
Here is my step (follow at your own risk) :
1. You have to know first your N7000 is the 16GB or 32GB, and then you download the correct pit for your phone.
2. After you download, extract the zip file.
3. Since mine is the 16GB, I've picked this pit file to use (inside the zip) : Q1_20110914_16GB-patched-regain-0102400-kB.pit (the pit file will be vary depending on which sector your phone brick)
4. Put your phone on to download mode.
5. Open ODIN PC and connect your phone, and wait till ODIN say "Added" and you see that your phone has connected.
6. Put the patch pit file I choose, then put the samsung stock rom as the PDA (if you downloaded 1 file only for the stock ROM, if not, put properly for the PDA, Phone, and CSC).
7. Check ON the "repartition", "Auto-reboot", "F-reset time"
8. Click Start, and wait till the process has finished. Your phone should auto reboot by then.
9. My phone has recovered, and I lost 1GB internal storage.
One last thing, try not to do wipe on ICS, unless you are on a safe kernel like speedmod / GLNotecore.
For Hydracore (You may check with the developer), I haven't tested it yet for wiping. But for those speedmod and GLNotecore, is confirm safe kernel. I've tried these 2 for wiping.
PS : if you are not sure with my step on reviving with the pit file, I suggest you to read the link above from the OP for the pit revive method.
Good Luck !
Click to expand...
Click to collapse
Thank you for this magnific guide but.. I got one question? How do I know wich sector on my phone is bricked? Is there a tool to flash or something? Can you simplify for me because here(http://forum.xda-developers.com/show...highlight=emmc) it's to complicated for me
Find your gb rom here. http://forum.xda-developers.com/showthread.php?t=1424997
No more option left, for mmc cap erase brick, go here. Pls read carefully. http://forum.xda-developers.com/showthread.php?t=1667886
I've got a problem: I am from Romania and all GB's from Romania are on COSMOSTE and VODAFONE but I'm on ORANGE..Is there a problem to install a VODAFONE/COSMOTE GB?
allexsava said:
I've got a problem: I am from Romania and all GB's from Romania are on COSMOSTE and VODAFONE but I'm on ORANGE..Is there a problem to install a VODAFONE/COSMOTE GB?
Click to expand...
Click to collapse
No problem. Just pick any gb rom, one problem at a time, your problem now is how your phone can boot up.
If you want go to www.sammobile.com and pick your specific rom.
I've downloaded the COSMOTE GB ROM and I will flash it with PC ODIN.
After that I need as I was saying few posts ago how to identify which part of my internal storage is bricked..but a simplified method/guide please.. and sorry for my requests but believe me I'm kinda desperate..
allexsava said:
I've downloaded the COSMOTE GB ROM and I will flash it with PC ODIN.
After that I need as I was saying few posts ago how to identify which part of my internal storage is bricked..but a simplified method/guide please.. and sorry for my requests but believe me I'm kinda desperate..
Click to expand...
Click to collapse
You may refer to this post.
http://forum.xda-developers.com/showthread.php?t=1823918
The OP stated very clear on how to get the part of your bricked storage.
After emmc_find_brick_start.zip I get stucked on:
scanning 1167 Mib = 1224 MB ... (picture below)
And now I am waiting emmc_find_brick_end.zip to get stuck
LE: emmc_find_brick_end.zip stuck at:
scanning 3356 MiB = 3520 MB ... (picture below)
allexsava said:
I've got a problem: I am from Romania and all GB's from Romania are on COSMOSTE and VODAFONE but I'm on ORANGE..Is there a problem to install a VODAFONE/COSMOTE GB?
Click to expand...
Click to collapse
Shouldn't be a problem. However, best to root current, then efs backup multiple locations. See dr ketans toolbox thread on how.
Your phones csc is also Romania? Best to stick with your phones csc and those country roms if you want to continue ota/kies updatability in the future Dial *#06# for emei and then *#272*yourimeihere# to find out 3 letter csc.
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Shouldn't be a problem. However, best to root current, then efs backup multiple locations. See dr ketans toolbox thread on how.
Your phones csc is also Romania? Best to stick with your phones csc and those country roms if you want to continue ota/kies updatability in the future Dial *#06# for emei and then *#272*yourimeihere# to find out 3 letter csc.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
If I can boot up my phone I'll consider your reply
allexsava said:
If I can boot up my phone I'll consider your reply
Click to expand...
Click to collapse
goodluck booting!
Sent from my GT-N7000 using Tapatalk 2
SOLVED
:fingers-crossed: Sorry for late response guys but yeah I've fixed it by patching the right .pit file and got only 8,83 GB internal memory.. Flashing CriskeloRomNOTE.vICS-V11.2 and HydraCore v3.5 STD.. I've got few problems with ROM, suddenly stuck in different situations but again yeah.. I'm happy I didn't changed my MB ..if someone got some ideas why it stucks please reply
At least you dont have to pay for mobo which is 200 dollars.
Sent from my GT-N7000 using xda premium
if you get succesful flash of gb then stay on it don't upgrade to ics.. "something is better then nothing"
Sent from my GT-N7000 using Tapatalk 2
Thank you all for the support
Sent from my GT-N7000 using xda premium
Hi,
I'm a newbee around here and I would really appreciate if someone could help me on this.
My GT-I9070 was fully functional till yesterday. I've been running CM10.2. Yesterday I tried to change the Kernal to Co-Core 8.2. I deeply regret doing that because I didn't had enough knowledge on how to change kernals. What I did was copied the Co-Core zip file to sdcard and applied it via CWM. After that, my phone restarted and it was stuck on the CM boot screen. I got mad and flashed the phone to stock 4.1.2 using ODIN. Then the setup wizard showed up and it kept on crashing giving me toasts, "gapps not working" and "setup wizard has unfortunately stopped".
I then went to stock recovery mode and the log said,
E:failed to mount /efs (No such file or directory)
E:failed to mount efs (Invalid argument)
Applying Multi CSC..
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs Multi csc applied failed
I searched on n number of threads here in XDA about this problem and read in one thread that IMEI could've corrupted.
Then using ODIN, I flashed my mob to stock GB 2.3.6 with DDLD4 baseband. Then everything worked perfect. Phone booted up and was working perfect. But then I tried to update the phone to 4.1.2 via KIES, the KIES said "This phone can't be upgraded".
I again flashed 4.1.2 using ODIN, again it said gapps and setup wizard unfortunately stopped. I tried installing CM10.1, CM10.2, MIUI but in all cases, it got stuck on the bootscreen of each ROM. I flashed back to stock GB again and phone is working perfect now. When I go to "about phone", IMEI is showing with no error. It is the same IMEI which the phone had when it was bought. But when I go into recovery mode, it still says "/efs can't be mount". What could be the possible reason for this? How I can I fix this? Is there anyway for me to install the CM ROM again and successfully keep it up and running?
arjunkdas said:
Hi,
I'm a newbee around here and I would really appreciate if someone could help me on this.
My GT-I9070 was fully functional till yesterday. I've been running CM10.2. Yesterday I tried to change the Kernal to Co-Core 8.2. I deeply regret doing that because I didn't had enough knowledge on how to change kernals. What I did was copied the Co-Core zip file to sdcard and applied it via CWM. After that, my phone restarted and it was stuck on the CM boot screen. I got mad and flashed the phone to stock 4.1.2 using ODIN. Then the setup wizard showed up and it kept on crashing giving me toasts, "gapps not working" and "setup wizard has unfortunately stopped".
I then went to stock recovery mode and the log said,
E:failed to mount /efs (No such file or directory)
E:failed to mount efs (Invalid argument)
Applying Multi CSC..
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs Multi csc applied failed
I searched on n number of threads here in XDA about this problem and read in one thread that IMEI could've corrupted.
Then using ODIN, I flashed my mob to stock GB 2.3.6 with DDLD4 baseband. Then everything worked perfect. Phone booted up and was working perfect. But then I tried to update the phone to 4.1.2 via KIES, the KIES said "This phone can't be upgraded".
I again flashed 4.1.2 using ODIN, again it said gapps and setup wizard unfortunately stopped. I tried installing CM10.1, CM10.2, MIUI but in all cases, it got stuck on the bootscreen of each ROM. I flashed back to stock GB again and phone is working perfect now. When I go to "about phone", IMEI is showing with no error. It is the same IMEI which the phone had when it was bought. But when I go into recovery mode, it still says "/efs can't be mount". What could be the possible reason for this? How I can I fix this? Is there anyway for me to install the CM ROM again and successfully keep it up and running?
Click to expand...
Click to collapse
Hi, did you try to flash other firmware?
Flash a new one and try to wipe data/factory reset.
YES, I DID
eduds said:
Hi, did you try to flash other firmware?
Flash a new one and try to wipe data/factory reset.
Click to expand...
Click to collapse
Yes, I mentioned, I tried to flash, CM10.1, CM 10.2 and MIUI also..I also did factory reset and wipe cache. But all of em was stuck on the bootscreen of the respective firmwares. :crying:
arjunkdas said:
Yes, I mentioned, I tried to flash, CM10.1, CM 10.2 and MIUI also..I also did factory reset and wipe cache. But all of em was stuck on the bootscreen of the respective firmwares. :crying:
Click to expand...
Click to collapse
No, I'm talking about original firmwares, not custom ROMs.
DDXL1 and DDLD4
eduds said:
No, I'm talking about original firmwares, not custom ROMs.
Click to expand...
Click to collapse
I flashed both of these baseband versions of GB..and DDULP8 baseband of JB..you want me to try flash more baseband versions?
did u solve it ?
arjunkdas
Click to expand...
Click to collapse
NO
amr diab said:
did u solve it ?
Click to expand...
Click to collapse
Not yet..I've been using GB for the past two months. Tried almost everything that I could find in xda. I'm afraid to go to Samsung SVC because I doubt they won't give me warranty for this problem. Do you have any solution?
arjunkdas said:
Not yet..I've been using GB for the past two months. Tried almost everything that I could find in xda. I'm afraid to go to Samsung SVC because I doubt they won't give me warranty for this problem. Do you have any solution?
Click to expand...
Click to collapse
i have the same problem
and i'm on GB too
i'm still searching every where
check this
http://forum.xda-developers.com/showthread.php?t=2506256&page=2
i will try and if it is solved i will tell u
amr diab said:
i have the same problem
and i'm on GB too
i'm still searching every where
check this
http://forum.xda-developers.com/showthread.php?t=2506256&page=2
i will try and if it is solved i will tell u
Click to expand...
Click to collapse
Ok man! I'm also on it!
arjunkdas said:
Hi,
I'm a newbee around here and I would really appreciate if someone could help me on this.
My GT-I9070 was fully functional till yesterday. I've been running CM10.2. Yesterday I tried to change the Kernal to Co-Core 8.2. I deeply regret doing that because I didn't had enough knowledge on how to change kernals. What I did was copied the Co-Core zip file to sdcard and applied it via CWM. After that, my phone restarted and it was stuck on the CM boot screen. I got mad and flashed the phone to stock 4.1.2 using ODIN. Then the setup wizard showed up and it kept on crashing giving me toasts, "gapps not working" and "setup wizard has unfortunately stopped".
I then went to stock recovery mode and the log said,
E:failed to mount /efs (No such file or directory)
E:failed to mount efs (Invalid argument)
Applying Multi CSC..
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs Multi csc applied failed
I searched on n number of threads here in XDA about this problem and read in one thread that IMEI could've corrupted.
Then using ODIN, I flashed my mob to stock GB 2.3.6 with DDLD4 baseband. Then everything worked perfect. Phone booted up and was working perfect. But then I tried to update the phone to 4.1.2 via KIES, the KIES said "This phone can't be upgraded".
I again flashed 4.1.2 using ODIN, again it said gapps and setup wizard unfortunately stopped. I tried installing CM10.1, CM10.2, MIUI but in all cases, it got stuck on the bootscreen of each ROM. I flashed back to stock GB again and phone is working perfect now. When I go to "about phone", IMEI is showing with no error. It is the same IMEI which the phone had when it was bought. But when I go into recovery mode, it still says "/efs can't be mount". What could be the possible reason for this? How I can I fix this? Is there anyway for me to install the CM ROM again and successfully keep it up and running?
Click to expand...
Click to collapse
i got that problem too. you should flash your .pit file and check repartition in odin.
this solved my problem.
Patlcs said:
i got that problem too. you should flash your .pit file and check repartition in odin.
this solved my problem.
Click to expand...
Click to collapse
Are you saying I have to flash pit file alone? Or do a full flash of GB with repartition checked?
While flashing JB, I didn't used any pit file. Just used the .tar file which was selected under PDA of ODIN.
Any idea if checking repartition while flashing JB would work?
I'm currently running GB 2.3.6 baseband version DXLD1. And I've got 2 pit files one for 8GB which I got from the DXLD1 package I downloaded and one 16 GB which I downloaded separately.
arjunkdas said:
Are you saying I have to flash pit file alone? Or do a full flash of GB with repartition checked?
While flashing JB, I didn't used any pit file. Just used the .tar file which was selected under PDA of ODIN.
Any idea if checking repartition while flashing JB would work?
I'm currently running GB 2.3.6 baseband version DXLD1. And I've got 2 pit files one for 8GB which I got from the DXLD1 package I downloaded and one 16 GB which I downloaded separately.
Click to expand...
Click to collapse
No... you should flash pit file with the .tar.md5 file.
repartition will work on either GB or JB.
if you have the 8gb version you should use the 8gb .pit file and use the 16 gb .pit file if you have the 16gb version.
http://forum.xda-developers.com/showthread.php?t=2353293
check this man
it is worked for me !!!!!!!!!!!!!!
NO Backup EFS
amr diab said:
http://forum.xda-developers.com/showthread.php?t=2353293
check this man
it is worked for me !!!!!!!!!!!!!!
Click to expand...
Click to collapse
solution in that thread says you need to have an EFS backup. And I dont have it. And in next post, that guy said his restored IMEI is corrupted. Did u checked yours??!
Doubts
Patlcs said:
No... you should flash pit file with the .tar.md5 file.
repartition will work on either GB or JB.
if you have the 8gb version you should use the 8gb .pit file and use the 16 gb .pit file if you have the 16gb version.
Click to expand...
Click to collapse
My phone is the 16 GB version. I'm having some weird doubts. I beg your pardon if I'm asking noob questions but I need to know them.
Ok, so here's how I flashed JB 4.1.2
In the JB package I downloaded, ther was only .tar file and nothing else. The baseband version is DDULP8. So everytime I flashed JB, I did with .tar file alone and no pit file.
Now, whenever I flashed back to GB 2.3.6, I flashed by selecting three files in the DXLD1 download package. PDA file, CSC file and an 8GB pit file. I flashed with these files at the first place and the phone boots up, works well. But the internal storage is shown as 3.91 GB. To solve this, I downloaded a separate 16GB pit file and flashed the phone by just selecting the 16GB pit file. After I rebooted my phone, it shows 11.1 GB internal storage.
My doubt is, do I need to select the 16GB pit file and check repartition while flashing JB 4.1.2?
Or just check repartition and flash with .tar file alone?!
Didn't solved
Patlcs said:
i got that problem too. you should flash your .pit file and check repartition in odin.
this solved my problem.
Click to expand...
Click to collapse
tried it..didnt solve the problem!
arjunkdas said:
solution in that thread says you need to have an EFS backup. And I dont have it. And in next post, that guy said his restored IMEI is corrupted. Did u checked yours??!
Click to expand...
Click to collapse
i didn't have any backup and the imei is ok
just try it from 1-10
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
amr diab said:
i didn't have any backup and the imei is ok
just try it from 1-10
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
Click to expand...
Click to collapse
Tried! Still getting steup wizard stopped message!
arjunkdas said:
tried it..didnt solve the problem!
Click to expand...
Click to collapse
try to flash .pit file alone
Patlcs said:
try to flash .pit file alone
Click to expand...
Click to collapse
tried that too!
Hi friends ,
I am using Samsung S Advance since last eight month, Till now i have flash more than 300 nightly and custom roms over my mobile and evry time i succeeded, but two days back when i got stuck in omnirom I use ODIN to Flash Stock JB . My Phone Boot After that And got stuck on initial setting wizard everytime i try to pass that it shows
unfortunately samsung setting wizard stopped , so i can not pass that point ,
So i flash stock firmware again and again but everytime same problem
Then I reboot in Recovery which show message " fail to mount efs( invalid argument)
I ignore it and Start Recovery again and root my mobile using update.zip(which is temporary recovery) and then flash cocore kernel And try to restore my backup( I have 6 different rom backup , i tried them all) but every rom got stuck in bootloop .
Then I try to Flash CM10.2 but that also didn't work
Then I Flash some custom rom like sami-os and galexperia which are based on stock firmware and they start working but those roms are freezing a lot, When i try to install any software in those rom they says insufficient memory , I Check storage and it shows
"DEVICE MEMORY 0.00B"
Everytime I reboot all user data get wiped and evrytime setting wizard appear like first boot
I have tried to mount efs, data, ,system via cwm . There is error to mount efs via cwm . I mount data, system successfully but after every reboot they are unmounted.
So Made some search and finally decide to repartition via odin using PIT file given somewhere in this forum but odin shows "fail"
My Friend suggest me to revert back to gb but i couldn't find Indian firmware ( All sites give link to hotfile page which is banned), so i followed post in xda about downgrading from JB to GB and try to flash PIT, PDA , CSC file given by OP via odin but it fails everytime .
So again I flash JB via odin but same result( Got stuck in setting wizard)
So I Tried to root again using update.zip(which i mentioned earlier and which works for me everytime in past) but it switched off during update in recovery so now i can not start cwm now and can use only stock recovery and unable to flash custom rom.
I have Given All Details about how problem start and here is summary of all problems
1. fail to mount efs(invalid argument)
2. 0.0b internal memory
3. unable to repartition using ODIN
4. user data deleted on every boot and boot as first boot
5. can not pass setup wizard in stock firmware after flashing stock via Odin
I think i have messed up with internal memory and which is causing problem or my recovery is damaged.
please give me solution .
If any one have INDIAN GB firmware with pit, csc , pda, bootloader please upload and give link , i searched everywhere no link is working.
Thanks in advance
EDIT: I have successfully downgrade to GB and 0.0b internal memory problem is solved , for detail read 7th post
But still FACING " efs error" and unable to upgrade to jb
Every time i flash jb with odin it get stuck in start up in setting wizard with message " process com.google.process.gapps has stopped" and then " setting wizard stopped"
please help me to solve this
Any one need to know how i solved my problem of 0.0mb and downgrade GB he can read post and even PM me.
androiddoctor said:
Hi friends ,
I am using Samsung S Advance since last eight month, Till now i have flash more than 300 nightly and custom roms over my mobile and evry time i succeeded, but two days back when i got stuck in omnirom I use ODIN to Flash Stock JB . My Phone Boot After that And got stuck on initial setting wizard everytime i try to pass that it shows
unfortunately samsung setting wizard stopped , so i can not pass that point ,
So i flash stock firmware again and again but everytime same problem
Then I reboot in Recovery which show message " fail to mount efs( invalid argument)
I ignore it and Start Recovery again and root my mobile using update.zip(which is temporary recovery) and then flash cocore kernel And try to restore my backup( I have 6 different rom backup , i tried them all) but every rom got stuck in bootloop .
Then I try to Flash CM10.2 but that also didn't work
Then I Flash some custom rom like sami-os and galexperia which are based on stock firmware and they start working but those roms are freezing a lot, When i try to install any software in those rom they says insufficient memory , I Check storage and it shows
"DEVICE MEMORY 0.00B"
Everytime I reboot all user data get wiped and evrytime setting wizard appear like first boot
I have tried to mount efs, data, ,system via cwm . There is error to mount efs via cwm . I mount data, system successfully but after every reboot they are unmounted.
So Made some search and finally decide to repartition via odin using PIT file given somewhere in this forum but odin shows "fail"
My Friend suggest me to revert back to gb but i couldn't find Indian firmware ( All sites give link to hotfile page which is banned), so i followed post in xda about downgrading from JB to GB and try to flash PIT, PDA , CSC file given by OP via odin but it fails everytime .
So again I flash JB via odin but same result( Got stuck in setting wizard)
So I Tried to root again using update.zip(which i mentioned earlier and which works for me everytime in past) but it switched off during update in recovery so now i can not start cwm now and can use only stock recovery and unable to flash custom rom.
I have Given All Details about how problem start and here is summary of all problems
1. fail to mount efs(invalid argument)
2. 0.0b internal memory
3. unable to repartition using ODIN
4. user data deleted on every boot and boot as first boot
5. can not pass setup wizard in stock firmware after flashing stock via Odin
I think i have messed up with internal memory and which is causing problem or my recovery is damaged.
please give me solution .
If any one have INDIAN GB firmware with pit, csc , pda, bootloader please upload and give link , i searched everywhere no link is working.
Thanks in advance
Click to expand...
Click to collapse
If your phone is I9070 and not I9070P then use this: http://forum.xda-developers.com/showthread.php?t=2195673
After that you can use your country GB. We all downgrade this way, and after that use any other firmware.
shut_down said:
If your phone is I9070 and not I9070P then use this: http://forum.xda-developers.com/showthread.php?t=2195673
After that you can use your country GB. We all downgrade this way, and after that use any other firmware.
Click to expand...
Click to collapse
ithink your internal memory can broken..missd=ing the repartition table index
shut_down said:
If your phone is I9070 and not I9070P then use this: http://forum.xda-developers.com/showthread.php?t=2195673
After that you can use your country GB. We all downgrade this way, and after that use any other firmware.
Click to expand...
Click to collapse
Thank you for replying so fast , but i have already tried it and now trying one again .
i follow all the step , even odin say pass but phone stuck at Samsung galaxy S Advance logo
nowfalsalahudeen said:
ithink your internal memory can broken..missd=ing the repartition table index
Click to expand...
Click to collapse
yeah you are right , i m also thinking that internal memory is broken but i m unable to solve it. Give me some solution please
downgrade to gb if you know the procedure... this'll fix your problem .. if you get any error after downgrading then go to recovery and wipe factory and cache...
0.0b memory problem and downgrading GB is solved BUT still efs , JB error
Hi friends , Finally i have succeeded to downgrade to GB with given procedure in forum and solve low memory problem also
here is what happened
As i Said earlier when i follow procedure to downgrade to gb my phone stuck at samsung logo,
The problem was pit file given in that procedure was 8gb and my mobile was 16 gb with only 1gb usb storage remaining and it shrunk my memory and as my usb storage was full and it eat my whole internal memory so i again flash JB which is also not working but with recovery i flash Sami-OS which was working partially with lots of problem And i format my usb storage there and it shrunk to 3.9gb from 11gb then from download mode I flash GB as per this forum http://forum.xda-developers.com/showthread.php?t=2195673 and it start working , then I flash 16 gb pit file then official gb for my country and evrything is fine with GB it works flawless
BUT when i try to upgrade to JB via odin its showing same problem
when phone start there is warning" process com.google.process.gapps has stopped" and when try to go further "setting wizard stopped" and i got stuck in there again again
also recovery show failed to mount efs(invalid argument)
So please help me to get rid of this efs problem and Ugrade to JB
androiddoctor said:
Hi friends , Finally i have succeeded to downgrade to GB with given procedure in forum and solve low memory problem also
here is what happened
As i Said earlier when i follow procedure to downgrade to gb my phone stuck at samsung logo,
The problem was pit file given in that procedure was 8gb and my mobile was 16 gb with only 1gb usb storage remaining and it shrunk my memory and as my usb storage was full and it eat my whole internal memory so i again flash JB which is also not working but with recovery i flash Sami-OS which was working partially with lots of problem And i format my usb storage there and it shrunk to 3.9gb from 11gb then from download mode I flash GB as per this forum http://forum.xda-developers.com/showthread.php?t=2195673 and it start working , then I flash 16 gb pit file then official gb for my country and evrything is fine with GB it works flawless
BUT when i try to upgrade to JB via odin its showing same problem
when phone start there is warning" process com.google.process.gapps has stopped" and when try to go further "setting wizard stopped" and i got stuck in there again again
also recovery show failed to mount efs(invalid argument)
So please help me to get rid of this efs problem and Ugrade to JB
Click to expand...
Click to collapse
is your baseband working ok? I had a similar problem when flashing a rom, couldn't get out of setup wizard and also my baseband was XXXX as soon as i fixed the baseband and re-flashed the problem was gone, here is how:
I've flashed modemfs.img.md5 now 3G is working.
On another device (same model and region) I did:
dd if=/dev/block/mmcblk0p2 of=/sdcard/modemfs.img.md5
Copied generated file to my sdcard and did:
dd if=/sdcard/modemfs.img.md5 of=/dev/block/mmcblk0p2
Reboot and it's done.
Click to expand...
Click to collapse
Thanks to @Skarllot @ http://forum.xda-developers.com/show...2119292&page=3
more on the thread i created because of this:
http://forum.xda-developers.com/showthread.php?t=2548933
good luck!
alete89 said:
is your baseband working ok? I had a similar problem when flashing a rom, couldn't get out of setup wizard and also my baseband was XXXX as soon as i fixed the baseband and re-flashed the problem was gone, here is how:
Thanks to @Skarllot @ http://forum.xda-developers.com/show...2119292&page=3
more on the thread i created because of this:
http://forum.xda-developers.com/showthread.php?t=2548933
good luck!
Click to expand...
Click to collapse
Thank You For Helping,
I have exact same problem like you and i have successfully downgrade to GB but the only difference between your problem and mine is i can still see my baseband which is ddlk and i still have imei number and network
I understand my problem that unable my phone "unable to mount efs"
which is very imp .And i think i m facing all problem just because of that , solution given by you restores efs but i dont have efs backup ,
I will discuss this in your post in more detail
Here's your Solver !
I have the same problem with you and now its solved!
check this thread http://forum.xda-developers.com/showthread.php?t=2353293
Ok , step by step of what I did and where Im at now .
I got the Note 4 today . Played with stock firmware for a moment ( last running firmware was Anj7 baseband stock unrooted ) . Booted into download mode rooted with ch-root and checked nand erase all in Odin . I believe it erased the stock rom . Binary was changed to custom confirmed in download mode screen .
Then Flashed TWRP .
boot into TWRP when I try to wipe it says
cant mount /data cant mount anything basically and wipe fails because nothing will mount.
I try to install FireKat v5 rom and it says successful despite TWRP wont mount anything( is v5 anj? . Do I need to flash stock rooted before I can flash any other rom ? )
Reboot after install and it goes into a boot loop after boot screen transitions into boot animation .
So at this point I have no bootable rom . It doesnt appear anything will mount in TWRP for some reason .
And Im considering flashing sammo official ANJ rom to atleast get a working phone but I dont know what changes the bootloader version be it ch root or flashing a rom . And right now Im scared if the bootloader has changed and I try to revert to an older bootloader with the sammo official anj rom it could hard brick .
Im gonna need some serious advanced help here. I never done nothing like this mess before
Some_dude36 said:
Ok , step by step of what I did and where Im at now .
I got the Note 4 today . Played with stock firmware for a moment ( last running firmware was Anj7 baseband stock unrooted ) . Booted into download mode rooted with ch-root and checked nand erase all in Odin . I believe it erased the stock rom . Binary was changed to custom confirmed in download mode screen .
Then Flashed TWRP .
boot into TWRP when I try to wipe it says
cant mount /data cant mount anything basically and wipe fails because nothing will mount.
I try to install FireKat v5 rom and it says successful despite TWRP wont mount anything( is v5 anj? . Do I need to flash stock rooted before I can flash any other rom ? )
Reboot after install and it goes into a boot loop after boot screen transitions into boot animation .
So at this point I have no bootable rom . It doesnt appear anything will mount in TWRP for some reason .
And Im considering flashing sammo official ANJ rom to atleast get a working phone but I dont know what changes the bootloader version be it ch root or flashing a rom . And right now Im scared if the bootloader has changed and I try to revert to an older bootloader with the sammo official anj rom it could hard brick .
Im gonna need some serious advanced help here. I never done nothing like this mess before
Click to expand...
Click to collapse
Let me try my noob expertise out lol...from what I know the only way to hardbrick is by using the wrong modem on your variant. So I think you have nothing to worry about. What you have is soft brick.
Download from sam mobile nj7 or nk4 firmware and reflash via odin. Hope this helps.
NOTE 12-10+2 ?
T LEONARDIS said:
Let me try my noob expertise out lol...from what I know the only way to hardbrick is by using the wrong modem on your variant. So I think you have nothing to worry about. What you have is soft brick.
Download from sam mobile nj7 or nk4 firmware and reflash via odin. Hope this helps.
NOTE 12-10+2 ?
Click to expand...
Click to collapse
Ok im downloading nj7 right now . I think the problem I did was erasing nand when I did first root and it caused no partitions to be set.
What part of the root process was not clear. If you look online u will find step by step rooting video. Go back to stock and try again thru odin
BAD ASS NOTE 4
Just flash stock rom with Odin and start over. Don't do the crazy erasing step next time. These phones are hard to brick. I've honestly never seen one I couldn't fix.
Yes, in Odin you shouldn't be clicking anything other then the pda box to put the proper tar in. Which of you download the cf auto root zip. Then make a new folder on your desktop. Open the downloaded cf auto root zip. Then highlight and drag n drop all files/contents of your Cf auto root zip into the newly created folder on your desktop. From the newly loaded folder right click on Odin run as administrator. Once in there put your phone into download mode and hook it up via USB to your pc a blue box with the word Com and a number will pop up in the upper left. The number doesn't matter as long as it says Com and a number, this is odin's way of showing it recognizes your device. . Hit the pda tab it'll bring you to that folder with only one file showing. Double check it's named Tmo to insure you downloaded the correct one. Select it. Odin will automatically fill in the proper boxes.
Hit run and it should knock it out fairly quick.
If you have ANY QUESTIONS just follow this video tutorial to the T... How to Root the Samsung Galaxy Note 4: http://youtu.be/mdkLxNNLGiA
That's by QBKING77 He knows what he's doing. Let us know how it goes
http://forum.xda-developers.com/showthread.php?t=2957156
I try to use sam fix tool to get my baseband (unknown) and sim cad imei fixed
i use the tool and choose baseband fix it boot into donwload mode and flash something
after that my note 9 stuck bootloop
i flashed stock frimware using odin and didnt work
i flashed combination file and also got bootloop
i can go to download mode
but whatever i do my phone stuck bootloop
plz need help plz guys
BUT I MADE A EFS BACKUB USING SCRIPT CMD IT CREAT A FLASH FILE CAN BE FLASHED USING ODIN VIA AP
BUT I CAN ACCESS IT RIGHT NOW BECASE I HAVE IT IN MY WORK
IS THAT ABLE TO HELP ME FIX THE PROBLEME[/COLOR]
Make you post readable for everyone using the dark theme and you might get more response.
What exactly did you flash with Odin and what happened, other than it didn't work?
willhemmens said:
Make you post readable for everyone using the dark theme and you might get more response.
What exactly did you flash with Odin and what happened, other than it didn't work?
Click to expand...
Click to collapse
I used a tool to fix baseband the tool reboot my phone into download mode and flash something
i try to boot my phone it get bootloop i try flash stock rom still bootloop
i flashed combination file still bootloop
i think the tool did something to efs partition
Did you complete a backup with TWRP?
willhemmens said:
did you complete a backup with twrp?
Click to expand...
Click to collapse
no i didint flash twrp my device not rooted
devil499 said:
no i didint flash twrp my device not rooted
Click to expand...
Click to collapse
You shouldn't have used any tool.
You could have easily recovered your unknown baseband by simply flashing your stock firmware.
Retry flashing the Stock firmware. But this time, do a wipe cache partition, wipe data/factory reset in recovery mode first.
Use the latest stock firmware that is available for your country/CSC.
If you can find a pit file, include that in odin flash with the stock firmware. Put a checkmark on the "repartition" option.
It's normal for the device to take 5-10 minutes or more during the initial boot.
Sent from my SM-N960F using Tapatalk
Good luck dude when the mention above most really suck having a bricked note 9
jaylence said:
You shouldn't have used any tool.
You could have easily recovered your unknown baseband by simply flashing your stock firmware.
Retry flashing the Stock firmware. But this time, do a wipe cache partition, wipe data/factory reset in recovery mode first.
Use the latest stock firmware that is available for your country/CSC.
If you can find a pit file, include that in odin flash with the stock firmware. Put a checkmark on the "repartition" option.
It's normal for the device to take 5-10 minutes or more during the initial boot.
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
i have done that but didnt worked
plz help me
i didint find pit file for my device
n960f
HtcOnekid said:
Good luck dude when the mention above most really suck having a bricked note 9
Click to expand...
Click to collapse
i found this post https://forum.xda-developers.com/ga...ide-fix-n950f-efs-failed-to-mount-dm-t3831184
i beg you can you plz help understand it
Extract Stock firmware AP file (rename .md5 to .tar)
this i cant understand wich should i rename or what i do
Rename dqmdbg.img to efs.img (or smallest image must be smaller than 8000 KB). Extract Dqmdbg.img.lz4 so it’s just “Dqmdbg.img” and then rename it to efs.img and put that one in a tar. Other option is downloading a file that’s already made this way if your bootloader is binary 4, Saves you trouble of extracting / renaming: http://www.mediafire.com/file/589wuc...f/efs.tar/file (if you download this file just move onto number 3)
Add file new efs.img into tar archive.
Flash tar as AP file in odin + download mode
Reboot download mode
Flash Combination with odin + nand erase option on Edit: suggest you to flash stock rom first and oem unlock, don't need to wait for 7 days if imei is 0000 skip combination step
Device Should boot into Factory binary
Use IME to restore imei using *#06# (or imei 0000 in stock rom) Edit: This step is not required if efs backup is restored successful
Your device should have dm-verify failed in recovery due to drk error
Continue drk bypass for dm verify error below to continue
willhemmens said:
Make you post readable for everyone using the dark theme and you might get more response.
What exactly did you flash with Odin and what happened, other than it didn't work?
Click to expand...
Click to collapse
What? I'm using desktop. Is there a different view on mobile?
Bricked Note 9 due to efs
devil499 said:
I try to use sam fix tool to get my baseband (unknown) and sim cad imei fixed
i use the tool and choose baseband fix it boot into donwload mode and flash something
after that my note 9 stuck bootloop
i flashed stock frimware using odin and didnt work
i flashed combination file and also got bootloop
i can go to download mode
but whatever i do my phone stuck bootloop
plz need help plz guys
BUT I MADE A EFS BACKUB USING SCRIPT CMD IT CREAT A FLASH FILE CAN BE FLASHED USING ODIN VIA AP
BUT I CAN ACCESS IT RIGHT NOW BECASE I HAVE IT IN MY WORK
IS THAT ABLE TO HELP ME FIX THE PROBLEME[/COLOR]
Click to expand...
Click to collapse
I have the same problem with my note 9. Im looking if anyone can provide me with efs file of N960F Binary 3 so i can get it unbricked again.
I found this website but it has efs files for binary 1 and 2 not 3. Will it still work if i use binary 2 efs?
//frpdone.com/efs-mdm-samsung/
Did u find a solution?