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
Current setup - stock - 4.0.4 - I have not made any modifications to this phone so far other than upgrading it from GB OTA. It is the standard unlocked SIM free UK/Irelend edition.
PDA: I9100XWLPT
PHONE: I9100XXLQ6
CSC: I9100XEULPA
I am interested in trying the stock leaked version of 4.1.2 - actually I'm fed up with waiting for the official release which always seems to be "coming in the very near future" but never arrives.
I have read around extensively on this site and others about how to do this, but still have some questions that I would be grateful if someone could answer.
1. Brick bug - I have run eMMC check and it reports that it reports: NO. Sane chip. Does this mean that I have nothing to fear regarding factory resets/data wiping on 4.0.4?
2. Some mention that USB debugging should be checked - others make not mention of it at all. Should USB debugging be checked in this case when going up to 4.1.2 or back down to 4.0.4?
3. Should the SIM card be removed before flashing with odin or is it alright to leave it in?
4. When the phone reboots after flashing 4.1.2 with odin, some tutorials do nothing and let the phone reboot - others suggest removing the battery as it begins to reboot and then booting into stock recovery mode and doing a factory reset, wipe cache. Some even say also wipe dalvik cache. Is this battery removal step necessary? Or should the phone be left to attempt to boot and if the process hangs enter recovery and reset/wipe cache?
5. I have read in a couple of cases that the SIM lock has been activated after this flashing procedure on a previously unlocked phone. I have found an unlock apk on this forum that can resolve this issue. But why does it happen? How common is this problem?
6. In my 4.1.2 download from Sammobile there are 2 files that are not mentioned in the articles I have read. emmc_EXT4_16GB.pit and emmc_EXT4_32GB.pit - what are these for? Are they needed for this procedure?
7. How long should the reboot process take after the flashing is complete? - or after how long should I start to get worried if it seems to be stuck?
8. If I wish to return to stock 4.0.4 (here the brick bug is the problem yes?)- is the procedure the same as flashing 4.1.2? And if I do go back to 4.0.4 stock will the phone work with KIES again?
9. I have odin 3.07 - is this version appropriate for this procedure?
dimbo33 said:
Current setup - stock - 4.0.4 - I have not made any modifications to this phone so far other than upgrading it from GB OTA. It is the standard unlocked SIM free UK/Irelend edition.
PDA: I9100XWLPT
PHONE: I9100XXLQ6
CSC: I9100XEULPA
I am interested in trying the stock leaked version of 4.1.2 - actually I'm fed up with waiting for the official release which always seems to be "coming in the very near future" but never arrives.
I have read around extensively on this site and others about how to do this, but still have some questions that I would be grateful if someone could answer.
1. Brick bug - I have run eMMC check and it reports that it reports: NO. Sane chip. Does this mean that I have nothing to fear regarding factory resets/data wiping on 4.0.4?
Yes. If you have the sane/safe chip no need to worry.
2. Some mention that USB debugging should be checked - others make not mention of it at all. Should USB debugging be checked in this case when going up to 4.1.2 or back down to 4.0.4?
Doesn't matter whether it is on or off. It's just for debugging. I usually keep it on since you don't know when it might be useful. There is no harm in keeping it ticked.
3. Should the SIM card be removed before flashing with odin or is it alright to leave it in?
No need to remove sim card.
4. When the phone reboots after flashing 4.1.2 with odin, some tutorials do nothing and let the phone reboot - others suggest removing the battery as it begins to reboot and then booting into stock recovery mode and doing a factory reset, wipe cache. Some even say also wipe dalvik cache. Is this battery removal step necessary? Or should the phone be left to attempt to boot and if the process hangs enter recovery and reset/wipe cache?
After flashing, your phone will restart. If it doesn't go past the samsung logo, you'll need to pull out the battery, reinsert it, boot into recovery and perform a factory reset. Wiping cache and dalvik isn't necessary. However, if you do boot into recovery (which most certainly you'll have to, to do the data wipe), it takes less than 15 seconds to wipe the cache and dalvik.
5. I have read in a couple of cases that the SIM lock has been activated after this flashing procedure on a previously unlocked phone. I have found an unlock apk on this forum that can resolve this issue. But why does it happen? How common is this problem?
I believe it's designed to be that way. However, I am not sure about this one. Sorry.
6. In my 4.1.2 download from Sammobile there are 2 files that are not mentioned in the articles I have read. emmc_EXT4_16GB.pit and emmc_EXT4_32GB.pit - what are these for? Are they needed for this procedure?
No need for the .pit files. Better avoid them at all costs.
7. How long should the reboot process take after the flashing is complete? - or after how long should I start to get worried if it seems to be stuck?
Don't worry. You'll know when to worry ... Taking upto 5 minutes is perhaps normal. After that, update here if you think there is a problem.
8. If I wish to return to stock 4.0.4 (here the brick bug is the problem yes?)- is the procedure the same as flashing 4.1.2? And if I do go back to 4.0.4 stock will the phone work with KIES again?
Yes, and yes.
9. I have odin 3.07 - is this version appropriate for this procedure?
Better use v1.83 or v1.85. I've read a complaint against the latest one. Old is gold in some cases
Click to expand...
Click to collapse
I've replied under every question. Didn't want to quote the whole thing then write my answers, or scroll up and down continuously. Good luck and don't worry
Sent from my GT-I9100 using Tapatalk 2
Spiralzz said:
I've replied under every question. Didn't want to quote the whole thing then write my answers, or scroll up and down continuously. Good luck and don't worry
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your answers. I appreciate it. I've done this kind of thing loads of times on other types of device, but I'm always nervous as hell when it's the first time and don't want any holes in my understanding of the process.
dimbo33 said:
Current setup - stock - 4.0.4 - I have not made any modifications to this phone so far other than upgrading it from GB OTA. It is the standard unlocked SIM free UK/Irelend edition.
PDA: I9100XWLPT
PHONE: I9100XXLQ6
CSC: I9100XEULPA
I am interested in trying the stock leaked version of 4.1.2 - actually I'm fed up with waiting for the official release which always seems to be "coming in the very near future" but never arrives.
I have read around extensively on this site and others about how to do this, but still have some questions that I would be grateful if someone could answer.
1. Brick bug - I have run eMMC check and it reports that it reports: NO. Sane chip. Does this mean that I have nothing to fear regarding factory resets/data wiping on 4.0.4?
2. Some mention that USB debugging should be checked - others make not mention of it at all. Should USB debugging be checked in this case when going up to 4.1.2 or back down to 4.0.4?
3. Should the SIM card be removed before flashing with odin or is it alright to leave it in?
4. When the phone reboots after flashing 4.1.2 with odin, some tutorials do nothing and let the phone reboot - others suggest removing the battery as it begins to reboot and then booting into stock recovery mode and doing a factory reset, wipe cache. Some even say also wipe dalvik cache. Is this battery removal step necessary? Or should the phone be left to attempt to boot and if the process hangs enter recovery and reset/wipe cache?
5. I have read in a couple of cases that the SIM lock has been activated after this flashing procedure on a previously unlocked phone. I have found an unlock apk on this forum that can resolve this issue. But why does it happen? How common is this problem?
6. In my 4.1.2 download from Sammobile there are 2 files that are not mentioned in the articles I have read. emmc_EXT4_16GB.pit and emmc_EXT4_32GB.pit - what are these for? Are they needed for this procedure?
7. How long should the reboot process take after the flashing is complete? - or after how long should I start to get worried if it seems to be stuck?
8. If I wish to return to stock 4.0.4 (here the brick bug is the problem yes?)- is the procedure the same as flashing 4.1.2? And if I do go back to 4.0.4 stock will the phone work with KIES again?
9. I have odin 3.07 - is this version appropriate for this procedure?
Click to expand...
Click to collapse
Firstly,
Idk exactly about USB debugging but what i do know is that...
"USB Debugging is intended for development purposes only. It can be used to copy data between your computer and your device, install applications on your device without notification, and read log data." A few apps use it, like the aforementioned PdaNet app. USB Debugging can also be used with ADB when issuing commands from a command line on your computer to your Android handset or tablet. One-Click root apps often require USB Debugging to be enabled to deliver the exploit that roots your device.
SIM card wouldn't affect anything, so it doesn't matter if you leave it in the phone..
After Flashing the JB, first check whether the phone goes into boot loop or anything like that....if you experience any problems then do the factory reset, wipe cache...though its usually recommended to factory reset anyways..
I don't think we need to flash the "emmc_EXT4_16GB.pit" or the other pit file..
The reboot process shouldn't take more than 5-10 minutes max..
Well i have gone from custom ROM 4.1.2 XXLSJ back to the stock 4.0.4 using the usual flashing steps of ODIN....I didn't experience any problems..
If its anything above Odin3v1.85 it shouldn't be a problem...
Press thanx if i helped..
Is there any need to do any factory reset/cache wiping from recovery before flashing 4.1.2?
I guess that when I flashed jb leak I had all those questions, and maybe a couple of more.
Then I read about Mobile Odin, flashed & rooted my device in half a smoke (3 mins). All I had to do was select the 3 tar files.
The flash did network lock my device. Galaxysim Unlock solved it for me.
good luck and happy flashing.
dimbo33 said:
Is there any need to do any factory reset/cache wiping from recovery before flashing 4.1.2?
Click to expand...
Click to collapse
Only once. Either before flashing the ROM, or after. Order doesn't matter.
Sent from my GT-I9100 using Tapatalk 2
Spiralzz said:
Only once. Either before flashing the ROM, or after. Order doesn't matter.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
I would imagine then it's better to do it whilst on 4.0.4 prior to flashing (since I have the sane chip) so that you don't get the possible failed boot after flashing 4.1.2 with odin.
So after doing the wipes in recovery prior to flashing, is the phone turned off by a long press of the power button?
dimbo33 said:
I would imagine then it's better to do it prior to flashing so that you don't get the possible failed boot after flashing 4.1.2 with odin.
So after doing the wipes in recovery prior to flashing, is the phone turned off by a long press of the power button?
Click to expand...
Click to collapse
No, I don't think so. Come to think of it, I've never tried that A battery pull works though
Sent from my GT-I9100 using Tapatalk 2
Spiralzz said:
No, I don't think so. Come to think of it, I've never tried that A battery pull works though
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Do you mean it's not better to factory reset before flashing or the long press doesn't turn off the phone from recovery (in which case best to pull the battery out)?
dimbo33 said:
I would imagine then it's better to do it whilst on 4.0.4 prior to flashing (since I have the sane chip) so that you don't get the possible failed boot after flashing 4.1.2 with odin.
So after doing the wipes in recovery prior to flashing, is the phone turned off by a long press of the power button?
Click to expand...
Click to collapse
Well since your flashing 4.0.4 its pretty much a must to also install custom kernel to avoid possible silly bricks by wiping data.
So simply flash rom via odin and then do same for custom kernel like Siyah and then reboot into kernel and wipe data/factory reset and you're off
TheATHEiST said:
Well since your flashing 4.0.4 its pretty much a must to also install custom kernel to avoid possible silly bricks by wiping data.
So simply flash rom via odin and then do same for custom kernel like Siyah and then reboot into kernel and wipe data/factory reset and you're off
Click to expand...
Click to collapse
Sane chip, he's already off.
gastonw said:
Sane chip, he's already off.
Click to expand...
Click to collapse
Yeah didnt notice OP was on sane chip. Was speaking more in general though anyway.
TheATHEiST said:
Yeah didnt notice OP was on sane chip. Was speaking more in general though anyway.
Click to expand...
Click to collapse
Sometimes I dream my phone is bricked or scracthed. This Q&A thing might be messing with my head.
gastonw said:
Sometimes I dream my phone is bricked or scracthed. This Q&A thing might be messing with my head.
Click to expand...
Click to collapse
:laugh:
gastonw said:
Sometimes I dream my phone is bricked or scracthed. This Q&A thing might be messing with my head.
Click to expand...
Click to collapse
I know what you mean. I haven't even done this procedure yet and I'm dreaming of bricked phones/ corrupted IMEIs etc.
Probably a bit melodramatic I know.
It did occur to me that instead of flashing stock 4.1.2 from stock 4.0.4, it may be better to flash the Siyah kernel to my current 4.0.4. This way I can back up efs, do a nandroid and titanium - before embarking on fully fledged ROM flashing etc.
What do you think?
dimbo33 said:
I know what you mean. I haven't even done this procedure yet and I'm dreaming of bricked phones/ corrupted IMEIs etc.
Probably a bit melodramatic I know.
It did occur to me that instead of flashing stock 4.1.2 from stock 4.0.4, it may be better to flash the Siyah kernel to my current 4.0.4. This way I can back up efs, do a nandroid and titanium - before embarking on fully fledged ROM flashing etc.
What do you think?
Click to expand...
Click to collapse
Well...the beauty of flashing is that you can do both Stock & Custom. You can also Dual Boot if you want.
My advice is this:
1) Always Back up EFS folder (HC-ktool is a good app for that).
2) Get Titanium Back up Pro.
3) Flash CMW or Flash siyah, it can't never hurt (well, if you go JB leak, might wanna try usin stock kernel first and the flash a custom kernel)
4) Get mobile odin Pro (so you can flash as many stock ROMs as you like, with the chance of getting bricked or soft bricked close to none + you'll always be rooted)
5) Read about ROMs features. You are the only person in the world that knows what ROM will fit your needs.
6) Start flashing.
7) If you are scared about bricks, read the bricked device's threads. That way you will know what NOT to do.
In my experience, I went jb and never came back.
Now, you really dream about IMEI, lol, that's something
I haven't flashed 4.1.2 yet. I was going to do it last night but realised I had forgotten my GPS active and the battery went flat. I took this as an omen and aborted the mission.
I've been reading around the subject for days. There seem to be so many people that encounter problems that it is difficult to have any perspective. The myriad of users that flash stuff via odin without any trouble obviously don't post that it went well - so you read 10 problem posts and never see the other thousand flashes that went without a hitch.
I also have read on xda that the leaked JB 4.1.2 is somewhat buggy. I'm not sure how buggy, but the lock screen freeze would be annoying in practice.
Again the carrot of official jb has been dangled before us - supposedly in February now.......Given that this will probably be the last official release for the S2 I might hang on and wait for it - then embark on the routing/custom ROM journey.
dimbo33 said:
I haven't flashed 4.1.2 yet. I was going to do it last night but realised I had forgotten my GPS active and the battery went flat. I took this as an omen and aborted the mission.
I've been reading around the subject for days. There seem to be so many people that encounter problems that it is difficult to have any perspective. The myriad of users that flash stuff via odin without any trouble obviously don't post that it went well - so you read 10 problem posts and never see the other thousand flashes that went without a hitch.
I also have read on xda that the leaked JB 4.1.2 is somewhat buggy. I'm not sure how buggy, but the lock screen freeze would be annoying in practice.
Again the carrot of official jb has been dangled before us - supposedly in February now.......Given that this will probably be the last official release for the S2 I might hang on and wait for it - then embark on the routing/custom ROM journey.
Click to expand...
Click to collapse
Well, you read 10 problems while flashing, right now we got 50.000 users going thru these threads, here, at XDA.
Jb is buggy, it's a leak, but too buggy? don't think so.
As for the bugs, we got plenty of people coming up with work arounds & fixes every day. In my case, I only have the lockscreen issue (let's face it, it doesn't always happens, like maybe 1 time a day and it's only for 3 seconds till the capacitive buttons light up. If you lock the screen and re unlock it with the power button, you're off. For me, it's not even an issue). I don't even remember when was the last time I had this issue, maybe 3 days ago now that I think about it.
Where's flashing, there's risk. TRUE. That's why I layed the Mobile Odin Pro option for you, that could be the best way to lose you flashing's fright.
BTW: we are getting the lime pie update, SII Plus was released just now
gastonw said:
Where's flashing, there's risk. TRUE. That's why I layed the Mobile Odin Pro option for you, that could be the best way to lose you flashing's fright.
Click to expand...
Click to collapse
I have had a look at mobile Odin Pro and I like the look of it. Thanks for the tip. To use it I need to root the S2.
I have seen this guide http://forum.xda-developers.com/showthread.php?t=1501719 - this seems simple. I could also flash the Siyah kernel via Odin. Which root method would you recommend? The first method seems to avoid the triangle issue - although this is not a big deal.
With a routed device I can backup efs etc before flashing anything else. Does the efs folder contain the simlock status?
Also, as you know I have been looking at the leaked jb, but perhaps it might be worth looking at neatrom 4.1.2 (or similar) instead?
I seem to get the impression that mobile Odin Pro is a safe method. Is it safer than using PC Odin?
Hey guys,
I'd like to return to stock samsung rom, resetting the device to factory setting (keep reading).
Reason for this is
1 I'am experiencing fastidious UI lags issue.
2 I've done several "Restore factory Setting/Wipe all data" and I can see folders of applications I installed at least three roms ago (and not installed anymore). Some of them are empty, some are not.
Maybe my device is just imploding bacause of the number of apps he keeps managing.
Maybe he doesn't like me anymore,
or maybe he is dying of cancer. :crying:
Info about my device:
Kernel: Siyah 1.8.9
1st ROM: Samsung 4.1.1
2nd ROM: CM10.1, 20120117 build
Goal:
I'd like to return to Stock Kernel with the stock 4.1.2 Samsung firmware.
So, how can I REALLY reset my device, starting againg form where I indicated?
domenicop said:
Hey guys,
I'd like to return to stock samsung rom, resetting the device to factory setting (keep reading).
Reason for this is
1 I'am experiencing fastidious UI lags issue.
2 I've done several "Restore factory Setting/Wipe all data" and I can see folders of applications I installed at least three roms ago (and not installed anymore). Some of them are empty, some are not.
Maybe my device is just imploding bacause of the number of apps he keeps managing.
Maybe he doesn't like me anymore,
or maybe he is dying of cancer. :crying:
Info about my device:
Kernel: Siyah 1.8.9
1st ROM: Samsung 4.1.1
2nd ROM: CM10.1, 20120117 build
Goal:
I'd like to return to Stock Kernel with the stock 4.1.2 Samsung firmware.
So, how can I REALLY reset my device, starting againg form where I indicated?
Click to expand...
Click to collapse
Anyone help????//??
The absolute cleanest way, is to do a mega wipe. Use Titanium Backup to save all the apps you want/need (NO SYSTEM APPS). Then, Factory Reset/Wipe Data, wipe internal sd card and wipe external sd (if you have one). Backup all pictures, photos and files you want on your pc first, then wipe everything. The Megawipe script can help you with this. Follow up by downloading one of the new 4.1.2 deodexed roms (Preferably LKC or LLA). You can keep the stock kernel or choose from my main 2 - Perseus Kernel or Yank kernel
Umh.. I'm not sure I got it.
First, I should remove Siyah kernel and the second ROM right?
How can I do it?
Will the Siyah Kernel be overwritten when I'll write the Stock Samsung 4.1.2 firmware?
domenicop said:
Will the Siyah Kernel be overwritten when I'll write the Stock Samsung 4.1.2 firmware?
Click to expand...
Click to collapse
Yes.
There is a sticky .
One run Triangle Away reset rom counter to zero .
Two flash your original saved stock rom Via Odin = wipes phone .
Three factory reset .
Four boot to download mode check status original and count is 0.
Boot phone settings about phone Status device status not modified .
Finally check there are no left over root apps on the phone .
jje
Need detailed info on this, anyone willing to help?
all the details are there for you to read
Thank you, anyway I'd like to advise that flashing via Odin doesn't format anything.
Step 0 is: Do a full data wipe (if you do it after triangle remover, I think counter will be incremented to 1, not tried though... )
domenicop said:
Thank you, anyway I'd like to advise that flashing via Odin doesn't format anything.
Step 0 is: Do a full data wipe (if you do it after triangle remover, I think counter will be incremented to 1, not tried though... )
Click to expand...
Click to collapse
Yes, yes, you are right, rest of the XDA community, with special attention to author of this are wrong, otherwise you have the headache and your nanny doesn't know what to do except from calling parents.
Would someone buy this kiddo a happy meal, please?
PS. Following the XDA RULES, especially search BEFORE posting, does not hurt.
Now im ****ed up! Im stuck at boot logo (samsung) need urgent help. it all happens after installing font installer. My phone was rooted. I want a clean format and i ended at this problem.
sometime flashing rom and than flah another rom may cause lag even the rom are really smooth. Try this, it work for me. Wipe Data, Cache Partition, Clear dalvike cache, format system and format preload. As far as i know, preload where it chaching framework. Sometime when flashing and keep flashing rom that different framework, the cache still there. that may cause lag.
zebroid said:
Now im ****ed up! Im stuck at boot logo (samsung) need urgent help. it all happens after installing font installer. My phone was rooted. I want a clean format and i ended at this problem.
Click to expand...
Click to collapse
That coz u replace roboto-bold. Lol. Im using JB multipack v3. It got quite font collection there. No bootloop. And yes, JB multipack replace roboto-bolt but no bootloop
zebroid said:
Now im ****ed up! Im stuck at boot logo (samsung) need urgent help. it all happens after installing font installer. My phone was rooted. I want a clean format and i ended at this problem.
Click to expand...
Click to collapse
If you want a clean install, without lags, I'd recommend not messing about with the fonts. Try running it stock for a while and see if your lags have gone, before fiddling with it.
Sent from my GT-I9300 using Tapatalk 2
What is all the complaining about? Do all of you complaining only have 1GB of RAM? Do you have windows animations turned off which also helps?
Sent from my 32GB Verizon Galaxy S III (SCH-1535) - stock (unrooted) JellyBean ROM with 64GB Class 10 MICROSDXC - using XDA Premium
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!