I have been having major problems with my i9100. The main symptom is that if shut down the fun in a violent way, i.e by taking the battery out or if it dies on me, then on restart it will just be stuck on the bootloader (the first i9100 screen) and won't boot. The only way i've found to fix this is by going into recovery and doing a factory reset, but this just keeps on happening.
i am using wanamlite rom LSD but this also happend with omega rom.
I tried to completely reset using odin, so i downloaded the odin image of JB but it wouldnt install, would take like 10 minutes and tell me it failed with no specific reason. So baisiaclly odin is off as well. i obviously also tried deleting chace delvik cache, reinstalling rom, installing different kernels (like siyah, it would even boot). nothing works! this is really frustrating, almost every day i need to completetly reinstall everything on my phone. Any ideas what is going on?
It seems that LS8 and LSD both have it. Try to flash LSJ or go back to ICS and wait for an official patch (fingers crossed).
Sent from my digital submersible hovercraft.
Nuke script can get your device all cleaned up.
Sent from the little guy
There is no bootloop or boot bug with JB roms. Its simply that people are not properley doing a clean install. A normal wipe data/factory reset is not enough in this case. Instead you need to format the /emmc and /sdcard or you can try the rom/kernel nuke scripts from dev forum.
Backup needed apps/appdata using TB pro or restore from a nandroid using appextractor.
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.
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
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!
I normally don't post unless I've exhausted every other option.
But this issue I am having has completely baffled me, and I really have exhausted every thing I know.
I was going through a rash of flashing roms on my I9300.
After finding an issue downgrading from 4.2.2 back down to 4.1.2. I Odin back to stock... so I though ok lets have another go at it.
However... Every ROM I flash will not boot (ie stuck @ Samsung I9300 screen). The flash goes well, MD5's are all ok, and I made sure to wipe data and cache like I've don't 500 times b4 on a dozen different phones.
I've even tried keeping the stock rom, simply rooted and just flashing another kernel both speedmod and siyah for 4.1.2... no go... no boot. I'm not quite sure what the issue is as it boots just fine on stock.
Any opinions?
Did you do a full wipe?
(Factory reset, Format system, cache, data and preload)
Sent from my GT-I9305 using XDA Premium HD app
Yep, full wipe each time, I even went so far as to format internal SD from CWM, just in case there was anything lingering.
did you try a mega wipe (will erase anything besides ext. sd)?
did you try to run a custom rom with stock kernel (as I understand stock rom & kernel are working?)?
Yep everything has been wiped down to the core.
And yes stock rom runs fine, and boots fine right off of odin, and even after running CF-Root.
I only get this no booting issue when trying to flash any other rom, even ones that I've previously flashed today b4 my first odin back to stock.
It def has something to do with the soft brick I recovered from earlier today, but I'm just not sure how or why, since I wiped everything and re flashed with odin.
Must be missing something tho.
Edit: Will try Flashing UltimaRom again with default setting and stock kernal see if anything changes.
Ok well i'm not really sure what I did, but I wiped everything again, from data to cache, to preload.
Reflashed ultimarom, this time on stock kernel, and whalha! Boot!
Then went back and flashed Siyah 1.8.9, and that booted ok aswell.
Not quite sure what the problem was but it seems to have been fixed.
Maybe phone was just being moody after all the flashes today!
Thanks for your help!
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.