[Guide]How to revive your bricked Gnote

[shkippo]

new other solution !!!!!!

when i am surfing ce4arab website i found a simple new solution and its back the note to life and you can flash via odin normal

first flash via odin the pit brick patched

after done flash via odin ( N7000XXLA3_N7000OXALA3_OXA )

1-BOOTLOADER: KERNEL_N7000XXLA3_CL880036_REV02_eng_mid _noship.tar.md5
2-PDA: CODE_N7000XXLA3_CL880036_REV02_user_low_ ship.tar.md5
3-PHONE: MODEM_N7000XXLA3_REV_05_CL1095424.tar.md 5
4-CSC: GT-N7000-MULTI-CSC-OXALA3.tar.md5
5-UMS: UMS_N7000XXLA3_CL880036_REV02_user_low_s hip_16GB.tar.md5

please try it and let me know

about me i sell my note today b4 i tried this solution

hope for you a good luck

 

[a1919kimo]

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.

Microsoft Windows [版本 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Moore>cd Downloads/

C:\Users\Moore\Downloads>cd tools

C:\Users\Moore\Downloads\tools>adb devices
List of devices attached
304D19EC6613792F recovery


C:\Users\Moore\Downloads\tools>adb shell
~ # umount/cache
umount/cache
/sbin/sh: umount/cache: not found
~ # parted/dev/block/mmcblk0
parted/dev/block/mmcblk0
/sbin/sh: parted/dev/block/mmcblk0: not found
~ #


I installed the zip file via CWM and reboot in recovery!!
Should I replace with abyss kernel ??

 

[forest1971]

Microsoft Windows [版本 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Moore>cd Downloads/

C:\Users\Moore\Downloads>cd tools

C:\Users\Moore\Downloads\tools>adb devices
List of devices attached
304D19EC6613792F recovery


C:\Users\Moore\Downloads\tools>adb shell
~ # umount/cache
umount/cache
/sbin/sh: umount/cache: not found
~ # parted/dev/block/mmcblk0
parted/dev/block/mmcblk0
/sbin/sh: parted/dev/block/mmcblk0: not found
~ #


I installed the zip file via CWM and reboot in recovery!!
Should I replace with abyss kernel ??

If you already installed the CWM-4-pda.zip and still cannot runt parted then it looks like there is a more serious problem here. In another forum there a similar case which is quite difficult.

I would just need to try to install one of the kernel with cwm suggested and see if you can run adb then parted print and can see partitions.

Someone also suggest thor kernel which can be download from this site:

http://www.tegraowners.com/?cat=95

Also the method suggested in some post above can also be tried.

 

[speterlau]

millions of thanks

thanks!! forest1971 and other members!!
I have to express my gratitude to u guys after unbricking my gnote.
Here is the story. I used officical ICS which was updated from GB through KIES. First I rooted the ics phone with SU-Busybox-Installer & CWM.zip successfully. After reboot, it looked fine. Then I tried to enter cwm recovery and I found that it was official recovery mode. I decide to install CWM.zip again and I successlly entered CWM recovery. After that, I installed abyssnotekernel42cwtouchoriginalLogo.tar without reboot recovery, and click factory reset.
The nightmare came...................
It shucked at factory reset about 5mins and then reboot. The boot screen was shucked. I can't even enter recovery mode.

Here is what i did after that.
1) Flash GB stock rom using Odin v1.85 (tried 2 versions of GB stock rom), Stuck at FACTORYFS.img
2) Flash abyssnotebkernel using Odin v1.86, success! I could enter cwm recovery. Surprise me!

I kept search about brick, unbrick, etc..... and I read a lot about corrupted ICS. therefore, i m afraid to do any more progress. Finally I found your guide to unbrick my gnote. My Gnote revived!!!

Here is the question.
Is it ok if I flash abyssnotebkernel successfully and conduct full wipe under official ICS?
What should and shouldn't I do to deal with the faulty system partitions? Will it affect the firmware update through KIES or Odin?

 

