[Guide]How to revive your bricked Gnote

[shkippo]

I am very happy too to see you get your Note back working again. Congratulation!

As for the partition format just go back to adb shell and run parted then print command you can see the partition table with the format again.

If it is still ext2 you can repeat the 4 steps to convert it to ext4, (or you can format it using cwm it should convert as well.)

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

 

[rizdroid]

Thank you!

I'm not bricked, but I have to thank Uggies for creating this thread, forest1971 for sharing his knowledge and for his dedication/patience, and all the users who have been reporting their progress.

I've learned a lot in here. The info found in this thread is not only useful for Note. Definitely, it's a must read/follow thread.

Thx!

 

[forest1971]

I'm not bricked, but I have to thank Uggies for creating this thread, forest1971 for sharing his knowledge and for his dedication/patience, and all the users who have been reporting their progress.

I've learned a lot in here. The info found in this thread is not only useful for Note. Definitely, it's a must read/follow thread.

Thx!

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.

cheers

 

[oseeeo]

Thanks for sharing good news. Very happy to see you get it work again.

It seems that the new partition will need a custom PIT with the updated info from the new partition table to work. There is custom PIT file made by hg42 (in another thread in general) which will help to repartition if you do not have any faulty area in your former sdcard area. Try with that PIT and if you get success will be able to flash via odin again.

One the other hand, flashing a large rom file through usb cable can also has chance to make things go wrong especially if you use non-standard usb cable.

Therefore, flashing from cwm is not a bad idea.

There are ways to convert .tar rom to .zip for using with CWM but also a bit complicated. below is oneway. I've not tried it yet.

http://forum.xda-developers.com/showthread.php?t=1405041

Yes, it's work good. But lose 3Go of memory when you don't have an other SD it's a little bit huge lol. And I would not have time to try again. I will try to change the phone where I buy it but it's not sure that will work. So I hope, at least, that they would be ok to repare my phone.

 

[a1919kimo]

i flash the tar file, but still can not into recovery mode!!

 

[forest1971]

i flash the tar file, but still can not into recovery mode!!

But could you get into recovery before?

Sometime it is just need to do the procedures in a right way:

"Hold down Volume Up, Center Home button, and Power buttons together and let go of Power button after your Galaxy Note resets then shows the Galaxy Note splash screen."

Otherwise, there maybe other problem with your phone that prevent it from getting into recovery.

 

[a1919kimo]

But could you get into recovery before?

Sometime it is just need to do the procedures in a right way:

"Hold down Volume Up, Center Home button, and Power buttons together and let go of Power button after your Galaxy Note resets then shows the Galaxy Note splash screen."

Otherwise, there maybe other problem with your phone that prevent it from getting into recovery.

Yes, I always flash the custom ROM via recovery, so I know the way into recovery !!

Other problem?? What can I do?

 

[forest1971]

Yes, I always flash the custom ROM via recovery, so I know the way into recovery !!

Other problem?? What can I do?

I mean if before flash kernel.tar can you get into recovery. if yes, then just try to flash the kernel again. also try speedmod kernel as well since people get in work with speedmod.

If you could not get into recovery before flash kernel.tar then there may be other problem with the recovery.

 

[a1919kimo]

I mean if before flash kernel.tar can you get into recovery. if yes, then just try to flash the kernel again. also try speedmod kernel as well since people get in work with speedmod.

If you could not get into recovery before flash kernel.tar then there may be other problem with the recovery.

I can not get into recovery, speedmod kernel tried already yesterday.
When I flash ROM via Odin that stay factoryfs.

 

[forest1971]

I can not get into recovery, speedmod kernel tried already yesterday.
When I flash ROM via Odin that stay factoryfs.

Maybe try to flash the custom PIT file from hg42 in another thread in general. see how it goes.

 

[Herk718]

Maybe try to flash the custom PIT file from hg42 in another thread in general. see how it goes.

I had the same problem and this is what I did, I flash the kernel tar file (with a custom recovery), Custom pit file, the CSC file from any stock rom along with the modem file. And after flashing, it should boot into recovery by itself and do some sort of update. After that recovery should work fine, then you can flash (in CWM)the 4pda kernel with custom recovery zip not tar.

 

[unkeen]

Superunbricked:

I unbricked my N7000 with forest1971's instructions. Out of routine, I made a data and dalvik cache erase and the bug hit me hard.
I thought that it has to be the partition map and forest1971 had the idea to use parted. THANK YOU!
Installed kernel via odin, went into recovery, rm 9,10,11 and recreated them following the guide. Afterwards I flashed a GB-rom via ClockworkmodRecovery "ROCKET-v22-LA6-eybee1970.zip" which works like a charm.
And my Note is back! Thank you very much.


