Problem: Brickad s3:a?

Har du provat med den lösningen som beskrivs i S-Droids länk?

 

Du ska inte packa upp dem en extra gång utan det är .tar eller .tar.md5 du använder i Odin. Men filnamnet du skrev (I9300lfb...) verkar rätt.

 

Jag har provat att flasha .PIT -filerna för sig själv och det funkade inte. Provade även att flasha PIT + Stock PDA med samma resultat. Jag fattade det som att man var tvungen att flasha in en 3-parts firmware samtidigt som PIT-filen om jag förstod den följande diskutionen på XDA rätt.

 

Jag vet att man inte gör så vanligen men eftersom inget annat funkar så är min sista utväg en 3-parts firmware troligen.

 

Jo men att packa upp dem en gång till är inte 3partsgrejen. Du behöver filer som heter code.tar, modem.tar och csc.tar (med en massa extra siffror och bokstäver i filnamnen) som ska till pda/phone/csc i Odin. Har du kollat att re-partition är ikryssat när du lagt in pit-fil?

 

Dock kan du bli lurad om ditt tex zipprogram är inställd att visa alla filer som zip.
Så var de på min dator.
Klickade bara ur .tar filer

 

josåatt: Jo, re-partition blir automatiskt ikryssat när jag väljer en PIT-fil. Har du något tips på vart jag kan hitta dom filerna?

moparlinke: Ok, men förstår inte riktigt vad du menar? vad ska jag packa upp för något?

 

Antar att det är ungefär samma sak som när man brickat sin Galaxy Note.
Kolla i Note avdelning under rom, eller sök.
Ska finnas lösning hur man gör.

 

ok, ska kolla. Jäkligt irriterande när telefonens grundfunktioner ändå verkar funka. Startar jag den som vanligt så kommer jag in och kan tillockmed starta någon app om jag är snabb innan den startar om.

Download mode funkar men failar när jag försöker flasha.

CWM funkar tills jag försöker wipa, eller installera någon rom. Såg att det fans repartition SDcard i CWM menyn. Skulle det vara någon ide att prova det? och vad ska jag välja på nästa steg isåfall? måste välja storlek eller något på partitionerna.

 

När du packar upp den rätta filen får du minst 3 .tar.md5
Code,,csc,modem
Då ska du använda pit filen, kolla på bilden ovan


Skickat från min GT-I9300 via Tapatalk 2

 

Du ska från XDA eller Samfirmware hämta hem 3-paket med csc.tar, pda-tar och modem.tar. Dom lägger du på rätt plats i Odin, samt pit-filen på rätt plats. Sen flashar du. Och fungerar inte en pit-fil så provar du nästa med samma procedur. Här nedan har du en lista på vilka som har provats i tråden, du får dock leta efter dom själv.

GT-I9300_mx_20120220.pit
GT-I9300_mx_20120322.pit
GT-I9300_mx_20120329.pit
M0_20120220.pit
mx.pit

with the third one I was able to get recovery mode again but not sure if it's really the good one
I have a Belgian unlocked phone (provider is Proximus (Vodafone group))

I'll try all pit files again while installing stock ROM (3files: PDA,phone,csc) via ODIN

 

Detta är hur de ska gå på Note, borde fungera på S3, men vad vet jag, äger ingen S3.
(Du återskapar factoryfs)

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 to hg42's thread
to get the PIT file and how to flash.

The custom PIT should work in majority of cases that have partition problems. Someone may ask a question: how do I know if there are faulty blocks in the partition or not and where, in which partitions, they are. The answers to that question can be found by scanning partitions for errors, with the procedures described in the manual method below (need to go until steps 4 to find the answers). in Short: the manual method will give more control over scanning for partition errors, size and location of new partitions which can save you some more memory space, but the PIT method is easier for new users. Also, you can also combine two methods in an intuitive way to fix your brick Note.

-----------------------------------
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. Requires some basic knowledge of MS-DOS and adb (few simple commands).
3. Partitions can be delete and recreate like in a computer hdd but requires more skills.
4. If you like to recover data from your internal sdcard (photos, music, books...) you should look at Item 6 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
- download and install the attached 4pda_kernel.tar, which has the partition tools and CWM with it, although it will raise flash counter. To avoid that you can download and install the CWM_4pda_kernel.zip (also attached in the post) by putting it in sdcard and flash with your existing CWM.
- 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:
Code:
adb shell
it should give you the sign like this: ~ #

