Hey guys, had a Note for a little while now and was running stock AT&T GB. I tried upgrading to ICS a couple of times using other threads in this forum, but I'd keep getting stuck in a boot loop and had to revert back to stock AT&T GB to recover my device per Da_G's method here: http://forum.xda-developers.com/showthread.php?t=1506330, and it worked fine.
However, I recently tried one more time to upgrade to ICS, failed and reverted back to stock AT&T GB per Da_G's method, and while my phone turns on, it has become sluggish to the point of being absolutely unusable. Screen touches work fine in some cases, and then take forever to register in the same spot later. The on screen keyboard cannot be invoked - it almost always hangs the phone. And the phone randomly reboots.
I did forget to wipe cache and dalvik cache the last time around while doing the install, and that probably caused this problem. But sine then I've wiped both caches and retried flashing, and also reinstalled a stock AT&T radio in case that was the problem, and also reset the flash counter per braway's methode here: http://forum.xda-developers.com/showthread.php?t=1569206, but to no avail...
My Note is pretty much useless at this time, so any light you guys can shed or any other tack you can suggest is going to help me immensely!
Thanks for the help!
Sid.
Wiping caches is not enough. You need to to a full data wipe/factory reset. At this point why not just flash your phone with Odin.
http://www.samsdroid.com/2012/07/i717uclf6-android-404-usa-at-stock-rom.html
This will fully wipe your phone and install the UCLF6 ICS ROM with matching radio.
Agoattamer said:
Wiping caches is not enough. You need to to a full data wipe/factory reset. At this point why not just flash your phone with Odin.
Click to expand...
Click to collapse
Sorry, I didn't mention - I DID do a factory wipe/data reset and I've been flashing the stock GB ROM via ODIN itself. But thanks for the link to the ICS ROM - I'll try installing this and report back.
Okay, I downloaded the UCLF6 ROM from the samsdroid site (took like 3 hours to download!), performed several factory data resets, cache wipes and dalvik cache wipes on my phone, and then flashed the ICS ROM via Odin. Odin showed "Passed", but the phone rebooted into recovery with a message "failed to mount /system" and "failed to mount /data". I then hit "reboot system now" and am stuck at boot loop. Booted back into recovery, got the same message about not being able to mount system and data. Hit "reboot system" again and back to boot loop...
What the heck am I doing wrong???
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
You do have an ATT i717 and not a canadian version? But I think your phone has other issues.
It is an AT&T SGH-i717. I've used it for 6 months now and it worked fine - it just never let me upgrade it to anything beyond GB... and now it is unusable even with GB.
Do you think it might be a hardware issue? Although, how could flashing and reflashing ROMs impact the hardware?
If the odin flashing did not straighten things out then I have to believe that there are other issues.
sid.asu said:
It is an AT&T SGH-i717. I've used it for 6 months now and it worked fine - it just never let me upgrade it to anything beyond GB... and now it is unusable even with GB.
Do you think it might be a hardware issue? Although, how could flashing and reflashing ROMs impact the hardware?
Click to expand...
Click to collapse
Did you try to flash ICS with Samsung Kies? If that doesn't work, your phone may have developed a hardware problem.
i have had the same issues as well, i am unsure if its me or what but everytime i have tried to flash a tmobile rom on my note which should work it slows down to a crawl i cannot even go through the setup process. I have tried via odin and through cwm touch. the next thing i flashed was t879uvlg3 modem and i was wondering if that was the issue and if so what modem should i flash that way i dont have to use kies for recovery cause man..........thats slow. I even made a nandroid backup and it was slow as well so if anyone has had this issue or any ideas please help me
oort cloud said:
Did you try to flash ICS with Samsung Kies? If that doesn't work, your phone may have developed a hardware problem.
Click to expand...
Click to collapse
My problem is that the phone does not stay on long enough for Kies to detect it - it keeps rebooting on GB. Well, guess it's cooked! Thanks for the help!
Related
Hey guys this is where I am with this issue. Kind of new to Android so forgive me if something is obvious and left out.
Bell Galaxy Note, unlocked via unlock code.
Please note that before I ever flash a new rom, I do a factory wipe, wipe cache, wipe dalvik..3 times first, then I redownload and install from Play
1. Noticed that my phone on Flappjaxx's rom was acting flaky. (ie FCs more than usual). This rom worked fine for a few weeks.
2. Tried CM9 via Rom Manager. Phone still a bit flakey.
3. Used CWM Recovery to return to FJ's rom which I made a backup first.
4. Phone even more flakey (ie. noticed some apps could get the internet, others could not. Phone would FC as well every time).
5. Tried clearing cache, dalvik, and fixed permissions. FJs rom still flakey (at this point 2-3 attempts to fully boot). Factory reset and caches cleared again but still the same.
6. Used Odin to flash the Bell stock system, recovery, and boot from this thread: http://forum.xda-developers.com/showthread.php?t=1599127
Did a factory reset using the stock recovery after this was flashed as well.
7. Having the same issues on the stock rom as I had on FJs rom and CM9.
8. I was eventually able to get the phone to allow me to see the baseband version before it rebooted (took a few tries) and I see the baseband is still UCLF6. I thought the baseband would have been reset too but I guess not.
Is there something else I should do? Will popping CWM recovery on there again and flashing another modem fix this?
How would that justify a warranty return? It's a result of you flashing custom software, warranty returns are for manufacturer defects. Are you restoring system apps or something in tibu? Otherwise just keep trying to get back completely stock and completely wipe everything.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
This happens sometimes. You just have to find and flash the stock modem through odin to get it 100 percent out of the box.
As far as the warranty return, no one would allow it because you have no way of proving that the problems with the phone are not directly related to your modifications to the device even if they are not.
However, I would suggest flashing the stock modem and then reformatting your device through kies as a last resort. If this does not still work, I would suggest (although never used) the flash counter reset zip once youre on stock and sending it in for repair.
Hope you get it up and working
welchertc said:
How would that justify a warranty return? It's a result of you flashing custom software, warranty returns are for manufacturer defects. Are you restoring system apps or something in tibu? Otherwise just keep trying to get back completely stock and completely wipe everything.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Understood about warranty of course.
- not restoring anything...as mentioned, everything is always set up from scratch, including all apps from Play store.
- I'm trying to get back to stock, and everything looks stock except that my baseband reads UCLF6, which I assume is not stock GB. I have tried flashing the modems, kernals, and roms found here http://forum.xda-developers.com/showthread.php?t=1506330 and here http://forum.xda-developers.com/showthread.php?t=1599127
This is why I am asking if my hardware seems defective, or if there is something amiss in what I am trying to do (if I am seeing UCLF6 in my baseband, I am assuming I am missing something).
Last attempt to get rid of the UCLF6 baseband I downloaded this modem: http://forum.xda-developers.com/showthread.php?t=1506330 , did a reset, wiped caches, and still showing UCLF6.
Don't know what I did differently, but I tried pterry30's modem and flashed via CWM (I could not find an Odin modem tar) and my phone seems normal now (but very stock) and I got the 'mugla' version of the modem listed in my system settings.
Thanks for the suggestions...hopefully its really fixed. Since I went through all this trouble I'll try Bell's ICS update.
Problems like this are great learning tools...but a bit stressful lol
Happy all is well. Good luck.
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
I'm guessing the infamous brick bug is responsible.
What was your configuration before flashing the new ROM?
What ROM and kernel?
Sent from a GT-I9100 having a mind of its own
TechnicallyImpaired said:
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
Click to expand...
Click to collapse
I'm sorry bro but you might have suffered from the infamous super brick bug and your inability to read.
Solution:
Package the phone and send it to Samsung repair center
Swyped from Samsung Galaxy SII
TechnicallyImpaired said:
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
Click to expand...
Click to collapse
No offense to the two responders above me, but you can ignore them.
The problem is that you attempted to flash a firmware not meant for your phone.
You yourself said you have an SGH-I757. Well, that ICS ROM you linked that you tried to flash is for the GT-i9100. The two models have different hardware, so firmwares, kernels, and ROMs are NOT compatible between them.
This probably screwed up the bootloader. Your only course of action at this point will probably be either JTag repair, or sending it to Samsung for repair.
ctomgee said:
No offense to the two responders above me, but you can ignore them.
The problem is that you attempted to flash a firmware not meant for your phone.
You yourself said you have an SGH-I757. Well, that ICS ROM you linked that you tried to flash is for the GT-i9100. The two models have different hardware, so firmwares, kernels, and ROMs are NOT compatible between them.
This probably screwed up the bootloader. Your only course of action at this point will probably be either JTag repair, or sending it to Samsung for repair.
Click to expand...
Click to collapse
Thanks for not being a douche bag in your response, much appreciated. Thanks for the info BTW, I just got myself a new one and I'll be more careful now. My biggest annoyance with native ICS on this phone is one is looks like gingerbread and two it comes with a tonne of bloatware that you can't remove without rooting ect. At this point should I flash CWM again since it installed successfully last time, root, and use that as a method to remove the unwanted bloatware. I'm so hesitant to flash this phone now, it seems it was much ease on my SGS1.
TechnicallyImpaired said:
Thanks for not being a douche bag in your response, much appreciated. Thanks for the info BTW, I just got myself a new one and I'll be more careful now. My biggest annoyance with native ICS on this phone is one is looks like gingerbread and two it comes with a tonne of bloatware that you can't remove without rooting ect. At this point should I flash CWM again since it installed successfully last time, root, and use that as a method to remove the unwanted bloatware. I'm so hesitant to flash this phone now, it seems it was much ease on my SGS1.
Click to expand...
Click to collapse
Just make sure you stick to flashing things meant for your model. Those things compatible with your device will be clearly labeled with the model number.
Problem is the SGH-i757 doesn't have its own forum, so stuff for it gets posted in here.
ctomgee said:
Just make sure you stick to flashing things meant for your model. Those things compatible with your device will be clearly labeled with the model number.
Problem is the SGH-i757 doesn't have its own forum, so stuff for it gets posted in here.
Click to expand...
Click to collapse
Yup, I've found a few but I also have a few questions maybe you can help me with. According to this thread ( http://forum.xda-developers.com/showthread.php?t=1756242) only stock ICS v 4.0.4 is effected by this superbrick. The SGS2 I hardbricked earlier today was updated to this version via keys to 4.0.4 before installing the custom ROM. So provided I stick to ROMS such as lets say the one here (http://forum.xda-developers.com/showthread.php?t=1740188) and avoid upgrading to 4.0.4 I should be able to CWM + Flash + Root correct? I should also be able to do the standard factory reset / wipe cache / wipe dalvik? I also used the eMMC Brickbug Check app in the first post I liked under how to AVOID the superbrick and it came up saying my chip was sane. Thanks in advance and also I pressed the thank you button
TechnicallyImpaired said:
Yup, I've found a few but I also have a few questions maybe you can help me with. According to this thread ( http://forum.xda-developers.com/showthread.php?t=1756242) only stock ICS v 4.0.4 is effected by this superbrick. The SGS2 I hardbricked earlier today was updated to this version via keys to 4.0.4 before installing the custom ROM. So provided I stick to ROMS such as lets say the one here (http://forum.xda-developers.com/showthread.php?t=1740188) and avoid upgrading to 4.0.4 I should be able to CWM + Flash + Root correct? I should also be able to do the standard factory reset / wipe cache / wipe dalvik? I also used the eMMC Brickbug Check app in the first post I liked under how to AVOID the superbrick and it came up saying my chip was sane. Thanks in advance and also I pressed the thank you button
Click to expand...
Click to collapse
The brick bug may not affect you at all. The most common Galaxy S2 affected is the i9100, which we have established is NOT your device. And you already used the app that said your chip is "sane", so it's confirmed you don't have to worry about it.
Again, you bricked the device by flashing a ROM meant for a different device. Had nothing to do with the brick bug.
ctomgee said:
The brick bug may not affect you at all. The most common Galaxy S2 affected is the i9100, which we have established is NOT your device. And you already used the app that said your chip is "sane", so it's confirmed you don't have to worry about it.
Again, you bricked the device by flashing a ROM meant for a different device. Had nothing to do with the brick bug.
Click to expand...
Click to collapse
Thanks, I wasn't aware flashing a rom not meant for your device can cause a hard brick to the point where you cant turn anything on and no buttons are responsive ect. Thanks for the help.
Dear All
I've had the unpleasant problem of having used ICS encryption then using CWM recovery to wipe partititions and have even flashed by odin to to try and get back to defaults.
Gingerbread backups work fine (presumably they arent encryption aware) but ICS or JB roms insist on asking for a boot unlock password which I now can't get round.
Found some search results on the Galaxy Nexus forum about using flashboot to install a stock rom - any pointers much appreciated otherwise I'm doomed to GB roms.
Thanks for your attention.
TK0 said:
Dear All
I've had the unpleasant problem of having used ICS encryption then using CWM recovery to wipe partititions and have even flashed by odin to to try and get back to defaults.
Gingerbread backups work fine (presumably they arent encryption aware) but ICS or JB roms insist on asking for a boot unlock password which I now can't get round.
Found some search results on the Galaxy Nexus forum about using flashboot to install a stock rom - any pointers much appreciated otherwise I'm doomed to GB roms.
Thanks for your attention.
Click to expand...
Click to collapse
Let me get this straight, you were on ICS, JB, ICS again, went all the way back to GB and both ICS and JB keep asking for a code?
You didn't wipe data during the flashing journey, did you?
Sounds about right, been having a lot of stability issues here and there.
I have been doing the data, cache and dalvik wipes in clockwork each time and have also on occasion used the format emmc and sdcard for good measure
If theres a more complete/better method of wiping to get rid of any trace of encryption I'd love to be enlightened
TK0 said:
Sounds about right, been having a lot of stability issues here and there.
I have been doing the data, cache and dalvik wipes in clockwork each time and have also on occasion used the format emmc and sdcard for good measure
If theres a more complete/better method of wiping to get rid of any trace of encryption I'd love to be enlightened
Click to expand...
Click to collapse
hum.....with those wipes you shouldn't be hearing about previous ROMs...I'll look into it tomorrow.
You might as well search for "Full Data Wipe". You might have missed a wipe there (dunno which one right now).
gastonw said:
hum.....with those wipes you shouldn't be hearing about previous ROMs...I'll look into it tomorrow.
You might as well search for "Full Data Wipe". You might have missed a wipe there (dunno which one right now).
Click to expand...
Click to collapse
Attempted following full wipe instructions using stock (GB) rom and factory reset plus format of sdcard and internal storage - same problem. I wonder if some kind of repartition is required? odin has an option but without the pit file you are apparently doomed
TK0 said:
Attempted following full wipe instructions using stock (GB) rom and factory reset plus format of sdcard and internal storage - same problem. I wonder if some kind of repartition is required? odin has an option but without the pit file you are apparently doomed
Click to expand...
Click to collapse
I don't think this is about repartitions, tried flashing back to ICS?
Monsters never scared me, pit files do.
Will try a stock ICS now and get back.
After a factory reset what could possibly remain to indicate encryption? only googling I've found suggests trying to use adb in recovery to repartition using mkfs - however this isn't something I could pull off
UPDATE: SUCCESS - ICS stock from sammobile installs via ODIN OK and boots without asking for any encryption password.
Thanks for your help gastonw!
I guess the problem was something to do with DarkyRom? or its method of installation, curious that it was to do with encryption which I was previously using. In any case at least my phone isnt consigned to a life of GB!
SOLUTION FOR ANYONE FOLLOWING/WITH ISSUE ALSO:
I have now successfully flashed my JB rom also, I think there are two possibilities as to why this has now worked:
1. gastonw's suggestion of flashing stock ICS and performing an ICS factory reset somehow properly wiped the phone to factory.
2. I realised that on flashing JB (a process which was to odin a GB with Clockwork, wipe, then clockwork the JB ROM then wipe) my first boot would hang and I would flash the JB rom again - perhaps this was causing the issue. To fix I simply pulled the battery out on first boot hang and restarted - rom loads. I.e. this might have been a red herring and coincidentally talking about encryption.
Good luck
Glad to hear that man.
And no, flashing ain't stopping now for you
I recently had an issue with my Note 2 when I went to flash (yet another) ROM. I tried to run the "Wipe Data/Factory reset" from within CWMR (Touch), and it would lock up/freeze during the format /data portion of the wipe. It would eventually just reboot itself back into recovery mode.
I eventually got to a point where I tried flashing a TW4.3 (rooted) stock ROM, but it was flaking out because obviously the data partition never did get properly wiped (lots of FC's, etc after it finished booting). I tried to do a factory wipe from WITHIN the booted OS. This took me a the android with the spinning blue "heart" and pseudo-progress bar. It then just stayed on this screen for 3-5 minutes and then rebooted back to the screen over and over.
I eventually gave up and ODIN'ed it back to the a stock, unrooted state (but I chose NOT to go to the latest 4.3 release so I could still possibly unlock again).
For some reason, the stock recovery doesn't have any issues formatting the /data partition now. I actually went back to stock thinking I might have to file a warranty claim on the phone (and I could right now, since it appears to be fully stock in all the various places you might look for tampering).
I am still concerned, however, that there is a corruption present in the /data partition and I would like to know if there is a way to test for it. Do I need to re-root just to test it?
spiff72 said:
I recently had an issue with my Note 2 when I went to flash (yet another) ROM. I tried to run the "Wipe Data/Factory reset" from within CWMR (Touch), and it would lock up/freeze during the format /data portion of the wipe. It would eventually just reboot itself back into recovery mode.
I eventually got to a point where I tried flashing a TW4.3 (rooted) stock ROM, but it was flaking out because obviously the data partition never did get properly wiped (lots of FC's, etc after it finished booting). I tried to do a factory wipe from WITHIN the booted OS. This took me a the android with the spinning blue "heart" and pseudo-progress bar. It then just stayed on this screen for 3-5 minutes and then rebooted back to the screen over and over.
I eventually gave up and ODIN'ed it back to the a stock, unrooted state (but I chose NOT to go to the latest 4.3 release so I could still possibly unlock again).
For some reason, the stock recovery doesn't have any issues formatting the /data partition now. I actually went back to stock thinking I might have to file a warranty claim on the phone (and I could right now, since it appears to be fully stock in all the various places you might look for tampering).
I am still concerned, however, that there is a corruption present in the /data partition and I would like to know if there is a way to test for it. Do I need to re-root just to test it?
Click to expand...
Click to collapse
I had this issue as well at one point, my phone actually soft bricked. What you need to do is use the pit file thru odin, flash any firmware in odin EXCEPT THE NEW OTA. Then you need to unlock again using the proper version of CASUAL for the base in which you relocked.
Sent from my Galaxy Note II
icedventimocha said:
I had this issue as well at one point, my phone actually soft bricked. What you need to do is use the pit file thru odin, flash any firmware in odin EXCEPT THE NEW OTA. Then you need to unlock again using the proper version of CASUAL for the base in which you relocked.
Sent from my Galaxy Note II
Click to expand...
Click to collapse
Thanks...
I actually went through the whole revert to stock with ODIN (but I used the PDA button/file). Was this the wrong approach? It sounds like I ended up at the same point as you...
And of course I couldn't leave it alone last night and unlocked and rooted with Casual last night. So far no issues with recovery data wipes.
I would like to understand what the problem was! Is it hardware, or a flash gone wrong?
I've looked all over for answers on this. I hope I didn't miss something, but here is my issue:
After being fed up with Touchwiz, I tried flashing AOSP ROMs instead. Ever since then, every AOSP ROM I flash will freeze during boot (usually it freezes after 15-20 seconds), I'll see a glitched image for 10 seconds, and then reboot. This bootloop has happened with AICP, Resurrection Remix, and a few others. I'm about to try CyanogenMod, but I assume that will fail as well since the others were mostly based off CM. I always wipe data, cache, and dalvik before flashing (sometimes system too, and now internal storage to try to fix this issue).
Can anyone figure this out?
I have very limited access to a PC and my Mac refuses to recognize this phone in download mode, so Odin isn't readily available and Heimdall has been no good so far.
G900TUVS1FOL1
EDIT: Apparently EVERYTHING is bootlooping this phone. I flashed other Touchwiz-based ROM's and those aren't working. Finally I returned to stock firmware using Kies, and I'm STILL stuck in an endless loop.
I NEED HELP. SERIOUSLY.
This is probably a bad idea, but I'm headed to T-Mobile to try and get help. I can't afford to wait.
t3st4m3nt said:
This is probably a bad idea, but I'm headed to T-Mobile to try and get help. I can't afford to wait.
Click to expand...
Click to collapse
in twrp you need to format data partion and wipe internal storage cache,data, and davilk cache
then use kies for emergency restore
malbert16442 said:
in twrp you need to format data partion and wipe internal storage cache,data, and davilk cache
then use kies for emergency restore
Click to expand...
Click to collapse
Honestly, I feel like I should've just stuck with your ROMs
I've done all of the above, and I do so every time I flash a ROM. I tried re-flashing after wiping system, no good. And the restore from Kies failed to fix the issue.
Kies removed twrp, so I was able to take it to a Samsung Center at Best Buy without the device drawing suspicion of having been rooted (they ignore Knox at this one), and they failed to solve the issue with a home reset. Right now they have no idea what is happening, and neither do I.