[forest1971]

thanks!! forest1971 and other members!!
I have to express my gratitude to u guys after unbricking my gnote.
Here is the story. I used officical ICS which was updated from GB through KIES. First I rooted the ics phone with SU-Busybox-Installer & CWM.zip successfully. After reboot, it looked fine. Then I tried to enter cwm recovery and I found that it was official recovery mode. I decide to install CWM.zip again and I successlly entered CWM recovery. After that, I installed abyssnotekernel42cwtouchoriginalLogo.tar without reboot recovery, and click factory reset.
The nightmare came...................
It shucked at factory reset about 5mins and then reboot. The boot screen was shucked. I can't even enter recovery mode.

Here is what i did after that.
1) Flash GB stock rom using Odin v1.85 (tried 2 versions of GB stock rom), Stuck at FACTORYFS.img
2) Flash abyssnotebkernel using Odin v1.86, success! I could enter cwm recovery. Surprise me!

I kept search about brick, unbrick, etc..... and I read a lot about corrupted ICS. therefore, i m afraid to do any more progress. Finally I found your guide to unbrick my gnote. My Gnote revived!!!

Here is the question.
Is it ok if I flash abyssnotebkernel successfully and conduct full wipe under official ICS?
What should and shouldn't I do to deal with the faulty system partitions? Will it affect the firmware update through KIES or Odin?

Hi good to hear it helps .

No body seems to have tried with updating through Kies.

As for Odin: it looks like after we re-partition we need a customized PIT file which reflect the exact new partition scheme in order to flash successful with Odin.

There has been a custom PIT file by member hg42 that can be used for the case that you have no faulty block on UMS partition (actually suggested in few post above). You can try it. Still I would suggest using CWM to install roms. It still works well. cheers.

 

[a1919kimo]

If you already installed the CWM-4-pda.zip and still cannot runt parted then it looks like there is a more serious problem here. In another forum there a similar case which is quite difficult.

I would just need to try to install one of the kernel with cwm suggested and see if you can run adb then parted print and can see partitions.

Someone also suggest thor kernel which can be download from this site:

http://www.tegraowners.com/?cat=95

Also the method suggested in some post above can also be tried.

the kernle (thor-kernel-v0.4+Thor-Recovery-1.8-cwm) I flashed, not find...
is the method of hg42 suitable for me?

 

[forest1971]

the kernle (thor-kernel-v0.4+Thor-Recovery-1.8-cwm) I flashed, not find...
is the method of hg42 suitable for me?

Just need to try it. It works if their is no faulty blocks in UMS partition.

 

[a1919kimo]

Just need to try it. It works if their is no faulty blocks in UMS partition.

thor-kernel-v0.4+Thor-Recovery-1.8-cwm I flashed reboot into recovery mode, install the ZSLA2, it work...
Now I am restoring my back up...
But I got the problem with attached picture, my USB storage is smaller, should I flash a pit (16G) again?

 

[forest1971]

thor-kernel-v0.4+Thor-Recovery-1.8-cwm I flashed reboot into recovery mode, install the ZSLA2, it work...
Now I am restoring my back up...
But I got the problem with attached picture, my USB storage is smaller, should I flash a pit (16G) again?

Good to see you get it working again .

No you should not flash that PIT since you need a customed one. If you flash the original PIT things would most certainly to mess up again.

You loose some space of sdcard because those are faulty areas that cannot be used. But I can see you have large storage, is your Note 32gb version or is your Note somehow can support external card?

 

[a1919kimo]

Good to see you get it working again .

No you should not flash that PIT since you need a customed one. If you flash the original PIT things would most certainly to mess up again.

You loose some space of sdcard because those are faulty areas that cannot be used. But I can see you have large storage, is your Note 32gb version or is your Note somehow can support external card?

