Related
help, stuck in bootloader/recovery
« on: Today at 01:48:03 AM » Quote Modify Remove
--------------------------------------------------------------------------------
stock 2.2 3.29 rooted w/unrevolked.
any help is appreciated.
So I was looking into roms and I downloaded ROM manager 3.0.1.1. Thats when my trouble started. I did a back up with the rom manager and it wiped my old nandroid back ups and I was stuck in bootloader/recovery and couldn't restore my back up. I do an nandroid back up about once a month and they were all gone. I did back up my sd card in december and I had an old back up on it and I flashed it and it worked.
Tonight I tired to flash an older version of clockwork (like I had before) and I'm stuck at the bootloader/recovery again. I tried to restore an old nandroid and nothing seems to work.
I'm open to suggestions.
Should I try to flash a new rom and start over ?
any way to get my old customized rom back ? (I have the clockwork back ups)
thanks
are you able to boot a rom at all?
I haven't tried a different rom, but I cannot boot my current or older.
It can't load PM36IMG.zip, I tried loading one onto my card but it just aborts the installation. Is there a more current or older one one I need ?
that might be a problem. you sayed you were trying to put a PM36IMG.ZIP on but you need a PC36IMG.ZIP i believe if your on an evo. use amon-ra and and flash a new rom and see if it works. copy and paste this link into your url and it will start a download for amon-ra recovery. hope this works
http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=PC36IMG.zip
also don't try to flash a clockwork nandroid backup with amon-ra or vise versa. it will mess up your phone from what ive heard
I wonder if it does not like your sd. I am thinking try a different sd or see if you can format yours.
I also do not like ROM managers. They always seem to want an upgrade and then when you do the upgrade your old backups may or may not be compatible any more. To get your old file back you would probably have to run an unerase or some type of debug program on the sd card. erased files are not really erased they just have an F5 in front of them to tell the computer that the space is availible. If you have a backup on your compter or old SD I think you should be able to that.
I did check for errors on my SD card, nothing bad there.
I put a PC36IMG.zip on my SD and when I try to install the zip from my sd it says operation aborted.
I think my entire problem is the fact that I have clockworkMod recovery v3.0.0.5. I've read (after) that anything after 2.6 is not going to play nice with my evo.
I tried downloading a stock rooted rom and I cannot flash it. Anytime I boot the phone it stays on the HTC EVO white screen, I can hold down the - and power and I can go into HBOOT/fastboot/bootloader/recovery, then it cannot find the PC36DIAG.zip, and PC36ING, and a few others.
I really appreciate the help, keep it coming
edit: I'll try pulling everything off my card and formatting it...
card is fine.
I loaded a older clockwork recovery then tried to flash a different rom...
it started opening, installing, formatting, deleting, copying, then...
E: can't symlink/system/xbin/su
E:failure at line 76:
synlink/system/bin/su SYSTEM:xbin/su
installation aborted.
and when I restore a previous nand backup it appears to work then when I reboot the screen looks scrambled and freezes.
I'm tired
I'm starting to think a hard reset and starting over might be my only way out.
Your system can not root since it can not find /system/xbin/su su is not in bin
ln -T /system/xbin/su /system/bin/su would probably be the approach if you were running. Not sure if you could edit line 76 to change bin to xbin, copy a proper symbolic link or?
I looked in bin and there were many links to the tool box that appeared to be associated with error logging. With this in mind it seems to me that this link is part of the recovery/installation process.
I would try to correct the permissions.
I was able to do a hard reset and my phone booted up rooted still..so I restored my apps from Titanium Back up.
Right now I can shut my phone off, restart it, no problem. If I go into recovery, problem.
I need to get rid of clockwork asap, I've read about Amon_ra's recovery but I don't think I have enough knowledge yet on how to install. I've tried installing from a zip but I'm just not doing it right. I can go into folders on my phone (root explorer), should I just delete clockwork anywhere I find it ? I just don't want to go blindly deleting files, that would be dumb.
I need recovery back...this is scary
suggestions ?
I have been into Android modding since My G1 from day ONE, I bricked a friends G1 and had to swap internal stuff and fixed it so I have never had a problem I could not solve till now, Like the guy above I cannot boot into my ROM. I have running Myn's Roms since his(their) first release with ZERO problems until RLS5. I started getting random reboots so like any other time when this happened with anyone elses ROM I did the Recovery, Wipe Dalvic Cache, Wipe Cache reboot and that was that, However today my Evo would not stop rebooting every 5-10 minutes so I wiped from scratch even my sd card was wiped, then reflashed Myn's RLS5 got it to boot once and after finishing SETUP it was on for like 2 maybe 3 minutes and again REBOOT!!! this time staying on the white screen, So I pulled the battery and went to recovery and wiped dalvic and cache rebooted and from then on It does not get past the white screen, I can still get into Fastboot and Recovery but it DOES NOT boot into the ROM, I am now Flashing MYN'S Z 2.2 and praying it boots. Do you guys think VIRUSES are now affecting OUR EVO's????
I just need to get rid of clockwork and I'm still stuck on that...
help ...
Attached is amon_ra 2.3 boot into the bootloader and apply update, reboot, boot into recovery and clockwork will be gone.
teh roxxorz said:
Attached is amon_ra 2.3 boot into the bootloader and apply update, reboot, boot into recovery and clockwork will be gone.
Click to expand...
Click to collapse
ok, I just want to be clear.
First, I'm sorry if I'm noobish
next, I'm gonna put that PC36IMG on my SD card (just anywhere on the card) then go into the bootloader, choose apply update, then boot into recovery, then done, correct ?
side note, I've read around that it should be put on the root of the card, I don't have a root folder on the card, but there is one in the internal system file (found it in root explorer).
just want to clarify before I loose everything again.
You are correct, and the "root" of the sdcard means to just be on the sdcard, not inside any folders. Also don't extract the zip file.
solved.
you sir, are my hero.
you have solved my problem, I'm speechless and so freakin excited right now.
I sincerely thank you and owe you.
teh roxxorz said:
Attached is amon_ra 2.3 boot into the bootloader and apply update, reboot, boot into recovery and clockwork will be gone.
Click to expand...
Click to collapse
Would this work for the Incredible as well? I have the same issue (tried to flash clockwork recover but can't get into it on the phone). Also cannot get into the ROM, so stuck at the boot screen and nearly every command brings me back to it...
Thanks
As I often have problem of internal memory (not enough),
I tried to apply on my Wildfire the Custom MTD Partitions, as explained here:
http://forum.xda-developers.com/showthread.php?t=1233340
(and which seems very interesting)
But even all steps seems to do something, it doesn't have any impact on the size of the memory...
I tried to apply this size of memory: 145 10 (mtdpartmap.txt)
In order, I did this:
backup, reboot to CMW Recovery, Nandroid Backup, copy the 3 files needed on the SDCard,
format /cache, then format /data, then format /system, then perform a Wipe Data / Factory Reset, then flashed recovery zip, then Reboot Recovery, then Restore the nandroid backup
=> Remark: at the end of the retore of backup, I had an error: "Error while formatting /sd-ext!" (don't know if it's normal)
Then I flashed the boot zip, and finally reboot the Wildfire.
But when I'm checking the memory, sizes are the sames: 183 interal (including 40 for cache).
What I did wrong ?
HTC Wildfire S-Off, CM7 n215
Recovery: 4.0.0.2
S2E used
Make sure your not naming the txt mtdpartmap.txt.txt only have 1 .txt at end.
Sent from my HTC Wildfire using XDA App
Yes, as I saw that someone did it, I verified it.
I tested without any extension too (only mtdpartmap), but result was the same.
I will try again, by changing the values-number in the file...
Maybe an additional question: inthe topic is written:
"When you flash a new ROM, you WILL lose the new settings ("partially"). To overcome this, after flashing your new ROM, flash the boot-v1.5.8-Beta-CustomMTD_S attachment immediately after flashing the ROM before restarting your device."
Does it mean that I should do these operations each time I want to install the last build of cm7 ?
Yes, you have to flash the 'boot' attachment only everytime you flash a new nightly (or a new ROM, or even restore an old ROM, for that matter). If you don't, the device will not boot. (This is applicable even if you do not wipe before flashing a new nightly)
For your issue, although I can't really seem to figure out what the issue is, I would say try flashing a fresh install once just to check whether the procedure itself works or not.
If it still doesn't work after a fresh ROM install, try with the older version of the Custom MTD Script: (Although this shouldn't really be the problem)
http://db.tt/JjGxneZD
http://db.tt/C5noTQl9
this happened to me, but i realized rooted phone doesn't mean s-off, double check it has s-off?
I can solve this issue lol i think. Do this order instead
:backup, reboot to CMW Recovery, Nandroid Backup, copy the 3 files needed on the SDCard
Wipe Data / Factory Reset
Flash bravo-recovery-v1.5.8-CustomMTD.zip
format /cache, then format /data, then format /system
Reboot Recovery, then Restore the nandroid backup
BEFORE REBOOT:Flash bravo-boot-v1.5.8-CustomMTD.zip
Now should work. Well this is how i do it and works. I did the order you said the first few times
I hope this helps
Thx to all for your help.
Yes, my wildfire is S-OFF, I verified again.
About the version v1.5.8, I got it, and will install it quietly in the order you indicated below, I will inform you if it's ok by this ;-)
I just tested in this order, and I'm blocked at the end on the blank screen HTC.
But, little question: I used the files recovery-v1.5.8-Beta-CustomMTD_S.zip et boot-v1.5.8-Beta-CustomMTD_S.zip (so tagged as beta). Are they the sames files than the ones you used ?
HTC Wildfire S-Off
HBOOT 6.01.1002, CM7 n228
S2E used
Just for info:
finally I just tested again the same order, but I flashed an new build instead of to restore my last backup.
It booted correctly, and as I can see, I have now more memory available.
Many thx
Now, I have to restore my apps and data (thx titanium )
flippy12 said:
Just for info:
finally I just tested again the same order, but I flashed an new build instead of to restore my last backup.
It booted correctly, and as I can see, I have now more memory available.
Many thx
Now, I have to restore my apps and data (thx titanium )
Click to expand...
Click to collapse
Damned, I talked too quickly.
This didn't impact the memory, even I flashed MTD for 145 10, I still have the sotck format memory
Only once have I had problems loading custom mtd values,I tried for hours and figured out it was the cwm 2.5.0.7 version which was causing problems cos as soon as I tried with 3.2.0.0 it applied 1st time. Have you tried different cwm?
sent from my wilderbeast:buzz
Which cmw are u using? I used version 5.0.2.0
Sent from my HTC Wildfire using xda premium
Ah yes, interesting point...
On ROM Manager (4.7.0.5), I see that CWM is 5.0.2.0.
In recovery mode (used to backup/restore for this operation) , CWM is v4.0.0.5.
Does this version a correct one, or should I upgrade it to the 5.0.2.0 ?
flippy12 said:
Ah yes, interesting point...
On ROM Manager (4.7.0.5), I see that CWM is 5.0.2.0.
In recovery mode (used to backup/restore for this operation) , CWM is v4.0.0.5.
Does this version a correct one, or should I upgrade it to the 5.0.2.0 ?
Click to expand...
Click to collapse
In order to ignore (solve I mean) this problem of CWM version, I flashed directly the version 5.0.2.0 by the terminal: now it's ok in recovery mode too.
So, I will start again this afternoon the MTD update..
Many thx, I think this time I'm in a good way to success the update
I will give you news...
Mtd certainly works with cwm 5.0.2.0 so you shouldn't have any problems.
sent from my wilderbeast:buzz
Finally, yesterday, I started all since the beginning:
downloaded again the files, installed CM7.1.0.1, followed the described procedure for MTD, and it's ok, I have the Power of ... my wildfire
Again, thx for your help, and I don't forget to thank 3xeno for the guide
Same problem with Custom MTD Partitions
I have flash the boot and recovery files. I have made a nandroid backup i restore it. The mtd file looks like : mtd 170 22 . The rom memory is 512 /system & /cache partitions have only 192 mb. Memory for my applications is only 274 mb. In "About Phone" says i have 118/310 (free/avail).Where it's manager of application i have 245 used and 29 free.I should have 55 mb free.. bot no. Rest of my memory to 512 where it is? Should i delete the nandroid backup? Danke!
amNezic# said:
I have flash the boot and recovery files. I have made a nandroid backup i restore it. The mtd file looks like : mtd 170 22 . The rom memory is 512 /system & /cache partitions have only 192 mb. Memory for my applications is only 274 mb. In "About Phone" says i have 118/310 (free/avail).Where it's manager of application i have 245 used and 29 free.I should have 55 mb free.. bot no. Rest of my memory to 512 where it is? Should i delete the nandroid backup? Danke!
Click to expand...
Click to collapse
Its 512MB and not 512MIB/MO. Hence, the actual usable capacity is actually 483MB instead of 512MB (If I am not mistaken). (The analogy is similar to any flash drive / hard disk you buy - the actual formatted capacity is lower than the rated capacity)
I'm currently running DINC2HD, and was wondering how boot manager works exactly. I'm going to be camping on the 10th, and I'm not sure if I'll have a reliable charging source. I was planning on running MIUI while I was gone. I don't wanna have to restore a backup and take the extra time for that. Can someone please tell me exactly how boot manager works??
Sent from my DINC2HD
if its anything like a multi-boot pc, it creates separate partitions on your card and saves each each install there and inside each partition is all the apps and whatnot, just like a regular install of a ROM is, but that's just me guessing, i don't have the app seeing as i usually stick to just one rom lol
digitalsynner85 said:
if its anything like a multi-boot pc, it creates separate partitions on your card and saves each each install there and inside each partition is all the apps and whatnot, just like a regular install of a ROM is, but that's just me guessing, i don't have the app seeing as i usually stick to just one rom lol
Click to expand...
Click to collapse
I usually do too, but like I said, I'm gonna be camping, and I'm not sure when/where I'll be able to charge, so I was gonna use a ROM I KNOW has amazing battery life.
When installing in BM, do I need to wipe and all that stuff, or is that only if I'm overwriting a slot?
tylerlawhon said:
When installing in BM, do I need to wipe and all that stuff, or is that only if I'm overwriting a slot?
Click to expand...
Click to collapse
Boot manager itself is just an app like any other, you don't need to wipe anything.
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of it's own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, etc. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flashable backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
ChrisDDD said:
Boot manager itself is just an app like any other, you don't need to wipe anything.
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of it's own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, etc. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flashable backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So, you're saying in theory I should be able to click install zip, find MIUI and without clicking any of the wipe options I should be able to make a usable MIUI setup that I can go back and forth to?
tylerlawhon said:
So, you're saying in theory I should be able to click install zip, find MIUI and without clicking any of the wipe options I should be able to make a usable MIUI setup that I can go back and forth to?
Click to expand...
Click to collapse
I think it's recommended that you wipe all three images when you initially install a rom, but that's the 3 images Boot Manger creates. I was just making the point that you don't need to wipe anything on your phone's currently installed rom.
But yea, after that, Miui should install and run just fine. You will need to install GApps to get the market on MIUI, since Boot Manager needs to install itself on each new rom you instal. This is so you can manage and reboot to other roms from roms installed through it. After that, you should be able to reboot back and forth at will.
I never had to install g-apps on MIUI before.... is that a recent thing?
Also, what Ext type should I choose? Ext4, or Ext2?
tylerlawhon said:
I never had to install g-apps on MIUI before.... is that a recent thing?
Also, what Ext type should I choose? Ext4, or Ext2?
Click to expand...
Click to collapse
Sorry, I was thinking about CM7, which doesn't include with the market app.
I've always installed as Ext2... never had much luck with 4.
I tried Boot manager while running CM7 and I was able to install it but got a force close when I open the app, I also try it with MIK's Inc2 HD 3D rom and didn't work either.
Using TWRP 2.6.3.0, I'm unable to wipe data. Every time I try, I get
"wiping data without wiping /data/media
E: error opening '/data/lost+found'
done."
I excluded the nonessential bits, if anyone wants a full log (something something partition details), I can make one.
I using ES File Explorer with root explorer on, I checked out /data and found two lost+found folders, which I think is causing my issue. I've tried deleting just one, but a second one is automatically generated. If I delete them both, then they're automatically recreated as well. If I delete them both and then remake one immediately after, another one will be remade.
I also checked the rest of the /data folder, and I did not find any lost+found files, so I'm pretty sure it's just the folders messing things up
I checked this thread, but I didn't find anything useful
http://forum.xda-developers.com/showthread.php?p=39497772
I ended up here after I accidentally wiped my internal storage with TWRP. I went from a 4.3 AOSP rom to 4.1.2 stock (HD RLS16). I wiped the 4.3 rom, but I think I accidentally wiped internal storage then as well, or maybe something was messed up with TWRP because the storage folder for 4.3 isn't in data/media (or at least not for the rom I was using). After that I used hyperdrive, which was super buggy with Gapps and didn't work at all. After adding an account, everything kept force closing, and things were extremely slow and took minutes to open, even after removing the account and wiping cache+dalvik.
I thought it had to do with the rom, so I went and wiped stuff, then went to CM 10.1.3 stable, but that didn't boot at all, so I tried wiping again and going to liquidsmooth 2.9, which is where my problems started again. I attempted to wipe again and go back to cm10.1.3. The wipe failed, but cm10.1.3 worked.
any ideas on how I can fix this? I was unable to find help on google.
xxkid123 said:
Using TWRP 2.6.3.0, I'm unable to wipe data. Every time I try, I get
"wiping data without wiping /data/media
E: error opening '/data/lost+found'
done."
I excluded the nonessential bits, if anyone wants a full log (something something partition details), I can make one.
I using ES File Explorer with root explorer on, I checked out /data and found two lost+found folders, which I think is causing my issue. I've tried deleting just one, but a second one is automatically generated. If I delete them both, then they're automatically recreated as well. If I delete them both and then remake one immediately after, another one will be remade.
I also checked the rest of the /data folder, and I did not find any lost+found files, so I'm pretty sure it's just the folders messing things up
I checked this thread, but I didn't find anything useful
http://forum.xda-developers.com/showthread.php?p=39497772
I ended up here after I accidentally wiped my internal storage with TWRP. I went from a 4.3 AOSP rom to 4.1.2 stock (HD RLS16). I wiped the 4.3 rom, but I think I accidentally wiped internal storage then as well, or maybe something was messed up with TWRP because the storage folder for 4.3 isn't in data/media (or at least not for the rom I was using). After that I used hyperdrive, which was super buggy with Gapps and didn't work at all. After adding an account, everything kept force closing, and things were extremely slow and took minutes to open, even after removing the account and wiping cache+dalvik.
I thought it had to do with the rom, so I went and wiped stuff, then went to CM 10.1.3 stable, but that didn't boot at all, so I tried wiping again and going to liquidsmooth 2.9, which is where my problems started again. I attempted to wipe again and go back to cm10.1.3. The wipe failed, but cm10.1.3 worked.
any ideas on how I can fix this? I was unable to find help on google.
Click to expand...
Click to collapse
I would flash back to stock in Odin and root again
xxkid123 said:
Using TWRP 2.6.3.0, I'm unable to wipe data. Every time I try, I get
"wiping data without wiping /data/media
E: error opening '/data/lost+found'
done."
I excluded the nonessential bits, if anyone wants a full log (something something partition details), I can make one.
I using ES File Explorer with root explorer on, I checked out /data and found two lost+found folders, which I think is causing my issue. I've tried deleting just one, but a second one is automatically generated. If I delete them both, then they're automatically recreated as well. If I delete them both and then remake one immediately after, another one will be remade.
I also checked the rest of the /data folder, and I did not find any lost+found files, so I'm pretty sure it's just the folders messing things up
I checked this thread, but I didn't find anything useful
http://forum.xda-developers.com/showthread.php?p=39497772
I ended up here after I accidentally wiped my internal storage with TWRP. I went from a 4.3 AOSP rom to 4.1.2 stock (HD RLS16). I wiped the 4.3 rom, but I think I accidentally wiped internal storage then as well, or maybe something was messed up with TWRP because the storage folder for 4.3 isn't in data/media (or at least not for the rom I was using). After that I used hyperdrive, which was super buggy with Gapps and didn't work at all. After adding an account, everything kept force closing, and things were extremely slow and took minutes to open, even after removing the account and wiping cache+dalvik.
I thought it had to do with the rom, so I went and wiped stuff, then went to CM 10.1.3 stable, but that didn't boot at all, so I tried wiping again and going to liquidsmooth 2.9, which is where my problems started again. I attempted to wipe again and go back to cm10.1.3. The wipe failed, but cm10.1.3 worked.
any ideas on how I can fix this? I was unable to find help on google.
Click to expand...
Click to collapse
Anytime you get that error format data (the one where you type yes) the folder gets corrupted and a format fixes it.
Sent from my SGH-I747 using xda app-developers app
Im getting the same E:Error opening '/data/lost+found' im my twrp 2.6.3.1 after flashing Official CM11 nightly dec 12.
So now my recovery is very messed up, i cant properly wipe or restore nandroid with ease anymore, did you by any chance find a solution to fixing this issue?
Mystikalrush said:
Im getting the same E:Error opening '/data/lost+found' im my twrp 2.6.3.1 after flashing Official CM11 nightly dec 12.
So now my recovery is very messed up, i cant properly wipe or restore nandroid with ease anymore, did you by any chance find a solution to fixing this issue?
Click to expand...
Click to collapse
This has happened to me twice and the only solution i have found was to wipe internal storage. unfortunately i wasnt able to backup my internal storage before wiping so eveything i had on my phone was erased. Everything in your external is safe you dont have to worry but if you had important files or anything that you wouldnt erase on your internal storage then that is very unfortunate.
As for me, i now backup everything maybe like once a month or so, just in case something like this happens again.
Its happened to me also and I could not resolve it without the wipe, that was the only viable solution that worked for me.
Sent from my SGH-I747M using Tapatalk
Although if you're using twrp I just found out you can still save some of your precious files.
How? Simple
You can go into recovery and into the file manager. I think it's in settings or advanced I'm not sure. But I know that is built into twrp. So then just go into your internal storage and select the files and move them to the external storage.
If it's your first time using the file manager then you'll have to get used to it because it's not 100% noob friendly
And remember the bigger the file the longer it'll take to move so just be patient.
Use AromaFM!
search bar will serve you..
KorGuy123 said:
Anytime you get that error format data (the one where you type yes) the folder gets corrupted and a format fixes it.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thank you very much, saved my life today!
Can i get some help please. I cant format data via TWRP, it says "E: unable to wipe data, unknow fle system, auto, unable to format to remove encryption". I did not put any encryption. What to do?
Have you tried using different versions of TWRP to wipe?
I rooted my phone and installed the stock detoxed Rom (I'll find the link to the Rom later), but ever since my phone shows I have very little internal memory and isn't using my internal card for my apps so I can only have about 5 to 10 apps installed at a time depending on the size of the apps.
I tried the lucky patcher and it didnt fix it.
Any suggestions would be appreciated. I tried a different rom and had the same problem
The phone is showing I only have 760mb of application space
What JB version rom are you running? and what recovery version?, might be the corruption bug with wrong recovery.
Another thing to check is with a root enabled browser, check the /LOST.DIR in /storage/sdcard0/ and /storage/sdcard1/
if there is files in the LOST.DIR folder delete them, it will return the lost space, but if there is lots of files in the LOST.DIR is most likely a sign of corruption.
I had an issue similar to this a week or two ago with stock cm10.2 nightly. Full wipe of system and data fixed it for me.
hmm well this week has been a nighmare lol.
I tried installing a different ROM and it didnt help the space issue, and it would freeze then reboot every time i went into the gallery. So then i cleaned everything again and reinstalled my old ROM because I was at work i didnt have much options at the time.
Then i was having random reboots, and then endless boot loop, and all kinds of random problems, not being able to get any service... ect.
So now im home im trying to reload stock with Kies and i got an error. So im about to put it in download mode and try to connect to kies again and see what happens, worst case looks like ill be using odin.
Im thinking its a problem with TWRP.... idk whats going on.
Heres one ROM i tried and i couldnt connect to my service provider.
http://forum.xda-developers.com/showthread.php?t=2344942
This is the ROM that would freeze and reboot when i went to the gallery
http://forum.xda-developers.com/showthread.php?t=2481542
And heres the one i have been running for a while and default back to... what im running right now until i can get it back to stock
http://forum.xda-developers.com/showthread.php?t=2226860
just reset everything using odin and its having the same problems... Completely stock now, not rooted at all.
Low space, (this is completely stock i have zero apps isntalled besides factory)
If i go to application manager it says 2.00 GB used 0.00 free space.
If i go to Storage it says total space 1.97gb, applications 153mb. available space 1.88mb
Idk i think i may have caught a virus...
Im going to move all my pictures and music off of it and format everything i can.
If you are still using an older recovery, I could bet that you have the corruption bug, when using any JB 4.3 based rom, such as the one you linked (United Basics) you must have a newer recovery or the chance of corruption is just a matter of time.
See this link for more info straight from TC: http://forum.xda-developers.com/showthread.php?t=2412652
I'd suggest either downloading their recovery if you like CWM or get TWRP v2.6.1.0 recovery and flash the *.tar while in download mode with Odin, after you have a 4.3 compatible recovery then do a complete wipe (Advanced), including System and internal SD card (first copy pics/movies/music etc to computer), then copy back the rom you want to use and flash it along with the proper gapps, the proper gapps version/date will be based upon which rom you flash, check here if not sure: http://wiki.rootzwiki.com/Google_Apps
I'm also having this problem with storage space.
I'm on CM10.2, and have the 4.3 compatible TWRP installed. Prior to installing Cm 10.2 (a few weeks ago), I fully wiped /data /system /cache /dalvik, and wiped internal storage. I'm not able to update any apps, as I'm using 700MB for apps, but less than 200MB available out of the 1300MB that should be free.
I've done everything I should have, by fully wiping on a 4.3 compatible TWRP. Going to check for Lost.dir files now.
---------- Post added at 04:42 PM ---------- Previous post was at 04:22 PM ----------
bechard said:
I'm also having this problem with storage space.
I'm on CM10.2, and have the 4.3 compatible TWRP installed. Prior to installing Cm 10.2 (a few weeks ago), I fully wiped /data /system /cache /dalvik, and wiped internal storage. I'm not able to update any apps, as I'm using 700MB for apps, but less than 200MB available out of the 1300MB that should be free.
I've done everything I should have, by fully wiping on a 4.3 compatible TWRP. Going to check for Lost.dir files now.
Click to expand...
Click to collapse
Woo! 1.3GB free space recovered! My /data/lost+found was most of it. Hopefully it was a flashing glitch and not a sign of bad flash storage.
Woo! 1.3GB free space recovered! My /data/lost+found was most of it. Hopefully it was a flashing glitch and not a sign of bad flash storage.
Click to expand...
Click to collapse
I had to do the same thing when I upgraded my 2.3 stock rom to CM10.1.3. Either use ADB shell or a root enabled explorer to remove the contents within the lost+found folder:
Code:
sudo rm -f *
(WARNING! Make **SURE** you are WITHIN the lost+found folder BEFORE issuing this command).