View Single Post
Posts: 7 | Thanked: 3 times | Joined on Jun 2011
#22
Originally Posted by jpala16 View Post
Hmm, that's suspicious. Has anybody installed Nitdroid in a 16GB Class 10 SD card with the Nitdroid installer with success?
I checked that the files for the installation were right because I achieved the installation in another card.
I checked that the card was not broken 'cause I was able to copy files onto it and then read them (the Nitdroid bootlog was really faster than with the other card, until it crashed, of course).
It must be something related to speed/capacity or maybe is a fake (or Kingston is really bad in this kind of products), and it writes or reads data with errors.
Yes, money down the drain galogeek. I suppose that I will use it for storing music...

well Idk what I did other than kept trying but I had kept running into the FAILURE...Bailing out issue but i realized it only bailed on certain parts of the process IE.downloading .nitdroid.manifest. so I kept re-editing the two manifest files in the root folder & .nitdroid folder until it surpassed that issue. The problem had appeared to be that the downloads ie.kernel were not matching up with the files listed in the manifest (I had c3 but in the manifest it requested c4) So after I corrected that the installation ran the manifest theennnnn it came to the downloading N12_UMAY part and the FAILURE..bailing out issue popped up again sooo i edited the manifest again to see if the link directed for the download was correct but when I inserted the link into my browser the page came back null so I added .deb at he end of the link in my browser and to the manifest and It went through after that and thedownload process passed. THENNNNNNN THE ISSUE I HAVE NOW....After the download of n12 went through the issue came up with extraction, ectractin N12_UMAY... FAILURE..bailing out. So I assumed that the file was corr. or bzip wasnt getting it to extract soooo smart experimenting me decided to manually extract it in term and it was extracting fine...for a while then gearing near the end It started saying could not find files then eventually it said the dreaded no space left on device so I ran df and my rootfs was full to 100 percent...sooo what i am assuming now is that either the partitioning is all wrong or somethings not setup correctly in the manifest and these files arent being extracted to the right place.

ANY IDEAS FELLAS? BTW I JUST WANNA THANK U ALL FOR ASSISTING ME IN MY MATTER IVE BEEN TRYING THIS FOR ABOUT A WEEK NO BUT IDK I JUST CANT FIGURE IT OUT. I am a complete noob to the linux OS and although this is frustrating...Ill admit Im not as dumb to it anymore. Ive learnt alot.

so yeah any ideas...oh yeah also I think I may have to reflash my phone given that although I was ablr to clear up somme of the files in my rootfs that was taking up all the space which brought it down to 76 per I still see alot of files there that I know is not supposed to be there..but..Im not sure..so maybe Ill have to flash..what do u think?

PS SORRY FOR THE LONG POST. ANY HELP WILL BE APPRECIATED!
 

The Following User Says Thank You to galogeek For This Useful Post: