[Q] can NOT install apps from Play store - Bravo General

i used CM10, after i flashed a CM7 and it stuck in red logo M,then i flashed CM10 new buil, after that i can not install apps from Play store
and how can i flash CM7 from CM10. i have flash normal, but it stuck at red logo M

ensure you're using ext3, flash cm7, factory reset from stock recovery, test. maybe install cm7 again.
If that doesn't work then flash the sbf. Sbf to cm7 only takes about 15 minutes.
I had the exact cm10 to cm7 issue. I've posted all the ways I've seen to fix it. I sbf'd after trying different things for an hour.
As for market apps not installing, sort of had that issue too. It wouldn't install old versions when I went to My Apps>All. Had to search Play for the latest versions. Happened with hacked and regular market. No real fix, but a dalvik/cache wipe plus a market cache wipe and I haven't had that problem since.

EXT3 ?
is what ?

kevins547 said:
EXT3 ?
is what ?
Click to expand...
Click to collapse
Ext3 and ext4 are different Linux file systems. By default (stock kernel) our file systems were mounted as either ext3. Custom kernels give us support for mounting /data, /cache, /sd-ext as ext4 (and ntfs/ext4 support on /sdcard -- no 4gb file size limit). Data on ext4 file systems should be better protected in case the phone freezes and you have to pull the battery.
Needless to say, if you're not sure if you're on ext3 or 4 and you didn't mess with the option in the bootmenu, you're formatted as ext3.

Related

[Q] Why does my evo hate new ROMs now?

Thankfully I have nandroids of Vaelpak and Myn2.2. I have tried synergy, stock rooted GB, and I can't remember the other two over the last couple days. Each time, it goes like this:
-Nandroid (typically from Rom manager out of laziness)
-Reboot into recovery
-wipe data/cache/dalvik (last few times I did this over and over)
-install zip of new rom
-boot loop
-pull battery and restore backup
I use CM 3.0.0.5 and have also tried RA 2.2.2.
I'm s-off (unrevoked forever).
My SD card is the last thing I can think of. I think I have to format and partition it (I know there are guides here...just never needed it). I just don't get it, I went through a phase where I was doing a new ROM every couple days and never had this issue. Thoughts?
Download Amon Ra 2.3, use as PC36ING.zip. Back up SD card to desktop. Format SD card, then partition it. Look in General or Development for a guide. Mount as MS (mass storage) and transfer files back, leaving out Android.secure, Android, RosieScroll, GoSMS and similar temporary folders and files. Nandroid, wipe system, data, dalvik, cache, factory reset, boot, android.secure and SDext twice. I would suggest VR Superwipe too. Flash new ROM and tweaks (if it is 2.3 Sense probably keep stock kernel). Reboot, enjoy new ROM.
Clockworkmod and AmonRa backups are not compatible.
Sent from my PC36100 using XDA Premium App
tropicalbrit said:
Download Amon Ra 2.3, use as PC36ING.zip. Back up SD card to desktop. Format SD card, then partition it. Look in General or Development for a guide. Mount as MS (mass storage) and transfer files back, leaving out Android.secure, Android, RosieScroll, GoSMS and similar temporary folders and files. Nandroid, wipe system, data, dalvik, cache, factory reset, boot, android.secure and SDext twice. I would suggest VR Superwipe too. Flash new ROM and tweaks (if it is 2.3 Sense probably keep stock kernel). Reboot, enjoy new ROM.
Clockworkmod and AmonRa backups are not compatible.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Other than getting amon 2.3 and copying the files back this was pretty much my plan. I was only going to restore my astro app backups after I get things running again. I do have VR superwipe...never worked with CM on the version I have.
Any reason other than preference for amon 2.3 (maybe the VR superwipe)? If I leave the SD blank but partitioned and just put the ROM back on it, is that an ok idea? I have it backed up...don't know if I have to have the file structure there.
also downgrading CWM down to 2.6.0.1 helped me flash the newer files and scripts as well if you dont like Amon 2.3. Just a thought!
As someone else suggested, you should either use a 'superwipe' script (flashable in recovery) or include /system in your wipe routine.
I don't get why people never wipe /system. That's where the entire ROM lives. If you don't wipe /system, then you are just flashing all kinds of ROMs on top of each other and you end up with a jungle of files from various ROMs all mixed together.
You might get lucky, many ROM devs account for this and wipe your /system partition for you before flashing the new files.
github said:
As someone else suggested, you should either use a 'superwipe' script (flashable in recovery) or include /system in your wipe routine.
I don't get why people never wipe /system. That's where the entire ROM lives. If you don't wipe /system, then you are just flashing all kinds of ROMs on top of each other and you end up with a jungle of files from various ROMs all mixed together.
You might get lucky, many ROM devs account for this and wipe your /system partition for you before flashing the new files.
Click to expand...
Click to collapse
Agreed. I don't believe in superwipes. But I DO agree to manually wile each category, except SD Card, including system.
What worked for me..
I had to upgrade my HBOOT from:
EVO_HBoot_0.76.2000
to
EVO_HBoot_0.97.0000
to load the Synergy ROM.
No wipe, wipe utilities, formats or partitions would work. Upgrading the HBoot fixed the boot loop issue... for me.
2k6_tx_dad said:
I had to upgrade my HBOOT from:
EVO_HBoot_0.76.2000
to
EVO_HBoot_0.97.0000
to load the Synergy ROM.
No wipe, wipe utilities, formats or partitions would work. Upgrading the HBoot fixed the boot loop issue... for me.
Click to expand...
Click to collapse
I am on the older HBOOT also. I will try this if the SD wipe and partition fails me. It could be this since it's recent ROMS giving me issue.
To the wipe /system comments...I did that one time for sure. Not each.

