I flashed MOAR 2.3 and update. I was playing around with my phone and decided to encrypt my device. I was having problems and I shut off my phone since it wasnt responding. Upon rebooting, I was prompted to factory reset since encryption failed. I did so, and it gave me the same problem... Here is what I've tried thus far
-wipe cache and dalvik
-factory reset
-restore previous backup (failed)
-odin to stock and factory reset
-reflash zip
-still failed
I am able to access download and recovery. but can't get past annoying prompt. Any ideas. Just an FYI I have Sprint Total Equipment Protection and was wondering if I can claim this as lost or i can destroy it beyond repair so I can get a replacement without them checking if it was rooted.
THANK YOU
Ok first, go into recovery and make a backup as is. Then download your rom again, or reflash if you have it, and flash with a full wipe (system, factory reset (aka data), cache, and dalvik)
Now try to see if it boots up. If it does, you can go into recovery and advanced restore your data.
There was someone else on here who had gotten stuck with encryption when trying to flash something. His thread might be a good place to start... I don't have the link with me, but search q&a for encryption or encrypted.
If I recall correctly, he had to Odin back to stock recovery. I could be wrong, though, it was a little while ago, and I was just reading through the thread, not actively participating in it.
Hope you can get your phone fixed!
Sent from my SPH-L710 using xda app-developers app
Related
I tried installing a rom last week on my Galaxy Note II (Rogers), i followed orders (this isn't my first time flashing roms), and it has been stuck in a constant boot loop.
I've tried everything, wiping cache, factory reset, tried to flash different roms, etc....
I am a mac user (which means Odin isn't an option).
If you guys have any suggestions on how to fix this it would be greatly appreciated.
What rom were you on and what rom were you trying to flash originally? Also what recovery are you using? Need a little more info because usually wiping caches dies the trick. Provide a link to the rom you were trying to flash of your can.
jethro650 said:
What rom were you on and what rom were you trying to flash originally? Also what recovery are you using? Need a little more info because usually wiping caches dies the trick. Provide a link to the rom you were trying to flash of your can.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1986893
This is the rom, i was using CMW to flash it, then it made me switch to TWRP (think its called that)......hope that helps.
Sorry I can't be of more help aside of redoing the installation of your recovery and redownloading the rom ( bad downloads happen) and making sure you do all the wipes (cache, dalvik cache and factory reset). If none of that works I'm sure someone more knowledgable than myself will chime in.
I've never run into a bootloop problem myself, but this might help you out :
hxxp://galaxynote2root.com/galaxy-note-2-tutorials/how-to-unrootunbrick-galaxy-note-2-with-stock-firmware/
Good luck
Have you had any luck with this yet? I've been unable to get my phone back up.
QuantumPSI said:
Have you had any luck with this yet? I've been unable to get my phone back up.
Click to expand...
Click to collapse
No luck, but then again i am a Mac user, so its a little more difficult for me to solve this problem.
Anirchy said:
I tried installing a rom last week on my Galaxy Note II (Rogers), i followed orders (this isn't my first time flashing roms), and it has been stuck in a constant boot loop.
I've tried everything, wiping cache, factory reset, tried to flash different roms, etc....
I am a mac user (which means Odin isn't an option).
If you guys have any suggestions on how to fix this it would be greatly appreciated.
Click to expand...
Click to collapse
Put another ROM on an sdcard. Take your battery out then press the button combo for recovery mode before you slip your battery back in. Then it'll force download mode. Reflash the new ROM after full wiping and you should be good.
Sent from my SGH-I317 using xda premium
Definitely a bad ROM. Run a MD5 checker against it prior to copying to the SD card. Note: your SD card could be the culprit.
If you have a recovery installed, ensure you WIPE everything, Fix permissions (i'm on CWM) and reflash the modem and carrier files POST rom install.
I experienced my first boot loop yesterday but I was able to recover from it thanks to a little common sense and patience. :fingers-crossed:
Good luck!
first of all, don't freak out, a bootloop isn't the end of the world. Sounds like it was a bad flash.
ppl above have obviously told you to wipe caches, and all that stuff and if it hasn't worked then you are still down and out.
I would suggest you get yourself into recovery - not going to explain that here as you said you were able to flash other roms and it didn't work and try flashing your nand backup - hopefully you have a nice clean backup from before you flashed. if so, clear caches, etc and then try flashing it it should be back to at least working.
your nand backup will have all your stuff in it as you would have had to backup from recovery, which means you'll at least still be rooted. you can then go ahead and get another rom - check the md5 and flash it
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.
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.
Ok I have T999L 16GB.
Phone working fine. Did hard reset because they hadn't been used in a while and wanted to start fresh.
After reboot, phone stuck in "T-Mobile 4G LTE" bootloop forever. Tried again, same thing.
Did Odin flash of latest ROM for that device (per what I could find?)
T999LUVUBOH1_T999LTMBBOH1_T999LUVUBOH1_HOME.tar
same thing, no result. Downloaded the PIT file for that phone, did another odin flash of the ROM above, but checked "re-partition" and pointed to the PIT file. Successful flashing, device rebooted. Same thing endless bootloop.
Not really sure what to do now, any ideas?
@DocHoliday77 possibly as one of the resident experts 'round these parts...
Immediately after flashing and before the first boot, get into recovery and perform a full wipe.
audit13 said:
Immediately after flashing and before the first boot, get into recovery and perform a full wipe.
Click to expand...
Click to collapse
worth a try, will report back.
edit: @audit13 - Worked like a boss, did the odin with repartition PIT file, but deselected auto-restart, went into recovery after flashed and wiped factory reset plus cache, rebooted, and BAM, got into the set up screen.
Thanks for your help.
Glad it worked for you. A factory wipe is sometimes required to make the data and cache partition available to the newly flashed rom. Even wiping via twrp or cwm may not be enough at times.
audit13 said:
Glad it worked for you. A factory wipe is sometimes required to make the data and cache partition available to the newly flashed rom. Even wiping via twrp or cwm may not be enough at times.
Click to expand...
Click to collapse
Yeah sure seems to be that way, glad that's all it was. I know the PIT mapping with the ROM must have helped too, but flashing in stock recovery after that cleared it up for writing to the new partitions like you said.
Coming from a Nexus 6 this was pretty annoying, I am used to using fastboot to do everything, I don't see a Samsung device in my future.
Same thing can happen with a nexus 4 and nexus 5 in that I still have to perform a full wipe in stock recovery if the phone was running a custom rom. Don't have a nexus 6 or 6p to play with
Samsung phones don't have a fastboot mode. The closest thing would be their download mode.