Related
No matter how many times I wipe my phone I still can't flash any pic the newer roms. I have root explorer an have been able to see that nothing changes. The weird thing is I'm not getting any errors after installing a Rom. Usually if there is a media folder on my SD card but never get passed the three skateboards. I can flash tazz14 an it boots just like I never took it off my phone. An no it wasn't flashed from a nand. Need help.
Sent from my Eris using XDA App
cpole17 said:
Usually if there is a media folder on my SD card but never get passed the three skateboards.
Click to expand...
Click to collapse
I intend no disrespect, and perhaps I am alone in this, but I'm having difficulty understanding, other than in a general sense, what this sentence means.
I agree. Don't really understand what you are saying. What are you trying to flash?
I've checked some of your previous post discussing the problem. It is unlikely but possible that your recovery image has been corrupted. I would suggest that you recover from a nandroid then run jcase's one click root app, don't worry about flashing rootme.zip, but do ensure that you reboot twice after running the app. And when you flash the ROM do both Dalvik wipe and factory/data wipe. Hope this works.
http://dl.dropbox.com/u/8699733/erisone010.apk
ok sorry for the broken sentences. I let my frustration get the best of me.
I use to be able to flash any rom. One day I decided to try some of Tazz and shed's roms. I had no problem flashing up to Tazz v14 and shed's v2. I tried to flash Tazz V15 and this is when I first noticed my problems.
When I would flash v15 or higher i would get the e: error in line 238 e:wasn't able to write boot image and installation aborted.
Shed's roms don't give me the error it just says installed from sdcard. On a re-boot I just get the skateboards and it never boots. just sits there. At first I thought I didn't wait log enough so I waited 20 minutes. Never booted.
I always do a factory/data and dalvik at least 3 times before trying to load a new rom
I don't believe it has anything to do with their roms. I went all the way back to 2.1 stock and started over. then one click eris root. It seems as if i flash a new rom the new stuff doesn't overwrite over the old system files.
sounds like it could be a couple of issues.
not sure what recovery you are using... but i'd read this thread here:
http://forum.xda-developers.com/showthread.php?t=827718
could be some very useful tips for clearing space on your phone.
reason i say that... if you are getting all the way to the boot image, then it's failing... then i'd say you either have a bad DL (check the md5's), a bad recovery image (already mentioned), or you are running out of space in /system/ block (maybe the reason some ROMs are successful in flashing, and not others... as the "heavier" ROMs maybe too big to fit on whatever amount of space you have left in /system/).
if you could, load/flash a ROM that works... then, from a command line, do the following and post it:
adb remount
adb shell
busybox df -h
copy/paste the results so we can have a look
Filesystem Size Used Available Use% Mounted on
tmpfs 95.4M 12.0K 95.4M 0% /dev
tmpfs 95.4M 0 95.4M 0% /mnt/asec
/dev/block/mtdblock3 170.0M 105.8M 64.2M 62% /system
/dev/block/mtdblock5 159.5M 37.0M 122.5M 23% /data
/dev/block/mtdblock4 130.0M 47.8M 82.2M 37% /cache
not sure if this is what you mean. never ran adb before.
I'm having a similar issue where I can't get past the skating androids when flashing new ROMs. KaosFroyo v37 is the only stable ROM I can flash. I've tried numerous things to fix with no luck. I hope we can find a fix.
P.S. - My mem usage breakdown looks very similar to yours. Within a few %.
There has to be away to clear alot of that data. Just don't know enough yet to do that.
Sent from my VANILLA TAZZ using XDA App
cpole17 said:
There has to be away to clear alot of that data. Just don't know enough yet to do that.
Sent from my VANILLA TAZZ using XDA App
Click to expand...
Click to collapse
hmmm... if I correctly recall there is a delete partition command associated with fastboot. I have no idea what would come of this. Perhaps as a last resort.
I haven't given up just have had no time to work on this.
Sent from my VANILLA TAZZ using XDA App
I'm still stuck with the same prob too. Here are a few things I have tried in the past week.
1. Repartition SD Card to 1 partition.
2. Format SD Card FAT32.
3. After flashing, booting w/o SD Card.
4. Completely unrooted back to 2.1, rerooted.
All of these were followed by a fully wipe, dav wipe, flashing new ROM and reboot and all resulted in endless skating androids.
I'm just stumped.
I have a feeling that the OP has one of those Erises that cannot be overclocked to 710 MHz; all of the latest ones seem to default to that. I'd say that it would be proved if you can flash Plain Jane and it works, as that defaults to stock 528 MHz.
I did find a way to alter the xtrROMs to allow a flash and then, before restarting the phone, using ADB commands to change the default maximum clock speed to something other than 710000. See http://androidforums.com/eris-all-things-root/212791-kernel-overclock-custom-rom-s.html#post1841188
It's worth a try, anyway. I'm not sure that I'd try it with anything other than xtrROM or xtrSENSE for now; I haven't checked any other ROMs to see if that would be the proper procedure.
I have been working with Conap who writes the kernel for many of the new roms out there for the past week and we finally resolved the issue. Apparently with CFSv6+ he added CIFS support to the kernel which was causing the boot problem for me. Try flashing his rom CELB v3.8 and see if it works for you.
I am curious as to why in my Task Manager it shows that I have 19mb of "Personal Info" (PI) when I know that is not true. I have googled and searched these threads about it and this is what I have found. It seems to be some dead apps. I am running Toxic8 w/ Bali 1.2 kernal but before I had stock 2.2 from Cincinnati Bell. While on Bell's 2.2, my PI was only around 2-4mbs max (facebook/ contacts/ media-those types of things). I wiped/reset/wiped again and flashed the Toxic8 ROM.
I have an app called DiskUsage (great app) which shows what is in each folder by apk/dalvik/data-pick one, two or all. I generally just use the /data as my view point. There is a Root point to that also scans you Root folders too. It can show, lets say Facebook. You can click on it>hit show and it takes you to that apps file in Manage Apps where you can delete data/cache.
Now, I say this b/c if I run it and it shows the /dbdata folder, it shows my normal amout of personal info +/-3mb but then it also shows that /system is taking up 16+/-mb of space. I think that is the problem. What is this /system part as I have looked all over the /system folder to see if there are any links or something and can find anything that matches.
Why is my Personal Information so big if I only have 3+/-mb of personal information on it.
This is what I have tried and searched.
SDmaidPro. Corpse, Clean system/apps/ Optimize No luck
Wiped, reset, reflashed, bootloop **crap.
Wiped, reset, relashed, wiped, bootloop **crap
Wiped, reset, restored only /system, bootloop **argg*crap.
Restored and it boots up just fine but PI is still sitting at 19mb b/c obviously it was restored.
I am thinking that it is maybe the symbolic links to my first ROM that came with the phone (only had it 2 weeks or so), PLUS all the apps that came with Toxic8, but a fair amount of those, I have deleted. Think this is a Samsung bug from what I have googled. I don't want to wipe internal SD card b/c I am fairly certain the bulk of what I am looking at is not there (so it would be pointless).
Ideas and sorry for the manifesto sized post?
This is what I am finding so far after some adb work. The /system is somehow mounted to the /dbdata partition. Maybe b/c of the voodoo making them both ext4 partitions. I ran Mount and confirmed both are ext4. I don't know how or why.
I also ran busybox df -h to see what partitions are and how munch total/free/used space there is. It shows that in my DBdata partition that I have way more that I should. My personal data should only be about 3mb but it is showing at now 20mb. Before you say "why worry, you have 126mb of space". I did some tests and if I install an app, fine that is great. But say that I install it, don't like it and uninstall, it is still inflating the Dbdata partition and will not come out. This can cause long term problems with partition filled and no where to install apps. They are not in /data/data anymore but are somehow getting linked to /system AND /dbdata.
The folders in Root Explorer are
dbdata/databases
dbdata/db-journal
dbdata/lost+found
dbdata/system The four of these are normal and contain the usual personal information like passwords, cache,...and total around the 3mb as stated above.
My problem is that the /dbdata and /system partitions are somehow linked and when I install and app, it gets pushed to that phantom link and cannot be deleted. See the long term problem now?
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.
So, this one confounded me for a while. I found the solution (I think) and hope this might help others.
I've been playing with ROMs these past few months and last week installed the latest Hellybean. I don't believe the ROM itself is relevant though.
Anyway, at first everything went well. Then I got warnings I was running out of space. My 2GB partition was down to less than 200MB. I checked Disk Usage and saw that 900 was for apps, but another 900MB was just marked 'System'?
Thinking it was maybe remnants of all my other flashes, I booted into TWRP, wiped everything again, and reflashed. Again, fine at first then no space after a day or so.
After much searching I found the problem using Storage Analyzer. It seems I had 900MB of files in the /data/lost+found directory. I'm not sure how so much lost and found data got created after my format, but that was it. I deleted it all and have been fine ever since.
My only question, I guess, is is that OK? From what I know of Linux my guess is yes, but I'm not 100% when it comes to Android. Anyone care to comment?
Thanks
Hi,
I own a rooted Lenovo P780 that was bought as a gift. The phone was pre-rooted (the bootscreen mentions lenovo-forums.ru, I think it's a worldwide ROM that's installed). It's been fine for a year, but in the last few days, the internal storage has maxed out, causing problems with updates.
Yesterday, I tried something as an experiment without really thinking through the full consequences.
I had busybox and terminal emulator installed so I made a copy of the /data/dalvik-cache in the built-in SD card (since it's always present and I have an external one for all my regular data), renamed the existing dalvik-cache directory to dalvik-cache-bak (as a precaution before outright deleting, lol) and created a symlink to the new location. Everything was fine, until I restarted...
I'm not sure if the permissions are invalid or the internal SD card is not mounted early enough in the boot sequence but now the phone is basically crippled. It's not outright bricked; it does progress so far into booting, then opens many requesters about all the stock applications failing. It basically gets stuck trying to restart them.
I've not really used ADB before, but I assume that it should be possible to mount the /data partition, remove the symlink and rename the dalvk-cache-bak to dalvik-cache and at least get the thing working before resorting to some sort of factory reset.
I feel completely nubular for having to ask, but the question is, what exactly do I need to do to get into the device?
kdkc said:
Hi,
I own a rooted Lenovo P780 that was bought as a gift. The phone was pre-rooted (the bootscreen mentions lenovo-forums.ru, I think it's a worldwide ROM that's installed). It's been fine for a year, but in the last few days, the internal storage has maxed out, causing problems with updates.
Yesterday, I tried something as an experiment without really thinking through the full consequences.
I had busybox and terminal emulator installed so I made a copy of the /data/dalvik-cache in the built-in SD card (since it's always present and I have an external one for all my regular data), renamed the existing dalvik-cache directory to dalvik-cache-bak (as a precaution before outright deleting, lol) and created a symlink to the new location. Everything was fine, until I restarted...
I'm not sure if the permissions are invalid or the internal SD card is not mounted early enough in the boot sequence but now the phone is basically crippled. It's not outright bricked; it does progress so far into booting, then opens many requesters about all the stock applications failing. It basically gets stuck trying to restart them.
I've not really used ADB before, but I assume that it should be possible to mount the /data partition, remove the symlink and rename the dalvk-cache-bak to dalvik-cache and at least get the thing working before resorting to some sort of factory reset.
I feel completely nubular for having to ask, but the question is, what exactly do I need to do to get into the device?
Click to expand...
Click to collapse
Hi. Try this: reflash stock 124 ROW firmware, then upgrade to KK.
Look in my posts for Stock 124 Firmware and how to root.
4GB: https://drive.google.com/folderview?id=0B2ORIgaV4iacaVNmUWEzcDh2Nzg&usp=sharing
8GB:https://drive.google.com/folderview?id=0B2ORIgaV4iacbmZrcWN1WEZDYlU&usp=sharing
Good luck.
Sent from my Lenovo P780 using XDA Free mobile app
Thanks for the post. However, I really don't wan't to reflash the phone just yet as there is data (contacts etc) on there that aren't synced yet and I don't want to lose. Also, reflashing the phone to fix a basic filesystem issue seems like using a nuke to crack an egg.
I need to be able to boot the phone into recovery mode, but I can't seem to find any option for that. The only key combination that does anything different than a regular boot is holding power & volume down which boots into "meta mode", which doesn't seem to be useful.
Is there some special trick for this model to get into recovery mode?
kdkc said:
Thanks for the post. However, I really don't wan't to reflash the phone just yet as there is data (contacts etc) on there that aren't synced yet and I don't want to lose. Also, reflashing the phone to fix a basic filesystem issue seems like using a nuke to crack an egg.
I need to be able to boot the phone into recovery mode, but I can't seem to find any option for that. The only key combination that does anything different than a regular boot is holding power & volume down which boots into "meta mode", which doesn't seem to be useful.
Is there some special trick for this model to get into recovery mode?
Click to expand...
Click to collapse
Did you tried key combination like: power + vol up and down pressed together?
Sent from my Lenovo P780 with TWRP 2.7.1.1