Develop Bugs

Can't Get a Clean install.... Need some help

I don't know what is wrong with my phone after trying to flash SenseGinger v2.1.2 (didn't work) then reflashed CM 7 RC 3 with Mattedblues theme, Then flashed to RC 4. But each time, i can't get a clean install.
Things like Mattedblues theme icons are there when I didn't even flashed the theme Also my old wallpaper is there too when its not even on the SD card. Also now my phones constantly reboots after trying to log into google after fresh install.
I cleared Factory reset/ Cleared Cache/ Cleared Dalvik cache/ Even installed a Blank SD with only the rom.
WHat the hell is going on??? is there is secret cache somewhere i forgot to clear?
help

if you have wifi enable it will do a bootloop, so after a install do a reboot and that should stop...try to do a clean install of RC4, also if you backed up from google it will restore everything even wallpaper

ilostchild said:
if you have wifi enable it will do a bootloop, so after a install do a reboot and that should stop...try to do a clean install of RC4, also if you backed up from google it will restore everything even wallpaper
Click to expand...
Click to collapse
No no wifi no nothing. Tried it even without a google account login and its still goes crazy. I think somehow my past rom data doesn't get deleted, but i have no idea where they are hiding at....
Right now i am doing a full HTC signed rom install and going to see how it goes.

acer ring from flex reaper rom, questions