Soft brick but common fixes not working

Hi,
I got my N7000 stuck in a bootloop. i did NOT flash any other rom not for the N7000. i was planning to flash the paranoidandroid rom and while shifting from ICS to GB [as it suggested] this happened.
I still have download and recovery modes. Flashing different stock roms is going through, and some custom kernels too [the yellow triangle appears after and the flash count increases]
trying to recovery from my nandroid backups gives the same result as the stock flashing
i.e. its goes through then get stuck in the boot screen before the animation [the screen which says Samsung Galaxy bla bla, the screen where the yellow triangle shows up to be clear]
What can i do now please??
thanks
edit: should i try to format /system /data /preload /emmc fom CWM recovery 5 becuase i can do that
So you flashed successfully gb? If you are on a gb and you have used a safe kernel to revert. Did you try to Wipe data and cache from recovery? Try it, it should bring you out of the boot loop.
Sent from my GT-N7000 using Tapatalk 2
Hi,
I don't know on what rom i am at the moment. it should be GB since i flashed SGN_XX_OXA_KJ1_FACTORYFS.tar
wiping data on the CWM worked before but this time it got stuck with out any progress in the blue bar for like 20min.
i was suggested to flash a wipe rom, but i dont know where to find one exactly
Like Baxos said. Try wipe all since you r at old GB. Its worked 4 for me. I've been at your stage then wipe all then root and flashed paranoidandroid. Try Get back to recovery and wipe all then reboot.
n7000 paranoid android v2
Will update to v3 when got time
wipe all = also formatting /system /data /preload /emmc fom CWM recovery 5?
because i did many of the restore to factory and clearing cache
the problem seems to be due to the fact that /data is not being wiped. the progress bar gets stuck and then reboots
any idea how i can wipe this partition?
Did you first install a safe gb kernel when you were on ics before downgrading the rom to gb? If not then you will have performed a wipe under ics kernel and it sounds like brick bug symptoms.
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
jan-sgs said:
the problem seems to be due to the fact that /data is not being wiped. the progress bar gets stuck and then reboots
any idea how i can wipe this partition?
Click to expand...
Click to collapse
Maybe your /data is corrupted. You can make a new /data with adb.
hi,
sorry for the late reply. i was busy with uni work
i will try the adb method.
thanks
all partitons were wiped on a different rom version.
the boot loop seems to be irreparable and i will have to send it abroad to get it fixed. hopefully i dont have any of my data on it

Ext4 on the Defy - breaks compatibilty with CWM/BM?