By the way. Shame on Samsung for not helping or fixing the bug!!

 

[forest1971]

I unbricked my N7000 with forest1971's instructions. Out of routine, I made a data and dalvik cache erase and the bug hit me hard.
I thought that it has to be the partition map and forest1971 had the idea to use parted. THANK YOU!
Installed kernel via odin, went into recovery, rm 9,10,11 and recreated them following the guide. Afterwards I flashed a GB-rom via ClockworkmodRecovery "ROCKET-v22-LA6-eybee1970.zip" which works like a charm.
And my Note is back! Thank you very much.


By the way. Shame on Samsung for not helping or fixing the bug!!

Very nice to hear that !

cheers

 

[shkippo]

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.

cheers[/QUOTE]

its not a big problem but i surprised when i saw it about 800 mb and b4 it was about 1890 mb

and like you said i can take space from UMS but i dont want to take risk again

anyway if someone else have that space like i had and want to take space from UMS what they should do this time !!!! bcz now after we revive our note we only have prob with low space not in FACTORYFS so they should do all the method in CMD or only They should work in UMS and DATAFS ?????

thanks you again for your patience


P.S : i already sell my black note

and soon of possible i will get a white note and i will never do again the same fault in ICS never wipe or format
and i hope this bug go away in the new ICS samsung firmware
good luck for everyone and thanks you all especialy a big thanks for forest1971 and Uggies

---------- Post added at 01:27 PM ---------- Previous post was at 01:19 PM ----------

I unbricked my N7000 with forest1971's instructions. Out of routine, I made a data and dalvik cache erase and the bug hit me hard.
I thought that it has to be the partition map and forest1971 had the idea to use parted. THANK YOU!
Installed kernel via odin, went into recovery, rm 9,10,11 and recreated them following the guide. Afterwards I flashed a GB-rom via ClockworkmodRecovery "ROCKET-v22-LA6-eybee1970.zip" which works like a charm.
And my Note is back! Thank you very much.


By the way. Shame on Samsung for not helping or fixing the bug!!

i am really happy for you i know thats feelings

and really shame on samsung bcz its not a normal phone its an expencive phone

and a little fault wiping in recovery we will lost our note really shame

 

[a1919kimo]

I had the same problem and this is what I did, I flash the recovery tar file, the pit file, the CSC file from any stock from along with the modem file and after flashing it should boot into recovery on its own and do should sort of update. After that recovery should work fine, then you can flash the 4pda custom recovery zip not tar.

The recovery tar file means Kernel with CWM or so on?
Would you please the offer the links?

 

[Herk718]

The recovery tar file means Kernel with CWM or so on?
Would you please the offer the links?

Here you go: View attachment speedmod-kernel-n7000-k2-12-Odin.tar

Let me know if it works out.

 

[a1919kimo]

Here you go: View attachment 1092747

Let me know if it works out.

Thx, but I did it by flashing pit from hg42!!

Maybe try to flash the custom PIT file from hg42 in another thread in general. see how it goes.

C:\Users\Moore>cd Downloads

C:\Users\Moore\Downloads>cd tools

C:\Users\Moore\Downloads\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
304D19EC6613792F recovery


C:\Users\Moore\Downloads\tools>adb shell
~ # umount/cache
umount/cache
/sbin/sh: umount/cache: not found
~ # pwd
pwd

~ # umount/cache
umount/cache
/sbin/sh: umount/cache: not found
~ #

Is it normal??

 

[forest1971]

Thx, but I did it by flashing pit from hg42!!



C:\Users\Moore>cd Downloads

C:\Users\Moore\Downloads>cd tools

C:\Users\Moore\Downloads\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
304D19EC6613792F recovery


C:\Users\Moore\Downloads\tools>adb shell
~ # umount/cache
umount/cache
/sbin/sh: umount/cache: not found
~ # pwd
pwd

~ # umount/cache
umount/cache
/sbin/sh: umount/cache: not found
~ #

Is it normal??

OK so you have been able to get into recovery and run adb. good progress.

Just ignore that and go on with parted and print. see how it goes.

 

[a1919kimo]

OK so you have been able to get into recovery and run adb. good progress.

Just ignore that and go on with parted and print. see how it goes.

/sbin/sh: parted/dev/block/mmcblk0: not found
~ #

not found again...

 

[forest1971]

/sbin/sh: parted/dev/block/mmcblk0: not found
~ #

not found again...

Try to copy the zip file attached from your computer to sdcard and flash it with cwm.

Since the current kernel does not have the tools needed.