Hello
I have nFlashed my devices twice, after each I just recirculate the TapNTap animation. I know I need to wipe data as that as worked in the past, but I can get get into CWM to do that. Im pretty sure I have CWM extracted on my internal card, but when I boot and press Vol+ I get the android screen, then a Big yield sign with an ! in the middle, then the device reboots itself.
What am I doing wrong? I also have cwmod in the external card but I do not think that card is being looked at upon boot. Any help is appreciated.
Thanks,
RalphTrent
I removed the update/recovery on the external card and re-extracted CWM onto the external card and I was able to get into CWM.
That was crazy
1. Wrong section...this is not development
2. This question has been asked and answered at least 200 times
3. Try searching before posting
http://forum.xda-developers.com/showthread.php?t=892090
Sorry, I thought this would be development and not general. I guess that is my why searches did not show anything. Also, as noted, i did resolve it my self. I could have probably deleted the entry, but I figured I would leave it out in case someone else comes into this thread looking for a similar issue.
Related
Hello people. I have a 32 GB Wi-Fi only Tab, running seraphimserapis' CM9 preview kang.
I'll dive right into things here. Earlier today, I flashed the above ROM, everything went perfectly, booted up just fine, and got all my apps back up and running. I was using my tab fine for the entire day with no problems to speak of. Later in the day, I began transferring some misc. files (documents, music, etc) to my internal SD card via MTP USB transfer. After the transfer was complete, I unplugged my tab, and went on my merry way. The next time I booted up, everything began FCing on me, and nearly every app I tried to open immediately FCed. Thinking it was a temporary bug, I rebooted my tab, but the same problem persisted, multiple different processes fced upon boot, and almost all my apps would fc as soon as I opened them. After trying a few more times, I gave up, and booted back into CWM (which I can do perfectly fine), cleared cahce and delvik cache, and did a factory reset. This however,seemed to only augment the problem. Upon booting up (after doing that initial tab setup), trebuchet FCes (in a "FC loop", as it continually tries to open), and the tablet is completely unusable. I have tried wiping cache, reformatting and rebooting several times, each time with the same result
I am able to get into settings however, by plugging in the tab, and clicking USB debugging (for whatever reason, settings does not FC), and am able to connect to my internal memory via MTP. When the tab pops up in my computer, it says I have 25 GB out of 28 available GB, but when I click on the folder, it is completely empty. If i try to move files over to my tab, or even create a new folder, I get an error message saying "the device has stopped responding or has been removed". (Pictures below)
http://img141.imageshack.us/img141/9855/75464072.jpg
http://img190.imageshack.us/img190/3395/61277691.jpg
I do not believe this is a problem with the rom for two reasons. (1) no one else has had this problem (to my knowledge), and (2) it was working fine the whole day, until i did that file transfer (that being said, this is my own amateur opinion, which you may choose to completely disregard it in your diagnosis). I am 99% sure I didn't unplug the tab while files were still transferring, but I did not unmount the storage or eject it or anything fancy of that nature before I unplugged it.
My question is, is there any way I can somehow reformat the internal memory of my tab? Otherwise, is there some other possible fix you experts may possibly have? Or am I screwed?
I apologize in advance if you ask me to try something and I cant respond promptly. Its 3AM here and i need to wake up early tomorrow. Thank you in advance
Edit:
I am quite convinced there is some kind of internal memory corruption problem here, but I really am not an expert enough to know for certain. The tablet still boots up fine, but is completely unusable as trebuchet fc loops 90% of the time i reboot the tab. Obviously, the entire thing isnt trashed as it appears to boot and get into the system fine, but I it's still completely unusable from that point on.
I have tried formatting the /data and /cache partitions of the internal memory to no avail. I would try formatting /system, but from my understanding, thats only advisable if you are able to flash a new rom after formatting, but if i cannot write into my internal memory, then there's no way i can flash a new rom. Conveniently enough, I deleted the .zip file for the rom off my internal sd, and i cannot access my clockworkmod recovery from CWM (gives an error, I don't think that would have worked anyway) since the internal sd is (i believe) corrupted. I also tried mounting as USB from CWM, and that also gives an error...
I am clean out of ideas. I'm not sure if this is a completely unfixable problem, or if self repairing is well within the realm of possibility. If someone can shed some light on me that would REALLY be appreciated. Otherwise i might have to send it back to sammy (still under warranty), which i dont mind doing, but if they boot it to find an ICS rom, they probably wont be so keen to repair it...perhaps there's a way to brick it further so they can't tell?
UPDATE 2:
Problem fixed! I still don't have a clue as to what the problem was, but thankfully I managed to escape out of this one. I tried pushing a new ROM via adb, and it worked (apparently), but this just forced me into a boot loop (never hit the homescreen).
As a last ditch effort I pushed the stock ROM, and completely removed root, and it worked. I can now boot up past the spash screen without all all my processes crashing. Really a strange issue, I have my theories, but they're probably blatanly wrong so I'll just keep them to myself. Im just glad I don't have to send it back to sammy... I plan to re-root shortly. I am confident I will get no further issues.
Even though no one helped me directly, it was thanks to the plethora of information available on this forum that I was able to resolve my issue...and for some reason, making a thread where I'm just talking to myself helps a bit too...maybe im just weird. Anyway if anyone's reading this, thanks again xda
.......HOW??
brennanyama said:
UPDATE 2:
Problem fixed! I still don't have a clue as to what the problem was, but thankfully I managed to escape out of this one. I tried pushing a new ROM via adb, and it worked (apparently), but this just forced me into a boot loop (never hit the homescreen).
As a last ditch effort I pushed the stock ROM, and completely removed root, and it worked. I can now boot up past the spash screen without all all my processes crashing. Really a strange issue, I have my theories, but they're probably blatanly wrong so I'll just keep them to myself. Im just glad I don't have to send it back to sammy... I plan to re-root shortly. I am confident I will get no further issues.
Even though no one helped me directly, it was thanks to the plethora of information available on this forum that I was able to resolve my issue...and for some reason, making a thread where I'm just talking to myself helps a bit too...maybe im just weird. Anyway if anyone's reading this, thanks again xda
Click to expand...
Click to collapse
I'm hoping you see this reply as its been quite a while since you've had the issue. I'm working with a Galaxy S2 Skyrocket with the same intenal memory corruption/ files system corruption you were facing. I followed what you did regarding push a rom thru adb and that worked for me, but my question is, how did you get the roms to successfully write if you couldnt write to internal memory? My system is mounted as read only apparently and locked itself with whatever I had on there on August 28th. No matter how many times I format, erase, or wipe it, it returns to the same state as if its a deep lock on it.
i installed it internal. Right after installation and SetUp i did a Reboot. And now my Nook is shut down and i cannot turn it on again. Tried Power Button once and Hold and Power+N-Button.
HELP Please
Did you format your sd card within Cm7? That seems to trigger a bug that completely bricks the device. Just happened to me, it's been discussed over in the development forum. Sucks but if you're like myself and several others, it's basically a 250$ paperweight now.
Keep watching, I wouldn't be surprised to see a fix at some point.
And shortly thereafter ...
Don't give up yet, there's hope on the horizon.
I found something that may be of use to you in the development forum. Also as a side note to other people, do your best to stay away from the SD card install of CM7! It's apparently extremely risky right now and pretty likely to brick Nooks. Go for an internal installation if you can.
Click here for the "Fix for bricked nooks from CM7" thread.
Mike_IronFist said:
I found something that may be of use to you in the development forum. Also as a side note to other people, do your best to stay away from the SD card install of CM7! It's apparently extremely risky right now and pretty likely to brick Nooks. Go for an internal installation if you can.
Click here for the "Fix for bricked nooks from CM7" thread.
Click to expand...
Click to collapse
Got mine fixed thankfully. Definitely a scary hour or two there.
Mine was an internal install, and the brick was caused by trying to format the sd card through CM7, which apparently formats some other vital partition instead....they've taken down the links to download CM7 for now.
Yeah, they don't want anyone else to stumble across the install files and end up bricking their Nooks. I'm impressed at how fast they've been moving though, so I won't be surprised if they have a fixed version up within the next week, or even earlier. These dudes are incredibly industrious and they really seem to love hacking.
Haha, now I have it back up and running, back to the 1.4.1 + root zip mod that's floating around the dev forum....and it reboots every time i start downloading something, anything so far, from the market. *sigh.* gonna try fixing permissions, and then possibly wipe and re-apply the mod with cwm....
porthos75 said:
Did you format your sd card within Cm7? That seems to trigger a bug that completely bricks the device. Just happened to me, it's been discussed over in the development forum. Sucks but if you're like myself and several others, it's basically a 250$ paperweight now.
Click to expand...
Click to collapse
I have entered the CM7, his operation was a success, but in the exit, I chose to restart, so, I wouldn't start NT. Now, press the power button have no reaction, and the screen is black.Can you tell me the recovery of the specific steps.Thank you can reply to me.
Does anyone have the internal zip the can email me. Please
Sent from my PG86100 using xda premium
Tony Brown said:
I have entered the CM7, his operation was a success, but in the exit, I chose to restart, so, I wouldn't start NT. Now, press the power button have no reaction, and the screen is black.Can you tell me the recovery of the specific steps.Thank you can reply to me.
Click to expand...
Click to collapse
Well, if you're having the same problem that many of us others are having, follow the link in Mike_Ironfist's post a few posts back from here. If you follow that link, it will walk you through creating a CWM SD card that you should be able to boot with, and then further fixes follow in that linked post.
Other than that, I'm not sure. It worked for me and got me unbricked but now I'm stumbling with other problems sadly.
porthos75 said:
Well, if you're having the same problem that many of us others are having, follow the link in Mike_Ironfist's post a few posts back from here. If you follow that link, it will walk you through creating a CWM SD card that you should be able to boot with, and then further fixes follow in that linked post.
Other than that, I'm not sure. It worked for me and got me unbricked but now I'm stumbling with other problems sadly.
Click to expand...
Click to collapse
Thank you very much, I am recovered ~ ~ thank you ~
16gb Nook Tablet. Internal NookOS has never been messed with. I've been running CM7 from the SD card. The CM7 crashes a lot because of my SD card and apparently that's messed up the NookOS and now I can't boot back into the internal. I've tried the step-by-step Unbrick from the thread here and that didn't work. It keeps going back to "Please Restart Your Device...".
Any ideas?
I am of no help but can offer one thing
hey I am having a similar problem, mine nt stopped working (spontaneously started trying to factory restore and failing over and over) then I booted off sd, cm7 for a while.
http://forum.xda-developers.com/showthread.php?t=1743884
You might want to keep an eye on the topic I posted today as well see if anyone has some help
Thanks. I thought about piggybacking on your thread, but then I decided against it. We are having similar problems. I guess we should keep an eye on each others threads.
mattc8210 said:
16gb Nook Tablet. Internal NookOS has never been messed with. I've been running CM7 from the SD card. The CM7 crashes a lot because of my SD card and apparently that's messed up the NookOS and now I can't boot back into the internal. I've tried the step-by-step Unbrick from the thread here and that didn't work. It keeps going back to "Please Restart Your Device...".
Any ideas?
Click to expand...
Click to collapse
Please tell us what you tried. .
I would recommend a CWM Recovery placed onto a ( good ) spare SD Card and boot it up ( from an 'off' condition ) by plugging in the power to the usb port.http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14
.
or how about a "a clockwork mod backup of stock rooted" ?
http://forum.xda-developers.com/showthread.php?t=1495869
.
And thoroughly read and ask questions. The worst thing to do is NOT ask a question.
Thanks for replying. This is what I tried...
http://forum.xda-developers.com/showthread.php?t=1663836
mattc8210 said:
Thanks for replying. This is what I tried...
http://forum.xda-developers.com/showthread.php?t=1663836
Click to expand...
Click to collapse
ah, and did you read this thread ?
http://forum.xda-developers.com/showthread.php?t=1610682
it was at the top of a google search.
I did check that out. Since it involved having rooted the internal and using CWM I kinda figured it might not apply to my situation.
I'm going to try the Ubuntu method. I'm downloading the image now. I didn't realize it's over a gig! Gonna take a few hours.
Any alternate links? This one is slow as heck.
I have read several times that the 'Ubuntu Method' does not work if you got bad ( goofed up ) partitions.
old_fart said:
I have read several times that the 'Ubuntu Method' does not work if you got bad ( goofed up ) partitions.
Click to expand...
Click to collapse
Isn't that the method you recommended before? Any other advice?
Edit: I suppose you didn't recommend it, you just pointed me at that thread. Not trying to insinuate you gave me bad advice.
I am trying to upgrade from CM7 to CM10 using this guide: http://forum.xda-developers.com/showthread.php?p=35669871#post35669871
Got everything in place, get into recovery, start the backup, and that's as far as I can get because the backup hangs. If I use CWM, it gets to a point where it says "Baseline.par" and hangs, if I use TWRP it gets system backed up, gets to "Generating MD5 system.ext4.win" and hangs. I tried with an 2gb card & an 16gb card. Same results. I've let it sit for a good 45 minutes and nothing.
Not sure if this matters with it, but after I re-booted I forgot to swap out the cards & still had the one with all the files on it in the nook. The nook was not plugged in to USB. As it came back up, it gave a message that I had a "bad boot file (in memory)". Is this because I didn't have the USB cord attached? I've never gotten that message before.
I posted all this in the thread itself, so I apologize for a bit of a double post but I'm hoping someone might notice the problem if it's in it's own thread & I don't really think it has to do with loading CM10, anyway.
Suggestions? Thanks!
rsdown said:
I am trying to upgrade from CM7 to CM10 using this guide: http://forum.xda-developers.com/showthread.php?p=35669871#post35669871
Got everything in place, get into recovery, start the backup, and that's as far as I can get because the backup hangs. If I use CWM, it gets to a point where it says "Baseline.par" and hangs, if I use TWRP it gets system backed up, gets to "Generating MD5 system.ext4.win" and hangs. I tried with an 2gb card & an 16gb card. Same results. I've let it sit for a good 45 minutes and nothing.
Not sure if this matters with it, but after I re-booted I forgot to swap out the cards & still had the one with all the files on it in the nook. The nook was not plugged in to USB. As it came back up, it gave a message that I had a "bad boot file (in memory)". Is this because I didn't have the USB cord attached? I've never gotten that message before.
I posted all this in the thread itself, so I apologize for a bit of a double post but I'm hoping someone might notice the problem if it's in it's own thread & I don't really think it has to do with loading CM10, anyway.
Suggestions? Thanks!
Click to expand...
Click to collapse
Use Titanium Backup to backup all your files. Or manually save them all on your computer then put them in the right spots when you update.
Hi there
I followed an online tutorial a while ago to put android 2.1 (could have been 2.3) on my htc hd2.
I loaded on the magloader and pushed on the android software and it worked lovely.
Then a week ago the phone decided to freeze and I couldn't unlock the screen. A few minutes before it locked it had unlocked a little sluggishly and then wouldn't unlock at all.
I re-started and tried a soft and a hard reset to no avail.
I can still load into the magloader and so had a go this weekend loading on clockwork recovery. Downloaded a newer version of android and put it on the sd card. I managed to get it to install from the zip on the sd card, but it won't launch into android, it just loads the magloader.
My pc won't find my phone so if anyone can help with a link to the right software for my winxp pc to recognise my hd2 that would be a first step as I think I need to remove the original android files from the phones internal memory.
If that's the wrong approach I would be grateful for any advice. :fingers-crossed:
I don't have the phone with me at work at the moment and I know I am a bit vague on the details, but I'm hoping someone knows their way around the magloader and clockwork to point me in the right direction. I am especially frustrated with the pc not seeing my phone. I installed the htc sync manager, but that doesn't work.
I can see the phone as a removeable drive in my disk management, but not in my computer. I can explore it from there, but it's just the sd card and not the phone itself.
If anyone could help that would be great. I don't want to give up on my hd2 yet, but I'm missing my whatsapp, etc
Thank you for looking and sorry for being so vague and so useless.
Mods: If this is in the wrong section please feel free to move it. Thanks.
All you had to do was download the .zip file for the ROM, copy it to your SD card, if you did not download the .zip with your HD2. Then boot into Clockwork Mod Recovery or whatever custom Recovery you have on your HD2. Then wipe your delvick cache, your cache, and data then flash the ROM using the recovery.
Click to expand...
Click to collapse
I've seen this by T-Macgnolia on a an upgrade thread http://forum.xda-developers.com/showthread.php?t=1618570
Is this likely to work for me? I will look at how to clear the delvick cache (whatever that is).
Please let me know if you can help.