Related
So im rooted, clockworked and nandroided. i go into rom manager and attempt to partition the sd, everything looks like it went fine. i get the samsung splash tmo bootup then it goes from the S splash screen to what seems to be a soft brick, just a blank screen and four lit up buttons. i try to boot into clockwork and i get the factory recovery mode. Clockwork is nowhere to be found. my sd card appears to be partitioned it shows a 14.8g card on a 16g, but the sd card still has everything on it, it did not get wiped. i have tried using odin, all that happens there is it runs through the motions, resets the phone back into this soft brick. anyone have similar issues or helpful ideas? i will be slowly bashing my head into the wall waiting for a reply. thanks in advance, any help will be appreciated
Same Problems Here
I came on to post and hopefully find a solution for a very similar problem. I rooted, clockworked, and nandroided my vibrant this morning and it worked fine all day. I got home and realized my phone was locked and didn't respond to the unlock button. I pulled the battery and rebooted and it all seemed fine. 5 minutes later i realized it wasn't responsive and once again pulled the battery and now won't boot past the "S" boot screen and seems to freeze. Now my clockwork restore won't backup and says it can't mount. I've tried a factory reset to no avail. Anytime I attempt a clockwork recovery I get the error
E:Can't mount /dev/block/mmcblk0p2
(file exists)
Can't mount /data/!
Any suggestions or solutions would be greatly appreciated.
I'm having the same issue, any help would be greatly appreciated.
did anyone get any help??
Same thing happened to me. I posted such on the market comment for rom manager. I ended up taking mine back to Best Buy (got another). I'm wanting to install linux on mine. Anyone been able to do that?
I hate to tell you this but you just partitioned the internal memory. If you had actually read the thread on clockwork recovery you would have seen that you cannot currently partition the external sd card with clockwork.
so what do i do??
nickerrides said:
so what do i do??
Click to expand...
Click to collapse
I honestly don't know the answer to that question. I'm kind of a casual flasher of my phones and I've never "bricked" one or had any major problem. I believe it can be fixed by using odin to flash back to stock. I'm pretty sure that you can recovery from it but it may take some work.
I would start by reading the entire clockwork recovery thread in the Android Development section. A few other people have made that mistake and may have a solution posted there. I'm at work posting from my phone or I would go look and try and find it.
Okay, I did some digging in that thread and it appears all you need to do is to use the re-partition option in Odin and then use Odin to flash a stock ROM and you should be all set.
Again, I have not used Odin myself so I don't know how easy/hard that is to do or if it will work at all.
nope i tried the repartition option in odin while flashing the stock rom.
With mine, I had success and got it out of the boot loop by using odin and flashing it back to stock.
The phone seems unbrickable, as
others have mentioned, just get it into download mode and use odin carefully.
Sent from my SGH-T959 using XDA App
wanna be more specific on what exactly you did?
Ok. Let me start by saying, I'm obviously not an expert on hacking/developing and stuff like that. I just love to tinker stuff so I learn in the process. So definitely not an expert. Just posted this thread hoping that someone whose possibly a lot more knowledgeable than I am would notice it and hopefully shed a light on this question.
Is TWRP 2.0 which can be seen here, working/compatible/available/will be available on our beloved NookColor?
All we are using right now is the ClockWorkMod Recoveries, right? Which I believe the latest is 3.2.0.1. I'm not saying at all that CWM is not sufficient enough to do whatever it needs to do, I just thought it would be awesome to be able to get your recovery things done THAT MUCH COOLER, navigating the device via the touchscreen rather than hardware buttons.
Hope this sparks more awareness!
+1 - I would like to see TWRP on our devices as well, BUT ... I would definitely miss the convenience of being able to install the nightlies directly from ROM manager.
OK, saying that, I also just had a perma-brick on my Nook and am getting a replacement due to an issue that occurred in recovery. I was stuck in the infamous CWR boot-loop, so did a restore, when I went to reboot, screen itself would never come on again - not after charge, not after holding buttons, nothing.
Is it related, I don't know, maybe not, but makes you think.
majorpay said:
+1 - I would like to see TWRP on our devices as well, BUT ... I would definitely miss the convenience of being able to install the nightlies directly from ROM manager.
OK, saying that, I also just had a perma-brick on my Nook and am getting a replacement due to an issue that occurred in recovery. I was stuck in the infamous CWR boot-loop, so did a restore, when I went to reboot, screen itself would never come on again - not after charge, not after holding buttons, nothing.
Is it related, I don't know, maybe not, but makes you think.
Click to expand...
Click to collapse
Oooh, that's too bad. And scary. Makes you worry about doing something that's not tried on the NookColor before. I wont dive in unless the devs really says that it's safe.
Hey, about your NC being bricked. I had something pretty similar happened to my NookColor before. Got stuck into a boot loop. Now before, I had my TitaniumBackup folder stored in the eMMC and I didn't want to do anything that would delete it. What I did is, I had another microSD card and created a bootable CWM. I installed a CM7 nightly on the microSD. Upon booting to the microSD build, I went and have adb wireless transfer my eMMC files to my PC. Now that I've recovered my TitaniumBackup folder, I formatted everything on my NC using the bootable CWM. Then what I did is I flashed the stock NC Rom which was 1.2 version. I did a factory reset. After that I had everything back to normal again. I flashed the nightly build on the eMMC again and from then on, had my TitaniumBackup folder on the microSD. Have you tried creating a bootable microSD?
A little late...
Did you try a formatted bootable sdcard? The nook is near indestructible. I had the same issue and recovered.
fr4nk1yn said:
Did you try a formatted bootable sdcard? The nook is near indestructible. I had the same issue and recovered.
Click to expand...
Click to collapse
Same here, I put together a nookie froyo card, and got bootloops.I took the memcard out and still got bootloops. I put a cwm card in, and STILL got bootloops. Then I made a new cwm card, and it booted just fine.
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.
i dont know if im asking for help to the right person but if you can help me tank you very much.
today i tried to restore my nook color by pressing u button and power and he goes to the factory reset asks to press u button and i press then he asks again and i press and after the yellow bar moves too fast only last about 3 seconds and it should take some minutes and after reboots. i think my factory partition in damaged.
;(
Don't get too upset. You can still boot from SD. At worst, you may have to (re)install some firmware. If you want the B&N firmware, you can reinstall B&N 1.3 and update, or stay at 1.3 if you prefer.
It's hard to totally brick a NC.
Take a look at the restoring to stock section of the guide in my sig
Sent from space
Listen to the two people above this post. They are right. It is nearly impossible to completely brick it. Trust me I've tried.:what:
Seems no matter what I do to it, short of kick boxing it, I've always been able to start from a brand new running nook. Just by reading many posts and the great help from everyone on this forum, who have usually, "been there, done that.", folks.
I'm sure this will work out and everything will be fine, but then you'll be able to help someone else too.
Sent from my GT-P7510 using Tapatalk
i just use this command "fdisk /dev/block/mmcblk0 -l"
i think it was to see the partitions and they dissapeared just chek the image ;(
I think what you are looking at there is the partitions on a booted SD card which look correct for an 8GB card.
bobtidey said:
I think what you are looking at there is the partitions on a booted SD card which look correct for an 8GB card.
Click to expand...
Click to collapse
Nope... you can see he's looking at /dev/block/mmcblk0... that is internal.
Need to find the thread about the nook color partitions and create partitions 5-8 then dd the images to them.
i already fixed ! its working again
i can´t believe,
i was thinking about doing a tutorial in how to soft unbrick your nook, i´m not an expert but is a lot of people with the same problem as mine
basically when i enter in recovery receive errors in logs and he dont let me mount or format any of mine partitions(except boot and sdcard), a lot of people are having the same issues and i was thinking about doing a tutorial in how to do it.
should i do it??
thanks everybody
More tutorials are always good. One thing to remember though, is that if someone is looking for a tutorial that means they are usually starting with a small knowledge base. You not only need to be clear, you need to be right.
All I am saying is an underinformed/incorrect tutorial is worse than no tutorial at all. The information is out there, but can be hard to find. If you know your stuff, and have a place to present it where it doesn't already exist, then sure, people will benifit from your knowledge.
Just a guess, but problems mounting within CWM tend to come from old and/or incompatible versions of Clockwork. Is that where you had your problem? I definitely wished that had been stressed on the tutorial I first followed. Would have saved me untold hours of pointless reflashing.
you are right but in my case and i think that is the same of a lot of people (who follow this tutorial http://www.youtube.com/watch?v=szlGSBtWbKY) i tried about 7 to eight diferent versions of clockworkmod and including change of sdcard, i also tried DD the images of the boot and system, when nothing of this works we start get in panic, with no necessity because its only a partition problem, i fixed my 4 partition and he started working
Yeah, I can see where you are coming from. I followed an older tutorial as well, and never saw anything to indicate the link to the CWM image might be outdated.
For sure, that info should be wider spread.
Good luck on your video (?)
hackerse7en said:
i dont know if im asking for help to the right person but if you can help me tank you very much.
today i tried to restore my nook color by pressing u button and power and he goes to the factory reset asks to press u button and i press then he asks again and i press and after the yellow bar moves too fast only last about 3 seconds and it should take some minutes and after reboots. i think my factory partition in damaged.
;(
Click to expand...
Click to collapse
I am not sure where to ask for help. I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install, I power off forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. Am I bricked my nook?? please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stacked at the cw recovery screen. Help...
Well, I first of all was using TWRP 2.0 as my recovery. However, i did not know that it was known to cause bricks. Anyway, I was doing a routine clean flash of a new rom i wanted to try, the aokp build 22 rom. I wiped everything, making sure to hit wipe system as well in twrp, then i put my phone to mount the sd card, transfered the rom, flashed it and its gapps then i reboot. Now all my phone can do is reboot endlessly, So I got into the bootloader and selected recovery, still, just keeps bootlooping. So then I decide to find an RUU and flash it through fastboot. It flashed everything correctly but when it got to step 4, (system) the phone would say error and it would fail to flash the system. After this I was still at bootloop. I dont know what it is, I even tried flashing Amon_Ra through fastboot, and ive been able to get to recovery once or twice but just to find it completely unresponsive and it wont read/mount my SD card even though i checked and the sd card was fine. All in all, I took it over to sprint and since i have TEP they agreed to get me a new one, though it was backordered so now im a week without a phone. Anyway just wanted to share my story, if anyone else knows of a way to fix it, im all yours.
TWRP kills. Good luck. Sorry you didn't follow up regularly on the thread of the product you were using. If anyone can help you, it might be Captain Throwback, but I think he's been a bit busy lately (i.e. been absent). Good luck, but TWRP fncks you.
sent from AOKP heaven
TWRP2.0 is an evo killer as far as I know there is no fix for a TWRP brick I'm pretty sure it messes up something in the partitions possibly boot or system partition which is why it bootloops
We are legion, for we are many
Unfortunately your phone is toast. Had the same problem, and really there is no way to recover. You should have bit the bullet in used insurance instead of going through Sprint since the Evo is past EOL. You maybe waiting a long time to get a replacement where as going through Ausion (sp) you either would have gotten either a new Evo, a refurb'ed Evo, or a new Evo3D (most likely).
Sent from my ICS-less Transformer TF101 using Tapatalk
Art2Fly said:
Well, I first of all was using TWRP 2.0 as my recovery. However, i did not know that it was known to cause bricks. Anyway, I was doing a routine clean flash of a new rom i wanted to try, the aokp build 22 rom. I wiped everything, making sure to hit wipe system as well in twrp, then i put my phone to mount the sd card, transfered the rom, flashed it and its gapps then i reboot. Now all my phone can do is reboot endlessly, So I got into the bootloader and selected recovery, still, just keeps bootlooping. So then I decide to find an RUU and flash it through fastboot. It flashed everything correctly but when it got to step 4, (system) the phone would say error and it would fail to flash the system. After this I was still at bootloop. I dont know what it is, I even tried flashing Amon_Ra through fastboot, and ive been able to get to recovery once or twice but just to find it completely unresponsive and it wont read/mount my SD card even though i checked and the sd card was fine. All in all, I took it over to sprint and since i have TEP they agreed to get me a new one, though it was backordered so now im a week without a phone. Anyway just wanted to share my story, if anyone else knows of a way to fix it, im all yours.
Click to expand...
Click to collapse
scottspa74 said:
TWRP kills. Good luck. Sorry you didn't follow up regularly on the thread of the product you were using. If anyone can help you, it might be Captain Throwback, but I think he's been a bit busy lately (i.e. been absent). Good luck, but TWRP fncks you.
sent from AOKP heaven
Click to expand...
Click to collapse
It's been a busy week for me, but I am still alive, and still using my previously-soft-bricked device .
I can link you to what I was able to do to get mine working (HERE), but if you can't get the device to boot up at all, you might be in dire straits. What is your HBOOT status? (version, NAND status)
hey Cap'n, you need some kind of superhero shield in your user icon
sent from AOKP heaven