So i just flashed this rom. and everything worked fine including the ring. So after, i flashed diff mods and colors for the acer ring and also the fix (that was updated 6/2/12 i believe?
then after taking some screen shots. a pop up said,
system ui has stopped unexpecticly. or something like that.
and now the botton in the center is gone. So i cant use it at all.
Checked settings and it is enabled.
What should i do to fix? just reflash any acer ring or just the fix. or just flash the hole rom again?

trevor7428 said:
So i just flashed this rom. and everything worked fine including the ring. So after, i flashed diff mods and colors for the acer ring and also the fix (that was updated 6/2/12 i believe?
then after taking some screen shots. a pop up said,
system ui has stopped unexpecticly. or something like that.
and now the botton in the center is gone. So i cant use it at all.
Checked settings and it is enabled.
What should i do to fix? just reflash any acer ring or just the fix. or just flash the hole rom again?
Click to expand...
Click to collapse
Reboot into recovery then wipe cache, dalvik, fix permissions then reboot check the ring.
Tapatalked from my Galaxy S II.

pio_masaki said:
Reboot into recovery then wipe cache, dalvik, fix permissions then reboot check the ring.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
ya. i got it working again.
i get nervous going into recovery to flash something. i already bricked my transformer tf300 last week. but i got it back up and running. i just get scared. I'm gunna do a noob mistake and permently brick one of my devices.
but i didnt wipe anything. i rebooted, but it was still gone, went in settings unchecked, checked acer ring, rebooted again then it was back
btw do you no how to change bookmarks in acer ring. too ur google/ chrome bookmarks instead of the stock ones?

I haven't noticed a way it seems to only show the stock browser, import them into the stock browser should put them on the ring too. Also delete from the stock any you don't want.
Huge edit: forgot to mention, any changes like flashing rings or mods etc. Should be followed by cache and dalvik wipe, and maybe fix permissions. That way old info is wiped so the new info can settle instead of it finding new info where it expects old info...make sense?
Flashing is fine provided you know what you're doing. Don't just do random things and you'll be OK. Only flash for your device, and mods meant for your rom, like the stuff civato posts for his FR rom. Recovery is safe as long as you use common sense and caution. If you don't know what something does, don't use it. Google it or ask, better to wait and know then guess and brick.
Generally always safe to do is wipe cache dalvik fix permissions. No data loss that you see occurs.
Safe if something broke and won't boot BUT you lose apps and settings is wipe data/ factory reset, done with wipe cache and dalvik and maybe fix permissions.
Wiping system wipes out android and you must flash a new rom or restore to boot into the system, and is always done with cache dalvik and data.
I strongly advise against partitioning from recovery if possible. If you must partition your SD card then use a PC tool not recovery. Don't initiate sd-ext wipes directly, if it happens on resets that's fine just don't do it by itself. I only mention this because on my phone we had a string of bricks due to bad recovery mapping and it was nuking our loaders instead. Stick to what I said and you're safe in recovery and flashing. I'm sure others can chime in with more info on this too.
Tapatalked from my Galaxy S II.

pio_masaki said:
I haven't noticed a way it seems to only show the stock browser, import them into the stock browser should put them on the ring too. Also delete from the stock any you don't want.
Huge edit: forgot to mention, any changes like flashing rings or mods etc. Should be followed by cache and dalvik wipe, and maybe fix permissions. That way old info is wiped so the new info can settle instead of it finding new info where it expects old info...make sense?
Flashing is fine provided you know what you're doing. Don't just do random things and you'll be OK. Only flash for your device, and mods meant for your rom, like the stuff civato posts for his FR rom. Recovery is safe as long as you use common sense and caution. If you don't know what something does, don't use it. Google it or ask, better to wait and know then guess and brick.
Generally always safe to do is wipe cache dalvik fix permissions. No data loss that you see occurs.
Safe if something broke and won't boot BUT you lose apps and settings is wipe data/ factory reset, done with wipe cache and dalvik and maybe fix permissions.
Wiping system wipes out android and you must flash a new rom or restore to boot into the system, and is always done with cache dalvik and data.
I strongly advise against partitioning from recovery if possible. If you must partition your SD card then use a PC tool not recovery. Don't initiate sd-ext wipes directly, if it happens on resets that's fine just don't do it by itself. I only mention this because on my phone we had a string of bricks due to bad recovery mapping and it was nuking our loaders instead. Stick to what I said and you're safe in recovery and flashing. I'm sure others can chime in with more info on this too.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
i thanked you for your last post i feel i owe you more thanks than replies you made specifically to me lol. yah i had no idea you had to wipe cache and dalvik and fix permissions. when flashing the acer ring. i thought only do that on roms. thats probably why my acer ring was giving me problems. havn't had one problem with it since i wiped.
but just to clarify, do you wipe cache/ dalvik before or after you flash (Acer ring for example) or both?

trevor7428 said:
i thanked you for your last post i feel i owe you more thanks than replies you made specifically to me lol. yah i had no idea you had to wipe cache and dalvik and fix permissions. when flashing the acer ring. i thought only do that on roms. thats probably why my acer ring was giving me problems. havn't had one problem with it since i wiped.
but just to clarify, do you wipe cache/ dalvik before or after you flash (Acer ring for example) or both?
Click to expand...
Click to collapse
Either or. Some say before flashing some say after. I do before and after but that's just because of my scripts doing it before I flash (full rom). Something like the ring I flash then wipe cache dalvik fix perms after, so any of the mods etc that are not rom installs. Full rom installs I full wipe before then flash everything then clear cache and dalvik. I only fix perms if I get FCs.
Tapatalked from my Galaxy S II.

What could be causing bootloops on AT&T SGS3?

Hello,
I am from the i9300 forum. My GF has a SGH-i747. When she updated it to official Jelly bean using Kies, all seemed to go well but then when she booted up to her home screen the phone would reboot. It would continuously do this over and over again.
So we had to use KIES to do a complete format of the phone and reboot it. This deleted everything and made it factory brand new again. This is that option where you have to type in your serial number into kies to do the emergency firmware recovery.
Well a few months went by and today while my GF was using her phone it froze and rebooted. It is now stuck in the bootloop. I don't understand why this is happening. She doesn't have the phone rooted nor has she flashed anything on it. I'm not familiar with the SGH-i747 so I'm not sure if this is a common bug that has been addressed for fixed.
Please help, my GF needs her phone for work and she's a few miles away from me. Any help or advice would be appreciated.

SlimJ87D said:
Hello,
I am from the i9300 forum. My GF has a SGH-i747. When she updated it to official Jelly bean using Kies, all seemed to go well but then when she booted up to her home screen the phone would reboot. It would continuously do this over and over again.
So we had to use KIES to do a complete format of the phone and reboot it. This deleted everything and made it factory brand new again. This is that option where you have to type in your serial number into kies to do the emergency firmware recovery.
Well a few months went by and today while my GF was using her phone it froze and rebooted. It is now stuck in the bootloop. I don't understand why this is happening. She doesn't have the phone rooted nor has she flashed anything on it. I'm not familiar with the SGH-i747 so I'm not sure if this is a common bug that has been addressed for fixed.
Please help, my GF needs her phone for work and she's a few miles away from me. Any help or advice would be appreciated.
Click to expand...
Click to collapse
Might've to get in recovery (hold vol up+home+power), clear cache, reboot.
If that doesn't work, back in recovery and factory reset, then reboot.

BWolf56 said:
Might've to get in recovery (hold vol up+home+power), clear cache, reboot.
If that doesn't work, back in recovery and factory reset, then reboot.
Click to expand...
Click to collapse
Yeah, I tried all that. I managed to back up her data so maybe we can restore her apps and information later. But this is similar to last time. I had her factory reset it, wipe cache, wipe dalvick, format system and format data.
We then followed by restoring her backup but the problem still persist. I might need to flash the stock ROM.
Could Fix Permissions fix the problem? It seems that the phone boots up to the home screen. While loading files, something at this point is causing it to bootloop. It will freeze after a few seconds and then reboot and repeat the problem.
Something is definitely conflicting within the first 30 seconds of booting up to the home screen. Any ideas?

SlimJ87D said:
Yeah, I tried all that. I managed to back up her data so maybe we can restore her apps and information later. But this is similar to last time. I had her factory reset it, wipe cache, wipe dalvick, format system and format data.
We then followed by restoring her backup but the problem still persist. I might need to flash the stock ROM.
Click to expand...
Click to collapse
Debloated stock ROM might be a good idea. When restoring, you might be bringing the problem right back. It should be very minimal (the needed stuff that you can't simply re-download or re-setup) to avoid issues coming back.

BWolf56 said:
Debloated stock ROM might be a good idea. When restoring, you might be bringing the problem right back. It should be very minimal (the needed stuff that you can't simply re-download or re-setup) to avoid issues coming back.
Click to expand...
Click to collapse
I edited my post above about fixing permissions.
But this is very similar to what happen last time. I had wiped factory reset, wipe cache, wipe dalvick, format data and system, installed fresh new ROM and that boot looped too.
It took KIES emergency firmware recovery (where you have to type in your serial number) to fix the problem, but everything was deleted even the internal SD card.

SlimJ87D said:
I edited my post above about fixing permissions.
But this is very similar to what happen last time. I had wiped factory reset, wipe cache, wipe dalvick, format data and system, installed fresh new ROM and that boot looped too.
It took KIES emergency firmware recovery (where you have to type in your serial number) to fix the problem, but everything was deleted even the internal SD card.
Click to expand...
Click to collapse
I doubt fixing permissions will change much but could try it.
From the way you describe it, it sounds like a app or some bad data. Is she using a external SD? If so, try booting without it. If not, my guess is that there's a rogue app or something corrupted her data.

BWolf56 said:
I doubt fixing permissions will change much but could try it.
From the way you describe it, it sounds like a app or some bad data. Is she using a external SD? If so, try booting without it. If not, my guess is that there's a rogue app or something corrupted her data.
Click to expand...
Click to collapse
Thanks. Yes she's using an external SD card. I will have to get a hold of her phone and see what's going on. The first time it happened was because we upgraded to Jellybean. it happened right after so I don't think it was a rogue app. This time she just pulled her phone out of her purse and noticed it boot looping. Something sounds wrong with her phone... I think we might need to send it back for warranty repair.

Okay I need help. I have discovered the problem and it is the SUPERUSER app. When Superuser was updated it caused my GFs phone a boot loop.
Now that I put fresh rom and cleared everything her phone was working. But the moment I rooted the phone itboddly didn't come with SU, so upon installing SU nothing could access SU for some odd reason. So I found out you need a SU for Jelly Bean, upon installing this version of SU is when everything went to he'll and the same boot loop came back.
Sent from my GT-I9300 using xda app-developers app

SlimJ87D said:
Okay I need help. I have discovered the problem and it is the SUPERUSER app. When Superuser was updated it caused my GFs phone a boot loop.
Click to expand...
Click to collapse
What rooting method did you use to root your girlfriend's phone?
If I'm not wrong, most of the rooting method -- if not all -- for the SGH-i747 involve the SuperSU app instead of the Superuser app. And I believe most of the custom ROM, if you switched ROM, come with SuperSU pre-installed. If you try to install Superuser (without removing SuperSU), might that be the cause of your trouble?

Alexandre-P said:
What rooting method did you use to root your girlfriend's phone?
If I'm not wrong, most of the rooting method -- if not all -- for the SGH-i747 involve the SuperSU app instead of the Superuser app. And I believe most of the custom ROM, if you switched ROM, come with SuperSU pre-installed. If you try to install Superuser (without removing SuperSU), might that be the cause of your trouble?
Click to expand...
Click to collapse
Perhaps, I will try and fix the problem again. We just got back from a movie. Thank you.

if everything doesn't work
here's what you should do
first go look for AT&T 4.1.1 stock rom
download ODIN
go to recovery by vol up + power + home
clear cache, data and dalvik
flash stock rom thru odin.
that should fix soft brick

Camera only works w/o flash after rooting (several roms) only stock rom allows works

Hi Guys,
I was wondering if anyone could help me with a strange issue I have.
When I flash to stock root ROM my phone works fine, including my camera, however, when I flash to ANY custom ROM my camera only works when my flash is off. If I turn the flash on the camera attempts to take a picture and then freezes and I have to do a battery pull to get it back on.
I will through a curveball here and say that I have had extremely limited success (but success nonetheless) when I use my original OEM battery.
The flash itself works fine as I can use apps like flashlight no problem.
Oh and app's from the Play store work fine as well w/ flash on.
Anybody experience this before? I have searched and found nothing,
Thanks everyone.

How are you wiping before flashing? I recommend wipe data, cache, dalvik, format /system.
And by "any" ROMs do you mean 4.2 ROMs or both 4.1 and 4.2?

Well the stock ROM was 4.1.1.
The thing is I've had this problem for a long time now so it would be on both 4.1 and 4.2.
New development though, I just re- flashed to PKD ROM and the flash works intermittently. It seems when I take a picture if something closeup with flash it works but when the subject is far away the camera app just goes black.

So, about your wipe procedures...

xBeerdroiDx said:
So, about your wipe procedures...
Click to expand...
Click to collapse
Sorry,
So when I flash a ROM I wipe data/factory clear dalvik and clear cache.
I've done that from stock to custom.

The next time you flash, have everything backed up/saved to your sd card or pay and follow the wipe procedures I recommended above. It wipes the OS completely off, leaving you a completely blank slate for the new rom. Have your desired rom and gapps on your micro sd card

Blender7 said:
Sorry,
So when I flash a ROM I wipe data/factory clear dalvik and clear cache.
I've done that from stock to custom.
Click to expand...
Click to collapse
You forgot to format /system manually in mount/boot, that causes a lot of errors (it caused a bootloop issue when going from stock to Slim for me)

Help with Rebooting wiping storage

Hello everyone,
I would post this in the development thread but I can't since I am a ne user. Anyway..
I am currently on InFamous switching between the 2.4 TW version and the Google Edition v2.0.
My problem is every time I reboot my phone, it gets stuck on the Samsung Galaxy S4 boot image. Then when I go to recovery the Internal storage shows 0 MB available, and I can't fix permissions or wipe anything without having to format data first. The only way to boot my phone again, is to format data, wipe everything, and reinstall the ROM which is very annoying and time consuming.
PLEASE HELP!!
Thanks in advance
-Jesse

re: rebooting into Google Edition Rom
razorj7 said:
Hello everyone,
I would post this in the development thread but I can't since I am a ne user. Anyway..
I am currently on InFamous switching between the 2.4 TW version and the Google Edition v2.0.
My problem is every time I reboot my phone, it gets stuck on the Samsung Galaxy S4 boot image. Then when I go to recovery the Internal storage shows 0 MB available, and I can't fix permissions or wipe anything without having to format data first. The only way to boot my phone again, is to format data, wipe everything, and reinstall the ROM which is very annoying and time consuming.
PLEASE HELP!!
Thanks in advance
-Jesse
Click to expand...
Click to collapse
Have you tried this:
Before doing anything, be sure to back up the internal sdcard to a folder on your computer if you have anything you
want to save on the internal sdcard. Also be sure that the Google Edition zip file rom is on your "external" sdcard.
When the phone is flashed and ready to use go into settings>accounts tab>backup and reset>"Factory data reset".
Click on the factory data reset.
After doing that reboot into cwm or twrp which ever you are using and do a full wipe as you usually do but don't
forget to include "Factory reset".
Then flash the Google Edition rom as you normally have done and it should fix the problem you are having hopefully.
Good luck!

Misterjunky said:
Have you tried this:
Before doing anything, be sure to back up the internal sdcard to a folder on your computer if you have anything you
want to save on the internal sdcard. Also be sure that the Google Edition zip file rom is on your "external" sdcard.
When the phone is flashed and ready to use go into settings>accounts tab>backup and reset>"Factory data reset".
Click on the factory data reset.
After doing that reboot into cwm or twrp which ever you are using and do a full wipe as you usually do but don't
forget to include "Factory reset".
Then flash the Google Edition rom as you normally have done and it should fix the problem you are having hopefully.
Good luck!
Click to expand...
Click to collapse
Unfortunately, this did not work =(. Again, as soon s I reboot, I get stuck on the Samsung screen and have to pull out the battery. Then, in recovery my Internal storage has 0 MB aeven though the folders are empty.

razorj7 said:
Unfortunately, this did not work =(. Again, as soon s I reboot, I get stuck on the Samsung screen and have to pull out the battery. Then, in recovery my Internal storage has 0 MB aeven though the folders are empty.
Click to expand...
Click to collapse
Have you tried holding the power button, home key and the volume up key all at the same time to boot in recovery? If not do a battery pull and do it when turning the phone back on
Sent from my SGH-M919 using xda premium

razorj7 said:
Unfortunately, this did not work =(. Again, as soon s I reboot, I get stuck on the Samsung screen and have to pull out the battery. Then, in recovery my Internal storage has 0 MB aeven though the folders are empty.
Click to expand...
Click to collapse
If you already tried to Odin flash the STOCK rom and formatted your internal sdcard and you still find "0 MB"
in your internal storage then it must be a hardware issue and if I were you I would return/exchange the phone.
Good luck!

It's not a hardware issue. It's a bug in twrp. Whenever you do "format data" it corrupts the data partition. Use PhilZ Touch recovery. His recovery includes the fix. Try it.

teshxx said:
It's not a hardware issue. It's a bug in twrp. Whenever you do "format data" it corrupts the data partition. Use PhilZ Touch recovery. His recovery includes the fix. Try it.
Click to expand...
Click to collapse
Thanks, I'll try that. How do I get rid of the bug after writing the new recovery? Format data?
Thanks!

Hello, any progress please? I have exactly the same issue.

I found here http://forum.xda-developers.com/showthread.php?t=2265588&page=23 this solution:
I wanted to clean my internal SD card before flashing Omega ROM, so I used Format Data option from Wipe section in TWRP.
After that I lost almost two days trying to fix my phone. Flashed stock ROM, TWRP and Omega ROM endless times without success after that.
My phone became randomly unbootable on reboot or power on! It was stuck on i9505 logo that is shown before boot animation forever. It was same for both stock and Omega ROM, with or without external micro SD.
After endless tries, I figured out that my phone works fine if I do factory reset and wipe from original recovery. Worked fine before and after flashing TWRP.
I tired to Format Data from TWRP again and my phone again was stuck on boot.
So I did everything once more. Flashed stock, did factory reset and wipe from original recovery and then installed TWRP and in the end I flashed Omega without wiping anything.
Everything works just fine now and I will not try to use Format data option from TWRP on this device in near time! Please fix this.
First I used TWRP 2.5.0.1 and then 2.5.0.2, but it is same in both of them.
Click to expand...
Click to collapse
Now I'm downloading stock rom so I'll try it in next 2 hours.

bet you guys previously flashed a aosp rom, I could be wrong, but it sounds as if you did.

TheAxman said:
bet you guys previously flashed a aosp rom, I could be wrong, but it sounds as if you did.
Click to expand...
Click to collapse
It says so in the OP... going between TW and Google Edition 2.0.. Out of curiosity though, what difference would that make? I have flashed and have backups of two versions of TW and quite a few AOSP variants... I can move between them seamlessly and haven't encountered any such problems as the OP. I use TWRP as well.

It was TWRP problem. I have flashed the stock ROM with stock recovery. I have done full wipe and my phone works well again. This is bug in TWRP. Don't push "format data" button!