Related
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
Long story short, I was running out of space and was thinking of deleting the backups from titanium backup but I think I accidently clicked Delete all user data and app.
Right now I can only access Download mode and CWM, whenever I tried to wipe install zip from sdcard it reboots, when I try to wipe data/factory reset it reboots, wipe cache partition it reboots, wipe davik it reboots help!!!
Lol. Flash stock with Odin
been there done that, doesn't work
nite4evr said:
been there done that, doesn't work
Click to expand...
Click to collapse
I don't see why odin shouldn't work
So your factory reset doesn't work?
Just dirty flashing a rom.
But really, odin should work at all times unless your phone's hard bricked
I found an old nandroid backup from when I first got my phone. Early when root, recovery etc came out. Flashed it once, it worked half way before reset, done it again and it worked.
Thank god!!!!!!! ALWAYS BACKUP KIDS, ALWAYS BACKUP!!
I tried to flash CWM through odin many times, CWM was still giving me trouble. It was wierd!
Dirty flash didn't work, it kept resetting.
hello. yesterday i decided to go ahead and flash miui. this is what i did:
-made a nandroid backup of my current rom (liquidsmooth 2.2)
-factory reset
-flash miui
-flash gapps
-wipe cache and dalvik cache
it worked perfectly, but i didnt like miui so i wanted to go back to liquidsmooth. so i did this
-factory reset (successful)
-restore nandroid of liquidsmooth (successful)
this worked fine but when i rebooted it got stuck on a black screen, so i pulled the battery and tried again but it was the same.
then i went into recovery and did a factory reset. but this time it failed! so i restored liquidsmooth without wiping and it was successful, but then when i rebooted everything was force closing.
finally i went into recovery again and did a factory reset and it worked ok, then i restored liquid smooth again and it worked ok too. i rebooted and everything seems to be ok now.
now im scared to flash any roms. is the problem twrp or liquidsmooth? everything worked properly when i installed miui. i did some research and it looks like restore fails are common, but i couldnt find anything about wipe fails. is this normal?
thanks in advance
KeyLemonPie said:
hello. yesterday i decided to go ahead and flash miui. this is what i did:
-made a nandroid backup of my current rom (liquidsmooth 2.2)
-factory reset
-flash miui
-flash gapps
-wipe cache and dalvik cache
it worked perfectly, but i didnt like miui so i wanted to go back to liquidsmooth. so i did this
-factory reset (successful)
-restore nandroid of liquidsmooth (successful)
this worked fine but when i rebooted it got stuck on a black screen, so i pulled the battery and tried again but it was the same.
then i went into recovery and did a factory reset. but this time it failed! so i restored liquidsmooth without wiping and it was successful, but then when i rebooted everything was force closing.
finally i went into recovery again and did a factory reset and it worked ok, then i restored liquid smooth again and it worked ok too. i rebooted and everything seems to be ok now.
now im scared to flash any roms. is the problem twrp or liquidsmooth? everything worked properly when i installed miui. i did some research and it looks like restore fails are common, but i couldnt find anything about wipe fails. is this normal?
thanks in advance
Click to expand...
Click to collapse
Must be a TWRP issue. Time to use CWM.
Aerowinder said:
Must be a TWRP issue. Time to use CWM.
Click to expand...
Click to collapse
ok, should i use rom manager to flash it?
KeyLemonPie said:
ok, should i use rom manager to flash it?
Click to expand...
Click to collapse
Never failed me lol on all accounts.
mt3g said:
Never failed me lol on all accounts.
Click to expand...
Click to collapse
does it support the t999v with the VLDLL1 bootloader? also will it be able to install the touch version of cwm? i really dont like using the hardware buttons.
KeyLemonPie said:
does it support the t999v with the VLDLL1 bootloader? also will it be able to install the touch version of cwm? i really dont like using the hardware buttons.
Click to expand...
Click to collapse
That I don't know. Don't follow your guys' stuff. You guys have a large thread for canadian users, and the touch version is available for DL from their website, don't think so for free app.
KeyLemonPie said:
does it support the t999v with the VLDLL1 bootloader? also will it be able to install the touch version of cwm? i really dont like using the hardware buttons.
Click to expand...
Click to collapse
http://db.tt/VnhR8dCO
Flash that in TWRP.
Aerowinder said:
http://db.tt/VnhR8dCO
Flash that in TWRP.
Click to expand...
Click to collapse
ok. but is it safe to flash it in twrp since it has been acting weird?
what if something goes wrong? also do i need to wipe anything before flashing it?
KeyLemonPie said:
ok. but is it safe to flash it in twrp since it has been acting weird?
what if something goes wrong? also do i need to wipe anything before flashing it?
Click to expand...
Click to collapse
Just flash it.:laugh:
I was on 4.2.2 XenonHD with LeanKernel. I directly flashed Cataclysm ROM with cache, dalvik cache wipe and factory reset on GooManager. It booted flawlessly the first time. Then after completing the startup I rebooted. But then I became stuck on the google logo (surprise surprise...)
I don't get it. Why did it boot perfectly the first time but not after a reboot?
Anyway, I tried to restore my nandroid backup of the 4.2.2 XenonHD ROM. But then I got stuk at the google logo again. Why?
I haven't backed up my mediafiles (music, photo's etc) yet, in case a factory image installation is needed. I assumed I didn't need to backup those mediafiles, becuase I already have a nandroid backup, meaning I can always go back to the last ROM.
Does anybody have a solution for this? I don't care if I end up booting in 4.2.2 or 4.3, as long as I can preserve my media files.
Or do I have no other options than installing factory boot image of 4.3, meaning my files will be gone?
Thanks in advance.
No as long as you don't flash userdata.img nothing will be wiped (I think maybe to be sure you have to check twice). You can use adb pull to pull the mediafiles if you want.
Sent from my Galaxy Nexus using XDA Premium HD app
Try factory reset and then try to restore from the backup..
lastforone said:
Try factory reset and then try to restore from the backup..
Click to expand...
Click to collapse
It didn't work. I can still see my files and everything in TWRP recovery.
Rapydax said:
It didn't work. I can still see my files and everything in TWRP recovery.
Click to expand...
Click to collapse
I had Purity ROM with A.S.K.P kernel when 4.3 came out, i grabbed the zip from one of the topic in development and flashed it VIA CWMRecovery, was pretty smooth but i wanted all my setting which wasn't possible so i reverted back to Purity, this is how i did it.
Factory Reset.
Format /system
Flashed 4.3
--
Factory Reset.
Format /system, /cache, cleared Dalvik Cache as well
Flashed PurityRom 4.2
Flashed A.S.K.P Kernel
Flashed CrossBreeder Mod
Booted into OS successfully.
Restored My Apps
Click to expand...
Click to collapse
had no problem, well yeh first boot took its time to load but it did, i knew that A.S.K.P will take its time to boot for the first time so i let it be for like 4-8 mins.
Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );
if you can still get to recovery, download latest gapps and flash that
Did you factory reset before or after you restored your back up?
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Try to factory reset again
vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.