Related
I bought a T-Mobile Samsung Galaxy S III yesterday. It was working like a champ. I tapped the Software update button, it installed, rebooted, poof phone + contacts icons are now turned into little android icons, the apps are gone. Every app on the phone is crashing, Factory Reset doesn't remedy this.
So I decide, oh okay, I'll restore the stock rom that came with it. Did this after much trial and error but now everything on the phone is crashing constantly. The UI won't even stay running for more than 1 minute.
So far I have tried: Reinstalling the original stock rom, and the updated stock rom.
( T999UVALEM_T999TMBALEM_T999UVALEM_HOME.tar.md5 and T999UVALH2_T999TMBALH2_T999UVALH2_HOME.tar.md5 )
I was using a tool I found here called Samsung Galaxy S3 QCom ToolKit.
I have tried everything and I am at wits end.
Reflash one of them. Wipe all including /data /cache /dalvik-cache /system before you flash. As soon as its finished reboot straight to recovery and wipe data/factory reset
billard412 said:
Reflash one of them. Wipe all including /data /cache /dalvik-cache /system before you flash. As soon as its finished reboot straight to recovery and wipe data/factory reset
Click to expand...
Click to collapse
It suddenly works again after rebooting several times (Nothing has crashed at all so far)
I wish I could offer an explanation as to why it suddenly works now. I used to be really big into android but we are talking back when the HTC Hero on Sprint was new.
hiimcody1 said:
It suddenly works again after rebooting several times (Nothing has crashed at all so far)
I wish I could offer an explanation as to why it suddenly works now. I used to be really big into android but we are talking back when the HTC Hero on Sprint was new.
Click to expand...
Click to collapse
I would go into recovery and wipe system, data, cache and dalvik cache then use ODIN and flash T999UVALH2_T999TMBALH2_T999UVALH2_HOME.tar.md5 just to make sure you dont have any problems like this again in the future, especially if it crashed and after several reboots and it is finally working. Start FRESH.
I'd like to start by apologizing for what is probably the 9,000th "help, I've bricked my phone!" thread. I did some searching, and while I found many, I wasn't able to find one that both dealt with my specific issue, and did so assuming a level of newbishness appropriate for me.
Months ago, I rooted my AT&T Galaxy SIII, and installed CM10. It's been all candy and rainbows since. This morning, I somewhat foolishly decided to update from a nightly I installed in October/November, to the January 7 CM 10.1 nightly, using the built-in updater I had previously used to switch to a nightly.
It worked...sort of. I guess I should have cleared my cache or something ahead of time, because almost all of my GAPPS stopped working. Woops! Figuring that I should probably stop dicking around with my phone until I learned a bit more, I just went back and told the phone to switch back to the nightly I from October/November that I was previously using.
It didn't work. My phone now reaches the CM boot animation and just...sits there. And sits there. And sits there. To complicate the issue, I cannot get the phone to boot into recovery mode (although admittedly, I'm too thick to know what I'm meant to do once I'm there anyway). I CAN get the phone into download mode, but not being sure what I should do there, I thought it best to consult you all on what to do next.
I'm happy to give any additional information needed, and I hope it goes without saying that I am extremely thankful for any help you all can offer.
Try to get it back into recovery by taking the battery out, putting it back in and then holding volume up, home, and power. If you are sure you can't get it into Recovery, but know for sure you can get it into Download, go into Download and flash stock and go from there. These aren't bricks. These are just whoops. Lol.
If you can reach download mode, you'll be okay. What you want to do is use Odin to flash a rooted stock image; from there, you should be able to get back to a point where you can re-install a custom recovery of your choice and try flashing your favourite ROM again.
For the record, it's always a good idea to clear data/cache when changing ROMs, or changing between major revisions of a ROM (such as CM10 -> CM10.1) to avoid this sort of problem.
Actually, you should always wipe cache and dalvik when flashing the update. If it is a major update like 4.1.2 to 4.2.1, then you should wipe cache, wipe dalvik, Factory Reset, Format System then flash your ROM.
Move important files to SD using twrp file manager. Put rom on SD with gapps. Format internal, wipe caches, format system, factory reset, load ROM, load gapps. Reboot.
Sent from a Horny Pink Pony
smelenchuk said:
If you can reach download mode, you'll be okay. What you want to do is use Odin to flash a rooted stock image; from there, you should be able to get back to a point where you can re-install a custom recovery of your choice and try flashing your favourite ROM again.
For the record, it's always a good idea to clear data/cache when changing ROMs, or changing between major revisions of a ROM (such as CM10 -> CM10.1) to avoid this sort of problem.
Click to expand...
Click to collapse
I did this, being careful to follow all the instructions provided. Odin seemed to think everything worked, and after about 10 minutes, it rebooted the phone.
However, it still gets stuck. Now, since CM is no longer installed, it just sits at the SAMSUNG logo forever.
It still boots into download mode, and will now boot into recovery as well. Any suggestions?
naporeon said:
It still boots into download mode, and will now boot into recovery as well. Any suggestions?
Click to expand...
Click to collapse
Boot to recovery and clear data and cache.
smelenchuk said:
Boot to recovery and clear data and cache.
Click to expand...
Click to collapse
Worked like a charm, thanks! Can't believe after all that trouble, I didn't think to do that myself. >.<
I've got a T-Mobile Note 3 that I picked it up on launch day last Thursday at a T-mobile store. I proceeded to root the phone with Odin, then restore via Titanium Backup and then fix the backup with "restorecon -R -v /data". Life has been great until last night. Initially I got a circle with a line through it instead of the mobile signal and my cellular link would not connect, but my wifi was fine. When the problem was sill occurring this morning I figured it was an odd cellular problem and rebooted the phone this morning when it persisted. Now the phone is rebooting a few minutes after it completes booting.
It will boot normally, then I'll unlock the phone and get my window manager (Holo)...then I'll get the error "Process system isn't responding. Do you want to close it?". Then I get the error "Unfortunately, Favorite Apps has stopped." Regardless whether I interact with those error messages the phone then reboots a minute later. I have *not* done a restore from CWM ever and the phone doesn't seem to have suffered any physical damage.
The things I've tried include:
*) power down, remove sdcard, then reboot
*) power down, remove sim card, then reboot
*) power down, remove sim card, remove sdcard, then reboot
*) clear cache, then reboot
*) clear dalvik-cache, then reboot
*) clear dalvik-cache and cache, then reboot
*) clear dalvik-cache, clean cache, then wipe to factory, then reboot
In all the above scenarios nothing has changed. The phone reboots after it completes booting.
In the past, I've rooted and flashed on a G1, a G2, and an S3. I've bricked my S3 that had to be repaired via JTAG. This reboot problem with my Note 3 is completely unlike any of the things I've seen with previous phones.
I've read through some of the other threads about reboot loops, but all the threads I've read were caused by a CWM restore and have no solution yet.
Does anyone know the cause of this and what could fix it?
digitalfiend said:
I've got a T-Mobile Note 3 that I picked it up on launch day last Thursday at a T-mobile store. I proceeded to root the phone with Odin, then restore via Titanium Backup and then fix the backup with "restorecon -R -v /data". Life has been great until last night. Initially I got a circle with a line through it instead of the mobile signal and my cellular link would not connect, but my wifi was fine. When the problem was sill occurring this morning I figured it was an odd cellular problem and rebooted the phone this morning when it persisted. Now the phone is rebooting a few minutes after it completes booting.
It will boot normally, then I'll unlock the phone and get my window manager (Holo)...then I'll get the error "Process system isn't responding. Do you want to close it?". Then I get the error "Unfortunately, Favorite Apps has stopped." Regardless whether I interact with those error messages the phone then reboots a minute later. I have *not* done a restore from CWM ever and the phone doesn't seem to have suffered any physical damage.
The things I've tried include:
*) power down, remove sdcard, then reboot
*) power down, remove sim card, then reboot
*) power down, remove sim card, remove sdcard, then reboot
*) clear cache, then reboot
*) clear dalvik-cache, then reboot
*) clear dalvik-cache and cache, then reboot
*) clear dalvik-cache, clean cache, then wipe to factory, then reboot
In all the above scenarios nothing has changed. The phone reboots after it completes booting.
In the past, I've rooted and flashed on a G1, a G2, and an S3. I've bricked my S3 that had to be repaired via JTAG. This reboot problem with my Note 3 is completely unlike any of the things I've seen with previous phones.
I've read through some of the other threads about reboot loops, but all the threads I've read were caused by a CWM restore and have no solution yet.
Does anyone know the cause of this and what could fix it?
Click to expand...
Click to collapse
I would just Odin to stock and restart. I'm guessing some app your restored form another phone did it.
YellowGTO said:
I would just Odin to stock and restart. I'm guessing some app your restored form another phone did it.
Click to expand...
Click to collapse
I don't believe it was an app that was restored because the restore had run perfectly for 5 full days. I completed the restore last Thursday...that's what makes this so unusual.
Do you know where to get the stock zips to use with Odin?
digitalfiend said:
I don't believe it was an app that was restored because the restore had run perfectly for 5 full days. I completed the restore last Thursday...that's what makes this so unusual.
Do you know where to get the stock zips to use with Odin?
Click to expand...
Click to collapse
There's some stock Odin tar files in the Android development forum. Download and flash using Odin. Once it reboots, remove battery and manually boot into stock recovery and do a factory reset/wipe. Reboot and it should work.
Sent from my SGH-T889
jmerlos said:
There's some stock Odin tar files in the Android development forum. Download and flash using Odin. Once it reboots, remove battery and manually boot into stock recovery and do a factory reset/wipe. Reboot and it should work.
Sent from my SGH-T889
Click to expand...
Click to collapse
It looks as if the stock tar in zip format (N900TUVUBMI7_N900TTMBBMI7_TMB.zip) can be downloaded from either of these links:
http://forum.xda-developers.com/showthread.php?t=2465764 (faster download link)
http://forum.xda-developers.com/showthread.php?t=2468275 (slow download link)
I just finished downloading from the first link and after extracting the zip file I have these files:
N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar.md5
SS_DL.dll
This seems like an obvious thing, but want to ask because of how odd this problem is: Do I simply flash the "N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar.md5" file the same way that I flashed the CWM through Odin?
Yes, but IIRC, just uncheck reboot, reboot manually into recovery, then wipe, factory reset, etc. Pull your battery, reboot. Check the TWRP thread, it has exact directions.
sgh-TWEAKED-889©
Warrior1975 said:
Yes, but IIRC, just uncheck reboot, reboot manually into recovery, then wipe, factory reset, etc. Pull your battery, reboot. Check the TWRP thread, it has exact directions.
sgh-TWEAKED-889©
Click to expand...
Click to collapse
Got it, thank you! Here's what I'm referencing for the Odin options:
http://forum.xda-developers.com/showpost.php?p=46110842&postcount=2
I'll flash this and update the thread.
Good luck bro!!
sgh-TWEAKED-889©
Ok, I flashed with Odin then once it completed I got the "PASS!" status in Odin. I shut down Odin, pulled the battery from the Note 3, then allowed the phone to boot. There was a "booting recovery" message in blue at the top of the screen before the phone booted, then it booted to the "samsung logo", then the animated circular logo, then the white screen with the "T-Mobile 4G LTE" logo, then rebooted. The second boot, it did the same thing but stayed on the "T-Mobile 4G LTE" screen for many minutes...then it seemed as if it was completing it's reboot because I got the notification bar with the time and the circle with the line through it for the cell signal strength. I got the same error when the phone seemed to have completed booting, then a reboot. Now it's back to the same place it started in it's rebooting cycle.
This makes absolutely no sense at all. If I'd have done a CWM restore then I could understand that...but there's no reason for this that I can see. The phone acts as if it was knocked off of the T-Mobile network and now it finishes it's booting cycle long enough to be rebooted.
So now I have a useless Note 3. I'm game for taking the phone back to the T-Mobile store and requesting that they replace the phone, which they probably would, but I have no guarantee that this wouldn't happen again. I'm open to suggestions as long as they don't cause me to brick my phone completely.
I finished installing TWRP and darthrom successfully. However, after the darthrom finishes booting I have the exact same problem with the phone rebooting that the stock ROM had.
I'm back to square one.
I'm open to suggestions.
There are a lot of people having boot loop problems even without root though they are spread out among various sub forums. Try this thread for example:
http://forum.xda-developers.com/show....php?t=2467005[Q] Reboot cycle after restart help
Sent from my SAMSUNG-SGH-I317
Dumbo53 said:
There are a lot of people having boot loop problems even without root though they are spread out among various sub forums. Try this thread for example:
http://forum.xda-developers.com/show....php?t=2467005[Q] Reboot cycle after restart help
Sent from my SAMSUNG-SGH-I317
Click to expand...
Click to collapse
I saw a couple threads last night when I was searching around on the web about other models of phones with SIM socket and SIM card issues. I'm beginning to think that my issue is hardware-related, and not software. I did another wipe last night based on this thread's post: http://forum.xda-developers.com/showpost.php?p=46157872&postcount=6&nocache=1&z=7848000959493220
Instead of simply wiping, I formatted /data/, then wiped, then I flashed on the stock ROM, then flashed on the darth rom. I got slightly different results once the phone was done with it's firstboot - it kept giving me the error that a new SIM card had been installed and the phone needed to be rebooted. This causes me to suspect the physical hardware of my Note 3 or the SIM card. I have ruled out the SIM card because I've been using it in my old G2 since this started, via an adapter for the G2's SIM socket, and it's been fine. I'm planning on taking the phone to T-Mobile today and seeing what they can sort out with either a SIM exchange or phone exchange.
The note 3 misbehaved the same way while in the T-Mobile store. They swapped the phone out under warranty after asking only the basic questions and trying a factory reset. The same SIM card in the new note 3 works fine.
I'm on the same boat. Got my Note 3 this morning, rooted an hour ago with CMW, made backup and flashed Stock ROM from Jovy. Result: bootloop. Restore backup and still on bootloop. DLing the Odin stock .tar to see if it helps. Any more suggestions?
Edit: After flashing with Odin the stock tar from Sammy all it's good...at least for now.
Wally72 said:
I'm on the same boat. Got my Note 3 this morning, rooted an hour ago with CMW, made backup and flashed Stock ROM from Jovy. Result: bootloop. Restore backup and still on bootloop. DLing the Odin stock .tar to see if it helps. Any more suggestions?
Edit: After flashing with Odin the stock tar from Sammy all it's good...at least for now.
Click to expand...
Click to collapse
How far into the booting process would you get before the phone rebooted?
digitalfiend said:
How far into the booting process would you get before the phone rebooted?
Click to expand...
Click to collapse
Never passed Samsung! In my case, flashing the .tar with Odin from Samfirmware fixed my issue. I think imma wait for a more stable recovery.
Sent from my SM-N900T using Tapatalk now Free
Wally72 said:
Never passed Samsung! In my case, flashing the .tar with Odin from Samfirmware fixed my issue.
Click to expand...
Click to collapse
Interesting...it sounds like you had the boot loop that many others have had...it's cool to hear that you got it fixed. I think my problem was hardware-based since the phone completed it's boot process and *then* had issues. Luckily T-Mobile was there for me and helped out.
Wally72 said:
I think imma wait for a more stable recovery.
Click to expand...
Click to collapse
I know what you mean as far as waiting for a stable recovery. If it's any help, I've decided to stay far away from the recovery restore and simply use Titanium backup to do restores. It's more work than a nandroid recovery, but it reliably does it's job well for me.
digitalfiend said:
Interesting...it sounds like you had the boot loop that many others have had...it's cool to hear that you got it fixed. I think my problem was hardware-based since the phone completed it's boot process and *then* had issues. Luckily T-Mobile was there for me and helped out.
I know what you mean as far as waiting for a stable recovery. If it's any help, I've decided to stay far away from the recovery restore and simply use Titanium backup to do restores. It's more work than a nandroid recovery, but it reliably does it's job well for me.
Click to expand...
Click to collapse
Well...I'm doing a lot of reading. I can't stand this "stock look" and me, every time I root a phone, I always do my own modifications within the ROM I choose to flash. SystemUI and apk's. I only change the .png's, therefore, getting the visual look I want/like. Always done it with certain ROMs/Themes. I downloaded Jovy's stock ROM and made the visual changes I wanted. I flashed and got into that bootloop scenario. Restore backup with CWM provided by Zedomax and made it worse. I think the problem is recovery (at least from what I've read). In this case, CWM been less unstable than TWRP. I f you read a bit around, must ppl if not all, had the "dead bootloop" issue with TWRP. I haven't read from anybody yet having the "dead bootloop" with CWM. Ppl with CWM that flashed their backup and got that bootloop, fixed it flashing back to stock, where ppl that had TWRP have tried to flash back to stock and their phones never boot completely
Again...imma wait a little more for good reports as far as recovery goes!
Bigbiff has a file he uploaded, it may be a fix for the bootlooping issue. You'd be the first to try at this point. It's linked below, but the entire thread is in the OG development of tmobile.
http://forum.xda-developers.com/showthread.php?p=46379854
sgh-TWEAKED-889©
I've never seen so many issues with a brand new flagship phone before. Makes me think it wasn't tested fully before release. I mean all these problems!
Even though I returned my N3 after I tried restoring and getting bootloop of death, I feel this model is really flawed. Hearing new things everyday.
Greetings,
I would have liked to post this questions, where it belongs to, but I'm new to this forum, so I put it here.
Last September I've updated my DHD following the instructions given in the thread mentioned in the headline and everything was fine. Yesterday in the evening, I got the notification to restart using the recovery mode, because something in the context of the superuser should be updated or modified. Because it was not the first time, I just did it. But this time, after rebooting, the device stopped with the HTC bootscreen (green HTC on white background).
After 10 minutes I took out the battery and restarted again. Again I was able to choose recovery mode, but while starting the DHD got stuck with the bootscreen. I decided to wait and just put it aside showing the boot screen, but the result this morning was that the battery is empty and nothing changed.
Does someone know about that issue and what do I need to do to get the device to work again? Why was this update needed in the first place?
Thanks a lot in advance...
im not sure why
but have you tried re-flashing the ROM?
PHOENIX-9 said:
im not sure why
but have you tried re-flashing the ROM?
Click to expand...
Click to collapse
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
If you don't wipe your data partition (dirty flash) and you flash the exact same ROM, you shouldn't lose data.
KKrittel said:
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
Click to expand...
Click to collapse
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
PHOENIX-9 said:
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
Click to expand...
Click to collapse
Tried to make a backup, but it recovering did not work. Doesn't matter. I just flashed the same image again, downloaded 'my' apps and restored the status from before the crash.
Nevertheless the same notification showed up, saying that the superuser kernel needs to be updated and I should use 'recovery mode' again. With a bad feeling, I did it again, but this time it works.
So to sum it up: device was useless for some days, restored it with some effort and now it works again. But I need to get prepared for the next time and to think of an app to backup all apps including app-data.
...but as always, this is a task for laaaaater
Thx,
Karl
Hi guys, I've been looking for a solution for almost a week for my n7100 international version and I am tired of trying all the solutions which none of them worked. If you have any tiny idea crumb it will be welcomed because I'm out of ideas.
I can summarize the problems like this;
I was using DN3 RC2 rom, it was very stable and it had a very good battery life (almost 4 days). Everything started with choosing Ultra Power Saving mode. I realized that my battery was draining too quickly right after I choosed Ultra power saving mode. I did not care about this and changed battery with the fully charged one. I turned on the phone disable the ultra power saving mode but not a single change, it is still consuming the battery like it never did before. I disabled everything,took the phone to flight mode but no solution. (6 hours in flight mode, everything disabled, %25 battery consumption, normally it was %1 max %2).
I reset the phone, wipe phone/cache, changed to stock rom, reflashed with other roms without gapps but it did not work. The only single thing common is "No Deep Sleep" even with stock rom nothing installed, furthermore I tried not to touch the phone after flashing, I mean it stayed in very first screen which is choosing language of the phone, but it didnt work either.
While dealing with this power problem, I noticed that I have other problems like recovery screen freezes and resets to recovery screens after freezing event occured.
-Recovery screen (tried all versions philz touch, TWRP, original CWM) freezes at random times, mostly after 15 seconds or 6-7 choices. Only Philz Touch 5.xx version worked without freezing, all other recovery screens freeze even with their latest versions.
And final problem is usb recognition, I couldnt make any PC,Mac,linux (with kies, without kies, with generic android drivers, without generic drivers, with many cables including the original which is still working with other phones) to recognize note 2. Only in download/odin mode it is working so I can flash the stock bootloader or other roms.
Because of my recklessness, by installing stock 4.4.2 rom, and then flashing again with custom roms knox warranty void counter increased to 1. So I am without samsung warranty now. I am still using phone with DN3 V5 with No Deep Sleep, No Usb Recognition, Terrible Battery Life.
I think that this is now beyond software issue and something in hardware should be changed. What are your opinions?
Thanks to all participants in advance!
Have you tried wiping everything (system, cache etc but NOT efs) in recovery then flashing stock with odin? Remember to back up first though...
sparky b said:
Have you tried wiping everything (system, cache etc but NOT efs) in recovery then flashing stock with odin? Remember to back up first though...
Click to expand...
Click to collapse
Yeah, the OP didnt mention anything about wiping/reformatting/resetting. In addition to the above, also try wiping dalvik cache.
Stuff to try...
1) Wipe Dalvik Cache and cache.
2) Factory reset.
3) Mega wipe then flash stock ROM through ODIN.
4) Flash another ROM (Since ODIN is working.)
N7105 rocking AOSB with AGNi kernel,
Sent from a small country named Singapore.
Click "Thanks" if I was of any help!
sparky b said:
Have you tried wiping everything (system, cache etc but NOT efs) in recovery then flashing stock with odin? Remember to back up first though...
Click to expand...
Click to collapse
thanks for the advice, I ve systematically done wiping before and after all flashing actions. But none of them worked.
Irwenzhao said:
Stuff to try...
1) Wipe Dalvik Cache and cache.
2) Factory reset.
3) Mega wipe then flash stock ROM through ODIN.
4) Flash another ROM (Since ODIN is working.)
N7105 rocking AOSB with AGNi kernel,
Sent from a small country named Singapore.
Click "Thanks" if I was of any help!
Click to expand...
Click to collapse
Unfortunately these are so basic actions(all kind of wiping, flashing another rom, flashing stock rom) that I ve done in first place and they didnt work out.