Related
I was running CM7.0.3 and had flashed on a different kernel. It started to run stably for a few days and then started locking up. I had it over clocked to 1.7ghz using setcpu. I decided to use Kernel Manager to put the original CM kernel back on. After it did it I got stuck in a boot loop so I went in to recovery and tried to restore the backup I had from a couple weeks before. It goes through it until it gets to /system and says cant mount /system status 1. I did a little searching and tried using PD15IMG. When I click update everything it goes through says FAIL-PU until it gets to Radio and then just sits there saying updating and never goes any farther. Can I fix this or is my phone ruined? Thanks for any help.
gamershadow said:
I was running CM7.0.3 and had flashed on a different kernel. It started to run stably for a few days and then started locking up. I had it over clocked to 1.7ghz using setcpu. I decided to use Kernel Manager to put the original CM kernel back on. After it did it I got stuck in a boot loop so I went in to recovery and tried to restore the backup I had from a couple weeks before. It goes through it until it gets to /system and says cant mount /system status 1. I did a little searching and tried using PD15IMG. When I click update everything it goes through says FAIL-PU until it gets to Radio and then just sits there saying updating and never goes any farther. Can I fix this or is my phone ruined? Thanks for any help.
Click to expand...
Click to collapse
This issue has cropped up a lot recently. I'm sorry to say it but you might have bricked it. There is a chance though. 2 questions:
1. did you use gfree to root?
2. do you have the engineering Hboot? (.85.2007?)
I did use gfree to root. and i dont have the engineering Hboot.
gamershadow said:
I did use gfree to root. and i dont have the engineering Hboot.
Click to expand...
Click to collapse
Unfortunatly at this time there is no way to fix your situation with out an eng spl. So I hate to be the bearer of bad news but the phone is done.
Sent from my Faux powered Glacier
mark manning said:
Unfortunatly at this time there is no way to fix your situation with out an eng spl. So I hate to be the bearer of bad news but the phone is done.
Sent from my Faux powered Glacier
Click to expand...
Click to collapse
Thanks even if it is bad news. I've only had the phone 10 days. Think tmo would exchange it?
gamershadow said:
Thanks even if it is bad news. I've only had the phone 10 days. Think tmo would exchange it?
Click to expand...
Click to collapse
Ya you shouldn't have a prob
Yeah, they should give you a brand new in the box, depending on which state you're in, you have either 14 days or 30 to return the phone
Sent from my HTC Glacier using XDA App
I'm stuck as well.
Don't know WTF happened. Was running Iced Glacier for a couple of months, then decided to try one of the new ROMs, so took CM7 for a spin, then went to RoyalGinger for a day or two. Things were working, but RG started freezing up, etc. so tried going back to CM7. Once I started through the flash process I hit an error when trying to format /system.
Now when I even attempt a wipe (or most anything) via CWM I continuously get errors like:
E:\Can't mount /cache/recovery/log
E:\Can't open /cache/recovery/log
E:\Can't mount /cache/recovery/last_log
E:\Can't open /cache/recovery/last_log
...and this latest time, I now got this as well:
E:\Can't mount /cache/recovery/command
I had CWM 3.0.2.4 through all of this, so should be able to flash 2.2 and 2.3 ROMs, as I understand. I can only get into CWMR and HBOOT.
I used gfree to root & have engineering HBOOT (.85.2007).
I can't get device listed in ADB, but can under fastboot. Tried flash command using fastboot to try and re-flash CWM (no idea if it would do any good), but it says cannot open the .img file.
The ONLY thing I got to work was mounting SD to USB in CWM and putting PD15IMG.zip in the root of the SD card, then rebooting and letting it run an auto update as it looks for this by default. That worked and took me back to stock...nothing else I tried would work.
Now I'm afraid of doing anything else or risk creating an expensive @ss paperweight.
Any help or suggestions appreciated as to HOW this happened, and next steps.
So I went to install adrylnaline's rom and somewhere along the way my wife continuum went hay wire. During the wipe stage it froze for 15 min so I had to do a battery pull. After that I got sd card error after sd card error. After a lot of troubleshooting I got those to go away, and thought I had it fixed. I now was back in cwm with no errors, and able to do full wipes. So i went for a restore, it said it took, had a sigh of relief, and phone rebooted straight to recovery. I tried this numerous times and each time straight to recovery. Now one error I had involved the cache recovery log. Now I don't know exactly what it does but I thought maybe I lost my recoveries, so I decided to try installing the ROM again, and once again nothing. Now My current theory is I lost root, and even though Im in CWM I shouldnt be. I'm currently trying the odin recovery stock file to see what happens, but if this doesn't work if anyone has any ideas Im game.
edit 2:27 am est, i still have the softkey menu restore, and even though it is saying restore are taking it still isnt what is gone on....
2:37 new error message, but maybe why the restores arent taking. E: can't mount /dev/block/mmcblk0p3 (no such file or director) E:install_application_for_customer: can't mout hiddensdcard:
your storage not prepared yet, please use ui menu for format and reboot actions
Someone else had a problem like this that I helped... I have a half day today, and its my last day of school
So I'll help you when I get home, unless anyone else wants to explain what I make you do when your phones broke to him?
Sent from my SCH-I400 using XDA Premium App
anything would be appreciated at this point I tried everything
solved
Okay, I've searched and searched and no one seems to have the specific problem that I'm having with my phone, so I'm taking to the forums myself. I've been rooting since the G1, I know how to adb push things, I have used google and multiple forums to try to fix this problem. So here goes, anyone that can help I thank you in advance.
1-My phone, like some other MT4G users, reboots itself each time it's plugged in. Initially I thought this was because I was using a Kindle cord to plug it into the pc, so I bought an MT4G usb cable from tmobile, and still it boot loops (just the first white screen for maybe 4 seconds, then black then again and again). The only way to charge it is to let it start boot looping, take the battery out, turn it on, and if I'm lucky enough that it begins to boot up correctly I plug it in mid boot. If I wait til it's fulled loaded it just starts rebooting again.
2-It will not at all from any angle go into Recovery mode. If I try to go to recovery from Rom Manager, or from the screen you get when holding power and lower volume key or by flashing a rom through Rom Manager, it just boot loops just like mentioned above, until I pull the battery for a while (it is currently sitting next to me with the battery out) and then put it back in.
3-If by chance it's on, and plugged into the computer, it is not at all recognized. Ever. While it's booting up my computer finds something, but doesn't know what it is, and doesn't allow me to view any folders on the SD card. Yes I've installed the HTC drivers file. I've adb'ed things to this phone before, now it says device not found. I don't know when it stopped being recognized...
4-I've even tried to fastboot something over to it, but to no avail, still not found.
If I try to do a factory reset, it boot loops. If I sneeze it boot loops.... I don't know what to do, and if I trade it in under warranty, I have to reset it to stock rom, or they're going to charge me for a new phone. Any ideas!?
I have Cyanogen mod 7 on here.
have you tried a fastboot wipe? or have you tried to reboot to recovery from adb?
First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Edit: I didn't realize you tried to enter recovery, oops. But yeah try what the buy above me said. Try re-installing the latest CWM recovery, if that still fails then try heading into there via ADB.
mackster248 said:
First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Click to expand...
Click to collapse
I second that, flashing ROMs from ROM Manager a terrible idea.
Well...if all else fails and if you are really thinking about returning it and still under warranty...few seconds in the microwave method should work just fine. They wont be able to see that its rooted if the phone wouldn't turn on, would they???
glimmer of hope...
So by the grace of god I did get it flashed back to unrooted, stock 2.2 by putting it as pd15img.zip on my sd card and going into bootloader. Once that was done I thought I would be out of the woods... I even plugged it in last night and no boot loop!! but this morning I unpllugged it (and I'm using a tmobile cable for the phone attached to my pc) and here it sits, next to me again with the battery out of it because everytime I try to turn it on (for over 40 minutes now) it boot loops to that stupid white screen (that is honestly driving me insane at this point). I know that it isn't rooted (because I dl'ed rom manager and it won't let me do anything without being rooted) so do we think that I'm safe to go to the store today to request a new one be sent? Thoughts? And thanks for the help thus far!
yeah I would send that back
Bad emmc chip? I'm sorry man, that's a terrible story.
Sent from my HTC Glacier using XDA App
Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
wow, it seems like all the old school glacier users are having bad luck... Glad mine is still going strong though! Sorry to hear it though, you have been a great help to many of us and will be missed bro!
Sent from my HTC Glacier using xda premium
irrelephant said:
wow, it seems like all the old school glacier users are having bad luck... Glad mine is still going strong though! Sorry to hear it though, you have been a great help to many of us and will be missed bro!
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I'm on my 3rd one going strong :/ with bad screen and chip but I call every once in awhile to see if I can get a mt4gs. Good luck teejay! As for none booting just run pd15img and do a battery pull while it's updating until it won't turn on anymore
Sent from my HTC Glacier using xda premium
This is one of the reasons I had to jump ship on this phone. Was scared it might take a **** on any given time.
But I always love the MT4G, hopefully TJ can get something viable from TMO.
TeeJay3800 said:
Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
Click to expand...
Click to collapse
that doesn't really look like failed eMMC yet... and you can't really tell until you flash PD15IMG.zip in bootloader. but yeah, if the phone can still boot, i think it's just that your recovery is messin' with ya
how about reflashing the recovery image and see if those errors are still there?
saranhai said:
that doesn't really look like failed eMMC yet... and you can't really tell until you flash PD15IMG.zip in bootloader. but yeah, if the phone can still boot, i think it's just that your recovery is messin' with ya
how about reflashing the recovery image and see if those errors are still there?
Click to expand...
Click to collapse
You think re-flashing the recovery will eliminate the errors? I could be wrong, but it seems to me that even if that works, the errors could still reappear at any time. My gut says there is an actual hardware problem, and that measures like recovery flashing would only be a temporary fix. Worth a shot though.
TeeJay3800 said:
You think re-flashing the recovery will eliminate the errors? I could be wrong, but it seems to me that even if that works, the errors could still reappear at any time. My gut says there is an actual hardware problem, and that measures like recovery flashing would only be a temporary fix. Worth a shot though.
Click to expand...
Click to collapse
yeah, worth a shot lol
but well, like i said before, unless you try the PD15IMG file and it gives you Fail-PUs, you don't know if it's dead eMMC. but if your phone still works, then i doubt the chip died...
Your eMMC most likely isn't dead or anywhere near. Cache errors in recovery can be a lot of things, usually partition corruption.
If you have engineering bootloader, try "fastboot erase cache" and "fastboot flash recovery". If that doesn't help - flash PASSIMG and re-root (after you backed up the ROM, of course).
I heard awhile back that there was a way to enter some commands through terminal emulator to the hboot partition that will brick the phone. dont know which partition it is though.
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
my2sense said:
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
Click to expand...
Click to collapse
Had the exact same thing happen to me yesterday.
Mine went belly-up recently too. No Failed-PU message but it would not flash or boot properly. Powered it on and got a 7 to 8 vibrates in a row on the splash screen before it powered itself off. Recovery (4EXT) failed to restore a nandroid (couldn't mount data) and shortly thereafter couldn't boot recovery. Flashing recovery (and original splash) through ADB fastboot claimed to be successful but didn't actually work. Flashing PD15IMG from bootloader also failed, shortly into it. T-Mobile sent a warranty replacement MT4G (it was just under 1 year). Bad screen and eMMC, but I'll live with it. Will find out if they notice the engineering bootloader and custom splash...
Jack_R1 said:
Your eMMC most likely isn't dead or anywhere near. Cache errors in recovery can be a lot of things, usually partition corruption.
If you have engineering bootloader, try "fastboot erase cache" and "fastboot flash recovery". If that doesn't help - flash PASSIMG and re-root (after you backed up the ROM, of course).
Click to expand...
Click to collapse
my2sense said:
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
Click to expand...
Click to collapse
Well, this is a little embarrassing, but it seems that a simple cache wipe fixed the problem. I was hesitant doing that initially thinking that would aggravate the problem and make the phone unusable. The question now is what caused it. Last week I flashed the newest radio. I knew that in some cases a cache wipe was necessary after flashing a radio to prevent freezing at the slash screen, but my phone booted normally after the radio flash and worked fine for days after. This is the first case I've heard of where I radio flash caused cache errors in recovery. In any case, it all seems fine now so thanks all for the kind words and input.
If you've flashed radio from recovery - the script that didn't properly unmount the /cache partition after flashing and before reboot might have been the reason for corruption, or some well-hidden bugs in the CWM itself.
Anyway, glad that your phone is working. It's better to panic and be relieved, than not to panic but get things screwed
Jack_R1 said:
If you've flashed radio from recovery - the script that didn't properly unmount the /cache partition after flashing and before reboot might have been the reason for corruption, or some well-hidden bugs in the CWM itself.
Anyway, glad that your phone is working. It's better to panic and be relieved, than not to panic but get things screwed
Click to expand...
Click to collapse
I only flash radios via fastboot commands from the computer, but I think you're right about something not unmounting or a CWM bug. There were something like half a dozen CWM bug-fix releases after the original version 5, so it wouldn't be too surprising. And yeah your last statement is exactly correct!
TeeJay3800 said:
Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
Click to expand...
Click to collapse
Sorry to hear that, if you was to give an estimate, how many roms have you flashed before this happened, also tmobile still ships mt4g, i just ordered a replacement for my girlfriend last week thursday and she received a new phone next day.. she had the bad emmc(Embedded Multi-Media Card) chip, i ran the code with terminal emulator and she's not rooted, she's on stock rom..her problem was the buttonS was not responding..after she received the new phone, it still had the bad chip(she don't care as long as the darn phone works).. so you just might get a good or bad one either way i believe they still ship the mt4g.
jr_718 said:
Sorry to hear that, if you was to give an estimate, how many roms have you flashed before this happened, also tmobile still ships mt4g, i just ordered a replacement for my girlfriend last week thursday and she received a new phone next day.. she had the bad emmc(Embedded Multi-Media Card) chip, i ran the code with terminal emulator and she's not rooted, she's on stock rom..her problem was the buttonS was not responding..after she received the new phone, it still had the bad chip(she don't care as long as the darn phone works).. so you just might get a good or bad one either way i believe they still ship the mt4g.
Click to expand...
Click to collapse
Thanks, but did you read the rest of the thread? No replacement for me, at least not yet.
TeeJay3800 said:
Well, this is a little embarrassing, but it seems that a simple cache wipe fixed the problem.
Click to expand...
Click to collapse
Awesome. Glad it worked for you too. I never had to clear cache after radio flash before either except for the latest radio. Freaked me out too when I first saw it too
my2sense said:
Awesome. Glad it worked for you too. I never had to clear cache after radio flash before either except for the latest radio. Freaked me out too when I first saw it too
Click to expand...
Click to collapse
I hadn't had to either. There's definitely something different about this latest radio.
Well, I loved this kernel! But I appear to have bricked when flashing another (also aparrently kernel fixed) rom.
I *could* get to CWM, but I can't touch system. The phone freezes if I try to do anything.
Odin will not flash.
I'm an experienced user, I've owned several Android phones in the past and understand how everything works, however, this time, it really appears I am dead.
I can take the phone back so no big deal, but I just wanted to let people know. If I am unable to get this working, it appears the new kernels still have some risk involved.
I was on UK Stock ICS (Not sure what the version was now), flashed Francos using DD, everything was fine but Wifi did not work, so I wanted to try Speedmod. This caused a bootloop. So I reverted, and the bootloop remained. At this point I downloaded a Lite rom that used Franco V4, (sorry, the name has escaped me) this flashed but also gave a bootloop. So I wiped, and re-applied.
When I reinstalled after wiping, the install bar glitched and flew past it's usual 100% right off the side of the screen. Then it froze.
After this I am unable to flash *anything* to the phone. CWM boots but I can't do anything within it. Odin attempts to flash but I see the phone send invalid responses back (non-alphabetical characters) and Odin then fails.
Anything else I could do? I think I've tried everything possible at this point. Gutted!
[edit]
UPDATE: This does currently appear to be a case of bad luck, and NOT The eMMC Bug. The eMMC Bug fix is now under critical testing by myself (as I have access to replacement phones within minutes), though I have flashed 18 times at present with no superbricks or broken eMMCs. So far so good!
I think u wiped from ICS kernel and this may have caused u a brick. At first when you flashed speedmod and had bootloop you could have flashed back to Abyss kernel wiped and reinstalled the whole rom instead of wiping from ICS kernel and installing rom. Its a known fact that while installing or restoring roms from ICS kernels people have faced lot of issues..
I'm aware of that issue. I used Franco's R5 kernel (which is ICS and superbug fixed. The fix was not a guaranteed fix, and sadly I appear to have proven this fix to be non-working at the moment.)
I guess I'll be popping back to the shop at lunchtime!
Cheers.
One last try just pull the battery for 30 seconds and try to get into download mode and try to flash stock GB with 16gb pit file and gb bootloaders
---------- Post added at 12:58 PM ---------- Previous post was at 12:56 PM ----------
When i had Galaxy s same thing happened to me only download mode no cwm nothing and Odin was failing to flash stock roms even with a pit file and what i did was flash with bootloaders along with pit file and rom files and voila my phone was back to bussiness
You might be right about the PIT files. It would make sense, Odin almost completes when the phone throws out the invalid text- might be trying to put data out of the partition.
I'll give it a go, thanks. I do still have Download mode. I no longer can access recovery though.
so you cant flash on ODIN?? stuck on factoryimg??
Well, that didn't go to plan. Crashed again, and now I have no download mode, instead the phone appears to be insisting that the battery is not installed. How odd!
musashiro said:
so you cant flash on ODIN?? stuck on factoryimg??
Click to expand...
Click to collapse
This was the case, yes.
Oh, I just got Download mode back, Stupid thing. What odd behavior.
I can get the phone replaced within minutes if required (I'm 5 mins away from the shop) but I'd rather try to keep my internal storage intact
Here's the guide to fix it. I along with many others managed to fix our phones using this guide: http://www.android.gs/easily-fix-bricked-samsung-galaxy-note-n7000/
Thanks for that. I'd just found it before you posted and am reading through it now.
I am half tempted to try it, but I think if there are now "bad blocks" in internal memory, I will just get it swapped for a fresh device.
It's behaving weird, sporadically thinking the battery was removed etc. so I am not 100% sure this is a superbrick /mmc problem, and it could be some other issue that cropped up. Let's hope so (because I'd really like to think Superbrick is fixed as we had suspected!)
Thanks for your input. I'm off down the shops!
Eyup! New phone in hand.
So I have 13 days in which to take advantage of this quick-swap. What I'm going to do now is begin heavy flashing with the R5 "fixed" kernel. If I succeed in breaking it, we know the fix isn't working. If I fail at breaking it, we're all good. Sound like a plan?
damiensturdy said:
Eyup! New phone in hand.
So I have 13 days in which to take advantage of this quick-swap. What I'm going to do now is begin heavy flashing with the R5 "fixed" kernel. If I succeed in breaking it, we know the fix isn't working. If I fail at breaking it, we're all good. Sound like a plan?
Click to expand...
Click to collapse
Yes seems like a good plan to me, looking forward to get results from you soon.
Thanks
Right, OK, I managed to duplicate the crash, but instead of using ODIN which failed the first time round and caused very, very weird behavior, I installed THOR'S CWM. This was able to unmount, format, etc the system partition. This means that despite the other errors, there was no EMMC damage
(I'm aware the damage is not always the same, but I was able to consistently cause the crash with no damage.)
After installing Thor, I was able to reinstall other roms
IMPORTANT!!!
When I tried to install Thor's CWM, It froze - I gave up hope here, but after forcing a reboot the phone had Thor's CWM anyway, so it'd written the important parts over before crashing
Hope this helps. If you find yourself with a recovery unable to flash roms, try flashing Thor's CWM, it may freeze, but give it a minute then pull the battery and re-enter recovery. Fingers crossed
Glad to have someone willing to risk their devices in these dark times. Well appreciated!
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
In order to run the test, you need to actually boot up the device, go through the settings, and install a few apps. Then go to recovery, and perform a wipe.
Simply hitting the Wipe key in succession (like 100 times) does not work. There must be something to format in the respective partitions.
Thank you for doing what you're doing. But if you could, and only if you have the time, could you try wiping from CWM (just wiping, not nandroid restore), for say 20 ~ 30 times? It's very tedious to do it due to the setting up and needing to wait for it to boot and install a few apps from the market.
I'm sure with 20 ~ 30 or more wipes on a single device, we can safely say that the fix is a likely permanent fix.
damiensturdy said:
Right, OK, I managed to duplicate the crash, but instead of using ODIN which failed the first time round and caused very, very weird behavior, I installed THOR'S CWM. This was able to unmount, format, etc the system partition. This means that despite the other errors, there was no EMMC damage
(I'm aware the damage is not always the same, but I was able to consistently cause the crash with no damage.)
After installing Thor, I was able to reinstall other roms
IMPORTANT!!!
When I tried to install Thor's CWM, It froze - I gave up hope here, but after forcing a reboot the phone had Thor's CWM anyway, so it'd written the important parts over before crashing
Hope this helps. If you find yourself with a recovery unable to flash roms, try flashing Thor's CWM, it may freeze, but give it a minute then pull the battery and re-enter recovery. Fingers crossed
Click to expand...
Click to collapse
So, in short, you had /system corrupted at the filesystem level, not the eMMC level. This seems to be a common problem on the Note, and some people falsely describe it as "partial root". CM9's initramfs has had changes made to make it easier to fix these problems by not automatically mounting /system on entry into recovery.
The problem was: If /system was corrupted due to plain-jane filesystem corruption, it would be mounted read-only if mounted at any time. Also, it seems that CWM would be unable to unmount it, preventing CWM from reformatting it.
Solution (which I haven't fully tested as I haven't had this issue in a few weeks, but I have encountered it before) is not to mount /system automatically on boot when entering recovery.
I pointed Franco to the fix for this but I'm not sure if he's included it yet.
Note that this is NOT the eMMC brick bug, it's completely different and is recoverable.
Alternate recovery method:
In CWM, connect via ADB, and in an ADB shell:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=1M count=1
Clobbers the first 1M of system so CWM will completely fail to mount it instead of treating it as corrupt. At this point it can be formatted in CWM's Mounts and Storage menu.
Good input guys. Thanks.
Yes, indeed this didn't appear to be the eMMC Bug. I can't guarantee what it was on the old phone (which did appear bricked.), I just know I started off the same. It's more likely that I knackered it with failed Odin flashes than the eMMC bug at this time.
I'm still flashing, installing, wiping, etc. I'm basically trying everything that we're not supposed to do. So far the worst I've got is a corrupt system partition (indeed, that is not an eMMC bug) but the only CWM able to fix that was Thors.
Basically if I knacker the phone I can get it replaced within minutes, so I might as well take advantage so that we can all relax knowing it's fixed (or continue to look for a fix if it isn't)
Obviously I shouldn't take the piss. If somehow I brick it a couple more times I'll be forced to stop. But I like to help so let's go! :-D
What does "flashed Franco from DD" mean? After that process did you ever verify that you where actually on Franco?
Perhaps the kernel flash didn't take and your subsequent wipes/flashes where from stock ICS kernel.
Sent from my GT-N7000 using xda premium
Entropy512 said:
The problem was: If /system was corrupted due to plain-jane filesystem corruption, it would be mounted read-only if mounted at any time. Also, it seems that CWM would be unable to unmount it, preventing CWM from reformatting it.
Solution (which I haven't fully tested as I haven't had this issue in a few weeks, but I have encountered it before) is not to mount /system automatically on boot when entering recovery.
I pointed Franco to the fix for this but I'm not sure if he's included it yet.
Note that this is NOT the eMMC brick bug, it's completely different and is recoverable.
Alternate recovery method:
In CWM, connect via ADB, and in an ADB shell:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=1M count=1
Clobbers the first 1M of system so CWM will completely fail to mount it instead of treating it as corrupt. At this point it can be formatted in CWM's Mounts and Storage menu.
Click to expand...
Click to collapse
VERY Useful information. Just got myself back into this situation and this did fix it without Thors CWM, although I recommend everyone have a copy of Thor's CWM on their card just in case!
Actually I notice that Thor does NOT Mount System by default, this seems to match your information.
Nice one, Thanks!
damiensturdy said:
VERY Useful information. Just got myself back into this situation and this did fix it without Thors CWM, although I recommend everyone have a copy of Thor's CWM on their card just in case!
Actually I notice that Thor does NOT Mount System by default, this seems to match your information.
Nice one, Thanks!
Click to expand...
Click to collapse
That's because he kangs from CM and then releases warez based on our work.
Linux kernel without source code published = warez.