Then run (noted that umount is without N):
Code:
~ # umount /cache
~ # umount /system
~ # umount /data
If one of those "umount /" commands return "invalid argument" just ignore it and continue with next steps.
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.
Code:
~ # parted /dev/block/mmcblk0
if it aska you to fix something just choose yes. It should give you bellow:

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:
Code:
(parted) print
It will give you a picture of your Note’s partitions as in the screen shots I have attached. (text version is below):
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:
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
Code:
(parted) check 11
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.

For a more thorough scan of partition 11 you can use this command (it only read partition bit by bit and no write, so it is safe):
Code:
~ # dd if=/dev/block/mmcblk0p11 of=/dev/null
if it freeze or run too long (more than 10 minutes), then it means you have some damage in that partition and read command failed.

For other ext4 partition (partition 7, 9, and 10) you can use the same dd command above (just need to change partition number-p11 to the respective number) or you can use e2fsck as below. The benefits of using e2fsck is that it can help repair some minor file system faults and in some case solve the problems without the need of further re-partitioning.

It is noted that e2fsck should be run after "umount" the partition using the commands in step 3 above.

For example, if you like to check partition 7, which is cache, then run:
Code:
(parted) quit
~ # e2fsck -f -c –y /dev/block/mmcblk0p7
You can do the same with 9, 10.

If e2fsck report bad block not found it is good Or if it does not freeze then it means it has effectively dealt with the file system corruptions. If it freezes it means the errors caused by EMMC bug and cannot be repaired. In that case you will need to do re-partitioning workaround to leave those faulty areas unused.

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.

Below are further steps to do manual re-partitioning using parted.

---------------------

5. Start dealing with partitions: Now just suppose that you have 2 faulty system partitions: factoryfs (partition 9) and datafs (partition 10), 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:
~ # parted /dev/block/mmcblk0
(parted) rm 9
(parted) rm 10
(parted) rm 11
That will remove three partitions factoryfs (9), datafs (10) and UMS (11) so as to make rooms for new partitions

5.2. To create three new partitions from the good area:
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. For example:
- after you run "(parted) mkpartfs primary ext2 3322 4215" it returned "Error: Input/output error during write on /dev/block/mmcblk0
Retry/Ignore/Cancel?"
- then press "c" and "enter".
- Then create partition in the next block range below:
Code:
(parted) mkpartfs primary ext2 4215 5108
(parted) mkpartfs primary ext2 5108 7255
(parted) mkpartfs primary fat32 7255 15200
Continue to move up until parted is happy with the block range chosen. (You need to make some calculation of partition size, the start and end block for the code above, follow the example given).

Once done, with 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.

Code:
(parted) rm 7
Then recreate it:
Code:
(parted) mkpartfs primary ext2 54.5 264
(parted) name 7 CACHE
Then you can go into CWM and format /cache, it will convert file system to ext4.

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. 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.

7. 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).

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.

If you like to know more about using parted, go to the documentation page here:
http://www.gnu.org/software/parted/m...no/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.

 

Hyper-skummt. jag kan starta telefonen som vanligt om jag snabbar mig att avaktivera Wifi och mobildata. Kan man göra något mer i det läget?

 

Okeeej.... låter som att nåt blivit knas med din radio!?
Tanka ner den senaste och flasha med Mobile Odin Lite. Finns på market eller xda.

Sent from my Nexus 7 using Tapatalk 2

 

just pgr utav detta jag håller mig ifrån att roota och lägga in roms, men jag hoppas verkligen du löser dit problem!

Skickat från min GT-I9300 via Tapatalk 2

 

Har du testat 3-part romen ännu?

 

Finns dom som får fel på telefonen utan att roota och byta roms också så helt säker är du inte

 

Jag hittar tyvärr ingen 3-parts rom varken på samfirmwares eller någon annan stans. Vet inte riktigt vard jag ska prova nu. Man kanske kan göran något magiskt via adb?

 

säkerligen, men det måste vara något mer allvarligt fel eftersom jag varken kan flasha in något i CWM eller via odin

 

Installera om drivrutiner och starta om både dator och mobil.Kontrollera så kies inte är igång i bakgrunden på din pc. testa sen igen. Fungerar inte det så testa odin mobile!

Har du kikat på tråden "flasha stock ROM"? ska inte behövas med 3e part flash