[HTC Pico (Explorer)] BleedingIris:
[color="red"] [b]

0110…380“30…4010¨¨1WELCOME TO NAND/recovery BURNT ZONE 0110…380“30…4010¨¨1

0„30†2Moved by touch0160†640„30†3Inc.

0110…380“30…4010¨¨1DON'T FLASH AN RUU AT ANY STAGE 0110…380“30…4010¨¨1

0. What's burnt nand?

It's condition caused by overclocking(oc)[CPU oc ,to be specific. For gpu oc,go to the last part of this post question 10 ] resulting in bad blocks all over your system, data, cache and recovery.

Important: Use diskusage app to determine size. Don't go by phone's inbuilt settings

A case of burned /system partition in cm10 beta6 running overnight:

Uploaded with ImageShack.us

A late case of burnt nand of /data :

Uploaded with ImageShack.us

1 &2:Not applicable anymore. Peace!

3. No one has burnt thier nand*it's just some people think that thier nand is burnt * is this true?

Well, I'm sure, going through the forums and q &a ,I know that people have indeed burnt thier nands and some just by using the overclocked kernel without even overclocking.

Sources:

http://xdaforums.com/showthread.php?t=1847002&page=400

http://xdaforums.com/showthread.php?t=2243719

http://xdaforums.com/showthread.php?p=39985385

http://xdaforums.com/showthread.php?p=39799173

http://xdaforums.com/showthread.php?p=39439861

http://xdaforums.com/showthread.php?p=39428922

http://xdaforums.com/showthread.php?p=39402187

http://xdaforums.com/showthread.php?p=38941663

http://xdaforums.com/showthread.php?p=39216556

http://xdaforums.com/showthread.php?p=38945489

http://xdaforums.com/showthread.php?p=39197918

http://xdaforums.com/showthread.php?p=39169697

http://xdaforums.com/showthread.php?p=38657723

http://xdaforums.com/showthread.php?p=40616272

http://xdaforums.com/showthread.php?p=39331139

But below is a strong correlation with bad block proof between overclocking and burnt recovery. Yes it burns recovery too.

http://xdaforums.com/showthread.php?p=39196574

THE ABOVE LINKED POSTS ARE MOSTLY SOLVED BY ME OR SENIOR MEMBER S, BUT SOME HAVE LOST THEIR DEVICES. IF YOU CAN'T FIND THE ANSWER HERE, I SUGGEST YOU READ ALL THE LINKED POSTS-VARIOUS DIFFERENT METHODS HAVE BEEN EMPLOYED.,WHICH ARE TOO LONG TO EXPLAIN HERE. READ AND READ-YOU'LL FIND.

4. What are the symptoms of burnt nand?

Early symptoms:

You'll notice a strong drop in your free space in /data

Late symptoms:

/data free space is Nil /below 50%of what you saw before

Error in /cache /recovery/log.

Error in /cache/recovery/last log.Not readable.

No apps can be installed

Rom lags like hell

No Rom can be flashed /boots

Previous nandroids ,which are successfully restored before fails to restore now.

Really abrupt and fast restores with twrp

RUU cannot be done ~user data(mtd5) fail. System fail (mtd3)

5. How can I diagnose burnt nand early?

If you suspect burnt nand ,

1.Watch out for free space in /data and watch out for sharp reduction.

2.Download this app Disk Usage and watch out for increase in system data in /data

http://xdaforums.com/showthread.php?p=39464989

3.Make a dmesg and look for these errors

http://xdaforums.com/showthread.php?p=36834988

4.Definitive method is this :

1.DOWNLOAD THE TERMINAL.ZIP ATTACHED BELOW

