Sorry it did not work out for you. The installing application from google play involve cache partition. So should also try to scan to fheck or to remove and recreate cache, if you have not don so.
[Guide]How to revive your bricked Gnote
- Thread starter uggies
- Start date
Infact partition 12 is not even needed for our normal use and installing roms as you fan see in some posts ealier. So you can even remove it totally and then expand ums to cover it. That is ti makw ums until 15800 mb. Hope it work out for you.
Sent from my LT18i using XDA
It only works on stock ICS? I tried on CM9 and the triangle and count remains :-(
Should use the application called Triangle Away by Chainfire (search in the forum). It is safer and work with both ICS stock and CM9 roms. cheers.
Edit: I guess other people have warned several time but for sake of being careful, please remember to change to another kernel asap since that Angelom kernel is dangerous, I heard!
cheers!
Last edited:
Have been using this method successfully for about a week and a half to "re-tune" my partitions and have a working phone again. Something that happened over the weekend while I was reloading the XEU ICS rom ..... my /efs wouldn't mount and I lost all connectivity. After reflashing GB LA4 (the original for my internationa Note) I got the files back, however, I'm now on a generic IMEI and have a serial number of all 0's. Guidance??
Did you ever had a efs backup ??
Normally it is the way out of this situation.
Working up for your old IMEI might be difficult.
I will post in case I get a way.
OK I went to the SGS2 forum and this is the only way out.
Check your /efs folder for the backupfile .nv-data.bak and .nv-data.bak.md5
Use root explorer; if you find you are in luck
You can backup all the 4 files .bak and .bin files first ....
Rename the .bak file to nv-data.bin and nv-data.bin.md5. Just check that you have set the permissions as original.
Reboot
Hope it helps ....
Normally it is the way out of this situation.
Working up for your old IMEI might be difficult.
I will post in case I get a way.
OK I went to the SGS2 forum and this is the only way out.
Check your /efs folder for the backupfile .nv-data.bak and .nv-data.bak.md5
Use root explorer; if you find you are in luck
You can backup all the 4 files .bak and .bin files first ....
Rename the .bak file to nv-data.bin and nv-data.bin.md5. Just check that you have set the permissions as original.
Reboot
Hope it helps ....
Last edited:
There has been confirmation that In many cases it is the faulty system partitions (caused by the suspected ICS kernel or whatever reason). In that case relocating the corrupted partition to the good areas works. The first one who has applied the method successfully is "Drnull" for another similar device (epic4g).
So for those who would like to use this solution follow the guide below which I developed based on the hints from Drnull and a guide for another android device by Eldarerathis and Soundwire.
Credits and thanks to them.
Also Big thanks to: Prabhu1980, Matiasg85, Uggies, Bodivas, As i9000, Alekhkhanna, Hg42, Travis82 and others who have provided precious tools, troubleshoot solutions, advice and support for making this guide complete and more easy to use!
------------------
Important Note:
As the method progress, thanks to member Hg42 custom PIT files have been made that can help re-partition automatically. This will make it much easier for those who find adb things too much to handle. Follow the:
Link one
or Link two
to get the PIT file and how to flash.
The custom PIT should work in majority of cases that have partition problems. Still, in a number of cases when there are bad blocks inside the (original) internal sdcard area and/or cache partition, in which case you still need to follow the manual method below.
In fact the best way is to combine both manual and custom PIT method. Using manual way to diagnose which partition is faulty then choose the most suitable PIT file for that scenario (or you will know you need to do manual way if you identify there is fault block inside the internal sdcard and/or cache partition). On the other hand, the manual way requires good skills in handling android phone, so for average users the best way is to use PIT file method.
-----------------------------------
More notes for Manual method:
1. For those who can get SS warranty service to fix it for free then you should go there asap, and do not need to try.
2. Requires some basic knowledge of MS-DOS and adb (just a few simple commands).
3. Partitions can be delete and recreate like in a computer hdd but requires more skills. So if you are not confident do not jumped into this method.
4. You should have had your back-up your data (music, books...) before, since this method will erase all the data in your sdcard.
5. And do not try to hold me responsible if you mess things up further than your current state in your phone.
1. The tools:
- Download the screen shot of the Note’s partitions for your reference information
- download and install the attached kernel.tar. This kernel has the partition tools and CWM with it.
- You should be able to have adb driver for Note and adb.exe in you computer. The easy way is to download Note usb driver from here, then download adb folder attached in the post. Install driver you have downloaded and extract adb folder to c: driver of your computer, you will have the tools folder which has adb.exe in it. You should now have adb working for your Note. (Alternatively, if you have installed Kies, then the usb driver should already installed. Then you just need to download the adb folder provided.)
2. Set up the tools:
- Use odin to flash attached kernel .tar file.
- Then restart the phone to recovery
- Then connect to computer using usb cable.
3. Then run cmd from your computer and cd (for those new to MS-DOS: this is change directory command under DOS. You just need to do a search on how to use cd command for DOS) to the folder that has adb.exe in your computer.
Then run,
Code:adb devices
it should give you some number then it means your device is connect in adb
then:
it should give you the sign like this: ~ #Code:adb shell
Then run (noted that umount is without N):
If one of those "umount /" commands return "invalid argument" just ignore it and continue with next steps.Code:~ # umount /cache ~ # umount /system ~ # umount /data
This is to unmount cache, systemfs and datafs partitions.
Note: it is easier to copy and paste (right click mouse) the code to CMD windown to save time and avoid typing error.
Then run the parted.
if it ask you to fix something just choose yes. It should give you bellow:Code:~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted)
Then run:
It will give you a picture of your Note’s partitions as in the screen shots I have attached. (text version is below):Code:(parted) print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 264MB 210MB ext4 CACHE
8 264MB 281MB 16.8MB MODEM
9 281MB 1174MB 893MB ext4 FACTORYFS
10 1174MB 3322MB 2147MB ext4 DATAFS
11 3322MB 15.2GB 11.9GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
--------------------
4. Partition checks:
If you like to check if a partition has bad block or not you can use the tools that already come with the kernel.
For partition 11 you can check using parted which handle fat32
if it does not return any error the partition 11 is probably fine, although parted only scan area that has been used by files, it does not scan all blocks.Code:(parted) check 11
For other ext4 partition you can use e2fsck as below. For example, if you like to check partition 7, which is cache, then run:
You can do the same with 9, 10.Code:(parted) quit ~ # e2fsck -c /dev/block/mmcblk0p7
(Note: e2fsck should be run after umount /cache and umount /system and umount /data)
The scan can report bad blocks or can freeze when it encounter bad blocks. In case you do not find any bad blocks in the above 4 partitions, the problem may be not related to partitions fault. Then you should explore other unbrick methods, using Heimdall to flash instead of odin for example.
If you encounter faults then you could follow the guide below to do manual re-partitioning.
---------------------
5. Start dealing with partitions: Now just suppose that you have 2 faulty system partitions: factoryfs and datafs, then the work-around way is below:
5.1 remove partitions to get rid of the faulty ones and make space available for new ones:
code:
That will remove three partitions factoryfs (9), datafs (10) and UMS (11) so as to make rooms for new partitionsCode:(parted) rm 9 (parted) rm 10 (parted) rm 11
5.2. To create three new partitions from the good area:
Code:
Code:(parted) mkpartfs primary ext2 3322 4215 (parted) mkpartfs primary ext2 4215 6362 (parted) mkpartfs primary fat32 6362 15200 (parted) name 9 FACTORYFS (parted) name 10 DATAFS (parted) name 11 UMS
-------------
Important Note: If while creating partitions parted give some error like:
Error: Input/output error during write on /dev/block/mmcblk0
Retry/Ignore/Cancel?
that would mean the area chosen for that partition include some faulty block somewhere in that range. Then you need to select another range for the partition by changing start and end number in respective code. If there is no error in the creation of partitions above, then move on with 5.3.
-------------
5.3. Convert format for 9 and 10: The above steps have created three new partitions. However, for 9 and 10 the format is ext2 and now need to be converted to ext4.
The easiest way is to go back to CWM in your phone. Then, go into mounts and storage menu and choose format /system and format /data. It will convert file system of partition 9 and 10 to ext4 automatically for you.
If the above steps are successful then check:
------------Code:~ # parted /dev/block/mmcblk0 (parted) print
Optional:
5.4. It is very unlikely that Cache is also faulty but if you think it is a problem. So for the first time you should not touch Cache. But then if you suspect the Cache partition then below is the way to do it.
Then recreate it:Code:(parted) rm 7
Then you can go into CWM and format /cache, it will convert file system to ext4.Code:(parted) mkpartfs primary ext2 54.5 264 (parted) name 7 CACHE
In case there is faulty area in Cache area, you can try to reduce the size of cache to 128MB, choose the start and end number somewhere in the space from 54.5MB to 264MB.
If everything works: Then go to cwm and try to mount your sdcard (or usb storage) to PC then copy rom.zip file to it and then flash using CWM. In many cases CWM see sdcard as internal sdcard, so you need to make sure to check both sdcard and internal sdcard.
It is recommend to use a custom GB rom first (Darky, CheckRom, Litening, Rocket, Xtralite GB...) or a CM9 rom.
Note: Flash rom by CWM (load rom.zip from computer to sdcard and flash) seem to be a better way since most members reported they cannot flash rom via odin a least for the first time after recovered using the manual re-partition method. Some member reported they can flash with odin. Just remember not to put any PIT file and do not tick re-partition when flash with odin.
6. More Notes:
It is now appear that people may have faulty blocks in different area somewhere in all 4 partitions above including factoryfs, datafs, ums and cache but internal sdcard USM is often have less chance of being faulty.
Also if you have done it successfully with the above steps and have created partitions from 3322mb up, then you can try to go back to explore the areas which belong to the former factoryfs and datafs partitions (from 281mb to 3322mb) to see if you can use some space in there for factoryfs partition or some part for the datafs partition. In that case you may also save some more space for your sdcard (UMS partition).
If it also know that the hidden partition (partition 12) is not needed for normal use and install of roms. So you can delete it and enlarge the UMS partition (to 15800mb) and you will have a larger sdcard to use.
If you like to know more about using parted, go to the documentation page here:
http://www.gnu.org/software/parted/manual/html_mono/parted.html
Update of progress: More than 30 members have reported successfully revised their Notes after fixing partitions problems using manual methods. A few more dozen has made it using custom PIT file by Hg42. Re-partition have revised many super-bricks Notes!
If you can revive your Note please share with us so that we can share your good feeling
And press thanks if you find this guide useful. Thanks.
gotta give it a try before im send out my SGN to SS
There are some guide on the web, one from XDA. It does not look so easy, though:
http://xdaforums.com/showthread.php?t=1264021
http://www.youtube.com/watch?v=JqLK_2I-SBM
cheers,
---------- Post added at 10:51 PM ---------- Previous post was at 10:50 PM ----------
Did you ever had a efs backup ??
Normally it is the way out of this situation.
Hope it helps ....
Hi Prabhu: good to see you posting again from time to time
. cheers!---------- Post added at 10:53 PM ---------- Previous post was at 10:51 PM ----------
gotta give it a try before im send out my SGN to SS
Hi: The quote of the whole guideline is very long, will be good to trim down it. cheers.
Got my note back from the service center. Got the board replaced under warranty Didnt have to pay anything.
Didnt have to pay anything.I would like to say thank you for putting this up here and helping get my phone back up and working.
I followed the instructions directly and now have CM9 installed on my Note.
I followed the instructions directly and now have CM9 installed on my Note.
Thanks for sharing good news! this make me very happy too, and it is good for health
. cheers.
First of all I would like to thank you so much for your help and for your great support helping others fixing the Note brick issue.
Unfortunately, I just bought a Note phone 3 days ago and I got bricked! ,, I'm so disappointed really and I tried the method you described very carefully but with no luck .. every time I try to create the DATAFS partition an error appear (like Error: Input/output error during write on /dev/block/mmcblk0
Retry/Ignore/Cancel?) I tried to use the partition table you advised (starting from 4215 6362) but with no luck at all.
I can install any ROM from ODIN or recovery .. but every time I do that the installation completes but it stuck on Samsung Logo.
Now I'm out of warranty, an I heard the Samsung are working to fix this issue. Do you think I should go and replace my Motherboard, or wait for Samsung solution, or what do you think the correct discussion here?
Thank you a lot.
Regards,
Mohamed ElShafei
Unfortunately, I just bought a Note phone 3 days ago and I got bricked! ,, I'm so disappointed really and I tried the method you described very carefully but with no luck .. every time I try to create the DATAFS partition an error appear (like Error: Input/output error during write on /dev/block/mmcblk0
Retry/Ignore/Cancel?) I tried to use the partition table you advised (starting from 4215 6362) but with no luck at all.
I can install any ROM from ODIN or recovery .. but every time I do that the installation completes but it stuck on Samsung Logo.
Now I'm out of warranty, an I heard the Samsung are working to fix this issue. Do you think I should go and replace my Motherboard, or wait for Samsung solution, or what do you think the correct discussion here?
Thank you a lot.
Regards,
Mohamed ElShafei
Hi:
If you have already been able to connect adb then it is better to use scan tools to check if there is faulty blocks in partitions and then choose the healthy areas to create new partitions.
Otherwise, you can try to make partitions in different areas from one range to another, moving by about 500MB or one GB each time, until it works.
If 4215 6362 do not work then you can try 5000 7147 or try 6362 8509 and so on.
If you have an external sdcard slot then the loss of space in the internal sdcard should not matter much.
About potential fix from SS from the discussions and update in the forum it appears that there are two things below (some people can misunderstand one thing for another):
1- a firmware patch to prevent healthy phone from bricking when using erase command: it looks like they might release it at some point of time in the future, and it may be in the form of an update pack.
2- about a fix for already bricked phone: The fact is nobody knows if and when there can be such as fix for already bricked phone. And if they release a tool, it is probably only to the service centers where they can perform a complicated operations to wipe everything in the chip and build it from zero again (it is still just a speculation, though). Such operation cannot be done as a do-it-yourself thing for an averaged user.
Hope it helps
Last edited:
I was in the same position a few days ago with my new Note. I resolved it by flashing AllianceROM_N7000 GB v3.4 from here: http://www.alliance-rom.com/communi...ancerom_n7000-v3-4-resurrection-edition.7668/
Then I went to CM9 but you can choose when your phone is fully functional again.
IT IS GOING TO INCREASE YOUR CUSTOM COUNTER. You can run Triangle Away afterwards.
Dear forest1971,
Thank you for your explanation, now I understand that the phone Motherboard must be replaced in order to work properly again .. what do you think is the price of changing the Motherboard?
Now with the help of hg42, and your topic, I finally managed to get the system works with the following specs:
1. cm-9-20120622-NIGHTLY-n7000.zip ROM .. For anyone you can get it from here.
2. The only Kernel that worked with this ROM was thor-kernel-v0.14-BURN-GNOTE.zip, in addition, I used several kernels but no one works, such as:
Question: What is the Kernel and the ROM you recommend? In addition, can I install "Litening ROM Note v2.0" from Odin without problems?
3. I used the Q1_20110914_16GB-patched-ums-bricked+7340032-kB.pit file and it worked well. Now my space is 1.25 GB when I connect my Note to the PC.
I usually was flashing any ROM without reading for all my previous android phones (HTC Desire, Sensation, SGS2, and Ace), but really SAMSUNG was a shock to me doing this bug .. a device 600$ price with this bug ..
SHAM ON YOU SAMSUNG
I'm now able to work with the phone and added 16GB SD Memory to work with it.
Thank you for your continuous support and wish you a wonderful day.
Mohamed
Thank you for your explanation, now I understand that the phone Motherboard must be replaced in order to work properly again .. what do you think is the price of changing the Motherboard?
Now with the help of hg42, and your topic, I finally managed to get the system works with the following specs:
1. cm-9-20120622-NIGHTLY-n7000.zip ROM .. For anyone you can get it from here.
2. The only Kernel that worked with this ROM was thor-kernel-v0.14-BURN-GNOTE.zip, in addition, I used several kernels but no one works, such as:
- 4pda_kernel.tar - it didn't boot the ROM and stuck at Samsung N7000 Logo.
- speedmod-kernel-n7000-ics-k3-3-Odin.tar - it didn't boot the ROM and stuck at Samsung N7000 Logo.
- cm9_safe_kernel.tar - Works and make the ROM boot, but the Wireless was disabled.. I don't know why.
Question: What is the Kernel and the ROM you recommend? In addition, can I install "Litening ROM Note v2.0" from Odin without problems?
3. I used the Q1_20110914_16GB-patched-ums-bricked+7340032-kB.pit file and it worked well. Now my space is 1.25 GB when I connect my Note to the PC.
I usually was flashing any ROM without reading for all my previous android phones (HTC Desire, Sensation, SGS2, and Ace), but really SAMSUNG was a shock to me doing this bug .. a device 600$ price with this bug ..
SHAM ON YOU SAMSUNG
I'm now able to work with the phone and added 16GB SD Memory to work with it.
Thank you for your continuous support and wish you a wonderful day.
Mohamed
Last edited:
Dear forest1971,
Thank you for your explanation, now I understand that the phone Motherboard must be replaced in order to work properly again .. what do you think is the price of changing the Motherboard?
Now with the help of hg42, and your topic, I finally managed to get the system works with the following specs:
1. cm-9-20120622-NIGHTLY-n7000.zip ROM .. For anyone you can get it from here.
2. The only Kernel that worked with this ROM was thor-kernel-v0.14-BURN-GNOTE.zip, in addition, I used several kernels but no one works, such as:
- 4pda_kernel.tar - it didn't boot the ROM and stuck at Samsung N7000 Logo.
- speedmod-kernel-n7000-ics-k3-3-Odin.tar - it didn't boot the ROM and stuck at Samsung N7000 Logo.
- cm9_safe_kernel.tar - Works and make the ROM boot, but the Wireless was disabled.. I don't know why.
Question: What is the Kernel and the ROM you recommend? In addition, can I install "Litening ROM Note v2.0" from Odin without problems?
3. I used the Q1_20110914_16GB-patched-ums-bricked+7340032-kB.pit file and it worked well. Now my space is 1.25 GB when I connect my Note to the PC.
I usually was flashing any ROM without reading for all my previous android phones (HTC Desire, Sensation, SGS2, and Ace), but really SAMSUNG was a shock to me doing this bug .. a device 600$ price with this bug ..
SHAM ON YOU SAMSUNG
I'm now able to work with the phone and added 16GB SD Memory to work with it.
Thank you for your continuous support and wish you a wonderful day.
Mohamed
If you want too much and read too little it will just get you into more trouble sooner or later.
Go read, read and read, and stay happy with what works for you. Btw, where did I say "the phone Motherboard must be replaced in order to work properly again"?
You are correct in everything you said .. I'm sad that this happened to me but also I learned a lot from it.
What I understood from your explanation that fixing the damaged emmc by SAMSUNG is a very small hope and I don't think they will care to do that .. i believe they will be more concern to fix the Kernel itself .. but for any one who bricked the warranty by flashing a cocked rom, they will not give care to him .. Anyway I think days will tell us what will happen .. in the mean time, the device is working .. not as I wished .. but at least I can use it for normal phone usage.
BTW: you didn't tell me, what rom and Kernel you recommend, also do you know the price of the Note Motherboard.
Thank you.
Mohamed
What I understood from your explanation that fixing the damaged emmc by SAMSUNG is a very small hope and I don't think they will care to do that .. i believe they will be more concern to fix the Kernel itself .. but for any one who bricked the warranty by flashing a cocked rom, they will not give care to him .. Anyway I think days will tell us what will happen .. in the mean time, the device is working .. not as I wished .. but at least I can use it for normal phone usage.
BTW: you didn't tell me, what rom and Kernel you recommend, also do you know the price of the Note Motherboard.
Thank you.
Mohamed
Hi mate: before you can read properly to know more about what is good about a certain rom and what your need is, then any working rom is already good for you! There are numerous places in the forum where people say how much they paid to get their motherboard replaced, so again: read and search. cheers.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
213Guide for repartition workaround to fix super-brick Note
I was on Offical leaked Taiwan version of ICS, then i decided to move to XXLPY version of ICS. I went to CMW to full wipe data, but for some reason, my note froze during wiping data...
I have waited long enough, but it was stuck. With no choice, I removed the battery then tried to boot, but it was stuck on the first screen.
From then on, I have tried to recover my note using various Offical ROMs, the taiwan leak, German leak and even old GB ROM, but I am stuck at Factoryfs...
I am pretty sure Ive tried everything, put PIT and not put PIT, Kernel, etc...
For some reason, Kernel can be installed just fine, but when it comes to ROMs, it stucks at this screen.
View attachment 1069879
Please, any help is appreciated
There has been confirmation that In many cases it is the faulty system partitions (caused by wipe using the buggy ICS stock kernel or other reasons). In that case re-partition workaround will help revive your brick phone. The first one who has applied the method successfully is "Drnull" for another similar device (epic4g).
So for those who would like to use this solution follow the guide below which I developed based on the hints from Drnull and a re-partition guide for Kindle Fire by Eldarerathis and Soundwire.
Credits and thanks to them.
Big thanks to: Prabhu1980, Matiasg85, Uggies, Bodivas, As i9000, Alekhkhanna, Travis82 and others who have provided precious tools, troubleshoot solutions, advice and support for making this guide more complete and easy to use! Also Special thanks to Lyriquidperfection for his great PIT Magic and Hg42 for his custom PIT method!
------------------
I. Case Classification and solution when there is no recovery mode:
1. Case A. If you can enter recovery: then use scanning tool to find where the damage is. Should use hg42 scanners or use the procedures described in the manual method below (Go until steps 4 to find the answers). The scanning can guide you to find the most suitable strategy for re-partition. After scanning you can use the most suitable custom pit files from the set of custom pit files in hg42's thread or use the method in this guide or a combination of both in an intuitive way to revive your brick Note. .
2. Case B. If you only have download mod, no recovery: if you flash using odin and it gets stuck at factoryfs or datafs repeatedly and you have made wipe/factory reset using ICS stock kernel, then you certainly have emmc brick. You can try to flash some kernel attached in this guide to see if can enter recovery. IF yes, then go back to Case A. If not you can use a blind method using the custom pit files below. Try one by one. The one from 2.0 should work for you. If not then from 2.1 to 2.5, one of those should work.
2.0. Custom pit that works for most cases of emmc brick
2.1. Custom pit option 1
2.2. Custom pit option 2
2.3. Custom pit option 3
2.4. Custom pit option 4
2.5. Custom pit option 5
-----------------------------------
II. Manual re-partition
Notes for using Manual repartition:
1. For those who can get SS warranty service to fix it for free then you should go there, and do not need to try repartition.
2. know how to run command prompt (MS-DOS) from window.
3. Partitions can be delete and recreate like in a computer hdd and it is reversible: you can do and redo again and again and can also go back to original scheme by flashing original PIT file.
4. If you like to recover data from your internal sdcard (photos, music, books...) you should look at Item 9 near the end of the guide.
5. And do not try to hold me responsible if you mess things up further than your current state in your phone.
1. The tools:
- Download the screen shot of the Note’s partitions for your reference information
- Install USB driver: You should be able to have adb driver for Note. If not, then download Note usb driver from here.
- Prepare adb folder: download adb folder from Here and extract adb folder to c: driver of your computer, you will have the tools folder which has adb.exe in it. You should now have adb working for your Note.
- Install custom recovery so that you can get into recovery and connect adb.
+ if you have installed GB rom (as part of the unbrick process) then download and install the attached 4pda_kernel.tar from Here.
It will raise flash counter but you can reset later using Triangleaway by Chainfire.
+ If you were ICS rom: then download and flash Speemod kernel for ICS Here., using odin.
+ If you were on JB rom then download and flash Speedmod kernel for JB from Here.
2. Set up the tools:
- after flashing one of the suitable kernel from above you should now be able to enter recovery.
- Then restart the phone to recovery (Using three buttons).
- Then connect to computer using usb cable.
3. Then run cmd from your computer and cd (change directory) to the folder that has adb.exe in your computer.
Then run,
Code:adb devices
it should give you some number then it means your device is connect in adb
then:
it should give you the sign like this: ~ #Code:adb shell
-------
Note: In case adb shell it only gives this sign $ (after you have installed the 4pda_kernel) then it showed there is a mismatch of that kernel with the rom that is sitting on your (semi-brick) Note and it does not give full root. In that case you should download and install this CM9 based safe kernel from this links which should help you to get full adb root access with this sign ~ #. It is a zip file and need to be install from CWM (not odin) by copy it to external sdcard or internal sdcard (by mount usb storage to PC or adb push.
-------
Then run (noted that umount is without N):
If one of those "umount /" commands return "invalid argument" just ignore it and continue with next steps.Code:~ # umount /cache ~ # umount /system ~ # umount /data
This is to unmount cache, systemfs and datafs partitions.
Note: it is easier to copy and paste (right click mouse) the code to CMD windown to save time and avoid typing error.
Then run the parted.
if it aska you to fix something just choose yes. It should give you bellow:Code:~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted)
Then run:
It will give you a picture of your Note’s partitions as in the screen shots I have attached. (text version is below):Code:(parted) print
print
print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 264MB 210MB ext4 CACHE
8 264MB 281MB 16.8MB MODEM
9 281MB 1174MB 893MB ext4 FACTORYFS
10 1174MB 3322MB 2147MB ext4 DATAFS
11 3322MB 15.2GB 11.9GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
--------------------
4. Scanning for Partition errors:
4.1. Use DD:
Do to a thorough scan of partitions (block damage) you can use DD command below one by one (it only read partition block by block and no write, so it is totally safe).
Damage is mostly found in partition 7, 9, 10, 11. You can use dd to check other partition from 1 to 6 as well.
Scan partition 7 and 9 will be quick (less than a minute) partition 10 take about 3 minutes and 11 about 5-7 minutes.Code:(parted) quit ~ # dd if=/dev/block/mmcblk0p7 of=/dev/null ~ # dd if=/dev/block/mmcblk0p9 of=/dev/null ~ # dd if=/dev/block/mmcblk0p10 of=/dev/null ~ # dd if=/dev/block/mmcblk0p11 of=/dev/null
- If it return in and outs and partition size then they are fine (no faulty blocks)
- If it freezes (or run too long more than 10 minutes), or return something like "read/write I/O error" then it means you have some damage in that respective partition and read command failed. In this case should restart CMD/adb and run the test again for the partition that give I/O error to make sure the error is permanent and result of test is reliable.
4.2. There is also anther scan tool to double check if there are partitions faults: that is e2fsck. It comes with 4_pda and CM9 kernel given. The added benefit is that it can also repair minor memory block damage.
This tool can only be used for ext4 partition (7, 9,10) and it need to be used after "umount /cache"... steps in point 3. It is suggested that before attempting with re-partition you should first try to use this tool to scan and fix the damaged block. The command is below:
The results of e2fsck scanning can be as below:Code:~ # e2fsck -f -c –y /dev/block/mmcblk0p7 ~ # e2fsck -f -c –y /dev/block/mmcblk0p9 ~ # e2fsck -f -c –y /dev/block/mmcblk0p10
- If there is no faulty block e2fsck will report: "no bad block found". then good!
- If it freezes then it has encountered emmc bug damaged and cannot fix: In this case will definitely need re-partition.
- If it report encountered some damaged block and has fixed the damage: In this case you can try to go back to install rom. If it work, that is great. If still get stuck as before then you will need to do re-partition.
Guide for the most suitable re-partition scheme after scanning partitions (read carefully for the best result):
1. In case you do not find bad blocks in the above 4 partitions, the problem is certainly not related to partitions fault. Then you should explore other unbrick methods, using Heimdall to flash instead of odin for example.
2. In case there are fault in both partition 9 and 10 then follow steps in point from 5.1 to 5.3 below. applying this scheme of re-partition should work in most cases!.
3. In case there are faulty in partition 9 only, then can follow steps in point 7 to save some more space.
4. In case there are faulty in partition 10 only, then can follow steps in point 7 to save some more space.
5. In case there are faulty blocks in Cache partition, then follow point 5.4
6. In case there are faulty in partition 11: go to point 8 .
---------------------
5. Re-partition workaround for case of faulty in partitions 9 and 10::
5.1 remove partitions to get rid of the faulty ones and make space available for new ones:
That will remove three partitions factoryfs (9), datafs (10) and UMS (11) so as to make rooms for new partitionsCode:~ # parted /dev/block/mmcblk0 (parted) print (parted) rm 9 (parted) rm 10 (parted) rm 11
5.2. To create three new partitions from the good area:
Code:(parted) mkpart primary 3322.881536 4216.268288 (parted) mkpart primary 4217 6364 (parted) mkpartfs primary fat32 6364 15200 (parted) name 9 FACTORYFS (parted) name 10 DATAFS (parted) name 11 UMS
Notes: You can also use custom pit provided in 2.0 to re-partition in this case.
-------------
5.3. Convert format for 9 and 10: The above steps have created three new partitions. However, for 9 and 10 the format is ext2 and now need to be converted to ext4.
The easiest way is to go back to CWM in your phone. Then, go into mounts and storage menu and choose format /system and format /data. It will convert file system of partition 9 and 10 to ext4 automatically for you.
If the above steps are successful then check:
Code:~ # parted /dev/block/mmcblk0 (parted) print
Note: after printed partition and they look fine, then should check again the partition using dd command to scan partitions 9, 10, 11 as in the step 4 to make sure that newly created partition are fault-free. If they continue to report faulty block then you will need to do re-partition again and create new partitions in the new range (by changing start and end number of partitions).
------------
Dealing with Cache partition:
5.4. It is very, very unlikely that Cache is also faulty but in case there is you can follow steps below to deal with it.
First should remove and recreate with same size and location:
Then recreate it:Code:(parted) rm 7
Then you can go into CWM and format /cache, it will convert file system to ext4.Code:(parted) mkpartfs primary ext2 54.5 264 (parted) name 7 CACHE
In case parted give I/O error then you can try to reduce the size of cache to 128MB, choose the start and end number somewhere in the space from 54.5MB to 264MB.
6. Suggestions for rom installations:
It is recommend to use a custom GB rom (Darky GB, CheckRom GB, and Rocket GB...)they are old but very good roms. Dowload links and instructions for installation can be found in this link. Custom ICS roms (such as Rocket ICS, CleaNote ICS...) are also good. They can be found from the same link for GB rom provided or from the Note development sections. Using CM9 ICS such as Nightlies is recommended since it is safe and very lightweight (less than 140 MB) so it is quick to download.
Note: Flash custom rom by CWM (load rom.zip from computer to internal or external sdcard and flash) seem to be a better way than using odin and is recommended but you can try both.
7. Guide for some cases of only one partition have faulty blocks:
7.1. In case you scan partition and identify that there are damage only in partition 9 (factoryfs) then you can remove 9, 10, and 11 and then start making partition from 1174 MB:
Then go into CWM to format system and data. Then you can install rom.Code:(parted) rm 9 (parted) rm 10 (parted) rm 11 (parted) mkpart primary 1174.405120 2067.791872 (parted) mkpart primary 2068 4215 (parted) mkpartfs primary fat32 4215 15200 (parted) name 9 FACTORYFS (parted) name 10 DATAFS (parted) name 11 UMS
7.2. In case you identify that there is faulty blocks in partition 10 only (datafs) then you can remove 10 and 11 only (leave 9 alone) and start making partition 10 from 3322 mb:
Code:(parted) rm 10 (parted) rm 11 (parted) mkpart primary 3322 5469 (parted) mkpartfs primary fat32 5469 15200 (parted) name 10 DATAFS (parted) name 11 UMS
Then go into CWM and format data. and you can install rom.
It is also known that the hidden partition (partition 12) is not needed for normal use and install of roms. So you can delete it and enlarge the UMS partition (to 15800mb) and you will have a larger sdcard to use.
It is also noted that the size of datafs partition does not need to be exact 2147 mb so you can create it with the size of 2000 mb or smaller or bigger as you wish.
Still the size of factoryfs partition has to be correct so that odin will accept it when flash.
8. In the case of damage in partition 11 (UMS) this often also go with damage in partition 9 and 10. In this case I have worked out 5 options of partition scheme. You need to try from one to 5. One of those should work for you.
You can also use one of the custom Pit files provided at 2.1 to 2.5 above.
Option 1:
After done, reboot into recovery format system, format data. Then you can proceed with install stock or custom rom.Code:~ # parted /dev/block/mmcblk0 (parted) print (parted) rm 9 (parted) rm 10 (parted) rm 11 (parted) mkpart primary 4608 5501.386752 (parted) mkpart primary 5501.386752 7648.8704 (parted) mkpartfs primary fat32 7648.8704 15200 (parted) name 9 FACTORYFS (parted) name 10 DATAFS (parted) name 11 UMS
If it get errors when create partition or CWM get stuck during format then you need to try the next option of partition scheme as below.
Option 2:
Option 3:Code:(parted) mkpart primary 6400 7293.386752 (parted) mkpart primary 7293.386752 9440.8704 (parted) mkpartfs primary fat32 9440.8704 15200
Option 4:Code:(parted) mkpart primary 7936 8829.386752 (parted) mkpart primary 8829.386752 10976.8704 (parted) mkpartfs primary fat32 10976.8704 15200
Option 5:Code:(parted) mkpart primary 9216 10109.386752 (parted) mkpart primary 10109.386752 12256.8704 (parted) mkpartfs primary fat32 12256.8704 15200
Code:(parted) mkpart primary 11,008 11901.386752 (parted) mkpart primary 11901.386752 14048.8704 (parted) mkpartfs primary fat32 14048.8704 15200
9. Notes on recovering files from brick phone: For recovering data from internal sdcard, there are few ways below:
- You can try to install aroma file manager under CWM recovery using file from here. It works under recovery environment and allow you to copy files from internal sdcard to external sdcard.
- If that does not work, you can follow the guide until step 4, then in step 5 remove only partition 9 and 10 and leave partition 11 alone. Then try to create a full size partition 9 (factoryfs) with about 800MB and a very small size (100mb) partition 10 (datafs) and fit these two partitions within the remaining good area in the range from 281mb to 3322mb. Then you can install a custom rom and get it working to copy files to your PC. After that you can remove partition 11 to make full size partition 9 and 10 with steps as in the guide.
- Also you can adb shell, then list directory and files in internal sdcard (~ # ls /sdcard ...etc) and then adb pull files from internal sdcard to your PC one by one.
If you like to know more about using parted, go to the documentation page here:
http://www.gnu.org/software/parted/manual/html_mono/parted.html
Update of progress: As rough figures, more than 100 users have reported successfully revised their Notes after fixing partitions problems using either manual/adb methods or custom PIT file method from Hg42 or combined both. Re-partition have revised many super-bricks Notes!.
If you can revive your Note please share your success with us so that we can share your good feeling!
And press thanks if you find this guide useful. Thanks.12I was on Offical leaked Taiwan version of ICS, then i decided to move to XXLPY version of ICS. I went to CMW to full wipe data, but for some reason, my note froze during data wiping...
I have waited long enough, but it was froze. With no choice, I removed the battery then tried to boot, but it was stuck on the first screen.
From then on, I have tried to recover my note using various Offical ROMs, the taiwan leak, German leak and even old GB ROMs, but I am stuck at Factoryfs...
I am pretty sure Ive tried everything, add PIT and not add PIT, Kernel, etc...
For some reason, Kernel can be flashed just fine, but when it comes to ROMs, it stucks at this screen.
Please, any help is appreciated
--------------------------------------------------------------------------
That was my situation 3 days ago, but i managed to get it back to life from this post by Forest1971:
http://xdaforums.com/showpost.php?p=26285877&postcount=12
Thank you Forest1971 for this great guide3
Yes in post 12.
Also Matiasg85, Uggies and other people in the forum can also help.
Goodluck
---------- Post added at 01:03 AM ---------- Previous post was at 01:01 AM ----------
Wow. I love every time to see that kind of report.
thanks you too. But remember to press some thanks to me and others too!. Thanks3
Thanks for nice comments!
Yes. I guess it is useful partition tools for all android devices.
cheers
---------- Post added at 09:41 AM ---------- Previous post was at 09:36 AM ----------
I am very happy too to see you get your Note back working again. Congratulation!
The speed of 1.5 MB per second is not too slow.
cheers,
thanks you very much from the bottom of my heart
i did like you told me (parted) print to check if its ext2 or ext4 so its ext4
pleaze check my screenshot and told me if everything is correct now bcz i checked my internel phone storage its 798 mb only b4 it was about 2 gb
Yes it looks fine.
Also the internal storage (datafs partition) is now only 850mb which I think is quite sufficient. It is good that now you still have a large sdcard partition of more than 11GB, so you did not loose any useful space.
In case your internal data partition fill-up and not enough for installing more applications (which I doubt will be the case for most users) you can go back and change the size again (taking the space from UMS partition).
About slow data transfer: my phone also have similar slow data transfer even though I have not messed with it's partitions. So I am not sure why yet.
cheers3thanks uggies for the guide
yesterday i had hard-brick but was fixed by adb shell with this guide
i deleted 4 partitons FACTORYFS,DATAFS,UMS and CACHE and i recreated them again i'm over the moon and alive again
It is forest1971 who wrote the guide and you should be thankful to him
Also, I am very happy to hear that your note have been unbricked ! Life is good again yay?
Forest, you have got quite a few successors today havent ya ?
Cheers mate