Hi,
I'm running Quarx2k's nightly (JB 4.1.2) and I'd like to try Ext4 on my Defy for various reasons, and I found followed a guide how to do it, it was basically something like this:
make backup
Boot into Boot Menu
Filesystem tools
Format with ext4
restore backup
This works fine. The phone boots and all - the problem is that I can no longer get into CWM or Boot Menu. So has anyone else tried ext4 on their Defy? Is it even possible?
Unfortunately I do not know any good workaround for the problem but it exists for some (not all) CM10 users.
It looks like some file system corruption. If you can use a terminal you can try to format data and cache to ext3 and restore nandroid backup of data. If not flashing of full sbf can repair it.
But can you get to bootmenu with pressing volume down while blue LED is on?
corrinti said:
Unfortunately I do not know any good workaround for the problem but it exists for some (not all) CM10 users.
It looks like some file system corruption. If you can use a terminal you can try to format data and cache to ext3 and restore nandroid backup of data. If not flashing of full sbf can repair it.
But can you get to bootmenu with pressing volume down while blue LED is on?
Click to expand...
Click to collapse
No, I can't get to neither bootmenu or CWM. However, it can be fixed by flashing sbf and starting from scratch. I have a few ideas which I will try in the next days, I'll post if I get it working.
I Tried the same procedure:
-Backup /system - /data
-Format Ext4
-Recover /system n' /data
If select reboot to recovery o bootmenu don't work ... but if i press voldown enters on Boot menu and CMW

Broken /data/ partition MB525

Hey everyone.
I'll go straight to my problem.
My /data partition is broken. I can't mount it, just like if 1GB of space magically disappeared. Roms normally boot and work, but I can't install any apps. I remember that it happened after flashing modified SBF with Epsylon's CM9. Can't help it with flashing other roms (but I haven't tried stock Froyo yet, do you think it could help?) and I can't simply wipe as /data doesn't mount. Any suggestions on restoring the original partition layout?
Try flash SBF .... during flashing SBF file the partitions are formated so it may help

[Q]Motorola Defy(MB525)/data and /cache partition problem (corrupted?)

I found my data and cache partition corrupted, and i dont know why.
I don't know anyway to fix it but do SBF flash (so far I am doing the THIRD SBF flash today, really frustrating)
[edit] why i think data and cache partition corrupted:
1. I couldn't mount data and cache and psd partition in recovery, but i can mount sdcard (and can't unmount system partition, is it supposed that system can't be unmounted?)
2. when i booted up the system(Kayant's AOKP), the size of internal memory is 0.0B, as shown in the settings->storage
[/edit]
Is there any to fix without doing SBF flash?
another question:
How to prevent it/any precaution so that the partition wont mess up? (I probably did some wrong thats why the partition was messed up, but I have no idea what I had done wrong)
here is what i did:
I had had this problem before so I do a SBF flash and the problem is gone.(I installed Kayant's AOKP rom -4.1jb)
Yesterday I decided to flash another rom (that was Quarx's cm10.1 rom) i did a nandroid backup first, then installed the rom and installed some apps, after that I installed Kayant's Slim rom(from the new aokp paradise), i found some bug and at last decide to return to Kayant's AOKP rom. I installed the 2nd Init boot menu(coz i did the nandroid backup with CWMrecovery, not TWRP), and problems came while restoring it. It failed to restore /data partition, I tried more times but couldn't fix this. So at last I turned to SBF flashing.
I flashed and rooted it with SuperOneClick and installed 2nd Init boot menu then install the AOKP rom(didn't restore the nandroid this time) then factory reset-ed it with stock recovery, and I found the /data and /cache partition messed up again(obviously the partition isn't messed up right after SBF flashing because i can install the 2nd Init app).
Now I am doing the third SBF flash.
You shouldn't have formatted data and cache with stock recovery. That was a mistake in your second attempt.
hotdog125 said:
You shouldn't have formatted data and cache with stock recovery. That was a mistake in your second attempt.
Click to expand...
Click to collapse
should I use aroma wiper and do a ext4 wipe if i am going to flash jb roms (like cm10/android 4.1 or higher), to prevent messing it up?
is it necessary to do wipe before or after install a new rom?
besides, any idea why the partition messed up/ failed to restore data when i do a nandroid restore, when i tried to restore with cwm recovery within 2nd Init boot menu installed on Kayant's Slim rom?
dicksonlok said:
besides, any idea why the partition messed up/ failed to restore data when i do a nandroid restore, when i tried to restore with cwm recovery within 2nd Init boot menu installed on Kayant's Slim rom?
Click to expand...
Click to collapse
Yes, format to ext4 for JB ROMs. Full wipe not necessary but recommended.
Start afresh, install the ROM and restore data.
Plus, you shouldn't have installed 2ndinit again. You should have installed dual recovery and tried.
Got same problem, data and cache partition corrupted.
Fortunately I have TWRP installed so I went to File System utility and format data and cache (I choose ext3).
Then restored previous backup and everything worked like before!

Categories

Resources