***Edit as of 9:09 PM EST... We have confirmed that another "46" has rooted... Looks like my bud just has a partially broken NC, so move along....
Older info, left for posterity, incase the sky really is falling...
Please read carefully, I have tried everything. If you bought your NC within the past 3-4 weeks, please go to the last post on this thread, and create a new one with your serial number, leaving the last 4 as xxxx. We are trying to gather serial info, as I apparently have a "46", and no one else that we know of so far has anything newer than a "45"...
Ok, I've rooted about 20 of these so far. I know how to make a CWM 3.0.1.0 bootable microsd like the back of my hand. A Co-worked handed me his freshly bought NC. I noticed it was running 1.2. I turned it off. I popped the SD card in that I used to root one just this past weekend. I powered it back on, and it booted directly from emmc. I then went and made a brand new CWM SD card, using a different SD. Same behavior. Rebooted 8x, hoping that recovery would kick in. It did, but just brought me back to 1.2 again. Pondered, what would the XDA Gods do? ADB... Right, doesn't connect. Could be something on my machine, but I think it's due to USB debugging disabled, but I cant re-enable it from the sotck BN1.2 interface...
Has the end come? I dont want to yell that the sky is falling... I'll be here until 4p, and I'm willing to try anything other than breaking it open or returning it and hoping for an older 1.1x model.
Oh, and I know that the slot works, as after the boot, if I eject the sd and mount it on the pc, I see the lost.dir and other folders that android has created. (also, it can be seen on windows when I plug in the usb cable...)
You used the 1.2 Manual Nooter?
mr_fosi said:
You used the 1.2 Manual Nooter?
Click to expand...
Click to collapse
No, Step 1 of the manualnooter is booting from CWM sd. When I make the sd, and pop it in, it doesnt boot from it, it goes directly to emmc.
My bad.
So you are using 3.0.2.8 as recommended and you have tried the card you burned in another NC that you know boots from the SD?
Yep, well 3.0.1.0, but yes. I 've tried 2 cards, 1 of them I just used this past weekend to successfully root a stock 1.1.
Hrm.
I know it sounds dumb since you say that at least one of these cards worked just a few days ago, but I would create an upgraded 3.0.2.8 and try it again.
Winimage is writing now... I'll edit this post when its done, and I've updated to 3028
*edit* Yep, still no sd boot.
Interesting... Sucky, but interesting. Could it be a bum unit?
This makes me wonder things... Like why we use uSDs when B&N built in an update mechanism that only requires the update files to be placed in the USB-visible directory on the EMMC.
Sad turn of events if true. OTOH, it makes our NC's more valuable on the used market.
Dumb question, but I presume he had already registered the device? Also, maybe try a different card, it's possible that there may be something on that actual card that may cause a problem. As a last resort, return it to the store and ask for another? dunno Maybe see if the model number on the back is different? or see what serial number range it came from?
Registered status has nothing to do with the ability to boot from SD. The ability to boot from SD is set in the firmware, and apparently BN has changed it in the most recent version. I've tried 2 cards that I have used before. No dice.
computercarl said:
Registered status has nothing to do with the ability to boot from SD. The ability to boot from SD is set in the firmware, and apparently BN has changed it in the most recent version. I've tried 2 cards that I have used before. No dice.
Click to expand...
Click to collapse
Could this mean an end to an era???????
computercarl said:
Registered status has nothing to do with the ability to boot from SD. The ability to boot from SD is set in the firmware, and apparently BN has changed it in the most recent version. I've tried 2 cards that I have used before. No dice.
Click to expand...
Click to collapse
Oh noooooo.
One incident is not a pattern, it could be a fluke.
We won't know until we get more reports. I'm inclined to think that this is a faulty unit.
mr_fosi said:
One incident is not a pattern, it could be a fluke.
We won't know until we get more reports. I'm inclined to think that this is a faulty unit.
Click to expand...
Click to collapse
I hope your right.
Carl, Can you return the device for a replacement??
I'm instructing the actual owner to take it back to the BN store, get a refund, walk across the parkinglot to Staples and get a new one.
I like this plan.
computercarl said:
I'm instructing the actual owner to take it back to the BN store, get a refund, walk across the parkinglot to Staples and get a new one.
Click to expand...
Click to collapse
Do you have the serial number? Specifically, mine starts with 2004.. what does that one start with?
201146003592xxxx
Did you see if you could even read the SD from stock 1.2? Sure, android created some folders, but maybe the slot was not working well. My USB micro SD reader sometimes gives me errors when trying to copy files over. It will copy a fe MB, then it quits and the card disappears. I have to eject and reinsert the device a few times to get things working.
Related
So I attempted the OTA 2.2 update and I'm honestly not sure what exactly went wrong. I waited for Verizon to push the update, but apparently the update was corrupted because the OS was acting very sporadic and my Baseband wasn't upgraded because it was (and still is) on 1.x.
I attempted to upgrade the baseband and thing got really strange... I could try to explain everything I've done to try to fix the phone but I really can't come to a solid conclusion. I've worked extensively in the iPhone jailbreaking scene but the Android stuff is a bit different so I'm still learning how the phone is logically designed, etc the hard way.
Here's where I am now:
I cannot boot into recovery via any means... I'm pretty sure that the partition is deleted because it just jumps straight back to HBOOT. When I was still able to get into recovery, the sdcard couldn't mount as well as a few other things in /dev/block. I can't get HBOOT to recognize ANY PB31IMG.zip's nor would clockwork install them from recovery before I lost recover... when I try to flash recovery with fastboot, it says not allowed. I didn't think it would be an issue because I have S-OFF.
I feel like if I can re-flash the newest clockwork or cyanogen from HBOOT, I can then mount my sdcard and restore to 2.1 and then try to OTA again (after a nandroid backup), but I can't really get around HBOOT's permission hissy-fit.
I can't just take my phone back to the verizon store either because I'm in college and have no car and there isn't one nearby.
Any help is appreciated!
crizh4x said:
I can't get HBOOT to recognize ANY PB31IMG.zip's
Click to expand...
Click to collapse
One simple thing to check: is your SD card formatted FAT32? If it's the stock 2GB one, then probably not. You need FAT32 to flash PB31IMG.zip...
Yup, if you can get to hboot you're fine, just make sure its formatted correctly as previous poster said.
Hmm ok well, I read that little bit elsewhere and you are completely right, the card was fat16 so I formatted it as fat32 and it still doesn't offer to update the zip... The only thing I can think of is perhaps there was a problem with me having to use my phone as the card reader? I don't really have any other options there and now I can't mount it in recovery to try again.
I have a blackberry 9650 that could act as the reader I suppose... If I can get it to boot without the battery. I somehow had it pulled and left it all the way back home.
Any tips are still appreciated. Thanks guys!
I am not 100% sure this will work but since it sounds like your phone is not bricked but you have issues getting the right files on your SD card...
Card readers for your computer are dirt cheap, no?
Head to Best Buy, pick one up, and then download and transfer the files you need on it over from the computer. Then put the SD card back in your phone, and start over.
I hope someone will chime in if this sounds like a bad idea for some reason...
twentysided said:
I am not 100% sure this will work but since it sounds like your phone is not bricked but you have issues getting the right files on your SD card...
Card readers for your computer are dirt cheap, no?
Head to Best Buy, pick one up, and then download and transfer the files you need on it over from the computer. Then put the SD card back in your phone, and start over.
I hope someone will chime in if this sounds like a bad idea for some reason...
Click to expand...
Click to collapse
Or I'm sure one of your friends have a laptop or another smartphone..
Sent from my ADR6300 using XDA App
The problem is that I can't easily get to a place that sells MicroSD card readers. If I were so able, I would just go to the Verizon Store and get my unit replaced, as the technicians advised me to do on Twitter.
I need a way to format the SD card from fastboot or something else... perhaps my Blackberry 9650 will do it if it's only getting a charge from the sync cable. I shouldn't have left its battery at home. My mistake
Has anyone else had an issue with formatting it from a phone directly?
crizh4x said:
The problem is that I can't easily get to a place that sells MicroSD card readers. If I were so able, I would just go to the Verizon Store and get my unit replaced, as the technicians advised me to do on Twitter.
I need a way to format the SD card from fastboot or something else... perhaps my Blackberry 9650 will do it if it's only getting a charge from the sync cable. I shouldn't have left its battery at home. My mistake
Has anyone else had an issue with formatting it from a phone directly?
Click to expand...
Click to collapse
I formatted mine in the phone. FAT32 format is FAT32 format.
twentysided said:
I formatted mine in the phone. FAT32 format is FAT32 format.
Click to expand...
Click to collapse
I completely agree.. however I'm unable to get it formatted. One of my suite mates has a Moto Droid so hopefully it can format it and all will be well.
Here's another question though.. Why can't I flash a recovery image via fastboot? I keep getting "writing 'recovery'... FAILED (remote: not allowed)" and I'm using official images with S-OFF set so I don't really see what the problem is. I've searched around quite a lot and can't find much on it. I at least want to be able to boot recovery, or maybe flash the system partition back from hboot via fastboot.
Just curious. Thanks guys!
I had some problems with my SD Card as well (it would not recognize PB31IMG.zip) during hboot, but clockworkmod could read it. I believe there was a problem with the SD Card, kind of wierd to explain, but I replaced it with another SD Card and that problem has gone away. Could be your card is "partially" defective.
this scenario kind of happened to my friends's new incredible. unfortunately he is not rooted nor s-off. After he applied the OTA and rebooted the phone it just FC's after the boot screen animation. I'm hoping that the factory reset/data wipe will fix this thru the stock recovery or hopefully will let me put the signed .zip RUU on the sdcard and flash thru the stock recovery.
Ill let you know how things go, but it seems im in a darker situation than you are as I have no clockwork recovery to play with and get this working.
ladesidude said:
I had some problems with my SD Card as well (it would not recognize PB31IMG.zip) during hboot, but clockworkmod could read it. I believe there was a problem with the SD Card, kind of wierd to explain, but I replaced it with another SD Card and that problem has gone away. Could be your card is "partially" defective.
Click to expand...
Click to collapse
One of my SD cards is fully defective, but the one from my Blackberry is fine... I just have no means to format it.
And to the poster above me, I don't have recovery anymore since my recovery partition is apparently wiped (my bad ), however I do have S-OFF. It's just all frustrating. Why can't I flash it straight over USB like the iPhone? I miss my beloved DFU Restores with iTunes
You do need to format the SD card to fat 32 and I would do a factory re-set also.
jbh00jh said:
You do need to format the SD card to fat 32 and I would do a factory re-set also.
Click to expand...
Click to collapse
I realize the first bit but the second bit is impossible, check the rest of the thread.
crizh4x said:
One of my SD cards is fully defective, but the one from my Blackberry is fine... I just have no means to format it.
And to the poster above me, I don't have recovery anymore since my recovery partition is apparently wiped (my bad ), however I do have S-OFF. It's just all frustrating. Why can't I flash it straight over USB like the iPhone? I miss my beloved DFU Restores with iTunes
Click to expand...
Click to collapse
You realize that you don't need a micro SD reader if you have the full size sd to micro adapter card that comes with almost all micro sd cards...
Also make sure you didn't rename your file PB31IMG.zip.zip. One zip is enough and if it's a zip file, Windows will put the proper extension on automatically.
If you can get into hboot, you're not hosed yet.
douger1957 said:
You realize that you don't need a micro SD reader if you have the full size sd to micro adapter card that comes with almost all micro sd cards...
Also make sure you didn't rename your file PB31IMG.zip.zip. One zip is enough and if it's a zip file, Windows will put the proper extension on automatically.
If you can get into hboot, you're not hosed yet.
Click to expand...
Click to collapse
I have read that around... I work on a Mac and I have it setup so that file extensions are always displayed but I was last trying most of these fixes from a Win7 pc that isn't setup that way... the file extensions are hidden but that said, unless I saw "PB31IMG.zip" in explorer, I wouldn't have any issues because there is only one hidden file extension. However, now that most of the people here at my college have gone home for the weekend, I can't verify that =/
I understand that I'm not really hosed... I knew I wasn't bricked, but I'm close and it should get some people to look at this thread just a little bit more. It's a dirty little trick but it works. Hence "potentially"
And yes, I'm aware of the SD adapter thing, if I had one I could just format it through my digital camera... too bad all of my MicroSD cards came with my phones so there is no adapter.
You must be at the only college without a Walmart within walking distance. I hope you get it working, as a new SD card formatted FAT32 should fix you right up - I wouldn't trust your current card given what you've described already.
-M
smw420 said:
You must be at the only college without a Walmart within walking distance. I hope you get it working, as a new SD card formatted FAT32 should fix you right up - I wouldn't trust your current card given what you've described already.
-M
Click to expand...
Click to collapse
Much less the only college where you don't have friend or a friend of a friend that has what you need. Much less a resident dorm geek around to ask for help. I'm sure if you ask around someone would have a reader or adapter. Perhaps you will have to use it under their supervision so they make sure it doesn't grow it's own feet, but I'm sure if you asked around.
hey im a little new to droids. i have rooted my mytouch 4g and was installing iced glacier for the rom and it was successful. but now get an error message saying sd card read only. any ideas o how to fix?
Can you still access the sdcard rw through recovery?
BTW, make sure you post questions in the q&a section. I'm sure when a mod sees this they will tell you the same and move the thread.
My MyGlacier 4G MINE!!!
Had same issue, card probably had a sector corrupt. Plug into pc and right click select check card for errors and fix. It will say it found and fixed errors, you will be good after that. Thats what I get when I buy a 8gb class 6 card for $7.99
Sent from my HTC Glacier using Tapatalk
i had to pull everything off of it onto my computer then reformat the sd card then put everything back on it. i guess i had a corrupt file on it
I was in the process of pulling, reformatting, etc. But, as Johnowa stated, the option to "scan and fix", which I usually ignore, popped up, I thought, "Why not?", and it actually fixed the problem. As was mentioned, it was likely a bad sector. Hope this helps.
As the others have said, see if you can "scan and fix" or pull everything off it and reformat it. BTW, its Android. Droid is Verizons line of Android phones.
Kienz said:
I was in the process of pulling, reformatting, etc. But, as Johnowa stated, the option to "scan and fix", which I usually ignore, popped up, I thought, "Why not?", and it actually fixed the problem. As was mentioned, it was likely a bad sector. Hope this helps.
Click to expand...
Click to collapse
I would add one thing here.
Make sure you copy everything off the card BEFORE you "scan and fix" I had done that before without loosing anything. This time (on a 16 GB card I had used in another device previously), after it did the scan and fix, it generated a very long list of bad sectors, etc. and the result was an effective loss of most of the contents.
After the "fix", I reformatted and copied everything back without a problem.
Also... is this when its plugged in? I have noticed that mine likes to go into DISK MODE everytime I plug in the USB to charge. After I chnaged that in settings, I found my cable is slightly bad because if it moves the wrong direction, it pops it into disk mode again.
my apologies for posting in the wrong section i wont let it happen again. so ive tried pluging the phone into the pc to clear or format and my pc wont recognize it tried uninstalling the driver and reinstalling it and tried removing it ftom the phone and putting it in a reader directly into pc and still nothing. most likley i will go buy another today. i can access format sd card from clockwork mod but it stood idle for about 10 minutes saying formatting sd card is that normal i just removed the battery and stopped it
tbigtone210 said:
my apologies for posting in the wrong section i wont let it happen again. so ive tried pluging the phone into the pc to clear or format and my pc wont recognize it tried uninstalling the driver and reinstalling it and tried removing it ftom the phone and putting it in a reader directly into pc and still nothing. most likley i will go buy another today. i can access format sd card from clockwork mod but it stood idle for about 10 minutes saying formatting sd card is that normal i just removed the battery and stopped it
Click to expand...
Click to collapse
Sounds like you got a lemon. If this is the one you got with the phone I would call t-mo.
just got off the phone with tmobile they are gonna credit the cost of a new sd card to my account due to htc has no parts available. thanks guys for all the help. Happy Holidays!!
Please post questions in Q&A section.
Hey guys just got a nook color last night been doing some research but i made a card that I believe should have been able to boot from sd upon start up. I have not been able to get it to do this. I am not sure what needs to be done im running stock 1.2 and not feeling rooting yet just booting cm7 from the SD but if i need to root I can. Please advise i have looked around and searched and not found adequate information? Thanks
Sent from my SGH-T959 using XDA Premium App
If you follow the instructions in the forum you should have no problems. My suggestion is to try verygreens SD size agnostic setup. Follow the instructions exactly and you should have no problems.
Sent from my NookColor using XDA Premium App
k that's the one i followed but do i have the card in the nook when i write the image to it? because it says after writing the image to it to place it in the computer... also do i need to hit anything specific to boot up from SD when i turn the nook on? because those are the instructions that i followed and i have had no luck
edit: also if i am writing the disc onto the SDcard while in the nook how would i go about doing so?
but do i have the card in the nook when i write the image to it? because it says after writing the image to it to place it in the computer...
Click to expand...
Click to collapse
I was also confused by this...
I'm having the exact same problem, and am having no luck on here trying to read and find the answer.
I just got my Nook Saturday night from Best Buy, and updated it to stock 1.2. It's not rooted. I haven't done anything to it yet. Spent most of the day yesterday just trying to get the loader image to burn to the sd card, kept refusing to do it. I am absolutely NOT a geek, and hubby (who is) finally figured out what I did wrong when he got home last night. Apparently the program I used to unpack it, had it bloated to 4 GB, instead of about 130 mb.
Well, he tried following verygreen's instructions to put CM7 on the card (8 GB class 4) so we could use that in the Nook. Can't get the Nook to boot with the card, it just keeps booting stock. Once booted, I can see the card in it, but it is not booting from it. Also, there is no Touch the future of reading screen on this nook, there is a screen that says Read Forever, if that matters. I'd sure appreciate any insight into why it might not be recognizing that it should be booting from the card.
I was really excited to get this, it's the only decent tablet I can afford, but I'm a bit frustrated. And hubby doesn't really have the mental energy to deal with this sort of thing during the week when he comes home from work. And I really wanted to learn how to do this myself, so I can do what's needed when he isn't here...
Thanks ahead of time if you read all that and can/want to help me!!
It seems likely that the card didn't get made into a bootdisk correctly.
1) Are you using windows, mac, or linux?
2) How was the μsd card connected to your computer when making it into the boot disk?
3) When you connect the card back to the laptop in the same way, what happens? What is the card labeled?
Oh, and it says "Read Forever" in 1.2. "Touch the future of reading" is from 1.1, and also CM7.
chinly43 said:
It seems likely that the card didn't get made into a bootdisk correctly.
1) Are you using windows, mac, or linux?
2) How was the μsd card connected to your computer when making it into the boot disk?
3) When you connect the card back to the laptop in the same way, what happens? What is the card labeled?
Oh, and it says "Read Forever" in 1.2. "Touch the future of reading" is from 1.1, and also CM7.
Click to expand...
Click to collapse
Thank you for responding! I have actually fixed it finally. Seems the Microcenter card I was using must not have liked all this. So I had another card laying around, a 4 GB, no idea what brand, and tried it all again. This time it worked! So happy now, got it all going so I can play with it now!
Ok, I've been reading the forum until my eyes are popping out. I can not find my situation. So please forgive but I've been searching.
Bought a NC for my daughter for the purpose of Rooting it using the SD method. I followed the routine install last Monday:
1. Using WinImage, I burned the Size-agnostic SD Card image on the SDcard (Transcend 8GB Class 6 SDHC) using my HTC Incredible as my card reader.
2. Downloaded cm_encore_full-131.zip and moved it to the card.
3. Installed the SD card and bam! Everything was working and I was happy as hell!
4. I went through the process and got gapps-gb-20110307-signed.zip installed and I was working away downloading apps and stuff.
5. Downloaded update-CM7-dalingrin-OC-sd-063011.zip and got that loaded and our NC was flying high. And since we have the right kernel, downloaded Nook Tweaks and we can use a case with a USB keyboard with no issues playing Angrybirds and everything. LOVING IT!
I was happy as hell cause I wanted to be done in my limited time before tomorrow because my daughter is staying with my mom and this will give her something to do.
THEN today after powering it off. I powered it back on again and the following happened:
1. It appears to attempt boot from the SD card.
2. The green Cyannogen logo comes up and under it it says "loading..."
3. However, instead of the Android on the surfboard coming up like before, it will boot up to the stock Android with the N splash screen first then to the stock interface???
I tried several times powering it on and off to see if it was just a glitch but it still did it. Soooo, I redid the whole process again. But once I tried to boot from the SD card with CM7 loaded, the same thing happens. Green logo, loading..., then back to the NC stock OS.
I tried downloading the image a few times to make sure it wasn't corrupt and reburned the img on the SD card, tried booting it again and still the same results. (I did this whole process at least 5 times!)
Sorry for the long read but I am frustrated and disappointed that i will have to tell my girl that it's not working like it was earlier. Can someone give me any advice to try? Or what can I possibly doing wrong? I'm beyond my skill sets at this point. The only thing that I can find on the forum is that it maybe the Transcend SD card but it worked find for three days. Can it really suck that bad after 3 days? I only have tomorrow to work it during the day so If I have to I'll go to Costco and get a Scandisk over there as some have mentioned, I will. But if there is something someone can tell me to try, please let me know.
Thanks in advance!
You are probably on the right track with getting a new SD card. One of two things happened: the SD card failed during the initial "burn-in" period or the Nook's reader slot did. The card is thebmore likely point of failure.
If the problem persists with a new card, get your Nook back to B&N for warranty replacement. Just don't let them have your SD cards an you won't lose all your work
P.S. Yes, ANYthing electronic can "suck that bad after just 3 days". If an electronic component is going to fail, it will either be DOA (and even cursory quality control will catch it) or it will fail shortly after being placed in regular service (burn-in). If it survives the first 60 to 100 hours of use, it will PROBABLY last for years.
Thanks DiDGR8!
I hear you on the electronic part. I was also really tired when I posted. I guess I just didn't want to believe that the card was the issue or rather could be the issue specially when I can read the card from my phone and read it from the NC in the stock interface. It had to be something I did or forgot to do. But I've seen stranger things happen. LOL Things can break.
As soon as I can, I will run out and get a new (Scandisk) card and I hope that it resolves the issue. I hope it is not the NC's reader slot because I hate going through the "returning process" plus we have to leave tonight.
I'll post my results as soon as I can today.
I often not to believe the uSD card itself is the problem but I guess this time, I believe it.
I have the same card as yours (Transcend 8GB class 6), testing random read/write small block and the result were about 0.08 (meaning bad). Sure enough, running CM7 off it last few days then I got ton of FC errors. I now then boot CM7 from eMMC and use the card as an external storage, the card still gives me some problems.
Try Sandisk and keep yours fingers crossed.
Well at least I'm not alone. Thanks votinh!
I wanted to avoid running it from eMMC so that if i wanted to I can do the warranty thing.
Well, I got me a Scandisk 4Gb Class 4 this morning in addition to a card reader/writer to eliminate my phone as a card reader.
Followed the steps and still the same thing. However, I did noticed this time some I/O errors come up during the installation process.
So, I let it go to stock so i can test my phoness SD card (Scandisk 2GB) and it worked just fine. So, I'm really stumped now.
I'm going to try flashing it again a couple of more times. I can go to B&N and tell them it is not working but if i show them it does work reading my phone's SD card. unless i just push them for an exchange.
OK, tried the the latest stable and now the Driod comes up and it is in a loop. I abandoned that all together. Need to stay focused.
So, I went through the process again using #133 on my Scandisk 4GB and tried to boot with it. Same results again Green logo, loading..., then back to the NC stock OS.
However, this time I was able to take a pic of the screen so I can copy what I saw when I saw I/O errors during the installation. So at one point I got:
end_request: I/O error, dev mmcblkl, sector, <insert number>: this flashed down the screen quite a bit
also
JB2: DetectedIO errors while flushing file data on mmcblk1p2-8
Ok so I went back to the Transcend card and did #132 but using my new reader. This time it seem to install clean. When I powered it back up, this time str8 to the "Read Forever" splash screen and back to stock. Weird.
So, I redid the 4GB card again and got the I/O errors again same thing the "Read Forever" splash screen and agian back to stock. It's like it's telling me to go F*** myself.
At this point, I'm thinking its the NC reader reading off the card itself. I tried 2 brand new cards, dif brand, dif reader/writers, multiple downloads of the img and installers...I don't know what to say. I should just root it to eMMC but if i'm having trouble with the SD method and I go eMMC and that messes up I won't be able to return it on Warrenty. What am I doing wrong? Can anyone give me anything else, I'm desperate and ready to fling it out the window. LOL
LOL I love the way I'm bumping my own thread here.
So, I went to B&N and got me a new replacement NC without any hassles.
I ran through the routine from scratch with CM7 #133 (which I believe has the OC kernel in it) on my new Scandisk 4GB Class 4 without the gapps.zip just to take it one step at a time.
I powered it on and prayed to the CM7 gods. I see the same I/O errors on the install and I also saw chown: cannot access '/tmp/backuptool.sh' : No such file or directory which I've seen before as well. However, this time the droid came up refreshing itself in a continuous loop. Like when I tried the stable version earlier. I did this twice and the same results.
At this point I'm thinking it maybe the WinImage. I'm using Winimage V 8.50? So, I downloaded Win32disk imager to give it a try and using my phone as the reader again because that was the last known combo. Again, the same errors. Then the Logo, loading…, this time blank screen…crickets…
I’m out of ideas…I had a clean install once on Monday worked fine until yesterday and I can’t do a damn thing.
Different SD cards, 2 brand new NCs, different readers, multiple downloads of image, installer, etc. Two dif imagers as well…Someone please tell me you are missing a step or doing something working because this does not make any sense… Booting in recovery mode maybe?
The only idea I have is a longshot. When you were getting the looping bootanimation (the blue Andy on a skateboard), or the "crickets"; how long did you wait before aborting the boot?
I have seen it take a LOT longer in those steps than I ever remembered (or thought reasonable). I'm talking 5 or 10 minutes.
It has something to do with recreating internal partitions and the dalvik cache (IIRC). It's been so long since I booted off the SD card, I'm not really sure what is supposed to happen that way.
Sorry that I can't offer more than "just let the first boot take all the time it wants".
It's all good. I understand.
So, Truth be told I think the first time with the "stable" image I let it go for 3 rotations before I said jumped ship. As I type now, I tried going back to #128 and it's doing it again. Andy has done skated across it at least 20 times...21... I'll let it run for a bit since you say that while I research the recovering to stock in emmc in case I decide to chuck it up and go emmc. This is driving me crazy. I would guess that emmc maybe more stable than running it from an SDcard.
You have got to be s***ing me. So I staied persistant and used my 8GB Transcend card again. This time it installed clean (I was taking pictures so I can read the damn thing) and booted clean. WEIRD!!!
I'm going to see if I can get my Scandisk to do the same.
I have seen mention that using the latest winimage is not a good idea, something about it not working right.
Version 8.1 is the usual recommendation.
I have been using the dualboot image racks11479 put together, and i've burned it with winimage a handful of times without issue, but always used winimage 8.1
Not sure if that's your issue, as i've never forayed into the realm of recent nightlies, but it could be a contributing factor.
Win32Disk Imager works perfect for me, even on win7 x64 and winimage would write, but the disk wouldn't boot.
Sometime after I installed safestrap and a second rom, I lost the ability to write or delete from my external SD card. It may have something to do with SAFESTRAP, or possibly an app called SDFix: KitKat Writable MicrosSD which I installed and may have ran in preparation for any type of KitKat update. Anyone have any ideas of what I may have done?
edit for more info : The weird thing is, it lets me go through the motions to delete a movie file with say ES File Explorer, but when I reboot, the file is still there and I am able to watch the same exact file I thought I deleted. Also, if I set my camera to write external, it seems like it works, but when I reboot, the files aren't there anymore. Luckily the few pictures I tried taking like that were uploaded to my dropbox before I reboot..... Also, if I create a new folder and paste a file into there, the folder won't be there when I reboot. Also, it seems like my titanium backup files aren't updating, they all seem to be dated February 28 and they won't update even though it goes through the entire backup process!
ssmaster said:
Sometime after I installed safestrap and a second rom, I lost the ability to write or delete from my external SD card. It may have something to do with SAFESTRAP, or possibly an app called SDFix: KitKat Writable MicrosSD which I installed and may have ran in preparation for any type of KitKat update. Anyone have any ideas of what I may have done?
Click to expand...
Click to collapse
Have you tried taking the card out and seeing if it works properly on a computer?
airmaxx23 said:
Have you tried taking the card out and seeing if it works properly on a computer?
Click to expand...
Click to collapse
That is a good idea. I'll try once my co-worker comes back from lunch so I can borrow their microsd-usb adapter. The weird thing is, it lets me go through the motions to delete a movie file with say ES File Explorer, but when I reboot, the file is still there. I am able to watch the same exact file I thought I deleted. Also, if I set my camera to write external, it seems like it works, but when I reboot, the files aren't there anymore. Luckily the few pictures I tried taking like that were uploaded to my dropbox before I reboot.....
The card is an 64GB Sandisk, and the computer won't recognize it, I believe because of the way it is formatted. When I get home, I will try to connect via USB 3.0 and see if I can dump everything to my PC and go from there....
ssmaster said:
The card is an 64GB Sandisk, and the computer won't recognize it, I believe because of the way it is formatted. When I get home, I will try to connect via USB 3.0 and see if I can dump everything to my PC and go from there....
Click to expand...
Click to collapse
Your computer should still recognize it though.
uhh ohh, its a VDI virtual system, and it says this card needs to be formatted before windows can recognize it....
I am copying everything over to my PC over USB. I will try the card in a card reader to see what can be done. If I format it, and if it works after format, should I have confidence that the card won't crap out on me in the future¿???
I am finally able to format it using a slow format in Windows 7, lets see if it works...
Nope, still broken with all previous files in tact.
I'm having the exact same issue and I bet others are too. At first I thought it was something to do with an ESexplorer update since I never happened before it, but I've deleted ES and tried many other file managers/explorers and still have it happen. Someone has to know how to fix this.
nickgordi said:
I'm having the exact same issue and I bet others are too. At first I thought it was something to do with an ESexplorer update since I never happened before it, but I've deleted ES and tried many other file managers/explorers and still have it happen. Someone has to know how to fix this.
Click to expand...
Click to collapse
I had the same issue with the same card. After a lot of research I found that my SD card had somehow become locked...I know...WHAT? My sd card is looked with no way to unlock it. I can view files on it but i cannot add files or delete from the card.
I emailed Sandisk asking them if they had a solution but I never heard back from them
I have tried every solution that I have found and none have worked...
I've gone through 6 San disk 64gb class 10 cards between my Note 2 and Note 3 with my last cropping out 2 weeks ago. San disk will replace your card and tell you to contact the phone manufacturer. I did that contacted Samsung...at 1st I got the run around but I was persistent and got a hold of a good tech support agent. Samsung phones have issues writing info to the 64gb class 10 cards. They are aware of the issue and are working on a fix as of 2-3months ago. He told me the will work fine. He said they don't recommend over 32gb and a class 4 card because of the stability issues of files being corrupted on class 10s particularly 64gb 1s. Funny thing is i called San Disk back and told them what i was told and asked for a 32gb lower class and he told me i could buy it buy they could only replace it with the same one i had. Good luck!
Sent from my SM-N900V using Tapatalk
You know this is not the first time that I've heard of this. I actually had a 10s 32Gig SanDisk micro that I ended up losing because of this problem with my Galaxy S3. I got to work one day and set my phone down on the desk and it just seeming stopped working. I don't know what it is with the 10 series cards but it seems like they all have some kind of problem.
Thanks everyone for all the info. I guess I'll have to get another card and I'm going to be sure it's NOT another SanDisk.