Related
I have an unrevoked-forever (s-off) Incredible, running CM 6.0.2 (stable). I have been running an 8gb sd in, but recently I have been reaching the limits.... so I decided to upgrade it to 16gb.
I copied all the files from my 8gb to my PC, via phone USB. Then from my PC to a 16gb card, via card reader. When I unmounted the 8gb, and replaced it with the 16gb, it would not remount. I then started getting low memory warnings....but still could not get it to mount the SD card, old one or new one. So I rebooted and now I'm stuck in a boot loop, with either memory card, for some reason....
I tried a nandroid backup, and it says complete with one line saying "SD-ext.img not found- skipping...." then on reboot, it still goes into a boot loop.
Suggestions on what to try next are VERY welcome. I guess I should have not tried swapping the SD card while the phone was on?? I can of coarse boot into recovery, and I do have ClockworkMod 2.5.0.1.
Worse case scenerio, wipe? and run apply CM from SD card?
Why do people always get scared about the SD-ext error messages, where it's clearing data, formatting, or restoring backups. SD-ext is for apps2SD. The SD card partition for general storage is called sdcard.
With regards to your problem, I have no idea, Sorry.
SynbiosVyse said:
Why do people always get scared about the SD-ext error messages, where it's clearing data, formatting, or restoring backups. SD-ext is for apps2SD. The SD card partition for general storage is called sdcard.
With regards to your problem, I have no idea, Sorry.
Click to expand...
Click to collapse
I have no idea what SD-ext is for...I'm not "scared" of this error, I just want to get out of bootloop....if it's not related or important information, sorry....I assume I messed something related to the SD card....considering how/when this started happening....but of coarse I don't know exactly what I did, that's why I'm asking.
I don't get an "error" screen, I just get a boot loop. I don't even know where to begin to toubleshoot this....so thats what I am asking for...suggestions.
I thought that you assumed that error was the problem.
Does your phone still reboot loop when the sdcard is removed completely? You can try backing up the contents of the card onto your computer..then format it with FAT32 in windows. Try it with a completely empty card, but formatted as FAT32 of course.
If you're still having problems then if I were in your shoes I would resort to a factory reset, clear everything, and then start fresh (especially considering your nandroid backup did not work)
SynbiosVyse said:
I thought that you assumed that error was the problem.
Does your phone still reboot loop when the sdcard is removed completely? You can try backing up the contents of the card onto your computer..then format it with FAT32 in windows. Try it with a completely empty card, but formatted as FAT32 of course.
If you're still having problems then if I were in your shoes I would resort to a factory reset, clear everything, and then start fresh (especially considering your nandroid backup did not work)
Click to expand...
Click to collapse
The boot loop happens with, either card, and also with no SDcard in. I only get to the Cyanogen animation and it keeps looping......I will try formatting the cards on the PC and then pasting the SD card "copy/backup" from my initial try....
---if worse case----
I have never installed other roms, I have had relative success with CM....so I really don't know how to "wipe" and start fresh.
Are these steps close:
1. boot to recovery> ClockworkMod
2. select wipe data/factory reset
3. select wipe cache partition
4. select advanced> select wipe Dalvik cache?
5. install zip from SD card > select CM- 6.0.2
6. done?
Yes, those steps sound correct to me. That is your best shot.
The Incredible in general has reboot problems, for some reason it is very sensitive. I'm not really sure if you changing the SD card truly caused the problem or not, but it's worth reflashing the latest CM. I recommend 6.1 RC2
6.0.2 is quite old and it has a lot of problems, including force close mail client by default, a faulty radio interface layer that may cause reboots, and many, many other fixes have been implemented in 6.1 RC2 and the latest nightlies. Don't be discouraged that it is a release candidate..in reality it is much more stable than the 6.0.2 "stable".
SynbiosVyse said:
Yes, those steps sound correct to me. That is your best shot.
The Incredible in general has reboot problems, for some reason it is very sensitive. I'm not really sure if you changing the SD card truly caused the problem or not, but it's worth reflashing the latest CM. I recommend 6.1 RC2
6.0.2 is quite old and it has a lot of problems, including force close mail client by default, a faulty radio interface layer that may cause reboots, and many, many other fixes have been implemented in 6.1 RC2 and the latest nightlies. Don't be discouraged that it is a release candidate..in reality it is much more stable than the 6.0.2 "stable".
Click to expand...
Click to collapse
Well I downloaded a fresh 6.0.2 and 6.1 RC2 from Cyanogen....I followed the steps above to "wipe" and installed the 6.0.2....result= bootloop still
repeated steps to "wipe" again......selected to install 6.1 rc2......result= bootloop still
SO now I'm really at a loss. I figured with a wipe it would work....maybe my steps are wrong.....ANY suggestions now are welcome.
Do you know how to use advanced from the android ask. It can be used to figure out where your problems are.
Might be that the Dex cache is being created, but that only happened to me when flashing my own custom roms, not when changing SD cards.
Sent from my ADR6300 using XDA App
linuxmotion said:
Do you know how to use advanced from the android ask. It can be used to figure out where your problems are.
Might be that the Dex cache is being created, but that only happened to me when flashing my own custom roms, not when changing SD cards.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
No I do not know how to use the "advanced from android ask." But I am willing to learn if needed.....Is this the SDK tool? I believe I toyed with this when I first used the Unrevoked method to root....but thats been months and I don't mess with roms much. I started playing around with SDK a few minutes ago to familiarize myself....but idk.....
Is there a simple way to get some kind of log file? Can I load another recovery, like Amon_RA style type, which has some different options....but I don't know if it will help......Thanks for all suggestions thus far.
See I'm not exactly sure that the SD card was what caused the malfunction in the first place.
If you have an AMOLED incredible your 3G radio or battery may be beginning to fail...as I said before the Inc is very sensitive and tends to reboot a lot for stupid reasons.
You can certainly get a log if you use LogCat from ADB, but if you cant figure out exactly whats happening, then most likely you need a replacement.
You can unroot, turn S-ON, and put a stock RUU and see if you still get reboots (I'm willing to be that you will). But if you still get reboots completely stock, since you're stock you can go to verizon now and get a warranty replacement.
Quick review
- you unmounted the 8 Gb SD card, and removed it from the device while the device was still on, replaced it w/ the 16 Gb SD also while device still on?
- in the last working CM 6 ROM... were you using the SD card to cache memory or any other SD card usage tied to an AOSP ROM?
- what apps had you moved to SD card?
Absent all that, try and d/l a non AOSP ROM, for instance Virtuous, place it on your SD card in Recovery, and see if you can flash it.
Why? Solving for whether the device boots and will load a ROM at all - AOSP ROM's utilize the SD card more than Sense ROMs.
smtom said:
Quick review
- you unmounted the 8 Gb SD card, and removed it from the device while the device was still on, replaced it w/ the 16 Gb SD also while device still on?
Click to expand...
Click to collapse
Correct.
- in the last working CM 6 ROM... were you using the SD card to cache memory or any other SD card usage tied to an AOSP ROM?
Click to expand...
Click to collapse
I did use a rooted app to move things to the memory card, but I didn't see any benefits so I moved it back, at least I selected too, whether the program moved them back or not.....hmm...
- what apps had you moved to SD card?
Click to expand...
Click to collapse
you know I'm not sure I moved apps back. I know again I didn't see the benefit of apps/cache on the SD card, so I moved it back to phone....
------
Status as of 12/06/10 11:18am est.......Things I have done since last posts.
1. I have wiped numerous times via ClockworkMod. And tried CM 6.1rc2. Still got loop.
2. I installed Amon_RA recovery, wiped everything, formatted SD card through Amon, partioned SD card through Amon.....installed Cyan CM6.1 listed above, and phone sat loading at the initial screen "htc Incredible." Let it sit for 10+min....still nothing....
3. Tried to repeat step above...same results, now just initial screen, NO bootloop.
4. Installed ClockworkMod 2.5.0.5. Wiped. Install Virtuous 3.1.0. Recieved an error during install....."E:\" unable to read data...followed by a string of numbers and other info.....
5. Wiped.
6. Installed Hboot 92. (upgraded from 77)
7. Tried MIUI v0.12.3. Rom installed "successful." Rebooted and stuck on initial screen. been 5+ min as of now....
So NOW I am not getting a Bootloop....just a frozen screen. I can still get into recovery, so hopefully I still have options. Your insights or suggestions are the only thing keeping me trying ATM....I'm running out of options of my own.....
Well I still haven't got past initial boot screen with MIUI, even though it said installed correct during flash.....
SO I tried to wipe, and install Virtuous 3.1.0 again. got the same error...wrote it down this time:
E: Can't chown/mod /data/app (operation not permitted)
E: Failure at line 8: set_perm_recursive 1000 1000 0771 0644 DATA:app
Installation aborted.
I'm still at a loss, and taken any pointers or ideas. I may play around with other roms, but idk.
1. I tried Skyraid_333 and had the same results. Locked on initial white screen.
2. Wiped and tried a "stock" rom available from Virtuous.....http://www.virtuousrom.com/p/other-releases.html
It loaded and then it actually booted to the red eye droid (different from my original post which was the CyanMod boot anim)....yay....then it froze (eye stopped moving)....tried booting w/o SD card...same thing....
3. Wiped and decided to try Virtuous again. This time it loaded and installed "completely."
It booted again to the red eye animation....seemed to freeze, but I left it, and it finally started after 5+ min....I finally got a phone back.....
I do not know entirely what I did, in the process of loading all these roms. I do remember when I installed the "stock" rom, listed above, it had an install step which said installing "BOOT." (or something like that) I do not remember this listed step on the other rom installs...although they may do it and not list it....idk....
I have a feeling that the stock rom did something, but I don't know why a "wipe" does not reset everything, and why any rom wouldn't work....So I'm stuck back with HTC sense, due to the time I have been without a phone, I will live with it....I forgot how much I dislike this sense.......
Thanks to everyone who chimed in.
Congrats on you fixing your phone. I am still very new to this myself, but one of the first things I would have done would be install a stock rom again. It sounds like you lost or had some corrupt files which were fixed by going back to stock. If it were me I wouldn't be scared to wipe with a custom rom or nandroid backup, but thats just me.
i'm stuck with a similar problem: phone (dinc rooted, recovery CM 2.5.1.2, hboot .92) currently frozen on htc splash screen -
How it happened:
I was running MIUI 0.6 1.1.28.1, tried to re-format the SDcard to wipe it and start from scratch again. Did not nandroid beforehand (wiping SD) but pulled the 0.6 1.1.28.1 zip to my desktop. Tried formatting but phone wouldn't format it properly - wiped all info from SD, but no longer readable by phone or computer.
Used Mac disc utility to re-format and erase card to FAT32, still un-readable. Phone now only boots to splash screen, recovery works.
Brother has an un-rooted dinc so I grabbed his SD and mounted the card to the Mac via recovery, wrote onto it the MIUI rom I was previously using and did a full wipe (data, cache, davlik) and installed rom - rom installed correctly but still couldn't get past htc splash screen
Gave bro back his SD and tried mine again - got it to mount to the phone by partitioning through recovery, re-installed MIUI rom to my SD card and tried rebooting a number of times, still can't get past the splash screen (15+ mins)
Currently downloading virtuous "stock" rom as posted above and will try to wipe/ flash. It's a huge zip compared to the MIUI zip - maybe that's a good thing?
Here's to hoping.
Have tried flashing multiple versions of MIUI rom, packaged by n_i_x and warttack - no luck on either.
I just flashed the virtuous "stock" rom and got to the droid eye splash YES!! Mine may also be stuck in that screen though on the droid eye.
IT'S WORKING!!!!!!!!!!!!!!!
Can't even begin to say how relieved I am - I'm never getting rid of that magical virtuous zip.
So glad someone had gone though this before me.
AOSP interacts w/ SD
Handy information to know -
AOSP ROMs interact w/ the SD card quite a bit, whereas Sense ROMs not so much.
So, if a new SD and boot w/ AOSP, expect it to be wonky, particularly during boot.
hth
i dunno what caused it but mine has been doing this for about a month. Got my refurbished phone in today so HOPEFULLY that one will work better, but i dont really expect it, as this stupid boot loop issue seems to be a VERY common problem with inc's. I probably wont ever buy an HTC after this one, should have learned my lesson after the touch pro
anyway, even on stock rom, unrooted, with nothing extra, mine does this for no apparent reason
Please bare with me, as there's a lot to explain. I am in dire need for your help.
Starting off, my specs are as follows:
HTC Desire CDMA from U.S. Cellular
Rooted via Unrevoked (with unrevoked forever)
Current Recovery: ClockworkMod 2.5.0.9
Current ROM: CyanogenMod 6.1.0
Current SD: 8GB
The phone is barely over a week old. I rooted it last week, flashed Cyanogen, and customized everything. Well one thing I wished I had done before was partition a part of my SD to allow for more internal phone space. Even with
Cyanogen's FroYo (2.2.1) capability to move apps to the SD, I kept running a thin line on low memory. This is because, as most of you know, not the entire app is moved. I was faced with the decision of removing apps that I frequently used, or look for other storage solutions.
I found out that there was a way to make the phone think it has extra memory by partitioning a part of your MicroSD card to an Ext3. I researched how to do this with the tools I already had available (this being ROM Manager & ClockworkMod). I first tried ClockworkMod's recovery, which give me the option to partition the SD. I selected 512MB for the size (it's more than enough for me) and a swap size of 0. It completes, and I reboot the phone. I checked the internal storage space, and it's still low (< 15MB). Upon more research, I found that it may have only been an Ext2, and not Ext3. Upon plugging my phone back into the USB/Computer, I noticed the overall size for my MicroSD went from 7.5x GB to 6.9x GB. If the partition didn't work like I wanted, I wanted my space back.
So for hours I scour the forums with nothing helpful in return. I tried Partition Magic to try and merge the partition back to my original card, but it couldn't see it. It only saw a SD card that was 6.9x GB. So further research showed me that ClockworkMod was pretty bad at partitioning the SD card to Ext3, and everyone suggested AmonRa. I found a version of AmonRa that was designed for the HTC Desire. I placed the .img file on the root of my SD card and opened up ROM Manager. The option to "Flash Alternate Recovery" was greyed out, despite the fact that the image was on my SD Card (which was mounted; USB Storage for the PC was turned OFF). So further reading said I needed the premium version of Rom manager. I bought it, installed it, and re-fired it up. The option is still greyed out.
Frustrated, I look for alternate methods. I found one that recommended Terminal and the flash_image script.
I tried doing this with the AmonRa recovery image (which I renamed to recovery.img on my SD card). I rebooted into recovery, but instead of ClockworkMod or AmonRa appearing, I just got the HTC logo with the white
background where it would ultimately freeze. I performed a hard reset and tried again. Same thing. I reboot, went into ROM Manager and tried flashing ClockworkMod 2.5.0.9. It said it installed, so I reboot into recovery. Same HTC Logo freeze.
Freaking out, I tried other solutions, involving one where I placed a script on my SDcard. From there, I would go into Terminal and type the following:
su
sh /sdcard/FR-flashRec-v03.txt
And after the 2nd or 3rd time trying this, I reboot my phone, and instead of going into recovery, it dumps me back into Fastboot. Every time I tried selecting Recovery from bootloader, it would take me to Fastboot. I'm freaking out about now. So I fired up Unrevoked, the tool I used to originally root my phone. After the 2nd attempt, it successfully flashed ClockworkMod back to my phone.
Relieved but still unsolved, I continue to look for a reason why I'm not able to flash a different recovery image. Then I found a thread which dates back to June 2010 and applied to the CyanogenMod 5.0.x Eclair build. There was a disclaimer that read:
DO NOT USE ROM MANAGER TO FLASH YOUR RECOVERY.
DO NOT USE flash_image SCRIPT TO FLASH YOUR RECOVERY IN THE LIVE SYSTEM.
So I figured the problem was with my current ROM. Sure, that referred to CyM 5.0.x, and I'm running 6.1, but there was no documentation saying that the issue had been fixed, and there weren't any other threads regarding my issue.
Not wanting to take a risk losing my current recovery, I restored a backup from my stock ROM I received from U.S. Cellular. I installed ROM Manager and tried to flash the recovery image via the "Flash Alternate Recovery". The option was once again greyed out. I bought premium again and still, the option is still greyed out.
Running out of ideas, I restored my CyanogenMod state I made before I did any changes. And this is where I am.
I'm running out of internal phone space rapidly.
[*]I don't know how to restore the partition I made to get my SD storage space back (in fact, since I made that partition, it's been slower).
[*]I don't know how I can flash AmonRa, or if it's even possible with CyanogenMod.
[*]I don't know how to use ADB shell.
I found a site that has a collection of AmonRa images, and for the Desire, they have the following: recovery-RA-desire-v2.0.0-AW.img, recovery-RA-desire-v2.0.0-CM.img, and finally recovery-RA-desire-v2.0.0.img. I don't know which one I need to install for my HTC Desire CDMA.
If you've made it through this entire thread. Thank you. I really need some answers, and I don't know where else to look or to even ask. Can you please help me?
First of all making a ext partition won't magically provide more space, there is more behind it. See the second post in this thread under 'Still low storage for apps'.
And the partition made with rom manager should be fine however if you want something else use Gparted (can run of a linux live cd so no need to install anything)
For the restoring of the partition also use Gparted.
Not 100% sure but i believe that with unrevoked you can flash a alternative recovery image even if you are already rooted, but if you use Gparted there is no real reason for doing so.
For adb there are enough tutorials.
Hmm, many of these AmonRa releases are designed for HTC Desire GSM. Will these releases also work for CDMA devices?
Also, GParted will not work under Windows 7, and I don't use linux. All these other partitioning programs cannot detect the missing 1GB from my 8GB MicroSD. I have no idea how to restore it.
My HTC Desire started misbehaving earlier in the year, it would crash and reboot, when it rebooted the SDCard would not be detected, a few days later, it would crash again and the SDCard would re-appear.
When it was visible, the SDCard would work ok a long as you didn't use it much, listening to music for any length of time would cause it to fail again. The SDCard will stop working a day or so after boot, all by itself without any use.
Sometimes it was visible but apparently needed formatting (which isn't true). The card tests fine in computers and I've used two different cards with the same issues.
I figure the issue is with the SDCard controller, although I'd like to get other's views on what the issue might be. I'd like to repair the phone by replacing whatever is necessary, but my knowledge of the hardware build is non-existant right now, could anyone advise where I might start?
dnel said:
The card tests fine in computers and I've used two different cards with the same issues.
Click to expand...
Click to collapse
Do the cards misbehave in recovery also? Have you tried a different rom ?
handy5876 said:
Do the cards misbehave in recovery also? Have you tried a different rom ?
Click to expand...
Click to collapse
Yes, when the sdcard disappears completely CWM also cannot mount the card.
When the card stops being readable, reboot generally revives it for a little while so hard to tell if CWM is affected by this or not.
I've wiped and reloaded the rom, recently I successfully updated to the latest Cyanogenmod 7 but the procedure is too risky if I lose the card while flashing so I wouldn't do it again.
A link for HTC Desire disassembly if you are up to it
http://www.formymobile.co.uk/desiredisassembly.php
Never opened my desire. More details in this Nexus one teardown also http://www.ifixit.com/Teardown/Nexus-One-Teardown/1654/2
dnel said:
Yes, when the sdcard disappears completely CWM also cannot mount the card.
When the card stops being readable, reboot generally revives it for a little while so hard to tell if CWM is affected by this or not.
I/QUOTE]
check the contacts first before doing a disassembly . it might just need a spray contact cleaner on both card and phone.
Click to expand...
Click to collapse
or you could try this before disassembling your phone http://forum.xda-developers.com/showthread.php?t=691187
it might be an "usb brick".
Thanks for the replies, I decided to try a few things before I took a screw-driver to my phone and so far it's good news but I'm not sure why...
I remembered that a couple of weeks before the SDCard failed, I used alpharev to s-off and flash hboot to CM7r2. So a few days ago I reverted this change.
I re-flashed the stock hboot and then switched from Cyanogen 7.2.0.1 to the last MIUI gingerbread. This process nearly bricked my phone, at one point it wouldn't even boot into recovery and then the 4GB SDcard I was last using in the phone failed completely, but interestingly it failed while it was in my computer and not my phone. After this I switched to a 32GB class 10 SDCard that was in my phone when the SDCard originally started to misbehave so although the 4GB SDCard failed I don't think this is related to the problem because the problem presents with both cards.
After I flashed stock hboot and loaded MIUI, the problem hasn't presented itself, not once.
I then flashed back to CM7r2 and reloaded MIUI and the SDcard worked but I couldn't install any market apps, complaining of a lack of storage. This is with nothing in /data except for the dalvik cache and 250MB of "free space".
I then flashed to the Data++ hboot and reloaded MIUI and the market now works and the SDcard is working.
I don't know how the partition table on the MTD may have caused my SDCard to fail, the best I can guess is there is some bad memory area which when CM7r2 is loaded, corrupts an important system memory area.
I'm leaving it stable right now and will see whether the problem arises again before making further changes. I would be interested to know if there's any fsck-like apps that I could used to check the MTD for errors?
Hi
I have a Desire GSM rooted and S-ON RA-Desire v2.0.1 stock HBOOT Ext 4 1Gb latest radio ends in 23
Have been running on a custom rom for over a year now and want to install the latest copy of the same rom. The md5sum is identical for the zip file to the source.
Booted into recovery wiped all data, cache and then devlik-cache.
I have turned off signature verification and then selected my rom zip on SD card.
Installed the rom rather there were no errors and it took about 20 seconds (seemed too fast).
Next in recovery I did a reboot.
Now the screen went white with green HTC logo in centre for about 1 minute then after this a black screen with android written logo for about another 2 minutes.
Eventually phone boots into rom but it is not the new rom it is the exact same old rom.
I can see from applications listed that I am still super user so not lost root.
In settings software information everything is listed identical to what I had before.
The contents of the zip files are different so it is not the same rom being flashed.
Choosen rom is
[ROM][Cool Sense][5 April]Cool Droid v3|2.3.4|FASTEST|Data++/Stock (currently have Icecream sense v2 installed which is an earlier version of the same rom)
I did not install the alignment zip as I had already setup to use an earlier rom version and ext4.
What have I done wrong in trying to install my choosen rom please?
I feel like I must have missed something.
Not sure which recovery you have, with 4ext I boot to recover, format everything except sd then install zip and it seems to work, obviously everything then needs reinstalling from the backup you'll have made
Sent from my HTC Desire using Tapatalk 2
Hi
Unrevoked 3, as I have one of those odd PVT4 Desire phones 4000 erase size using RA Recovery. (something like that sorry if technical references are not super clear).
I use Titatium backup so reinstalling wont take long just need the ROM to install.
This is a fast glitch free rom using sense so I do not want to try a different rom as it gave me a year without trouble. Only doing this to start again with the space issue needing a refresh.
I have cleared delivk cache again and flashed my original v2 rom and that worked showing expected progress reports.
So I thought would try flashing the new v3 rom, and see if I got any joy this time.
Still no joy, it looks like it starts as two lines appear then it says complete with no obvious error.
So I reflashed the original v2 rom again and will go with that as I need a phone more then I need to play.
Odd.
Maybe the new v3 rom needs sOFF but as far as I could read it does not.
Even installing the previous rom things are still not right.
The apps that normally come with the rom are not installed such as Demon controller, No adds and Busy Box. I can see that they are in the zip file they are just not been added.
I can manually install Busy Box from the market so I know it is not a permission thing.
Titatium Backup is seeing my Ext4 partion (it calls it an ap2sd but it is showing) so I don't think there is a problem with my SD car arrangement.
I stupidly do not have a nandroid of the previous install I can restore.
So any ideas please why the previously working and installed rom is not reinstalling fully with all it's built in apps?
Anything I could try please?
Looks like I have identified the problem, my SD card is flakey and Gparted reports sick partion table that wont fix so the Ext4 partion was not been seen which is probably why the install failed and the apps were not installing.
New Sd card will be ordered and then start again.
Thankfully I dod have an uptodate SD card backup.
Phone is working just as a phone for the next few days.
These micro SD cards do not last long at this rate I get 1 year from them as this will be my third ordered.
Go to S-OFF, is better and mandatory for a lot of rom.
New card and more fiddle work with Gparted and now waiting for setup to complete as old v2 rom is installed. It works fast and is smooth plus has HTCsense so I can keep my sync capability so will be staying with it so I can live without S-OFF
Gparted when I followd the recommendations I kept getting a corrupt card on my phone so this is what worked for me.
Format card on phone
Then put card into usb card reader and place in PC
Reboot PC onto Gparted CD
Select SD card and then I resized the fat32 partion already there and then added a new EXT4 partion.
This worked for me.
Dump gparted, format the card through 4ext recovery
Sent from my HTC Desire using Tapatalk 2
I own a Galaxy Tab PRO 10.1" Wifi (SM-T520).
I have the stock ROM, rooted and with TWRP. And SDfix...
I have tried fat32 and ext4 on MicroSD, and without MicroSD. No difference.
I cannot boot any custom rom (Stuck at Samsung logo). Sometimes when I try to install a rom, it fails, or reboots TWRP.
I also encountered problem when trying to restore a nandroid. No DATA partition can be written to, restore fails. (after reboot recovery, its no problem to restore)
Angry Birds Epic does not work. It stops at "Loading Levels", and sometimes it fails to start, and says its not installed.
Spotify says that that it cannot be used because it has no storage.
I can access the partitions, but they are not writable. A reboot is getting the internal/external SD to be writabe again.
So, what is the problem with the partitions on TabPRO? or is it the Samsung android rom thats the problem?
Can it be fixed?
Regards,
-Exlo
Try installing FolderMount from the PlayStore. It can detect and fix issues with your partitions. You just need to run it, then reboot. I seem to get issues writing to my data partition after I install TWRP, on my SM-P900. FolderMount fixed it quickly and easily.
https://play.google.com/store/apps/details?id=com.devasque.fmount
Sent from my SM-P900 using Tapatalk
FolderMount did find an error, and fixed it, but same result
And it "fixed" the same problem as the SDfix app did.
But, I still made some progress. I managed to install a custom rom without error, and fully booted.
Team Freeze Rom installed fine. The rom is just under 800Mb. So i thought maybe it was some faulty memory sector on my tab.
Then I tried to flash GigaWatts ROM, and it failed. Same with ProPlus Rom.
When restoring my last nandroid, it fails when writing DATA partition.
Then I tried to restore my first nandroid, from "stock" rom, and it restored just fine.
First nandroid was from internal SD, and latest was from external SD. Made me wondering, so switched yet again another MicroSD, took a nandroid to it, and tried to restore. It fails again at DATA.
Then I tried t install GigaWatts ROM from internal SD, instead of external. Works without error.
Sooo.... I can flash custom ROM`s from Internal Memory, and restore from Internal Memory
Not from external SD.
Still, I do get internal/external SD dropouts, and getting "no space left/no memory to install on", which can be "fixed" by a reboot.(Still, it should`t be like this, and are quite annoying.
But, still no luck on getting past the "Loading Levels" on AngryBirds Epic
Where is the root of the problems? Faulty device? Android ROM? TWRP making trouble?
Please guide me if any logs should be provided to find out where the problems is, if i`m not the only one with these problems.
Regards,
Exlo
You can try flashing a stock ROM via Odin, and start from scratch. Factory Reset, Reroot, install twrp, etc. If you still can't write to /data properly, you may need to find a .PIT file and repartition your internal memory using Odin.
Sent from my SM-P900 using Tapatalk
I have had to reflash stock with Odin 4 times by now, and it has been the same pain every time.
I was hoping not to use re-partition, so I will wait and see if some new info will come by from other users, as I see there are more of the users that struggles with flashing custom rom. (Stuck at samsung logo, installation fails)
So, will hold off for a few days, and if no new info about partitions, rom flashing, low memory, sd cards not mounting correctly, etc, then I will try re-partition...
meanwile, I`ll investigate som more on my own, read overall the internet
Ok, so i have tried and failed, and learned something on the way
Ext SD is useless for flashing rom, nandroid, etc within TWRP. It does not mount partitions correctly.
If I make sure DATA partition is mounted in recovery, and only use Internal SD, everythin flashes, backups and restores just fine
(Mabye an issure with TWRP?)
SDfix, or FolderMount fixes write permissions to Ext SD in rom to use TitaniumBackup, games, downloads, etc.
Hopes this can help others in simular problems.
And thanks to all that have helped on the way
Regards,
-Exlo