2.EXTRACT TERMINAL.ZIP INTO /SDCARD/lol [create a folder named lol[small letters ]in SDcard, if there already isn't one ]

3.Open terminal emulator on your phone

4.type or copy and paste this code and press enter

su
cp /sdcard/lol/runme.sh /r.sh
chmod 0755 /r.sh
/r.sh

5.if it doesn't work first time, paste twice.

6.If pasting twice doesn't work, type each code one by one -you'll surely get it. Come on-its just 4 lines -type it lazy!

And Now you'll see the number of bad blocks you've got.

You can also Flash the zip below[for which you have to go to recovery ]or execute the attached script badblocks.sh as root.

6. What are the parts affected by burning?

Proved to affect

/Data

/system

/cache

/recovery

Rest is unknown

7. Ok I managed to burn my nand:D What are the recovery procedures available?

I SIMPLIFIED THINGS HERE BY MAKING A FLASHABLE FLASH_ERASE. ZIP[Code named FLASH_ERASEmadeflashablebyBANNED.zip ] it works with twrp2.5 to flash_erase needed partitions. However not tested fully. Problem? Post here.

Other long procedures:

Cute prince recovery procedure:

http://xdaforums.com/showthread.php?p=36868966

I think Cute prince missed this .Just add this at the end

./flash_erase -N /dev/mtd/mtd3 0 0

7.1 I GET FLASH ERASE NOT FOUND?

Flash the flash_erasemadeflashablebyBANNED.zip

Derefas recovery procedure:

derefas was the one who actually gave the idea of recovering nand

http://xdaforums.com/showthread.php?p=36867557

Sachin Thomas recovery procedure

Developed lately *can be done on phone itself */if it didn't involve recovery /*

http://xdaforums.com/showthread.php?p=38941897

Recovery recoveriNG procedure (bhargz16)

http://xdaforums.com/showthread.php?p=39198068

8. I can't find my answer here?

Go to official burnt nand discussion thread

http://xdaforums.com/showthread.php?t=2183130

Or you can ask your questions here.

9.can I Flash any other kernel to prevent overclocking?

You can Flash garuda2.6

Link in latest links post page 1.

http://xdaforums.com/showthread.php?p=38098567

Side effects:

http://xdaforums.com/showthread.php?p=39452607

10. Some more links:

Unknown recovery procedure

http://xdaforums.com/showthread.php?p=36836090

MTD status report:

http://xdaforums.com/showthread.php?p=36837173

11. Cannot go to recovery /burnt recovery /unable to flash recovery?

Not sure of the exact command,but will work.

Use

fastboot boot recovery /sdcard/twrp5.img

or

fastboot boot recovery.img

or

fastboot boot /sdcard/twrp5.img

You need twrp5.img or recovery.img present in /SDcard and renamed like that itself.

After booting into recovery, you can do everything you please. ~flash erase format and install new Rom and boot the device [do ruu here, if you haven't been able to enter hboot before]

After booting up the device, flash erase mtd1 through terminal emulator.and then flash a suitable small recovery. And then pledge here that you'll never overclock ever again.

12. GPU OC ?

gpu oc has been reverted along with CPU oc by sak for burnt nand. But may be added later. but not present in cm released on or two months before 9 may13.

12.1 is it safe?

I don't know. CPU oc did provide burnt nand and bad blocks. Gpu oc may also do some things, which may not be seen as of now. I've seen one case complaining that, after using Cyanogen and going back to stock - games started lagging, which did not lag, when he was in stock before. The reliability is doubtful. But not much people go back to stock either -so not much can be said.

12.2 do you recommend it?

"If any provider of any oc removes the "AS IS" tag and take responsibility,if something happens, then I'll probably may use that oc,otherwise count me out".

12.3 How to remove gpu oc ?

Its present in kernel. Flash another kernel. Or modify source and compile yourself.

Present at arch/arm/mach-msm/msm7x27a.c- kernel source.

Try here

Normal [bus, Gpu] is [0,133330000],[160000000,192000000],[200000000,245760000] I think.

13. Was there anyone unable to recover and lost thier device for ever?

AFAIK,

"The lost thier device for ever list RIP "

Ghostking

Hawk378

And May be many more

Legend *:

Attachment list:

***********************************************************VERY IMPORTANT : UNDER CLOCK BELOW 300MHZ ,IF YOU ARE USING ZIPS WHILE SYSTEM IS RUNNING.AFTER THE TESTS, YOU MAY OVER CLOCK AS YOU WISH. ********************************************************************************************

Provided "AS IS"

1- script to detect badblocks by banned.

2-flashable zip to detect badblocks by btfb0

3-Terminal method to detect bad blocks by banned .

4-flashable zip to detect bad blocks by banned.

5- Recovery procedure to delete bad blocks- Made flashable by BANNED.

All zips posted here has readme.txt files inside it-which are self explanatory to that particular zip.

*USE AT YOUR OWN RISK*