it happened again by flashing another pit file, 32G is external storage...
I can not into recovery mode again and I follow the way of mine, it does not work this time...

---------- Post added at 08:43 PM ---------- Previous post was at 07:48 PM ----------

it happened again by flashing another pit file, 32G is external storage...
I can not into recovery mode again and I follow the way of mine, it does not work this time...

It works again, steps that I find.

1.flash pit that hg42 attached via odin. (now can be into recovery)
2.flash the kernel thor-kernel-v0.4+Thor-Recovery-1.8-cwm, reboot in recovery.
3.flash the ROM ZSLA2(including root+CWM) via CWM
4.restore my back up via CWM.

step 2 is necessary, I have no idea why it is necessary.

but the atorage is the asme, would you please offer the pit of custome?

 

[apurvapatel]

CWM flashable stock ics rom

Thanks to Uggies for the thread and Forest and Prabhu for the solutions and all the posters and their success stories.

Solved my problem.... revived my almost dead note back on abyss 3.9 kernel and XXLC_CheckROM_NoteHD_V6 rom.... But now my counter is up to about 17.

Where can i find a CWM flashable stock ICS rom to use the triangleaway app? I cant use odin, freezes at the start of factoryfs write.

Apurva

 

[Archangel919]

bring back your phone from super brick

No need to go to any service centre and pay thousands to sammy service center ppl.

Yahooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo yessssssssssssssssssssssssssssssssssssssssssssssssssssssssss, it worked it worked it worked , my giant beauty is back to life , my galaxy note is breathing android again

Thanks a lot Forest 1971 (I think he liked Forest Gump ),but what a genius he is , he helped m bring back my phone to life .

Guys , i had installed ****ing KingDroid rom v2.1 with S3 mod on it , and i after i used it for a while i felt like going back to cyanogenmod 9 nightly . But was foolish enough to do a data wipe and factory reset on LPF or LP8 based rom :-( , what an idiot i was . I had read clearly to not to do that mistake but yet i did it !!!!!!!. i thought my phone's final resting place was either dustbin or in samsung service center , where i had to pay around 10,000 Indian Rupees , roughly 200$ t fix my phone !!!!!!!!!!!!!!!!
But no , i sat for an hour , read the method explained by Forest 1971 and followed it , and flashed checkrom v6 . And Boom , it started .Guys download android sdk from developers.android .com and install it . It has in built adb ( Android Debug Bridge ) , the download link posted by Forest , didnt work for me , but i figured out that adb comes pre installed with android sdk and is present in the platform-tools folder . So add its link or full path to the environment variable and follow exactly as mentioned by Forest 1971 . It worked for me . Thank you for all the ppl whose posts helped me get my phone to life , thanks a lot . And very very imp NOTE : KING DROID Sucks and takes life from your phone , so dont do the mistake which i did . And i have tried every single custom rom released till now including paranoid rom (awesome rom ), but the safest , fastest , lag-free , best battery life , Galaxy Note Saviour rom is CheckRom revo v6 . take my word , its the best even though its Gingerbread rom Nd by the way i am just 19 year old computer science engg

 

[Admor]

Yet another Note has came back to life. Thought was done for, but succeded like the others... Hail our savior, forest1971!

 

[ahenderson223]

Is there a youtube video to show step by step directions ?


Sent from my SAMSUNG-SGH-I957 using xda premium

 

[zylor]

No need to go to any service centre and pay thousands to sammy service center ppl.

You don't need to pay nothing.. if you have warranty of your device!

I went to Samsung Service Center and they held my phone for free!

I have my warranty and they will give me a full new motherboard for free

If i didn't had the warranty of my Note i would have to pay at least 350€ or more for the motherboard replacement!

 

[apurvapatel]

Seems my UMS partition has bad sectors too.

I did rm 11 and repartioned it quite a few times... just to check for bad sectors, i partitioned it in ext2 format to run the e2fsck... no error.

Most of the times the phone doesnt boot up, stays stuck at the "Samsung Galaxy Note N7000" screen and its got the dreaded Yellow Triangle...

When it does boot up... it freezes whenever I install any new application.... via market or sdcard... also many times the background applications suddenly force close and the phone freezes.

Tried removing the cache partition and making it again.... no help.

To get the phone to boot, I have to go through the grind.... repartition the whole thing, install 4pda_kernel.tar kernel ... abyss39.zip cwm and checkrom v6 rom.

BTW, my partition is exactly like Forest has suggested in the 12th post, FACTORYFS starts from where USM would actually start, at 3322.... and I have also reduced DATAFS size to 1gb, as suggested.... now my UMS starts at 5362 instead of 6362 as suggested by Forest in the 12th post.

 

[Morality]

Seems my UMS partition has bad sectors too.

I did rm 11 and repartioned it quite a few times... just to check for bad sectors, i partitioned it in ext2 format to run the e2fsck... no error.

Most of the times the phone doesnt boot up, stays stuck at the "Samsung Galaxy Note N7000" screen and its got the dreaded Yellow Triangle...

When it does boot up... it freezes whenever I install any new application.... via market or sdcard... also many times the background applications suddenly force close and the phone freezes.

Tried removing the cache partition and making it again.... no help.

To get the phone to boot, I have to go through the grind.... repartition the whole thing, install 4pda_kernel.tar kernel ... abyss39.zip cwm and checkrom v6 rom.

BTW, my partition is exactly like Forest has suggested in the 12th post, FACTORYFS starts from where USM would actually start, at 3322.... and I have also reduced DATAFS size to 1gb, as suggested.... now my UMS starts at 5362 instead of 6362 as suggested by Forest in the 12th post.

I fixed having to constantly reflash by restoring just the system and boot of an ics lpy nand BackUp i had.

I had to repartition UMS Start and end just Like you, I think i moved them both 300 units up, and im having the same problem as you. Random Freeze, inability to install Apps.. Unfortunately i cant Start trying to Fix this issue until Sunday Night when i get home, so Let me know if you Fix these issues.

 

[talhamid]

Hello

I am a LITTLE closer to rescuing my Note via this method. Now my recovery is wiping and flashing perfectly OK. But nothing boots! I flash the ROMs or NAND backups and they flash OK, but the phone remains stuck in bootloop.

I am trying to flash ICS Stunner ROM by the way, didn't try any of the GB ones. But i do it through Abyss Kernel 4.2 Redpill

Any advice?

 

[derekzxy]

I have just tried the adb shell, however when im doing it up to (parted) print

it thrown me a message as below:

Error: The backup GPT table is not at the end of the disk, as it should be. This
might mean that another operating system believes the disk is smaller. Fix, by
moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel?

I then Key in "Fix" and press enter

Then it thrown another message as below:

Warning: Not all of the space available to /home/henry/testmod.img appears to be
used, you can fix the GPT to use all of the space (an extra 204800 blocks) or
continue with the current setting?
Fix/Ignore?

I then key in "Ignore" and press enter
and the CMD stopped and not going any further

then I turned off the CMD and Reopen and
run
adb shell
run
~ # umount /cache

and then it said
umount: can't umount / cache: Invalid argument

then I ignored this message and
run
~ # parted /dev/block/mmcblk0

then its said
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 i key in Print it said

Error: /dev/block/mmcblk0: unrecognised disk label
(parted)

Then I cant go anything further.........

any suggestion guys , please help....

THanks

 

[talhamid]

forest1971: PLease add me to the list of eternally grateful users who rescued their device through your method. I have no qualms in admitting that I am close to tears. May God bless you and your colleagues.

Yes, it is all a little wonky and yes, I still shudder at the thought of restarting the thing. But that is all trivial compared to a device that is not booting into the OS at all.

Thanks